Subject: [mpls] Question regarding RFC 3209

From: Jim Ji <[email-masked]>
Date: Tue, 6 Mar 2018 08:29:02 +0000

Hi MPLS experts,
For RFC3209 section "4.7.4. Resource Affinity Procedures", it just points out that a link must confirming the affinity.
But it does not clearly define that RSVP should only validate the out-interface or both the in-interface and out-interface.
For an example:

R1-eth12------------------------eth21-R2-eth23-------------------eth32-R3

For this scenario, R1 is the ingress node of an rsvp session, R2 is a transmit node and R3 is the egress node.
eth12 connects eth21, eth23 connects eth32.

Question:

  1.  Eth12, eth23 meet the affinity, but eth21 and eth32 do not meet the affinity. Then these two links (eth12----eth21,  eth23----eth32) should be valid or not?

rsvp session can be up or not?

  1.  Eth12, eth21,eth23 and eth32 are all meet the affinity, then the rsvp session can be up. Right?

Thanks a lot!
Best Regards,
Jim