The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-May> msg00335



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

can egress know the ingress of a packet?

  • From: David Charlap <david.charlap@marconi.com>
  • Date: Tue, 30 May 2000 10:49:45 -0400

Rohit Chhapolia wrote:
> 
> To determine the ingress node, "Extended Tunnel ID" is useful.
> 
> From RSVP-TE draft,
> 
>     Extended Tunnel ID
> 
>        A 32-bit identifier used in the SESSION that  remains  constant
>        over  the  life  of  the  tunnel.   Normally  set to all zeros.
>        Ingress nodes that wish to narrow the scope of a SESSION to the
>        ingress-egress  pair  may  place  their  IPv4 address here as a
>        globally unique identifier.

I wouldn't use this for that purpose.  Note that the draft says "may",
not "must" or "shall".

This use of extended tunnel ID, while recommended and common, is not a
requirement.  In theory, any value may be used as long as it uniquely
identifies the sender withing the MPLS cloud.  This ID could be
something other than IP address.

-- David