1 / 7

Usage of The RSVP Association Object draft-berger-ccamp-assoc-info-01

Usage of The RSVP Association Object draft-berger-ccamp-assoc-info-01. Lou Berger <lberger@labn.net> Francois Le Faucheur <flefauch@cisco.com> Ashok Narayanan <ashokn@cisco.com>. Genesis of work. Recovery LSP association -- How does it work? Question raised by Nic Neate

jenna-burt
Download Presentation

Usage of The RSVP Association Object draft-berger-ccamp-assoc-info-01

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. Usage of The RSVP Association Objectdraft-berger-ccamp-assoc-info-01 Lou Berger <lberger@labn.net> Francois Le Faucheur <flefauch@cisco.com> Ashok Narayanan <ashokn@cisco.com> CCAMP - 77th IETF

  2. Genesis of work • Recovery LSP association -- How does it work? • Question raised by Nic Neate • Discussed in IETFs 72 & 73 and e-mail • At IETF 74: WG agreed to publish individual informational draft so that perceived issue can be closed. • At IETF 75&76: this draft presented • What does the association object look like?for: • End to end recovery (A-B-C-D-E, A-F-G-H-E) • Segment recovery (B-G-D) A B C D E F G H CCAMP - 77th IETF

  3. -00 Draft • Informational • No new procedures or formats • Is essentially formal write of Adrian’s E-mail on the topic • Subject: Re: Clearing up your misunderstanding of the Association ID • From: "Adrian Farrel" <adrian at olddog.co.uk> • Date: Tue, 18 Nov 2008 22:34:14 -0000 • http://www.ietf.org/mail-archive/web/ccamp/current/msg00644.html • Covers ASSOCIATION Object as defined in RFC 4872 and RFC 4873 • Reviews object definition • Analyzes conformance (RFC2119) language of each • Identifies valid Association ID use cases • Describes receiver processing to handle cases CCAMP - 77th IETF

  4. But… • There was related work happening in the context of RSVP • draft-narayanan-tsvwg-rsvp-resource-sharing • At IETF 76: Requested to expand association usage • For more general usage MPLS, GMPLS, non-LSP • Support Resv / downstream based association CCAMP - 77th IETF

  5. -01 Changes • Standards Track • But don’t modify usage for Recovery • Provides informational guidance from -00 document • Adds Non-Recovery Usage • Resuse recovery rules • Match LSPs with identical ASSOCIATION objects • Type, ID, & Source • Multiple associations are possible all association objects need to examined. • Allow for association based on Path or Resv messages • Upstream Initiated Association (Path state matching) • Downstream Initiated Association (Resv state matching) • No cross-direction association CCAMP - 77th IETF

  6. -01 Changes (cont.) • Add extended Association Identifiers • For IPv4 and IPv6 • 2 new C-Types • Association ID field • Original: 16 bits • Extended: 48 bits CCAMP - 77th IETF

  7. Next Steps • Comments? Three changes: • Allow for non-GMPLS usage • Allow for Downstream Initiated Association (Resv) • Expanded ID C-types • Proposed next steps • WG Document? CCAMP - 77th IETF

More Related