Re: Reposting: question on GMPLS TE flooding with OSPF

[Yakov Rekhter <yakov@juniper.net>]

Anca,

> > > At 06:02 AM 8/21/2002 -0400, Anca Zamfir wrote:
> > > >Hi,
> > > >When a node floods TE link information using OSPF, it needs to fill in 
> > the
> > > >neighbor OSPF RouterID as Link ID in the Link TLV. For an optical TE 
> > link,
> > > >this node discovers (e.g. using LMP) the neighbor TE Node ID, 
> > therefore it
> > > >will need the mapping between the neighbor TE Node ID and the neighbor
> > > >RouterID in order to be able to fill in the required information.
> > > >Is a GMPLS node expected to flood the Router TLV only, before the 
> > first TE
> > > >Link is configured? If yes, I was not able to find this specified in
> > > >draft-katz-yeung-ospf-traffic-06.txt or
> > > >draft-ietf-ccamp-ospf-gmpls-extensions-07.txt
> > > >Or is there another mechanism in place to discover this mapping?
> > > >Same questions may be valid for IS-IS.
> >
> >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.

Yakov.