RFC 6320 on Protocol for Access Node Control Mechanism in Broadband Networks

rfc-editor@rfc-editor.org Thu, 06 October 2011 00:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 151CA21F8DEB; Wed, 5 Oct 2011 17:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.157
X-Spam-Level:
X-Spam-Status: No, score=-102.157 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 3fxssQZ99EqR; Wed, 5 Oct 2011 17:15:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id A003021F8DEA; Wed, 5 Oct 2011 17:15:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DCC6798C277; Wed, 5 Oct 2011 17:18:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6320 on Protocol for Access Node Control Mechanism in Broadband Networks
From: rfc-editor@rfc-editor.org
Message-Id: <20111006001821.DCC6798C277@rfc-editor.org>
Date: Wed, 05 Oct 2011 17:18:21 -0700
Cc: ancp@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 06 Oct 2011 00:15:13 -0000

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

        
        RFC 6320

        Title:      Protocol for Access Node Control 
                    Mechanism in Broadband Networks 
        Author:     S. Wadhwa, J. Moisand,
                    T. Haag, N. Voigt,
                    T. Taylor, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2011
        Mailbox:    sanjay.wadhwa@alcatel-lucent.com, 
                    jmoisand@juniper.net, 
                    haagt@telekom.de,  norbert.voigt@nsn.com, 
                    tom111.taylor@bell.net
        Pages:      82
        Characters: 178446
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ancp-protocol-17.txt

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

This document describes the Access Node Control Protocol (ANCP).
ANCP operates between a Network Access Server (NAS) and an Access
Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)) in
a multi-service reference architecture in order to perform operations
related to Quality of Service, service, and subscribers.  Use cases
for ANCP are documented in RFC 5851.  As well as describing the base
ANCP protocol, this document specifies capabilities for Digital
Subscriber Line (DSL) topology discovery, line configuration, and
remote line connectivity testing.  The design of ANCP allows for
protocol extensions in other documents if they are needed to support
other use cases and other access technologies.

ANCP is based on the General Switch Management Protocol version 3
(GSMPv3) described in RFC 3292, but with many modifications and
extensions, to the point that the two protocols are not
interoperable.  For this reason, ANCP was assigned a separate version
number to distinguish it.  [STANDARDS-TRACK]

This document is a product of the Access Node Control Protocol 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