[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reposting: question on GMPLS TE flooding with OSPF



Jonathan,

> Yakov Rekhter (and others) wrote:
> > >Perhaps adding something like the following to the LMP spec
> > > >would address your question:
> > > >
> > > >     Node ID: a single, stable IP address that identifies a node.  For
> > > >        a node running OSPF, the LMP Node ID is the same as the OSPF
> > > >        Router ID.  For a node running IS-IS and advertising the TE
> > > >        Router ID TLV, the Node ID is the same as the advertised Router
> > > >        ID.
> > > >
> > > >Yakov.
> > >
> > > I wrongly assumed that, for OSPF, the LMP Node ID is the IP address also
> > > specified in the Router Address TLV.
> > > Yes, this will definitely clarify things and IMO will avoid any
> > > interoperability issues. Would it be possible to have this added in the
> > > next draft version?
> > 
> > The editor of the LMP draft promised to add this text to the next version
> > of the draft.
> 
> Unfortunately, OSPF Router IDs are a separate number space from the IP
> addresses number space.  Only convention has made the two the same. 
> Therefore it is unsafe to expect a Router ID to be a routable IP
> address.  The text proposed above should be changed to reflect this...

Here is the modified version:

     Node ID: For a node running OSPF, the LMP Node ID is the same as the OSPF
        Router ID.  For a node running IS-IS and advertising the TE
        Router ID TLV, the Node ID is the same as the advertised Router ID.

Yakov.
  
> Jonathan Sadler
> ============================================================
> The information contained in this message may be privileged 
> and confidential and protected from disclosure.  If the 
> reader of this message is not the intended recipient, or an 
> employee or agent responsible for delivering this message to 
> the intended recipient, you are hereby notified that any 
> reproduction, dissemination or distribution of this 
> communication is strictly prohibited. If you have received 
> this communication in error, please notify us immediately by 
> replying to the message and deleting it from your computer.
> 
> Thank you.
> Tellabs
> ============================================================
>