clarence, stewart,

In favor of interoperable implementations i feel one should document how to 
identify the transport IP address (in lieu of protocols extensions who would
explicitly advertise the transport IP addresses) to the PQ node for the 
targeted LDP session.

I am proposing to append the following text to 3.2. "Tunnel requirements":

3.2.  Tunnel Requirements
   [ … ]

   When a failure is detected, it is necessary to immediately redirect
   traffic to the repair path.  Consequently, the repair tunnel used
   must be provisioned beforehand in anticipation of the failure.  Since
   the location of the repair tunnels is dynamically determined it is
   necessary to establish the repair tunnels without management action.
   Multiple repairs may share a tunnel end point.

<added-text>

Targeted LDP sessions are brought up using a pair of source (PLR) and 
destination
(PQ node) loopback addresses. The following heuristics should be applied for 
deriving the
loopback IP address from a PQ nodes link-state advertisement.

for the IS-IS routing protocol:

A PLR router should connect to the address

 traffic-engineering deployments:
  - reported both in the TE-router ID TLV 134
  - and IP Reach TLVs (128,135) given that
  - the prefix length is /32

    or

 no traffic-engineering deployments:
  - reported both in the IP interface address TLV 132
  - and IP Reach TLVs (128,135), given that
  - there is only a single interface address advertised per the router
  - the prefix length is /32


for the OSPF routing protocol:

A PLR router should connect to the address

 traffic-engineering deployments:
  - reported in the Router Address TLV  (Type 10 LSA) and
  - router (Type 1 LSA) ) stub network  advertisement and
  - the address mask is 255.255.255.255

    or

 non-traffic-engineering deployments:
  - reported in the  router-id field of the Type-1 LSA)
  - the router (Type 1 LSA) stub network  advertisement and
  - the address mask is 255.255.255.255

</added-text>

tx,

/hannes
_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg

Reply via email to