draft-ietf-ancp-mc-extensions-06.txt   draft-ietf-ancp-mc-extensions-07.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: June 7, 2012 Telecom Italia Expires: November 2, 2012 Telecom Italia
T. Taylor T. Taylor
Huawei Huawei
December 5, 2011 May 1, 2012
Multicast Control Extensions for ANCP Multicast Control Extensions for ANCP
draft-ietf-ancp-mc-extensions-06.txt draft-ietf-ancp-mc-extensions-07.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 June 7, 2012. This Internet-Draft will expire on November 2, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 30 skipping to change at page 3, line 30
3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 13 3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 13
3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 13 3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 13
4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 15 4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1. Provisioning Message . . . . . . . . . . . . . . . . . . . 15 4.1. Provisioning Message . . . . . . . . . . . . . . . . . . . 15
4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 15 4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 15
4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 16 4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 16
4.2. Port Management Message . . . . . . . . . . . . . . . . . 17 4.2. Port Management Message . . . . . . . . . . . . . . . . . 17
4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 18 4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 18
4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 18 4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 18
4.3. Multicast Replication Control Message . . . . . . . . . . 19 4.3. Multicast Replication Control Message . . . . . . . . . . 19
4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 23 4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 22
4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 23 4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 23
4.4. Multicast Admission Control Message . . . . . . . . . . . 25 4.4. Multicast Admission Control Message . . . . . . . . . . . 25
4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 26 4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 26
4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 27 4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 27
4.5. Bandwidth Reallocation Request Message . . . . . . . . . . 28 4.5. Bandwidth Reallocation Request Message . . . . . . . . . . 28
4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 28 4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 29
4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 29 4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 29
4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . . 31 4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . . 32
4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 32 4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 33
4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 32 4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 33
4.7. Delegated Bandwidth Query Request Message . . . . . . . . 33 4.7. Delegated Bandwidth Query Request Message . . . . . . . . 34
4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 33 4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 35
4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 34 4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 35
4.8. Delegated Bandwidth Query Response Message . . . . . . . . 34 4.8. Delegated Bandwidth Query Response Message . . . . . . . . 35
4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 34 4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 36
4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 34 4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 36
4.9. Multicast Flow Query Request and Response Messages . . . . 35 4.9. Multicast Flow Query Request and Response Messages . . . . 37
4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 36 4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 37
4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 36 4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 38
4.10. Committed Bandwidth Report Message . . . . . . . . . . . . 38 4.10. Committed Bandwidth Report Message . . . . . . . . . . . . 39
4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 38 4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 39
4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 38 4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 40
5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 39 5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 41
5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 39 5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 41
5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . . 40 5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . . 42
5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 40 5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 42
5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 43 5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 45
5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . . 44 5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . . 45
5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . . 44 5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . . 46
5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 45 5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 47
5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 45 5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 47
5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 46 5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 48
5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . . 46 5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . . 48
5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . . 47 5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . . 49
5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 48 5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 50
5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 49 5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 51
6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . . 50 6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . . 52
6.1. Required Protocol Support . . . . . . . . . . . . . . . . 50 6.1. Required Protocol Support . . . . . . . . . . . . . . . . 52
6.1.1. Protocol Requirements For NAS-initiated Replication . 51 6.1.1. Protocol Requirements For NAS-Initiated Replication . 53
6.1.2. Protocol Requirements For Committed Multicast 6.1.2. Protocol Requirements For Committed Multicast
Bandwidth Reporting . . . . . . . . . . . . . . . . . 51 Bandwidth Reporting . . . . . . . . . . . . . . . . . 53
6.1.3. Protocol Requirements For Conditional Access With 6.1.3. Protocol Requirements For Conditional Access With
White and Black Lists . . . . . . . . . . . . . . . . 52 White and Black Lists . . . . . . . . . . . . . . . . 54
6.1.4. Protocol Requirements For Conditional Access With 6.1.4. Protocol Requirements For Conditional Access With
Grey Lists . . . . . . . . . . . . . . . . . . . . . . 53 Grey Lists . . . . . . . . . . . . . . . . . . . . . . 55
6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 54 6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 56
6.2. Capability-Specific Procedures for Providing Multicast 6.2. Capability-Specific Procedures for Providing Multicast
Service . . . . . . . . . . . . . . . . . . . . . . . . . 55 Service . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.2.1. Procedures For NAS-Initiated Replication . . . . . . . 55 6.2.1. Procedures For NAS-Initiated Replication . . . . . . . 57
6.2.2. Procedures For Committed Bandwidth Reporting . . . . 56 6.2.2. Procedures For Committed Bandwidth Reporting . . . . . 58
6.2.3. Procedures For Conditional Access With Black and 6.2.3. Procedures For Conditional Access With Black and
White Lists . . . . . . . . . . . . . . . . . . . . . 57 White Lists . . . . . . . . . . . . . . . . . . . . . 59
6.2.4. Procedures For Conditional Access With Grey Lists . . 59 6.2.4. Procedures For Conditional Access With Grey Lists . . 61
6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . . 60 6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . . 62
6.3. Combinations of Multicast Capabilities . . . . . . . . . . 61 6.3. Combinations of Multicast Capabilities . . . . . . . . . . 63
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 . . 61 Black Lists and Conditional Access With Grey Lists . . 63
6.3.2. Combination of Conditional Access With Delegated 6.3.2. Combination of Conditional Access With Delegated
Bandwidth . . . . . . . . . . . . . . . . . . . . . . 62 Bandwidth . . . . . . . . . . . . . . . . . . . . . . 64
6.3.3. Combination of NAS-Initiated Replication with 6.3.3. Combination of NAS-Initiated Replication with
Other Capabilities . . . . . . . . . . . . . . . . . . 62 Other Capabilities . . . . . . . . . . . . . . . . . . 64
6.3.4. Combinations of Committed Bandwidth Reporting with 6.3.4. Combinations of Committed Bandwidth Reporting with
Other Multicast Capabilities . . . . . . . . . . . . . 63 Other Multicast Capabilities . . . . . . . . . . . . . 65
7. Security Considerations . . . . . . . . . . . . . . . . . . . 64 7. Security Considerations . . . . . . . . . . . . . . . . . . . 66
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 69 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 71
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
10.1. Normative References . . . . . . . . . . . . . . . . . . . 70 10.1. Normative References . . . . . . . . . . . . . . . . . . . 72
10.2. Informative References . . . . . . . . . . . . . . . . . . 70 10.2. Informative References . . . . . . . . . . . . . . . . . . 72
Appendix A. Example of Messages and Message Flows . . . . . . . . 72 Appendix A. Example of Messages and Message Flows . . . . . . . . 74
A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . . 72 A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . . 74
A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 78 A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 80
A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 83 A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 85
A.4. Handling Of Black-Listed Join Requests . . . . . . . . . . 88 A.4. Handling Of Black-Listed Join Requests . . . . . . . . . . 90
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 . 90
A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 91 A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 93
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 97
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. [RFC6320] service-related and subscriber-related operations. [RFC6320]
specifies a protocol for Access Node Control in broadband networks in specifies a protocol for Access Node Control in broadband networks in
line with this framework. line with this framework.
skipping to change at page 9, line 24 skipping to change at page 9, line 24
or IGMP proxy in the Access Node and aggregation node(s). By or IGMP proxy in the Access Node and aggregation node(s). By
introducing IGMP processing in the access/aggregation nodes, the introducing IGMP processing in the access/aggregation nodes, the
multicast replication process is now divided between the NAS, the multicast replication process is now divided between the NAS, the
aggregation node(s) and Access Nodes. In order to ensure backward aggregation node(s) and Access Nodes. In order to ensure backward
compatibility with the ATM-based model, the NAS, aggregation node and compatibility with the ATM-based model, the NAS, aggregation node and
Access Node need to behave as a single logical device. This logical Access Node need to behave as a single logical device. This logical
device must have exactly the same functionality as the NAS in the ATM device must have exactly the same functionality as the NAS in the ATM
access/aggregation network. The Access Node Control Mechanism can be access/aggregation network. The Access Node Control Mechanism can be
used to make sure that this logical/functional equivalence is used to make sure that this logical/functional equivalence is
achieved by exchanging the necessary information between the Access achieved by exchanging the necessary information between the Access
Node and the NAS. " Node and the NAS."
[RFC5851] describes the use cases for ANCP associated with such [RFC5851] describes the use cases for ANCP associated with such
multicast operations, and identifies the associated ANCP multicast operations, and identifies the associated ANCP
requirements. The present section describes a subset of these use requirements. The present section describes a subset of these use
cases as background to facilitate reading of this document, but the cases as background to facilitate reading of this document, but the
reader is refered to [RFC5851] for a more exhaustive description of reader is refered to [RFC5851] for a more exhaustive description of
the ANCP multicast use cases. Detailed example message flows can the ANCP multicast use cases. Detailed example message flows can
also be found in Appendix A. also be found in Appendix A.
3.1. NAS Initiated Multicast Replication Control Use Case 3.1. NAS Initiated Multicast Replication Control Use Case
skipping to change at page 10, line 49 skipping to change at page 10, line 49
Authorization/Policy Server before admitting the flow. Authorization/Policy Server before admitting the flow.
Figure 1: NAS Initiated Multicast Replication Control Figure 1: NAS Initiated Multicast Replication Control
3.2. Conditional Access and Admission Control Use Case 3.2. Conditional Access and Admission Control Use Case
3.2.1. Goals 3.2.1. Goals
One option for multicast handling is for the access/aggregation nodes One option for multicast handling is for the access/aggregation nodes
to participate in IGMP/MLD processing (e.g. via IGMP/MLD snooping). to participate in IGMP/MLD processing (e.g. via IGMP/MLD snooping).
In this scenario, on detecting a join/leave request from an enduser In this scenario, on detecting a join/leave request from an end user
for a multicast flow (in the grey list), the AN uses ANCP to request for a multicast flow (in the grey list), the AN uses ANCP to request
conditional access and admission control decision from the NAS. In a conditional access and admission control decision from the NAS. In
turn, after conditional access and admission control checks, the NAS turn, after conditional access and admission control checks, the NAS
uses ANCP to instruct the AN to change the replication states uses ANCP to instruct the AN to change the replication states
accordingly. accordingly.
3.2.2. Message Flow 3.2.2. Message Flow
For support of the conditional access and admission control use case, For support of the conditional access and admission control use case,
on detection of an IGMP/MLD Join, the AN sends an Admission Control on detection of an IGMP/MLD Join, the AN sends an Admission Control
message to the NAS to request conditional access and admission message to the NAS to request a conditional access and admission
control check. In case of positive outcome, the NAS sends a control check. In the case of a positive outcome, the NAS sends a
Multicast Replication Control Message to the AN with a directive to Multicast Replication Control Message to the AN with a directive to
replicate the multicast flow to the corresponding user. Similarly on replicate the multicast flow to the corresponding user. Similarly on
detection of an IGMP/MLD leave, an Admission Control message is sent detection of an IGMP/MLD leave, an Admission Control message is sent
by the AN to the NAS to keep the NAS aware of user departure for the by the AN to the NAS to keep the NAS aware of user departure for the
flow. This message flow is illustrated in Figure 2. flow. This message flow is illustrated in Figure 2.
+----------+ +-------+ +-----+ ANCP +-----+ +----------+ +-------+ +-----+ ANCP +-----+
|Subscriber| | Home | | AN |<------------------->| NAS | |Subscriber| | Home | | AN |<------------------->| NAS |
+----------+ |Gateway| +-----+ +-----+ +----------+ |Gateway| +-----+ +-----+
| +-------+ | | | +-------+ | |
| | | | | | | |
| Join(Gr-Flow1) | Admission-Control | | Join(Gr-Flow1) | Admission-Control |
|------------+---------->| (Target,add,Gr-Flow1) | |------------+---------->| (Target,add,Gr-Flow1) |
| | |-------------------------->| | | |-------------------------->|
| | | (*) | | | (*)
| | | Multicast-Replication-Crl | | | | Multicast-Replication-Crl |
| | | (Target,add,Gr-Flow 1) | | | | (Target,add,Gr-Flow1) |
| | |<--------------------------| | | |<--------------------------|
| Mcast Gr-Flow1 | | | Mcast Gr-Flow1 | |
|<=======================+ | |<=======================+ |
| | | | | | | |
~ ~ ~ ~ ~ ~ ~ ~
| | | | | | | |
| Leave(Gr-Flow1) | Admission-Control | | Leave(Gr-Flow1) | Admission-Control |
|------------+---------->| (Target,delete,Gr-Flow1) | |------------+---------->| (Target,delete,Gr-Flow1) |
| | |-------------------------->| | | |-------------------------->|
| <Stop Replication of X | | <Stop Replication of X |
skipping to change at page 15, line 17 skipping to change at page 15, line 17
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 4.1 of [RFC6320] defines the Provisioning message that is Section 4.1 of [RFC6320] defines the Provisioning message that is
sent by the NAS to the AN to provision information in the AN. sent by the NAS to the AN to provision information in 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
in Section 5.1. Each instance of the Multicast-Service-Profile in Section 5.1. Each instance of the Multicast-Service-Profile
TLV contains a multicast service profile name and one or more list TLV contains a multicast service profile name and one or more list
actions. A list action consists of an action (add, delete, actions. A list action consists of an action (add, delete,
replace), a list type (White, Black, or Grey), and list content replace), a list type (white, black, or grey), and list content
(multicast source and group addresses). (multicast source and group addresses).
o an instance of the White-List-CAC TLV. The White-List-CAC TLV is o an instance of the White-List-CAC TLV. The White-List-CAC TLV is
defined in Section 5.6. If present, this TLV indicates that the defined in Section 5.6. If present, this TLV indicates that the
AN is required to do admission control before replicating White- AN is required to do admission control before replicating white-
listed flows. listed flows.
o an instance of the MRepCtl-CAC TLV. The MRepCtl-CAC TLV is o an instance of the MRepCtl-CAC TLV. The MRepCtl-CAC TLV is
defined in Section 5.7. If present, this TLV indicates that the defined in Section 5.7. If present, this TLV indicates that the
AN is required to do admission control before replicating flows AN is required to do admission control before replicating flows
specified in Multicast Replication Control messages. specified in Multicast Replication Control messages.
o an instance of the Report-Buffering-Time TLV. The Report- o an instance of the Report-Buffering-Time TLV. The Report-
Buffering-Time TLV is defined in Section 5.12. If present, this Buffering-Time TLV is defined in Section 5.12. If present, this
TLV indicates Committed Bandwidth Report messages should be TLV indicates Committed Bandwidth Report messages should be
buffered for the amount of time given by the TLV before being buffered for the amount of time given by the TLV before being
transmitted to the NAS. transmitted to the NAS.
See Section 6 for information on which multicast capabilities require See Section 6 for information on which multicast capabilities require
support of these TLVs in the Provisioning message. support of these TLVs in the Provisioning message.
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.
To require admission control to be performed at the AN on Grey-listed To require admission control to be performed at the AN on grey-listed
flows or on NAS-initiated flows, the NAS MUST include a copy of the flows or on NAS-initiated flows, the NAS MUST include a copy of the
MRepCtl-CAC TLV in the Provisioning message. The MRepCtl-CAC TLV MRepCtl-CAC TLV in the Provisioning message. The MRepCtl-CAC TLV
MUST NOT be provided unless the negotiated set of capabilities MUST NOT be provided unless the negotiated set of capabilities
includes NAS-initiated replication control or conditional access with includes NAS-initiated replication control or conditional access with
Grey lists. grey lists.
To require buffering of Committed Bandwidth Report messages so that To require buffering of Committed Bandwidth Report messages so that
reports for multiple access lines can be included in the same reports for multiple access lines can be included in the same
message, the NAS MUST include a copy of the Report-Buffering-Time TLV message, the NAS MUST include a copy of the Report-Buffering-Time TLV
containing a non-zero time value in a Provisioning message sent to containing a non-zero time value in a Provisioning message sent to
the AN. The Report-Buffering-Time TLV MUST NOT be provided unless the AN. The Report-Buffering-Time TLV MUST NOT be provided unless
the negotiated set of capabilities includes committed bandwidth the negotiated set of capabilities includes committed bandwidth
reporting. reporting.
4.1.2. Receiver Behaviour 4.1.2. Receiver Behaviour
The receiving AN provisions/updates the White, Black, and/or Grey The receiving AN provisions/updates the white, black, and/or grey
lists associated with the multicast service profile names contained lists associated with the multicast service profile names contained
in the Multicast-Service-Profile TLV instances within the message in the Multicast-Service-Profile TLV instances within the message
according to the contents of the associated List-Action TLVs. The AN according to the contents of the associated List-Action TLVs. The AN
MUST process List-Action TLVs in the order in which they appear MUST process List-Action TLVs in the order in which they appear
within the message. The AN MUST ignore instances of the List-Action within the message. The AN MUST ignore instances of the List-Action
TLV referring to any list type (White, Black, or Grey) that is not TLV referring to any list type (white, black, or grey) that is not
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.
When a new multicast service profile is identified by a Multicast- When a new multicast service profile is identified by a Multicast-
Service-Profile TLV, the initial state of all lists associated with Service-Profile TLV, the initial state of all lists associated with
that profile according to the negotiated set of multicast that profile according to the negotiated set of multicast
capabilities is empty until changed by the contents of Multicast- capabilities is empty until changed by the contents of Multicast-
Service-Profile TLVs. Service-Profile TLVs.
The receipt of a Provisioning message containing updates to an The receipt of a Provisioning message containing updates to an
skipping to change at page 18, line 6 skipping to change at page 18, line 6
to convey 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 When the Port Management message is used for this purpose:
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 o the Function field in the Port Management message MUST be set to
Section 5.1.2 of [RFC6320]. For non-DSL access lines, the 8, "Configure Connection Service Data".
appropriate alternative line-identifying TLV(s) MUST be present.
Line configuration data other than the two TLVs listed in the o the message MUST include TLV(s) to identify the access line
previous paragraph MAY be present. concerned. If the access line is a DSL loop, the line-identifying
TLV(s) MUST be as specified in Section 5.1.2 of [RFC6320]. 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
skipping to change at page 19, line 9 skipping to change at page 19, line 13
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 Result Code value returned in the response header. In by the Result Code value returned in the response header. In
particular, if the name within the Multicast-Service-Profile-Name TLV particular, if the name within the Multicast-Service-Profile-Name TLV
does not match a profile name given in a prior Provisioning message, does not match a profile name given in a prior Provisioning message,
the AN SHOULD return a reply where the Result Code field in the the AN SHOULD return a reply where the Result Code field in the
header indicates "Invalid TLV value" (85), the Error Message field in header indicates 0x55, "Invalid TLV contents", the Error Message
the Status-Info TLV contains the text "Multicast profile name not field in the Status-Info TLV contains the text "Multicast profile
provisioned", and the Status-Info TLV contains a copy of the name not provisioned", and the Status-Info TLV contains a copy of the
Multicast-Service-Profile-Name 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.
skipping to change at page 20, line 7 skipping to change at page 20, line 7
o an Accounting field; o an Accounting field;
o an instance of the Multicast-Flow TLV. o an instance of the Multicast-Flow TLV.
Figure 5 illustrates the complete Command TLV with the contents Figure 5 illustrates the complete Command TLV with the contents
specific to the Multicast Replication Control message. specific to the Multicast Replication Control message.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = Command | Command-TLV Length | | TLV Type = Command | Command-TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Command Code | Accounting | Reserved | |Command Code | Accounting | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast-Flow TLV | | Multicast-Flow TLV |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Other embedded TLV Type | Other embedded TLV Length | | Other embedded TLV Type | Other embedded TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Other embedded TLV data ~ ~ Other embedded TLV data ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Contents of the Command TLV in the Multicast Replication Figure 5: Contents of the Command TLV in the Multicast Replication
Control Message Control Message
Command Code: Command Code:
Command directive: Command directive:
0x01 - Add; 1 - Add;
0x02 - Delete; 2 - Delete;
0x03 - Delete All; 3 - Delete All;
0x04 - Admission Control Reject; 4 - Admission Control Reject;
0x05 - Conditional Access Reject; 5 - Conditional Access Reject;
0x06 - Admission Control and Conditional Access 6 - Admission Control and Conditional Access
Reject. Reject.
Directives 0x04 through 0x06 are used as described in Directives 4 through 6 are used as described in
Section 4.4.2 Section 4.4.2.
Accounting: Accounting:
Meaningful only when the Command Code is "Add" (0x01). In Meaningful only when the Command Code is "Add" (1). In
that case, 0x00 indicates no flow accounting, 0x01 that case, 0x00 indicates no flow accounting, 0x01
indicates that octet accounting for the flow is to indicates that octet accounting for the flow is to
commence. The Accounting field MUST be set to 0x00 for commence. The Accounting field MUST be set to 0x00 for
other Command Code values. other Command Code values.
Reserved: Reserved:
Reserved for future use. MUST be set to 0x0000 by the Reserved for future use. MUST be set to 0x0000 by the
sender and ignored by the receiver. sender and ignored by the receiver.
Multicast-Flow TLV: Multicast-Flow TLV:
An instance of the Multicast-Flow TLV (Section 5.11) An instance of the Multicast-Flow TLV (Section 5.11)
specifying the flow to be added or deleted. The Multicast- specifying the flow to be added or deleted. The Multicast-
Flow TLV MUST be omitted if the Command Code has value Flow TLV MUST be omitted if the Command Code has value
"Delete All" (0x03). "Delete All" (3).
Other embedded TLV: Other embedded TLV:
No other embedded TLVs are currently specified within the No other embedded TLVs are currently specified within the
Multicast Replication Control message/Command TLV. Multicast Replication Control message/Command TLV.
Unrecognized embedded TLVs SHOULD be silently discarded. However, see the description of the Multicast Admission
Control message (Section 4.4). Unrecognized embedded TLVs
SHOULD be silently discarded.
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 Source-Specific
192.0.2.1, 233.252.0.2, to 192.0.2.2, 233.252.0.3 on the Target Multicast (SSM) flows 2001:DB8::1, FF34::2, to 2001:DB8::2, FF34::3
identified by the "Access Loop Circuit ID": on the Target 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 (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub |MessageType=144| 0x02 | Result Code | | Version | MsgType=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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Access Loop Circuit ID ~ ~ Access Loop Circuit ID ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Command TLV | Command-TLV Length = 0x0014 | | Type = Command TLV | Command-TLV Length = 0x0014 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=0x02 |Acctg = 0x00 | Reserved = 0x0000 | | Cmd Code=2 |Acctg = 0x00 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = Multicast-Flow | TLV Length = 0x000C | |TLV Type = Multicast-Flow | TLV Length = 0x000C |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |AddrFam = 0x01 | Reserved = 0x0000 | |Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address: 233.252.0.2 | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ ~ Multicast Group Address ~
| Source Address = 192.0.2.1 | | = FF34::2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Command-TLV | Command-TLV Length = 0x0014 | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Source Address ~
| Cmd Code=0x01 |Acctg = 0x01 | Reserved = 0x0000 | | = 2001:DB8::1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = Multicast-Flow | TLV Length = 0x000C | | Type = Command-TLV | Command-TLV Length = 0x0014 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |AddrFam = 0x01 | Reserved = 0x0000 | | Cmd Code=1 |Acctg = 0x01 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = 233.252.0.3 | |TLV Type = Multicast-Flow | TLV Length = 0x000C |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Address = 192.0.2.2 | |Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = FF34::3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Address = 2001:DB8::2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
| |
~ Multicast Group Address ~
| = FF34::3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Source Address ~
| = 2001:DB8::2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.3.1. Sender Behaviour 4.3.1. Sender Behaviour
The NAS MAY issue a Multicast Replication Control message to the AN The NAS MAY issue a Multicast Replication Control message to the AN
to convey one or more directives to add (join) or delete (leave) one to convey one or more directives to add (join) or delete (leave) one
or more multicast flows. or more multicast flows.
The NAS MAY send this message on its own initiative to support the The NAS MAY send this message on its own initiative to support the
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
skipping to change at page 24, line 10 skipping to change at page 23, line 42
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 Result Code value for the error as described below. The appropriate Result Code value for the
response is 18 (0x012) "Insufficient resources". response is 0x013 "Out of 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 Result Code field is set to 0x000, and the to Success (0x3), the Result Code field is set to 0x000, and the
Transaction Identifier field is copied from the Multicast Replication Transaction Identifier field is copied from the Multicast Replication
Control message. The body of the response MAY be empty or MAY be Control message. The body of the response MAY be empty or MAY be
copied from the Multicast Replication Control message. copied from the Multicast Replication Control message.
skipping to change at page 24, line 39 skipping to change at page 24, line 23
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 Result Code values beyond those identifies the following new Result Code values beyond those
specified in [RFC6320], which MAY be used in a Generic Response sent specified in [RFC6320], which MAY be used in a Generic Response sent
in reply to a Multicast Replication Control message: in reply to a Multicast Replication Control message:
100 Command error. This SHOULD be reported for the case that an 0x64 Command error.
invalid command code has been received.
101 Bad flow address. This SHOULD be reported for the following Where detected: ANCP agent at the AN.
cases:
* unsupported address family; Further description: an invalid command code has been received.
* source address present for an ASM flow, or absent for an SSM Required additional information in the message: see below.
flow.
102 Multicast flow does not exist. This SHOULD be reported if the Target: ANCP agent at the NAS.
NAS attempts to delete a flow that is not enabled.
Action RECOMMENDED for the receiving ANCP agent: Correct the
error and re-send the request, if possible. Otherwise, report
the error to the control application with an indication of the
erroneous information associated with the invalid TLV(s).
0x65 Invalid flow address.
Where detected: ANCP agent at the AN.
Further description: either inconsistent flow address
information has been provided or the address family is
unsupported.
Required additional information in the message: see below.
Target: ANCP agent at the NAS.
Action RECOMMENDED for the receiving ANCP agent: correct the
error and re-send the request, if possible. Otherwise, report
the error to the control application with an indication of the
erroneous information associated with the invalid TLV(s).
0x66 Multicast flow does not exist.
Where detected: control application at the AN.
Further description: the NAS has attempted to delete a flow
that is not active on the given access line.
Required additional information in the message: see below.
Target: control application at the NAS.
Action RECOMMENDED for the receiving ANCP agent: report the
error to the control application with an indication of the
erroneous information associated with the invalid TLV(s).
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 Result Code values Control message and containing one of the above Result Code values
MUST include a Status-Info TLV which includes one or two embedded MUST include a Status-Info TLV which includes one or two embedded
TLVs as 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 Result Code value used to report more details than implied by the Result Code value
in the message header. For example, the Result Code value could in the message header. For example, the Result Code value could
be 101 and the Error Message field could contain the text: "Source be 0x65 and the Error Message field could contain the text:
address present for ASM flow". "Source 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 25, line 47 skipping to change at page 26, line 12
appear once and only once in the Multicast Admission Control appear once and only once in the Multicast Admission Control
message. It is encoded as specified in [RFC6320] or extensions message. It is encoded as specified in [RFC6320] or extensions
and identifies the AN port subject to the request for admission or and identifies the AN port subject to the request for admission or
release. release.
o Command TLV: The Command TLV is defined in [RFC6320]. It MUST be o Command TLV: The Command TLV is defined in [RFC6320]. It MUST be
present. If it appears more than once, only the first instance is present. If it appears more than once, only the first instance is
considered meaningful in the present version of this specification considered meaningful in the present version of this specification
and the other instances are ignored. and the other instances are ignored.
Informative note: Note:
In the future, the specification of the Admission Control message In the future, the specification of the Admission Control message
may be extended to allow transport of more than a single directive may be extended to allow transport of more than a single directive
(e.g. to carry both a leave from one group and a join to another (e.g., to carry both a leave from one group and a join to another
group for the same Target). It is expected that this would group for the same Target). It is expected that this would
support a similar notion of strict sequenced processing as support a similar notion of strict sequenced processing as
currently defined for handling multiple directives in the currently defined for handling multiple directives in the
Multicast Replication Control message whereby all directives Multicast Replication Control message whereby all directives
following the first directive that can not be executed are not following the first directive that can not be executed are not
executed either. When the strict sequenced processing of the executed either. When the strict sequenced processing of the
directives is not required the directives are distributed across directives is not required the directives are distributed across
separate messages. separate messages.
The Command TLV has the same contents as were described above for the The Command TLV has the same contents as were described above for the
skipping to change at page 26, line 30 skipping to change at page 26, line 44
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 3.6.1.6 of [RFC6320] . unique value, as described in Section 3.6.1.6 of [RFC6320].
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 "1 - Add" when the message
o the Command Code field MUST be set to "0x01 - Add" when the conveys a Join , to "2 - Delete" when the message conveys a Leave
message conveys a Join , to "0x02 - Delete" when the message and to "3 - Delete All" when the message conveys a Leave of all
conveys a Leave and to "0x03 - Delete All" when the message channels (on the target);
conveys a Leave of all channels (on the target);
o The Multicast-Flow TLV within the Command TLV identifies the o The Multicast-Flow TLV within the Command TLV identifies the
multicast flow subject to the request for admission or release. multicast flow subject to the request for admission or release.
When the Command Code is 0x03, the Multicast-Flow TLV is When the Command Code is 3, the Multicast-Flow TLV is meaningless
meaningless and MUST be omitted. and MUST be omitted.
o the Request-Source-IP embedded TLV MAY be included by the AN to o the Request-Source-IP embedded TLV MAY be included by the AN to
convey the IP address of the sender of the join/leave message convey the IP address of the sender of the join/leave message
(e.g. IGMP/MLD Join/Leave) that triggered the AN to include the (e.g., IGMP/MLD Join/Leave) that triggered the AN to include the
corresponding Command TLV in the Admission Control message. If it corresponding Command TLV in the Admission Control message. If it
appears more than once, only the first instance is considered appears more than once, only the first instance is considered
meaningful and the other instances are ignored. meaningful and the other instances are ignored.
o the Request-Source-MAC embedded TLV MAY be included by the AN to o the Request-Source-MAC embedded TLV MAY be included by the AN to
convey the MAC address of the sender of the join/leave message convey the MAC address of the sender of the join/leave message
(e.g. IGMP/MLD Join/Leave) that triggered the AN to include the (e.g., IGMP/MLD Join/Leave) that triggered the AN to include the
corresponding Command TLV in the Admission Control message. If it corresponding Command TLV in the Admission Control message. If it
appears more than once, only the first instance is considered appears more than once, only the first instance is considered
meaningful and the other instances are ignored. meaningful and the other instances are ignored.
4.4.2. Receiver Behaviour 4.4.2. Receiver Behaviour
On receipt of an Multicast Admission Control message, the NAS: On receipt of an Multicast Admission Control message, the NAS:
o MUST ignore the Result field; o MUST ignore the Result field;
o if the directive in the Multicast Admission Control message is o if the directive in the Multicast Admission Control message is "2
"0x02 - Delete" or "0x03 - Delete All" and is processed correctly - Delete" or "3 - Delete All" and is processed correctly by the
by the NAS, the NAS MUST NOT generate any ANCP message in response NAS, the NAS MUST NOT generate any ANCP message in response to the
to the Multicast Admission Control message; Multicast Admission Control message;
o if the directive in the Multicast Admission Control message is o if the directive in the Multicast Admission Control message is "1
"0x01 - Add" and is accepted by the NAS, the NAS MUST generate a - Add" and is accepted by the NAS, the NAS MUST generate a
Multicast Replication Control in response to the Multicast Multicast Replication Control in response to the Multicast
Admission Control message. The Multicast Replication Control Admission Control message. The Multicast Replication Control
message: message:
* MUST contain a Result set to Nack (0x1); * MUST contain a Result set to Nack (0x1);
* MUST contain a Transaction ID generated by the NAS (distinct * MUST contain a Transaction ID with a unique value, as described
non-zero, and linearly incremented by NAS for each request per in Section 3.6.1.6 of [RFC6320];
adjacency);
* MUST contain the directive as accepted by the NAS. The NAS MAY * MUST contain the directive as accepted by the NAS. The NAS MAY
modify the Accounting field if flow accounting is required. modify the Accounting field if flow accounting is required.
o if the directive in the Multicast Admission Control message is o if the directive in the Multicast Admission Control message is "1
"0x01 - Add", is processed correctly but not accepted by the NAS - Add", is processed correctly but not accepted by the NAS (i.e.,
(i.e. it does not pass the admission control or conditional access it does not pass the admission control or conditional access
check), the NAS MAY generate a Multicast Replication Control check), the NAS MAY generate a Multicast Replication Control
message in response to the Multicast Admission Control message. message in response to the Multicast Admission Control message.
This optional message can be used by the AN to maintain statistics This optional message can be used by the AN to maintain statistics
about admission control rejections. about admission control rejections.
In the future, the AN may be able to notify the subscriber that In the future, the AN may be able to notify the subscriber that
the request was rejected (e.g. using the request was rejected (e.g., using
[I-D.morin-mboned-igmpmld-error-feedback]). [I-D.morin-mboned-igmpmld-error-feedback]).
When used in this situation, the Multicast Replication Control When used in this situation, the Multicast Replication Control
message: message:
* MUST contain a Result set to 0x0; * MUST contain a Result set to 0x0;
* MUST contain a Transaction ID generated by the NAS (distinct * MUST contain a Transaction ID with a unique value, as described
non-zero, and linearly incremented by NAS for each request per in Section 3.6.1.6 of [RFC6320];
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 "4 -
Admission Control Reject", "0x05 - Conditional Access Reject", Admission Control Reject", "5 - Conditional Access Reject", or
or "0x06 - Admission Control and Conditional Access Reject". "6 - Admission Control and Conditional Access Reject" as
applicable.
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 4.2 of [RFC6320]) with Response message (defined in Section 4.2 of [RFC6320]) with
appropriate content indicating the reason for the failure. appropriate content indicating the 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
skipping to change at page 29, line 20 skipping to change at page 29, line 34
to keep their respective views of the current amount of delegated to keep their respective views of the current amount of delegated
bandwidth synchronized. bandwidth synchronized.
Because the values are totals rather than desired increments/ Because the values are totals rather than desired increments/
decrements, the relationship between the required amount and the decrements, the relationship between the required amount and the
preferred amount will differ depending on whether the Bandwidth preferred amount will differ depending on whether the Bandwidth
Reallocation Request message is issued by the NAS or the AN. Reallocation Request message is issued by the NAS or the AN.
o If the NAS is making the request, the preferred amount MUST be o If the NAS is making the request, the preferred amount MUST be
less than or equal to the required amount. The required amount less than or equal to the required amount. The required amount
MUST be less than the currently amount of delegated bandwidth. MUST be less than the current amount of delegated bandwidth.
o If the AN is making the request, the preferred amount MUST be o If the AN is making the request, the preferred amount MUST be
greater than or equal to the required amount. The required amount greater than or equal to the required amount. The required amount
MUST be greater than the currently amount of delegated bandwidth. MUST be greater than the current amount of delegated bandwidth.
4.5.2. Receiver Behaviour 4.5.2. Receiver Behaviour
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 the Bandwidth Transfer message MUST be set to Success (0x3), the
Result Code field MUST be set to 0x000, and the Bandwidth-Allocation Result Code field MUST be set to 0x000, and the Bandwidth-Allocation
TLV (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 Result Code field MUST be message MUST be set to Failure (0x4), the Result Code field MUST be
set to 0x000, and the Bandwidth Allocation TLV MUST contain the value set to 0x000, and the Bandwidth Allocation TLV MUST contain the value
of the currently allocated amount of delegated bandwidth as the of the currently allocated amount of delegated bandwidth as the
skipping to change at page 30, line 33 skipping to change at page 30, line 47
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
Result Code value set to 105 "Bandwidth request conflict". Result Code value set to 0x68 "Inconsistent views of delegated
bandwidth amount" or 0x69 "Bandwidth request conflict" as
applicable. (See below for more information).
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
skipping to change at page 31, line 17 skipping to change at page 31, line 34
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 Result 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
Result Code values by their nature MUST only be used when the error Result Code values by their nature MUST only be used when the error
is being reported in a Bandwidth Transfer message rather than a is being reported in a Bandwidth Transfer message rather than a
Generic Response message. Generic Response message.
103 invalid preferred bandwidth amount. This indicates that the 0x67 Invalid preferred bandwidth amount.
preferred and required amounts of bandwidth in the TLV do not have
the numerical relationship described in the previous section.
104 inconsistent views of delegated bandwidth amount. This will Where detected: control application at the receiver of the
appear only in a Bandwidth Transfer message from the NAS to the AN Bandwidth Reallocation Request message.
in the case where the NAS has an outstanding Bandwidth
Reallocation Request. The recommended procedure for recovery is
described in Section 4.6.2.
105 bandwidth request conflict. The NAS has rejected the AN's Further description: the preferred and required amounts of
request for more bandwidth because the NAS has an outstanding bandwidth in the TLV do not have the numerical relationship
bandwidth request. described above.
Required additional information in the message: as described
above.
Target: control application at the sender of the Bandwidth
Reallocation Request message.
Action RECOMMENDED for the receiving ANCP agent: report the
error to the control application with the returned value of the
Bandwidth-Allocation TLV. See also Section 4.6.2.2.
0x68 Inconsistent views of delegated bandwidth amount.
Where detected: control application at the NAS.
Further description: the NAS has an outstanding Bandwidth
Reallocation Request, so it is rejecting a similar request from
the AN. In the AN request, the required amount was less than
the NAS's view of the current amount of delegated bandwidth.
Required additional information in the message: as described
above.
Target: control application at the AN.
Action RECOMMENDED for the receiving ANCP agent: report the
error to the AN control application with the returned value of
the Bandwidth-Allocation TLV. See also Section 4.6.2.2.
0x69 Bandwidth request conflict.
Where detected: control application at the NAS.
Further description: the NAS has an outstanding Bandwidth
Reallocation Request, so it is rejecting a similar, valid
request from the AN.
Required additional information in the message: as described
above.
Target: control application at the AN.
Action RECOMMENDED for the receiving ANCP agent: report the
error to the AN control application with the returned value of
the Bandwidth-Allocation TLV. See also Section 4.6.2.2.
4.6. Bandwidth Transfer Message 4.6. Bandwidth Transfer Message
The Bandwidth Transfer message is used to transfer video bandwidth The Bandwidth Transfer message is used to transfer video bandwidth
from the sender to the peer for a specific access line. This message from the sender to the peer for a specific access line. This message
MAY be sent either from the AN or from the NAS. As described in the MAY be sent either from the AN or from the NAS. As described in the
previous section, it is the required response to a valid Bandwidth previous section, it is the required response to a valid Bandwidth
Reallocation Request message. Reallocation Request message.
The Bandwidth Transfer message MAY also be used to transfer bandwidth The Bandwidth Transfer message MAY also be used to transfer bandwidth
skipping to change at page 33, line 8 skipping to change at page 34, line 17
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 Result Code field equal to 104 field equal to Failure (0x4) and a Result Code field equal to 0x68
"Inconsistent views of delegated bandwidth amount" or 105 "Bandwidth "Inconsistent views of delegated bandwidth amount" or 0x69 "Bandwidth
request conflict". If Result Code value 104 is received, the AN MUST request conflict". If Result Code value 0x68 is received, the AN
issue a Delegated Bandwidth Query Request message to determine the MUST issue a Delegated Bandwidth Query Request message to determine
NAS's current view of the amount of delegated bandwidth. The AN MUST the NAS's current view of the amount of delegated bandwidth. The AN
update its own view based on the value returned in the Delegated MUST update its own view based on the value returned in the Delegated
Bandwidth Query Response. If Result Code value 105 is received, the Bandwidth Query Response. If Result Code value 0x69 is received, the
AN 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 Result Code values indicate a race condition where the AN The two Result Code values indicate a race condition where the AN
may 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
skipping to change at page 34, line 23 skipping to change at page 35, line 32
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 Result Code field MUST be set to the value that indicates (0x3). The Result Code field MUST be set to the value that indicates
the nature of the error (e.g., 4 "Unrecognized target"). The the nature of the error (e.g., 0x500 "One or more of the specified
Transaction-Id field MUST be copied from the request. The body of ports do not exist"). The Transaction-Id field MUST be copied from
the response MUST contain the Target TLV copied from the request. the request. The body of the response MUST contain the Target TLV
This MAY be followed by a Status-Info TLV giving further information copied from the request. This MAY be followed by a Status-Info TLV
about the error. giving further information 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:
o the Target TLV, copied from the request; o the Target TLV, copied from the request;
o a Bandwidth-Allocation TLV, giving the responder's view of the o a Bandwidth-Allocation TLV, giving the responder's view of the
skipping to change at page 36, line 25 skipping to change at page 37, line 37
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
and every port of the AN. access port of the AN.
To retrieve the AN's view of which multicast flows are currently To retrieve the AN's view of which multicast flows are currently
active on a given port of the AN, the NAS MUST include a Target TLV active on a given port of the AN, the NAS MUST include a Target TLV
in the Multicast Flow Query Request payload identifying that port. in the Multicast Flow Query Request payload identifying that port.
The Target TLV is encoded as specified in [RFC6320]. The Target TLV is encoded as specified in [RFC6320].
To retrieve the AN's view of the ports currently receiving a given To retrieve the AN's view of the ports currently receiving a given
multicast flow, the NAS MUST include a Multicast-Flow TLV in the multicast flow, the NAS MUST include a Multicast-Flow TLV in the
Multicast Flow Query Request payload identifying that flow. The Multicast Flow Query Request payload identifying that flow. The
Multicast-Flow TLV is encoded as specified in Section 5.11. Multicast-Flow TLV is encoded as specified in Section 5.11.
skipping to change at page 37, line 23 skipping to change at page 38, line 36
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.
The Target TLVs MUST appear in the response from the AN in the same The Target TLVs MUST appear in the response from the AN in the same
order as in the query from the NAS. order as in the query from the NAS.
If the Multicast Flow Query Request contained one (or more) If the Multicast Flow Query Request contained one (or more)
Multicast-Flow TLVs, the AN MUST include, for each of these Multicast-Flow TLVs, the AN MUST include, for each of these
Multicast-Flow TLVs, the following set of TLVs: Multicast-Flow TLVs, the following set of TLVs:
o Multicast-Flow TLV. This MUST be identical to the Multicast- Flow o Multicast-Flow TLV. This MUST be identical to the Multicast-Flow
TLV in the received Multicast Flow Query Request message. TLV in the received Multicast Flow Query Request message.
o Target TLV(s). The Target TLV MUST appear once per AN port on o Target TLV(s). The Target TLV MUST appear once per AN port on
which the multicast flow identified in the preceding Multicast which the multicast flow identified in the preceding Multicast-
Flow TLV is active. Flow TLV is active.
The Multicast-Flow TLVs MUST appear in the response from the AN in The Multicast-Flow TLVs MUST appear in the response from the AN in
the same order as in the query from the NAS. the same order as in the query from the NAS.
If the Multicast Flow Query Request contained no Target TLV and no If the Multicast Flow Query Request contained no Target TLV and no
Multicast Flow TLV, the AN MUST include, for each AN port currently Multicast Flow TLV, the AN MUST include, for each AN port currently
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.
skipping to change at page 39, line 19 skipping to change at page 41, line 19
5.1. Multicast-Service-Profile TLV 5.1. Multicast-Service-Profile TLV
This document defines the new Multicast-Service-Profile TLV. This document defines the new Multicast-Service-Profile TLV.
The Multicast-Service-Profile TLV MAY be included in a Provisioning The Multicast-Service-Profile TLV MAY be included in a Provisioning
message as specified in Section 4.1. message as specified in Section 4.1.
The Multicast-Service-Profile TLV is illustrated in Figure 6. It The Multicast-Service-Profile TLV is illustrated in Figure 6. It
consists of a TLV header encapsulating a single instance of the consists of a TLV header encapsulating a single instance of the
Multicast-Service- Profile-Name TLV and one or more instances of the Multicast-Service-Profile-Name TLV and one or more instances of the
List-Action TLV. List-Action TLV.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = Mcast Serv Profile | TLV Length | |TLV Type = Mcast Serv Profile | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast-Service-Profile-Name TLV | | Multicast-Service-Profile-Name TLV |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 39, line 44 skipping to change at page 41, line 44
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| List-Action TLV | | List-Action TLV |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Multicast-Service-Profile TLV Figure 6: Multicast-Service-Profile TLV
The Multicast-Service-Profile TLV has the following fields: The Multicast-Service-Profile TLV has the following fields:
o The Multicast-Service-Profile TLV Type is 0x13. o The Multicast-Service-Profile TLV Type is 0x0013.
o The TLV length is determined by the contents following the TLV o The TLV length is determined by the contents following the TLV
header. header.
o The Multicast-Service-Profile-Name TLV is described in o The Multicast-Service-Profile-Name TLV is described in
Section 5.2. The Multicast-Service-Profile-Name TLV MUST contain Section 5.2. The Multicast-Service-Profile-Name TLV MUST contain
an identifier which is unique over all profiles provisioned to the an identifier which is unique over all profiles provisioned to the
same AN partition. This identifier will be used to refer to the same AN partition. This identifier will be used to refer to the
profile when activating it for a given target within a Port profile when activating it for a given target within a Port
Management message (see Section 4.2). Management message (see Section 4.2).
o The List-Action TLV is described in Section 5.3. The List-Action o The List-Action TLV is described in Section 5.3. The List-Action
TLV(s) provide the content of a newly defined multicast service TLV(s) provide the content of a newly defined multicast service
profile or modify the existing content. If more than one List- profile or modify the existing content. If more than one List-
Action TLV is present, the order of the TLVs may be significant, Action TLV is present, the order of the TLVs may be significant,
since List- Action TLVs are processed in the order in whch they since List-Action TLVs are processed in the order in whch they
appear. appear.
5.2. Multicast-Service-Profile-Name TLV 5.2. Multicast-Service-Profile-Name TLV
The Multicast-Service-Profile-Name TLV carries the identifier of a The Multicast-Service-Profile-Name TLV carries the identifier of a
multicast service profile provisioned on the AN. It is illustrated multicast service profile provisioned on the AN. It is illustrated
in Figure 7. in Figure 7.
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
skipping to change at page 40, line 33 skipping to change at page 42, line 33
|TLV Type = MSP Name | TLV Length | |TLV Type = MSP Name | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast service profile identifier | | Multicast service profile identifier |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Multicast-Service-Profile-Name TLV Figure 7: Multicast-Service-Profile-Name TLV
The Multicast-Service-Profile-Name TLV has the following fields: The Multicast-Service-Profile-Name TLV has the following fields:
o The Multicast-Service-Profile-Name TLV Type is 0x18. o The Multicast-Service-Profile-Name TLV Type is 0x0018.
o TLV Length: up to 255 octets. o TLV Length: up to 255 octets.
o Multicast service profile identifier: an opaque sequence of bits o Multicast service profile identifier: an opaque sequence of octets
identifying a specific multicast service profile. identifying a specific multicast service profile.
The identifier could have the form of human-readable text or an The identifier could have the form of human-readable text or an
arbitrary binary value, depending on the operator's practices. arbitrary binary value, depending on the operator's practices.
5.3. List-Action TLV 5.3. List-Action TLV
The List-Action TLV identifies multicast flows to be added to or The List-Action TLV identifies multicast flows to be added to or
removed from a list of White-, Black-, or Grey-listed flows. It is removed from a list of white-, black-, or grey-listed flows. It is
meaningful only in association with a Multicast-Service-Profile-Name meaningful only in association with a Multicast-Service-Profile-Name
TLV identifying the profile to which the List-Action TLV applies. TLV identifying the profile to which the List-Action TLV applies.
Such an association can be achieved by placing both TLVs in the same Such an association can be achieved by placing both TLVs in the same
base message payload or as embedded TLVs of another TLV such as the base message payload or as embedded TLVs of another TLV such as the
Multicast-Service-Profile. The List-Action TLV is shown in Figure 8. Multicast-Service-Profile. The List-Action TLV is shown in Figure 8.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = List-Action TLV | TLV Length | | TLV Type = List-Action TLV | TLV Length |
skipping to change at page 41, line 29 skipping to change at page 43, line 29
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast flow fields | | Multicast flow fields |
...... ......
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8: List-Action TLV Figure 8: List-Action TLV
The List-Action TLV contains the following fields: The List-Action TLV contains the following fields:
o The List-Action TLV Type is 0x21. o The List-Action TLV Type is 0x0021.
o TLV Length: length of the subsequent contents. o TLV Length: length of the subsequent contents.
o Operation: operation to be performed upon the White, Black, or o Operation: operation to be performed upon the white, black, or
Grey list identified by the List Type field within the profile grey list identified by the List Type field within the profile
identified by the associated Multicast-Service-Profile-Name identified by the associated Multicast-Service-Profile-Name
embedded TLV. The possible values are: embedded TLV. The possible values are:
* Add (0x01): the multicast flow fields are to be added to the * Add (0x01): the multicast flow fields are to be added to the
list. list.
* Delete (0x02): the multicast flow fields are to be removed from * Delete (0x02): the multicast flow fields are to be removed from
the list. Each multicast flow field in the List-Action MUST the list. Each multicast flow field in the List-Action MUST
match exactly an existing entry in the list concerned. Thus to match exactly an existing entry in the list concerned. Thus to
remove part of the range provided by a wildcarded list entry, remove part of the range provided by a wildcarded list entry,
skipping to change at page 43, line 9 skipping to change at page 45, line 9
The prefix length has its usual meaning. It is the number of most- The prefix length has its usual meaning. It is the number of most-
significant bits specified within the corresponding prefix. The significant bits specified within the corresponding prefix. The
prefix length MAY vary from 0 to 32 in the IPv4 sub-list, and from 0 prefix length MAY vary from 0 to 32 in the IPv4 sub-list, and from 0
to 128 in the IPv6 sub-list. to 128 in the IPv6 sub-list.
A value of 0x00 for either the Group PrefLen (prefix length) or the A value of 0x00 for either the Group PrefLen (prefix length) or the
Source PrefLen indicates that any value of the corresponding address Source PrefLen indicates that any value of the corresponding address
will match (wild card). If the value 0x00 is provided for a will match (wild card). If the value 0x00 is provided for a
particular prefix length, the corresponding prefix MUST be omitted particular prefix length, the corresponding prefix MUST be omitted
from the field contents. In particular, a value of 0x00 for the from the field contents.
Source PrefLen indicates an ASM multicast entry, and the Source
Prefix will be absent.
The length of a Source or Group Prefix field is equal to (PrefLen + The length of a Source or Group Prefix field is equal to (PrefLen +
7)/8 octets, truncated to the nearest integer. Unused bits at the 7)/8 octets, truncated to the nearest integer. Unused bits at the
end of the prefix MUST be set to zeroes. end of the prefix MUST be set to zeroes.
5.4. Sequence-Number TLV 5.4. Sequence-Number TLV
The Sequence-Number TLV conveys a sequence number of some sort. The The Sequence-Number TLV conveys a sequence number of some sort. The
specific meaning of the sequence number is message-specific. Within specific meaning of the sequence number is message-specific. Within
this specification, the Sequence-Number TLV is used as a embedded TLV this specification, the Sequence-Number TLV is used as a embedded TLV
within a Status-Info TLV, in a Generic Response reporting a failed in a Status-Info TLV, in a Generic Response reporting a failed
command within a Multicast Replication Control or Multicast Admission command in a Multicast Replication Control or Multicast Admission
Request message. It identifies the sequence number within the Request message. It identifies the sequence number within the
message of the command that failed. message of the command that failed.
The Sequence-Number TLV has the format shown in Figure 10. The Sequence-Number TLV has the format shown in Figure 10.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = Sequence-Number | TLV Length = 4 | |TLV Type = Sequence-Number | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence number | | Sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 10: Sequence-Number TLV Figure 10: Sequence-Number TLV
The Sequence-Number TLV has the following fields: The Sequence-Number TLV has the following fields:
o The Sequence-Number TLV Type is 0x22. o The Sequence-Number TLV Type is 0x0022.
o TLV length is 0x0004. o TLV length is 0x0004.
o Sequence number: the sequence number of a specific entity within a o Sequence number: the sequence number of a specific entity within a
series, where numbering starts from 1 for the first entity in the series, where numbering starts from 1 for the first entity in the
series. Represented as a 32-bit binary number, most significant series. Represented as a 32-bit binary number, most significant
bit first. bit first.
5.5. Bandwidth-Allocation TLV 5.5. Bandwidth-Allocation TLV
skipping to change at page 44, line 24 skipping to change at page 46, line 18
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = BW-Allocation | TLV Length = 4 | |TLV Type = BW-Allocation | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delegated amount (kbits/s) | | Delegated amount (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11: The Bandwidth-Allocation TLV Figure 11: The Bandwidth-Allocation TLV
The Bandwidth-Allocation TLV has the following fields: The Bandwidth-Allocation TLV has the following fields:
o The Bandwidth-Allocation TLV Type is 0x15. o The Bandwidth-Allocation TLV Type is 0x0015.
o TLV length is 4. o TLV length is 4.
o Delegated amount: the bandwidth amount delegated to the AN for o Delegated amount: the bandwidth amount delegated to the AN for
admission of multicast video on a given port, kilobits per second. admission of multicast video on a given port, kilobits per second.
Presented as a 32-bit binary value, most significant bit first. Presented as a 32-bit binary value, most significant bit first.
5.6. White-List-CAC TLV 5.6. White-List-CAC TLV
The White-List-CAC TLV is used to indicate that the NAS wishes the AN The White-List-CAC TLV is used to indicate that the NAS wishes the AN
to do admission control for White-listed flows. Details on when the to do admission control for white-listed flows. Details on when the
White-List-CAC TLV may be provisioned are specified in Section 6. White-List-CAC TLV may be provisioned are specified in Section 6.
The White- List-CAC TLV is illustrated in Figure 12. The White-List-CAC TLV is illustrated in Figure 12.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = White-List-CAC | TLV Length = 0 | |TLV Type = White-List-CAC | TLV Length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12: White-List-CAC TLV Figure 12: White-List-CAC TLV
The White-List-CAC TLV contains the following fields: The White-List-CAC TLV contains the following fields:
o The White-List-CAC TLV Type is 0x24. o The White-List-CAC TLV Type is 0x0024.
o TLV length is 0, since the TLV contains no data other than the TLV o TLV length is 0, since the TLV contains no data other than the TLV
header. header.
5.7. MRepCtl-CAC TLV 5.7. MRepCtl-CAC TLV
The MRepCtl-CAC TLV is used to indicate that the NAS wishes the AN to The MRepCtl-CAC TLV is used to indicate that the NAS wishes the AN to
do admission control for flows added by the Multicast Replication do admission control for flows added by the Multicast Replication
Control message. Details on when the MRepCtl-CAC TLV may be Control message. Details on when the MRepCtl-CAC TLV may be
provisioned are specified in Section 6. The MRepCtl-CAC TLV is provisioned are specified in Section 6. The MRepCtl-CAC TLV is
skipping to change at page 45, line 23 skipping to change at page 47, line 23
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = MRepCtl-CAC | TLV Length = 0 | |TLV Type = MRepCtl-CAC | TLV Length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 13: MRepCtl-CAC TLV Figure 13: MRepCtl-CAC TLV
The MRepCtl-CAC TLV contains the following fields: The MRepCtl-CAC TLV contains the following fields:
o The MRepCtl-CAC TLV Type is 0x25. o The MRepCtl-CAC TLV Type is 0x0025.
o TLV length is 0, since the TLV contains no data other than the TLV o TLV length is 0, since the TLV contains no data other than the TLV
header. header.
5.8. Bandwidth-Request TLV 5.8. Bandwidth-Request TLV
The Bandwidth-Request TLV is used to request an adjustment of the The Bandwidth-Request TLV is used to request an adjustment of the
total amount of video bandwidth allocated to the AN for multicast total amount of video bandwidth allocated to the AN for multicast
admission control for a given line. The "Required amount" field admission control for a given line. The "Required amount" field
indicates the minimum adjustment required to meet the request. The indicates the minimum adjustment required to meet the request. The
skipping to change at page 46, line 7 skipping to change at page 48, line 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required amount (kbits/s) | | Required amount (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Preferred amount (kbits/s) | | Preferred amount (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 14: The Bandwidth-Request TLV Figure 14: The Bandwidth-Request TLV
The Bandwidth-Request TLV has the following fields: The Bandwidth-Request TLV has the following fields:
o The Bandwidth-Request TLV Type is 0x16. o The Bandwidth-Request TLV Type is 0x0016.
o The TLV length is 8 octets. o The TLV length is 8 octets.
o Required amount: the minimum or maximum amount, depending on o Required amount: the minimum or maximum amount, depending on
whether the sender is the AN or the NAS respectively, of delegated whether the sender is the AN or the NAS respectively, of delegated
video bandwidth that is being requested, in kilobits per second. video bandwidth that is being requested, in kilobits per second.
Presented as a 32-bit binary value, most significant bit first. Presented as a 32-bit binary value, most significant bit first.
o Preferred amount: the preferred amount of delegated video o Preferred amount: the preferred amount of delegated video
bandwidth that is being requested, in kilobits per second. bandwidth that is being requested, in kilobits per second.
skipping to change at page 46, line 38 skipping to change at page 48, line 38
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = Request-Source-IP | TLV length = 4 or 16 | | TLV Type = Request-Source-IP | TLV length = 4 or 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Address | | Unicast Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 15: Request-Source-IP TLV Figure 15: Request-Source-IP TLV
The Request-Source-IP TLV contains the following fields: The Request-Source-IP TLV contains the following fields:
o The Request-Source-IP TLV Type is 0x92. o The Request-Source-IP TLV Type is 0x0092.
o TLV length is 4 for an IPv4 address or 16 for an IPv6 address. o TLV length is 4 for an IPv4 address or 16 for an IPv6 address.
o Unicast address: IP address of the source of a multicast flow join o Unicast address: IP address of the source of a multicast flow join
request, in network byte order. request, in network byte order.
5.10. Request-Source-MAC TLV 5.10. Request-Source-MAC TLV
The Request-Source-MAC TLV provides the MAC address of the entity The Request-Source-MAC TLV provides the MAC address of the entity
that originated a specific request to join or leave a multicast that originated a specific request to join or leave a multicast
skipping to change at page 47, line 19 skipping to change at page 49, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+- IEEE MAC Address +-+-+-+ +-+-+- IEEE MAC Address +-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 16: Request-Source-MAC TLV Figure 16: Request-Source-MAC TLV
The Request-Source-MAC TLV contains the following fields: The Request-Source-MAC TLV contains the following fields:
o The Request-Source-MAC TLV Type is 0x93. o The Request-Source-MAC TLV Type is 0x0093.
o TLV length is either 6 octets (MAC-48 or EUI-48) or 8 octets o TLV length is either 6 octets (MAC-48 or EUI-48) or 8 octets
(EUI-64). (EUI-64).
o IEEE MAC Address: MAC address of the device originating the o IEEE MAC Address: MAC address of the device originating the
request to join a multicast flow. Within the address, bytes and request to join a multicast flow. Within the address, bytes and
bits respectively shall be ordered from most to least significant, bits respectively shall be ordered from most to least significant,
consistently with [IEEE48] for MAC-48 and EUI-48, and with consistently with [IEEE48] for MAC-48 and EUI-48, and with
[IEEE64] for EUI-64. [IEEE64] for EUI-64.
skipping to change at page 48, line 5 skipping to change at page 50, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address | | Multicast Group Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
| Unicast Source Address (for SSM flows only) | | Unicast Source Address (for SSM flows only) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 17: Multicast-Flow TLV Figure 17: Multicast-Flow TLV
The Multicast-Flow TLV has the following fields: The Multicast-Flow TLV has the following fields:
o The Multicast-Flow TLV Type is 0x19. o The Multicast-Flow TLV Type is 0x0019.
o TLV Length: ranges from a minimum of 8 (for an ASM IPv4 flow) to o TLV Length: ranges from a minimum of 8 (for an ASM IPv4 flow) to
36 (for an IPv6 SSM flow. 36 (for an IPv6 SSM flow).
o Flow Type: 0x01 for Any Source Multicast (ASM), 0x02 for Specific- o Flow Type: 0x01 for Any Source Multicast (ASM), 0x02 for Source-
Source Multicast (SSM). Specific Multicast (SSM).
o Addr Family: address family of the multicast source and group o Addr Family: address family of the multicast source and group
addresses, encoded in accordance with the IANA PIM Address Family addresses, encoded in accordance with the IANA PIM Address Family
registry ([PIMreg]). 0x01 indicates IPv4, 0x02 indicates IPv6. registry ([PIMreg]). 0x01 indicates IPv4, 0x02 indicates IPv6.
o Reserved: MUST be set to 0x0000 by the sender and MUST be ignored o Reserved: MUST be set to 0x0000 by the sender and MUST be ignored
by the receiver. by the receiver.
One possible use for this field in the future is to indicate One possible use for this field in the future is to indicate
the presence of PIM Join attributes attached to the source the presence of PIM Join attributes attached to the source
skipping to change at page 49, line 7 skipping to change at page 51, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type=Report-Buffering-Time | TLV Length = 4 | |TLV Type=Report-Buffering-Time | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Buffering Time (ms) | | Buffering Time (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 18: Report-Buffering-Time TLV Figure 18: Report-Buffering-Time TLV
The Report-Buffering-Time TLV contains the following fields: The Report-Buffering-Time TLV contains the following fields:
o The Report-Buffering-Time TLV Type is 0x94. o The Report-Buffering-Time TLV Type is 0x0094.
o TLV length is 4 octets. o TLV length is 4 octets.
o Buffering Time is a 32-bit unsigned integer containing a time o Buffering Time is a 32-bit unsigned integer containing a time
value in ms. value in ms.
5.13. Committed-Bandwidth TLV 5.13. Committed-Bandwidth TLV
The Committed-Bandwidth TLV identifies an access line and provides The Committed-Bandwidth TLV identifies an access line and provides
the current amount of multicast bandwidth that the AN has committed the current amount of multicast bandwidth that the AN has committed
skipping to change at page 49, line 36 skipping to change at page 51, line 34
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+- Target TLV +-+-+-+ +-+-+- Target TLV +-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 19: Committed-Bandwidth TLV Figure 19: Committed-Bandwidth TLV
The Committed-Bandwidth TLV contains the following fields: The Committed-Bandwidth TLV contains the following fields:
o The Committed-Bandwidth TLV Type is 0x95. o The Committed-Bandwidth TLV Type is 0x0095.
o TLV length is 4 octets plus the length of the Target TLV including o TLV length is 4 octets plus the length of the Target TLV including
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 3.5 of [RFC6320] defines a capability negotiation mechanism Section 3.5 of [RFC6320] defines a capability negotiation mechanism
as well as a number of capabilities. This section defines five new as well as a number of capabilities. This section defines five new
capabilities in support of different modes of multicast operation: capabilities in support of different modes of multicast operation:
o NAS-initiated replication (capability type 0x03); o NAS-initiated replication (capability type 3);
o committed multicast bandwidth reporting (capability type 0x05); o committed multicast bandwidth reporting (capability type 5);
o conditional access with white and black lists (capability type o conditional access with white and black lists (capability type 6);
0x06);
o conditional access with grey lists (capability type 0x07); o conditional access with grey lists (capability type 7);
o bandwidth delegation (capability type 0x08). o bandwidth delegation (capability type 8).
The "Capability Data" field within the Capability TLV for all of The "Capability Data" field within the Capability TLV for all of
these capabilities is empty. All of these capabilities are these capabilities is empty. All of these capabilities are
independent of the access technology. independent of the access technology.
The remainder of this section consists of three sub-sections. The remainder of this section consists of three sub-sections.
Section 6.1 specifies the protocol elements that must be implemented Section 6.1 specifies the protocol elements that must be implemented
in order to support each capability. Section 6.2 specifies the in order to support each capability. Section 6.2 specifies the
procedures that apply to each capability on its own. Section 6.3 procedures that apply to each capability on its own. Section 6.3
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. The body of the message MUST contain a Status-Info TLV.
capability set"). The body of the message MUST contain a Status-Info See Sections 4.2 and 4.5 in [RFC6320] for more details.
TLV. See Sections 4.2 and 4.5 in [RFC6320] for more 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 In addition to the elements listed below, implementation of the
Target TLV (Section 4.3 of [RFC6320]) is REQUIRED for all of the
capabilities specified in this document.
6.1.1. Protocol Requirements For NAS-Initiated Replication
Table 1 specifies the protocol elements within Section 4 and Table 1 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the NAS-initiated Section 5 that MUST be implemented to support the NAS-initiated
replication multicast capability. replication multicast capability. Additionally, implementation of
the Multicast Replication Control message requires implementation of
the Command TLV (Section 4.4 of [RFC6320] with additional details in
Section 4.3 of this document).
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Section 4.1 | Provisioning message with MRepCtl-CAC TLV | | Section 4.1 | Provisioning message with MRepCtl-CAC TLV |
| | | | | |
| Section 4.2 | Port Management message with Bandwidth-Allocation | | Section 4.2 | Port Management message with Bandwidth-Allocation |
| | TLV. | | | TLV. |
| | | | | |
| Section 4.3 | Multicast Replication Control message | | Section 4.3 | Multicast Replication Control message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section 5.4 | Command Number TLV | | Section 5.4 | Sequence Number TLV |
| | |
| Section 5.5 | Bandwidth-Allocation TLV |
| | | | | |
| Section 5.7 | MRepCtl-CAC TLV | | Section 5.7 | MRepCtl-CAC TLV |
| | | | | |
| Section 5.11 | Multicast-Flow TLV | | Section 5.11 | Multicast-Flow TLV |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
Table 1: Protocol Requirements For NAS-initiated Replication Table 1: Protocol Requirements For NAS-Initiated Replication
6.1.2. Protocol Requirements For Committed Multicast Bandwidth 6.1.2. Protocol Requirements For Committed Multicast Bandwidth
Reporting Reporting
Table 2 specifies the protocol elements within Section 4 and Table 2 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the NAS-initiated Section 5 that MUST be implemented to support the committed multicast
replication multicast capability. bandwidth reporting capability.
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Section 4.1 | Provisioning message with Report-Buffering-Time | | Section 4.1 | Provisioning message with Report-Buffering-Time |
| | TLV | | | TLV |
| | | | | |
| Section 4.10 | Committed Bandwidth Report message | | Section 4.10 | Committed Bandwidth Report message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
skipping to change at page 53, line 9 skipping to change at page 55, line 9
Black Lists Black Lists
Table 3 specifies the protocol elements within Section 4 and Table 3 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the conditional access Section 5 that MUST be implemented to support the conditional access
with white and black lists multicast capability. with white and black lists multicast capability.
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Section 4.1 | Provisioning message with | | Section 4.1 | Provisioning message with |
| | Multicast-Service-Profile TLV, White and Black | | | Multicast-Service-Profile TLV, white and black |
| | lists only, and White-List-CAC TLV | | | lists only, and White-List-CAC TLV |
| | | | | |
| Section 4.2 | Port Management message with | | Section 4.2 | Port Management message with |
| | Multicast-Service-Profile-Name and | | | Multicast-Service-Profile-Name and |
| | Bandwidth-Allocation TLVs. | | | Bandwidth-Allocation TLVs. |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section 5.1 | Multicast-Service-Profile TLV | | Section 5.1 | Multicast-Service-Profile TLV |
| | | | | |
| Section 5.2 | Multicast-Service-Profile-Name TLV | | Section 5.2 | Multicast-Service-Profile-Name TLV |
| | | | | |
| Section 5.3 | List-Action TLV, White and Black lists only | | Section 5.3 | List-Action TLV, white and black lists only |
| | | | | |
| Section 5.5 | Bandwidth-Allocation TLV | | Section 5.5 | Bandwidth-Allocation TLV |
| | | | | |
| Section 5.6 | White-List-CAC TLV | | Section 5.6 | White-List-CAC TLV |
| | | | | |
| Section 5.11 | Multicast-Flow TLV | | Section 5.11 | Multicast-Flow TLV |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
Table 3: Protocol Requirements For Conditional Access with White and Table 3: Protocol Requirements For Conditional Access with White and
Black Lists Black Lists
6.1.4. Protocol Requirements For Conditional Access With Grey Lists 6.1.4. Protocol Requirements For Conditional Access With Grey Lists
Table 4 specifies the protocol elements within Section 4 and Table 4 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the conditional access Section 5 that MUST be implemented to support the conditional access
with grey lists multicast capability. with grey lists multicast capability. Additionally, implementation
of the Multicast Replication Control message requires implementation
of the Command TLV (Section 4.4 of [RFC6320] with additional details
in Section 4.3 of this document).
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Section 4.1 | Provisioning message with | | Section 4.1 | Provisioning message with |
| | Multicast-Service-Profile TLV, Grey lists only, | | | Multicast-Service-Profile TLV, grey lists only, |
| | and MRepCtl-CAC TLV | | | and MRepCtl-CAC TLV |
| | | | | |
| Section 4.2 | Port Management message with | | Section 4.2 | Port Management message with |
| | Multicast-Service-Profile-Name and | | | Multicast-Service-Profile-Name and |
| | Bandwidth-Allocation TLVs. | | | Bandwidth-Allocation TLVs. |
| | | | | |
| Section 4.3 | Multicast Replication Control message | | Section 4.3 | Multicast Replication Control message |
| | | | | |
| Section 4.4 | Multicast Admission Control Message | | Section 4.4 | Multicast Admission Control Message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section 5.1 | Multicast-Service-Profile TLV, Grey lists only | | Section 5.1 | Multicast-Service-Profile TLV, grey lists only |
| | | | | |
| Section 5.2 | Multicast-Service-Profile-Name TLV | | Section 5.2 | Multicast-Service-Profile-Name TLV |
| | | | | |
| Section 5.3 | List-Action TLV, Grey lists only | | Section 5.3 | List-Action TLV, grey lists only |
| | | | | |
| Section 5.4 | Command Number TLV | | Section 5.4 | Sequence Number TLV |
| | | | | |
| Section 5.5 | Bandwidth-Allocation TLV | | Section 5.5 | Bandwidth-Allocation TLV |
| | | | | |
| Section 5.7 | MRepCtl-CAC TLV | | Section 5.7 | MRepCtl-CAC TLV |
| | | | | |
| Section 5.9 | Request-Source-IP TLV | | Section 5.9 | Request-Source-IP TLV |
| | | | | |
| Section 5.10 | Request-Source-MAC TLV | | Section 5.10 | Request-Source-MAC TLV |
| | | | | |
| Section 5.11 | Multicast-Flow TLV | | Section 5.11 | Multicast-Flow TLV |
skipping to change at page 55, line 45 skipping to change at page 57, line 45
capabilities are described in Section 6.3. capabilities are described in Section 6.3.
The use of the Multicast Flow Query Request and Response messages to The use of the Multicast Flow Query Request and Response messages to
determine the association between multicast flows and ports is common determine the association between multicast flows and ports is common
to all multicast capabilities. No additional text is required here, to all multicast capabilities. No additional text is required here,
beyond that already given in Section 4.9 to describe the use of those beyond that already given in Section 4.9 to describe the use of those
messages. messages.
6.2.1. Procedures For NAS-Initiated Replication 6.2.1. Procedures For NAS-Initiated Replication
NAS-initiated replication MAY be negotiated to support a mode of NAS-initiated replication may be negotiated to support a mode of
operation where IGMP/MLD requests are terminated on the NAS. operation where IGMP/MLD requests are terminated on the NAS.
Alternatively, it MAY be negotiated to allow the NAS to respond to Alternatively, it may be negotiated to allow the NAS to respond to
requests sent by other means (e.g., through application signalling) requests sent by other means (e.g., through application signalling)
that require the replication of multicast channels to a given access that require the replication of multicast channels to a given access
line. line.
6.2.1.1. Provisioning 6.2.1.1. Provisioning
The NAS MAY perform admission control for NAS-initiated replication. The NAS MAY perform admission control for NAS-initiated replication.
In this case, it MUST NOT include the MRepCtl-CAC TLV in a In this case, it MUST NOT include the MRepCtl-CAC TLV in a
Provisioning message sent to the AN. Alternatively, the NAS MAY Provisioning message sent to the AN. Alternatively, the NAS MAY
enable admission control at the AN for NAS-initiated replication. To enable admission control at the AN for NAS-initiated replication. To
skipping to change at page 56, line 26 skipping to change at page 58, line 26
The procedures associated with NAS-initiated replication are The procedures associated with NAS-initiated replication are
straightforward. To initiate replication, the NAS MUST send a straightforward. To initiate replication, the NAS MUST send a
Multicast Replication Control message to the AN, containing one or Multicast Replication Control message to the AN, containing one or
more commands adding flows, as described in Section 4.3.1. To more commands adding flows, as described in Section 4.3.1. To
terminate replication the NAS MUST send a Multicast Replication terminate replication the NAS MUST send a Multicast Replication
Control message where the commands delete instead of adding the Control message where the commands delete instead of adding the
flows. The AN acts upon these messages as specified in flows. The AN acts upon these messages as specified in
Section 4.3.2. Section 4.3.2.
6.2.2. Procedures For Committed Bandwidth Reporting 6.2.2. Procedures For Committed Bandwidth Reporting
Committed bandwidth reporting MAY be negotiated if the NAS requires Committed bandwidth reporting may be negotiated if the NAS requires
current knowledge of the amount of multicast bandwidth committed to current knowledge of the amount of multicast bandwidth committed to
each access line and cannot obtain this information by other means. each access line and cannot obtain this information by other means.
6.2.2.1. Provisioning 6.2.2.1. Provisioning
The default buffering time when committed bandwidth reporting is The default buffering time when committed bandwidth reporting is
enabled is zero (immediate reporting). To change this, the NAS MAY enabled is zero (immediate reporting). To change this, the NAS MAY
send an instance of the Report-Buffering-Time TLV containing a non- send an instance of the Report-Buffering-Time TLV containing a non-
zero time value to the AN in a Provisioning message. If the NAS zero time value to the AN in a Provisioning message. If the NAS
subsequently wishes to change the buffering time again, it MAY do so subsequently wishes to change the buffering time again, it MAY do so
skipping to change at page 57, line 13 skipping to change at page 59, line 13
line changes. It leaves buffering state when the AN sends a line changes. It leaves buffering state when the AN sends a
Committed Bandwidth Report. Committed Bandwidth Report.
Upon entry to the buffering state, the AN MUST start a buffering Upon entry to the buffering state, the AN MUST start a buffering
timer and create a Committed Bandwidth Report message containing a timer and create a Committed Bandwidth Report message containing a
Committed-Bandwidth TLV for the triggering access line, but MUST NOT Committed-Bandwidth TLV for the triggering access line, but MUST NOT
send it. If a multicast bandwidth change occurs for another access send it. If a multicast bandwidth change occurs for another access
line, the AN MUST add a new Committed-Bandwidth TLV to the message line, the AN MUST add a new Committed-Bandwidth TLV to the message
for that additional line. If a multicast bandwidth change occurs for for that additional line. If a multicast bandwidth change occurs for
a line for which a Committed-Bandwidth TLV is already present in the a line for which a Committed-Bandwidth TLV is already present in the
buffered report, the AN MUST update the Committed-Bandwidth TLV to buffered report, the AN MUST update the corresponding Committed-
contain the new bandwidth value, rather than adding another Bandwidth TLV to contain the new bandwidth value, rather than adding
Committed-Bandwidth TLV for the same access line. another Committed-Bandwidth TLV for the same access line.
The buffering timer expires after the period provided by the Report- The buffering timer expires after the period provided by the Report-
Buffering-Time TLV. When it expires, the AN MUST send the Committed Buffering-Time TLV. When it expires, the AN MUST send the Committed
Bandwidth Report message that it has been accumulating to the NAS. Bandwidth Report message that it has been accumulating to the NAS.
Exceptionally, the AN MAY choose to send the message before the timer Exceptionally, the AN MAY choose to send the message before the timer
expires, in which case it MUST clear the buffering timer when the expires, in which case it MUST clear the buffering timer when the
message is sent. In either case, the AN enters the not-buffering message is sent. In either case, the AN enters the not-buffering
state as a result. state as a result.
Report buffering implies that NAS reaction to changes in multicast Report buffering implies that NAS reaction to changes in multicast
bandwidth usage is delayed by the amount of the buffering period. bandwidth usage is delayed by the amount of the buffering period.
The choice of buffering period must take this into consideration. The choice of buffering period must take this into consideration.
6.2.3. Procedures For Conditional Access With Black and White Lists 6.2.3. Procedures For Conditional Access With Black and White Lists
6.2.3.1. Provisioning 6.2.3.1. Provisioning
The NAS provisions named multicast service profiles containing White The NAS provisions named multicast service profiles containing white
and Black lists on the AN using the Provisioning message containing and black lists on the AN using the Provisioning message containing
one or more Multicast-Service-Profile TLVs. The NAS MAY update the one or more Multicast-Service-Profile TLVs. The NAS MAY update the
contents of these profiles from time to time as required, by sending contents of these profiles from time to time as required, by sending
additional Provisioning messages with Multicast-Service-Profile TLVs additional Provisioning messages with Multicast-Service-Profile TLVs
containing incremental modifications to the existing White and Black containing incremental modifications to the existing white and black
lists or replacements for them. lists or replacements for them.
The NAS assigns a specific multicast service profile to an individual The NAS assigns a specific multicast service profile to an individual
access line using the Port Management message containing a Multicast- access line using the Port Management message containing a Multicast-
Service-Profile-Name TLV. The NAS MAY change the multicast service Service-Profile-Name TLV. The NAS MAY change the multicast service
profile for a given access line at any time by sending a Port profile for a given access line at any time by sending a Port
Management message identifying a new multicast service profile. Management message identifying a new multicast service profile.
The NAS MAY choose to enable admission control at the AN for White- The NAS MAY choose to enable admission control at the AN for white-
listed flows. To do this, it MUST send a Provisioning message as listed flows. To do this, it MUST send a Provisioning message as
described in Section 4.1, which includes the White-List-CAC TLV and described in Section 4.1, which includes the White-List-CAC TLV and
it MUST provide a multicast bandwidth allocation for each access line it MUST provide a multicast bandwidth allocation for each access line
by including a Bandwidth-Allocation TLV in a Port Management message. by including a Bandwidth-Allocation TLV in a Port Management message.
6.2.3.2. Multicast Service Procedures 6.2.3.2. Multicast Service Procedures
The conditional access with White and Black lists capability assumes The conditional access with white and black lists capability assumes
that IGMP/MLD requests are terminated on the AN. When the AN that IGMP/MLD requests are terminated on the AN. When the AN
receives a "join" request, it MUST check to see whether the requested receives a "join" request, it MUST check to see whether the requested
flow is White-listed or Black-listed as described below. Requests flow is white-listed or black-listed as described below. Requests
for Black-listed flows MUST be discarded. If the NAS has enabled for black-listed flows MUST be discarded. If the NAS has enabled
admission control on the AN as described in the previous section, but admission control on the AN as described in the previous section, but
a White-listed flow would cause the amount of committed multicast a white-listed flow would cause the amount of committed multicast
bandwidth to exceed the provisioned limit, the request MUST be bandwidth to exceed the provisioned limit, the request MUST be
discarded. The AN replicates flows passing these checks to the discarded. The AN replicates flows passing these checks to the
access line. access line.
To determine if a requested flow is White-listed, the AN searches for To determine if a requested flow is white-listed, the AN searches for
a best match to the flow in the applicable multicast service profile. a best match to the flow in the applicable multicast service profile.
Matching is done on the prefixes specified in the profile, ignoring Matching is done on the prefixes specified in the profile, ignoring
the address bits of lower order than those in the prefix. the address bits of lower order than those in the prefix.
If the requested multicast flow matches multiple lists associated If the requested multicast flow matches multiple lists associated
with the access line, then the most specific match will be considered with the access line, then the most specific match will be considered
by the AN. If the most specific match occurs in multiple lists, the by the AN. If the most specific match occurs in multiple lists, the
Black list entry takes precedence over the White list. In this black list entry takes precedence over the white list. In this
context, the most specific match is defined as: context, the most specific match is defined as:
o first, most specific match (longest prefix length) on the o first, most specific match (longest prefix length) on the
multicast flow address (i.e., on G of <S,G>) multicast group address (i.e., on G of <S,G>)
o then, most specific match (longest prefix length) on the unicast o then, most specific match (longest prefix length) on the unicast
source address (i.e. on S of <S,G>) source address (i.e. on S of <S,G>)
If the requested multicast flow is not part of any list, the join If the requested multicast flow is not part of any list, the join
message SHOULD be discarded by the AN. This default behavior can message SHOULD be discarded by the AN. This default behavior can
easily be changed by means of a "catch-all" statement in the White easily be changed by means of a "catch-all" statement in the white
list. For instance, adding (<S=*,G=*>) in the White List would make list. For instance, adding (<S=*,G=*>) in the white List would make
the default behavior to accept join messages for a multicast flow the default behavior to accept join messages for a multicast flow
that has no other match on any list. that has no other match on any list.
When the AN receives a "leave" request, it terminates replication of When the AN receives a "leave" request, it terminates replication of
the multicast flow. the multicast flow.
If the AN receives a Provisioning message which updates an existing If the AN receives a Provisioning message which updates an existing
multicast service profile, the AN MUST review the status of active multicast service profile, the AN MUST review the status of active
flows on all ports to which the updated profile is currently flows on all ports to which the updated profile is currently
assigned. Similarly, if a Port Management message assigns a new assigned. Similarly, if a Port Management message assigns a new
multicast service profile to a given port, the AN MUST review all multicast service profile to a given port, the AN MUST review all
active flows on that port. If the most specific match for any flow active flows on that port. If the most specific match for any flow
is a Black list entry, the flow MUST be terminated immediately. If is a black list entry, the flow MUST be terminated immediately. If
any of the remaining flows do not match an entry in the White list, any of the remaining flows do not match an entry in the white list,
they also MUST be terminated immediately. White listed flows MUST be they also MUST be terminated immediately. White listed flows MUST be
allowed to continue. allowed to continue.
6.2.4. Procedures For Conditional Access With Grey Lists 6.2.4. Procedures For Conditional Access With Grey Lists
6.2.4.1. Provisioning 6.2.4.1. Provisioning
The NAS provisions named multicast service profiles containing Grey The NAS provisions named multicast service profiles containing grey
lists on the AN using the Provisioning message containing one or more lists on the AN using the Provisioning message containing one or more
Multicast-Service-Profile TLVs. The NAS MAY update the contents of Multicast-Service-Profile TLVs. The NAS MAY update the contents of
these profiles from time to time as required, by sending additional these profiles from time to time as required, by sending additional
Provisioning messages with Multicast-Service-Profile TLVs containing Provisioning messages with Multicast-Service-Profile TLVs containing
incremental modifications to the existing Grey lists or replacements incremental modifications to the existing grey lists or replacements
for them. for them.
The NAS assigns a specific multicast service profile to an individual The NAS assigns a specific multicast service profile to an individual
access line using the Port Management message containing a Multicast- access line using the Port Management message containing a Multicast-
Service-Profile-Name TLV. The NAS MAY change profiles on the line by Service-Profile-Name TLV. The NAS MAY change profiles on the line by
sending a subsequent Port Management message identifying a new sending a subsequent Port Management message identifying a new
profile. profile.
The NAS MAY perform admission control for grey-listed flows. In that The NAS MAY perform admission control for grey-listed flows. In that
case, the NAS MUST NOT include the MRepCtl-CAC TLV in a Provisioning case, the NAS MUST NOT include the MRepCtl-CAC TLV in a Provisioning
message sent to the AN. Alternatively, the NAS MAY enable admission message sent to the AN. Alternatively, the NAS MAY enable admission
control at the AN for Grey-listed flows. To do this, it MUST include control at the AN for grey-listed flows. To do this, it MUST include
the MRepCtl-CAC TLV in a Provisioning message sent to the AN and MUST the MRepCtl-CAC TLV in a Provisioning message sent to the AN and MUST
also provide a Bandwidth- Allocation TLV in a Port Management message also provide a Bandwidth-Allocation TLV in a Port Management message
for each access line. for each access line.
6.2.4.2. Multicast Service Procedures 6.2.4.2. Multicast Service Procedures
The conditional access with Grey lists capability assumes that IGMP/ The conditional access with grey lists capability assumes that IGMP/
MLD requests are terminated on the AN. When the AN receives a "join" MLD requests are terminated on the AN. When the AN receives a "join"
request, it MUST determine whether there is a match to the requested request, it MUST determine whether there is a match to the requested
flow in the Grey list of the multicast service profile provisioned flow in the grey list of the multicast service profile provisioned
against the given access line. If there is no match, the request is against the given access line. If there is no match, the request is
discarded. Otherwise, the AN MUST send a Multicast Admission Control discarded. Otherwise, the AN MUST send a Multicast Admission Control
message to the NAS with content identifying the access line and the message to the NAS with content identifying the access line and the
multicast flow to be added. As indicated in Section 4.4, the AN MAY multicast flow to be added. As indicated in Section 4.4, the AN MAY
add information identifying the requestor by IP address and/or MAC add information identifying the requestor by IP address and/or MAC
address. address.
If the NAS decides to enable the flow, it MUST send a Multicast If the NAS decides to enable the flow, it MUST send a Multicast
Replication Control request to the AN to replicate the flow to the Replication Control request to the AN to replicate the flow to the
access line with the Result field set to Nack (0x1), as described in access line with the Result field set to Nack (0x1), as described in
skipping to change at page 60, line 26 skipping to change at page 62, line 26
When the AN receives a "leave" request, it MUST terminate replication When the AN receives a "leave" request, it MUST terminate replication
of the flow to the access line. It MUST then send a Multicast of the flow to the access line. It MUST then send a Multicast
Admission Control message to the NAS indicating the deletion. The Admission Control message to the NAS indicating the deletion. The
NAS updates its internal records but MUST NOT respond to the message. NAS updates its internal records but MUST NOT respond to the message.
If the AN receives a Provisioning message which updates an existing If the AN receives a Provisioning message which updates an existing
multicast service profile, the AN MUST review the status of active multicast service profile, the AN MUST review the status of active
flows on all ports to which the updated profile has been assigned. flows on all ports to which the updated profile has been assigned.
Similarly, if a Port Management message that assigns a new profile to Similarly, if a Port Management message that assigns a new profile to
a given port, the AN MUST review all active flows on that port. In a given port, the AN MUST review all active flows on that port. In
either case, if any flow does not match an entry in the Grey list, it either case, if any flow does not match an entry in the grey list, it
MUST be terminated immediately. MUST be terminated immediately.
6.2.5. Procedures For Delegated Bandwidth 6.2.5. Procedures For Delegated Bandwidth
6.2.5.1. Provisioning 6.2.5.1. Provisioning
The NAS SHOULD provision an initial amount of delegated multicast The NAS SHOULD provision an initial amount of delegated multicast
bandwidth for each access line using the Port Management message bandwidth for each access line using the Port Management message
containing the Bandwidth-Allocation TLV. containing the Bandwidth-Allocation TLV.
skipping to change at page 61, line 32 skipping to change at page 63, line 32
The NAS or AN MAY at any time release bandwidth to the peer using an The NAS or AN MAY at any time release bandwidth to the peer using an
autonomous Bandwidth Transfer message. The contents of this message autonomous Bandwidth Transfer message. The contents of this message
are described in Section 4.6. are described in Section 4.6.
6.3. Combinations of Multicast Capabilities 6.3. Combinations of Multicast Capabilities
6.3.1. Combination of Conditional Access With White and Black Lists and 6.3.1. Combination of Conditional Access With White and Black Lists and
Conditional Access With Grey Lists Conditional Access With Grey Lists
If conditional access with White and Black lists is combined with If conditional access with white and black lists is combined with
conditional access with Grey lists, provisioning of the multicast conditional access with grey lists, provisioning of the multicast
service profiles is as described in Section 6.2.3.1 except that service profiles is as described in Section 6.2.3.1 except that
multicast service profiles will also include Grey lists. Admission multicast service profiles will also include grey lists. Admission
control is enabled independently on the AN for White lists by control is enabled independently on the AN for white lists by
including the White-list-CAC TLV in the Provisioning message and for including the White-List-CAC TLV in the Provisioning message and for
Grey lists by including the MRepCtl-CAC TLV in the Provisioning grey lists by including the MRepCtl-CAC TLV in the Provisioning
message. The Bandwidth-Allocation TLV provisions an amount that message. The Bandwidth-Allocation TLV provisions an amount that
applies to both White- and Grey- listed flows if admission control is applies to both white- and grey- listed flows if admission control is
enabled for both. enabled for both.
With regard to multicast service procedures, one point of difference With regard to multicast service procedures, one point of difference
from the individual capabilities must be noted. This is an from the individual capabilities must be noted. This is an
interaction during the profile matching procedure. The AN MUST seek interaction during the profile matching procedure. The AN MUST seek
the best match amongst multiple lists as described in the best match amongst multiple lists as described in
Section 6.2.3.2. However, if there are multiple matches of equal Section 6.2.3.2. However, if there are multiple matches of equal
precision, the order of priority is Black list first, Grey list precision, the order of priority is black list first, grey list
second, and White list last. second, and white list last.
Once profile matching has been completed, processing of a "join" Once profile matching has been completed, processing of a "join"
request is as described in Section 6.2.3.2 for White or Black listed request is as described in Section 6.2.3.2 for white or black listed
flows or Section 6.2.4.2 for Grey listed flows. Requests that do not flows or Section 6.2.4.2 for grey listed flows. Requests that do not
match any list SHOULD be discarded. match any list SHOULD be discarded.
When the AN receives a "leave" request, it MUST terminate replication When the AN receives a "leave" request, it MUST terminate replication
of the flow to the access line. If the flow was Grey-listed, the AN of the flow to the access line. If the flow was grey-listed, the AN
MUST then send a Multicast Admission Control message to the NAS MUST then send a Multicast Admission Control message to the NAS
indicating the deletion. Thus the AN needs to retain the fact that indicating the deletion. Thus the AN needs to retain the fact that
the flow was Grey-listed for the life of the flow. the flow was grey-listed for the life of the flow.
If the AN receives a Provisioning message which updates an existing If the AN receives a Provisioning message which updates an existing
multicast service profile, the AN MUST review the status of active multicast service profile, the AN MUST review the status of active
flows on all ports to which the updated profile is currently flows on all ports to which the updated profile is currently
assigned. Similarly, if a Port Management message assigns a new assigned. Similarly, if a Port Management message assigns a new
multicast service profile to a given port, the AN MUST review all multicast service profile to a given port, the AN MUST review all
active flows on that port. If any flow has its most specific match active flows on that port. If any flow has its most specific match
in a Black list entry, it MUST be terminated immediately. If any of in a black list entry, it MUST be terminated immediately. If any of
the remaining flows do not match an entry in the White or Grey list, the remaining flows do not match an entry in the white or grey list,
they MUST also be terminated immediately. Finally, if any remaining they MUST also be terminated immediately. Finally, if any remaining
flows were originally admitted because they were White-listed, but flows were originally admitted because they were white-listed, but
after the change they are Grey- listed, the AN MUST generate a after the change they are grey-listed, the AN MUST generate a
Multicast Flow Query response message autonomously as if it were Multicast Flow Query response message autonomously as if it were
responding to a Multicast Flow Query request, listing all such flows. responding to a Multicast Flow Query request, listing all such flows.
These flows MUST be allowed to continue until the NAS or the These flows MUST be allowed to continue until the NAS or the
subscriber terminates them. Flows with their most specific match in subscriber terminates them. Flows with their most specific match in
the White list MUST be allowed to continue. the white list MUST be allowed to continue.
The autonomously-generated Multicast Flow Query response message MUST The autonomously-generated Multicast Flow Query response message MUST
be formatted as if it were a successful response to a request be formatted as if it were a successful response to a request
containing no Target and no Multicast-Flow TLV, as described in containing no Target and no Multicast-Flow TLV, as described in
Section 4.9.2, with the exception that the Transaction-Id MUST be set Section 4.9.2, with the exception that the Transaction-Id MUST be set
to all zeroes. to all zeroes.
6.3.2. Combination of Conditional Access With Delegated Bandwidth 6.3.2. Combination of Conditional Access With Delegated Bandwidth
The provisioning and bandwidth management procedures of Section 6.2.5 The provisioning and bandwidth management procedures of Section 6.2.5
apply in addition to the procedures in Section 6.2.3, Section 6.2.4, apply in addition to the procedures in Section 6.2.3, Section 6.2.4,
or Section 6.3.1 as applicable. Admission control follows the rules or Section 6.3.1 as applicable. Admission control follows the rules
for conditional access in terms of matching flows against White and for conditional access in terms of matching flows against white and
Black and/or Grey lists and performing or not performing bandwidth black and/or grey lists and performing or not performing bandwidth
checks at the AN, but the amount of bandwidth used by the AN to checks at the AN, but the amount of bandwidth used by the AN to
perform admission control is negotiable as described in perform admission control is negotiable as described in
Section 6.2.5.2. Section 6.2.5.2.
6.3.3. Combination of NAS-Initiated Replication with Other Capabilities 6.3.3. Combination of NAS-Initiated Replication with Other Capabilities
NAS-initiated replication can coexist with the other capabilities, NAS-initiated replication can coexist with the other capabilities,
but some means must exist to prevent double replication of flows. but some means must exist to prevent double replication of flows.
The simplest way to do this is to terminate all IGMP/MLD requests on The simplest way to do this is to terminate all IGMP/MLD requests on
the AN, so that NAS-initiated replication is stimulated only by the AN, so that NAS-initiated replication is stimulated only by
signalling through other channels. Other arrangements are possible, signalling through other channels. Other arrangements are possible,
but need not be discussed here. but need not be discussed here.
Assuming the necessary separation of responsibilities, the only point Assuming the necessary separation of responsibilities, the only point
of interaction between NAS-initiated replication and the other of interaction between NAS-initiated replication and the other
multicast capabilities is in the area of admission control. multicast capabilities is in the area of admission control.
Specifically, inclusion of the MRepCtl-CAC TLV in a Provisioning Specifically, if the AN is to do admission control for flows added by
message and the Bandwidth-Allocation TLV in a Port Management message Multicast Replication Control messages, regardless of whether they
enables admission control by the AN for flows added by Multicast are part of NAS-initiated replication or grey list multicast service
Replication Control messages, regardless of whether they are part of processing, the NAS includes the MRepCtl-CAC TLV in a Provisioning
NAS-initiated replication or Grey list multicast service processing. message and the Bandwidth-Allocation TLV in a Port Management
Conversely, non inclusion of the MRepCtl-CAC TLV in Provisioning message. If instead the NAS will do admission control for flows
messages to the AN enables admission control by the NAS for flows
added by Multicast Replication Control messages, regardless of added by Multicast Replication Control messages, regardless of
whether they are part of NAS- initiated replication or Grey list whether they are part of NAS-initiated replication or grey list
multicast service processing. Admission Control for white flows can multicast service processing, it does not send the MRepCtl-CAC TLV in
also be enabled independently on the AN by inclusion by the NAS of a Provisioning messages to the AN. The NAS can independently enable
the White-List-CAC TLV in the Provisioning message. Admission Control for white flows on the AN by including the White-
List-CAC TLV in the Provisioning message.
6.3.4. Combinations of Committed Bandwidth Reporting with Other 6.3.4. Combinations of Committed Bandwidth Reporting with Other
Multicast Capabilities Multicast Capabilities
Committed bandwidth reporting can take independently of which other Committed bandwidth reporting can take place independently of which
multicast capabilities have been negotiated. However, some other 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 [RFC6320] and in The security considerations of ANCP are discussed in [RFC6320] and in
[RFC5713]. [RFC5713]. Multicast does not in principle introduce any new
security considerations, although it does increase the attractiveness
of the ANCP protocol as a means of denial of service (e.g., through
direction of multicast streams onto the target) or theft of service.
8. IANA Considerations 8. IANA Considerations
IANA NOTE: Please replace XXXX with the RFC number of this document. IANA NOTE: Please replace XXXX with the RFC number of this document.
This document defines the following additional values within the ANCP This document defines the following additional values within the ANCP
Message Type Name Space registry: Message Type Name Space registry:
+--------------+--------------------------------+-----------+ +--------------+--------------------------------+-----------+
| Message Type | Message Name | Reference | | Message Type | Message Name | Reference |
skipping to change at page 65, line 39 skipping to change at page 67, line 39
This document defines the following additional values for the ANCP This document defines the following additional values for the ANCP
Result Code registry: Result Code registry:
+------------+------------------------------------------+-----------+ +------------+------------------------------------------+-----------+
| Result | One-Line Description | Reference | | Result | One-Line Description | Reference |
| Code | | | | Code | | |
+------------+------------------------------------------+-----------+ +------------+------------------------------------------+-----------+
| 0x64 | Command error. | RFC XXXX | | 0x64 | Command error. | RFC XXXX |
| | | | | | | |
| 0x65 | Bad flow address. | RFC XXXX | | 0x65 | Invalid flow address. | RFC XXXX |
| | | | | | | |
| 0x66 | Multicast flow does not exist. | RFC XXXX | | 0x66 | Multicast flow does not exist. | RFC XXXX |
| | | | | | | |
| 0x67 | Invalid preferred bandwidth amount. | RFC XXXX | | 0x67 | Invalid preferred bandwidth amount. | RFC XXXX |
| | | | | | | |
| 0x68 | Inconsistent views of delegated | RFC XXXX | | 0x68 | Inconsistent views of delegated | RFC XXXX |
| | bandwidth amount. | | | | bandwidth amount. | |
| | | | | | | |
| 0x69 | Bandwidth request conflict. | RFC XXXX | | 0x69 | Bandwidth request conflict. | RFC XXXX |
+------------+------------------------------------------+-----------+ +------------+------------------------------------------+-----------+
skipping to change at page 67, line 8 skipping to change at page 69, line 8
| 6 | Admission Control and Conditional | RFC XXXX | | 6 | Admission Control and Conditional | RFC XXXX |
| | Access Reject | | | | Access Reject | |
+----------------+--------------------------------------+-----------+ +----------------+--------------------------------------+-----------+
This document defines the following additional values within the ANCP This document defines the following additional values within the ANCP
TLV Type Registry: TLV Type Registry:
+-----------+--------------------------------+-----------+ +-----------+--------------------------------+-----------+
| Type Code | TLV Name | Reference | | Type Code | TLV Name | Reference |
+-----------+--------------------------------+-----------+ +-----------+--------------------------------+-----------+
| 0x13 | Multicast-Service-Profile | RFC XXXX | | 0x0013 | Multicast-Service-Profile | RFC XXXX |
| | | | | | | |
| 0x15 | Bandwidth-Allocation | RFC XXXX | | 0x0015 | Bandwidth-Allocation | RFC XXXX |
| | | | | | | |
| 0x16 | Bandwidth-Request | RFC XXXX | | 0x0016 | Bandwidth-Request | RFC XXXX |
| | | | | | | |
| 0x18 | Multicast-Service-Profile-Name | RFC XXXX | | 0x0018 | Multicast-Service-Profile-Name | RFC XXXX |
| | | | | | | |
| 0x19 | Multicast-Flow | RFC XXXX | | 0x0019 | Multicast-Flow | RFC XXXX |
| | | | | | | |
| 0x21 | List-Action | RFC XXXX | | 0x0021 | List-Action | RFC XXXX |
| | | | | | | |
| 0x22 | Sequence-Number | RFC XXXX | | 0x0022 | Sequence-Number | RFC XXXX |
| | | | | | | |
| 0x24 | White-List-CAC | RFC XXXX | | 0x0024 | White-List-CAC | RFC XXXX |
| | | | | | | |
| 0x25 | MRepCtl-CAC | RFC XXXX | | 0x0025 | MRepCtl-CAC | RFC XXXX |
| | | | | | | |
| 0x92 | Request-Source-IP | RFC XXXX | | 0x0092 | Request-Source-IP | RFC XXXX |
| | | | | | | |
| 0x93 | Request-Source-MAC | RFC XXXX | | 0x0093 | Request-Source-MAC | RFC XXXX |
| | | | | | | |
| 0x94 | Report-Buffering-Time | RFC XXXX | | 0x0094 | Report-Buffering-Time | RFC XXXX |
| | | | | | | |
| 0x95 | Committed-Bandwidth | RFC XXXX | | 0x0095 | 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 Type registry: Capability Type registry:
+-------+-------------------------+--------+------------+-----------+ +-------+-------------------------+--------+------------+-----------+
| Value | Capability Type Name | Tech | Capability | Reference | | Value | Capability Type Name | Tech | Capability | Reference |
| | | Type | Data? | | | | | Type | Data? | |
+-------+-------------------------+--------+------------+-----------+ +-------+-------------------------+--------+------------+-----------+
| 3 | NAS-Initiated | 0 | No | RFC XXXX | | 3 | NAS-Initiated | 0 | No | RFC XXXX |
skipping to change at page 70, line 22 skipping to change at page 72, line 22
[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.
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
Listener Discovery (MLD) for IPv6", RFC 2710, Listener Discovery (MLD) for IPv6", RFC 2710,
October 1999. October 1999.
[RFC3292] Doria, A., Hellstrand, F., Sundell, K., and T. Worster,
"General Switch Management Protocol (GSMP) V3", RFC 3292,
June 2002.
[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.
[RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T. [RFC6320] 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", RFC 6320, October 2011. Broadband Networks", RFC 6320, October 2011.
skipping to change at page 72, line 28 skipping to change at page 74, line 28
o Some premium services are available, but requests for these o Some premium services are available, but requests for these
services must be referred to the policy server for proper credit services must be referred to the policy server for proper credit
processing. For this reason they are grey-listed. The NAS will processing. For this reason they are grey-listed. The NAS will
be responsible for admission control for these services. be responsible for admission control for these services.
o The subscriber has asked that certain services be blocked so that o The subscriber has asked that certain services be blocked so that
his children cannot view them. These services are black-listed. his children cannot view them. These services are black-listed.
o All of the above services are Source-Specific Multicast (SSM). In o All of the above services are Source-Specific Multicast (SSM). In
addition, by means which bypass the AN, the subscriber can signal addition, by means which bypass the AN, the subscriber can signal
intent to join an on- line game service which is Any-Source intent to join an on-line game service which is Any Source
Multicast (ASM). The NAS is responsible for admission control for Multicast (ASM). The NAS is responsible for admission control for
this service. this service.
o Bandwidth delegation is in effect to share video bandwidth between o Bandwidth delegation is in effect to share video bandwidth between
the AN and the NAS. the AN and the NAS.
The stated conditions require the use of four of the five The stated conditions require the use of four of the five
capabilities specified in this memo. capabilities specified in this memo.
A.1. Provisioning Phase A.1. Provisioning Phase
skipping to change at page 73, line 6 skipping to change at page 75, line 6
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 Result Code fields in the header are set to zeroes, o The Result and Result Code fields in the header are set to zeroes,
as specified in the ANCP base protocol document. as specified [RFC6320].
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
192.0.2.16. The Grey listed flows are in the band 192.0.2.16. The grey-listed flows are in the band
233.252.0.64/29, coming from a server at 192.0.2.21. Finally, the 233.252.0.64/29, coming from a server at 192.0.2.21. Finally, the
Black list flows are two individual flows that happen to overlap black list flows are two individual flows that happen to overlap
with the Grey list band: 233.252.0.65, and 233.252.0.69, also with with the grey list band: 233.252.0.65, and 233.252.0.69, also with
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 (0x880C) | Length = 132 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type = 93 | 0x00 | Result Code = 0x000 | | Version | 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 74, line 44 skipping to change at page 76, line 44
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 192.0.2.21 | G Preflen = 32| S Preflen = 32| / 192.0.2.21 | G Preflen = 32| S Preflen = 32|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Group prefix = 233.252.0.69 | | Group prefix = 233.252.0.69 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source prefix = 192.0.2.21 | | Source prefix = 192.0.2.21 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|White-List-CAC TLV Type = 0x24 | TLV Length = 0 | |White-List-CAC TLV Type = 0x24 | TLV Length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV lengths are given in decimal for easier understanding. Note that
the padding after the middle List-Action TLV is counted as part of
length of the Multicast-Service-Profile TLV, but is not included in
the length of that List-Action TLV. Note also that the Length field
in the message header, unlike those in the TLVs, includes the message
header itself, as required by [RFC3292]. Finally, note that the
Provisioning message does not include a MRepCtl-CAC TLV since in our
example admission control for Grey listed flows and for NAS-initiated
replication is performed by the NAS.
Figure 20: Example Provisioning Message Figure 20: Example Provisioning Message
TLV lengths in the figure are given in decimal for easier
understanding. Note that the padding after the middle List-Action
TLV is counted as part of length of the Multicast-Service-Profile
TLV, but is not included in the length of that List-Action TLV. Note
also that the Length field in the message header, unlike those in the
TLVs, includes the message header itself, as required by [RFC6320].
Finally, note that the Provisioning message does not include a
MRepCtl-CAC TLV since in our example admission control for grey
listed flows and for NAS-initiated replication is performed by the
NAS.
As soon as the AN port comes up, the AN sends an ANCP PORT_UP message As soon as the AN port comes up, the AN sends an ANCP PORT_UP message
to the NAS specifying the Access Loop Circuit ID. The NAS replies to the NAS specifying the Access Loop Circuit ID. The NAS replies
with an ANCP Port Management message that, together with the other with an ANCP Port Management message that, together with the other
parameters, includes the multicast service profile name to be parameters, includes the multicast service profile name to be
associated to that port along with the initial amount of delegated associated to that port along with the initial amount of delegated
bandwidth. The corresponding message flow is illustrated in bandwidth. The corresponding message flow is illustrated in
Figure 21. Figure 21.
+----------+ +---------+ +--- +----------+ +---------+ +-----+ +-----+
|Subscriber| | Home | | AN | | NAS | |Subscriber| | Home | | AN | | NAS |
+----------+ | Gateway | +-----+ +-----+ +----------+ | Gateway | +-----+ +-----+
| +---------+ | | | +---------+ | |
| | | | | | | |
| | | | | | | |
| | DSL Synch. | | | | DSL Synch. | |
| |--------------------->| | | |--------------------->| |
| | |(M1)PORT_UP(Port ID) | | | |(M1)PORT_UP(Port ID) |
| | |-------------------->| | | |-------------------->|
| | | (*) | | | (*)
| | |(M2) PORT_MNGT | | | |(M2) PORT_MNGT |
| | | (Port ID, | | | | (Port ID, |
| | |Mcast S Profile Name,| | | |Mcast S Profile Name,|
| | |Bandwidth Allocation)| | | |Bandwidth Allocation)|
| | |<--------------------| | | |<--------------------|
(*) The NAS may optionally seek direction from an external (*) The NAS may optionally seek direction from an external
Autorization/Policy Server Autorization/Policy Server
Figure 21: Configuring an AN Port With Multicast Service Profile ID Figure 21: Configuring an AN Port With Multicast Service Profile ID
and Delegated Bandwidth amount and Delegated Bandwidth Amount
The Port Management message will typically contain other TLVs but our The Port Management message will typically contain other TLVs but our
example (Figure 22) just shows the Target, Multicast- Service- example (Figure 22) just shows the Target, Multicast-Service-Profile-
Profile-Name, and Bandwidth-Allocation TLVs. The Target TLV Name, and Bandwidth-Allocation TLVs. The Target TLV identifies the
identifies the subscriber line, the Multicast-Service-Profile-Name subscriber line, the Multicast-Service-Profile-Name TLV is identical
TLV is identical to the one contained in the Provisioning message, to the one contained in the Provisioning message, and the Bandwidth-
and the Bandwidth-Allocation TLV provides just enough bandwidth (2000 Allocation TLV provides just enough bandwidth (2000 kbits/s) for one
kbits/s) for one channel to start with. 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 Result Code is 0x000. o Result Code is 0x000.
skipping to change at page 77, line 8 skipping to change at page 79, line 8
o Tech Type is 0x05 (DSL). o Tech Type is 0x05 (DSL).
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 (0x880C) | Length = 84 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type = 32 | 0x01 | Result Code = 0x000 | | Version | 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 78, line 10 skipping to change at page 80, line 10
| Bandwidth value = 0x000007D0 (2000 kbits/s) | | Bandwidth value = 0x000007D0 (2000 kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 22: Example Port Management Message Figure 22: Example Port Management Message
A.2. Handling a Grey-Listed Flow A.2. Handling a Grey-Listed Flow
Suppose now that the subscriber chooses to watch the premium channel Suppose now that the subscriber chooses to watch the premium channel
characterized by source 192.0.2.21, group 233.252.0.67. Upon characterized by source 192.0.2.21, group 233.252.0.67. Upon
receiving the Join request, the AN matches it against the multicast receiving the Join request, the AN matches it against the multicast
service profile for the port and determines that it is a Grey-listed service profile for the port and determines that it is a grey-listed
flow. Figure 23 illustrates the resulting ANCP message flow for the flow. Figure 23 illustrates the resulting ANCP message flow for the
case of a simple join and leave, when admission control for Grey- case of a simple join and leave, when admission control for grey-
listed flows is not activated on the AN. To start the flow, the AN listed flows is not activated on the AN.
sends a Multicast Admission Control request (M1) to the NAS. The NAS
decides whether flow can be admitted, applying both policy and To start the flow, the AN sends a Multicast Admission Control request
bandwidth criteria. It returns its decision (positive in this (M1) to the NAS. The NAS decides whether flow can be admitted,
example) in a Multicast Replication Control message (M2). Later, applying both policy and bandwidth criteria. It returns its decision
when the subscriber leaves the flow, the AN informs the NAS by (positive in this example) in a Multicast Replication Control message
sending another Multicast Admission Control message. (M2). Later, when the subscriber leaves the flow, the AN informs the
NAS by sending another Multicast Admission Control message.
+----------+ +-------+ +-----+ ANCP +-----+ +----------+ +-------+ +-----+ ANCP +-----+
|Subscriber| | Home | | AN |<---------->| NAS | |Subscriber| | Home | | AN |<---------->| NAS |
+----------+ |Gateway| +-----+ +-----+ +----------+ |Gateway| +-----+ +-----+
| +-------+ | | | +-------+ | |
| | | Multicast | | | | Multicast |
| Join(Grey-Fl) | Admission | | Join(Grey-Fl) | Admission |
|-----------+---------->| Control (M1) | |-----------+---------->| Control (M1) |
| | |------------------>| | | |------------------>|
| | | | (NAS performs | | | | (NAS performs
skipping to change at page 78, line 43 skipping to change at page 80, line 44
| Mcast Grey Flow |<------------------| | Mcast Grey Flow |<------------------|
|<======================+ | |<======================+ |
| | | | | | | |
~ ~ ~ ~ ~ ~ ~ ~
| | | Multicast | | | | Multicast |
| Leave(Grey-Fl) | Admission | | Leave(Grey-Fl) | Admission |
|-----------+---------->| Control (M3) | |-----------+---------->| Control (M3) |
| | |------------------>| | | |------------------>|
| | | | | | | |
Grey-Fl : Multicast Flow matching an entry in Grey List Grey-Fl : Multicast Flow matching an entry in grey List
(*) The NAS may optionally seek direction from an external (*) The NAS may optionally seek direction from an external
Authorization/Policy Server Authorization/Policy Server
Figure 23: Successful Join/Leave Operations, Grey- Listed Flow Figure 23: Successful Join/Leave Operations, Grey-Listed Flow
The Multicast Admission Control message M1 contains: The Multicast Admission Control message M1 contains:
o an ANCP Header with: o an ANCP Header with:
* Message-Type = 145 - Multicast Admission Control; * Message-Type = 145 - Multicast Admission Control;
* Result= 0x0 (Ignore); * Result= 0x0 (Ignore);
* Transaction-ID = Transaction-ID maintained by AN; * Transaction-ID = Transaction-ID maintained by AN;
o a Target TLV identifying the AN Port o a Target TLV identifying the AN Port
o a Command TLV containing: o a Command TLV containing:
* Command Code = Add (0x01); * Command Code = Add (1);
* Accounting = 0; * Accounting = 0;
* a Multicast-Flow embedded TLV indicating the SSM multicast flow * a Multicast-Flow embedded TLV indicating the SSM multicast flow
(Flow Type = 0x02) for which the AN received the IGMP Join: (Flow Type = 0x02) for which the AN received the IGMP Join:
IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source
Address = 192.0.2.21; Address = 192.0.2.21;
* 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 in
Figure 24:
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 (0x880C) | Length = 98 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=145 | 0x0 | Result Code = 0x000 | | Version | 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 80, line 39 skipping to change at page 82, line 39
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = 233.252.0.67 | | Multicast Group Address = 233.252.0.67 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Source Address = 192.0.2.21 | | Unicast Source Address = 192.0.2.21 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
| Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | | Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Address = 192.0.2.100 | | Unicast Address = 192.0.2.100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Multicast Admission Control Message Seeking To Add A Flow Figure 24: Multicast Admission Control Message Seeking To Add A Flow
The Multicast Replication Control message M2 contains: The Multicast Replication Control message M2 contains:
o an ANCP Header with: o an ANCP Header with:
* Message Type = 144 - Multicast Replication Control; * Message Type = 144 - Multicast Replication Control;
* Result= 0x1 (NAck); * Result= 0x1 (NAck);
* Transaction-ID = Transaction-ID maintained by NAS; * Transaction-ID = Transaction-ID maintained by NAS;
o a Target TLV identifying the AN Port; o a Target TLV identifying the AN Port;
o a Command TLV containing: o a Command TLV containing:
* Command Code = Add (0x01); * Command Code = Add (1);
* Accounting = 1 (begin flow accounting), since in our example * Accounting = 1 (begin flow accounting), since in our example
the operator wants accounting on this flow. the operator wants accounting on this flow.
* a Multicast-Flow embedded TLV indicating the SSM multicast flow * a Multicast-Flow embedded TLV indicating the SSM multicast flow
(Flow Type = 0x02) that the NAS is admitting for this access (Flow Type = 0x02) that the NAS is admitting for this access
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 in
Figure 25.
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 (0x880C) | Length = 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=144 | 0x1 | Result Code = 0x000 | | Version | 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 81, line 51 skipping to change at page 83, line 52
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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.0.67 | | Multicast Group Address = 233.252.0.67 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Source Address = 192.0.2.21 | | Unicast Source Address = 192.0.2.21 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 24: Multicast Replication Control Message Admitting A Flow Figure 25: Multicast Replication Control Message Admitting A Flow
The Multicast Admission Control message M3 advising the NAS that the The Multicast Admission Control message M3 advising the NAS that the
flow has been terminated contains: flow has been terminated contains:
o an ANCP Header with: o an ANCP Header with:
* Message-Type = 145 - Multicast Admission Control * Message-Type = 145 - Multicast Admission Control
* Result= 0x0 (Ignore) * Result= 0x0 (Ignore)
* Transaction-ID = Transaction-ID maintained by AN * Transaction-ID = Transaction-ID maintained by AN
o a Target TLV identifying the AN Port o a Target TLV identifying the AN Port
o a Command TLV containing: o a Command TLV containing:
* a Command Code = Delete (0x02); * a Command Code = Delete (2);
* Accounting = 0; * Accounting = 0;
* a Multicast-Flow embedded TLV indicating the SSM multicast flow * a Multicast-Flow embedded TLV indicating the SSM multicast flow
(Flow Type = 0x02) for which the AN received the IGMP leave: (Flow Type = 0x02) for which the AN received the IGMP leave:
IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source
Address = 192.0.2.21. Address = 192.0.2.21.
* 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 in
Figure 26.
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 (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=145 | 0x0 | Result Code = 0x000 | | Version | 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 83, line 39 skipping to change at page 85, line 39
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = 233.252.0.67 | | Multicast Group Address = 233.252.0.67 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Source Address = 192.0.2.21 | | Unicast Source Address = 192.0.2.21 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | | Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Address = 192.0.2.100 | | Unicast Address = 192.0.2.100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Multicast Admission Control Message Signalling flow Termination Figure 26: Multicast Admission Control Message Signalling Flow
Termination
A.3. Handling White-Listed Flows A.3. Handling White-Listed Flows
The NAS has enabled White list admission control on the AN, and the The NAS has enabled white list admission control on the AN, and the
bandwidth delegation capability has been negotiated. White listed bandwidth delegation capability has been negotiated. White listed
flows in themselves require no messages to the NAS, either upon flows in themselves require no messages to the NAS, either upon
admission or upon termination, but the AN may request an increase in admission or upon termination, but the AN may request an increase in
the amount of delegated bandwidth if it needs the increase to admit a the amount of delegated bandwidth if it needs the increase to admit a
flow. flow.
Consider an example where the AN has already admitted one White- Consider an example where the AN has already admitted one white-
listed flow, thereby using up the initially provisioned amount of listed flow, thereby using up the initially provisioned amount of
delegated bandwidth (2000 kbits/s). A request is received to join a delegated bandwidth (2000 kbits/s). A request is received to join a
new flow in the White list range. The AN chooses to send a Bandwidth new flow in the white list range. The AN chooses to send a Bandwidth
Reallocation Request message to the NAS, requesting that the Reallocation Request message to the NAS, requesting that the
delegated bandwidth allocation be increased to 4000 kbits/s at a delegated bandwidth allocation be increased to 4000 kbits/s at a
minimum, and preferably to 6000 kbits/s. minimum, and preferably to 6000 kbits/s.
In our example, the NAS is managing bandwidth tightly, as witnessed In our example, the NAS is managing bandwidth tightly, as witnessed
by its minimal initial allocation of just enough for one flow. It is by its minimal initial allocation of just enough for one flow. It is
willing to provide the minimum additional amount only, and therefore willing to provide the minimum additional amount only, and therefore
returns a Bandwidth Transfer message where the delegated bandwidth returns a Bandwidth Transfer message where the delegated bandwidth
value is given as 4000 kbits/s. With this amount, the AN is able to value is given as 4000 kbits/s. With this amount, the AN is able to
admit the second White-listed flow. The AN could send a similar admit the second white-listed flow. The AN could send a similar
Bandwidth Transfer message back to the NAS bringing the delegated Bandwidth Transfer message back to the NAS bringing the delegated
bandwidth amount back down to 2000 kbits/s when one of the flows is bandwidth amount back down to 2000 kbits/s when one of the flows is
terminated, but this shows nothing new and is omitted. terminated, but this shows nothing new and is omitted.
As one more point of illustration, suppose that the NAS chooses to As one more point of illustration, suppose that the NAS chooses to
audit the current amount of delegated bandwidth to ensure it is audit the current amount of delegated bandwidth to ensure it is
synchronized with the AN. It sends a Delegated Bandwidth Query synchronized with the AN. It sends a Delegated Bandwidth Query
request message to the AN, and receives a Delegated Bandwidth Query request message to the AN, and receives a Delegated Bandwidth Query
response message with the current allocation as the AN sees it. response message with the current allocation as the AN sees it.
The complete message flow is shown in Figure 25. The complete message flow is shown in Figure 27.
+----------+ +-------+ +-----+ ANCP +-----+ +----------+ +-------+ +-----+ ANCP +-----+
|Subscriber| | Home | | AN |<---------->| NAS | |Subscriber| | Home | | AN |<---------->| NAS |
+----------+ |Gateway| +-----+ +-----+ +----------+ |Gateway| +-----+ +-----+
| +-------+ | | | +-------+ | |
| | | | | | | |
| Join(White-F1) | | | Join(White-F1) | |
|-----------+---------->| | |-----------+---------->| |
| | |AN performs | | | |AN performs |
| Mcast White Flow 1 | admission control | | Mcast White Flow 1 | admission control |
skipping to change at page 85, line 43 skipping to change at page 87, line 43
| | |<------------------|(M3) | | |<------------------|(M3)
| | | | | | | |
| | |Delegated Bandwidth| | | |Delegated Bandwidth|
| | | Query response | | | | Query response |
| | |------------------>|(M4) | | |------------------>|(M4)
| | | | | | | |
(*) The NAS may optionally seek direction from an external (*) The NAS may optionally seek direction from an external
Authorization/Policy Server Authorization/Policy Server
Figure 25: Successful Join/Leave Operations, Grey-Listed Flow Figure 27: Successful Join/Leave Operations, White-Listed Flow
The Bandwidth Reallocation Request message (M1) is shown in The Bandwidth Reallocation Request message (M1) is shown in
Figure 26. The contents require little explanation. The Message Figure 28. The contents require little explanation. The Message
Type for the Bandwidth Reallocation Request is 146. The Result field Type for the Bandwidth Reallocation Request is 146. The Result field
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 (0x880C) | Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=146 | 0x0 | Result Code = 0x000 | | Version | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Bandwidth-Req TLV Type = 0x16 | TLV Length = 8 | |Bandwidth-Req TLV Type = 0x16 | TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required Amount = 0x00000FA0 (4000 kbits/s) | | Required Amount = 0x00000FA0 (4000 kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Preferred Amount = 0x00001770 (6000 kbits/s) | | Preferred Amount = 0x00001770 (6000 kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 26: Bandwidth Reallocation Request Message Figure 28: Bandwidth Reallocation Request Message
The Bandwidth Transfer message (M2) is shown in Figure 27. Again, The Bandwidth Transfer message (M2) is shown in Figure 29. Again,
the contents are easily understood. The Message Type for the the contents are easily understood. The Message Type for the
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 (0x880C) | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=147 | 0x3 | Result Code = 0x000 | | Version | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|BW-Allocation TLV Type = 0x15 | TLV Length = 4 | |BW-Allocation TLV Type = 0x15 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delegated Amount = 0x00000FA0 (4000 kbits/s) | | Delegated Amount = 0x00000FA0 (4000 kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 27: NAS Response, Bandwidth Transfer Message Figure 29: NAS Response, Bandwidth Transfer Message
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 30. 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 (0x880C) | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=148 | 0x2 | Result Code = 0x000 | | Version | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 28: Delegated Bandwidth Query Request Message Figure 30: Delegated Bandwidth Query Request Message
Finally, the Delegated Bandwidth Query response message (M4) is shown Finally, the Delegated Bandwidth Query response message (M4) is shown
in Figure 29. The Message Type for the Delegated Bandwidth Query in Figure 31. 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 (0x880C) | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=148 | 0x3 | Result Code = 0x000 | | Version | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|BW-Allocation TLV Type = 0x15 | TLV Length = 4 | |BW-Allocation TLV Type = 0x15 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delegated Amount = 0x00000FA0 (4000 kbits/s) | | Delegated Amount = 0x00000FA0 (4000 kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 29: Delegated Bandwidth Query Response Message Figure 31: Delegated Bandwidth Query Response Message
A.4. Handling Of Black-Listed Join Requests A.4. Handling Of Black-Listed Join Requests
This section introduces no new messages, since requests for flows in This section introduces no new messages, since requests for flows in
the Black list are simply ignored. The one thing to point out is the the black list are simply ignored. The one thing to point out is the
overlap in our example between the set of flows in the Grey list and overlap in our example between the set of flows in the grey list and
the flows in the Black list. This does not create any ambiguity, the flows in the black list. This does not create any ambiguity,
since not only does the Black list have priority for equally good since not only does the black list have priority for equally good
matches, but also the Black list entries are more specific (group matches, but also the black list entries are more specific (group
prefix lengths of 32 versus 29 in the Grey list) than the Grey list prefix lengths of 32 versus 29 in the grey list) than the grey list
flow prefixes. flow prefixes.
A.5. Handling Of Requests To Join and Leave the On-Line Game A.5. Handling Of Requests To Join and Leave the On-Line Game
The final class of multicast control actions in our example allows The final class of multicast control actions in our example allows
the subscriber to enter and leave the on-line game. As described at the subscriber to enter and leave the on-line game. As described at
the beginning of this example, the game uses Any Source Multicast the beginning of this example, the game uses Any Source Multicast
(ASM). Subscriber signalling bypasses the AN, going directly to the (ASM). Subscriber signalling bypasses the AN, going directly to the
NAS (e.g., through a web interface). NAS (e.g., through a web interface).
When the subscriber requests to join the game, the NAS (after When the subscriber requests to join the game, the NAS (after
applying policy and bandwidth checks) sends a Multicast Replication applying policy and bandwidth checks) sends a Multicast Replication
Control message to the AN to enable the flow on the port concerned. Control message to the AN to enable the flow on the port concerned.
The AN knows not to apply admission control, since it has not The AN knows not to apply admission control, since it has not
received an MRepCtl-CAC TLV in the Provisioning message. When the received an MRepCtl-CAC TLV in the Provisioning message. When the
subscriber leaves, the NAS sends another Multicast Replication subscriber leaves, the NAS sends another Multicast Replication
Control message to delete the flow. This message sequence is shown Control message to delete the flow. This message sequence is shown
in Figure 30. in Figure 32.
It is possible that the NAS finds that there is not enough bandwidth It is possible that the NAS finds that there is not enough bandwidth
available to accommodate the subscriber's request. In this case, the available to accommodate the subscriber's request. In this case, the
NAS could send a Bandwidth Reallocation Request message to the AN, NAS could send a Bandwidth Reallocation Request message to the AN,
asking it to release some of the bandwidth delegated to it. This is asking it to release some of the bandwidth delegated to it. This is
not shown in the present example, since the messages are the same as not shown in the present example, since the messages are the same as
those already presented with the exception that the Preferred Amount those already presented with the exception that the Preferred Amount
in the request will be *less than* or equal to the Required amount, in the request will be *less than* or equal to the Required amount,
rather than *greater than* or equal to it. rather than *greater than* or equal to it.
skipping to change at page 89, line 50 skipping to change at page 91, line 50
| | | Multicast | | | | Multicast |
| | | Replication | | | | Replication |
| | | Control (M2) | | | | Control (M2) |
| Mcast Game Flow |<------------------| | Mcast Game Flow |<------------------|
| discontinued | | | discontinued | |
| | | | | | | |
(*) The NAS may optionally seek direction from an external (*) The NAS may optionally seek direction from an external
Authorization/Policy Server Authorization/Policy Server
Figure 30: NAS-Initiated Flows For On-Line Gaming Figure 32: NAS-Initiated Flows For On-Line Gaming
Multicast Replication Control message (M1) in Figure 31 looks like Multicast Replication Control message (M1) in Figure 33 looks like
the message in Figure 24 with two exceptions. The first is that the the message in Figure 25 with two exceptions. The first is that the
NAS has the option to set the Result field to AckAll (0x02) if it NAS has the option to set the Result field to AckAll (0x02) if it
needs positive reassurance that the flow has been enabled. This was needs positive reassurance that the flow has been enabled. This was
not done here to save having to depict a response differing only in not done here to save having to depict a response differing only in
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 (0x880C) | Length = 44 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type=144 | 0x1 | Result Code = 0x000 | | Version | 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 90, line 41 skipping to change at page 92, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 | | Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 8 | |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x01 |Addr Fam =0x01 | Reserved = 0x0000 | |Flow Type=0x01 |Addr Fam =0x01 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = 233.252.1.100 | | Multicast Group Address = 233.252.1.100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
Figure 31: Enabling The Subscriber To Join An On- Line Game Figure 33: Enabling The Subscriber To Join An On-Line Game
Message M2 terminating the flow when the subscriber leaves the game Message M2 terminating the flow when the subscriber leaves the game
looks the same as the message in Figure 31 with two exceptions: the looks the same as the message in Figure 33 with two exceptions: the
Command Code becomes Delete (0x02), and Accounting is set to 0 to Command Code becomes Delete (2), and Accounting is set to 0 to turn
turn off flow accounting. Of course, the Transaction Identifier off flow accounting. Of course, the Transaction Identifier values
values will differ between the two messages. will differ between the two messages.
A.6. Example Flow For Multicast Flow Reporting A.6. Example Flow For Multicast Flow Reporting
The example in this section is independent of the example in the The example in this section is independent of the example in the
preceding sections. preceding sections.
Figure 32 illustrates a message flow in a case where the NAS queries Figure 34 illustrates a message flow in a case where the NAS queries
the AN about which multicast flows are active on port 10, on port 20 the AN about which multicast flows are active on port 10, on port 11
and on port 11 of the AN. and on port 20 of the AN.
+----------+ +-------+ +-----+ ANCP +----------+ +-------+ +-----+ ANCP +-----+
+-----+
|Subscriber| | Home | | AN |<---------->| NAS | |Subscriber| | Home | | AN |<---------->| NAS |
+----------+ |Gateway| +-----+ +-----+ +----------+ |Gateway| +-----+ +-----+
| +-------+ | | | +-------+ | |
| | | Multicast Flow | | | | Multicast Flow |
| | | Query Request | | | | Query Request |
| | | (M1) | | | | (M1) |
| | |<------------------| | | |<------------------|
| | | | | | | |
| | | Multicast Flow | | | | Multicast Flow |
| | | Query Response | | | | Query Response |
| | | (M2) | | | | (M2) |
| | |------------------>| | | |------------------>|
| | | | | | | |
| | | | | | | |
Figure 32: Per Port Multicast Flow Reporting Figure 34: Per-Port Multicast Flow Reporting
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 35. 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 (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type = 149|Rslt=2 | Result Code = 0 | | Version | 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 92, line 41 skipping to change at page 94, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 33: Multicast Flow Query Request Message For Per-Port Figure 35: Multicast Flow Query Request Message For Per-Port
Multicast Flow Reporting Multicast Flow Reporting
The Multicast Flow Query Response message (M2) is illustrated in The Multicast Flow Query Response message (M2) is illustrated in
Figure 34. It indicates that there is one active multicast flow Figure 36. It indicates that there is one active multicast flow
[(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 (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers | Sub | Msg Type = 149|Rslt=3 | Result Code = 0 | | Version | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
skipping to change at page 94, line 14 skipping to change at page 96, line 13
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
|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.10 | | Multicast Group Address: 233.252.2.10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Source Address = 192.0.2.2 | | Unicast Source Address = 192.0.2.2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
Figure 34: Multicast Flow Query Response message for per-port Figure 36: Multicast Flow Query Response message For Per-Port
Mulicast Flow Reporting Multicast Flow Reporting
Authors' Addresses Authors' Addresses
Francois Le Faucheur Francois Le Faucheur
Cisco Systems Cisco Systems
Greenside, 400 Avenue de Roumanille Greenside, 400 Avenue de Roumanille
Sophia Antipolis 06410 Sophia Antipolis 06410
France France
Phone: +33 4 97 23 26 19 Phone: +33 4 97 23 26 19
skipping to change at page 95, line 30 skipping to change at page 97, line 30
Italy Italy
Phone: Phone:
Email: roberta.maglione@telecomitalia.it Email: roberta.maglione@telecomitalia.it
Tom Taylor Tom Taylor
Huawei Technologies Huawei Technologies
Ottawa Ottawa
Canada Canada
Email: tom111.taylor@bell.net Email: tom.taylor.stds@gmail.com
 End of changes. 259 change blocks. 
498 lines changed or deleted 601 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/