1 / 4

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

Usage of The RSVP Association Object draft-ietf-ccamp-assoc-info-02.txt. Lou Berger <lberger@labn.net >. Question from last IETF: One draft or two?. draft-ietf-ccamp-assoc-info-0 1 covered : Informational usage for GMPLS recovery

hope-walker
Download Presentation

Usage of The RSVP Association Object draft-ietf-ccamp-assoc-info-02.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-02.txt Lou Berger <lberger@labn.net> CCAMP - 81st IETF

  2. Question from last IETF: One draft or two? • draft-ietf-ccamp-assoc-info-01 covered: • Informational usage for GMPLS recovery • Standards track extensions for non-GMPLS recovery usage and Extended association • Discussed at IETF 80:Should Information and Standards track sections be separated? E.g.: • “Usage of The RSVP Association Object” • “RSVP Association Object Extensions ” Consensus to separate This presentation covers #1 CCAMP - 81st IETF

  3. draft-ietf-ccamp-assoc-info-02 Draft now only has one part: • 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 - 81st IETF

  4. Next steps • Draft stable • Only minor changes in March 2010 (on top of 2009 rev) • Ready to move forward / LC • Perhaps wait for LC until extensions draft ready? • Early reviews would be appreciated! CCAMP - 81st IETF

More Related