1 / 6

Zafar Ali, Reshad Rahman and Danny Prairie

Node ID based RSVP Hello: A Clarification Statement draft-ali-ccamp-rsvp-node-id-based-hello-00.txt. Zafar Ali, Reshad Rahman and Danny Prairie zali@cisco.com , rrahman@cisco.com , dprairie@cisco.com. HELLO REQUEST (Source Address: A.B.C.D. Destination Address: E.F.G.H).

penda
Télécharger la présentation

Zafar Ali, Reshad Rahman and Danny Prairie

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Node ID based RSVP Hello: A Clarification Statementdraft-ali-ccamp-rsvp-node-id-based-hello-00.txt Zafar Ali, Reshad Rahman and Danny Prairie zali@cisco.com, rrahman@cisco.com, dprairie@cisco.com

  2. HELLO REQUEST (Source Address: A.B.C.D. Destination Address: E.F.G.H) What’s a Node-id based Hello? • A Hello session such that local and remote node-ids are used in the source and destination fields of the Hello packet, respectively. • Node-ID is “Router-id” as defined in the Router Address TLV for OSPF and Traffic Engineering router ID TLV for ISIS. It usually refers to a loopback address. Node-id = E.F.G.H Node-id = A.B.C.D ... HELLO ACK (Source Address: E.F.G.H Destination Address: A.B.C.D)

  3. RSVP Hellos over Optical Links • Data and control plan are separated. Node-id = A.B.C.D Node-id = E.F.G.H 10.1.2.1 10.1.2.11 10.1.2.2 Router OXC 10.1.2.12 ... 10.1.2.9 10.1.2.19 Control Channel Node-id based Hello Session

  4. Optimization Aspect • When link level failure detection is performed by some means other than RSVP Hellos, the use of node-id based Hellos is also optimal for detection of RSVP-TE signaling adjacency failure. • We RSVP Hellos are used for GR applications only. Node-id = A.B.C.D Node-id = E.F.G.H 10.1.2.1 10.1.3.1 10.1.2.2 10.1.3.2 ... 10.1.3.255 10.1.2.255 One node-id based Hello

  5. Use of node-id based RSVP Hello messages is implied in many cases, e.g., When data and control plan are separated. When TE links are unnumbered. When RSVP Hellos are used for GR procedure. When link level failure detection is performed by some means other than RSVP Hellos, e.g., BFD, use of node-id based Hellos is optimal for RSVP-TE signaling adjacency failure. Inter-AS links. The draft clarifies use of node-id based RSVP Hellos. The ID is informational and backward compatible. Summary:ID is Really a Clarification Statement 

  6. Next Steps • Given that, • We had various off-line discussions with many key contributors, including service providers. • All the SP/ contributors we spoke with are interested in this ID. • We agreed to include comments on the mailing list in the next revision. • We would like the WG to adopt this ID as a WG document.

More Related