[CCAMP] RFC 6780 on RSVP ASSOCIATION Object Extensions

rfc-editor@rfc-editor.org Sat, 27 October 2012 02:06 UTC

Return-Path: <wwwrun@rfc-editor.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 120E221F84D9; Fri, 26 Oct 2012 19:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.018
X-Spam-Level:
X-Spam-Status: No, score=-102.018 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nma12nx+AUSV; Fri, 26 Oct 2012 19:06:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 5480D21F84CA; Fri, 26 Oct 2012 19:06:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CE3B5B1E002; Fri, 26 Oct 2012 19:00:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121027020009.CE3B5B1E002@rfc-editor.org>
Date: Fri, 26 Oct 2012 19:00:09 -0700
Cc: ccamp@ietf.org, rfc-editor@rfc-editor.org
Subject: [CCAMP] RFC 6780 on RSVP ASSOCIATION Object Extensions
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: Sat, 27 Oct 2012 02:06:07 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6780

        Title:      RSVP ASSOCIATION Object Extensions 
        Author:     L. Berger,  
                    F. Le Faucheur,
                    A. Narayanan
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2012
        Mailbox:    lberger@labn.net, 
                    flefauch@cisco.com, 
                    ashokn@cisco.com
        Pages:      17
        Characters: 41252
        Updates:    RFC2205, RFC3209, RFC3473, RFC4872

        I-D Tag:    draft-ietf-ccamp-assoc-ext-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6780.txt

The RSVP ASSOCIATION object was defined in the context of GMPLS-controlled
Label Switched Paths (LSPs).  In this context, the object is used to
associate recovery LSPs with the LSP they are protecting.  This
object also has broader applicability as a mechanism to associate
RSVP state.  This document defines how the ASSOCIATION object
can be more generally applied.  This document also defines
Extended ASSOCIATION objects that, in particular, can be used in
the context of the MPLS Transport Profile (MPLS-TP).  This document 
updates RFC 2205, RFC 3209, and RFC 3473.  It also generalizes the 
definition of the Association ID field defined in RFC 4872.
[STANDARDS-TRACK]


This document is a product of the Common Control and Measurement Plane Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC