1 / 5

Usage of The RSVP Association Object draft-ietf-ccamp-assoc-info-00

Lou Berger <lberger@labn.net> Francois Le Faucheur <flefauch@cisco.com> Ashok Narayanan <ashokn@cisco.com>. Usage of The RSVP Association Object draft-ietf-ccamp-assoc-info-00. WG -00 Draft Background. Individual draft now WG document

meda
Télécharger la présentation

Usage of The RSVP Association Object draft-ietf-ccamp-assoc-info-00

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

  2. CCAMP - 79th IETF WG -00 Draft Background Individual draft now WG document As mentioned in last meeting and as discussed with AD Draft has two parts: Informational (Discussed at IETF 74-76) 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 (GMPLS Only) Reviews object definition Analyzes conformance (RFC2119) language of each Identifies valid Association ID use cases Describes receiver processing to handle cases

  3. CCAMP - 79th IETF Non-Recovery Associaton • Non-Recovery Usage (Per IETF 76, 77) • Standards Track • But don’t modify usage for Recovery • Provides informational guidance for Recovery • Non-Recovery Usage • Reuse recovery rules • Match LSPs with identical ASSOCIATION objects • Type, ID, & Source • Multiple associations are possible all association objects need to examined. • Applies to LSP and non-LSP forms of RSVP • 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

  4. CCAMP - 79th IETF Extended Association IDs Current draft: Adds extended Association Identifiers, withlarger fixed size extended ID field Planned Changes: Add global Association ID based on MPLS-TP identifiers Replace fixed sized extended ID with variable length form In increments of 32 bits Only association IDs of identical length can match

  5. CCAMP - 79th IETF Next Steps • Update document as discussed • Comments/Feedback?

More Related