The MPLS WG Archive

["chetan kumar s" <chetan.kumar@wipro.com>]

On Thu, 28 Mar 2002, Manikantan Srinivasan wrote:

> Hello Chetan,

Hi Manikantan,

	Please find my comments embedded..

>
> Good idea..
>
> Following are my comments/feedback.
>
> 1) The advantage of the "LSPID" is not clearly mentioned.
>
>     I understand the need of LSPID as follows. Please correct
>     me if I am wrong.
>     A tunnel interface, is treated as a point-to-point interface.
>     The Link TLV proposed in [OSPF-TE] provides support to
>     specify point-to-point interfaces. However if there are multiple
>     point-to-point links (They can be virtual tunnels/circuits etc.,)
>     originating on the same physical interface and ending on
>     the same physical interface between two routers, the source
>     IP address, destination IP address will not help distinguish
>     the different links. In this case a link id, or LSPID is helpful.

You are right. In a case where there are multipule tunnels originate on
the same physical i/f, it is not scalable to have ip numbers associated
with each tunnels. So tunnels can be signalled as LSP's and LSPID can be
signalled via OSPF-TE. If is this is not clear, I will update the draft.


>
>     If am I am right, can it be added? or the actual intent.
>
> 2) How the LSPID helps in automated CSPF calculation is
>     not clearly highlighted. (I think automated CSPF for
>     TE Paths is the final intent).

Excatly, final intent is automation of CSPF calculation. When one
calculates the path from a central node (as against distributed method),
calculated path would be optimal. One needs to provide full information to
the central node. How the central node use this information is left to
(CSPF) implementation.

>
> 3) Sections 4, 5 are missing.

oops, the section numbering is incorrect, not that section 4 and 5
missing. I will update this..

>
> with best regards
> mani
> /*-------------------------------------*/
> S.Manikantan
> Future Communications Software,
> 4300, Stevens Creek Blvd,
> Suite 187, San Jose,
> CA 95129
> Tel : (408) 243-3887 Extn 107
> Fax: (408) 243-0772
> email: manis@futsoft.com
> /*-------------------------------------*/
>
>
>
>
>
> -----Original Message-----
> From:	chetan kumar s [SMTP:chetan.kumar@wipro.com]
> Sent:	Thursday, March 28, 2002 5:56 AM
> To:	mpls@uu.net
> Subject:	new draft
>
> Hi,
> 	I a new draft is avilable in TE WG. I solicit your comments on
> this and like to know the list views on this..
>
> Thanks
> Chetan S
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : Signalling LSPID's in OSPF TE
>         Author(s)       : K. Chetan, K. Sunil
>         Filename        : draft-chetan-lspid-ospf-00.txt
>         Pages           : 5
>         Date            : 21-Mar-02
>
> This draft introduces new a sub TLV to OSPF TE extensions to signal
> the LSPID (Label Switch Path ID) of an LSP (Label Switch Path).
> This information can be used by any mechanism (normally constraint
> based path calculation (CSPF) procedures) to calculate paths that
> may contain LSPID's as one its Explict Route Objects.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-chetan-lspid-ospf-00.txt
>