Subject: RE: [Isis-wg] doubts.

From: Satish Dattatri <[email-masked]>
Date: Mon, 1 Jul 2002 16:30:34 -0700

o Traffic engg needs information about links and the best way is to
put that info along with the IS neighbors. There are 2 interface
address(es) our own put in the IPV4 Address sub-tlv and the 
IPV4 Neighbor Address sub-tlv contains the neigh's.

o In order to compute route(s) we need the IP reachability information.
Remember this draft is talking about new TLVs as replacement for the 
Old advertisement of IS Neighbor TLV, IP Internal Reachability Option
and IP External Reachability Option. Both the Old and the New options
may co-exist until the transition is completed.

Hope that helps,
satish

> -----Original Message-----
> From: ramanathan rams [mailto:[email-masked]]
> Sent: Monday, July 01, 2002 4:03 PM
> To: [email-masked]'
> Cc: [email-masked]'
> Subject: [Isis-wg] doubts.
> 
> 
> hi all,
> 
>       could u please explain me the following doubts?
> 
> In the ISIS extensions for TE draft,
> 
> *  IPV4 Address sub TLV gives the IPv4 Address of the 
> interface described 
> by the main TLV.
>    Main TLV is IS extended reachability TLV. And IS extended 
> reachability 
> describes about the link to the neighbour.  So the IPv4 
> Address of the 
> interface described is the IPv4 Address of the neighbour. is 
> this right?
> if so, what does the IPv4 neighbour address sub TLV describe?
> 
> *  we have IP reachability TLV also.  Could u please explain 
> me the reason 
> why all the TE properties sub TLVs are added to IS 
> reachability TLV rather 
> than IP reachability TLV?.
> 
> thanks
> rams.
> 
> 
> 
> _______________________________________________
> Isis-wg mailing list  -  [email-masked]
> http://spider.juniper.net/mailman/listinfo/isis-wg
> 
_______________________________________________
Isis-wg mailing list  -  [email-masked]
http://spider.juniper.net/mailman/listinfo/isis-wg