Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks
RFC 5851

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 13

Internet Engineering Task Force (IETF)                          S. Ooghe
Request for Comments: 5851                                Alcatel-Lucent
Category: Informational                                         N. Voigt
ISSN: 2070-1721                                   Nokia Siemens Networks
                                                              M. Platnic
                                                             ECI Telecom
                                                                 T. Haag
                                                        Deutsche Telekom
                                                               S. Wadhwa
                                                        Juniper Networks
                                                                May 2010

    Framework and Requirements for an Access Node Control Mechanism
                  in Broadband Multi-Service Networks

Abstract

   The purpose of this document is to define a framework for an Access
   Node Control Mechanism 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 service, quality of service, and
   subscribers.  The Access Node Control Mechanism will ensure that the
   transmission of the information does not need to go through distinct
   element managers but rather uses a direct device-device
   communication.  This allows for performing access-link-related
   operations within those network elements, while avoiding impact on
   the existing Operational Support Systems.

   This document first identifies a number of use cases for which the
   Access Node Control Mechanism may be appropriate.  It then presents
   the requirements for the Access Node Control Protocol (ANCP) that
   must be taken into account during protocol design.  Finally, it
   describes requirements for the network elements that need to support
   ANCP and the described use cases.  These requirements should be seen
   as guidelines rather than as absolute requirements.  RFC 2119
   therefore does not apply to the nodal requirements.

Ooghe, et al.                 Informational                     [Page 1]
RFC 5851                     ANCP Framework                     May 2010

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc5851.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Ooghe, et al.                 Informational                     [Page 2]
RFC 5851                     ANCP Framework                     May 2010

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Requirements Notation  . . . . . . . . . . . . . . . . . .  5
     1.2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  General Architecture Aspects . . . . . . . . . . . . . . . . .  7
     2.1.  Concept of an Access Node Control Mechanism  . . . . . . .  7