The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-Apr> msg00111



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

FW: I-D ACTION:draft-ietf-mpls-rsvp-tunnel-applicability-01.t xt

  • From: "Abes, Andi" <aabes@quarrytech.com>
  • Date: Fri, 14 Apr 2000 14:44:52 -0400
  • Cc: mpls@UU.NET





 Back to reality, draft-swallow-rsvp-bypass-label-00.txt
> provides an example
> of different ingress nodes using the same session objects
> including the
> extended tunnel id for association of backup LSPs with LSPs
> being backed up.
>
>


Dimitry,

I was looking for the refrence you gave, but the only
thing I found was an example discussing using different IP addresses
in the sender_template, not in the session.

(end of section 3.1)

   We therefore propose that backup tunnels be identified as follows.
   The SESSION object and the LSP_ID are copied from the LSP tunnel
   being backed up.  The IPv4 tunnel sender address is set to an address
   of the PLR node.  If the head-end of a tunnel is also acting as the
   PLR, it must choose an IP address different from the one used in the
   SENDER_TEMPLATE of the original LSP tunnel.


Did you mean something else ?


Andi.