draft-ietf-ancp-mc-extensions-12.txt   draft-ietf-ancp-mc-extensions-13.txt 
ANCP F. Le Faucheur ANCP F. Le Faucheur
Internet-Draft Cisco Internet-Draft Cisco
Updates: 6320 (if approved) R. Maglione Updates: 6320 (if approved) R. Maglione
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: May 23, 2014 T. Taylor Expires: June 13, 2014 T. Taylor
Huawei Huawei
November 19, 2013 December 10, 2013
Multicast Control Extensions for ANCP Multicast Control Extensions for ANCP
draft-ietf-ancp-mc-extensions-12.txt draft-ietf-ancp-mc-extensions-13.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 10 skipping to change at page 2, line 10
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 May 23, 2014. This Internet-Draft will expire on June 13, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 40 skipping to change at page 2, line 40
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 6 3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 6
3.1. NAS Initiated Multicast Replication Control Use Case . . 7 3.1. NAS Initiated Multicast Replication Control Use Case . . 7
3.1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 7 3.1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.2. Message Flow . . . . . . . . . . . . . . . . . . . . 7 3.1.2. Message Flow . . . . . . . . . . . . . . . . . . . . 7
3.2. Conditional Access and Admission Control Use Case . . . . 8 3.2. Conditional Access and Admission Control Use Case . . . . 8
3.2.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 8 3.2.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.2. Message Flow . . . . . . . . . . . . . . . . . . . . 8 3.2.2. Message Flow . . . . . . . . . . . . . . . . . . . . 8
3.3. Multicast Flow Reporting Use Case . . . . . . . . . . . . 9 3.3. Multicast Flow Reporting Use Case . . . . . . . . . . . . 9
3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9 3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 9 3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10
3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . 10 3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . 10
3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10 3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10 3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 11
4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11 4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 11 4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 12
4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12 4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12
4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 13 4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 13
4.2. Port Management Message . . . . . . . . . . . . . . . . . 14 4.2. Port Management Message . . . . . . . . . . . . . . . . . 14
4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 15 4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 15
4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 15 4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 15
4.3. Multicast Replication Control Message . . . . . . . . . . 16 4.3. Multicast Replication Control Message . . . . . . . . . . 16
4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 19 4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 19
4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 20 4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 20
4.4. Multicast Admission Control Message . . . . . . . . . . . 22 4.4. Multicast Admission Control Message . . . . . . . . . . . 22
4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 23 4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 23
4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 24 4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 24
4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25 4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25
4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25 4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25
4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26 4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26
4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29 4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29
4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 30 4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 29
4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30 4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30
4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31 4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31
4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31 4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31
4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 31 4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32
4.8. Delegated Bandwidth Query Response Message . . . . . . . 32 4.8. Delegated Bandwidth Query Response Message . . . . . . . 32
4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32 4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32
4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32 4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32
4.9. Multicast Flow Query Request and Response Messages . . . 33 4.9. Multicast Flow Query Request and Response Messages . . . 33
4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 34 4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 34
4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34 4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34
4.10. Committed Bandwidth Report Message . . . . . . . . . . . 36 4.10. Committed Bandwidth Report Message . . . . . . . . . . . 36
4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 36 4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 36
4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36 4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36
5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 37 5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 37
5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 37 5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 37
5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . 38 5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . 38
5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 39 5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 39
5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 41 5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 41
5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . 42 5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . 42
5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . 42 5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . 42
5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 43 5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 43
5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43 5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43
5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 44 5.9. Subs-Session-Id TLV . . . . . . . . . . . . . . . . . . . 44
5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . 44 5.10. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45
5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45 5.11. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46
5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46 5.12. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 46
5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 47
6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47 6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47
6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48 6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48
6.1.1. Protocol Requirements For NAS-Initiated Replication . 48 6.1.1. Protocol Requirements For NAS-Initiated Replication . 48
6.1.2. Protocol Requirements For Committed Multicast 6.1.2. Protocol Requirements For Committed Multicast
Bandwidth Reporting . . . . . . . . . . . . . . . . . 49 Bandwidth Reporting . . . . . . . . . . . . . . . . . 49
6.1.3. Protocol Requirements For Conditional Access With 6.1.3. Protocol Requirements For Conditional Access With
White and Black Lists . . . . . . . . . . . . . . . . 50 White and Black Lists . . . . . . . . . . . . . . . . 50
6.1.4. Protocol Requirements For Conditional Access With 6.1.4. Protocol Requirements For Conditional Access With
Grey Lists . . . . . . . . . . . . . . . . . . . . . 50 Grey Lists . . . . . . . . . . . . . . . . . . . . . 51
6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 52 6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 52
6.2. Capability-Specific Procedures for Providing Multicast 6.2. Capability-Specific Procedures for Providing Multicast
Service . . . . . . . . . . . . . . . . . . . . . . . . . 52 Service . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.2.1. Procedures For NAS-Initiated Replication . . . . . . 53
6.2.1. Procedures For NAS-Initiated Replication . . . . . . 52 6.2.2. Procedures For Committed Bandwidth Reporting . . . . 54
6.2.2. Procedures For Committed Bandwidth Reporting . . . . 53
6.2.3. Procedures For Conditional Access With Black and 6.2.3. Procedures For Conditional Access With Black and
White Lists . . . . . . . . . . . . . . . . . . . . . 54 White Lists . . . . . . . . . . . . . . . . . . . . . 55
6.2.4. Procedures For Conditional Access With Grey Lists . . 56 6.2.4. Procedures For Conditional Access With Grey Lists . . 57
6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 57 6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 58
6.3. Combinations of Multicast Capabilities . . . . . . . . . 58 6.3. Combinations of Multicast Capabilities . . . . . . . . . 59
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 . 58 Black Lists and Conditional Access With Grey Lists . 59
6.3.2. Combination of Conditional Access With Delegated 6.3.2. Combination of Conditional Access With Delegated
Bandwidth . . . . . . . . . . . . . . . . . . . . . . 60 Bandwidth . . . . . . . . . . . . . . . . . . . . . . 60
6.3.3. Combination of NAS-Initiated Replication with Other 6.3.3. Combination of NAS-Initiated Replication with Other
Capabilities . . . . . . . . . . . . . . . . . . . . 60 Capabilities . . . . . . . . . . . . . . . . . . . . 61
6.3.4. Combinations of Committed Bandwidth Reporting with 6.3.4. Combinations of Committed Bandwidth Reporting with
Other Multicast Capabilities . . . . . . . . . . . . 61 Other Multicast Capabilities . . . . . . . . . . . . 61
7. Security Considerations . . . . . . . . . . . . . . . . . . . 61 7. Security Considerations . . . . . . . . . . . . . . . . . . . 61
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 64 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 65
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 64 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.1. Normative References . . . . . . . . . . . . . . . . . . 64 10.1. Normative References . . . . . . . . . . . . . . . . . . 65
10.2. Informative References . . . . . . . . . . . . . . . . . 64 10.2. Informative References . . . . . . . . . . . . . . . . . 66
Appendix A. Example of Messages and Message Flows . . . . . . . 65 Appendix A. Example of Messages and Message Flows . . . . . . . 66
A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 65 A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 67
A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 70 A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 72
A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 75 A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 78
A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 79 A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 83
A.5. Handling Of Requests To Join and Leave the On-Line Game . 79 A.5. Handling Of Requests To Join and Leave the On-Line Game . 83
A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 81 A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 85
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 89
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 6, line 39 skipping to change at page 6, line 30
NAS-initiated multicast replication capability and by changing the NAS-initiated multicast replication capability and by changing the
starting point for IANA allocation of result codes determined by IETF starting point for IANA allocation of result codes determined by IETF
Consensus from 0x100 to 0x64. Consensus from 0x100 to 0x64.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Within this document, the term "conditional access and admission
control (CAC)" refers to the complete decision process for allowing
or disallowing a subscriber request for a new flow. This process
consists of two parts: policy-based admission control and resource-
based admission control. The NAS can delegate policy-based admission
control to the Access Node if both devices support conditional access
with white and black lists. It can delegate resource-based admission
control to the Access Node if both devices support any of the
capabilities described in this document besides or other than
committed bandwidth reporting. The delegation is performed on a per-
subscriber basis using the Provisioning (Section 4.1) and Port
Management (Section 4.2) messages.
The expression "delegated bandwidth" is used as a shorter way of The expression "delegated bandwidth" is used as a shorter way of
saying: "the total amount of video bandwidth delegated to the AN for saying: "the total amount of video bandwidth delegated to the AN for
multicast admission control". multicast resource-based admission control".
3. Multicast Use Cases 3. Multicast Use Cases
Quoting from [RFC5851]: Quoting from [RFC5851]:
"... the Access Node, aggregation node(s) and the NAS must all be "... the Access Node, aggregation node(s) and the NAS must all be
involved in the multicast replication process. This avoids that involved in the multicast replication process. This avoids that
several copies of the same stream are sent within the access/ several copies of the same stream are sent within the access/
aggregation network. In case of an Ethernet-based access/aggregation aggregation network. In case of an Ethernet-based access/aggregation
network, this may, for example, be achieved by means of IGMP snooping network, this may, for example, be achieved by means of IGMP snooping
skipping to change at page 7, line 20 skipping to change at page 7, line 23
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 referred 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
3.1.1. Goals 3.1.1. Goals
One option for multicast handling is for the subscriber to One option for multicast handling is for the subscriber to
communicate the "join/leave" information to the NAS. This can be communicate the "join/leave" information to the NAS. This can be
done for instance by terminating all subscriber IGMP ([RFC3376]) or done for instance by terminating all subscriber IGMP ([RFC3376]) or
MLD ([RFC2710], [RFC3810]) signaling on the NAS. Another example MLD ([RFC2710], [RFC3810]) signaling on the NAS. Another example
could be a subscriber using some form of application level signaling, could be a subscriber using some form of application level signaling,
which is redirected to the NAS. In any case, this option is which is redirected to the NAS. In any case, this option is
transparent to the access and aggregation network. In this scenario, transparent to the access and aggregation network. In this scenario,
the NAS uses ANCP to create and remove replication state in the AN the NAS uses ANCP to create and remove replication state in the AN
for efficient multicast replication. Thus, the NAS only sends a for efficient multicast replication. Thus, the NAS only sends a
single copy of the multicast stream towards the AN, which in turn single copy of the multicast stream towards the AN, which in turn
performs replication to multiple subscribers as instructed by the NAS performs replication to multiple subscribers as instructed by the NAS
via ANCP. The NAS first performs conditional access and multicast via ANCP. The NAS performs conditional access and admission control
admission control when processing multicast join requests, and only when processing multicast join requests, and only creates replication
creates replication state in the AN if admission succeeds. state in the AN if admission succeeds.
3.1.2. Message Flow 3.1.2. Message Flow
With the NAS-initiated use case, a Multicast Replication Control With the NAS-initiated use case, a Multicast Replication Control
Message is sent by the NAS to the AN with a directive to either join Message is sent by the NAS to the AN with a directive to either join
or leave one (or more) multicast flow(s). In the example message or leave one (or more) multicast flow(s). In the example message
flow, the AN uses a Generic Response message to convey the outcome of flow, the AN uses a Generic Response message to convey the outcome of
the directive. Figure 1 illustrates such an ANCP message exchange as the directive. Figure 1 illustrates such an ANCP message exchange as
well as the associated AN behavior. well as the associated AN behavior.
+----------+ +-------+ +-----+ ANCP +-----+ +----------+ +-------+ +-----+ ANCP +-----+
|Subscriber| | Home | | AN |<-------------------->| NAS | |Subscriber| | Home | | AN |<-------------------->| NAS |
+----------+ |Gateway| +-----+ +-----+ +----------+ |Gateway| +-----+ +-----+
| +-------+ | | | +-------+ | |
| | | (*) | | | (*)
| | | Multicast-Replication-Crl | | | | Multicast-Replication-Ctl |
| | | (Target,add, Flow 1) | | | | (Target,add, Flow 1) |
| | |<--------------------------| | | |<--------------------------|
| Mcast Flow 1 | | | Mcast Flow 1 | |
|<==========================+ | |<==========================+ |
| | | Generic Response | | | | Generic Response |
| | |-------------------------->| | | |-------------------------->|
| | | | | | | |
| | | | | | | |
~ ~ ~ ~ ~ ~ ~ ~
| | | | | | | |
| | | Multicast-Replication-Crl | | | | Multicast-Replication-Ctl |
| | | (Target,delete, Flow 1) | | | | (Target,delete, Flow 1) |
| | |<--------------------------| | | |<--------------------------|
| | | | | | | |
| <Stop Replication of X | | <Stop Replication of X |
| Mcast Flow 1> | Generic Response | | Mcast Flow 1> | Generic Response |
| | |-------------------------->| | | |-------------------------->|
(*) The NAS may optionally seek direction from an external (*) The NAS may optionally seek direction from an external
Authorization/Policy Server before admitting the flow. Authorization/Policy Server before admitting the flow.
skipping to change at page 11, line 38 skipping to change at page 12, line 4
| | | | | Bandwidth Report | | | | | | Bandwidth Report |
| | | | |------------------>| | | | | |------------------>|
| | | | | (for latest | | | | | | (for latest |
| | | | | Subs1 and Subs2 | | | | | | Subs1 and Subs2 |
| | | | | bandwidth) | | | | | | bandwidth) |
| | | | | | | | | | | |
Figure 4: Message Flow For Committed Bandwidth Reporting Figure 4: Message Flow For Committed Bandwidth Reporting
4. ANCP Messages 4. ANCP Messages
This section defines new ANCP messages and new usage of existing ANCP This section defines new ANCP messages and new usage of existing ANCP
messages as well as procedures associated with the use of these messages as well as procedures associated with the use of these
messages. messages.
Unless stated otherwise, receivers MUST ignore message contents that
are not supported by the set of capabilities negotiated between the
NAS and the Access Node.
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 resource-based admission control before
listed flows. replicating white-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 resource-based admission control before
specified in Multicast Replication Control messages. replicating flows 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.11. 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 direct the AN to
perform admission control for specific classes of flows. perform resource-based 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 resource-based admission control to be performed at the AN
listed flows, the NAS MUST include a copy of the White-List-CAC TLV on white-listed flows, the NAS MUST include a copy of the White-List-
in the Provisioning message. The White-List-CAC TLV MUST NOT be CAC TLV in the Provisioning message. The White-List-CAC TLV MUST NOT
provided unless the negotiated set of capabilities includes be 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 resource-based admission control to be performed at the AN
flows or on NAS-initiated flows, the NAS MUST include a copy of the on grey-listed flows or on NAS-initiated flows, the NAS MUST include
MRepCtl-CAC TLV in the Provisioning message. The MRepCtl-CAC TLV a copy of the MRepCtl-CAC TLV in the Provisioning message. The
MUST NOT be provided unless the negotiated set of capabilities MRepCtl-CAC TLV MUST NOT be provided unless the negotiated set of
includes NAS-initiated replication control or conditional access with capabilities includes NAS-initiated replication control or
grey lists. conditional access with 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. In keeping with the general rule stated in
TLV referring to any list type (white, black, or grey) that is not Section 4, the AN MUST ignore instances of the List-Action 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
existing multicast service profile subsequent to startup will cause existing multicast service profile subsequent to startup will cause
the AN to review the status of active flows on all ports to which the AN to review the status of active flows on all ports to which
that profile has been assigned. For further details, see Section 6. that profile has been assigned. For further details, see Section 6.
If the White-List-CAC and/or MRepCtl-CAC TLV is present in the If the White-List-CAC and/or MRepCtl-CAC TLV is present in the
Provisioning message and the respective associated capabilities have Provisioning message and the respective associated capabilities have
been negotiated, the AN prepares (or continues) to do connection been negotiated, the AN prepares (or continues) to do resource-based
admission control on the indicated class(es) of flow. If one or both admission control on the indicated class(es) of flow. If one or both
of these TLVs was present in an earlier Provisioning message but is of these TLVs was present in an earlier Provisioning message but is
absent in the latest message received, the AN ceases to do connection absent in the latest message received, the AN ceases to do resource-
admission control on the indicated class(es) of flow. based admission control on the indicated class(es) of flow.
The buffering time specified in an instance of the Report-Buffering- The buffering time specified in an instance of the Report-Buffering-
Time TLV applies to only to Committed Bandwidth Report messages Time TLV applies only to Committed Bandwidth Report messages
initiated after the new buffering time is received at the AN, not to initiated after the new buffering time is received at the AN, not to
any message already in the process of accumulation. any message already in the process of accumulation.
As indicated in [RFC6320], the AN MUST NOT reply to the Provisioning As indicated in [RFC6320], the AN MUST NOT reply to the Provisioning
message if it processed it successfully. If an error prevents message if it processed it successfully. If an error prevents
successful processing of the message content, the AN MUST return a successful processing of the message content, the AN MUST return a
Generic Response message as defined in [RFC6320], containing a Generic Response message as defined in [RFC6320], containing a
Status-Info TLV with the appropriate content describing the error. Status-Info TLV with the appropriate content describing the error.
For this purpose, the presence of a list type in a Multicast-Service- For this purpose, the presence of a list type in a Multicast-Service-
Profile TLV which was ignored because it was not supported by the Profile TLV which was ignored because it was not supported by the
skipping to change at page 14, line 38 skipping to change at page 15, line 6
As specified in [RFC6320], the NAS may send DSL line configuration As specified in [RFC6320], the NAS may send DSL line configuration
information to the AN ("ANCP based DSL Line Configuration" use case) information to the AN ("ANCP based DSL Line Configuration" use case)
using ANCP Port Management messages. See Section 7.3 of [RFC6320] using ANCP Port Management messages. See Section 7.3 of [RFC6320]
for the format of the Port Management message in that usage. for the format of the Port Management message in that usage.
This document specifies that the Port Management message MAY be used This document specifies that the Port Management message MAY be used
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 line
specified by the extension block. specified by the extension block, and in the case of white and
black lists, delegates policy-based admission control to the AN
for the specified access line and channels.
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. resource-based admission control at the access line.
When the Port Management message is used for this purpose: When the Port Management message is used for this purpose:
o the Function field in the Port Management message MUST be set to o the Function field in the Port Management message MUST be set to
8, "Configure Connection Service Data". 8, "Configure Connection Service Data".
o the message MUST include TLV(s) to identify the access line o the message MUST include TLV(s) to identify the access line
concerned. If the access line is a DSL loop, the line-identifying 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 TLV(s) MUST be as specified in Section 5.1.2 of [RFC6320]. For
non-DSL access lines, the appropriate alternative line-identifying non-DSL access lines, the appropriate alternative line-identifying
TLV(s) MUST be present. Line configuration data other than the TLV(s) MUST be present. Line configuration data other than the
two TLVs listed in the previous paragraph MAY be present. 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 line specified in
the message and with the multicast capabilities negotiated between the message and with the multicast capabilities negotiated between
the NAS and the AN. The NAS MAY send additional Port Management the NAS and the AN. The NAS MAY send additional Port Management
messages subsequent to startup, to update or, in the case of the messages subsequent to startup, to update or, in the case of the
Bandwidth-Allocation TLV, reset these parameters. If the NAS Bandwidth-Allocation TLV, reset these parameters. If the NAS
includes a Multicast-Service-Profile-Name TLV in the Port Management includes a Multicast-Service-Profile-Name TLV in the Port Management
message, the name MUST match a profile name provided in a Multicast- message, the name MUST match a profile name provided in a Multicast-
Service-Profile TLV in a prior Provisioning message. The NAS MUST Service-Profile TLV in a prior Provisioning message. The NAS MUST
NOT include a TLV unless it is supported by the set of multicast NOT include a TLV unless it is supported by the set of multicast
capabilities negotiated between the NAS and the AN. See Section 6 capabilities negotiated between the NAS and the AN. See Section 6
for further information. for further information.
4.2.2. Receiver Behaviour 4.2.2. Receiver Behaviour
If the Port Management message contains a Multicast-Service-Profile- If the Port Management message contains a Multicast-Service-Profile-
Name TLV, the AN associates the named profile with the specified Name TLV, the AN associates the named profile with the specified
Access Port. This association replaces any previous association. access line. This association replaces any previous association.
That is, a given Access Port is associated with at most one multicast That is, a given access line is associated with at most one multicast
service profile. The replacement of one multicast service profile service profile. The replacement of one multicast service profile
with another will cause the AN to review the status of all active with another will cause the AN to review the status of all active
flows on the target port. For further details see Section 6. flows on the target port. For further details see Section 6.
If the Port Management message contains a Bandwidth-Allocation TLV, If the Port Management message contains a Bandwidth-Allocation TLV,
the AN adopts this as the current value of its total multicast the AN adopts this as the current value of its total multicast
bandwidth limit for the target port. If the AN has already committed bandwidth limit for the target port. If the AN has already committed
multicast bandwidth exceeding the amount given in the Bandwidth- multicast bandwidth exceeding the amount given in the Bandwidth-
Allocation TLV, the AN SHOULD NOT discontinue any multicast streams Allocation TLV, the AN SHOULD NOT discontinue any multicast streams
in order to bring bandwidth down to within the new limit. However, in order to bring bandwidth down to within the new limit, unless such
the AN MUST NOT admit new multicast streams that are subject to action is required by local policy. However, the AN MUST NOT admit
admission control until it can do so within the limit specified by new multicast streams that are subject to admission control until it
the Bandwidth-Allocation TLV. can do so within the limit specified by 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 0x55, "Invalid TLV contents", the Error Message header indicates 0x55, "Invalid TLV contents", the Error Message
skipping to change at page 16, line 44 skipping to change at page 17, line 19
o a Command Code field; o a Command Code field;
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 0x0011 | 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:
1 - Add; 1 "Add";
2 - Delete; 2 "Delete";
3 - Delete All; 3 "Delete All";
4 - Admission Control Reject; 4 "Admission Control Reject";
5 - Conditional Access Reject; 5 "Conditional Access Reject";
6 - Admission Control and Conditional Access Reject. 6 "Admission Control and Conditional Access Reject".
Directives 4 through 6 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" (1). In Meaningful only when the Command Code is "Add" (1). In
that case, 0x00 indicates no flow accounting, 0x01 that case, 0 indicates flow accounting is disabled, 1
indicates that octet accounting for the flow is to indicates that octet accounting for the flow is requested.
commence. The Accounting field MUST be set to 0x00 for The sender MUST set the Accounting field to 0 and the
other Command Code values. receiver MUST ignore the Accounting field for 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 zeroes 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.10)
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 is omitted if the Command Code has value "Delete
"Delete All" (3). 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.
However, see the description of the Multicast Admission However, see the description of the Multicast Admission
Control message (Section 4.4). Unrecognized embedded TLVs Control message (Section 4.4). Unrecognized embedded TLVs
SHOULD be silently discarded. 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 Source-Specific message that would result in a swap from multicast Source-Specific
Multicast (SSM) flows 2001:DB8::1, FF34::2, to 2001:DB8::2, FF34::3 Multicast (SSM) flows 2001:DB8::1, FF34::2, to 2001:DB8::2, FF34::3
on the Target identified by the "Access Loop Circuit ID": on the Target identified by the "Access Loop Circuit ID":
skipping to change at page 18, line 16 skipping to change at page 18, line 38
Multicast Replication Control message/Command TLV. Multicast Replication Control message/Command TLV.
However, see the description of the Multicast Admission However, see the description of the Multicast Admission
Control message (Section 4.4). Unrecognized embedded TLVs Control message (Section 4.4). Unrecognized embedded TLVs
SHOULD be silently discarded. 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 Source-Specific message that would result in a swap from multicast Source-Specific
Multicast (SSM) flows 2001:DB8::1, FF34::2, to 2001:DB8::2, FF34::3 Multicast (SSM) flows 2001:DB8::1, FF34::2, to 2001:DB8::2, FF34::3
on the Target 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 (0x880C) | Length | | Type (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | MsgType=144 | 0x02 | Result Code | | Version | MsgType=144 | Res=2 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier = 0001 | | Partition ID | Transaction Identifier = 18 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length | |I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Target 0x1000 | Target TLV Length | | TLV 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 | | TLV Type = Command 0x0011 | Command TLV Length = 44 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=2 |Acctg = 0x00 | Reserved = 0x0000 | | Cmd Code = 2 | Acctg = 0 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = Multicast-Flow | TLV Length = 0x000C | | Type = Multicast-Flow 0x0019 | TLV Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 | | Flow Type = 2 | AddrFam = 2 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Multicast Group Address ~ ~ Multicast Group Address ~
| = FF34::2 | | = FF34::2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Source Address ~ ~ Source Address ~
| = 2001:DB8::1 | | = 2001:DB8::1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Command-TLV | Command-TLV Length = 0x0014 | | TLV Type = Command 0x0011 | Command-TLV Length = 44 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=1 |Acctg = 0x01 | Reserved = 0x0000 | | Cmd Code = 1 | Acctg = 1 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = Multicast-Flow | TLV Length = 0x000C | | Type = Multicast-Flow 0x0019 | TLV Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 | | Flow Type = 2 | AddrFam = 2 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = FF34::3 | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Multicast Group Address ~
| Source Address = 2001:DB8::2 | | = FF34::3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Multicast Group Address ~ ~ Source Address ~
| = FF34::3 | | = 2001:DB8::2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ 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
field to AckAll (0x2) or Nack (0x1) according to its requirements. field to AckAll (0x2) or Nack (0x1) according to its requirements.
The NAS MAY also send this message in response to a Multicast The NAS MAY also send this message in response to a Multicast
Admission Control message (defined in Section 4.4) received from the Admission Control message (defined in Section 4.4) received from the
AN to support the conditional access and admission control use case AN to support the conditional access and admission control use case
presented in [RFC5851] and summarized in Section 3.2. In that case, presented in [RFC5851] and summarized in Section 3.2. In that case,
the NAS MUST set the Result field to NAck (0x1). the NAS MUST set the Result field to NAck (0x1).
In either case, the sender MUST populate the Result Code field with In either case, the sender MUST populate the Result Code field with
the value 0x000 and the ANCP Transaction Identifier field with a the value 0 and the ANCP Transaction Identifier field with a unique
unique value, as described in Section 3.6.1.6 of [RFC6320]. value, as described in Section 3.6.1.6 of [RFC6320].
Each Multicast Replication Control Message MUST contain one or more Each Multicast Replication Control Message MUST contain one or more
commands, each encapsulated in its own Command TLV. The sender MUST commands, each encapsulated in its own Command TLV. The sender MUST
use a separate Command TLV for each distinct multicast flow. use a separate Command TLV for each distinct multicast flow.
When the order of processing of two commands does not matter, the When the order of processing of two commands does not matter, the
commands MUST be transmitted in separate Multicast Replication commands MUST be transmitted in separate Multicast Replication
Control messages. Control messages.
4.3.2. Receiver Behaviour 4.3.2. Receiver Behaviour
When successive commands (in the same or different messages) relate When successive commands (in the same or different messages) relate
to the same Target and multicast flow, the state of each feature to the same Target and multicast flow, the state of each feature
controlled or affected by attributes received in the Multicast controlled or affected by attributes received in the Multicast
Replication Control message, SHALL be as set by the last command or Replication Control message, SHALL be as set by the last command or
message referring to that target and flow and containing the message referring to that target and flow and containing the
controlling attribute. As an example, successive Multicast controlling attribute. As an example, successive Multicast
Replication Control messages containing add commands for a given port Replication Control messages containing add commands for a given port
and flow, but differing only in the Accounting field setting SHALL be and flow but differing only in the Accounting field, update the state
interpreted to mean that the state of the accounting feature is as of the accounting feature to what is set in the final command
set in the final command received, but all other features are as set received, but all other features are unaffected by the second
in the initial message. message.
If more than one Command TLV is present in a Multicast Replication If more than one Command TLV is present in a Multicast Replication
Control message, the AN MUST act on the commands in the order in Control message, the AN MUST act on the commands in the order in
which they are presented in the message. The AN SHALL assign a which they are presented in the message. The AN SHALL assign a
sequence number to each command in a given Multicast Replication sequence number to each command in a given Multicast Replication
Control message, starting from 0x01 for the first command. Control message, starting from 1 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 resource-based
control for Multicast Replication Control messages, then the AN MUST admission control for Multicast Replication Control messages, then
perform admission control before replicating the flow. If the the AN MUST perform admission control before replicating the flow.
admission control check fails, the AN MUST treat the failure as an If the admission control check fails, the AN MUST treat the failure
error as described below. The appropriate Result Code value for the as an error as described below. The appropriate Result Code value
response is 0x013 "Out of resources". for the response is 0x13 "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 0, 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.
If the AN processes the complete Multicast Replication Control If the AN processes the complete Multicast Replication Control
message successfully and the Result field of the Multicast message successfully and the Result field of the Multicast
Replication Control message was set to Nack (0x1), the AN MUST NOT Replication Control message was set to Nack (0x1), the AN MUST NOT
respond to the message. respond to the message.
The processing/execution of multiple commands contained in a single The processing/execution of multiple commands contained in a single
skipping to change at page 21, line 20 skipping to change at page 21, line 38
0x64 Command error. 0x64 Command error.
Where detected: ANCP agent at the AN. Where detected: ANCP agent at the AN.
Further description: an invalid command code has been received. Further description: an invalid command code has been received.
Required additional information in the message: see below. Required additional information in the message: see below.
Target: ANCP agent at the NAS. Target: ANCP agent at the NAS.
Action RECOMMENDED for the receiving ANCP agent: Correct the Action RECOMMENDED for the receiving ANCP agent: Report the
error and re-send the request, if possible. Otherwise, report error to the control application with an indication of the
the error to the control application with an indication of the
erroneous information associated with the invalid TLV(s). erroneous information associated with the invalid TLV(s).
0x65 Invalid flow address. 0x65 Invalid flow address.
Where detected: ANCP agent at the AN. Where detected: ANCP agent at the AN.
Further description: either inconsistent flow address Further description: either inconsistent flow address
information has been provided or the address family is information has been provided or the address family is
unsupported. unsupported.
Required additional information in the message: see below. Required additional information in the message: see below.
Target: ANCP agent at the NAS. Target: ANCP agent at the NAS.
Action RECOMMENDED for the receiving ANCP agent: correct the Action RECOMMENDED for the receiving ANCP agent: Report the
error and re-send the request, if possible. Otherwise, report error to the control application with an indication of the
the error to the control application with an indication of the
erroneous information associated with the invalid TLV(s). erroneous information associated with the invalid TLV(s).
0x66 Multicast flow does not exist. 0x66 Multicast flow does not exist.
Where detected: control application at the AN. Where detected: control application at the AN.
Further description: the NAS has attempted to delete a flow Further description: the NAS has attempted to delete a flow
that is not active on the given access line. that is not active on the given access line.
Required additional information in the message: see below. Required additional information in the message: see below.
skipping to change at page 23, line 14 skipping to change at page 23, line 31
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
Multicast Replication Control message, with the following additions: Multicast Replication Control message, with the following addition:
o a Request-Source-IP TLV MAY be appended to the Command TLV as an
additional embedded TLV;
o similarly, a Request-Source-MAC TLV MAY be appended to the Command o a Subs-Session-ID TLV as defined in Section 5.9 MAY be appended to
TLV as an additional embedded TLV. the Command TLV as an additional embedded TLV. The need for this
TLV depends on what type of subscriber session identifier the
operator is using to retrieve the subscriber profile information
from AAA. Some of the types identified by [TR-146] requirement
R43 are covered by the contents of the Target TLV.
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 "Add" (1) when the message
conveys a Join , to "2 - Delete" when the message conveys a Leave conveys a Join , to "Delete" (2) when the message conveys a Leave
and to "3 - Delete All" when the message conveys a Leave of all and to "Delete All" (3) when the message conveys a Leave of all
channels (on the target); 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 3, the Multicast-Flow TLV is meaningless When the Command Code is 3, the Multicast-Flow TLV is omitted.
and MUST be omitted.
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
(e.g., IGMP/MLD Join/Leave) that triggered the AN to include the
corresponding Command TLV in the Admission Control message. If it
appears more than once, only the first instance is considered
meaningful and the other instances are ignored.
o the Request-Source-MAC embedded TLV MAY be included by the AN to o Depending on local configuration, the Subs-Session-Identifier
convey the MAC address of the sender of the join/leave message embedded TLV MAY be included by the AN. The content of this TLV
(e.g., IGMP/MLD Join/Leave) that triggered the AN to include the depends on local practice.
corresponding Command TLV in the Admission Control message. If it
appears more than once, only the first instance is considered
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 "2 o if the directive in the Multicast Admission Control message is
- Delete" or "3 - Delete All" and is processed correctly by the "Delete" (2) or "Delete All" (3) and is processed correctly by the
NAS, the NAS MUST NOT generate any ANCP message in response to the NAS, the NAS MUST NOT generate any ANCP message in response to the
Multicast Admission Control message; Multicast Admission Control message;
o if the directive in the Multicast Admission Control message is "1 o if the directive in the Multicast Admission Control message is
- Add" and is accepted by the NAS, the NAS MUST generate a "Add" (1) 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 with a unique value, as described * MUST contain a Transaction ID with a unique value, as described
in Section 3.6.1.6 of [RFC6320]; in Section 3.6.1.6 of [RFC6320];
* 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 "1 o if the directive in the Multicast Admission Control message is
- Add", is processed correctly but not accepted by the NAS (i.e., "Add" (1), is processed correctly but not accepted by the NAS
it does not pass the admission control or conditional access (i.e., it does not pass the conditional access and admission
check), the NAS MAY generate a Multicast Replication Control control check), the NAS MAY generate a Multicast Replication
message in response to the Multicast Admission Control message. Control message in response to the Multicast Admission Control
This optional message can be used by the AN to maintain statistics message. This optional message can be used by the AN to maintain
about admission control rejections. When used in this situation, statistics about admission control rejections. When used in this
the Multicast Replication Control message: situation, the Multicast Replication Control message:
* MUST contain a Result set to 0x0; * MUST contain a Result set to 0x0;
* MUST contain a Transaction ID with a unique value, as described * MUST contain a Transaction ID with a unique value, as described
in Section 3.6.1.6 of [RFC6320]; in Section 3.6.1.6 of [RFC6320];
* 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 "4 - TLV and Command TLV) but with a Command Code set to "Admission
Admission Control Reject", "5 - Conditional Access Reject", or Control Reject" (4), "Conditional Access Reject" (5), or
"6 - Admission Control and Conditional Access Reject" as "Admission Control and Conditional Access Reject" (6) as
applicable. 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
skipping to change at page 26, line 41 skipping to change at page 26, line 44
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 0, and the Bandwidth Allocation TLV MUST contain the value of
of the currently allocated amount of delegated bandwidth as the the currently allocated amount of delegated bandwidth as the
responder views it. responder views it.
The following cases indicate that the sender holds a different view The following cases indicate that the sender holds a different view
of the amount of delegated bandwidth from the receiver: of the amount of delegated bandwidth from the receiver:
o the NAS receives a request where the required amount is less than o the NAS receives a request where the required amount is less than
its view of the current amount of delegated bandwidth; its view of the current amount of delegated bandwidth;
o the AN receives a request where the required amount is greater o the AN receives a request where the required amount is greater
than its view of the current amount of delegated bandwidth. than its view of the current amount of delegated bandwidth.
skipping to change at page 31, line 45 skipping to change at page 31, line 43
the NAS or by the AN to retrieve the peer's view of the amount of the NAS or by the AN to retrieve the peer's view of the amount of
delegated bandwidth. The request contains one TLV: delegated bandwidth. The request contains one TLV:
o a Target TLV designating the access line for which the information o a Target TLV designating the access line for which the information
is requested. is requested.
4.7.1. Sender Behaviour 4.7.1. Sender Behaviour
The sender MUST set the Result field in the header of the Delegated The sender MUST set the Result field in the header of the Delegated
Bandwidth Query Request message to AckAll (0x2). The Result Code Bandwidth Query Request message to AckAll (0x2). The Result Code
value MUST be set to 0x000. The sender MUST populate the ANCP value MUST be set to 0. The sender MUST populate the ANCP
Transaction Identifier field with a unique value, as described in Transaction Identifier field with a unique value, as described in
Section 3.6.1.6 of [RFC6320]. Section 3.6.1.6 of [RFC6320].
4.7.2. Receiver Behaviour 4.7.2. Receiver Behaviour
If the AN or NAS receives a valid Delegated Bandwidth Query Request If the AN or NAS receives a valid Delegated Bandwidth Query Request
message, it MUST respond with a Delegated Bandwidth Query Response message, it MUST respond with a Delegated Bandwidth Query Response
message. The Result field in the header of the response MUST be set message. The Result field in the header of the response MUST be set
to Success (0x3). The Result Code field MUST be set to 0x000. The to Success (0x3). The Result Code field MUST be set to 0. The
Transaction-Id field MUST be copied from the request message. The Transaction-Id field MUST be copied from the request message. The
body of the response MUST contain the Target TLV, copied from the body of the response MUST contain the Target TLV, copied from the
request message. Finally, the body of the response MUST contain a request message. Finally, the body of the response MUST contain a
Bandwidth-Allocation TLV, containing the current amount of delegated Bandwidth-Allocation TLV, containing the current amount of delegated
bandwidth from the point of view of the receiver of the request. bandwidth from the point of view of the receiver of the request.
If the contents of the Delegated Bandwidth Query Request message are If the contents of the Delegated Bandwidth Query Request message are
in error, the receiver MUST return a Delegated Bandwidth Query in error, the receiver MUST return a Delegated Bandwidth Query
Response message with the Result field in the header set to Failure Response message with the Result field in the header set to Failure
(0x3). The Result Code field MUST be set to the value that indicates (0x3). The Result Code field MUST be set to the value that indicates
skipping to change at page 34, line 32 skipping to change at page 34, line 32
access 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.10.
The NAS MAY include multiple Target TLVs or multiple Multicast-Flow The NAS MAY include multiple Target TLVs or multiple Multicast-Flow
TLVs in the Multicast Flow Query Request, but MUST NOT include both TLVs in the Multicast Flow Query Request, but MUST NOT include both
Target and Multicast-Flow TLVs in the same message. Target and Multicast-Flow TLVs in the same message.
To retrieve the AN's view of all of the multicast flows currently To retrieve the AN's view of all of the multicast flows currently
active on each port of the AN, the NAS MUST send a Multicast Flow active on each port of the AN, the NAS MUST send a Multicast Flow
Query Request which does not contain any instance of the Target TLV Query Request which does not contain any instance of the Target TLV
or the Multicast-Flow TLV. or the Multicast-Flow TLV.
4.9.2. Receiver Behaviour 4.9.2. Receiver Behaviour
The AN MUST respond to a Multicast Flow Query Request message that The AN MUST respond to a Multicast Flow Query Request message that
has a valid format and a valid content with a Multicast Flow Query has a valid format and a valid content with a Multicast Flow Query
Response message. The Result field in the response MUST be set to Response message. The Result field in the response MUST be set to
Success (0x3). The Result Code field MUST be set to 0x000. The Success (0x3). The Result Code field MUST be set to 0. The
Transaction-Id field MUST be copied from the request. Transaction-Id field MUST be copied from the request.
If the Multicast Flow Query Request contained one (or more) Target If the Multicast Flow Query Request contained one (or more) Target
TLVs, the AN MUST include, for each of these Target TLVs, the TLVs, the AN MUST include, for each of these Target TLVs, the
following set of TLVs: following set of TLVs:
o Target TLV. This MUST be identical to the Target TLV in the o Target TLV. This MUST be identical to the Target TLV in the
received Multicast Flow Query Request message. received Multicast Flow Query Request message.
o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once
skipping to change at page 36, line 26 skipping to change at page 36, line 26
4.10. Committed Bandwidth Report Message 4.10. Committed Bandwidth Report Message
This section describes the Committed Bandwidth Report message, which This section describes the Committed Bandwidth Report message, which
is sent from the AN to the NAS to report the most recent amount of is sent from the AN to the NAS to report the most recent amount of
multicast bandwidth usage committed to one or more access lines. multicast bandwidth usage committed to one or more access lines.
The Message Type for the Committed Bandwidth Report message is 150. The Message Type for the Committed Bandwidth Report message is 150.
The Committed Bandwidth Report message contains one or more instances The Committed Bandwidth Report message contains one or more instances
of the Committed-Bandwidth TLV, as described in Section 5.13. of the Committed-Bandwidth TLV, as described in Section 5.12.
4.10.1. Sender Behaviour 4.10.1. Sender Behaviour
The sender of a Committed Bandwidth Report message MUST set the The sender of a Committed Bandwidth Report message MUST set the
Result field to Ignore (0x0). The Result Code field MUST be set to Result field to Ignore (0x0). The Result Code field MUST be set to
0x000. The sender MUST populate the ANCP Transaction Identifier 0x000. The sender MUST populate the ANCP Transaction Identifier
field with a unique value, as described in section 3.6.1.6 of field with a unique value, as described in section 3.6.1.6 of
[RFC6320]. [RFC6320].
Each instance of the Committed-Bandwidth TLV included in the message Each instance of the Committed-Bandwidth TLV included in the message
skipping to change at page 37, line 30 skipping to change at page 37, line 30
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 | | Mcast-Service-Profile 0x0013 | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast-Service-Profile-Name TLV | | Multicast-Service-Profile-Name TLV |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| List-Action TLV | | List-Action TLV |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 38, line 21 skipping to change at page 38, line 21
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 which 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = MSP Name | TLV Length | | Mcast-Svc-Profile-Name 0x0018 | 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 0x0018. o The Multicast-Service-Profile-Name TLV Type is 0x0018.
skipping to change at page 39, line 18 skipping to change at page 39, line 18
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 0x0021 | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Operation | List Type | Reserved | | Operation | List Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Family | Number of flow fields | | Address Family | Number of flow fields |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast flow fields | | Multicast flow fields |
...... ......
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Family | Number of flow fields | | Address Family | Number of flow fields |
skipping to change at page 39, line 48 skipping to change at page 39, line 48
o The List-Action TLV Type is 0x0021. 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 * 1 "Add": the multicast flow fields are to be added to the list.
list.
* Delete (0x02): the multicast flow fields are to be removed from * 2 "Delete": 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,
it is necessary to remove the entire entry and add back the it is necessary to remove the entire entry and add back the
remaining partial range(s). remaining partial range(s).
* Replace (0x03): the multicast flow fields replace the existing * 3 "Replace": the multicast flow fields replace the existing
contents of the list. contents of the list.
o List Type: the list type being modified by this List-Action. The o List Type: the list type being modified by this List-Action. The
possible values are White (0x01), Black (0x02), or Grey (0x03). possible values are 1 "White", 2 "Black", or 3 "Grey".
o Reserved: a sender MUST set this field to 0x0000. A receiver MUST o Reserved: a sender MUST set this field to zeroes. A receiver MUST
ignore the contents of this field. ignore the contents of this field.
o Address Family: the IP version of the set of multicast flow fields o Address Family: the IP version of the set of multicast flow fields
that follow, encoded according to [PIMreg]. Possible values are that follow, encoded according to [PIMreg]. Possible values are 1
0x0001 (IPv4) or 0x0002 (IPv6). Either an IPv4 list or an IPv6 "IPv4" or 2 "IPv6". Either an IPv4 list or an IPv6 list or both
list or both MAY be present in the List-Action TLV. MAY be present in the List-Action TLV.
o Number of flow fields: the number of multicast flow fields of the o Number of flow fields: the number of multicast flow fields of the
given address family which follow. given address family which follow.
o Multicast flow field: a field identifying one or more multicast o Multicast flow field: a field identifying one or more multicast
flows. It consists of an 8-bit group address prefix length, an flows. It consists of an 8-bit group address prefix length, an
8-bit source address prefix length, a 0-16 octet group prefix, and 8-bit source address prefix length, a 0-16 octet group prefix, and
a 0-16 octet source prefix, as shown in Figure 9. a 0-16 octet source prefix, as shown in Figure 9.
Each multicast flow field refers either to a Source-Specific Each multicast flow field refers either to a Source-Specific
skipping to change at page 40, line 43 skipping to change at page 41, line 5
The scope of the designation may be broadened to multiple channels or The scope of the designation may be broadened to multiple channels or
groups through use of prefix length values smaller than the total groups through use of prefix length values smaller than the total
address length for the given address family. Multicast flow fields address length for the given address family. Multicast flow fields
MUST be placed consecutively within the embedded TLV without MUST be placed consecutively within the embedded TLV without
intervening padding except to round out individual addresses to the intervening padding except to round out individual addresses to the
nearest octet boundary. nearest octet boundary.
A multicast flow field consists of two single-octet prefix lengths A multicast flow field consists of two single-octet prefix lengths
followed by zero to two prefix values as shown in Figure 9: followed by zero to two prefix values as shown in Figure 9:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Group PrefLen | | Group PrefLen |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Source PrefLen| | Source PrefLen|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Group Prefix (multicast) (0 to 16 octets) | | Group Prefix (multicast) (0 to 16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Prefix (unicast, SSM only) (0 to 16 octets) | | Source Prefix (unicast, SSM only) (0 to 16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9: Organization of a Single Multicast Flow Field Figure 9: Organization of a Single Multicast Flow Field
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 0 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 0 is provided for a particular
particular prefix length, the corresponding prefix MUST be omitted prefix length, the corresponding prefix MUST be omitted from the
from the field contents. field contents.
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
in a Status-Info TLV, in a Generic Response reporting a failed in a Status-Info TLV, in a Generic Response reporting a failed
command in 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 | | Type = Sequence-Number 0x0022 | 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 0x0022. o The Sequence-Number TLV Type is 0x0022.
o TLV length is 0x0004. o TLV length is 4.
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
The Bandwidth-Allocation TLV is used to indicate the total amount of The Bandwidth-Allocation TLV is used to indicate the total amount of
video bandwidth delegated to the AN for multicast admission control video bandwidth delegated to the AN for multicast admission control
for a given access line, in kilobits per second. The TLV has the for a given access line, in kilobits per second. The TLV has the
format shown in Figure 11. format shown in Figure 11.
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 = BW-Allocation | TLV Length = 4 | | Bandwidth-Allocation 0x0015 | 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 0x0015. o The Bandwidth-Allocation TLV Type is 0x0015.
skipping to change at page 42, line 47 skipping to change at page 43, line 8
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 | | Type = White-List-CAC 0x0024 | 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 0x0024. 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.
skipping to change at page 43, line 21 skipping to change at page 43, line 31
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
illustrated in Figure 13. illustrated in Figure 13.
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 0x0025 | 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 0x0025. 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.
skipping to change at page 43, line 49 skipping to change at page 44, line 10
"Preferred amount" field indicates the adjustment the requestor would "Preferred amount" field indicates the adjustment the requestor would
prefer to have, if possible. Section 4.5 discusses the required prefer to have, if possible. Section 4.5 discusses the required
relationships between the "Required amount", "Preferred amount", and relationships between the "Required amount", "Preferred amount", and
current values of total bandwidth allocated to the AN. current values of total bandwidth allocated to the AN.
The Bandwidth-Request TLV has the format shown in Figure 14. The Bandwidth-Request TLV has the format shown in Figure 14.
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 = Bandwidth-Request | TLV Length = 8 | | Type=Bandwidth-Request 0x0016 | TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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:
skipping to change at page 44, line 24 skipping to change at page 44, line 34
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.
Presented as a 32-bit binary value, most significant bit first. Presented as a 32-bit binary value, most significant bit first.
5.9. Request-Source-IP TLV 5.9. Subs-Session-Id TLV
The Request-Source-IP TLV provides the IP address of the entity that
originated a specific request to join or leave a multicast channel.
The TLV is illustrated in Figure 15.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = Request-Source-IP | TLV length = 4 or 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 15: Request-Source-IP TLV
The Request-Source-IP TLV contains the following fields:
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 Unicast address: IP address of the source of a multicast flow join
request, in network byte order.
5.10. Request-Source-MAC TLV The Subs-Session-Id TLV provides a subscriber session identifier for
The Request-Source-MAC TLV provides the MAC address of the entity the entity that originated a specific request to join or leave a
that originated a specific request to join or leave a multicast multicast channel. The subscriber session identifier is a value
channel. The TLV is illustrated in Figure 16. derived according to local policy from one of the types specified in
[TR-146] requirement R43. The TLV is illustrated in Figure 15.
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=Request-Source-MAC | TLV Length = 6 or 8 | | Type = Subs-Session-Id 0x0092 | TLV length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | Value |
+-+-+- IEEE MAC Address +-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 16: Request-Source-MAC TLV Figure 15: Subs-Session-Id TLV
The Request-Source-MAC TLV contains the following fields:
o The Request-Source-MAC TLV Type is 0x0093. The Subs-Session-Id TLV contains the following fields:
o TLV length is either 6 octets (MAC-48 or EUI-48) or 8 octets o The Subs-Session-Id TLV Type is 0x0092.
(EUI-64).
o IEEE MAC Address: MAC address of the device originating the o TLV length depends on the type of identifier used.
request to join a multicast flow. Within the address, bytes and
bits respectively shall be ordered from most to least significant,
consistently with [IEEE48] for MAC-48 and EUI-48, and with
[IEEE64] for EUI-64.
EUI-48 and EUI-64 are registered trademarks of the IEEE. o Value is the configured value of the identifier.
5.11. Multicast-Flow TLV 5.10. Multicast-Flow TLV
The Multicast-Flow TLV specifies a multicast flow in terms of its The Multicast-Flow TLV specifies a multicast flow in terms of its
multicast group address and, if applicable, its unicast source multicast group address and, if applicable, its unicast source
address. It is illustrated in Figure 17. address. It is illustrated in Figure 16.
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 = Multicast-Flow | TLV Length | | Type = Multicast-Flow 0x0019 | TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Type | Addr Family | Reserved | | Flow Type | Addr Family | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 16: 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 0x0019. 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 Source- o Flow Type: 1 "Any Source Multicast (ASM)", 2 "Source-Specific
Specific Multicast (SSM). 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]). 1 indicates IPv4, 2 indicates IPv6.
o Reserved: MUST be set to 0x0000 by the sender and MUST be ignored o Reserved: MUST be set to zeroes 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
address (see [RFC5384]). The applicability of PIM attributes address (see [RFC5384]). The applicability of PIM attributes
in the context of ANCP is for further study. in the context of ANCP is for further study.
o Multicast Group Address: a multicast group address within the o Multicast Group Address: a multicast group address within the
given address family. The group address MUST always be present. given address family. The group address MUST always be present.
o Unicast Source Address: unicast address within the given address o Unicast Source Address: unicast address within the given address
family. If the Flow Type is 0x01 (ASM), a source address MUST NOT family. If the Flow Type is "ASM" (1), a source address MUST NOT
be present. If the Flow Type is 0x02 (SSM), a source address MUST be present. If the Flow Type is "SSM" (2), a source address MUST
be present. be present.
5.12. Report-Buffering-Time TLV 5.11. Report-Buffering-Time TLV
The Report-Buffering-Time TLV provides the time for which a Committed The Report-Buffering-Time TLV provides the time for which a Committed
Bandwidth Report message must be held with the intention of Bandwidth Report message must be held with the intention of
accumulating multiple reports of changed committed multicast accumulating multiple reports of changed committed multicast
bandwidth in one report, to reduce the volume of messages sent to the bandwidth in one report, to reduce the volume of messages sent to the
NAS. For further information see Section 6.2.2. The TLV is NAS. For further information see Section 6.2.2. The TLV is
illustrated in Figure 18. illustrated in Figure 17.
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=Report-Buffering-Time | TLV Length = 4 | | Report-Buffering-Time 0x0094 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Buffering Time (ms) | | Buffering Time (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 18: Report-Buffering-Time TLV
Figure 17: 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 0x0094. 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.12. 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
to it. The TLV is illustrated in Figure 19. to it. The TLV is illustrated in Figure 18.
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=Committed-Bandwidth | TLV Length (variable) | | Committed-Bandwidth 0x0095 | TLV Length (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Committed Multicast Bandwidth (kbits/s) | | Committed Multicast Bandwidth (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+- Target TLV +-+-+-+ ~ Target TLV ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 19: Committed-Bandwidth TLV Figure 18: 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 0x0095. 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.
skipping to change at page 48, line 30 skipping to change at page 48, line 13
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
(according to the tables in Section 6.1) by the negotiated set of
multicast capabilities, the appropriate response is to return a
Generic Response message indicating Failure (0x4) with an appropriate
code value. The body of the message MUST contain a Status-Info 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.
In addition to the elements listed below, implementation of the In addition to the elements listed below, implementation of the
Target TLV (Section 4.3 of [RFC6320]) is REQUIRED for all of the Target TLV (Section 4.3 of [RFC6320]) is REQUIRED for all of the
skipping to change at page 49, line 4 skipping to change at page 48, line 26
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.
In addition to the elements listed below, implementation of the In addition to the elements listed below, implementation of the
Target TLV (Section 4.3 of [RFC6320]) is REQUIRED for all of the Target TLV (Section 4.3 of [RFC6320]) is REQUIRED for all of the
capabilities specified in this document. capabilities specified in this document.
6.1.1. Protocol Requirements For NAS-Initiated Replication 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. Additionally, implementation of replication multicast capability. Additionally, implementation of
the Multicast Replication Control message requires implementation of the Multicast Replication Control message requires implementation of
the Command TLV (Section 4.4 of [RFC6320] with additional details in the Command TLV (Section 4.4 of [RFC6320] with additional details in
Section 4.3 of this document). 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- | | Section 4.2 | Port Management message with Bandwidth-Allocation |
| | 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 | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | messages | | | |
| | | | Section 5.4 | Sequence 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.10 | 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 committed multicast Section 5 that MUST be implemented to support the committed multicast
bandwidth reporting 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 | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | messages | | | |
| | | | Section 5.11 | Report-Buffering-Timer TLV |
| Section 5.12 | Report-Buffering-Timer TLV | | | |
| | | | Section 5.12 | Committed-Bandwidth TLV |
| Section 5.13 | Committed-Bandwidth TLV | | | |
| | | | Section 5.10 | Multicast-Flow TLV |
| Section 5.11 | Multicast-Flow TLV | +--------------+----------------------------------------------------+
+-----------------+-------------------------------------------------+
Table 2: Protocol Requirements For Committed Multicast Bandwidth Table 2: Protocol Requirements For Committed Multicast Bandwidth
Reporting Reporting
6.1.3. Protocol Requirements For Conditional Access With White and 6.1.3. Protocol Requirements For Conditional Access With White and
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 Multicast-Service- | | Section | Provisioning message with Multicast-Service-Profile |
| | Profile TLV, white and black lists only, and | | 4.1 | TLV, white and black lists only, and White-List-CAC |
| | White-List-CAC TLV | | | TLV |
| | | | | |
| Section 4.2 | Port Management message with Multicast-Service- | | Section | Port Management message with Multicast-Service- |
| | Profile-Name and Bandwidth-Allocation TLVs. | | 4.2 | Profile-Name and Bandwidth-Allocation TLVs. |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section | Multicast Flow Query Request and Response messages |
| | | | 4.9 | |
| Section 5.1 | Multicast-Service-Profile TLV | | | |
| | | | Section | Multicast-Service-Profile TLV |
| Section 5.2 | Multicast-Service-Profile-Name TLV | | 5.1 | |
| | | | | |
| Section 5.3 | List-Action TLV, white and black lists only | | Section | Multicast-Service-Profile-Name TLV |
| | | | 5.2 | |
| Section 5.5 | Bandwidth-Allocation TLV | | | |
| | | | Section | List-Action TLV, white and black lists only |
| Section 5.6 | White-List-CAC TLV | | 5.3 | |
| | | | | |
| Section 5.11 | Multicast-Flow TLV | | Section | Bandwidth-Allocation TLV |
+--------------+----------------------------------------------------+ | 5.5 | |
| | |
| Section | White-List-CAC TLV |
| 5.6 | |
| | |
| Section | Multicast-Flow TLV |
| 5.10 | |
+-----------+-------------------------------------------------------+
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. Additionally, implementation with grey lists multicast capability. Additionally, implementation
of the Multicast Replication Control message requires implementation of the Multicast Replication Control message requires implementation
of the Command TLV (Section 4.4 of [RFC6320] with additional details of the Command TLV (Section 4.4 of [RFC6320] with additional details
in Section 4.3 of this document). in Section 4.3 of this document).
+-----------+-------------------------------------------------------+
| Reference | Protocol Element |
+-----------+-------------------------------------------------------+
| Section | Provisioning message with Multicast-Service-Profile |
| 4.1 | TLV, grey lists only, and MRepCtl-CAC TLV |
| | |
| Section | Port Management message with Multicast-Service- |
| 4.2 | Profile-Name and Bandwidth-Allocation TLVs. |
| | |
| Section | Multicast Replication Control message |
| 4.3 | |
| | |
| Section | Multicast Admission Control Message |
| 4.4 | |
| | |
| Section | Multicast Flow Query Request and Response messages |
| 4.9 | |
| | |
| Section | Multicast-Service-Profile TLV, grey lists only |
| 5.1 | |
| | |
| Section | Multicast-Service-Profile-Name TLV |
| 5.2 | |
| | |
| Section | List-Action TLV, grey lists only |
| 5.3 | |
| | |
| Section | Sequence Number TLV |
| 5.4 | |
| | |
| Section | Bandwidth-Allocation TLV |
| 5.5 | |
| | |
| Section | MRepCtl-CAC TLV |
| 5.7 | |
| | |
| Section | Subs-Session-Id TLV |
| 5.9 | |
| | |
| Section | Multicast-Flow TLV |
| 5.10 | |
+-----------+-------------------------------------------------------+
Table 4: Protocol Requirements For Conditional Access with Grey Lists
6.1.5. Protocol Requirements For Delegated Bandwidth
Table 5 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the delegated bandwidth
multicast capability.
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Section 4.1 | Provisioning message with Multicast-Service- | | Section 4.2 | Port Management message with Bandwidth-Allocation |
| | Profile TLV, grey lists only, and MRepCtl-CAC TLV | | | TLV. |
| | |
| Section 4.2 | Port Management message with Multicast-Service- |
| | Profile-Name and Bandwidth-Allocation TLVs. |
| | |
| Section 4.3 | Multicast Replication Control message |
| | |
| Section 4.4 | Multicast Admission Control Message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.5 | Bandwidth Reallocation Request Message |
| | | | | |
| Section 5.1 | Multicast-Service-Profile TLV, grey lists only | | Section 4.6 | Bandwidth Transfer Message |
| | | | | |
| Section 5.2 | Multicast-Service-Profile-Name TLV | | Section 4.7 | Delegated Bandwidth Query Request Message |
| | | | | |
| Section 5.3 | List-Action TLV, grey lists only | | Section 4.8 | Delegated Bandwidth Query Response Message |
| | | | | |
| Section 5.4 | Sequence Number TLV | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section 5.5 | Bandwidth-Allocation TLV | | Section 5.5 | Bandwidth-Allocation TLV |
| | | | | |
| Section 5.7 | MRepCtl-CAC TLV | | Section 5.8 | Bandwidth-Request TLV |
| | |
| Section 5.9 | Request-Source-IP TLV |
| | |
| Section 5.10 | Request-Source-MAC TLV |
| | | | | |
| Section 5.11 | Multicast-Flow TLV | | Section 5.10 | Multicast-Flow TLV |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
Table 4: Protocol Requirements For Conditional Access with Grey Lists
6.1.5. Protocol Requirements For Delegated Bandwidth
Table 5 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the delegated bandwidth
multicast capability.
+-----------------+-------------------------------------------------+
| Reference | Protocol Element |
+-----------------+-------------------------------------------------+
| Section 4.2 | Port Management message with Bandwidth- |
| | Allocation TLV. |
| | |
| Section 4.5 | Bandwidth Reallocation Request Message |
| | |
| Section 4.6 | Bandwidth Transfer Message |
| | |
| Section 4.7 | Delegated Bandwidth Query Request Message |
| | |
| Section 4.8 | Delegated Bandwidth Query Response Message |
| | |
| Section 4.9 | Multicast Flow Query Request and Response |
| | messages |
| | |
| Section 5.5 | Bandwidth-Allocation TLV |
| | |
| Section 5.8 | Bandwidth-Request TLV |
| | |
| Section 5.11 | Multicast-Flow TLV |
+-----------------+-------------------------------------------------+
Table 5: Protocol Requirements For Delegated Bandwidth Table 5: Protocol Requirements For Delegated Bandwidth
6.2. Capability-Specific Procedures for Providing Multicast Service 6.2. Capability-Specific Procedures for Providing Multicast Service
This section describes multicast service procedures for each This section describes multicast service procedures for each
capability as if it were the only multicast capability within the capability as if it were the only multicast capability within the
negotiated set. Procedures involving combinations of multicast negotiated set. Procedures involving combinations of multicast
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
skipping to change at page 53, line 4 skipping to change at page 53, line 47
negotiated set. Procedures involving combinations of multicast negotiated set. Procedures involving combinations of multicast
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 resource-based admission control for NAS-
In this case, it MUST NOT include the MRepCtl-CAC TLV in a initiated replication. In this case, it MUST NOT include the
Provisioning message sent to the AN. Alternatively, the NAS MAY MRepCtl-CAC TLV in a Provisioning message sent to the AN.
enable admission control at the AN for NAS-initiated replication. To Alternatively, the NAS MAY enable resource-based admission control at
do this, it MUST include the MRepCtl-CAC TLV in a Provisioning the AN for NAS-initiated replication. To do this, it MUST include
message sent to the AN and it MUST also include a Bandwidth- the MRepCtl-CAC TLV in a Provisioning message sent to the AN and it
Allocation TLV in a Port Management message for each access line. MUST also include a Bandwidth-Allocation TLV in a Port Management
message for each access line.
6.2.1.2. Multicast Service Procedures 6.2.1.2. Multicast Service Procedures
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
skipping to change at page 55, line 11 skipping to change at page 56, line 5
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 resource-based admission control at the
listed flows. To do this, it MUST send a Provisioning message as AN for white-listed flows. To do this, it MUST send a Provisioning
described in Section 4.1, which includes the White-List-CAC TLV and message as described in Section 4.1, which includes the White-List-
it MUST provide a multicast bandwidth allocation for each access line CAC TLV and it MUST provide a multicast bandwidth allocation for each
by including a Bandwidth-Allocation TLV in a Port Management message. access line 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 resource-based admission control on the AN as described in the
a white-listed flow would cause the amount of committed multicast previous section, but a white-listed flow would cause the amount of
bandwidth to exceed the provisioned limit, the request MUST be committed multicast bandwidth to exceed the provisioned limit, the
discarded. The AN replicates flows passing these checks to the request MUST be discarded. The AN replicates flows passing these
access line. checks to the 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
skipping to change at page 56, line 37 skipping to change at page 57, line 34
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 resource-based admission control for grey-listed
case, the NAS MUST NOT include the MRepCtl-CAC TLV in a Provisioning flows. In that case, the NAS MUST NOT include the MRepCtl-CAC TLV in
message sent to the AN. Alternatively, the NAS MAY enable admission a Provisioning message sent to the AN. Alternatively, the NAS MAY
control at the AN for grey-listed flows. To do this, it MUST include enable resource-based admission control at the AN for grey-listed
the MRepCtl-CAC TLV in a Provisioning message sent to the AN and MUST flows. To do this, it MUST include the MRepCtl-CAC TLV in a
also provide a Bandwidth-Allocation TLV in a Port Management message Provisioning message sent to the AN and MUST also provide a
for each access line. Bandwidth-Allocation TLV in a Port Management message 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 be configured to add a subscriber session identifier as described in
address. [TR-146] requirement R43.
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
Section 4.3.1. Section 4.3.1.
When the AN receives the Multicast Replication Control request, it When the AN receives the Multicast Replication Control request, it
performs admission control if admission control has been enabled as performs resource-based admission control if that has been enabled as
described in the previous section. If admitting the flow would cause described in the previous section. If admitting the flow would cause
the committed multicast bandwidth at the access line to exceed the the committed multicast bandwidth at the access line to exceed the
provisioned limit, the AN reports an error to the NAS as described in provisioned limit, the AN reports an error to the NAS as described in
Section 4.3.2. Otherwise it replicates the multicast flow as Section 4.3.2. Otherwise it replicates the multicast flow as
requested. requested.
If the NAS decides not to permit the flow, it MAY send a Multicast If the NAS decides not to permit the flow, it MAY send a Multicast
Replication Control message in response to the Multicast Admission Replication Control message in response to the Multicast Admission
Control message to allow the AN to update its internal records. The Control message to allow the AN to update its internal records. The
content of this message is described in Section 4.4.2. content of this message is described in Section 4.4.2.
skipping to change at page 59, line 8 skipping to change at page 59, line 44
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. Resource-
control is enabled independently on the AN for white lists by based admission control is enabled independently on the AN for white
including the White-List-CAC TLV in the Provisioning message and for lists by including the White-List-CAC TLV in the Provisioning message
grey lists by including the MRepCtl-CAC TLV in the Provisioning and for grey lists by including the MRepCtl-CAC TLV in the
message. The Bandwidth-Allocation TLV provisions an amount that Provisioning message. The Bandwidth-Allocation TLV provisions an
applies to both white- and grey- listed flows if admission control is amount that applies to both white- and grey- listed flows if
enabled for both. resource-based admission control is 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.
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
skipping to change at page 60, line 11 skipping to change at page 60, line 46
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 The procedures in the previous paragraphs imply that the AN has to
retain a memory of whether an admitted flow was white-listed or
grey-listed at the time of its admission/readmission.
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 resource-based admission control is negotiable as described
Section 6.2.5.2. in 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 resource-based admission
Specifically, if the AN is to do admission control for flows added by control. Specifically, if the AN is to do resource-based admission
Multicast Replication Control messages, regardless of whether they control for flows added by Multicast Replication Control messages,
are part of NAS-initiated replication or grey list multicast service regardless of whether they are part of NAS-initiated replication or
processing, the NAS includes the MRepCtl-CAC TLV in a Provisioning grey list multicast service processing, the NAS includes the MRepCtl-
message and the Bandwidth-Allocation TLV in a Port Management CAC TLV in a Provisioning message and the Bandwidth-Allocation TLV in
message. If instead the NAS will do admission control for flows a Port Management message. If instead the NAS will do resource-based
added by Multicast Replication Control messages, regardless of admission control for flows added by Multicast Replication Control
whether they are part of NAS-initiated replication or grey list messages, regardless of whether they are part of NAS-initiated
multicast service processing, it does not send the MRepCtl-CAC TLV in replication or grey list multicast service processing, it does not
a Provisioning messages to the AN. The NAS can independently enable send the MRepCtl-CAC TLV in a Provisioning messages to the AN. The
Admission Control for white flows on the AN by including the White- NAS can independently enable resource-based admission control for
List-CAC TLV in the Provisioning message. 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 place independently of which Committed bandwidth reporting can take place independently of which
other 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.
skipping to change at page 62, line 5 skipping to change at page 63, line 5
| 149 | Multicast Flow Query | RFC XXXX | | 149 | Multicast Flow Query | RFC XXXX |
| | | | | | | |
| 150 | Committed Bandwidth Report | RFC XXXX | | 150 | Committed Bandwidth Report | RFC XXXX |
+--------------+--------------------------------+-----------+ +--------------+--------------------------------+-----------+
This document defines the following additional values for the ANCP This document defines the following additional values for the ANCP
Result Code registry. In support of these assignments, IANA is Result Code registry. In support of these assignments, IANA is
requested to change the lower limit of 0x100 specified by [RFC6320] requested to change the lower limit of 0x100 specified by [RFC6320]
for assignments by IETF Consensus to 0x64. for assignments by IETF Consensus to 0x64.
+--------------+------------------------------------+---------------+ +------------+------------------------------------------+-----------+
| Result Code | One-Line Description | Reference | | Result | One-Line Description | Reference |
+--------------+------------------------------------+---------------+ | Code | | |
| 0x64 | Command error. | RFC XXXX | +------------+------------------------------------------+-----------+
| | | | | 0x64 | Command error. | RFC XXXX |
| 0x65 | Invalid 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 | RFC XXXX | | | | |
| | amount. | | | 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 |
+--------------+------------------------------------+---------------+ +------------+------------------------------------------+-----------+
This document defines the following additional values for the ANCP This document defines the following additional values for the ANCP
Command Code registry: Command Code registry:
+-----------------+---------------------------------+---------------+ +----------------+--------------------------------------+-----------+
| Command Code | Command Code Directive Name | Reference | | Command Code | Command Code Directive Name | Reference |
| Value | | | | Value | | |
+-----------------+---------------------------------+---------------+ +----------------+--------------------------------------+-----------+
| 1 | Add | RFC XXXX | | 1 | Add | RFC XXXX |
| | | | | | | |
| 2 | Delete | RFC XXXX | | 2 | Delete | RFC XXXX |
| | | | | | | |
| 3 | Delete All | RFC XXXX | | 3 | Delete All | RFC XXXX |
| | | | | | | |
| 4 | Admission Control Reject | RFC XXXX | | 4 | Admission Control Reject | RFC XXXX |
| | | | | | | |
| 5 | Conditional Access Reject | RFC XXXX | | 5 | Conditional Access Reject | RFC XXXX |
| | | | | | | |
| 6 | Admission Control and | RFC XXXX | | 6 | Admission Control and Conditional | RFC XXXX |
| | Conditional 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 |
+-----------+--------------------------------+-----------+ +-----------+--------------------------------+-----------+
| 0x0013 | Multicast-Service-Profile | RFC XXXX | | 0x0013 | Multicast-Service-Profile | RFC XXXX |
| | | | | | | |
| 0x0015 | Bandwidth-Allocation | RFC XXXX | | 0x0015 | Bandwidth-Allocation | RFC XXXX |
skipping to change at page 63, line 19 skipping to change at page 64, line 26
| 0x0019 | Multicast-Flow | RFC XXXX | | 0x0019 | Multicast-Flow | RFC XXXX |
| | | | | | | |
| 0x0021 | List-Action | RFC XXXX | | 0x0021 | List-Action | RFC XXXX |
| | | | | | | |
| 0x0022 | Sequence-Number | RFC XXXX | | 0x0022 | Sequence-Number | RFC XXXX |
| | | | | | | |
| 0x0024 | White-List-CAC | RFC XXXX | | 0x0024 | White-List-CAC | RFC XXXX |
| | | | | | | |
| 0x0025 | MRepCtl-CAC | RFC XXXX | | 0x0025 | MRepCtl-CAC | RFC XXXX |
| | | | | | | |
| 0x0092 | Request-Source-IP | RFC XXXX | | 0x0092 | Sub-Session-Id | RFC XXXX |
| | | |
| 0x0093 | Request-Source-MAC | RFC XXXX |
| | | | | | | |
| 0x0094 | Report-Buffering-Time | RFC XXXX | | 0x0094 | Report-Buffering-Time | RFC XXXX |
| | | | | | | |
| 0x0095 | 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 | Tech | Capability | Reference | | Value | Capability Type Name | Tech | Capability | Reference |
| | Name | Type | Data? | | | | | Type | Data? | |
+-------+---------------------+--------+--------------+-------------+ +-------+-------------------------+--------+------------+-----------+
| 3 | NAS-Initiated | 0 | No | RFC XXXX | | 3 | NAS-Initiated | 0 | No | RFC XXXX |
| | Replication | | | | | | Replication | | | |
| | | | | | | | | | | |
| 5 | Committed Bandwidth | 0 | No | RFC XXXX | | 5 | Committed Bandwidth | 0 | No | RFC XXXX |
| | Reporting | | | | | | Reporting | | | |
| | | | | | | | | | | |
| 6 | Conditional Access | 0 | No | RFC XXXX | | 6 | Conditional Access With | 0 | No | RFC XXXX |
| | With White and | | | | | | White and Black Lists | | | |
| | Black Lists | | | | | | | | | |
| | | | | | | 7 | Conditional Access With | 0 | No | RFC XXXX |
| 7 | Conditional Access | 0 | No | RFC XXXX | | | Grey Lists | | | |
| | With Grey Lists | | | | | | | | | |
| | | | | | | 8 | Bandwidth Delegation | 0 | No | RFC XXXX |
| 8 | Bandwidth | 0 | No | RFC XXXX | +-------+-------------------------+--------+------------+-----------+
| | Delegation | | | |
+-------+---------------------+--------+--------------+-------------+
9. Acknowledgements 9. Acknowledgements
The authors would like to acknowledge Wojciech Dec for providing The authors would like to acknowledge Wojciech Dec for providing
useful input to this document, Robert Rennison for his help in useful input to this document, Robert Rennison for his help in
shaping the definition of the Multicast-Service-Profile TLV, Shridhar shaping the definition of the Multicast-Service-Profile TLV, Shridhar
Rao for his comments and suggestions and Aniruddha A for his proposal Rao for his comments and suggestions and Aniruddha A for his proposal
that formed the base of the Multicast Flow Reporting solution. that formed the base of the Multicast Flow Reporting solution.
Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided
substantial contributions on the solution for the NAS initiated substantial contributions on the solution for the NAS initiated
multicast control use case. Kristian Poscic provided the committed multicast control use case. Kristian Poscic provided the committed
bandwidth reporting use case. bandwidth reporting use case.
Thanks to the Document Shepherd, Matthew Bocci, and Area Director,
Ted Lemon, for points raised by their reviews following Working Group
Last Call.
10. References 10. References
10.1. Normative References 10.1. Normative References
[PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim- [PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/
parameters.xhtml", 2005. pim-parameters.xhtml", 2005.
[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, October Listener Discovery (MLD) for IPv6", RFC 2710, October
1999. 1999.
[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.
10.2. Informative References [TR-146] Broadband Forum, "TR-146, Subscriber Sessions", May 2013.
[IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
EUI48.html", 2010.
[IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ 10.2. Informative References
EUI64.html", 2010.
[RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol
Independent Multicast (PIM) Join Attribute Format", RFC Independent Multicast (PIM) Join Attribute Format", RFC
5384, November 2008. 5384, November 2008.
[RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, "Security [RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, "Security
Threats and Security Requirements for the Access Node Threats and Security Requirements for the Access Node
Control Protocol (ANCP)", RFC 5713, January 2010. Control Protocol (ANCP)", RFC 5713, January 2010.
[RFC5851] Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S. [RFC5851] Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S.
skipping to change at page 66, line 8 skipping to change at page 67, line 27
A.1. Provisioning Phase A.1. Provisioning Phase
Assume that capability negotiation has been completed between the AN Assume that capability negotiation has been completed between the AN
and NAS and that the set of negotiated capabilities includes the and NAS and that the set of negotiated capabilities includes the
following four multicast capabilities: NAS-initiated replication, following four multicast capabilities: NAS-initiated replication,
conditional access with white and black list, conditional access with conditional access with white and black list, conditional access with
grey list, and bandwidth delegation. At this point, the NAS can grey list, and bandwidth delegation. At this point, the NAS can
provision the service profiles on the AN and enable admission control provision the service profiles on the AN and enable admission control
at the AN for white-listed flows. To do this, the NAS sends the AN a at the AN for white-listed flows. To do this, the NAS sends the AN a
Provisioning message containing this information. An example message Provisioning message containing this information. An example message
providing the profile for our assumed subscriber is shown in Figure providing the profile for our assumed subscriber is shown in
20. The message has the following contents: Figure 19. 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 [RFC6320]. 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 233.252.0.64/ 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 black list 29, coming from a server at 192.0.2.21. Finally, the black list
skipping to change at page 66, line 39 skipping to change at page 68, line 10
192.0.2.21. 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 (0x880C) | Length = 132 | | Type (0x880C) | Length = 132 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type = 93 | 0x00 | Result Code = 0x000 | | Version | Msg Type = 93 | Res=0 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 | | Mcast-Service-Profile 0x0013 | TLV Length = 112 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| M-S-Prof-Name TLV Type = 0x18 | Embedded TLV Length = 20 | | Mcast-Svc-Profile-Name 0x0018 | Embedded TLV Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast service profile name | | Multicast service profile name |
~ = "Cust 0127-53681-0003" ~ ~ = "Cust 0127-53681-0003" ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| List-Action TLV Type = 0x21 | Embedded TLV Length = 28 | | TLV Type = List-Action 0x0021 | Embedded TLV Length = 28 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Oper = 0x01 |Lst Typ = 0x01 | Reserved = 0x0000 | | Operation = 1 | List Type = 1 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Family = 0x01 | List Length = 20 | | Address Family = 1 | List Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| G Preflen = 29| S Preflen = 32| Group prefix = | | G Preflen = 29| S Preflen = 32| Group prefix = |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 233.252.0.0 | Source prefix = | | 233.252.0.0 | Source prefix = |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 192.0.2.15 | G Preflen = 29| S Preflen = 32| | 192.0.2.15 | G Preflen = 29| S Preflen = 32|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Group prefix = 233.252.0.32 | | Group prefix = 233.252.0.32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source prefix = 192.0.2.15 | | Source prefix = 192.0.2.15 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| List-Action TLV Type = 0x21 | Embedded TLV Length = 18 | | TLV Type = List-Action 0x0021 | Embedded TLV Length = 18 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Oper = 0x01 |Lst Typ = 0x03 | Reserved = 0x0000 | | Operation = 1 | List Type = 3 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Family = 0x01 | List Length = 10 | | Address Family = 1 | List Length = 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| G Preflen = 29| S Preflen = 32| Group prefix = / | G Preflen = 29| S Preflen = 32| Group prefix = /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 233.252.0.64 | Source prefix = / / 233.252.0.64 | Source prefix = /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 192.0.2.21 | Padding = 0x0000 | / 192.0.2.21 | Padding = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| List-Action TLV Type = 0x21 | Embedded TLV Length = 28 | | TLV Type = List-Action 0x0021 | Embedded TLV Length = 28 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Oper = 0x01 |Lst Typ = 0x02 | Reserved = 0x0000 | | Operation = 1 | List Type = 2 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Family = 0x01 | List Length = 20 | | Address Family = 1 | List Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| G Preflen = 32| S Preflen = 32| Group prefix = / | G Preflen = 32| S Preflen = 32| Group prefix = /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 233.252.0.65 | Source prefix = / / 233.252.0.65 | Source prefix = /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 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 | | Type = White-List-CAC 0x0024 | TLV Length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 20: Example Provisioning Message
TLV lengths in the figure are given in decimal for easier Figure 19: Example Provisioning Message
understanding. Note that the padding after the middle List-Action
TLV is counted as part of length of the Multicast-Service-Profile Note that the padding after the middle List-Action TLV is counted as
TLV, but is not included in the length of that List-Action TLV. Note part of length of the Multicast-Service-Profile TLV, but is not
also that the Length field in the message header, unlike those in the included in the length of that List-Action TLV. Note also that the
TLVs, includes the message header itself, as required by [RFC6320]. 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 Finally, note that the Provisioning message does not include a
MRepCtl-CAC TLV since in our example admission control for grey MRepCtl-CAC TLV since in our example resource-based admission control
listed flows and for NAS-initiated replication is performed by the for grey listed flows and for NAS-initiated replication is performed
NAS. 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 Figure bandwidth. The corresponding message flow is illustrated in
21. Figure 20.
+----------+ +---------+ +-----+ +-----+ +----------+ +---------+ +-----+ +-----+
|Subscriber| | Home | | AN | | NAS | |Subscriber| | Home | | AN | | NAS |
+----------+ | Gateway | +-----+ +-----+ +----------+ | Gateway | +-----+ +-----+
| +---------+ | | | +---------+ | |
| | | | | | | |
| | | | | | | |
| | DSL Synch. | | | | DSL Synch. | |
| |---------------->| | | |---------------->| |
| | |(M1)PORT_UP(Port ID) | | | |(M1)PORT_UP(Port ID) |
skipping to change at page 68, line 45 skipping to change at page 70, line 25
| | | (*) | | | (*)
| | |(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 20: 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-Profile- example (Figure 21) just shows the Target, Multicast-Service-Profile-
Name, and Bandwidth-Allocation TLVs. The Target TLV identifies the Name, and Bandwidth-Allocation TLVs. The Target TLV identifies the
subscriber line, the Multicast-Service-Profile-Name TLV is identical subscriber line, the Multicast-Service-Profile-Name TLV is identical
to the one contained in the Provisioning message, and the Bandwidth- to the one contained in the Provisioning message, and the Bandwidth-
Allocation TLV provides just enough bandwidth (2000 kbits/s) for one Allocation TLV provides just enough bandwidth (2000 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 (0x1) for this example.
o Result Code is 0x000. o Result Code is 0.
o A transaction identifier is assigned by the NAS.
o Port is set to 0. o Port is set to 0.
o Event Sequence Number, the R flag and the other bits marked x, o Event Sequence Number, the R flag and the other bits marked x,
Duration, the Event Flags, and the Flow Control Flags are all Duration, the Event Flags, and the Flow Control Flags are all
irrelevant for this function and are set to 0. irrelevant for this function and are set to 0.
o Function is set to 0x8, "Configure Connection Service Data". o Function is set to "Configure Connection Service Data" (8).
o X-Function is set to 0. o X-Function is set to 0.
o Tech Type is 0x05 (DSL). o Tech Type is "DSL" (5).
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 (0x880C) | Length = 84 | | Type (0x880C) | Length = 84 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type = 32 | 0x01 | Result Code = 0x000 | | Version | Msg Type = 32 | Res=1 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R|x|x|x|x|x|x|x| Duration = 0 | Function = 0x8| X-Function = 0| |R|x|x|x|x|x|x|x| Duration = 0 | Function = 0x8| X-Function = 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Flags | Flow Control Flags | | Event Flags | Flow Control Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x| Msg Type = 32 |Tech Type=0x05 | Blk Len = 56 | |x|x|x|x|x|x|x|x| Msg Type = 32 | Tech Type=5 | Blk Len = 56 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| # of TLVs = 3 | Extension Block length = 44 | | # of TLVs = 3 | Extension Block length = 44 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Target TLV Type = 0x1000 | Target TLV Length = 8 | | TLV Type = Target 0x1000 | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| M-S-Prof-Name TLV Type = 0x18 | TLV Length = 20 | | Mcast-Svc-Profile-Name 0x0018 | TLV Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast service profile name | | Multicast service profile name |
~ = "Cust 0127-53681-0003" ~ ~ = "Cust 0127-53681-0003" ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BW Alloc TLV Type = 0x15 | TLV Length = 4 | | Bandwidth-Allocation 0x0015 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth value = 0x000007D0 (2000 kbits/s) | | Bandwidth value = 2000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 22: Example Port Management Message Figure 21: 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 22 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 resource-based admission
listed flows is not activated on the AN. control for grey-listed flows is not activated on the AN.
To start the flow, the AN sends a Multicast Admission Control request To start the flow, the AN sends a Multicast Admission Control request
(M1) to the NAS. The NAS decides whether flow can be admitted, (M1) to the NAS. The NAS decides whether flow can be admitted,
applying both policy and bandwidth criteria. It returns its decision applying both policy and bandwidth criteria. It returns its decision
(positive in this example) in a Multicast Replication Control message (positive in this example) in a Multicast Replication Control message
(M2). Later, when the subscriber leaves the flow, the AN informs the (M2). Later, when the subscriber leaves the flow, the AN informs the
NAS by sending another Multicast Admission Control message. NAS by sending another Multicast Admission Control message.
+----------+ +-------+ +-----+ ANCP +-----+ +----------+ +-------+ +-----+ ANCP +-----+
|Subscriber| | Home | | AN |<---------->| NAS | |Subscriber| | Home | | AN |<---------->| NAS |
skipping to change at page 71, line 28 skipping to change at page 73, line 44
| 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 22: 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 is 145;
* Result = Ignore (0x0);
* Result= 0x0 (Ignore);
* Transaction-ID = Transaction-ID maintained by AN; * a transaction identifier assigned by the 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 (1); * Command Code = "Add" (1);
* Accounting = 0; * Accounting = "No" (0);
* a Multicast-Flow embedded TLV indicating the SSM multicast flow * a Multicast-Flow embedded TLV indicating the multicast flow for
(Flow Type = 0x02) for which the AN received the IGMP Join: which the AN received the IGMP Join: flow type "SSM" (2),
IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source address family "IPv4" (1), Group address = 233.252.0.67, Source
Address = 192.0.2.21; Address = 192.0.2.21;
* a Request-Source-IP embedded TLV containing the IGMP join * a Subs-Session-Identifier embedded TLV containing the value
source IP (192.0.2.100). 0x0C000264.
The Multicast Admission Control message M1 is illustrated in Figure The Multicast Admission Control message M1 is illustrated in
24: Figure 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x880C) | Length = 98 | | Type (0x880C) | Length = 98 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=145 | 0x0 | Result Code = 0x000 | | Version | Msg Type=145 | Res=0 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 | | TLV Type = Target 0x1000 | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Command TLV Type = 0x11 | TLV Length = 28 | | TLV Type = Command 0x0011 | TLV Length = 28 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=0x01 |Acctg = 0x00 | Reserved = 0x0000 | | Cmd Code = 1 | Acctg = 0 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | | Flow Type = 2 | Addr Fam = 1 | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
| Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | |Subs-Session-Identifier 0x0092 | Embedded TLV length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Address = 192.0.2.100 | | Value = 0x0C000264 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 24: Multicast Admission Control Message Seeking To Add A Flow Figure 23: 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 = "Multicast Replication Control" (144);
* Result= 0x1 (NAck); * Result= 0x1 (NAck);
* Transaction-ID = Transaction-ID maintained by NAS; * a transaction identifier assigned by the 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 (1); * Command Code = "Add" (1);
* Accounting = 1 (begin flow accounting), since in our example * Accounting = "Yes" (1), since in our example the operator wants
the operator wants accounting on this flow. accounting on this flow.
* a Multicast-Flow embedded TLV indicating the SSM multicast flow * a Multicast-Flow embedded TLV indicating the multicast flow
(Flow Type = 0x02) that the NAS is admitting for this access that the NAS is admitting for this access line: flow type "SSM"
port: IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) (2), address family "IPv4" (1), Group address = 233.252.0.67,
Source Address = 192.0.2.21. Source Address = 192.0.2.21.
The Multicast Admission Control message M2 is illustrated in Figure The Multicast Admission Control message M2 is illustrated in
25. 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 (0x880C) | Length = 48 | | Type (0x880C) | Length = 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=144 | 0x1 | Result Code = 0x000 | | Version | Msg Type=144 | Res=1 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 | | Target Type = 0x1000 | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Command TLV Type = 0x11 | TLV Length = 20 | | TLV Type = Command 0x0011 | TLV Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 | | Cmd Code = 1 | Acctg = 1 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | | Flow Type = 2 | Addr Fam = 1 | 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 25: Multicast Replication Control Message Admitting A Flow Figure 24: 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 is 145;
* Result= 0x0 (Ignore) * Result = Ignore (0x0)
* Transaction-ID = Transaction-ID maintained by AN * a transaction identifier assigned by the AN;
o a Target TLV identifying the AN Port o a Target TLV identifying the access line;
o a Command TLV containing: o a Command TLV containing:
* a Command Code = Delete (2); * a Command Code = "Delete" (2);
* Accounting = 0; * Accounting = "No" (0);
* a Multicast-Flow embedded TLV indicating the SSM multicast flow * a Multicast-Flow embedded TLV indicating the multicast flow for
(Flow Type = 0x02) for which the AN received the IGMP leave: which the AN received the IGMP leave: flow type "SSM" (2),
IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source address family "IPv4" (1), Group address = 233.252.0.67, Source
Address = 192.0.2.21. Address = 192.0.2.21.
* a Request-Source-IP embedded TLV containing the IGMP leave * a Subs-Session-Identifier embedded TLV containing the value
request source, IPv4 (0x01) address 192.0.2.100. 0x0C000264.
The Multicast Admission Control message M3 is illustrated in Figure The Multicast Admission Control message M3 is illustrated in
26. 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 (0x880C) | Length | | Type (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=145 | 0x0 | Result Code = 0x000 | | Version | Msg Type=145 | Res=0 | 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 = 8 | | TLV Type = Target 0x1000 | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Command TLV Type = 0x11 | TLV Length = 28 | | TLV Type = Command 0x0011 | TLV Length = 28 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=0x02 |Acctg = 0x00 | Reserved = 0x0000 | | Cmd Code = 2 | Acctg = 0 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | | Multicast-Flow Type = 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | | Flow Type = 2 | Addr Fam = 1 | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | |Subs-Session-Identifier 0x0092 | Embedded TLV length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Address = 192.0.2.100 | | Value = 0x0C000264 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 26: Multicast Admission Control Message Signalling Flow Figure 25: Multicast Admission Control Message Signalling Flow
Termination 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.
skipping to change at page 76, line 13 skipping to change at page 79, line 26
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 27. The complete message flow is shown in Figure 26.
+----------+ +-------+ +-----+ 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 77, line 4 skipping to change at page 80, line 42
| | | Query request | | | | Query request |
| | |<------------------|(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 27: Successful Join/Leave Operations, White-Listed Flow
The Bandwidth Reallocation Request message (M1) is shown in Figure Figure 26: Successful Join/Leave Operations, White-Listed Flow
28. The contents require little explanation. The Message Type for
the Bandwidth Reallocation Request is 146. The Result field is set The Bandwidth Reallocation Request message (M1) is shown in
to 0x0 (Ignore). Besides the Target, the message has one other TLV, Figure 27. The contents require little explanation. The Message
the Bandwidth-Request, with a TLV Type of 0x16. The TLV contains Type for the Bandwidth Reallocation Request is 146. The Result field
Required Amount and Preferred Amount fields, set to 4000 and 6000 is set to Ignore (0x0). Besides the Target, the message has one
kbits/s respectively. other TLV, the Bandwidth-Request, with a TLV Type of 0x0016. The TLV
contains Required Amount and Preferred Amount fields, set to 4000 and
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 (0x880C) | Length = 36 | | Type (0x880C) | Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=146 | 0x0 | Result Code = 0x000 | | Version | Msg Type=146 | Res=0 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 | | TLV Type = Target 0x1000 | 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-Request 0x0016 | TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required Amount = 0x00000FA0 (4000 kbits/s) | | Required Amount = 4000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Preferred Amount = 0x00001770 (6000 kbits/s) | | Preferred Amount = 6000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 28: Bandwidth Reallocation Request Message Figure 27: Bandwidth Reallocation Request Message
The Bandwidth Transfer message (M2) is shown in Figure 29. Again, The Bandwidth Transfer message (M2) is shown in Figure 28. 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 0x0015 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 (0x880C) | Length = 32 | | Type (0x880C) | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=147 | 0x3 | Result Code = 0x000 | | Version | Msg Type=147 | Res=3 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 | | TLV Type = Target 0x1000 | 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 | | Bandwidth-Allocation 0x0015 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delegated Amount = 0x00000FA0 (4000 kbits/s) | | Delegated Amount = 4000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 29: NAS Response, Bandwidth Transfer Message Figure 28: NAS Response, Bandwidth Transfer Message
The Delegated Bandwidth Query request message (M3) is shown in Figure The Delegated Bandwidth Query request message (M3) is shown in
30. The Message Type for the Delegated Bandwidth Query request Figure 29. The Message Type for the Delegated Bandwidth Query
message is 148. The Result field is set to AckAll (0x2). The request message is 148. The Result field is set to AckAll (0x2).
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 (0x880C) | Length = 24 | | Type (0x880C) | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=148 | 0x2 | Result Code = 0x000 | | Version | Msg Type=148 | Res=2 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 | | TLV Type = Target 0x1000 | 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 30: Delegated Bandwidth Query Request Message Figure 29: 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 31. The Message Type for the Delegated Bandwidth Query in Figure 30. 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 (0x880C) | Length = 32 | | Type (0x880C) | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=148 | 0x3 | Result Code = 0x000 | | Version | Msg Type=148 | Res=2 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 | | TLV Type = Target 0x1000 | 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 | | Bandwidth-Allocation 0x0015 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delegated Amount = 0x00000FA0 (4000 kbits/s) | | Delegated Amount = 4000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 31: Delegated Bandwidth Query Response Message Figure 30: 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
skipping to change at page 80, line 12 skipping to change at page 84, line 12
(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 32. in Figure 31.
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 80, line 50 skipping to change at page 84, 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 32: NAS-Initiated Flows For On-Line Gaming Figure 31: NAS-Initiated Flows For On-Line Gaming
Multicast Replication Control message (M1) in Figure 33 looks like Multicast Replication Control message (M1) in Figure 32 looks like
the message in Figure 25 with two exceptions. The first is that the the message in Figure 24 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 = 1) with IPv4 (1) group address
233.252.0.100. 233.252.0.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 (0x880C) | Length = 44 | | Type (0x880C) | Length = 44 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=144 | 0x1 | Result Code = 0x000 | | Version | Msg Type=144 | Res=1 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 | | TLV Type = Target 0x1000 | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Command TLV Type = 0x11 | TLV Length = 16 | | TLV Type = Command 0x0011 | TLV Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 | | Cmd Code = 1 | Acctg = 1 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 8 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x01 |Addr Fam =0x01 | Reserved = 0x0000 | | Flow Type = 1 | Addr Fam = 1 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = 233.252.0.100 | | Multicast Group Address = 233.252.0.100 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
Figure 33: Enabling The Subscriber To Join An On-Line Game Figure 32: 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 33 with two exceptions: the looks the same as the message in Figure 32 with two exceptions: the
Command Code becomes Delete (2), and Accounting is set to 0 to turn Command Code becomes "Delete" (2), and Accounting is set to "No" (0)
off flow accounting. Of course, the Transaction Identifier values to turn off flow accounting. Of course, the Transaction Identifier
will differ between the two messages. values 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 34 illustrates a message flow in a case where the NAS queries Figure 33 illustrates a message flow in a case where the NAS queries
the AN about which multicast flows are active on port 10, on port 11 the AN about which multicast flows are active on port 10, on port 11
and on port 20 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 34: Per-Port Multicast Flow Reporting Figure 33: 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 35. The Message Type is 149. The Result field is set to Figure 34. 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 (0x880C) | Length | | Type (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type = 149|Rslt=2 | Result Code = 0 | | Version | Msg Type = 149| Res=1 | 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 | | TLV 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 (port10) ~ ~ Access Loop Circuit ID (port10) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length | | TLV 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 (port20) ~ ~ Access Loop Circuit ID (port20) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length | | TLV 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 (port11) ~ ~ Access Loop Circuit ID (port11) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 35: Multicast Flow Query Request Message For Per-Port Figure 34: 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 36. It indicates that there is one active multicast flow Figure 35. It indicates that there is one active multicast flow
[(192.0.2.1, 233.252.0.4)] on port 10, no active multicast flow on [(192.0.2.1, 233.252.0.4)] on port 10, no active multicast flow on
port 20 and two active multicast flows [(192.0.2.1, 233.252.0.4) and port 20 and two active multicast flows [(192.0.2.1, 233.252.0.4) and
(192.0.2.2, 233.252.0.10)] on port 11. (192.0.2.2, 233.252.0.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 (0x880C) | Length | | Type (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | 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 | | TLV 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 (port10) ~ ~ Access Loop Circuit ID (port10) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | | Flow Type = 2 | Addr Fam = 1 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = 233.252.0.4 | | Multicast Group Address = 233.252.0.4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Source Address = 192.0.2.1 | | Unicast Source Address = 192.0.2.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
| Type = 0x1000 (Target) | Target TLV Length | | TLV 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 (port20) ~ ~ Access Loop Circuit ID (port20) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x1000 (Target) | Target TLV Length | | TLV 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 (port11) ~ ~ Access Loop Circuit ID (port11) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | | Flow Type = 2 | Addr Fam = 1 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = 233.252.0.4 | | Multicast Group Address = 233.252.0.4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Source Address = 192.0.2.1 | | Unicast Source Address = 192.0.2.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | | Flow Type = 2 | Addr Fam = 1 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address: 233.252.0.10 | | Multicast Group Address: 233.252.0.10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unicast Source Address = 192.0.2.2 | | Unicast Source Address = 192.0.2.2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
Figure 36: Multicast Flow Query Response message For Per-Port Figure 35: Multicast Flow Query Response message For Per-Port
Multicast 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
Email: flefauch@cisco.com Email: flefauch@cisco.com
Roberta Maglione Roberta Maglione
 End of changes. 299 change blocks. 
744 lines changed or deleted 731 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/