The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2005-Jul> msg00016



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

[mpls] Last Call: 'Definition of an RRO node-id subobject' toProposed Standard

  • From: "Balaji, Hemanth" <hbalaji@riverstonenet.com>
  • Date: Fri, 15 Jul 2005 18:40:40 +0530
  • Thread-Index: AcWJMWyxTSGJgRZeS4O4zBrkDpSLfAAC3i0g
  • Thread-Topic: [mpls] Last Call: 'Definition of an RRO node-id subobject' toProposed Standard
  • X-MIME-Autoconverted: from quoted-printable to 8bit by cell.onecall.net id j6FD5hr05349


Hi,

   I have a small doubt. ( may be related to the following draft or just
related to RRO )

"
http://www.ietf.org/internet-drafts/draft-ietf-mpls-nodeid-subobject-06.
txt"

The doubt might sound basic but it would be helpful if the authors or
anyone else could clarify it.


My Question is this,

Since we are talking about Inter-area or Inter-AS  TE LSPs, what will be
the
Behavior in case of duplication of Node-ids. i.e Since the scope of
router/node id is within the AS, the same router-id could exist in
another AS. Though this can always be prevented by being careful with
our configurations. I just wanted to know what will happen if the RRO
encounters the same node/router ID(in different ASs) along its path.
Since the router-id is appearing for a second time in the path, that
node will not be added to the RRO presuming that a loop would be formed.
But in this case, it is not so. So what would be the behavior?

Thanks,
Hemanth.




-----Original Message-----
From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org]
On Behalf Of The IESG
Sent: Thursday, July 14, 2005 10:39 PM
To: IETF-Announce
Cc: mpls@ietf.org
Subject: [mpls] Last Call: 'Definition of an RRO node-id subobject' to
Proposed Standard 

The IESG has received a request from the Multiprotocol Label Switching
WG to 
consider the following document:

- 'Definition of an RRO node-id subobject '
   <draft-ietf-mpls-nodeid-subobject-06.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-07-28.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mpls-nodeid-subobject-06.
txt


_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls