The attached patch design allows the following combinations
1)											----------LUN A
											|
		---------Initiator IQN1----Session 1--------------<Target IQN A>------------------LUN B
		|
		|									----------LUN A
		|									|
Pool A	-----------------Initiator IQN2----Session 2--------------<Target IQN A>------------------LUN B
		|
		|
		---------Initiator IQN3----Session 3--------------<Target IQN B>------------------LUN C

		Target IQN A, B and C 


		Or, 
											----------LUN A
2)											|
		---------Initiator IQN1----Session 1--------------<Target IQN A>------------------LUN B
		|
		|									----------LUN C
		|									|
Pool A	-----------------Initiator IQN2----Session 2--------------<Target IQN B>------------------LUN D
		|
		|
		---------Initiator IQN3----Session 3--------------<Target IQN C>------------------LUN E



And also, the one that is possible today. One pool for each initiator IQN

3)
		------------------------------------					----------LUN A
		|									|
Pool A	----------------Initiator IQN1-----Session 1--------------<Target IQN A>------------------LUN B      
		|									|
		------------------------------------					----------LUN C


Today, the pool concept abstracts multiple LUNs behind a Target IQN into a common storage pool with a single session. The advantage of doing that with one pool is that managing the multiple LUNs with one pool becomes easy.

By also abstracting multiple initiator iqns into a pool concept, the management of storage pools becomes easy for the same reason - "LUN management".
At the same time it allows flexibility to realize a one pool per initiator iqn scenario that exists today.

Consider the following example.


If we use a separate pool for each initiator IQNs.
#virsh
<virsh> pool create <StorageArray_1_initiatoriqn1> 
<virsh> pool create <StorageArray_1_initiatoriqn2>
...........................................
...........................................
<virsh> pool create <StorageArray_1_initiatoriqnN>

If all pools associated with StorageArray_1 had to be destroyed then the following would happen.
<virsh> pool destroy <StorageArray_1_initiatoriqn1>
<virsh> pool destroy <StorageArray_1_initiatoriqn2>
...........................................
...........................................
<virsh> pool destroy <StorageArray_1_initiatoriqnN>


In the design that allows multiple initiator IQNs for a pool.
#virsh
<virsh> pool create <StorageArray_1>
In this design the XML contains Multiple initiator IQNs and multiple sessions can be established for the pool "StorageArray_1".
<virsh> pool destroy <StorageArray_1>
With this design all the sessions for this pool will get destroyed with one effort.