draft-ietf-ancp-mc-extensions-04.txt   draft-ietf-ancp-mc-extensions-05.txt 
ANCP F. Le Faucheur ANCP F. Le Faucheur
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track R. Maglione Intended status: Standards Track R. Maglione
Expires: August 13, 2011 Telecom Italia Expires: December 19, 2011 Telecom Italia
T. Taylor T. Taylor
Huawei Huawei
February 9, 2011 June 17, 2011
Multicast Control Extensions for ANCP Multicast Control Extensions for ANCP
draft-ietf-ancp-mc-extensions-04.txt draft-ietf-ancp-mc-extensions-05.txt
Abstract Abstract
This document specifies the extensions to the Access Node Control This document specifies the extensions to the Access Node Control
Protocol required for support of the multicast use cases defined in Protocol required for support of the multicast use cases defined in
the Access Node Control Protocol framework document and one the Access Node Control Protocol framework document and one
additional use case described in this document. These use cases are additional use case described in this document. These use cases are
organized into the following ANCP capabilities: organized into the following ANCP capabilities:
o NAS-initiated multicast replication; o NAS-initiated multicast replication;
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on August 13, 2011. This Internet-Draft will expire on December 19, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 4, line 48 skipping to change at page 4, line 48
6.3.1. Combination of Conditional Access With White and 6.3.1. Combination of Conditional Access With White and
Black Lists and Conditional Access With Grey Lists . . 62 Black Lists and Conditional Access With Grey Lists . . 62
6.3.2. Combination of Conditional Access With Delegated 6.3.2. Combination of Conditional Access With Delegated
Bandwidth . . . . . . . . . . . . . . . . . . . . . . 63 Bandwidth . . . . . . . . . . . . . . . . . . . . . . 63
6.3.3. Combination of NAS-Initiated Replication with 6.3.3. Combination of NAS-Initiated Replication with
Other Capabilities . . . . . . . . . . . . . . . . . . 63 Other Capabilities . . . . . . . . . . . . . . . . . . 63
6.3.4. Combinations of Committed Bandwidth Reporting with 6.3.4. Combinations of Committed Bandwidth Reporting with
Other Multicast Capabilities . . . . . . . . . . . . . 64 Other Multicast Capabilities . . . . . . . . . . . . . 64
7. Security Considerations . . . . . . . . . . . . . . . . . . . 65 7. Security Considerations . . . . . . . . . . . . . . . . . . . 65
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 69 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 70
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 71
10.1. Normative References . . . . . . . . . . . . . . . . . . . 70 10.1. Normative References . . . . . . . . . . . . . . . . . . . 71
10.2. Informative References . . . . . . . . . . . . . . . . . . 70 10.2. Informative References . . . . . . . . . . . . . . . . . . 71
Appendix A. Example of Messages and Message Flows . . . . . . . . 72 Appendix A. Example of Messages and Message Flows . . . . . . . . 73
A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . . 72 A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . . 73
A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 78 A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 79
A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 83 A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 84
A.4. Handling Of Black-Listed Join Requests . . . . . . . . . . 88 A.4. Handling Of Black-Listed Join Requests . . . . . . . . . . 89
A.5. Handling Of Requests To Join and Leave the On-Line Game . 88 A.5. Handling Of Requests To Join and Leave the On-Line Game . 89
A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 91 A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 92
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 96
1. Introduction 1. Introduction
[RFC5851] defines a framework and requirements for an Access Node [RFC5851] defines a framework and requirements for an Access Node
control mechanism between a Network Access Server (NAS) and an Access control mechanism between a Network Access Server (NAS) and an Access
Node (e.g. a Digital Subscriber Line Access Multiplexer (DSLAM)) in a Node (e.g. a Digital Subscriber Line Access Multiplexer (DSLAM)) in a
multi-service reference architecture in order to perform QoS-related, multi-service reference architecture in order to perform QoS-related,
service-related and subscriber-related operations. service-related and subscriber-related operations.
[I-D.ietf-ancp-protocol] specifies a protocol for Access Node Control [I-D.ietf-ancp-protocol] specifies a protocol for Access Node Control
in broadband networks in line with this framework. in broadband networks in line with this framework.
skipping to change at page 15, line 13 skipping to change at page 15, line 13
Figure 4: Message Flow For Committed Bandwidth Reporting Figure 4: Message Flow For Committed Bandwidth Reporting
4. ANCP Messages 4. ANCP Messages
This section defines new ANCP messages and new usage of existing ANCP This section defines new ANCP messages and new usage of existing ANCP
messages as well as procedures associated with the use of these messages as well as procedures associated with the use of these
messages. messages.
4.1. Provisioning Message 4.1. Provisioning Message
Section 6.1.2 of [I-D.ietf-ancp-protocol] defines the Provisioning Section 4.1 of [I-D.ietf-ancp-protocol] defines the Provisioning
message that is sent by the NAS to the AN to provision information in message that is sent by the NAS to the AN to provision information in
the AN. the AN.
The present document specifies that the Provisioning message MAY be The present document specifies that the Provisioning message MAY be
used by the NAS to provision multicast-related information (e.g. used by the NAS to provision multicast-related information (e.g.
multicast service profiles). The ANCP Provisioning message payload multicast service profiles). The ANCP Provisioning message payload
MAY contain: MAY contain:
o one or more instances of the Multicast-Service-Profile TLV. The o one or more instances of the Multicast-Service-Profile TLV. The
Multicast- Service-Profile TLV is defined in the present document Multicast- Service-Profile TLV is defined in the present document
skipping to change at page 16, line 10 skipping to change at page 16, line 10
4.1.1. Sender Behaviour 4.1.1. Sender Behaviour
When directed by the Policy Server or by management action, the NAS When directed by the Policy Server or by management action, the NAS
sends the Provisioning message to initially provision or to update sends the Provisioning message to initially provision or to update
the White, Black, and/or Grey multicast channel lists associated with the White, Black, and/or Grey multicast channel lists associated with
a set of named multicast service profiles, or to enable the AN to a set of named multicast service profiles, or to enable the AN to
perform admission control for specific classes of flows. perform admission control for specific classes of flows.
To provision or update a multicast service profile, the NAS MUST To provision or update a multicast service profile, the NAS MUST
include within the message one or more instances of the Multicast- include within the message one or more instances of the Multicast-
Service- Profile TLV specifying the content to be provisioned or Service-Profile TLV specifying the content to be provisioned or
updated. The NAS SHOULD NOT include any list type (White, Black, or updated. The NAS SHOULD NOT include any list type (White, Black, or
Grey) that is not supported by the set of multicast capabilities Grey) that is not supported by the set of multicast capabilities
negotiated between the NAS and the AN. The NAS MUST NOT use the negotiated between the NAS and the AN. The NAS MUST NOT use the
Provisioning message to send instances of the Multicast- Service- Provisioning message to send instances of the Multicast-Service-
Profile TLV to the AN unless the Multicast-Service-Profile TLV is Profile TLV to the AN unless the Multicast-Service-Profile TLV is
supported by the set of multicast capabilities negotiated between the supported by the set of multicast capabilities negotiated between the
NAS and the AN. NAS and the AN.
To require admission control to be performed at the AN on White- To require admission control to be performed at the AN on White-
listed flows, the NAS MUST include a copy of the White-List-CAC TLV listed flows, the NAS MUST include a copy of the White-List-CAC TLV
in the Provisioning message. The White-List-CAC TLV MUST NOT be in the Provisioning message. The White-List-CAC TLV MUST NOT be
provided unless the negotiated set of capabilities includes provided unless the negotiated set of capabilities includes
conditional access with White and Black lists. conditional access with White and Black lists.
skipping to change at page 17, line 43 skipping to change at page 17, line 43
[I-D.ietf-ancp-protocol], containing a Status-Info TLV with the [I-D.ietf-ancp-protocol], containing a Status-Info TLV with the
appropriate content describing the error. For this purpose, the appropriate content describing the error. For this purpose, the
presence of a list type in a Multicast-Service-Profile TLV which was presence of a list type in a Multicast-Service-Profile TLV which was
ignored because it was not supported by the negotiated set of ignored because it was not supported by the negotiated set of
capabilities is not considered to be an error. capabilities is not considered to be an error.
4.2. Port Management Message 4.2. Port Management Message
As specified in [I-D.ietf-ancp-protocol], the NAS may send DSL line As specified in [I-D.ietf-ancp-protocol], the NAS may send DSL line
configuration information to the AN ("ANCP based DSL Line configuration information to the AN ("ANCP based DSL Line
Configuration" use case) using GSMP Port Management messages modified Configuration" use case) using ANCP Port Management messages. See
to contain additional information. See Section 5.3.3 of Section 7.3 of [I-D.ietf-ancp-protocol] for the format of the Port
[I-D.ietf-ancp-protocol] for details. Management message in that usage.
This document specifies that the Port Management message MAY also This document specifies that the Port Management message MAY be used
include either or both of the following TLVs: to convey either or both of the following TLVs:
o Multicast-Service-Profile-Name TLV (defined in Section 5.2). This o Multicast-Service-Profile-Name TLV (defined in Section 5.2). This
TLV associates a Multicast Service Profile with the Access Port TLV associates a Multicast Service Profile with the Access Port
specified by the extension block. specified by the extension block.
o Bandwidth-Allocation TLV (defined in Section 5.5). This TLV o Bandwidth-Allocation TLV (defined in Section 5.5). This TLV
specifies the total multicast bandwidth available to the AN for specifies the total multicast bandwidth available to the AN for
admission control at the Access Port. admission control at the Access Port.
When used for this purpose, the Port Management message MUST include
TLV(s) to identify the access line concerned. If the access line is
a DSL loop, the line-identifying TLV(s) MUST be as specified in
Section 5.1.2 of [I-D.ietf-ancp-protocol]. For non-DSL access lines,
the appropriate alternative line-identifying TLV(s) MUST be present.
Line configuration data other than the two TLVs listed in the
previous paragraph MAY be present.
4.2.1. Sender Behaviour 4.2.1. Sender Behaviour
The NAS sends the Port Management message at startup time to The NAS sends the Port Management message at startup time to
initialize parameters associated with the Access Port specified in initialize parameters associated with the Access Port specified in
the message and with the multicast capabilities negotiated between the message and with the multicast capabilities negotiated between
the NAS and the AN. The NAS MAY send additional Port Management the NAS and the AN. The NAS MAY send additional Port Management
messages subsequent to startup, to update or, in the case of the messages subsequent to startup, to update or, in the case of the
Bandwidth-Allocation TLV, reset these parameters. If the NAS Bandwidth-Allocation TLV, reset these parameters. If the NAS
includes a Multicast-Service-Profile-Name TLV in the Port Management includes a Multicast-Service-Profile-Name TLV in the Port Management
message, the name MUST match a profile name provided in a Multicast- message, the name MUST match a profile name provided in a Multicast-
Service- Profile TLV in a prior Provisioning message. The NAS MUST Service-Profile TLV in a prior Provisioning message. The NAS MUST
NOT include a TLV unless it is supported by the set of multicast NOT include a TLV unless it is supported by the set of multicast
capabilities negotiated between the NAS and the AN. See Section 6 capabilities negotiated between the NAS and the AN. See Section 6
for further information. for further information.
4.2.2. Receiver Behaviour 4.2.2. Receiver Behaviour
If the Port Management message contains a Multicast-Service-Profile- If the Port Management message contains a Multicast-Service-Profile-
Name TLV, the AN associates the named profile with the specified Name TLV, the AN associates the named profile with the specified
Access Port. This association replaces any previous association. Access Port. This association replaces any previous association.
That is, a given Access Port is associated with at most one multicast That is, a given Access Port is associated with at most one multicast
skipping to change at page 18, line 48 skipping to change at page 19, line 7
Allocation TLV, the AN SHOULD NOT discontinue any multicast streams Allocation TLV, the AN SHOULD NOT discontinue any multicast streams
in order to bring bandwidth down to within the new limit. However, in order to bring bandwidth down to within the new limit. However,
the AN MUST NOT admit new multicast streams that are subject to the AN MUST NOT admit new multicast streams that are subject to
admission control until it can do so within the limit specified by admission control until it can do so within the limit specified by
the Bandwidth-Allocation TLV. the Bandwidth-Allocation TLV.
If the Port Management request cannot be processed due to error and If the Port Management request cannot be processed due to error and
the Result field of the request is Nack (0x1) or AckAll (0x2), the AN the Result field of the request is Nack (0x1) or AckAll (0x2), the AN
SHOULD add a Status-Info TLV to the Extension Value field in its SHOULD add a Status-Info TLV to the Extension Value field in its
reply if this will provide useful information beyond what is provided reply if this will provide useful information beyond what is provided
by the Code value returned in the response header. In particular, if by the Result Code value returned in the response header. In
the name within the Multicast-Service-Profile-Name TLV does not match particular, if the name within the Multicast-Service-Profile-Name TLV
a profile name given in a prior Provisioning message, the AN SHOULD does not match a profile name given in a prior Provisioning message,
return a reply where the Code field in the header indicates "Invalid the AN SHOULD return a reply where the Result Code field in the
TLV value" (85), the Error Message field in the Status-Info TLV header indicates "Invalid TLV value" (85), the Error Message field in
contains the text "Multicast profile name not provisioned", and the the Status-Info TLV contains the text "Multicast profile name not
Status-Info TLV contains a copy of the Multicast-Service-Profile-Name provisioned", and the Status-Info TLV contains a copy of the
TLV. Multicast-Service-Profile-Name TLV.
4.3. Multicast Replication Control Message 4.3. Multicast Replication Control Message
This section defines a new message called the Multicast Replication This section defines a new message called the Multicast Replication
Control message. The Multicast Replication Control message is sent Control message. The Multicast Replication Control message is sent
by the NAS to the AN with one or more directives to add (join) or by the NAS to the AN with one or more directives to add (join) or
delete (leave) a multicast flow on a target object identified in the delete (leave) a multicast flow on a target object identified in the
content of the message. content of the message.
The Message Type for the Multicast Replication Control message is The Message Type for the Multicast Replication Control message is
144. 144.
The ANCP Multicast Replication Control message payload contains the The ANCP Multicast Replication Control message payload contains the
following TLVs: following TLVs:
o Target TLV: The Target TLV is defined in [I-D.ietf-ancp-protocol]. o Target TLV: The Target TLV is defined in Section 4.3 of
It MUST appear once and only once. It is encoded as specified in [I-D.ietf-ancp-protocol]. It MUST appear once and only once. It
[I-D.ietf-ancp-protocol] or extensions and identifies the AN port is encoded as specified in [I-D.ietf-ancp-protocol] or extensions
subject to the request for admission or release. and identifies the AN port subject to the request for admission or
release.
o Command TLV: The Command TLV is defined in o Command TLV: The Command TLV is defined in Section 4.4 of
[I-D.ietf-ancp-protocol]. It MUST be present. It MAY appear [I-D.ietf-ancp-protocol]. It MUST be present. It MAY appear
multiple times. multiple times.
As [I-D.ietf-ancp-protocol] indicates, the contents of the Command As [I-D.ietf-ancp-protocol] indicates, the contents of the Command
Info field within the Command TLV are specific to the message in Info field within the Command TLV are specific to the message in
which the TLV occurs. For the Multicast Replication Control Message, which the TLV occurs. For the Multicast Replication Control Message,
these contents consist of: these contents consist of:
o a Command Code field; o a Command Code field;
skipping to change at page 22, line 10 skipping to change at page 22, line 10
The figure below is an example of a Multicast Replication Control The figure below is an example of a Multicast Replication Control
message that would result in a swap from multicast SSM flows message that would result in a swap from multicast SSM flows
192.0.2.1, 233.252.0.2, to 192.0.2.2, 233.252.0.3 on the Target 192.0.2.1, 233.252.0.2, to 192.0.2.2, 233.252.0.3 on the Target
identified by the "Access Loop Circuit ID": identified by the "Access Loop Circuit ID":
1 2 3 1 2 3
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=144| 0x02 | Code | | Vers | Sub |MessageType=144| 0x02 | Result Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier = 0001 | | Partition ID | Transaction Identifier = 0001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length | |I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Target 0x1000 | Target TLV Length | | Type = Target 0x1000 | Target TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
skipping to change at page 23, line 22 skipping to change at page 23, line 22
NAS initiated Multicast Control use case presented in [RFC5851] and NAS initiated Multicast Control use case presented in [RFC5851] and
summarized in Section 3.1. In that case, the NAS MUST set the Result summarized in Section 3.1. In that case, the NAS MUST set the Result
field to AckAll (0x2) or Nack (0x1) according to its requirements. field to AckAll (0x2) or Nack (0x1) according to its requirements.
The NAS MAY also send this message in response to a Multicast The NAS MAY also send this message in response to a Multicast
Admission Control message (defined in Section 4.4) received from the Admission Control message (defined in Section 4.4) received from the
AN to support the conditional access and admission control use case AN to support the conditional access and admission control use case
presented in [RFC5851] and summarized in Section 3.2. In that case, presented in [RFC5851] and summarized in Section 3.2. In that case,
the NAS MUST set the Result field to NAck (0x1). the NAS MUST set the Result field to NAck (0x1).
In either case, the sender MUST populate the Code field with the In either case, the sender MUST populate the Result Code field with
value 0x000 and the ANCP Transaction Identifier field with a unique the value 0x000 and the ANCP Transaction Identifier field with a
value, as described in Section 4.4.1 of [I-D.ietf-ancp-protocol]. unique value, as described in Section 3.6.1.6 of
[I-D.ietf-ancp-protocol].
Each Multicast Replication Control Message MUST contain one or more Each Multicast Replication Control Message MUST contain one or more
commands, each encapsulated in its own Command TLV. The sender MUST commands, each encapsulated in its own Command TLV. The sender MUST
use a separate Command TLV for each distinct multicast flow. use a separate Command TLV for each distinct multicast flow.
When the order of processing of two commands does not matter, the When the order of processing of two commands does not matter, the
commands MUST be transmitted in separate Multicast Replication commands MUST be transmitted in separate Multicast Replication
Control messages. Control messages.
4.3.2. Receiver Behaviour 4.3.2. Receiver Behaviour
skipping to change at page 24, line 9 skipping to change at page 24, line 10
If more than one Command TLV is present in a Multicast Replication If more than one Command TLV is present in a Multicast Replication
Control message, the AN MUST act on the commands in the order in Control message, the AN MUST act on the commands in the order in
which they are presented in the message. The AN SHALL assign a which they are presented in the message. The AN SHALL assign a
sequence number to each command in a given Multicast Replication sequence number to each command in a given Multicast Replication
Control message, starting from 0x01 for the first command. Control message, starting from 0x01 for the first command.
If a Command TLV adds a flow and the AN is performing admission If a Command TLV adds a flow and the AN is performing admission
control for Multicast Replication Control messages, then the AN MUST control for Multicast Replication Control messages, then the AN MUST
perform admission control before replicating the flow. If the perform admission control before replicating the flow. If the
admission control check fails, the AN MUST treat the failure as an admission control check fails, the AN MUST treat the failure as an
error as described below. The appropriate Code value for the error as described below. The appropriate Result Code value for the
response is 18 (0x012) "Insufficient resources". response is 18 (0x012) "Insufficient resources".
If the AN processes the complete Multicast Replication Control If the AN processes the complete Multicast Replication Control
message successfully and the Result field of the Multicast message successfully and the Result field of the Multicast
Replication Control message was set to AckAll (0x2), the AN MUST Replication Control message was set to AckAll (0x2), the AN MUST
respond with a Generic Response message where the Result field is set respond with a Generic Response message where the Result field is set
to Success (0x3), the Code field is set to 0x000, and the Transaction to Success (0x3), the Result Code field is set to 0x000, and the
Identifier field is copied from the Multicast Replication Control Transaction Identifier field is copied from the Multicast Replication
message. The body of the response MAY be empty or MAY be copied from Control message. The body of the response MAY be empty or MAY be
the Multicast Replication Control message. copied from the Multicast Replication Control message.
If the AN processes the complete Multicast Replication Control If the AN processes the complete Multicast Replication Control
message successfully and the Result field of the Multicast message successfully and the Result field of the Multicast
Replication Control message was set to Nack (0x1), the AN MUST NOT Replication Control message was set to Nack (0x1), the AN MUST NOT
respond to the message. respond to the message.
The processing/execution of multiple commands contained in a single The processing/execution of multiple commands contained in a single
Multicast Control message MUST be interrupted at the first error Multicast Control message MUST be interrupted at the first error
encountered, and the remaining commands in the Multicast Replication encountered, and the remaining commands in the Multicast Replication
Control message discarded. Control message discarded.
If the AN detects an error in a received Multicast Replication If the AN detects an error in a received Multicast Replication
Control message and the Result field in that message was set to Nack Control message and the Result field in that message was set to Nack
(0x1) or AckAll(0x2), the AN MUST generate a Generic Response message (0x1) or AckAll(0x2), the AN MUST generate a Generic Response message
providing error information to the NAS. This specification providing error information to the NAS. This specification
identifies the following new Code values beyond those specified in identifies the following new Result Code values beyond those
[I-D.ietf-ancp-protocol], which MAY be used in a Generic Response specified in [I-D.ietf-ancp-protocol], which MAY be used in a Generic
sent in reply to a Multicast Replication Control message: Response sent in reply to a Multicast Replication Control message:
100 Command error. This SHOULD be reported for the case that an 100 Command error. This SHOULD be reported for the case that an
invalid command code has been received. invalid command code has been received.
101 Bad flow address. This SHOULD be reported for the following 101 Bad flow address. This SHOULD be reported for the following
cases: cases:
* unsupported address family; * unsupported address family;
* source address present for an ASM flow, or absent for an SSM * source address present for an ASM flow, or absent for an SSM
flow. flow.
102 Multicast flow does not exist. This SHOULD be reported if the 102 Multicast flow does not exist. This SHOULD be reported if the
NAS attempts to delete a flow that is not enabled. NAS attempts to delete a flow that is not enabled.
A Generic Response message responding to the Multicast Replication A Generic Response message responding to the Multicast Replication
Control message and containing one of the above Code values MUST Control message and containing one of the above Result Code values
include a Status-Info TLV which includes one or two embedded TLVs as MUST include a Status-Info TLV which includes one or two embedded
follows: TLVs as follows:
o a Sequence-Number TLV as described in Section 5.4, giving the o a Sequence-Number TLV as described in Section 5.4, giving the
sequence number of the failed command, MUST be included; sequence number of the failed command, MUST be included;
o the failed Command TLV itself SHOULD be included. o the failed Command TLV itself SHOULD be included.
Note that the Error Message field of the Status-Info TLV MAY be Note that the Error Message field of the Status-Info TLV MAY be
used to report more details than implied by the Code value in the used to report more details than implied by the Result Code value
message header. For example, the Code value could be 101 and the in the message header. For example, the Result Code value could
Error Message field could contain the text: "Source address be 101 and the Error Message field could contain the text: "Source
present for ASM flow". address present for ASM flow".
4.4. Multicast Admission Control Message 4.4. Multicast Admission Control Message
This section defines a new message called the Multicast Admission This section defines a new message called the Multicast Admission
Control message. The Multicast Admission Control message is sent by Control message. The Multicast Admission Control message is sent by
the AN to the NAS to request admission of a multicast flow, or to the AN to the NAS to request admission of a multicast flow, or to
notify of the removal of a multicast flow, for a given target. notify of the removal of a multicast flow, for a given target.
The Message Type for the Multicast Admission Control message is 145. The Message Type for the Multicast Admission Control message is 145.
skipping to change at page 26, line 31 skipping to change at page 26, line 31
Note that the Command TLV length includes the length of any embedded Note that the Command TLV length includes the length of any embedded
TLVs, including the embedded TLV headers. TLVs, including the embedded TLV headers.
4.4.1. Sender Behaviour 4.4.1. Sender Behaviour
The AN sending the Multicast Admission Control message MUST set the The AN sending the Multicast Admission Control message MUST set the
Result field to Ignore (0x0). Result field to Ignore (0x0).
The AN MUST populate the ANCP Transaction Identifier field with a The AN MUST populate the ANCP Transaction Identifier field with a
unique value, as described in Section 4.4.1 of unique value, as described in Section 3.6.1.6 of
[I-D.ietf-ancp-protocol] . [I-D.ietf-ancp-protocol] .
The AN MUST encode the Command TLV as specified in Section 4.3 with The AN MUST encode the Command TLV as specified in Section 4.3 with
the following additional rules: the following additional rules:
o the Accounting field MUST be set to 0; o the Accounting field MUST be set to 0;
o the Command Code field MUST be set to "0x01 - Add" when the o the Command Code field MUST be set to "0x01 - Add" when the
message conveys a Join , to "0x02 - Delete" when the message message conveys a Join , to "0x02 - Delete" when the message
conveys a Leave and to "0x03 - Delete All" when the message conveys a Leave and to "0x03 - Delete All" when the message
skipping to change at page 28, line 22 skipping to change at page 28, line 22
adjacency); adjacency);
* MUST contain the directive rejected by the NAS (i.e. Target * MUST contain the directive rejected by the NAS (i.e. Target
TLV and Command TLV) but with a Command Code set to "0x04 - TLV and Command TLV) but with a Command Code set to "0x04 -
Admission Control Reject", "0x05 - Conditional Access Reject", Admission Control Reject", "0x05 - Conditional Access Reject",
or "0x06 - Admission Control and Conditional Access Reject". or "0x06 - Admission Control and Conditional Access Reject".
o if the Multicast Admission Control message cannot be processed o if the Multicast Admission Control message cannot be processed
correctly by the NAS (e.g. the message is malformed, the multicast correctly by the NAS (e.g. the message is malformed, the multicast
flow does not exist etc.), the NAS MUST generate a Generic flow does not exist etc.), the NAS MUST generate a Generic
Response message (defined in Section 6.1.3 of Response message (defined in Section 4.2 of
[I-D.ietf-ancp-protocol]) with appropriate content indicating the [I-D.ietf-ancp-protocol]) with appropriate content indicating the
reason for the failure. reason for the failure.
4.5. Bandwidth Reallocation Request Message 4.5. Bandwidth Reallocation Request Message
The Bandwidth Reallocation Request message is used when the bandwidth The Bandwidth Reallocation Request message is used when the bandwidth
delegation capability is included in the negotiated set. It MAY be delegation capability is included in the negotiated set. It MAY be
sent either by the NAS or by the AN to request an adjustment in the sent either by the NAS or by the AN to request an adjustment in the
amount of delegated bandwidth. It will be sent by the NAS typically amount of delegated bandwidth. It will be sent by the NAS typically
to reduce the multicast bandwidth allocated to the AN in order for to reduce the multicast bandwidth allocated to the AN in order for
the NAS to satisfy a request to add one or more flows. Conversely, the NAS to satisfy a request to add one or more flows. Conversely,
the AN will send a Bandwidth Reallocation Request to obtain the AN will send a Bandwidth Reallocation Request to obtain
additional bandwidth to satisfy a request to add a multicast channel. additional bandwidth to satisfy a request to add a multicast channel.
In each case, the requestor has a minimum requirement for additional In each case, the requestor has a minimum requirement for additional
bandwidth, and MAY ask for additional bandwidth beyond this amount bandwidth, and MAY ask for additional bandwidth beyond this amount
(e.g., to handle anticipated future requests). (e.g., to handle anticipated future requests).
The Bandwidth Reallocation Request message contains two TLVs: The Bandwidth Reallocation Request message contains two TLVs:
o the Target TLV (Section 6.2.1 of [I-D.ietf-ancp-protocol] or an o the Target TLV (Section 4.3 of [I-D.ietf-ancp-protocol] or an
extension), specifying a single access line; extension), specifying a single access line;
o the Bandwidth-Request TLV (Section 5.8), specifying the required o the Bandwidth-Request TLV (Section 5.8), specifying the required
and preferred amounts of delegated bandwidth. and preferred amounts of delegated bandwidth.
The Message Type for the Bandwidth Reallocation Request message is The Message Type for the Bandwidth Reallocation Request message is
146. 146.
4.5.1. Sender Behaviour 4.5.1. Sender Behaviour
skipping to change at page 29, line 42 skipping to change at page 29, line 42
When the peer receives a valid Bandwidth Reallocation Request When the peer receives a valid Bandwidth Reallocation Request
message, it SHOULD determine whether it can satisfy the request from message, it SHOULD determine whether it can satisfy the request from
its existing allocation of unused video bandwidth. If it decides its existing allocation of unused video bandwidth. If it decides
that it can reallocate bandwidth to the peer, it MAY choose to return that it can reallocate bandwidth to the peer, it MAY choose to return
any amount between the required and the preferred amounts indicated any amount between the required and the preferred amounts indicated
in the Bandwidth Reallocation Request message. in the Bandwidth Reallocation Request message.
The peer MUST return a Bandwidth Transfer message Section 4.6 The peer MUST return a Bandwidth Transfer message Section 4.6
indicating its decision. If the request is met, the Result field of indicating its decision. If the request is met, the Result field of
the Bandwidth Transfer message MUST be set to Success (0x3), the Code the Bandwidth Transfer message MUST be set to Success (0x3), the
field MUST be set to 0x000, and the Bandwidth-Allocation TLV Result Code field MUST be set to 0x000, and the Bandwidth-Allocation
(Section 5.5) MUST contain the new value of total multicast TLV (Section 5.5) MUST contain the new value of total multicast
bandwidth. This new value MUST lie between the required and bandwidth. This new value MUST lie between the required and
preferred values, inclusive, from the request message. If the preferred values, inclusive, from the request message. If the
request is not met, the Result field of the Bandwidth Transfer request is not met, the Result field of the Bandwidth Transfer
message MUST be set to Failure (0x4), the Code field MUST be set to message MUST be set to Failure (0x4), the Result Code field MUST be
0x000, and the Bandwidth Allocation TLV MUST contain the value of the set to 0x000, and the Bandwidth Allocation TLV MUST contain the value
currently allocated amount of delegated bandwidth as the responder of the currently allocated amount of delegated bandwidth as the
views it. responder views it.
The following cases indicate that the sender holds a different view The following cases indicate that the sender holds a different view
of the amount of delegated bandwidth from the receiver: of the amount of delegated bandwidth from the receiver:
o the NAS receives a request where the required amount is less than o the NAS receives a request where the required amount is less than
its view of the current amount of delegated bandwidth; its view of the current amount of delegated bandwidth;
o the AN receives a request where the required amount is greater o the AN receives a request where the required amount is greater
than its view of the current amount of delegated bandwidth. than its view of the current amount of delegated bandwidth.
skipping to change at page 30, line 39 skipping to change at page 30, line 39
While the cases just described are an error condition, the success While the cases just described are an error condition, the success
response achieves a graceful recovery. response achieves a graceful recovery.
To avoid deadlock due to race conditions, the following rules MUST be To avoid deadlock due to race conditions, the following rules MUST be
applied: applied:
a. If the NAS receives a Bandwidth Reallocation Request message a. If the NAS receives a Bandwidth Reallocation Request message
while it has a Bandwidth Reallocation Request message of its own while it has a Bandwidth Reallocation Request message of its own
outstanding for the same access line, the NAS MUST provide an outstanding for the same access line, the NAS MUST provide an
immediate failure response to the request from the AN, with a immediate failure response to the request from the AN, with a
Code value set to 105 "Bandwidth request conflict". Result Code value set to 105 "Bandwidth request conflict".
b. If the AN receives a Bandwidth Reallocation Request message while b. If the AN receives a Bandwidth Reallocation Request message while
it has a Bandwidth Reallocation Request message of its own it has a Bandwidth Reallocation Request message of its own
outstanding for the same access line, the AN MUST release any outstanding for the same access line, the AN MUST release any
bandwidth it has already committed to an outstanding Join request bandwidth it has already committed to an outstanding Join request
while it is awaiting a response from the NAS. It MUST decide while it is awaiting a response from the NAS. It MUST decide
upon and send its response to the NAS taking the released upon and send its response to the NAS taking the released
bandwidth into account. bandwidth into account.
If the receiver is unable to process the Bandwidth Reallocation If the receiver is unable to process the Bandwidth Reallocation
Request message due to an error, then the receiver MUST return a Request message due to an error, then the receiver MUST return a
Bandwidth Transfer message where: Bandwidth Transfer message where:
o the Result field is set to Failure (0x4), o the Result field is set to Failure (0x4),
o the Code field is set appropriately to indicate the type of error o the Result Code field is set appropriately to indicate the type of
that was detected, error that was detected,
o the Bandwidth Allocation TLV contains the value of the current o the Bandwidth Allocation TLV contains the value of the current
amount of delegated bandwidth as the responder views it, and amount of delegated bandwidth as the responder views it, and
o a Status-Info TLV MAY follow the Bandwidth Allocation TLV giving o a Status-Info TLV MAY follow the Bandwidth Allocation TLV giving
further information about the error. further information about the error.
This specification provides three new Code values applicable This specification provides three new Result Code values applicable
specifically to the contents of the Bandwidth-Request TLV. These specifically to the contents of the Bandwidth-Request TLV. These
Code values by their nature MUST only be used when the error is being Result Code values by their nature MUST only be used when the error
reported in a Bandwidth Transfer message rather than a Generic is being reported in a Bandwidth Transfer message rather than a
Response message. Generic Response message.
103 invalid preferred bandwidth amount. This indicates that the 103 invalid preferred bandwidth amount. This indicates that the
preferred and required amounts of bandwidth in the TLV do not have preferred and required amounts of bandwidth in the TLV do not have
the numerical relationship described in the previous section. the numerical relationship described in the previous section.
104 inconsistent views of delegated bandwidth amount. This will 104 inconsistent views of delegated bandwidth amount. This will
appear only in a Bandwidth Transfer message from the NAS to the AN appear only in a Bandwidth Transfer message from the NAS to the AN
in the case where the NAS has an outstanding Bandwidth in the case where the NAS has an outstanding Bandwidth
Reallocation Request. The recommended procedure for recovery is Reallocation Request. The recommended procedure for recovery is
described in Section 4.6.2. described in Section 4.6.2.
skipping to change at page 33, line 13 skipping to change at page 33, line 13
enforce. enforce.
4.6.2.2. Behaviour of the AN 4.6.2.2. Behaviour of the AN
If the amount of delegated bandwidth provided in the Bandwidth- If the amount of delegated bandwidth provided in the Bandwidth-
Allocation TLV of the Bandwidth Transfer message differs from the Allocation TLV of the Bandwidth Transfer message differs from the
AN's view of the current amount of delegated bandwidth, the AN MUST AN's view of the current amount of delegated bandwidth, the AN MUST
update its view of the current amount of delegated bandwidth to the update its view of the current amount of delegated bandwidth to the
amount indicated in the Bandwidth Transfer message. This is required amount indicated in the Bandwidth Transfer message. This is required
with the exception of a Bandwidth Transfer message with a Result with the exception of a Bandwidth Transfer message with a Result
field equal to Failure (0x4) and a Code field equal to 104 field equal to Failure (0x4) and a Result Code field equal to 104
"Inconsistent views of delegated bandwidth amount" or 105 "Bandwidth "Inconsistent views of delegated bandwidth amount" or 105 "Bandwidth
request conflict". If Code value 104 is received, the AN MUST issue request conflict". If Result Code value 104 is received, the AN MUST
a Delegated Bandwidth Query Request message to determine the NAS's issue a Delegated Bandwidth Query Request message to determine the
current view of the amount of delegated bandwidth. The AN MUST NAS's current view of the amount of delegated bandwidth. The AN MUST
update its own view based on the value returned in the Delegated update its own view based on the value returned in the Delegated
Bandwidth Query Response. If Code value 105 is received, the AN Bandwidth Query Response. If Result Code value 105 is received, the
SHOULD carry out this procedure unless it can account for the AN SHOULD carry out this procedure unless it can account for the
discrepancy as a result of a transfer of bandwidth to the NAS that discrepancy as a result of a transfer of bandwidth to the NAS that
was carried out just before the incoming Bandwidth Transfer message was carried out just before the incoming Bandwidth Transfer message
was processed. was processed.
The two Code values indicate a race condition where the AN may The two Result Code values indicate a race condition where the AN
have just completed a transfer of bandwidth to the NAS. As a may have just completed a transfer of bandwidth to the NAS. As a
result, the value given in the Bandwidth Transfer message may be result, the value given in the Bandwidth Transfer message may be
outdated, and the AN needs to query the NAS to find its latest outdated, and the AN needs to query the NAS to find its latest
view. The procedure assumes that ordering is preserved between view. The procedure assumes that ordering is preserved between
the Bandwidth Transfer message sent by the AN in response to the the Bandwidth Transfer message sent by the AN in response to the
NAS's request and the subsequent Delegated Bandwidth Query Request NAS's request and the subsequent Delegated Bandwidth Query Request
message. message.
If as the result of the procedures just described the AN determines If as the result of the procedures just described the AN determines
that it has over-committed multicast bandwidth, it MUST NOT terminate that it has over-committed multicast bandwidth, it MUST NOT terminate
any currently-active programs, but MUST NOT honour any more "join" any currently-active programs, but MUST NOT honour any more "join"
skipping to change at page 34, line 8 skipping to change at page 34, line 8
The Delegated Bandwidth Query Request message MAY be sent either by The Delegated Bandwidth Query Request message MAY be sent either by
the NAS or by the AN to retrieve the peer's view of the amount of the NAS or by the AN to retrieve the peer's view of the amount of
delegated bandwidth. The request contains one TLV: delegated bandwidth. The request contains one TLV:
o a Target TLV designating the access line for which the information o a Target TLV designating the access line for which the information
is requested. is requested.
4.7.1. Sender Behaviour 4.7.1. Sender Behaviour
The sender MUST set the Result field in the header of the Delegated The sender MUST set the Result field in the header of the Delegated
Bandwidth Query Request message to AckAll (0x2). The Code value MUST Bandwidth Query Request message to AckAll (0x2). The Result Code
be set to 0x000. The sender MUST populate the ANCP Transaction value MUST be set to 0x000. The sender MUST populate the ANCP
Identifier field with a unique value, as described in Section 4.4.1 Transaction Identifier field with a unique value, as described in
of [I-D.ietf-ancp-protocol]. Section 3.6.1.6 of [I-D.ietf-ancp-protocol].
4.7.2. Receiver Behaviour 4.7.2. Receiver Behaviour
If the AN or NAS receives a valid Delegated Bandwidth Query Request If the AN or NAS receives a valid Delegated Bandwidth Query Request
message, it MUST respond with a Delegated Bandwidth Query Response message, it MUST respond with a Delegated Bandwidth Query Response
message. The Result field in the header of the response MUST be set message. The Result field in the header of the response MUST be set
to Success (0x3). The Code field MUST be set to 0x000. The to Success (0x3). The Result Code field MUST be set to 0x000. The
Transaction-Id field MUST be copied from the request message. The Transaction-Id field MUST be copied from the request message. The
body of the response MUST contain the Target TLV, copied from the body of the response MUST contain the Target TLV, copied from the
request message. Finally, the body of the response MUST contain a request message. Finally, the body of the response MUST contain a
Bandwidth-Allocation TLV, containing the current amount of delegated Bandwidth-Allocation TLV, containing the current amount of delegated
bandwidth from the point of view of the receiver of the request. bandwidth from the point of view of the receiver of the request.
If the contents of the Delegated Bandwidth Query Request message are If the contents of the Delegated Bandwidth Query Request message are
in error, the receiver MUST return a Delegated Bandwidth Query in error, the receiver MUST return a Delegated Bandwidth Query
Response message with the Result field in the header set to Failure Response message with the Result field in the header set to Failure
(0x3). The Code field MUST be set to the value that indicates the (0x3). The Result Code field MUST be set to the value that indicates
nature of the error (e.g., 4 "Unrecognized target"). The the nature of the error (e.g., 4 "Unrecognized target"). The
Transaction-Id field MUST be copied from the request. The body of Transaction-Id field MUST be copied from the request. The body of
the response MUST contain the Target TLV copied from the request. the response MUST contain the Target TLV copied from the request.
This MAY be followed by a Status-Info TLV giving further information This MAY be followed by a Status-Info TLV giving further information
about the error. about the error.
4.8. Delegated Bandwidth Query Response Message 4.8. Delegated Bandwidth Query Response Message
The Delegated Bandwidth Query Response message is sent in reply to a The Delegated Bandwidth Query Response message is sent in reply to a
Delegated Bandwidth Query Request. The response to a valid request Delegated Bandwidth Query Request. The response to a valid request
contains two TLVs: contains two TLVs:
skipping to change at page 36, line 15 skipping to change at page 36, line 15
The Message Type for the Multicast Flow Query Request and Multicast The Message Type for the Multicast Flow Query Request and Multicast
Flow Query Response messages is 149. Flow Query Response messages is 149.
The contents of the Multicast Flow Query Request and Response depend The contents of the Multicast Flow Query Request and Response depend
on the nature of the query, as described below. on the nature of the query, as described below.
4.9.1. Sender Behaviour 4.9.1. Sender Behaviour
The sender of a Multicast Flow Query Request message MUST set the The sender of a Multicast Flow Query Request message MUST set the
Result field to AckAll (0x2). The Code field MUST be set to 0x000. Result field to AckAll (0x2). The Result Code field MUST be set to
The sender MUST populate the ANCP Transaction Identifier field with a 0x000. The sender MUST populate the ANCP Transaction Identifier
unique value, as described in section 4.4.1 of [I-D.ietf-ancp- field with a unique value, as described in section 3.6.1.6 of
protocol]. [I-D.ietf-ancp-protocol].
The Multicast Flow Query Request MAY be used by the NAS to retrieve: The Multicast Flow Query Request MAY be used by the NAS to retrieve:
o the AN's view of which multicast flows are currently active on a o the AN's view of which multicast flows are currently active on a
specified set of access ports; or specified set of access ports; or
o the AN's view of the access ports on which a specified set of o the AN's view of the access ports on which a specified set of
multicast flows are currently active; or multicast flows are currently active; or
o the AN's view of all the multicast flows currently active on each o the AN's view of all the multicast flows currently active on each
skipping to change at page 37, line 10 skipping to change at page 37, line 10
To retrieve the AN's view of all of the multicast flows currently To retrieve the AN's view of all of the multicast flows currently
active on each port of the AN, the NAS MUST send a Multicast Flow active on each port of the AN, the NAS MUST send a Multicast Flow
Query Request which does not contain any instance of the Target TLV Query Request which does not contain any instance of the Target TLV
or the Multicast-Flow TLV. or the Multicast-Flow TLV.
4.9.2. Receiver Behaviour 4.9.2. Receiver Behaviour
The AN MUST respond to a Multicast Flow Query Request message that The AN MUST respond to a Multicast Flow Query Request message that
has a valid format and a valid content with a Multicast Flow Query has a valid format and a valid content with a Multicast Flow Query
Response message. The Result field in the response MUST be set to Response message. The Result field in the response MUST be set to
Success (0x3). The Code field MUST be set to 0x000. The Success (0x3). The Result Code field MUST be set to 0x000. The
Transaction-Id field MUST be copied from the request. Transaction-Id field MUST be copied from the request.
If the Multicast Flow Query Request contained one (or more) Target If the Multicast Flow Query Request contained one (or more) Target
TLVs, the AN MUST include, for each of these Target TLVs, the TLVs, the AN MUST include, for each of these Target TLVs, the
following set of TLVs: following set of TLVs:
o Target TLV. This MUST be identical to the Target TLV in the o Target TLV. This MUST be identical to the Target TLV in the
received Multicast Flow Query Request message. received Multicast Flow Query Request message.
o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once
skipping to change at page 38, line 4 skipping to change at page 38, line 4
receiving multicast flow(s), the following set of TLVs: receiving multicast flow(s), the following set of TLVs:
o Target TLV. This MUST identify one AN port. o Target TLV. This MUST identify one AN port.
o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once
per Multicast Flow that is currently active on the AN port per Multicast Flow that is currently active on the AN port
identified in the preceding Target TLV. identified in the preceding Target TLV.
If the contents of the Multicast Flow Query Request are in error, the If the contents of the Multicast Flow Query Request are in error, the
AN MUST reply with a Multicast Flow Query Response message with the AN MUST reply with a Multicast Flow Query Response message with the
Result field set to Failure (0x4) and the Code field set to indicate Result field set to Failure (0x4) and the Result Code field set to
the nature of the error. If the request contained multiple instances indicate the nature of the error. If the request contained multiple
of the Target TLV or the Multicast-Flow TLV and one of these is in instances of the Target TLV or the Multicast-Flow TLV and one of
error, the response message MUST contain the results for the these is in error, the response message MUST contain the results for
preceding instances of the TLV as if there had been no error. These the preceding instances of the TLV as if there had been no error.
successful results MUST be followed by the TLV in error, copied from These successful results MUST be followed by the TLV in error, copied
the request. The AN MUST NOT do further processing of the request. from the request. The AN MUST NOT do further processing of the
The AN MAY add a Status-Info TLV to provide further information on request. The AN MAY add a Status-Info TLV to provide further
the nature of the error. information on the nature of the error.
4.10. Committed Bandwidth Report Message 4.10. Committed Bandwidth Report Message
This section describes the Committed Bandwidth Report message, which This section describes the Committed Bandwidth Report message, which
is sent from the AN to the NAS to report the most recent amount of is sent from the AN to the NAS to report the most recent amount of
multicast bandwidth usage committed to one or more access lines. multicast bandwidth usage committed to one or more access lines.
The Message Type for the Committed Bandwidth Report message is 150. The Message Type for the Committed Bandwidth Report message is 150.
The Committed Bandwidth Report message contains one or more instances The Committed Bandwidth Report message contains one or more instances
of the Committed-Bandwidth TLV, as described in Section 5.13. of the Committed-Bandwidth TLV, as described in Section 5.13.
4.10.1. Sender Behaviour 4.10.1. Sender Behaviour
The sender of a Committed Bandwidth Report message MUST set the The sender of a Committed Bandwidth Report message MUST set the
Result field to Ignore (0x0). The Code field MUST be set to 0x000. Result field to Ignore (0x0). The Result Code field MUST be set to
The sender MUST populate the ANCP Transaction Identifier field with a 0x000. The sender MUST populate the ANCP Transaction Identifier
unique value, as described in section 4.4.1 of [I-D.ietf-ancp- field with a unique value, as described in section 3.6.1.6 of
protocol]. [I-D.ietf-ancp-protocol].
Each instance of the Committed-Bandwidth TLV included in the message Each instance of the Committed-Bandwidth TLV included in the message
MUST identify an access line for which the amount of committed MUST identify an access line for which the amount of committed
multicast bandwidth has changed since the previous Committed multicast bandwidth has changed since the previous Committed
Bandwidth Report message was sent and MUST report the latest amount Bandwidth Report message was sent and MUST report the latest amount
of multicast bandwidth committed to that line. There MUST be only of multicast bandwidth committed to that line. There MUST be only
one instance of the Committed-Bandwidth TLV present in the message one instance of the Committed-Bandwidth TLV present in the message
for any given access line. The message MUST include an instance of for any given access line. The message MUST include an instance of
the Committed-Bandwidth TLV for every access line for which committed the Committed-Bandwidth TLV for every access line for which committed
multicast bandwidth has changed since the previous Committed multicast bandwidth has changed since the previous Committed
skipping to change at page 51, line 7 skipping to change at page 51, line 7
its header and any padding. its header and any padding.
o Committed Multicast Bandwidth is a 32-bit unsigned integer o Committed Multicast Bandwidth is a 32-bit unsigned integer
providing a bandwidth amount in kbits/s. providing a bandwidth amount in kbits/s.
o The Target TLV identifies the access line to which this amount of o The Target TLV identifies the access line to which this amount of
multicast bandwidth is currently committed. multicast bandwidth is currently committed.
6. Multicast Capabilities 6. Multicast Capabilities
Section 4.3 of [I-D.ietf-ancp-protocol] defines a capability Section 3.5 of [I-D.ietf-ancp-protocol] defines a capability
negotiation mechanism as well as a number of capabilities. This negotiation mechanism as well as a number of capabilities. This
section defines five new capabilities in support of different modes section defines five new capabilities in support of different modes
of multicast operation: of multicast operation:
o NAS-initiated replication (capability type 0x03); o NAS-initiated replication (capability type 0x03);
o committed multicast bandwidth reporting (capability type 0x05); o committed multicast bandwidth reporting (capability type 0x05);
o conditional access with white and black lists (capability type o conditional access with white and black lists (capability type
0x06); 0x06);
skipping to change at page 51, line 41 skipping to change at page 51, line 41
specifies how the capabilities interact if more than one multicast specifies how the capabilities interact if more than one multicast
capability is included in the set of capabilities negotiated between capability is included in the set of capabilities negotiated between
the AN and the NAS. the AN and the NAS.
Note that if a request contains content that is not supported Note that if a request contains content that is not supported
(according to the tables in Section 6.1) by the negotiated set of (according to the tables in Section 6.1) by the negotiated set of
multicast capabilities, the appropriate response is to return a multicast capabilities, the appropriate response is to return a
Generic Response message indicating Failure (0x4) with an appropriate Generic Response message indicating Failure (0x4) with an appropriate
code value (e.g., 84 "TLV or value not supported by negotiated code value (e.g., 84 "TLV or value not supported by negotiated
capability set"). The body of the message MUST contain a Status-Info capability set"). The body of the message MUST contain a Status-Info
TLV. See Sections 6.1.3 and 6.2.3 in [I-D.ietf-ancp-protocol] for TLV. See Sections 4.2 and 4.5 in [I-D.ietf-ancp-protocol] for more
more details. details.
6.1. Required Protocol Support 6.1. Required Protocol Support
This section specifies the protocol elements that MUST be implemented This section specifies the protocol elements that MUST be implemented
to support each of the four multicast capabilities. Support of to support each of the four multicast capabilities. Support of
multiple multicast capabilities requires implementation of the union multiple multicast capabilities requires implementation of the union
of the sets of protocol elements applying to each of the individual of the sets of protocol elements applying to each of the individual
capabilities in the supported set. capabilities in the supported set.
6.1.1. Protocol Requirements For NAS-initiated Replication 6.1.1. Protocol Requirements For NAS-initiated Replication
skipping to change at page 65, line 8 skipping to change at page 65, line 8
Committed bandwidth reporting can take independently of which other Committed bandwidth reporting can take independently of which other
multicast capabilities have been negotiated. However, some multicast capabilities have been negotiated. However, some
combinations do not make sense because of redundancy. In particular, combinations do not make sense because of redundancy. In particular,
the NAS obtains the same information that committed bandwidth the NAS obtains the same information that committed bandwidth
reporting gives if the only other capabilities operating are NAS- reporting gives if the only other capabilities operating are NAS-
initiated replication and/or conditional access with Grey lists. initiated replication and/or conditional access with Grey lists.
7. Security Considerations 7. Security Considerations
The security considerations of ANCP are discussed in The security considerations of ANCP are discussed in
[I-D.ietf-ancp-protocol] and in [I-D.ietf-ancp-security-threats]. [I-D.ietf-ancp-protocol] and in [RFC5713].
[Probably need to say more, but will do so later.]
8. IANA Considerations 8. IANA Considerations
RFC EDITOR'S NOTE: Please replace XXXX with the RFC number of this IANA NOTE: Please replace XXXX with the RFC number of this document.
document.
This document defines the following additional values within the
GSMPv3 Message Type Name Space registry, under the new heading
"Multicast Extensions To ANCP/GSMPv3":
+-----------------------------+----------------+--------+-----------+ This document defines the following additional values within the ANCP
| Message Name | Message Number | Status | Reference | Message Type Name Space registry:
+-----------------------------+----------------+--------+-----------+
| Multicast Replication | 144 | | RFC XXXX |
| Control | | | |
| | | | |
| Multicast Admission Control | 145 | | RFC XXXX |
| | | | |
| Bandwidth Reallocation | 146 | | RFC XXXX |
| Request | | | |
| | | | |
| Bandwidth Transfer | 147 | | RFC XXXX |
| | | | |
| Delegated Bandwidth Query | 148 | | RFC XXXX |
| | | | |
| Multicast Flow Query | 149 | | RFC XXXX |
| | | | |
| Committed Bandwidth Report | 150 | | RFC XXXX |
+-----------------------------+----------------+--------+-----------+
This document defines the following additional values for the GSMPv3 +--------------+--------------------------------+-----------+
Failure Response Message Name Space registry: | Message Type | Message Name | Reference |
+--------------+--------------------------------+-----------+
| 144 | Multicast Replication Control | RFC XXXX |
| | | |
| 145 | Multicast Admission Control | RFC XXXX |
| | | |
| 146 | Bandwidth Reallocation Request | RFC XXXX |
| | | |
| 147 | Bandwidth Transfer | RFC XXXX |
| | | |
| 148 | Delegated Bandwidth Query | RFC XXXX |
| | | |
| 149 | Multicast Flow Query | RFC XXXX |
| | | |
| 150 | Committed Bandwidth Report | RFC XXXX |
+--------------+--------------------------------+-----------+
+-------+-----------------------------------------------+-----------+ This document defines the following additional values for the ANCP
| Value | Failure Response Message Name | Reference | Result Code registry:
+-------+-----------------------------------------------+-----------+
| 100 | Command error. | RFC XXXX |
| | | |
| 101 | Bad flow address. | RFC XXXX |
| | | |
| 102 | Multicast flow does not exist. | RFC XXXX |
| | | |
| 103 | Invalid preferred bandwidth amount. | RFC XXXX |
| | | |
| 104 | Inconsistent views of delegated bandwidth | RFC XXXX |
| | amount. | |
| | | |
| 105 | Bandwidth request conflict. | RFC XXXX |
+-------+-----------------------------------------------+-----------+
This document defines the following additional values within the ANCP
TLV Type Registry:
+--------------------------------+-----------+-----------+ +------------+------------------------------------------+-----------+
| TLV Name | Type Code | Reference | | Result | One-Line Description | Reference |
+--------------------------------+-----------+-----------+ | Code | | |
| Multicast-Service-Profile | 0x13 | RFC XXXX | +------------+------------------------------------------+-----------+
| | | | | 0x64 | Command error. | RFC XXXX |
| Bandwidth-Allocation | 0x15 | RFC XXXX | | | | |
| | | | | 0x65 | Bad flow address. | RFC XXXX |
| Bandwidth-Request | 0x16 | RFC XXXX | | | | |
| | | | | 0x66 | Multicast flow does not exist. | RFC XXXX |
| Multicast-Service-Profile-Name | 0x18 | RFC XXXX | | | | |
| | | | | 0x67 | Invalid preferred bandwidth amount. | RFC XXXX |
| Multicast-Flow | 0x19 | RFC XXXX | | | | |
| | | | | 0x68 | Inconsistent views of delegated | RFC XXXX |
| List-Action | 0x21 | RFC XXXX | | | bandwidth amount. | |
| | | | | | | |
| Sequence-Number | 0x22 | RFC XXXX | | 0x69 | Bandwidth request conflict. | RFC XXXX |
| | | | +------------+------------------------------------------+-----------+
| White-List-CAC | 0x24 | RFC XXXX |
| | | |
| MRepCtl-CAC | 0x25 | RFC XXXX |
| | | |
| Request-Source-IP | 0x92 | RFC XXXX |
| | | |
| Request-Source-MAC | 0x93 | RFC XXXX |
| | | |
| Report-Buffering-Time | 0x94 | RFC XXXX |
| | | |
| Committed-Bandwidth | 0x95 | RFC XXXX |
+--------------------------------+-----------+-----------+
This document defines the following additional values for the ANCP This document defines the following additional values for the ANCP
Command Code registry: Command Code registry:
+--------------------------------------+----------------+-----------+ +----------------+--------------------------------------+-----------+
| Command Code Directive Name | Command Code | Reference | | Command Code | Command Code Directive Name | Reference |
| | Value | | | Value | | |
+--------------------------------------+----------------+-----------+ +----------------+--------------------------------------+-----------+
| Add | 0x01 | RFC XXXX | | 1 | Add | RFC XXXX |
| | | | | | | |
| Delete | 0x02 | RFC XXXX | | 2 | Delete | RFC XXXX |
| | | | | | | |
| Delete All | 0x03 | RFC XXXX | | 3 | Delete All | RFC XXXX |
| | | | | | | |
| Admission Control Reject | 0x04 | RFC XXXX | | 4 | Admission Control Reject | RFC XXXX |
| | | | | | | |
| Conditional Access Reject | 0x05 | RFC XXXX | | 5 | Conditional Access Reject | RFC XXXX |
| | | | | | | |
| Admission Control and Conditional | 0x06 | RFC XXXX | | 6 | Admission Control and Conditional | RFC XXXX |
| Access Reject | | | | | Access Reject | |
+--------------------------------------+----------------+-----------+ +----------------+--------------------------------------+-----------+
This document defines the following additional values within the ANCP
TLV Type Registry:
+-----------+--------------------------------+-----------+
| Type Code | TLV Name | Reference |
+-----------+--------------------------------+-----------+
| 0x13 | Multicast-Service-Profile | RFC XXXX |
| | | |
| 0x15 | Bandwidth-Allocation | RFC XXXX |
| | | |
| 0x16 | Bandwidth-Request | RFC XXXX |
| | | |
| 0x18 | Multicast-Service-Profile-Name | RFC XXXX |
| | | |
| 0x19 | Multicast-Flow | RFC XXXX |
| | | |
| 0x21 | List-Action | RFC XXXX |
| | | |
| 0x22 | Sequence-Number | RFC XXXX |
| | | |
| 0x24 | White-List-CAC | RFC XXXX |
| | | |
| 0x25 | MRepCtl-CAC | RFC XXXX |
| | | |
| 0x92 | Request-Source-IP | RFC XXXX |
| | | |
| 0x93 | Request-Source-MAC | RFC XXXX |
| | | |
| 0x94 | Report-Buffering-Time | RFC XXXX |
| | | |
| 0x95 | Committed-Bandwidth | RFC XXXX |
+-----------+--------------------------------+-----------+
This document defines the following additional values for the ANCP This document defines the following additional values for the ANCP
Capability registry: Capability Type registry:
+------------------------------------+------------------+-----------+ +-------+-------------------------+--------+------------+-----------+
| Capability Type Name | Capability Type | Reference | | Value | Capability Type Name | Tech | Capability | Reference |
| | Code | | | | | Type | Data? | |
+------------------------------------+------------------+-----------+ +-------+-------------------------+--------+------------+-----------+
| NAS-initiated replication | 0x3 | RFC XXXX | | 3 | NAS-Initiated | 0 | No | RFC XXXX |
| | | | | | Replication | | | |
| Committed bandwidth reporting | 0x5 | RFC XXXX | | | | | | |
| | | | | 5 | Committed Bandwidth | 0 | No | RFC XXXX |
| Conditional access with white and | 0x6 | RFC XXXX | | | Reporting | | | |
| black lists | | | | | | | | |
| | | | | 6 | Conditional Access With | 0 | No | RFC XXXX |
| Conditional access with grey lists | 0x7 | RFC XXXX | | | White and Black Lists | | | |
| | | | | | | | | |
| Bandwidth delegation | 0x8 | RFC XXXX | | 7 | Conditional Access With | 0 | No | RFC XXXX |
+------------------------------------+------------------+-----------+ | | Grey Lists | | | |
| 8 | Bandwidth Delegation | 0 | No | RFC XXXX |
+-------+-------------------------+--------+------------+-----------+
9. Acknowledgements 9. Acknowledgements
The authors would like to acknowledge Wojciech Dec for providing The authors would like to acknowledge Wojciech Dec for providing
useful input to this document, Robert Rennison for his help in useful input to this document, Robert Rennison for his help in
shaping the definition of the Multicast-Service-Profile TLV, Shridhar shaping the definition of the Multicast-Service-Profile TLV, Shridhar
Rao for his comments and suggestions and Aniruddha A for his proposal Rao for his comments and suggestions and Aniruddha A for his proposal
that formed the base of the Multicast Flow Reporting solution. that formed the base of the Multicast Flow Reporting solution.
Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided
substantial contributions on the solution for the NAS initiated substantial contributions on the solution for the NAS initiated
multicast control use case. Kristian Poscic provided the committed multicast control use case. Kristian Poscic provided the committed
bandwidth reporting use case. bandwidth reporting use case.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-ancp-protocol] [I-D.ietf-ancp-protocol]
Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T. Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T.
Taylor, "Protocol for Access Node Control Mechanism in Taylor, "Protocol for Access Node Control Mechanism in
Broadband Networks", draft-ietf-ancp-protocol-15 (work in Broadband Networks", draft-ietf-ancp-protocol-17 (work in
progress), February 2011. progress), April 2011.
[IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ [IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
EUI48.html", 2010. EUI48.html", 2010.
[IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ [IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
EUI64.html", 2010. EUI64.html", 2010.
[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.
skipping to change at page 70, line 41 skipping to change at page 71, line 41
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, October 2002. 3", RFC 3376, October 2002.
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
10.2. Informative References 10.2. Informative References
[I-D.ietf-ancp-security-threats]
Moustafa, H., Tschofenig, H., and S. Cnodder, "Security
Threats and Security Requirements for the Access Node
Control Protocol (ANCP)",
draft-ietf-ancp-security-threats-08 (work in progress),
July 2009.
[I-D.morin-mboned-igmpmld-error-feedback] [I-D.morin-mboned-igmpmld-error-feedback]
Morin, T. and B. Haberman, "IGMP/MLD Error Feedback", Morin, T. and B. Haberman, "IGMP/MLD Error Feedback",
draft-morin-mboned-igmpmld-error-feedback-02 (work in draft-morin-mboned-igmpmld-error-feedback-02 (work in
progress), November 2008. progress), November 2008.
[PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim- [PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim-
parameters.xhtml", 2005. parameters.xhtml", 2005.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006. Protocol Specification (Revised)", RFC 4601, August 2006.
[RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol
Independent Multicast (PIM) Join Attribute Format", Independent Multicast (PIM) Join Attribute Format",
RFC 5384, November 2008. RFC 5384, November 2008.
[RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, "Security
Threats and Security Requirements for the Access Node
Control Protocol (ANCP)", RFC 5713, January 2010.
[RFC5851] Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S. [RFC5851] 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",
RFC 5851, May 2010. RFC 5851, May 2010.
Appendix A. Example of Messages and Message Flows Appendix A. Example of Messages and Message Flows
This appendix provides an example in which most of the possible This appendix provides an example in which most of the possible
message flows for multicast control are illustrated. This appendix message flows for multicast control are illustrated. This appendix
is for informational purposes only. In case of discrepancy with text is for informational purposes only. In case of discrepancy with text
skipping to change at page 73, line 5 skipping to change at page 74, line 5
conditional access with white and black list, conditional access with conditional access with white and black list, conditional access with
grey list, and bandwidth delegation. At this point, the NAS can grey list, and bandwidth delegation. At this point, the NAS can
provision the service profiles on the AN and enable admission control provision the service profiles on the AN and enable admission control
at the AN for white-listed flows. To do this, the NAS sends the AN a at the AN for white-listed flows. To do this, the NAS sends the AN a
Provisioning message containing this information. An example message Provisioning message containing this information. An example message
providing the profile for our assumed subscriber is shown in providing the profile for our assumed subscriber is shown in
Figure 20. The message has the following contents: Figure 20. The message has the following contents:
o Message type is 93. o Message type is 93.
o The Result and Code fields in the header are set to zeroes, as o The Result and Result Code fields in the header are set to zeroes,
specified in the ANCP base protocol document. as specified in the ANCP base protocol document.
o A Transaction identifier is assigned by the NAS. o A Transaction identifier is assigned by the NAS.
o The Multicast-Service-Profile TLV (of which typically there would o The Multicast-Service-Profile TLV (of which typically there would
be multiple instances) contains a Multicast-Service-Profile-Name be multiple instances) contains a Multicast-Service-Profile-Name
TLV (with a length of 20 octets assumed for the example) and three TLV (with a length of 20 octets assumed for the example) and three
List-Action TLVs, one each for the White, Grey, and Black lists List-Action TLVs, one each for the White, Grey, and Black lists
within the profile. The White list flows come in two sets of within the profile. The White list flows come in two sets of
group addresses: 233.252.0.0/29, coming from a server at group addresses: 233.252.0.0/29, coming from a server at
192.0.2.15, and 233.252.0.32/29, coming from a server at 192.0.2.15, and 233.252.0.32/29, coming from a server at
skipping to change at page 73, line 31 skipping to change at page 74, line 31
source 192.0.2.21. source 192.0.2.21.
o The White-List-CAC TLV indicates that the AN does admission o The White-List-CAC TLV indicates that the AN does admission
control on White-listed flows. control on White-listed flows.
1 2 3 1 2 3
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 = 132 | | Type (0x88-0C) | Length = 132 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type = 93 | 0x00 | Code = 0x000 | | Vers | Sub | Msg Type = 93 | 0x00 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 132 | |I| SubMessage Number | Length = 132 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| M-Serv-Prof TLV Type = 0x13 | TLV Length = 112 | | M-Serv-Prof TLV Type = 0x13 | TLV Length = 112 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| M-S-Prof-Name TLV Type = 0x18 | Embedded TLV Length = 20 | | M-S-Prof-Name TLV Type = 0x18 | Embedded TLV Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast service profile name | | Multicast service profile name |
skipping to change at page 76, line 9 skipping to change at page 77, line 9
kbits/s) for one channel to start with. kbits/s) for one channel to start with.
The following fields in the Port Management message header are shown The following fields in the Port Management message header are shown
with specific values either as directed by the base protocol document with specific values either as directed by the base protocol document
or for the sake of our example: or for the sake of our example:
o Message Type is 32. o Message Type is 32.
o Result is set to Nack (0x01) for this example. o Result is set to Nack (0x01) for this example.
o Code is 0x000. o Result Code is 0x000.
o Port is set to 0. o Port is set to 0.
o Event Sequence Number, the R flag and the other bits marked x, o Event Sequence Number, the R flag and the other bits marked x,
Duration, the Event Flags, and the Flow Control Flags are all Duration, the Event Flags, and the Flow Control Flags are all
irrelevant for this function and are set to 0. irrelevant for this function and are set to 0.
o Function is set to 0x8, "Configure Connection Service Data". o Function is set to 0x8, "Configure Connection Service Data".
o X-Function is set to 0. o X-Function is set to 0.
skipping to change at page 77, line 10 skipping to change at page 78, line 10
o Block lengths are calculated assuming a Circuit-Id length of 4 in o Block lengths are calculated assuming a Circuit-Id length of 4 in
our example. Recall that the example Multicast-Service-Profile- our example. Recall that the example Multicast-Service-Profile-
Name TLV length is 20. Name TLV length is 20.
1 2 3 1 2 3
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 = 84 | | Type (0x88-0C) | Length = 84 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type = 32 | 0x01 | Code = 0x000 | | Vers | Sub | Msg Type = 32 | 0x01 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 84 | |I| SubMessage Number | Length = 84 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port = 0 | | Port = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number | | Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number = 0 | | Event Sequence Number = 0 |
skipping to change at page 80, line 10 skipping to change at page 81, line 10
* a Request-Source-IP embedded TLV containing the IGMP join * a Request-Source-IP embedded TLV containing the IGMP join
source IP (192.0.2.100). source IP (192.0.2.100).
The Multicast Admission Control message M1 is illustrated below: The Multicast Admission Control message M1 is illustrated below:
1 2 3 1 2 3
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 = 98 | | Type (0x88-0C) | Length = 98 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=145 | 0x0 | Code = 0x000 | | Vers | Sub | Msg Type=145 | 0x0 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 98 | |I| SubMessage Number | Length = 98 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length = 8 | | Type = 0x1000 (Target) | Target TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
skipping to change at page 81, line 26 skipping to change at page 82, line 26
port: IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) port: IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01)
Source Address = 192.0.2.21. Source Address = 192.0.2.21.
The Multicast Admission Control message M2 is illustrated below. The Multicast Admission Control message M2 is illustrated below.
1 2 3 1 2 3
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 = 48 | | Type (0x88-0C) | Length = 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=144 | 0x1 | Code = 0x000 | | Vers | Sub | Msg Type=144 | 0x1 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 48 | |I| SubMessage Number | Length = 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length = 8 | | Type = 0x1000 (Target) | Target TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
skipping to change at page 83, line 10 skipping to change at page 84, line 10
* a Request-Source-IP embedded TLV containing the IGMP leave * a Request-Source-IP embedded TLV containing the IGMP leave
request source, IPv4 (0x01) address 192.0.2.100. request source, IPv4 (0x01) address 192.0.2.100.
The Multicast Admission Control message M3 is illustrated below. The Multicast Admission Control message M3 is illustrated below.
1 2 3 1 2 3
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 | Msg Type=145 | 0x0 | Code = 0x000 | | Vers | Sub | Msg Type=145 | 0x0 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length | |I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length = 8 | | Type = 0x1000 (Target) | Target TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
skipping to change at page 86, line 10 skipping to change at page 87, line 10
is set to 0x0 (Ignore). Besides the Target, the message has one is set to 0x0 (Ignore). Besides the Target, the message has one
other TLV, the Bandwidth- Request, with a TLV Type of 0x16. The TLV other TLV, the Bandwidth- Request, with a TLV Type of 0x16. The TLV
contains Required Amount and Preferred Amount fields, set to 4000 and contains Required Amount and Preferred Amount fields, set to 4000 and
6000 kbits/s respectively. 6000 kbits/s respectively.
1 2 3 1 2 3
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 = 36 | | Type (0x88-0C) | Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=146 | 0x0 | Code = 0x000 | | Vers | Sub | Msg Type=146 | 0x0 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 36 | |I| SubMessage Number | Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length = 8 | | Type = 0x1000 (Target) | Target TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
skipping to change at page 87, line 10 skipping to change at page 88, line 10
Bandwidth Transfer message is 147. The Result field is set to Bandwidth Transfer message is 147. The Result field is set to
Success (0x3). The message contains the Target TLV and the Success (0x3). The message contains the Target TLV and the
Bandwidth- Allocation TLV. The latter has a TLV Type of 0x15 and Bandwidth- Allocation TLV. The latter has a TLV Type of 0x15 and
contains a Delegated Amount field, set to 4000 kbits/s. contains a Delegated Amount field, set to 4000 kbits/s.
1 2 3 1 2 3
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 = 32 | | Type (0x88-0C) | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=147 | 0x3 | Code = 0x000 | | Vers | Sub | Msg Type=147 | 0x3 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 32 | |I| SubMessage Number | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length = 8 | | Type = 0x1000 (Target) | Target TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
skipping to change at page 87, line 39 skipping to change at page 88, line 39
The Delegated Bandwidth Query request message (M3) is shown in The Delegated Bandwidth Query request message (M3) is shown in
Figure 28. The Message Type for the Delegated Bandwidth Query Figure 28. The Message Type for the Delegated Bandwidth Query
request message is 148. The Result field is set to AckAll (0x2). request message is 148. The Result field is set to AckAll (0x2).
The message contains the Target TLV only. The message contains the Target TLV only.
1 2 3 1 2 3
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 = 24 | | Type (0x88-0C) | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=148 | 0x2 | Code = 0x000 | | Vers | Sub | Msg Type=148 | 0x2 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 24 | |I| SubMessage Number | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length = 8 | | Type = 0x1000 (Target) | Target TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
skipping to change at page 88, line 16 skipping to change at page 89, line 16
in Figure 29. The Message Type for the Delegated Bandwidth Query in Figure 29. The Message Type for the Delegated Bandwidth Query
response message is 148. The Result field is set to Success (0x3). response message is 148. The Result field is set to Success (0x3).
The message contains the Target TLV and the Bandwidth-Allocation TLV The message contains the Target TLV and the Bandwidth-Allocation TLV
with the Delegated Amount field set to 4000 kbits/s. with the Delegated Amount field set to 4000 kbits/s.
1 2 3 1 2 3
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 = 32 | | Type (0x88-0C) | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=148 | 0x3 | Code = 0x000 | | Vers | Sub | Msg Type=148 | 0x3 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier (copied from request) | | Partition ID | Transaction Identifier (copied from request) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 32 | |I| SubMessage Number | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length = 8 | | Type = 0x1000 (Target) | Target TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
skipping to change at page 90, line 18 skipping to change at page 91, line 18
the Result field. The larger difference in this example is that the the Result field. The larger difference in this example is that the
flow description in the Multicast-Flow embedded TLV is that of an ASM flow description in the Multicast-Flow embedded TLV is that of an ASM
multicast group (Flow Type = 0x01) with IPv4 (0x01) group address multicast group (Flow Type = 0x01) with IPv4 (0x01) group address
233.252.1.100. 233.252.1.100.
1 2 3 1 2 3
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 = 44 | | Type (0x88-0C) | Length = 44 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=144 | 0x1 | Code = 0x000 | | Vers | Sub | Msg Type=144 | 0x1 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 44 | |I| SubMessage Number | Length = 44 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length = 8 | | Type = 0x1000 (Target) | Target TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
skipping to change at page 92, line 10 skipping to change at page 93, line 10
The Multicast Flow Query Request message (M1) is illustrated in The Multicast Flow Query Request message (M1) is illustrated in
Figure 33. The Message Type is 149. The Result field is set to Figure 33. The Message Type is 149. The Result field is set to
AckAll (0x2). Three Target TLVs are present, identifying port 10, AckAll (0x2). Three Target TLVs are present, identifying port 10,
port 20, and port 11 respectively. port 20, and port 11 respectively.
0 1 2 3 0 1 2 3
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 | Msg Type = 149|Rslt=2 | Code = 0 | | Vers | Sub | Msg Type = 149|Rslt=2 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length | |I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length | | Type = 0x1000 (Target) | Target TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
skipping to change at page 93, line 8 skipping to change at page 94, line 8
[(192.0.2.1, 233.252.2.4)] on port 10, no active multicast flow on [(192.0.2.1, 233.252.2.4)] on port 10, no active multicast flow on
port 20 and two active multicast flows [(192.0.2.1, 233.252.2.4) and port 20 and two active multicast flows [(192.0.2.1, 233.252.2.4) and
(192.0.2.2, 233.252.2.10)] on port 11. (192.0.2.2, 233.252.2.10)] on port 11.
0 1 2 3 0 1 2 3
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 | Msg Type = 149|Rslt=3 | Code = 0 | | Vers | Sub | Msg Type = 149|Rslt=3 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length | |I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length | | Type = 0x1000 (Target) | Target TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Access Loop Circuit ID (port10) ~ ~ Access Loop Circuit ID (port10) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = 233.252.2.4 | | Multicast Group Address = 233.252.2.4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Source Address = 192.0.2.1 | | Unicast Source Address = 192.0.2.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
| Type = 0x1000 (Target) | Target TLV Length | | Type = 0x1000 (Target) | Target TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Access Loop Circuit ID (port20) ~ ~ Access Loop Circuit ID (port20) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length | | Type = 0x1000 (Target) | Target TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Access Loop Circuit ID (port11) ~ ~ Access Loop Circuit ID (port11) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 End of changes. 72 change blocks. 
245 lines changed or deleted 251 lines changed or added

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