draft-ietf-ancp-protocol-08.txt   draft-ietf-ancp-protocol-09.txt 
Network Working Group S. Wadhwa Network Working Group S. Wadhwa
Internet-Draft J. Moisand Internet-Draft J. Moisand
Intended status: Standards Track S. Subramanian Intended status: Standards Track S. Subramanian
Expires: May 13, 2010 Juniper Networks Expires: August 30, 2010 Juniper Networks
T. Haag T. Haag
Deutsche Telekom Deutsche Telekom
N. Voigt N. Voigt
Siemens Siemens
R. Maglione R. Maglione
Telecom Italia Telecom Italia
November 9, 2009 February 26, 2010
Protocol for Access Node Control Mechanism in Broadband Networks Protocol for Access Node Control Mechanism in Broadband Networks
draft-ietf-ancp-protocol-08 draft-ietf-ancp-protocol-09
Abstract Abstract
This document describes proposed extensions to the GSMPv3 protocol to This document describes proposed extensions to the GSMPv3 protocol to
allow its use in a broadband environment, as a control plane between allow its use in a broadband environment, as a control plane between
Access Nodes (e.g. DSLAM) and Broadband Network Gateways (e.g. Access Nodes (e.g. DSLAM) and Broadband Network Gateways (e.g.
NAS). These proposed extensions are required to realize a protocol NAS). These proposed extensions are required to realize a protocol
for "Access Node Control" mechanism as described in [ANCP-FRAMEWORK]. for "Access Node Control" mechanism as described in [ANCP-FRAMEWORK].
The resulting protocol with the proposed extensions to GSMPv3 The resulting protocol with the proposed extensions to GSMPv3
[RFC3292] is referred to as "Access Node Control Protocol" (ANCP). [RFC3292] is referred to as "Access Node Control Protocol" (ANCP).
skipping to change at page 2, line 13 skipping to change at page 2, line 13
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 13, 2010. This Internet-Draft will expire on August 30, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the 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.
Table of Contents Table of Contents
1. Specification Requirements . . . . . . . . . . . . . . . . . . 4 1. Specification Requirements . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
3. Broadband Access Aggregation . . . . . . . . . . . . . . . . . 6 3. Broadband Access Aggregation . . . . . . . . . . . . . . . . . 6
3.1. ATM-based broadband aggregation . . . . . . . . . . . . . 6 3.1. ATM-based broadband aggregation . . . . . . . . . . . . . 6
3.2. Ethernet-based broadband aggregation . . . . . . . . . . . 7 3.2. Ethernet-based broadband aggregation . . . . . . . . . . . 7
4. Access Node Control Protocol . . . . . . . . . . . . . . . . . 7 4. Access Node Control Protocol . . . . . . . . . . . . . . . . . 7
4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 8
skipping to change at page 3, line 40 skipping to change at page 3, line 40
5.4.3. Line Configuration Extensions . . . . . . . . . . . . 37 5.4.3. Line Configuration Extensions . . . . . . . . . . . . 37
5.4.4. OAM Extensions . . . . . . . . . . . . . . . . . . . . 40 5.4.4. OAM Extensions . . . . . . . . . . . . . . . . . . . . 40
5.4.5. Additional GSMP Extensions for future use cases . . . 43 5.4.5. Additional GSMP Extensions for future use cases . . . 43
5.4.5.1. General well known TLVs . . . . . . . . . . . . . 44 5.4.5.1. General well known TLVs . . . . . . . . . . . . . 44
5.4.5.1.1. Target TLV . . . . . . . . . . . . . . . . . . 44 5.4.5.1.1. Target TLV . . . . . . . . . . . . . . . . . . 44
5.4.5.1.2. Command TLV . . . . . . . . . . . . . . . . . 45 5.4.5.1.2. Command TLV . . . . . . . . . . . . . . . . . 45
5.4.5.1.3. Status-info TLV . . . . . . . . . . . . . . . 47 5.4.5.1.3. Status-info TLV . . . . . . . . . . . . . . . 47
5.4.5.2. Generic Response Message . . . . . . . . . . . . . 48 5.4.5.2. Generic Response Message . . . . . . . . . . . . . 48
5.5. ATM-specific considerations . . . . . . . . . . . . . . . 50 5.5. ATM-specific considerations . . . . . . . . . . . . . . . 50
5.6. Ethernet-specific considerations . . . . . . . . . . . . . 50 5.6. Ethernet-specific considerations . . . . . . . . . . . . . 50
6. Appendix: Handling of pre-RFC deployments of the ANCP 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51
protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 7. Security Considerations . . . . . . . . . . . . . . . . . . . 56
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 56
8. Security Considerations . . . . . . . . . . . . . . . . . . . 56 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 57 9.1. Normative References . . . . . . . . . . . . . . . . . . . 56
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57 9.2. Informative References . . . . . . . . . . . . . . . . . . 56
10.1. Normative References . . . . . . . . . . . . . . . . . . . 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 57
10.2. Informative References . . . . . . . . . . . . . . . . . . 57
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 58
1. Specification Requirements 1. Specification Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
DSL is a widely deployed access technology for Broadband Access for DSL is a widely deployed access technology for Broadband Access for
skipping to change at page 51, line 27 skipping to change at page 51, line 27
discovery and line configuration messages, and then hve a mechanism discovery and line configuration messages, and then hve a mechanism
by which this can be correlated to the context of an "aggregation by which this can be correlated to the context of an "aggregation
network" facing IP interface (for the subscriber) on the NAS. This network" facing IP interface (for the subscriber) on the NAS. This
can either be based on local configuration on the NAS, or on the fact can either be based on local configuration on the NAS, or on the fact
that such DSLAM (access node) typically inserts the "Access Loop that such DSLAM (access node) typically inserts the "Access Loop
Circuit ID" in subscriber signaling messages relayed to the NAS (i.e. Circuit ID" in subscriber signaling messages relayed to the NAS (i.e.
DHCP or PPPoE discovery messages). DHCP or PPPoE discovery messages).
Section Section 5.4.1 defines "Access Loop Circuit ID". Section Section 5.4.1 defines "Access Loop Circuit ID".
6. Appendix: Handling of pre-RFC deployments of the ANCP protocol 6. IANA Considerations
This appendix is non normative.
Prior to completion of this document, several pre-RFC versions of the
protocol were documented and implemented. There were numerous pre-
standard versions of the protocol all using a version/sub-version
fields set to 3.1.
A NAS implementing the ANCP protocol as defined in this document may,
on a peer basis, use the version and sub-version fields to detect a
pre-RFC implementation of the protocol and choose to work with such
pre-RFC peers. The version and sub-version negotiation phase is part
of the adjacency protocol and is performed before synchronisation is
achieved.
7. IANA Considerations
This document defines the following additions to the GSMPv3 Message This document defines the following additions to the GSMPv3 Message
Type Name Space registry: Type Name Space registry:
+--------------+--------+---------------+ +--------------+--------+---------------+
| Message | Number | Source | | Message | Number | Source |
+--------------+--------+---------------+ +--------------+--------+---------------+
| Provisioning | 93 | This document | | Provisioning | 93 | This document |
+--------------+--------+---------------+ +--------------+--------+---------------+
skipping to change at page 52, line 32 skipping to change at page 52, line 12
Function Name Space registry [editor's note GMSPv3 did not define a Function Name Space registry [editor's note GMSPv3 did not define a
Name Space for Function even if RFC3292 defines values for function Name Space for Function even if RFC3292 defines values for function
field]: field]:
+----------------+-----------------+---------------+ +----------------+-----------------+---------------+
| Function Value | Function Name | Reference | | Function Value | Function Name | Reference |
+----------------+-----------------+---------------+ +----------------+-----------------+---------------+
| 0x09 | Remote loopback | This document | | 0x09 | Remote loopback | This document |
+----------------+-----------------+---------------+ +----------------+-----------------+---------------+
This document reserves the range 0x500 to 0x5ff of GSMPv3 Failure The GSMPv3 Failure Response Message Name Space is extended from the
Response Message Name Space registry to indicate the status of the GSMPv3 limit of 255 to a new upper limit of 4095 and this document
executed test for OAM use case described in Section 5.4.4. The adds the following values to the GSMPv3 Failure Response Message Name
initial entries are as follows: Space registry:
+-------------------------+----------------------------+------------+ +-------------------+-----------------------------------+-----------+
| Failure Response | Failure Response Message | Reference | | Failure Response | Failure Response Message Name | Reference |
| Message Value | Name | | | Message Value | | |
+-------------------------+----------------------------+------------+ +-------------------+-----------------------------------+-----------+
| 0x500 | Specified access line does | This | | 81d | Request message type not | This |
| | not exist | document | | | implemented (0x51) | document |
| 0x501 | Loopback test timed out | This | | 82d | Transaction identifier out of | This |
| | | document | | | sequence (0x52) | document |
| 0x502 | Reserved | This | | 83d | Malformed message (0x53) | This |
| | | document | | | | document |
| 0x503 | DSL line status showtime | This | | 84d | TLV or value not supported by | This |
| | | document | | | negotiated capability set (0x54) | document |
| 0x0504 | DSL line status idle | This | | 85d | Invalid value in TLV (0x55) | This |
| | | document | | | | document |
| 0x0505 | DSL line status silent | This | | From 256d to 499d | Reserved for IETF use (0x0100 - | This |
| | | document | | | 0x1F3) | document |
| 0x0506 | DSL line status training | This | | 1280d | Specified access line does not | This |
| | | document | | | exist (0x500) | document |
| 0x507 | DSL line integrity error | This | | 1281d | Loopback test timed out (0x501) | This |
| | | document | | | | document |
| 0x0508 | DSLAM resource not | This | | 1282d | Reserved (0x502) | This |
| | available | document | | | | document |
| 0x509 | Invalid test parameter | This | | 1283 | DSL line status showtime (0x503) | This |
| | | document | | | | document |
+-------------------------+----------------------------+------------+ | 1284 | DSL line status idle (0x504) | This |
| | | document |
| 1285 | DSL line status silent (0x505) | This |
| | | document |
| 1286 | DSL line status training (0x506) | This |
| | | document |
| 1287 | DSL line integrity error (0x507) | This |
| | | document |
| 1288 | DSLAM resource not available | This |
| | (0x508) | document |
| 1289 | Invalid test parameter (0x509) | This |
| | | document |
| From 509d to | Reserved for IETF use (0x1FD - | This |
| 4095d | 0XFFF) | document |
+-------------------+-----------------------------------+-----------+
This document reserves the values 256 to 499 and 509 to 4095 within
the GSMPv3 Failure Response Message Name Space registry for use by
extensions to the Access Node Control Protocol (ANCP).
This document defines a new ANCP Version Space registry. The initial This document defines a new ANCP Version Space registry. The initial
entry is as follows: entry is as follows:
+--------------------+-------------------+---------------+ +--------------------+-------------------+---------------+
| ANCP Version Value | ANCP Version Name | Reference | | ANCP Version Value | ANCP Version Name | Reference |
+--------------------+-------------------+---------------+ +--------------------+-------------------+---------------+
| 3 | ANCP Version | This document | | 3 | ANCP Version | This document |
+--------------------+-------------------+---------------+ +--------------------+-------------------+---------------+
skipping to change at page 53, line 48 skipping to change at page 53, line 48
+-----------------+----------------------------+---------------+ +-----------------+----------------------------+---------------+
| Tech Type Value | Tech Type Name | Reference | | Tech Type Value | Tech Type Name | Reference |
+-----------------+----------------------------+---------------+ +-----------------+----------------------------+---------------+
| 0x00 | Extension block not in use | This document | | 0x00 | Extension block not in use | This document |
| 0x01 | PON | This document | | 0x01 | PON | This document |
| 0x05 | DSL | This document | | 0x05 | DSL | This document |
| 0x06 - 0xFE | Reserved | This document | | 0x06 - 0xFE | Reserved | This document |
| 0xFF | Base Specification Use | This document | | 0xFF | Base Specification Use | This document |
+-----------------+----------------------------+---------------+ +-----------------+----------------------------+---------------+
This document reserves the range 0x500 to 0x5ff of GSMPv3 Failure
Response Message Name Space registry.
This document adds the following values to the GSMPv3 Failure
Response Message Name Space registry:
+--------------------------------------+----------------+-----------+
| Command Code Directive Name | Command Code | Reference |
| | Value | |
+--------------------------------------+----------------+-----------+
| Request message type not implemented | 0x81 | This |
| | | document |
| Transaction identifier out of | 0x82 | This |
| sequence | | document |
| Malformed message | 0x83 | This |
| | | document |
| TLV or value not supported by | 0x84 | This |
| negotiated capability set | | document |
| From 0x256 to 0x4095 | Reserved for | This |
| | IETF use | document |
+--------------------------------------+----------------+-----------+
This document reserves the values 0x100 to 0x1ff (256 to 511) within
the GSMPv3 Failure Response Message Name Space registry for use by
extensions to the Access Node Control Protocol (ANCP).
This document defines a new ANCP Command Code registry. The initial This document defines a new ANCP Command Code registry. The initial
entries are as follows: entries are as follows:
+-----------------------------+--------------------+---------------+ +-----------------------------+--------------------+---------------+
| Command Code Directive Name | Command Code Value | Reference | | Command Code Directive Name | Command Code Value | Reference |
+-----------------------------+--------------------+---------------+ +-----------------------------+--------------------+---------------+
| Reserved | 0x00 | This document | | Reserved | 0x00 | This document |
+-----------------------------+--------------------+---------------+ +-----------------------------+--------------------+---------------+
This document defines a new ANCP TLV Type registry. The initial This document defines a new ANCP TLV Type registry. The initial
skipping to change at page 56, line 45 skipping to change at page 56, line 8
| Actual-Interleaving-Delay-Downstream | 0x8E | This | | Actual-Interleaving-Delay-Downstream | 0x8E | This |
| | | document | | | | document |
| DSL line state | 0x8F | This | | DSL line state | 0x8F | This |
| | | document | | | | document |
| Access Loop Encapsulation | 0x90 | This | | Access Loop Encapsulation | 0x90 | This |
| | | document | | | | document |
| DSL-Type | 0x91 | This | | DSL-Type | 0x91 | This |
| | | document | | | | document |
+--------------------------------------------+--------+-------------+ +--------------------------------------------+--------+-------------+
8. Security Considerations 7. Security Considerations
Security of the ANCP protocol is discussed in [ANCP-SEC] Security of the ANCP protocol is discussed in [RFC5713]
9. Acknowledgements 8. Acknowledgements
The authors would like to thank everyone that has provided comments The authors would like to thank everyone that has provided comments
or inputs to this document. In particular, the authors acknowledge or inputs to this document. In particular, the authors acknowledge
the inputs provided by Wojciech Dec, Peter Arberg, Josef Froehler, the inputs provided by Wojciech Dec, Peter Arberg, Josef Froehler,
Derek Harkness, Kim Hyldgaard, Sandy Ng, Robert Peschi, Michel Derek Harkness, Kim Hyldgaard, Sandy Ng, Robert Peschi, Michel
Platnic and Tom Taylor. Platnic and Tom Taylor.
10. References 9. References
10.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3046] Patrick, M., "DHCP Relay Agent Information Option", [RFC3046] Patrick, M., "DHCP Relay Agent Information Option",
January 2001. RFC 3046, January 2001.
[RFC3292] Doria, A. and et all, "General Switch Management Protocol [RFC3292] Doria, A., Hellstrand, F., Sundell, K., and T. Worster,
(GSMP) V3", June 2002. "General Switch Management Protocol (GSMP) V3", RFC 3292,
June 2002.
[RFC3293] Worster, T., Doria, A., and and J. Buerkle, "General [RFC3293] Worster, T., Doria, A., and J. Buerkle, "General Switch
Switch Management Protocol (GSMP) Packet Encapsulations Management Protocol (GSMP) Packet Encapsulations for
for Asynchronous Transfer Mode (ATM), Ethernet and Asynchronous Transfer Mode (ATM), Ethernet and
Transmission Control Protocol (TCP)", June 2002. Transmission Control Protocol (TCP)", RFC 3293, June 2002.
10.2. Informative References 9.2. Informative References
[ANCP-FRAMEWORK] [ANCP-FRAMEWORK]
Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S. Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S.
Wadhwa, "Framework and Requirements for an Access Node Wadhwa, "Framework and Requirements for an Access Node
Control Mechanism in Broadband Multi-Service Networks", Control Mechanism in Broadband Multi-Service Networks",
draft-ietf-ancp-framework-12.txt, work in progress, draft-ietf-ancp-framework-13.txt, work in progress,
October 2009. February 2010.
[ANCP-SEC]
Moustafa, H., Tschofenig, T., and S. De Cnodder, "Security
Threats and Security Requirements for the Access Node
Control Protocol (ANCP)",
draft-ietf-ancp-security-threats-08.txt work in progress,
July 2009.
[G.988.1] "ITU-T recommendation G.998.1, ATM-based multi-pair [G.988.1] "ITU-T recommendation G.998.1, ATM-based multi-pair
bonding", 2005. bonding", 2005.
[G.988.2] "ITU-T recommendation G.998.2, Ethernet-based multi-pair [G.988.2] "ITU-T recommendation G.998.2, Ethernet-based multi-pair
bonding,", 2005. bonding,", 2005.
[RFC5713] Moustafa , H., Tschofenig, H., and S. De Cnodder,
"Security Threats and Security Requirements for the Access
Node Control Protocol (ANCP)", January 2010.
[TR-058] Elias, M. and S. Ooghe, "DSL Forum TR-058, Multi-Service [TR-058] Elias, M. and S. Ooghe, "DSL Forum TR-058, Multi-Service
Architecture & Framework Requirements", September 2003. Architecture & Framework Requirements", September 2003.
[TR-059] Anschutz, T., "DSL Forum TR-059, DSL Evolution - [TR-059] Anschutz, T., "DSL Forum TR-059, DSL Evolution -
Architecture Requirements for the Support of QoS-Enabled Architecture Requirements for the Support of QoS-Enabled
IP Services", September 2003. IP Services", September 2003.
[TR-092] "DSL Forum TR-092, Broadband Remote access server [TR-092] "DSL Forum TR-092, Broadband Remote access server
requirements document", 2005. requirements document", 2005.
 End of changes. 22 change blocks. 
108 lines changed or deleted 92 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/