draft-ietf-ancp-mc-extensions-13.txt   draft-ietf-ancp-mc-extensions-14.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: June 13, 2014 T. Taylor Expires: July 12, 2014 T. Taylor
Huawei Huawei
December 10, 2013 January 8, 2014
Multicast Control Extensions for ANCP Multicast Control Extensions for ANCP
draft-ietf-ancp-mc-extensions-13.txt draft-ietf-ancp-mc-extensions-14.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 June 13, 2014. This Internet-Draft will expire on July 12, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 6 3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . . . . 9
3.3. Multicast Flow Reporting Use Case . . . . . . . . . . . . 9 3.3. Multicast Flow Reporting Use Case . . . . . . . . . . . . 10
3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9 3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10 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 . . . . . . . . . . . . . . . . . . . . 11 3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 11
4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11 4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 12 4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 12
4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12 4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 13
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 . . . . . . . . . . . . . . . . . 25
4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25 4.5. Bandwidth Reallocation Request Message . . . . . . . . . 26
4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25 4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 26
4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26 4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 27
4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29 4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 30
4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 29 4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 30
4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30 4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 31
4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31 4.7. Delegated Bandwidth Query Request Message . . . . . . . . 32
4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31 4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32
4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32 4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32
4.8. Delegated Bandwidth Query Response Message . . . . . . . 32 4.8. Delegated Bandwidth Query Response Message . . . . . . . 33
4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32 4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 33
4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32 4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 33
4.9. Multicast Flow Query Request and Response Messages . . . 33 4.9. Multicast Flow Query Request and Response Messages . . . 34
4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 34 4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 34
4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34 4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 35
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 . . . . . . . . . . . . . . . . . . 37
4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36 4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 37
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 . . . . . . . . . . . 39
5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 39 5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 39
5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 41 5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 42
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 . . . . . . . . . . . . . . . . . . . 43
5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 43 5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 43
5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43 5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 44
5.9. Subs-Session-Id TLV . . . . . . . . . . . . . . . . . . . 44 5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 45
5.10. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45 5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . 45
5.11. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46 5.11. Request-Source-Device-Id TLV . . . . . . . . . . . . . . 46
5.12. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 46 5.12. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 47
6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47 5.13. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 48
6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48 5.14. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 48
6.1.1. Protocol Requirements For NAS-Initiated Replication . 48 6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 49
6.1. Required Protocol Support . . . . . . . . . . . . . . . . 50
6.1.1. Protocol Requirements For NAS-Initiated Replication . 50
6.1.2. Protocol Requirements For Committed Multicast 6.1.2. Protocol Requirements For Committed Multicast
Bandwidth Reporting . . . . . . . . . . . . . . . . . 49 Bandwidth Reporting . . . . . . . . . . . . . . . . . 51
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 . . . . . . . . . . . . . . . . 52
6.1.4. Protocol Requirements For Conditional Access With 6.1.4. Protocol Requirements For Conditional Access With
Grey Lists . . . . . . . . . . . . . . . . . . . . . 51 Grey Lists . . . . . . . . . . . . . . . . . . . . . 53
6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 52 6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 54
6.2. Capability-Specific Procedures for Providing Multicast 6.2. Capability-Specific Procedures for Providing Multicast
Service . . . . . . . . . . . . . . . . . . . . . . . . . 53 Service . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.2.1. Procedures For NAS-Initiated Replication . . . . . . 53 6.2.1. Procedures For NAS-Initiated Replication . . . . . . 55
6.2.2. Procedures For Committed Bandwidth Reporting . . . . 54 6.2.2. Procedures For Committed Bandwidth Reporting . . . . 56
6.2.3. Procedures For Conditional Access With Black and 6.2.3. Procedures For Conditional Access With Black and
White Lists . . . . . . . . . . . . . . . . . . . . . 55 White Lists . . . . . . . . . . . . . . . . . . . . . 57
6.2.4. Procedures For Conditional Access With Grey Lists . . 57 6.2.4. Procedures For Conditional Access With Grey Lists . . 59
6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 58 6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 60
6.3. Combinations of Multicast Capabilities . . . . . . . . . 59 6.3. Combinations of Multicast Capabilities . . . . . . . . . 61
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 . 59 Black Lists and Conditional Access With Grey Lists . 61
6.3.2. Combination of Conditional Access With Delegated 6.3.2. Combination of Conditional Access With Delegated
Bandwidth . . . . . . . . . . . . . . . . . . . . . . 60 Bandwidth . . . . . . . . . . . . . . . . . . . . . . 63
6.3.3. Combination of NAS-Initiated Replication with Other 6.3.3. Combination of NAS-Initiated Replication with Other
Capabilities . . . . . . . . . . . . . . . . . . . . 61 Capabilities . . . . . . . . . . . . . . . . . . . . 63
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 . . . . . . . . . . . . 63
7. Security Considerations . . . . . . . . . . . . . . . . . . . 61 7. Security Considerations . . . . . . . . . . . . . . . . . . . 64
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 65 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 68
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 65 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 68
10.1. Normative References . . . . . . . . . . . . . . . . . . 65 10.1. Normative References . . . . . . . . . . . . . . . . . . 68
10.2. Informative References . . . . . . . . . . . . . . . . . 66 10.2. Informative References . . . . . . . . . . . . . . . . . 69
Appendix A. Example of Messages and Message Flows . . . . . . . 66 Appendix A. Example of Messages and Message Flows . . . . . . . 69
A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 67 A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 70
A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 72 A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 76
A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 78 A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 81
A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 83 A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 86
A.5. Handling Of Requests To Join and Leave the On-Line Game . 83 A.5. Handling Of Requests To Join and Leave the On-Line Game . 86
A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 85 A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 89
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 92
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 12, line 42 skipping to change at page 12, line 45
AN is required to do resource-based admission control before AN is required to do resource-based admission control before
replicating white-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 resource-based admission control before AN is required to do resource-based admission control before
replicating flows specified in Multicast Replication Control replicating flows specified in Multicast Replication Control
messages. 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.11. If present, this Buffering-Time TLV is defined in Section 5.13. 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 direct the AN to a set of named multicast service profiles, or to direct the AN to
perform resource-based admission control for specific classes of perform resource-based admission control for specific classes of
flows. 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
skipping to change at page 18, line 21 skipping to change at page 18, line 21
indicates that octet accounting for the flow is requested. indicates that octet accounting for the flow is requested.
The sender MUST set the Accounting field to 0 and the The sender MUST set the Accounting field to 0 and the
receiver MUST ignore the Accounting field for other Command receiver MUST ignore the Accounting field for other Command
Code values. Code values.
Reserved: Reserved:
Reserved for future use. MUST be set to zeroes 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.10) An instance of the Multicast-Flow TLV (Section 5.12)
specifying the flow to be added or deleted. The Multicast- specifying the flow to be added or deleted. The Multicast-
Flow TLV is omitted if the Command Code has value "Delete Flow TLV is omitted if the Command Code has value "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.
skipping to change at page 23, line 31 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 addition: Multicast Replication Control message, with the following additions:
o a Subs-Session-ID TLV as defined in Section 5.9 MAY be appended to o a Request-Source-IP TLV MAY be appended to the Command TLV as an
the Command TLV as an additional embedded TLV. The need for this additional embedded TLV;
TLV depends on what type of subscriber session identifier the
operator is using to retrieve the subscriber profile information o similarly, a Request-Source-MAC TLV MAY be appended to the Command
from AAA. Some of the types identified by [TR-146] requirement TLV as an additional embedded TLV.
R43 are covered by the contents of the Target TLV.
o Finally and preferably, a Request-Source-Device-Id TLV MAY be
appended to the Command TLV as an additional embedded 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
skipping to change at page 24, line 16 skipping to change at page 24, line 19
o the Command Code field MUST be set to "Add" (1) when the message o the Command Code field MUST be set to "Add" (1) when the message
conveys a Join , to "Delete" (2) when the message conveys a Leave conveys a Join , to "Delete" (2) when the message conveys a Leave
and to "Delete All" (3) 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 omitted. When the Command Code is 3, the Multicast-Flow TLV is omitted.
o Depending on local configuration, the Subs-Session-Identifier o The Request-Source-IP embedded TLV MAY be included by the AN to
embedded TLV MAY be included by the AN. The content of this TLV convey the IP address of the sender of the join/leave message
depends on local practice. (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
convey the MAC address of the sender of the join/leave message
(e.g., IGMP/MLD Join/Leave) that triggered the AN to include the
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 As a third alternative, the Request-Source-Device-Id embedded TLV
MAY be included by the AN to convey a local identifier 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.
The inclusion of Request-Source-IP or Request-Source-MAC in the
Multicast Admission Control message is typically done to allow the
application of policies applicable to specific devices within the
customer's network. However, transmission of either of these fields
beyond the AN introduces potential privacy issues. Instead of
transmitting either of these identifiers, it is RECOMMENDED that the
AN map the required identifier to a local value known to the AN and
AAA but not to the NAS, as discussed in Section 7. The local
identifier is transmitted using the Request-Source-Device-Id TLV.
4.4.2. Receiver Behaviour 4.4.2. Receiver Behaviour
On receipt of an Multicast Admission Control message, the NAS: On receipt of an Multicast Admission Control message, the NAS:
o MUST ignore the Result field; o MUST ignore the Result field;
o if the directive in the Multicast Admission Control message is o if the directive in the Multicast Admission Control message is
"Delete" (2) or "Delete All" (3) 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
skipping to change at page 34, line 32 skipping to change at page 35, line 22
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.10. Multicast-Flow TLV is encoded as specified in Section 5.12.
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.
skipping to change at page 36, line 26 skipping to change at page 37, line 6
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.12. of the Committed-Bandwidth TLV, as described in Section 5.14.
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 44, line 34 skipping to change at page 45, line 14
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. Subs-Session-Id TLV 5.9. Request-Source-IP TLV
The Subs-Session-Id TLV provides a subscriber session identifier for The Request-Source-IP TLV provides the IP address of the entity that
the entity that originated a specific request to join or leave a originated a specific request to join or leave a multicast channel.
multicast channel. The subscriber session identifier is a value The TLV is illustrated in Figure 15.
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
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 Request-Source-MAC TLV provides the MAC address of the entity
that originated a specific request to join or leave a multicast
channel. The TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Subs-Session-Id 0x0092 | TLV length | |TLV Type=Request-Source-MAC | TLV Length = 6 or 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value | | |
+-+-+- IEEE MAC Address +-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 15: Subs-Session-Id TLV Figure 16: Request-Source-MAC TLV
The Subs-Session-Id TLV contains the following fields: The Request-Source-MAC TLV contains the following fields:
o The Subs-Session-Id TLV Type is 0x0092. o The Request-Source-MAC TLV Type is 0x0093.
o TLV length depends on the type of identifier used. o TLV length is either 6 octets (MAC-48 or EUI-48) or 8 octets
(EUI-64).
o Value is the configured value of the identifier. o IEEE MAC Address: MAC address of the device originating the
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.
5.10. Multicast-Flow TLV EUI-48 and EUI-64 are registered trademarks of the IEEE.
5.11. Request-Source-Device-Id TLV
The Request-Source-Device-Id TLV provides a local identifier of the
entity that originated a specific request to join or leave a
multicast channel. The TLV is illustrated in Figure 17.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Request-Source-Device-Id | TLV length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 17: Request-Source-Device-Id TLV
The Request-Source-Device-Id TLV contains the following fields:
o The Request-Source-IP TLV Type is 0x0096.
o TLV length is 4.
o Local device identifier value, known to the AN and AAA. Given
that the scope of the identifier is a single customer network, 32
bits is a more than sufficient numbering space.
5.12. 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 16. address. It 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Multicast-Flow 0x0019 | 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 16: Multicast-Flow TLV Figure 18: 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: 1 "Any Source Multicast (ASM)", 2 "Source-Specific o Flow Type: 1 "Any Source Multicast (ASM)", 2 "Source-Specific
Multicast (SSM)". Multicast (SSM)".
skipping to change at page 46, line 13 skipping to change at page 48, line 10
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 "ASM" (1), 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 "SSM" (2), a source address MUST be present. If the Flow Type is "SSM" (2), a source address MUST
be present. be present.
5.11. Report-Buffering-Time TLV 5.13. 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 17. illustrated in Figure 19.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Report-Buffering-Time 0x0094 | TLV Length = 4 | | Report-Buffering-Time 0x0094 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Buffering Time (ms) | | Buffering Time (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 17: Report-Buffering-Time TLV Figure 19: 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.12. Committed-Bandwidth TLV 5.14. 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 18. to it. The TLV is illustrated in Figure 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Committed-Bandwidth 0x0095 | TLV Length (variable) | | Committed-Bandwidth 0x0095 | TLV Length (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Committed Multicast Bandwidth (kbits/s) | | Committed Multicast Bandwidth (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Target TLV ~ ~ Target TLV ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 18: Committed-Bandwidth TLV Figure 20: 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 49, line 23 skipping to change at page 51, line 23
| Section 4.3 | Multicast Replication Control message | | Section 4.3 | Multicast Replication Control message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section 5.4 | 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.12 | 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.
skipping to change at page 50, line 15 skipping to change at page 52, line 15
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Section 4.1 | Provisioning message with Report-Buffering-Time | | Section 4.1 | Provisioning message with Report-Buffering-Time |
| | TLV | | | TLV |
| | | | | |
| Section 4.10 | Committed Bandwidth Report message | | Section 4.10 | Committed Bandwidth Report message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section 5.11 | Report-Buffering-Timer TLV | | Section 5.13 | Report-Buffering-Timer TLV |
| | | | | |
| Section 5.12 | Committed-Bandwidth TLV | | Section 5.14 | Committed-Bandwidth TLV |
| | | | | |
| Section 5.10 | Multicast-Flow TLV | | Section 5.12 | 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 | Provisioning message with Multicast-Service-Profile | | Section 4.1 | Provisioning message with Multicast-Service- |
| 4.1 | TLV, white and black lists only, and White-List-CAC | | | Profile TLV, white and black lists only, and |
| | TLV | | | White-List-CAC TLV |
| | | | | |
| Section | Port Management message with Multicast-Service- | | Section 4.2 | Port Management message with Multicast-Service- |
| 4.2 | Profile-Name and Bandwidth-Allocation TLVs. | | | Profile-Name and Bandwidth-Allocation TLVs. |
| | | | | |
| Section | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
| 4.9 | | | | |
| | | | Section 5.1 | Multicast-Service-Profile TLV |
| Section | Multicast-Service-Profile TLV | | | |
| 5.1 | | | Section 5.2 | Multicast-Service-Profile-Name TLV |
| | | | | |
| Section | Multicast-Service-Profile-Name TLV | | Section 5.3 | List-Action TLV, white and black lists only |
| 5.2 | | | | |
| | | | Section 5.5 | Bandwidth-Allocation TLV |
| Section | List-Action TLV, white and black lists only | | | |
| 5.3 | | | Section 5.6 | White-List-CAC TLV |
| | | | | |
| Section | Bandwidth-Allocation TLV | | Section 5.12 | Multicast-Flow 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 | | Reference | Protocol Element |
+-----------+-------------------------------------------------------+ +--------------+----------------------------------------------------+
| Section | Provisioning message with Multicast-Service-Profile | | Section 4.1 | Provisioning message with Multicast-Service- |
| 4.1 | TLV, grey lists only, and MRepCtl-CAC TLV | | | Profile TLV, grey lists only, and MRepCtl-CAC TLV |
| | | | | |
| Section | Port Management message with Multicast-Service- | | Section 4.2 | Port Management message with Multicast-Service- |
| 4.2 | Profile-Name and Bandwidth-Allocation TLVs. | | | Profile-Name and Bandwidth-Allocation TLVs. |
| | | | | |
| Section | Multicast Replication Control message | | Section 4.3 | Multicast Replication Control message |
| 4.3 | | | | |
| | | | Section 4.4 | Multicast Admission Control Message |
| Section | Multicast Admission Control Message | | | |
| 4.4 | | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section | Multicast Flow Query Request and Response messages | | Section 5.1 | Multicast-Service-Profile TLV, grey lists only |
| 4.9 | | | | |
| | | | Section 5.2 | Multicast-Service-Profile-Name TLV |
| Section | Multicast-Service-Profile TLV, grey lists only | | | |
| 5.1 | | | Section 5.3 | List-Action TLV, grey lists only |
| | | | | |
| Section | Multicast-Service-Profile-Name TLV | | Section 5.4 | Sequence Number TLV |
| 5.2 | | | | |
| | | | Section 5.5 | Bandwidth-Allocation TLV |
| Section | List-Action TLV, grey lists only | | | |
| 5.3 | | | Section 5.7 | MRepCtl-CAC TLV |
| | | | | |
| Section | Sequence Number TLV | | Section 5.9 | Request-Source-IP TLV |
| 5.4 | | | | |
| | | | Section 5.10 | Request-Source-MAC TLV |
| Section | Bandwidth-Allocation TLV | | | |
| 5.5 | | | Section 5.11 | Request-Source-Device-Id TLV |
| | | | | |
| Section | MRepCtl-CAC TLV | | Section 5.12 | Multicast-Flow 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 Table 4: Protocol Requirements For Conditional Access with Grey Lists
6.1.5. Protocol Requirements For Delegated Bandwidth 6.1.5. Protocol Requirements For Delegated Bandwidth
Table 5 specifies the protocol elements within Section 4 and Table 5 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the delegated bandwidth Section 5 that MUST be implemented to support the delegated bandwidth
multicast capability. multicast capability.
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Section 4.2 | Port Management message with Bandwidth-Allocation | | Section 4.2 | Port Management message with Bandwidth-Allocation |
| | TLV. | | | TLV. |
| | | | | |
skipping to change at page 53, line 28 skipping to change at page 55, line 25
| Section 4.7 | Delegated Bandwidth Query Request Message | | Section 4.7 | Delegated Bandwidth Query Request Message |
| | | | | |
| Section 4.8 | Delegated Bandwidth Query Response Message | | Section 4.8 | Delegated Bandwidth Query Response Message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section 5.5 | Bandwidth-Allocation TLV | | Section 5.5 | Bandwidth-Allocation TLV |
| | | | | |
| Section 5.8 | Bandwidth-Request TLV | | Section 5.8 | Bandwidth-Request TLV |
| | | | | |
| Section 5.10 | Multicast-Flow TLV | | Section 5.12 | 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.
skipping to change at page 58, line 4 skipping to change at page 59, line 47
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
be configured to add a subscriber session identifier as described in add information identifying the requesting device.
[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 resource-based admission control if that 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
skipping to change at page 62, line 4 skipping to change at page 64, line 6
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.
7. Security Considerations 7. Security Considerations
The security considerations of ANCP are discussed in [RFC6320] and in The security considerations of ANCP are discussed in [RFC6320] and in
[RFC5713]. Multicast does not in principle introduce any new [RFC5713]. Multicast does not in principle introduce any new
security considerations, although it does increase the attractiveness security considerations, although it does increase the attractiveness
of the ANCP protocol as a means of denial of service (e.g., through of the ANCP protocol as a means of denial of service (e.g., through
direction of multicast streams onto the target) or theft of service. direction of multicast streams onto the target) or theft of service.
As mentioned in Section 4.4, the inclusion of the Request-Source-MAC
or Request-Source-IP TLV in the Multicast Admission Control message
presents privacy issues. An attacker able to to get access to the
contents of this message would, like the content provider, be able to
track consumption of multicast content to the individual device and
potentially to individual persons if they are associated with
particular devices. To make the connection between devices and
individuals, the attacker needs to get information from sources other
than ANCP, of course, but let us assume that this has happened.
The protection specified for ANCP in [RFC6320] will apply to the
transmission of the Multicast Admission Control message across the
access network to the NAS. Hence the attacker's potential points of
access are between the subscriber and the AN, at the AN and at the
NAS. Moreover, if the MAC or IP address are transmitted onwards from
the NAS to AAA in a request for policy, that whole onward path has to
be examined for vulnerability.
The question is how many of these potential points of attack can be
eliminated through operational practice. The segment from the
subscriber through the AN itself seems out of scope of this
discussion -- protection of this segment is basic to subscriber
privacy in any event, and likely a business requirement. The segment
from the AN to the NAS is covered by the basic ANCP protection
specified in RFC 6320. This leaves the NAS and the path between the
NAS and AAA for consideration.
The operator can eliminate the path between the NAS and AAA as a
point where the attacker can access per-device information by
downloading per- device policy to the NAS for all identified user
devices for the particular subscriber. The NAS then selects the
applicable policy based on the particular device identifier it has
received. This is as opposed to the NAS sending the identifier of
the device in question to AAA and getting policy just for that
device.
This leaves the NAS itself as a point of attack. In theory the NAS
could be eliminated if the AN remapped the requesting MAC or IP
address to an identifier known to itself and AAA, but not the NAS.
This would require local configuration on the AN, which may be
possible under some circumstances. The Request-Source-Device-Id TLV
specified in Section 5.11 is available to transmit such an identifier
in place of the Request-Source-MAC or Request-Source-IP.
8. IANA Considerations 8. IANA Considerations
IANA NOTE: Please replace XXXX with the RFC number of this document. IANA NOTE: Please replace XXXX with the RFC number of this document.
This document defines the following additional values within the ANCP This document defines the following additional values within the ANCP
Message Type Name Space registry: Message Type Name Space registry:
+--------------+--------------------------------+-----------+ +--------------+--------------------------------+-----------+
| Message Type | Message Name | Reference | | Message Type | Message Name | Reference |
+--------------+--------------------------------+-----------+ +--------------+--------------------------------+-----------+
skipping to change at page 64, line 26 skipping to change at page 67, 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 | Sub-Session-Id | RFC XXXX | | 0x0092 | Request-Source-IP | 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 |
| | | |
| 0x0096 | Request-Source-Device-Id | RFC XXXX |
+-----------+--------------------------------+-----------+ +-----------+--------------------------------+-----------+
This document defines the following additional values for the ANCP This document defines the following additional values for the ANCP
Capability Type registry: Capability Type registry:
+-------+-------------------------+--------+------------+-----------+ +-------+-------------------------+--------+------------+-----------+
| Value | Capability Type Name | Tech | Capability | Reference | | Value | Capability Type Name | Tech | Capability | Reference |
| | | Type | Data? | | | | | Type | Data? | |
+-------+-------------------------+--------+------------+-----------+ +-------+-------------------------+--------+------------+-----------+
| 3 | NAS-Initiated | 0 | No | RFC XXXX | | 3 | NAS-Initiated | 0 | No | RFC XXXX |
skipping to change at page 66, line 16 skipping to change at page 69, line 16
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.
[TR-146] Broadband Forum, "TR-146, Subscriber Sessions", May 2013.
10.2. Informative References 10.2. Informative References
[IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
EUI48.html", 2010.
[IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
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.
Wadhwa, "Framework and Requirements for an Access Node Wadhwa, "Framework and Requirements for an Access Node
skipping to change at page 67, line 28 skipping to change at page 70, line 33
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 providing the profile for our assumed subscriber is shown in
Figure 19. The message has the following contents: Figure 21. 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
skipping to change at page 69, line 22 skipping to change at page 72, line 28
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = White-List-CAC 0x0024 | TLV Length = 0 | | Type = White-List-CAC 0x0024 | TLV Length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 19: Example Provisioning Message Figure 21: Example Provisioning Message
Note that the padding after the middle List-Action TLV is counted as Note that the padding after the middle List-Action TLV is counted as
part of length of the Multicast-Service-Profile TLV, but is not part of length of the Multicast-Service-Profile TLV, but is not
included in the length of that List-Action TLV. Note also that the included in the length of that List-Action TLV. Note also that the
Length field in the message header, unlike those in the TLVs, Length field in the message header, unlike those in the TLVs,
includes the message header itself, as required by [RFC6320]. 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 resource-based admission control MRepCtl-CAC TLV since in our example resource-based admission control
for grey listed flows and for NAS-initiated replication is performed for grey listed flows and for NAS-initiated replication is performed
by the 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 bandwidth. The corresponding message flow is illustrated in
Figure 20. Figure 22.
+----------+ +---------+ +-----+ +-----+ +----------+ +---------+ +-----+ +-----+
|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 70, line 25 skipping to change at page 73, 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 20: Configuring an AN Port With Multicast Service Profile ID Figure 22: 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 21) just shows the Target, Multicast-Service-Profile- example (Figure 23) 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:
skipping to change at page 72, line 47 skipping to change at page 75, line 47
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast service profile name | | Multicast service profile name |
~ = "Cust 0127-53681-0003" ~ ~ = "Cust 0127-53681-0003" ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth-Allocation 0x0015 | TLV Length = 4 | | Bandwidth-Allocation 0x0015 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth value = 2000 (kbits/s) | | Bandwidth value = 2000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 21: Example Port Management Message Figure 23: 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 22 illustrates the resulting ANCP message flow for the flow. Figure 24 illustrates the resulting ANCP message flow for the
case of a simple join and leave, when resource-based admission case of a simple join and leave, when resource-based admission
control for grey-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.
skipping to change at page 73, line 44 skipping to change at page 76, line 49
| 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 22: Successful Join/Leave Operations, Grey-Listed Flow Figure 24: 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 is 145; * Message Type is 145;
* Result = Ignore (0x0); * Result = Ignore (0x0);
* a transaction identifier assigned by the 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);
skipping to change at page 74, line 21 skipping to change at page 77, line 26
* Command Code = "Add" (1); * Command Code = "Add" (1);
* Accounting = "No" (0); * Accounting = "No" (0);
* a Multicast-Flow embedded TLV indicating the multicast flow for * a Multicast-Flow embedded TLV indicating the multicast flow for
which the AN received the IGMP Join: flow type "SSM" (2), which the AN received the IGMP Join: flow type "SSM" (2),
address family "IPv4" (1), Group address = 233.252.0.67, Source address family "IPv4" (1), Group address = 233.252.0.67, Source
Address = 192.0.2.21; Address = 192.0.2.21;
* a Subs-Session-Identifier embedded TLV containing the value * a Request-Source-Device-Id embedded TLV containing the IGMP
0x0C000264. join source local device identifier value 5.
The Multicast Admission Control message M1 is illustrated in The Multicast Admission Control message M1 is illustrated in
Figure 23: 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 = 98 | | Type (0x880C) | Length = 98 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=145 | Res=0 | Result Code = 0 | | Version | Msg Type=145 | Res=0 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 75, line 34 skipping to change at page 78, line 34
| Cmd Code = 1 | Acctg = 0 | Reserved = 0x0000 | | Cmd Code = 1 | Acctg = 0 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Type = 2 | Addr Fam = 1 | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
|Subs-Session-Identifier 0x0092 | Embedded TLV length = 4 | |Request-Source-Device-Id 0x0092| Embedded TLV length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value = 0x0C000264 | | Value = 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 23: Multicast Admission Control Message Seeking To Add A Flow Figure 25: 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 = "Multicast Replication Control" (144); * Message Type = "Multicast Replication Control" (144);
* Result= 0x1 (NAck); * Result= 0x1 (NAck);
* a transaction identifier assigned by the NAS; * a transaction identifier assigned by the NAS;
skipping to change at page 76, line 17 skipping to change at page 79, line 17
* Accounting = "Yes" (1), since in our example the operator wants * Accounting = "Yes" (1), since in our example the operator wants
accounting on this flow. accounting on this flow.
* a Multicast-Flow embedded TLV indicating the multicast flow * a Multicast-Flow embedded TLV indicating the multicast flow
that the NAS is admitting for this access line: flow type "SSM" that the NAS is admitting for this access line: flow type "SSM"
(2), address family "IPv4" (1), Group address = 233.252.0.67, (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 The Multicast Admission Control message M2 is illustrated in
Figure 24. Figure 26.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x880C) | Length = 48 | | Type (0x880C) | Length = 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=144 | Res=1 | Result Code = 0 | | Version | Msg Type=144 | Res=1 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 76, line 49 skipping to change at page 79, line 49
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Type = 2 | Addr Fam = 1 | 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 24: Multicast Replication Control Message Admitting A Flow Figure 26: 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 is 145; * Message Type is 145;
* Result = Ignore (0x0) * Result = Ignore (0x0)
skipping to change at page 77, line 29 skipping to change at page 80, line 29
* a Command Code = "Delete" (2); * a Command Code = "Delete" (2);
* Accounting = "No" (0); * Accounting = "No" (0);
* a Multicast-Flow embedded TLV indicating the multicast flow for * a Multicast-Flow embedded TLV indicating the multicast flow for
which the AN received the IGMP leave: flow type "SSM" (2), which the AN received the IGMP leave: flow type "SSM" (2),
address family "IPv4" (1), Group address = 233.252.0.67, Source address family "IPv4" (1), Group address = 233.252.0.67, Source
Address = 192.0.2.21. Address = 192.0.2.21.
* a Subs-Session-Identifier embedded TLV containing the value * a Request-Source-Device-Id embedded TLV containing the IGMP
0x0C000264. leave request source, the device identified by the local value
5.
The Multicast Admission Control message M3 is illustrated in The Multicast Admission Control message M3 is illustrated in
Figure 25. Figure 27.
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 | Res=0 | Result Code = 0 | | Version | Msg Type=145 | Res=0 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 78, line 34 skipping to change at page 81, line 34
| Cmd Code = 2 | Acctg = 0 | Reserved = 0x0000 | | Cmd Code = 2 | Acctg = 0 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast-Flow Type = 0x0019 | Embedded TLV Length = 12 | | Multicast-Flow Type = 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Type = 2 | Addr Fam = 1 | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Subs-Session-Identifier 0x0092 | Embedded TLV length = 4 | |Request-Source-Device-Id 0x0092| Embedded TLV length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value = 0x0C000264 | | Value = 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 25: Multicast Admission Control Message Signalling Flow Figure 27: 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 79, line 26 skipping to change at page 82, 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 26. The complete message flow is shown in Figure 28.
+----------+ +-------+ +-----+ 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 80, line 43 skipping to change at page 83, line 43
| | |<------------------|(M3) | | |<------------------|(M3)
| | | | | | | |
| | |Delegated Bandwidth| | | |Delegated Bandwidth|
| | | Query response | | | | Query response |
| | |------------------>|(M4) | | |------------------>|(M4)
| | | | | | | |
(*) The NAS may optionally seek direction from an external (*) The NAS may optionally seek direction from an external
Authorization/Policy Server Authorization/Policy Server
Figure 26: Successful Join/Leave Operations, White-Listed Flow Figure 28: Successful Join/Leave Operations, White-Listed Flow
The Bandwidth Reallocation Request message (M1) is shown in The Bandwidth Reallocation Request message (M1) is shown in
Figure 27. The contents require little explanation. The Message Figure 29. The contents require little explanation. The Message
Type for the Bandwidth Reallocation Request is 146. The Result field Type for the Bandwidth Reallocation Request is 146. The Result field
is set to Ignore (0x0). Besides the Target, the message has one is set to Ignore (0x0). Besides the Target, the message has one
other TLV, the Bandwidth-Request, with a TLV Type of 0x0016. The TLV other TLV, the Bandwidth-Request, with a TLV Type of 0x0016. The TLV
contains Required Amount and Preferred Amount fields, set to 4000 and contains Required Amount and Preferred Amount fields, set to 4000 and
6000 kbits/s respectively. 6000 kbits/s respectively.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x880C) | Length = 36 | | Type (0x880C) | Length = 36 |
skipping to change at page 81, line 29 skipping to change at page 84, line 29
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth-Request 0x0016 | TLV Length = 8 | | Bandwidth-Request 0x0016 | TLV Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required Amount = 4000 (kbits/s) | | Required Amount = 4000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Preferred Amount = 6000 (kbits/s) | | Preferred Amount = 6000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 27: Bandwidth Reallocation Request Message Figure 29: Bandwidth Reallocation Request Message
The Bandwidth Transfer message (M2) is shown in Figure 28. Again, The Bandwidth Transfer message (M2) is shown in Figure 30. 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 0x0015 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 |
skipping to change at page 82, line 27 skipping to change at page 85, line 27
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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-Allocation 0x0015 | TLV Length = 4 | | Bandwidth-Allocation 0x0015 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delegated Amount = 4000 (kbits/s) | | Delegated Amount = 4000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 28: NAS Response, Bandwidth Transfer Message Figure 30: NAS Response, Bandwidth Transfer Message
The Delegated Bandwidth Query request message (M3) is shown in The Delegated Bandwidth Query request message (M3) is shown in
Figure 29. The Message Type for the Delegated Bandwidth Query Figure 31. The Message Type for the Delegated Bandwidth Query
request message is 148. The Result field is set to AckAll (0x2). request message is 148. The Result field is set to AckAll (0x2).
The message contains the Target TLV only. The message contains the Target TLV only.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x880C) | Length = 24 | | Type (0x880C) | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=148 | Res=2 | Result Code = 0 | | Version | Msg Type=148 | Res=2 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 82, line 52 skipping to change at page 85, line 52
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length = 24 | |I| SubMessage Number | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = Target 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 29: Delegated Bandwidth Query Request Message Figure 31: 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 30. The Message Type for the Delegated Bandwidth Query in Figure 32. 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 | Res=2 | Result Code = 0 | | Version | Msg Type=148 | Res=2 | Result Code = 0 |
skipping to change at page 83, line 33 skipping to change at page 86, line 33
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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-Allocation 0x0015 | TLV Length = 4 | | Bandwidth-Allocation 0x0015 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delegated Amount = 4000 (kbits/s) | | Delegated Amount = 4000 (kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 30: Delegated Bandwidth Query Response Message Figure 32: 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 84, line 12 skipping to change at page 87, 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 31. in Figure 33.
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 84, line 50 skipping to change at page 87, 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 31: NAS-Initiated Flows For On-Line Gaming Figure 33: NAS-Initiated Flows For On-Line Gaming
Multicast Replication Control message (M1) in Figure 32 looks like Multicast Replication Control message (M1) in Figure 34 looks like
the message in Figure 24 with two exceptions. The first is that the the message in Figure 26 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 = 1) with IPv4 (1) 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
skipping to change at page 85, line 43 skipping to change at page 88, line 43
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code = 1 | Acctg = 1 | Reserved = 0x0000 | | Cmd Code = 1 | Acctg = 1 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Type = 1 | Addr Fam = 1 | 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 32: Enabling The Subscriber To Join An On-Line Game Figure 34: 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 32 with two exceptions: the looks the same as the message in Figure 34 with two exceptions: the
Command Code becomes "Delete" (2), and Accounting is set to "No" (0) Command Code becomes "Delete" (2), and Accounting is set to "No" (0)
to turn off flow accounting. Of course, the Transaction Identifier to turn off flow accounting. Of course, the Transaction Identifier
values 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 33 illustrates a message flow in a case where the NAS queries Figure 35 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 33: Per-Port Multicast Flow Reporting Figure 35: 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 34. The Message Type is 149. The Result field is set to Figure 36. 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| Res=1 | Result Code = 0 | | Version | Msg Type = 149| Res=1 | Result Code = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 87, line 41 skipping to change at page 90, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV 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 (port11) ~ ~ Access Loop Circuit ID (port11) ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 34: Multicast Flow Query Request Message For Per-Port Figure 36: 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 35. It indicates that there is one active multicast flow Figure 37. 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 |
skipping to change at page 89, line 13 skipping to change at page 92, line 13
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
| Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 | | Type = Multicast-Flow 0x0019 | Embedded TLV Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Type = 2 | Addr Fam = 1 | 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 35: Multicast Flow Query Response message For Per-Port Figure 37: 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
 End of changes. 111 change blocks. 
231 lines changed or deleted 364 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/