The MPLS WG Archive

["Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>]

	Hi! I have few questions related to establishment of
point-to-multipoint
	connections using LSR-MIB. Your comments / suggestions will be
	appreciated.

	Thanks,
	sanjay

	Consider the following example:
	-------------------------------------
	In mplsInSegmentTable :
	{
		mplsInSegmentIfIndex	= 10
		mplsInSegmentLabel	= 100
		...
	}
	In mplsOutSegmentTable:
	{
		mplsOutSegmentIndex	= 1
		mplsOutSegmentIfIndex	= 11
		...
		----------------------------------
		mplsOutSegmentIndex	= 2
		mplsOutSegmentIfIndex	= 12
		...
	}

	As per the current indexing scheme, I have to create the following
	two rows in the mplsXCTable:
	{
		(create a row in this table using the index: 1.10.100.1)
		mplsXCIndex		= 1
		mplsXCLSPId		= 999
		....

		(create a row in this table using the index: 1.10.100.2)
		mplsXCIndex		= 2
		mplsXCLSPId		= 999
		....
	}
	
	Creation of the above mentioned row in the XC table will
automatically 
	populate the mplsInSegmentXCIndex and mplsOutSegmentXCIndex.

	Now the questions:
	-----------------------
	(a) mplsXCTable.1.10.100.2.mplsXCAdminStatus == down(2)
	=>The desired operational status of this segment (outgoing) is
	down and no packets should be forwarded on this segment.

	Is my assumption correct ?
		
	(b) Assume that mplsXCTable.1.10.100.1.mplsXCAdminStatus == down(2)

	What does this mean ? Is this the adminStatus of the incoming
segment
	or the outgoing segment ? or Does it represent the overall admin
Status of the 
	point-to-multipoint connection ?

	(c) Do you think, the XC model will be simpler, if we create only
ONE XC 
	entry for each connection and make the mplsInSegmentXCIndex &
	mplsOutSegmentXCIndex read-write (for SNMP initiated p2mp & mp2p 
	connections) ? The mplsInSegmentXCIndex & mplsOutSegmentXCIndex
	can still be automatically created for control protocol initiated
connections.
	[May also need to move the mplsXCLabelStackIndex to
outSegmentTable.]