The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Jun> msg00097



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

RSVP-TE: How to use "Tunnel Sender Address"?

  • From: Yuan Gu <yuangu@ipinfusion.com>
  • Date: Mon, 17 Jun 2002 11:21:47 -0700
  • CC: mpls@UU.NET
  • Organization: IP Infusion Inc

Bin Zhou wrote:

> Hi, Yuan
>
> You ask a good question.
> I think Tunnel ID is local in the daemon of the sender. We can use Tunnel ID
> and Sender address to distinguish a tunnel. If I need to identify
> application in my case, I need host address. The host address should be
> informed to destination and intermediate node in my case. So what should I
> do?
>
> BTW, I like the maillist very much :)
>
> Bin

Bin:

But there is only one RSVP application in each node. Puting your host address
into "extended tunnel id" is allowed(but not mandatory! Other boxes receive it
may only consider it as an identifier of a tunnel rather than a host address.).

I can't figure out what's your exact problem from a few words above. But I feel
it's rather an implementation issue than protocol itself.

Regards!
Yuan

>
>
> > Bin:
> >
> > Are you trying to send FEC information to intermediate/egress node? FEC is
> only
> > known by ingress node when packets need to be classified for LSPs. In
> > intermediate and egress node, the only way to identify the LSP tunnel in
> data
> > plane is LABEL.
> >
> > Regards!
> > Yuan