Subject: [CCAMP] Co-routed bidirectional XC entries

From: Srivatsan Raghavan <[email-masked]>
Date: Thu, 1 Jul 2010 16:57:31 +0530

Hi all

RFC 4802/03 introduces the gmplsTunnelDirection object which has an additional enumeration to specify a bidirectional tunnel.
This I assume, is used for co-routed bidirectional tunnels , independent of whether the tunnel is static or signalled.
So there is one tunnel row instance, and there is no reference as such to a remote tunnel number.
Is this understanding right ?

Secondly,
As per RFC 4803, for such a [ co-routed ] bidirectional tunnel, there are two XC entries, [for each of the directions]
Both these XC entries share the same XC index and that is how these two XC entries are co-related. In that sense the example in RFC 4803 needs to be corrected [ it shows
two different XC indices

example below :
In mplsXCTable:

{
mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000015,
mplsXCOutSegmentIndex = 0x00000012,
 ... < snip>
}

In mplsXCTable:
{
mplsXCIndex = 0x02,   ===> should also read 0x01
mplsXCInSegmentIndex = 0x00000016,
mplsXCOutSegmentIndex = 0x00000013,
.. < snip >
}

Is this understanding right that the example needs to be corrected
or is there some other interpretation to this ?

Thanks
Srivatsan

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."