[CCAMP] Document Action: 'Usage of The RSVP Association Object' to Informational RFC (draft-ietf-ccamp-assoc-info-03.txt)
The IESG <iesg-secretary@ietf.org> Tue, 29 May 2012 22:53 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3811621F86C6; Tue, 29 May 2012 15:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level:
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 87OD4OMOs7UH; Tue, 29 May 2012 15:53:11 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5354311E8170; Tue, 29 May 2012 15:53:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120529225311.30298.15051.idtracker@ietfa.amsl.com>
Date: Tue, 29 May 2012 15:53:11 -0700
Cc: ccamp mailing list <ccamp@ietf.org>, ccamp chair <ccamp-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [CCAMP] Document Action: 'Usage of The RSVP Association Object' to Informational RFC (draft-ietf-ccamp-assoc-info-03.txt)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2012 22:53:12 -0000
The IESG has approved the following document: - 'Usage of The RSVP Association Object' (draft-ietf-ccamp-assoc-info-03.txt) as Informational RFC This document is the product of the Common Control and Measurement Plane Working Group. The IESG contact persons are Adrian Farrel and Stewart Bryant. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-ccamp-assoc-info/ Technical Summary The RSVP ASSOCIATION object was defined in the context of GMPLS (Generalized Multi-Protocol Label Switching) controlled label switched paths (LSPs). In this context, the object is used to associate recovery LSPs with the LSP they are protecting. This document reviews how association is to be provided in the context of GMPLS recovery. No new procedures or mechanisms are defined by this document and it is strictly informative in nature. Working Group Summary Nothing in WG process worth noting. Document was a result of questions on proper interpretation of this object. Good support by the WG. Document Quality Not applicable for this Informational document. Personnel Deborah Brungard (db3546@att.com) is the Document Sphepherd. Adrian Farrel (adrian@olddog.co.uk) is the Responsible AD. RFC Editor Note Abstract s/RSVP/Resource Reservation Protocol (RSVP)/ Section 2.1 s/RSVP-TE/Resource Reservation Protocol - Traffic Engineering (RSVP-TE)/ Section 2.1 OLD It is explicitly defined as having both general application and specific use within the context of recovery. End-to- end recovery usage is defined in [RFC4872] and is covered in Section 2.2. Segment recovery usage is defined in [RFC4873] and is covered in Section 2.3. Resource sharing LSP association is also defined in [RFC4873], while strictly speaking such association is beyond the scope of this document, for completeness it is covered in Section 2.4. NEW It is explicitly defined as having both general application and specific use within the context of recovery. End-to- end recovery usage is defined in [RFC4872] and is covered in Section 2.2 of this document. Segment recovery usage is defined in [RFC4873] and is covered in Section 2.3 of this document. Resource sharing LSP association is also defined in [RFC4873], while strictly speaking such association is beyond the scope of this document, for completeness it is covered in Section 2.4 of this document END Section 2.1 s/independent from/independently of/ Section 2.2 OLD - The LSP ID of the LSP protecting an LSP. NEW - The LSP ID of the protection LSP. END