1 / 6

Usage of The RSVP Association Object draft-ietf-ccamp-assoc-info-01.txt

Usage of The RSVP Association Object draft-ietf-ccamp-assoc-info-01.txt. Lou Berger <lberger@labn.net> Francois Le Faucheur <flefauch@cisco.com> Ashok Narayanan < ashokn@cisco.com>. Three Part Draft. Draft has three parts: Informational (Discussed at IETF 74-76)

Download Presentation

Usage of The RSVP Association Object draft-ietf-ccamp-assoc-info-01.txt

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-ietf-ccamp-assoc-info-01.txt Lou Berger <lberger@labn.net> Francois Le Faucheur <flefauch@cisco.com> Ashok Narayanan <ashokn@cisco.com> CCAMP - 80th IETF

  2. Three Part Draft Draft has three 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 No Change CCAMP - 80th IETF

  3. Part 2: Non-Recovery Association • 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 • All fields: 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 No Change CCAMP - 80th IETF

  4. Part 3: Extended Association • IPv4 and IPv6 Extended ASSOCIATION Objects • Revised per plan discussed at IETF 79 • Supports • Association identifiers > 16 bits • MPLS TP identifiers – ICC and Global ID • Format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | Class-Num(199)| C-Type (TBA) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Association Type | Association ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | IPv4 Association Source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Global Association Source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : . : : Extended Association ID : : . : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Per RFC 4872 Global ID: <0> | <2|4-byte ASN> 4 bytes >= 0 bytes, 32-bit aligned [<ICC> <0x00>] [<data>] CCAMP - 80th IETF

  5. Question: One draft or two? • Current draft covers: • Informational usage for GMPLS recovery • Standards track extensions for non-GMPLS recovery usage and Extended association • Should Information and Standards track sections be separated? E.g.: • “Usage of The RSVP Association Object” • “RSVP Association Object Extensions ” CCAMP - 80th IETF

  6. Next steps • Updated based on today’s discussion • Solicit additional feedback on extended association CCAMP - 80th IETF

More Related