draft-ietf-ancp-protocol-04.txt   draft-ietf-ancp-protocol-05.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 7, 2009 Juniper Networks Expires: September 10, 2009 Juniper Networks
T. Haag T. Haag
T-systems T-systems
N. Voigt N. Voigt
Siemens Siemens
R. Maglione R. Maglione
Telecom Italia Telecom Italia
November 3, 2008 March 9, 2009
Protocol for Access Node Control Mechanism in Broadband Networks Protocol for Access Node Control Mechanism in Broadband Networks
draft-ietf-ancp-protocol-04 draft-ietf-ancp-protocol-05
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 7, 2009. This Internet-Draft will expire on September 10, 2009.
Copyright Notice
Copyright (c) 2009 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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
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).
This document currently focuses on specific use cases of access node This document currently focuses on specific use cases of access node
control mechanism for topology discovery, line configuration, and OAM control mechanism for topology discovery, line configuration, and OAM
as described in ANCP framework document [ANCP-FRAMEWORK]. It is as described in ANCP framework document [ANCP-FRAMEWORK]. It is
intended to be augmented by additional protocol specification for intended to be augmented by additional protocol specification for
future use cases considered in scope by the ANCP charter. future use cases considered in scope by the ANCP charter.
ANCP framework document [ANCP-FRAMEWORK] describes the ANCP use-cases ANCP framework document [ANCP-FRAMEWORK] describes the ANCP use-cases
in detail. Illustrative text for the use-cases is included here to in detail. Illustrative text for the use-cases is included here to
skipping to change at page 3, line 41 skipping to change at page 3, line 41
5.4.1. General Extensions . . . . . . . . . . . . . . . . . . 24 5.4.1. General Extensions . . . . . . . . . . . . . . . . . . 24
5.4.2. Topology Discovery Extensions . . . . . . . . . . . . 25 5.4.2. Topology Discovery Extensions . . . . . . . . . . . . 25
5.4.3. Line Configuration Extensions . . . . . . . . . . . . 35 5.4.3. Line Configuration Extensions . . . . . . . . . . . . 35
5.4.4. OAM Extensions . . . . . . . . . . . . . . . . . . . . 38 5.4.4. OAM Extensions . . . . . . . . . . . . . . . . . . . . 38
5.4.5. Multicast Extensions . . . . . . . . . . . . . . . . . 41 5.4.5. Multicast Extensions . . . . . . . . . . . . . . . . . 41
5.4.5.1. General well known TLVs . . . . . . . . . . . . . 42 5.4.5.1. General well known TLVs . . . . . . . . . . . . . 42
5.4.5.1.1. Target TLV . . . . . . . . . . . . . . . . . . 42 5.4.5.1.1. Target TLV . . . . . . . . . . . . . . . . . . 42
5.4.5.1.2. Command TLV . . . . . . . . . . . . . . . . . 43 5.4.5.1.2. Command TLV . . . . . . . . . . . . . . . . . 43
5.4.5.1.3. Status-Info TLV . . . . . . . . . . . . . . . 44 5.4.5.1.3. Status-Info TLV . . . . . . . . . . . . . . . 44
5.4.5.2. Multicast Replication Control Message . . . . . . 45 5.4.5.2. Multicast Replication Control Message . . . . . . 45
5.4.5.3. Multicast Status Message . . . . . . . . . . . . . 52 5.4.5.3. Multicast Status Message . . . . . . . . . . . . . 51
5.5. ATM-specific considerations . . . . . . . . . . . . . . . 53 5.5. ATM-specific considerations . . . . . . . . . . . . . . . 53
5.6. Ethernet-specific considerations . . . . . . . . . . . . . 54 5.6. Ethernet-specific considerations . . . . . . . . . . . . . 54
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54
7. Security Considerations . . . . . . . . . . . . . . . . . . . 55 7. Security Considerations . . . . . . . . . . . . . . . . . . . 59
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 55 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 60
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 55 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 60
9.1. Normative References . . . . . . . . . . . . . . . . . . . 55 9.1. Normative References . . . . . . . . . . . . . . . . . . . 60
9.2. Informative References . . . . . . . . . . . . . . . . . . 55 9.2. Informative References . . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 56 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 61
Intellectual Property and Copyright Statements . . . . . . . . . . 59
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 25, line 20 skipping to change at page 25, line 20
extension block is used. extension block is used.
Tech Type Tech Type
An 8-bit field indicating the applicable technology type value. An 8-bit field indicating the applicable technology type value.
The Message Type plus the Tech Value uniquely define a single The Message Type plus the Tech Value uniquely define a single
Extension Type and can be treated as a single 16 bit extension Extension Type and can be treated as a single 16 bit extension
type. "Tech Type" value of 0x05 SHOULD be used by ANCP for DSL type. "Tech Type" value of 0x05 SHOULD be used by ANCP for DSL
technology. technology.
0x00 Extension block not it use. 0x00 Extension block not in use.
0x01 - 0x04 Already in use by various technologies 0x01 - 0x04 Already in use by various technologies
0x05 DSL 0x05 DSL
0x06 - 0xFE Reserved 0x06 - 0xFE Reserved
0xFF Base Specification Use 0xFF Base Specification Use
Block Length Block Length
skipping to change at page 42, line 40 skipping to change at page 42, line 40
reflected in the message length field. reflected in the message length field.
5.4.5.1. General well known TLVs 5.4.5.1. General well known TLVs
This section contains the definitions of three general well known This section contains the definitions of three general well known
TLVs. These TLVs are intended to be re-usable across different TLVs. These TLVs are intended to be re-usable across different
Multicast messages. Multicast messages.
5.4.5.1.1. Target TLV 5.4.5.1.1. Target TLV
The Target TLV (TBD) is intended to be a general well known TLV The Target TLV (0x10) is intended to be a general well known TLV
allowing the representation of different types of objects. Its use allowing the representation of different types of objects. Its use
is not restricted to any specific Message Type. is not restricted to any specific Message Type.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = Target | Target-TLV Length | | TLV Type = Target | Target-TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Target Info ~ ~ Target Info ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Target TLV: Target TLV:
TLV (0xTBD) indicating the type of target being addressed. TLV (0x10) indicating the type of target being addressed.
Numbers TBC. Tentative 0x1000 for single Access-Port. Numbers TBC. Tentative 0x1000 for single Access-Port.
Target TLV Length: Target TLV Length:
Length in bytes of Target Info. Excludes TLV header Length in bytes of Target Info. Excludes TLV header
Target Info: Target Info:
Target information as defined for each the given target. Target information as defined for each the given target.
The field can consist of sub-TLVs. The field can consist of sub-TLVs.
In its simplest form, when targeting a single access line the Target- In its simplest form, when targeting a single access line the Target-
TLV will be set to a value of (0xTBD), and carry in its payload one TLV will be set to a value of (0x10), and carry in its payload one or
or more sub-TLVs identifying the target. The following example more sub-TLVs identifying the target. The following example
illustrates the message format for a single port identified by an illustrates the message format for a single port identified by an
Access-Loop-Circuit-ID TLV (0x0001) that could be derived from a Access-Loop-Circuit-ID TLV (0x0001) that could be derived from a
Port-UP message: Port-UP message:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = Target | Target-TLV Length | | TLV Type = Target | Target-TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID=0x0001 | Circuit-ID Length | | Access-Loop-Circuit-ID=0x0001 | Circuit-ID Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Access Loop Circuit ID ~ ~ Access Loop Circuit ID ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5.4.5.1.2. Command TLV 5.4.5.1.2. Command TLV
The Command TLV (TBD) is intended to be a general well known TLV The Command TLV (0x11) is intended to be a general well known TLV
allowing the encapsulation of one or more command directives in a TLV allowing the encapsulation of one or more command directives in a TLV
oriented message. The semantics of the command are allowed to be oriented message. The semantics of the command are allowed to be
specified for each message type, ie different message types that specified for each message type, ie different message types that
choose to carry the Command TLV are expected to define the meaning of choose to carry the Command TLV are expected to define the meaning of
the content of the payload, which could be re-used from those already the content of the payload, which could be re-used from those already
defined elsewhere if appropriate. defined elsewhere if appropriate.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = Command | Command-TLV Length | | TLV Type = Command | Command-TLV Length |
skipping to change at page 44, line 22 skipping to change at page 44, line 22
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional sub-TLV Type | Additional sub-TLV Length | | Additional sub-TLV Type | Additional sub-TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Additional sub-TLV data ~ ~ Additional sub-TLV data ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Command TLV: Command TLV:
TLV (0xTBD) indicating the contents to be one or more TLV (0x11) indicating the contents to be one or more
command directives. command directives.
Command TLV Length: Command TLV Length:
Combined length in bytes of the data in Command Info and Combined length in bytes of the data in Command Info and
sub-TLV. Excludes the Command TLV header sub-TLV. Excludes the Command TLV header
Commad-Info: Commad-Info:
Command information as defined for each message type. The Command information as defined for each message type. The
skipping to change at page 44, line 49 skipping to change at page 44, line 49
Additional sub-TLV Length: Additional sub-TLV Length:
Number of actual bytes contained in the value portion of Number of actual bytes contained in the value portion of
each additional sub-TLV each additional sub-TLV
5.4.5.1.3. Status-Info TLV 5.4.5.1.3. Status-Info TLV
The Status-info-TLV is intended to be a general well known TLV used The Status-info-TLV is intended to be a general well known TLV used
to convey the status code regarding commands and/or requests. The to convey the status code regarding commands and/or requests. The
format of the Status-Info-TLV (TBD) is shown below. format of the Status-Info-TLV (0x012) is shown below.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = Status-info | Status TLV Length | | TLV Type = Status-info | Status TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result Code | Cmnd Nmbr | Error Message Length | | Result Code | Cmnd Nmbr | Error Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Message (aligned to 4 bytes length) | | Error Message (aligned to 4 bytes length) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-TLVs... | | sub-TLVs... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Status-info TLV: Status-info TLV:
TLV (0xTBD) conveying the status or error response of a TLV (0x12) conveying the status or error response of a
command command
Status TLV Length: Status TLV Length:
Specifies the length in bytes of the Status Info TLV Specifies the length in bytes of the Status Info TLV
payload. Excludes the TLV header payload. Excludes the TLV header
Result Code: Result Code:
Conveys the result code for the command or message, as Conveys the result code for the command or message, as
skipping to change at page 45, line 52 skipping to change at page 45, line 52
TLVs: TLVs:
This field is of indeterminate length, and contains zero or This field is of indeterminate length, and contains zero or
more of the TLVs associated with the Status-info-TLV. more of the TLVs associated with the Status-info-TLV.
5.4.5.2. Multicast Replication Control Message 5.4.5.2. Multicast Replication Control Message
The Multicast Replication Control Message Type 0x90 (TBC) is sent by The Multicast Replication Control Message Type 0x90 (TBC) is sent by
the NAS to the AN with a directive to either add (join) or delete the NAS to the AN with a directive to either add (join) or delete
(leave) one or more multicast flows on a target object identified in (leave) one or more multicast flows on a target object identified in
the content of the message. An AN will use a Multicast Status the content of the message. When a response is needed an AN MUST use
message when conveying the outcome of the directive, and this message the Multicast Status message to convey the outcome of the directive;
type is covered in Section 5.4.5.3. this message type is covered in Section 5.4.5.3.
The sender of a Multicast Replication Control message MUST set the The sender of a Multicast Replication Control message MUST set the
Result field to either "AckAll" or "NAck", and SHOULD use "NAck" by Result field to 0x00 meaning "Ignore". The sender MUST populate the
default. Furthermore it SHOULD use the same Result field code for ANCP Transaction Identifier field with a distinct non-zero, linearly
all Multicast Replication Control Messages sent, i.e. Result field
changes SHOULD be avoided. The sender MUST populate the ANCP
Transaction Identifier field with a distinct non-zero, linearly
incrementing value for each Request per adjacency, as described in incrementing value for each Request per adjacency, as described in
Section 5.4.5 . Section 5.4.5 .
The ANCP Multicast Replication Control message payload contains the The ANCP Multicast Replication Control message payload contains the
following TLVs: following TLVs:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Target TLV | Length of Target-Info | | Type = Target TLV | Length of Target-Info |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 46, line 36 skipping to change at page 46, line 33
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Command TLV | Length of Command Info | | Type = Command TLV | Length of Command Info |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Value = Command Info ~ ~ Value = Command Info ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Target: Target:
See Section 5.4.5.1.1. The Target TLV (0xTBD) can only feature See Section 5.4.5.1.1. The Target TLV (0x10) can only feature
once in a Multicast Replication Control Message. Only one such once in a Multicast Replication Control Message. Only one such
TLV is allowed in this message type. TLV is allowed in this message type.
Length of Target-Info: Length of Target-Info:
See Section 5.4.5.1.1 See Section 5.4.5.1.1
Target Info: Target Info:
See Section 5.4.5.1.1 See Section 5.4.5.1.1
Command TLV: Command TLV:
The Command TLV (0xTBD) contains the multicast flow The Command TLV (0x11) contains the multicast flow
directive(s) for the target and any additional parameters directive(s) for the target and any additional parameters
passed via sub-TLVs. See Section 5.4.5.1.2 passed via sub-TLVs. See Section 5.4.5.1.2
Length of Command Info: Length of Command Info:
Includes sub-TLVs. See Section 5.4.5.1.2 Includes sub-TLVs. See Section 5.4.5.1.2
Command Info: Command Info:
Command information as defined in section Command information as defined in section
skipping to change at page 52, line 19 skipping to change at page 52, line 7
and its command directives. A Multicast Status message MUST use the and its command directives. A Multicast Status message MUST use the
same ANCP Transaction ID as that in the original Multicast same ANCP Transaction ID as that in the original Multicast
Replication Control Message. The Success or Failure status is Replication Control Message. The Success or Failure status is
reported in the Result field of the ANCP header as described in reported in the Result field of the ANCP header as described in
Section 5.4.5. Section 5.4.5.
A Multicast Status Message indicating Success SHOULD simply consist A Multicast Status Message indicating Success SHOULD simply consist
only of the base ANCP header with no body, however the message MAY only of the base ANCP header with no body, however the message MAY
contain one or more TLVs that are meant to communicate any relevant contain one or more TLVs that are meant to communicate any relevant
information to an application. The payload of a Multicast Status information to an application. The payload of a Multicast Status
Message indicating Failure MUST contain an Status-Info TLV (0xTBD), Message indicating Failure MUST contain an Status-Info TLV (0x12), as
as defined in Section 5.4.5.1.3, as its first TLV and SHOULD be defined in Section 5.4.5.1.3, as its first TLV and SHOULD be followed
followed by the Target TLV and Port-info. Other TLVs MAY be present. by the Target TLV and Port-info. Other TLVs MAY be present. A
A Multicast Status message indicating Failure MUST be sent whenever a Multicast Status message indicating Failure MUST be sent whenever a
Multicast Control message cannot be fulfilled or results in an Multicast Control message cannot be fulfilled or results in an
execution error. The Cmnd Nmbr parameter in the Status-Info TLV execution error. The Cmnd Nmbr parameter in the Status-Info TLV
contained by the Multicast Status Message is to indicate the number contained by the Multicast Status Message is to indicate the number
of the command in the Multicast Replication Control Message that of the command in the Multicast Replication Control Message that
resulted in an error. resulted in an error.
0x00 - Success 0x00 - Success
0x01 - Malformed message 0x01 - Malformed message
skipping to change at page 53, line 31 skipping to change at page 53, line 22
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x88-0C) | Length | | Type (0x88-0C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub |MessageType=91 | 0x4 | Code | | Vers | Sub |MessageType=91 | 0x4 | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier = 0001 | | Partition ID | Transaction Identifier = 0001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length | |I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status-info-TLV=TBD | Status-TLV-Length | | Status-info-TLV=0x12 | Status-TLV-Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result Code | Cmd Number | Error Message Length | | Result Code | Cmd Number | Error Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Message (padded to 4) if Length > 0 | | Error Message (padded to 4) if Length > 0 |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
| Target TLV=0x100 | Target-Length | | Target TLV=0x10 | Target-Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop ID type | Access-Loop ID Length | | Access Loop ID type | Access-Loop ID Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| circuit ID | | circuit ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5.5. ATM-specific considerations 5.5. ATM-specific considerations
The topology discovery and line configuration involve the DSL line The topology discovery and line configuration involve the DSL line
attributes. For ATM based access networks, the DSL line on the DSLAM attributes. For ATM based access networks, the DSL line on the DSLAM
skipping to change at page 55, line 7 skipping to change at page 54, line 42
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. IANA Considerations 6. IANA Considerations
New Tech-Type, capability types, TLVs, sub-TLV types related to This document defines the following additions to the GSMPv3 Message
topology discovery, line configuration and Multicast will need to be Type Name Space registry:
reserved.
+-------------------------------+--------+---------------+
| Message | Number | Reference |
+-------------------------------+--------+---------------+
| Multicast Replication Control | 90 | This document |
| Multicast Status | 91 | This document |
+-------------------------------+--------+---------------+
This document defines the following modification to the Global Switch
Management Protocol version 3 (GSMPv3) Result Type Name Space
registry:
+--------------+------------------------+---------------+
| Result Value | Result Type Name | Reference |
+--------------+------------------------+---------------+
| 0 | Ignore (from Reserved) | This document |
+--------------+------------------------+---------------+
This document defines the following addition to the GSMPv3 Message
Function Name Space registry [editor's note GMSPv3 did not define a
Name Space for Function even if RFC3292 defines values for function
field]:
+----------------+-----------------+---------------+
| Function Value | Function Name | Reference |
+----------------+-----------------+---------------+
| 0x09 | Remote loopback | This document |
+----------------+-----------------+---------------+
This document reserves the range 0x500 to 0x5ff of GSMPv3 Failure
Response Message Name Space registry to indicate the status of the
executed test for OAM use case described in Section 5.4.4. The
initial entries are as follows:
+-------------------------+----------------------------+------------+
| Failure Response | Failure Response Message | Reference |
| Message Value | Name | |
+-------------------------+----------------------------+------------+
| 0x500 | Specified access line does | This |
| | not exist | document |
| 0x501 | Loopback test timed out | This |
| | | document |
| 0x502 | Reserved | This |
| | | document |
| 0x503 | DSL line status showtime | This |
| | | document |
| 0x0504 | DSL line status idle | This |
| | | document |
| 0x0505 | DSL line status silent | This |
| | | document |
| 0x0506 | DSL line status training | This |
| | | document |
| 0x507 | DSL line integrity error | This |
| | | document |
| 0x0508 | DSLAM resource not | This |
| | available | document |
| 0x509 | Invalid test parameter | This |
| | | document |
+-------------------------+----------------------------+------------+
This document defines a new ANCP Tech Type Name Space registry. The
initial entries are as follows:
+----------------+-----------------------------------+--------------+
| Tech Type | Tech Type Name | Reference |
| Value | | |
+----------------+-----------------------------------+--------------+
| 0x00 | Extension block not in use | This |
| | | document |
| 0x01 - 0x04 | Already in use by various | This |
| | technologies | document |
| 0x05 | DSL | This |
| | | document |
| 0x06 - 0xFE | Reserved | This |
| | | document |
| 0xFF | Base Specification Use | This |
| | | document |
+----------------+-----------------------------------+--------------+
This document defines a new ANCP Status-Info Result Code registry.
The initial entries are as follows:
+-----------------------------------------------+-------+-----------+
| Result Code | Value | Reference |
+-----------------------------------------------+-------+-----------+
| Success | 0x00 | This |
| | | document |
| Malformed message | 0x01 | This |
| | | document |
| Command not supported | 0x02 | This |
| | | document |
| Flag set but not supported | 0x03 | This |
| | | document |
| Unrecognized Target | 0x04 | This |
| | | document |
| Unsupported Address Family | 0x05 | This |
| | | document |
| Malformed flow address | 0x06 | This |
| | | document |
| No resources | 0x07 | This |
| | | document |
| Unknown Target | 0x08 | This |
| | | document |
| Target down | 0x09 | This |
| | | document |
| Configuration error (such as Port not enabled | 0x0a | This |
| for multicast) | | document |
| Multicast flow does not exist | 0x0b | This |
| | | document |
| Unsupported address encoding | 0x0c | This |
| | | document |
| Additional info needed to execute command | 0x0d | This |
| (payload MAY contain an indication of the | | document |
| expected info) | | |
| Multicast flow count exceeded | 0x0e | This |
| | | document |
| M Flag set, but no IP Source address provided | 0x0f | This |
| | | document |
| Transaction-id out of sequence | 0x010 | This |
| | | document |
+-----------------------------------------------+-------+-----------+
This document defines a new ANCP Command Code registry. The initial
entries are as follows:
+-----------------------------+--------------------+---------------+
| Command Code Directive Name | Command Code Value | Reference |
+-----------------------------+--------------------+---------------+
| Reserved | 0x00 | This document |
| Add | 0x01 | This document |
| Delete | 0x02 | This document |
| Delete All | 0x03 | This document |
+-----------------------------+--------------------+---------------+
This document defines a new ANCP TLV Type registry. The initial
entries are as follows:
+--------------------------------------+-----------+---------------+
| TLV Name | Type Code | Reference |
+--------------------------------------+-----------+---------------+
| Access-Loop-Circuit-ID | 0x01 | This document |
| Access-Loop-Remote-Id | 0x02 | This document |
| Access-Aggregation-Circuit-ID-ASCII | 0x03 | This document |
| DSL Line Attributes | 0x04 | This document |
| Service-Profile-Name | 0x05 | This document |
| Access-Aggregation-Circuit-ID-Binary | 0x06 | This document |
| OAM-Loopback-Test-Parameters | 0x07 | This document |
| Opaque-Data | 0x08 | This document |
| OAM-Loopback-Test-Response-String | 0x09 | This document |
| Reserved | 0x0a-0x0f | This document |
| Target | 0x10 | This document |
| Command | 0x11 | This document |
| Status-Info | 0x012 | This document |
+--------------------------------------+-----------+---------------+
This document defines a new ANCP Capability registry. The initial
entries are as follows:
+----------------------------+----------------------+---------------+
| Capability Type Name | Capability Type Code | Reference |
+----------------------------+----------------------+---------------+
| Dynamic-Topology-Discovery | 0x01 | This document |
| Line-Configuration | 0x02 | This document |
| Transactional-Multicast | 0x03 | This document |
| OAM | 0x04 | This document |
+----------------------------+----------------------+---------------+
This document defines a new ANCP sub-TLV Type registry. The initial
entries are as follows:
+--------------------------------------------+--------+-------------+
| sub-TLV Name | Type | Reference |
| | Code | |
+--------------------------------------------+--------+-------------+
| Actual-Net-Data-Upstream | 0x81 | This |
| | | document |
| Actual-Net-Data-Rate-Downstream | 0x82 | This |
| | | document |
| Minimum-Net-Data-Rate-Upstream | 0x83 | This |
| | | document |
| Minimum-Net-Data-Rate-Downstream | 0x84 | This |
| | | document |
| Attainable-Net-Data-Rate-Upstream | 0x85 | This |
| | | document |
| Attainable-Net-Data-Rate-Downstream | 0x86 | This |
| | | document |
| Maximum-Net-Data-Rate-Upstream | 0x87 | This |
| | | document |
| Maximum-Net-Data-Rate-Downstream | 0x88 | This |
| | | document |
| Minimum-Net-Low-Power-Data-Rate-Upstream | 0x89 | This |
| | | document |
| Minimum-Net-Low-Power-Data-Rate-Downstream | 0x8A | This |
| | | document |
| Maximum-Interleaving-Delay-Upstream | 0x8B | This |
| | | document |
| Actual-Interleaving-Delay-Upstream | 0x8C | This |
| | | document |
| Maximum-Interleaving-Delay-Downstream | 0x8D | This |
| | | document |
| Actual-Interleaving-Delay-Downstream | 0x8E | This |
| | | document |
| DSL line state | 0x8F | This |
| | | document |
| Access Loop Encapsulation | 0x90 | This |
| | | document |
| DSL-Type | 0x91 | This |
| | | document |
+--------------------------------------------+--------+-------------+
7. Security Considerations 7. Security Considerations
Security of the ANCP protocol is discussed in [ANCP-SEC] Security of the ANCP protocol is discussed in [ANCP-SEC]
8. 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 Peter Arberg, Josef Froehler, Derek Harkness, the inputs provided by Peter Arberg, Josef Froehler, Derek Harkness,
Kim Hyldgaard, Sandy Ng, Robert Peschi, Michel Platnic and the work Kim Hyldgaard, Sandy Ng, Robert Peschi, Michel Platnic, Tom Taylor
done by Philippe Champagne, Wojciech Dec and Stefaan De Cnodder and the work done by Philippe Champagne, Wojciech Dec and Stefaan De
regarding multicast extensions. Cnodder regarding multicast extensions.
9. References 9. References
9.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. January 2001.
skipping to change at page 55, line 48 skipping to change at page 60, line 38
Switch Management Protocol (GSMP) Packet Encapsulations Switch Management Protocol (GSMP) Packet Encapsulations
for Asynchronous Transfer Mode (ATM), Ethernet and for Asynchronous Transfer Mode (ATM), Ethernet and
Transmission Control Protocol (TCP)", June 2002. Transmission Control Protocol (TCP)", June 2002.
9.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-06.txt, , May 2008. draft-ietf-ancp-framework-08.txt, , February 2009.
[ANCP-SEC] [ANCP-SEC]
Moustafa, H., Tschofenig, T., and S. De Cnodder, "Security Moustafa, H., Tschofenig, T., and S. De Cnodder, "Security
Threats and Security Requirements for the Access Node Threats and Security Requirements for the Access Node
Control Protocol (ANCP)", Control Protocol (ANCP)",
draft-ietf-ancp-security-threats-06.txt work in progress, draft-ietf-ancp-security-threats-07.txt work in progress,
October 2008. March 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.
[IANAAEA] "http://www.iana.org/assignments/address-family-numbers", [IANAAEA] "http://www.iana.org/assignments/address-family-numbers",
2005. 2005.
[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.
skipping to change at page 58, line 4 skipping to change at page 62, line 27
Phone: Phone:
Fax: Fax:
Email: thomas.haag@t-systems.com Email: thomas.haag@t-systems.com
Norber Voigt Norber Voigt
Siemens Siemens
Phone: Phone:
Fax: Fax:
Email: norbert.voigt@siemens.com Email: norbert.voigt@siemens.com
Roberta Maglione Roberta Maglione
Telecom Italia Telecom Italia
via Reiss Romoli 274 via Reiss Romoli 274
Torino Torino
Italy Italy
Phone: Phone:
Email: roberta.maglione@telecomitalia.it Email: roberta.maglione@telecomitalia.it
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 30 change blocks. 
53 lines changed or deleted 265 lines changed or added

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