RFC 6123 on Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group Drafts

rfc-editor@rfc-editor.org Thu, 03 February 2011 04:01 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 3AF893A67EC; Wed, 2 Feb 2011 20:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.308
X-Spam-Status: No, score=-102.308 tagged_above=-999 required=5 tests=[AWL=0.292, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7BS1kBh+t8Nl; Wed, 2 Feb 2011 20:01:29 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 4C86B3A67A1; Wed, 2 Feb 2011 20:01:25 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E02F4E0753; Wed, 2 Feb 2011 20:04:46 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6123 on Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group Drafts
From: rfc-editor@rfc-editor.org
Message-Id: <20110203040446.E02F4E0753@rfc-editor.org>
Date: Wed, 02 Feb 2011 20:04:46 -0800
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 04:01:30 -0000

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

        RFC 6123

        Title:      Inclusion of Manageability Sections in 
                    Path Computation Element (PCE) Working Group 
        Author:     A. Farrel
        Status:     Historic
        Stream:     IETF
        Date:       February 2011
        Mailbox:    adrian@olddog.co.uk
        Pages:      13
        Characters: 28277
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-manageability-requirements-11.txt

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

It has often been the case that manageability considerations have
been retrofitted to protocols after they have been specified,
standardized, implemented, or deployed.  This is sub-optimal.
Similarly, new protocols or protocol extensions are frequently
designed without due consideration of manageability requirements.

The Operations Area has developed "Guidelines for Considering
Operations and Management of New Protocols and Protocol Extensions"
(RFC 5706), and those guidelines have been adopted by the Path Computation
Element (PCE) Working Group.

Previously, the PCE Working Group used the recommendations contained
in this document to guide authors of Internet-Drafts on the contents
of "Manageability Considerations" sections in their work.  This
document is retained for historic reference.  This document 
defines a Historic Document for the Internet community.

This document is a product of the Path Computation Element Working Group of the IETF.

HISTORIC: This memo defines a Historic Document for the Internet
community.  It does not specify an Internet standard of any kind.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

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