< draft-ietf-ancp-mc-extensions-09.txt   draft-ietf-ancp-mc-extensions-10.txt >
ANCP F. Le Faucheur ANCP F. Le Faucheur
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track R. Maglione Intended status: Standards Track R. Maglione
Expires: August 28, 2013 Cisco Systems Expires: February 23, 2014 Cisco Systems
T. Taylor T. Taylor
Huawei Huawei
February 24, 2013 August 22, 2013
Multicast Control Extensions for ANCP Multicast Control Extensions for ANCP
draft-ietf-ancp-mc-extensions-09.txt draft-ietf-ancp-mc-extensions-10.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 1, line 35 skipping to change at page 1, line 35
o conditional access with grey lists; o conditional access with grey lists;
o bandwidth delegation; o bandwidth delegation;
o committed bandwidth reporting. o committed bandwidth reporting.
These capabilities may be combined according to the rules given in These capabilities may be combined according to the rules given in
this specification. this specification.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 28, 2013. This Internet-Draft will expire on February 23, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 7 skipping to change at page 2, line 35
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 8 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 9 3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 6
3.1. NAS Initiated Multicast Replication Control Use Case . . . 9 3.1. NAS Initiated Multicast Replication Control Use Case . . 7
3.1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9 3.1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 10 3.1.2. Message Flow . . . . . . . . . . . . . . . . . . . . 7
3.2. Conditional Access and Admission Control Use Case . . . . 10 3.2. Conditional Access and Admission Control Use Case . . . . 8
3.2.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10 3.2.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 11 3.2.2. Message Flow . . . . . . . . . . . . . . . . . . . . 8
3.3. Multicast Flow Reporting Use Case . . . . . . . . . . . . 12 3.3. Multicast Flow Reporting Use Case . . . . . . . . . . . . 9
3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 12 3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 12 3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 9
3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . . 13 3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . 10
3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 13 3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 13 3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10
4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 15 4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1. Provisioning Message . . . . . . . . . . . . . . . . . . . 15 4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 11
4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 15 4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12
4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 16 4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 13
4.2. Port Management Message . . . . . . . . . . . . . . . . . 17 4.2. Port Management Message . . . . . . . . . . . . . . . . . 14
4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 18 4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 15
4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 18 4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 15
4.3. Multicast Replication Control Message . . . . . . . . . . 19 4.3. Multicast Replication Control Message . . . . . . . . . . 16
4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 22 4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 19
4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 23 4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 20
4.4. Multicast Admission Control Message . . . . . . . . . . . 25 4.4. Multicast Admission Control Message . . . . . . . . . . . 22
4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 26 4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 23
4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 27 4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 24
4.5. Bandwidth Reallocation Request Message . . . . . . . . . . 28 4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25
4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 29 4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25
4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 29 4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26
4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . . 32 4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29
4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 33 4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 30
4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 33 4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30
4.7. Delegated Bandwidth Query Request Message . . . . . . . . 34 4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31
4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 35 4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31
4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 35 4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 31
4.8. Delegated Bandwidth Query Response Message . . . . . . . . 35 4.8. Delegated Bandwidth Query Response Message . . . . . . . 32
4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 36 4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32
4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 36 4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32
4.9. Multicast Flow Query Request and Response Messages . . . . 37 4.9. Multicast Flow Query Request and Response Messages . . . 33
4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 37 4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 34
4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 38 4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34
4.10. Committed Bandwidth Report Message . . . . . . . . . . . . 39 4.10. Committed Bandwidth Report Message . . . . . . . . . . . 36
4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 39 4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 36
4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 40 4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36
5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 37
5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 41 5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 37
5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 41 5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . 38
5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . . 42 5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 39
5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 42 5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 41
5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 45 5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . 42
5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . . 45 5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . 42
5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . . 46 5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 43
5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 47 5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43
5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 47 5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 44
5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 48 5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . 44
5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . . 48 5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45
5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . . 49 5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46
5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 50 5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 47
5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 51 6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47
6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . . 52 6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48
6.1. Required Protocol Support . . . . . . . . . . . . . . . . 52 6.1.1. Protocol Requirements For NAS-Initiated Replication . 48
6.1.1. Protocol Requirements For NAS-Initiated Replication . 53
6.1.2. Protocol Requirements For Committed Multicast 6.1.2. Protocol Requirements For Committed Multicast
Bandwidth Reporting . . . . . . . . . . . . . . . . . 53 Bandwidth Reporting . . . . . . . . . . . . . . . . . 49
6.1.3. Protocol Requirements For Conditional Access With 6.1.3. Protocol Requirements For Conditional Access With
White and Black Lists . . . . . . . . . . . . . . . . 54 White and Black Lists . . . . . . . . . . . . . . . . 50
6.1.4. Protocol Requirements For Conditional Access With 6.1.4. Protocol Requirements For Conditional Access With
Grey Lists . . . . . . . . . . . . . . . . . . . . . . 55 Grey Lists . . . . . . . . . . . . . . . . . . . . . 50
6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 56 6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 52
6.2. Capability-Specific Procedures for Providing Multicast 6.2. Capability-Specific Procedures for Providing Multicast
Service . . . . . . . . . . . . . . . . . . . . . . . . . 57 Service . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.2.1. Procedures For NAS-Initiated Replication . . . . . . . 57 6.2.1. Procedures For NAS-Initiated Replication . . . . . . 52
6.2.2. Procedures For Committed Bandwidth Reporting . . . . . 58 6.2.2. Procedures For Committed Bandwidth Reporting . . . . 53
6.2.3. Procedures For Conditional Access With Black and 6.2.3. Procedures For Conditional Access With Black and
White Lists . . . . . . . . . . . . . . . . . . . . . 59 White Lists . . . . . . . . . . . . . . . . . . . . . 54
6.2.4. Procedures For Conditional Access With Grey Lists . . 61 6.2.4. Procedures For Conditional Access With Grey Lists . . 56
6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . . 62 6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 57
6.3. Combinations of Multicast Capabilities . . . . . . . . . . 63 6.3. Combinations of Multicast Capabilities . . . . . . . . . 58
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 . . 63 Black Lists and Conditional Access With Grey Lists . 58
6.3.2. Combination of Conditional Access With Delegated 6.3.2. Combination of Conditional Access With Delegated
Bandwidth . . . . . . . . . . . . . . . . . . . . . . 64 Bandwidth . . . . . . . . . . . . . . . . . . . . . . 60
6.3.3. Combination of NAS-Initiated Replication with 6.3.3. Combination of NAS-Initiated Replication with Other
Other Capabilities . . . . . . . . . . . . . . . . . . 64 Capabilities . . . . . . . . . . . . . . . . . . . . 60
6.3.4. Combinations of Committed Bandwidth Reporting with 6.3.4. Combinations of Committed Bandwidth Reporting with
Other Multicast Capabilities . . . . . . . . . . . . . 65 Other Multicast Capabilities . . . . . . . . . . . . 61
7. Security Considerations . . . . . . . . . . . . . . . . . . . 66 7. Security Considerations . . . . . . . . . . . . . . . . . . . 61
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 71 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 64
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 64
10.1. Normative References . . . . . . . . . . . . . . . . . . . 72 10.1. Normative References . . . . . . . . . . . . . . . . . . 64
10.2. Informative References . . . . . . . . . . . . . . . . . . 72 10.2. Informative References . . . . . . . . . . . . . . . . . 64
Appendix A. Example of Messages and Message Flows . . . . . . . . 74 Appendix A. Example of Messages and Message Flows . . . . . . . 65
A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . . 74 A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 66
A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 80 A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 70
A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 85 A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 75
A.4. Handling Of Black-Listed Join Requests . . . . . . . . . . 90 A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 79
A.5. Handling Of Requests To Join and Leave the On-Line Game . 90 A.5. Handling Of Requests To Join and Leave the On-Line Game . 80
A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 93 A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 82
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 85
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 7, line 30 skipping to change at page 6, line 19
The AN reports the amount of multicast bandwidth it has granted to a The AN reports the amount of multicast bandwidth it has granted to a
given access line each time that value changes. These reports may be given access line each time that value changes. These reports may be
buffered for a NAS-provisionable interval so that reports for buffered for a NAS-provisionable interval so that reports for
multiple access lines can be bundled into the same message. multiple access lines can be bundled into the same message.
The formal specification of the behaviours associated with each of The formal specification of the behaviours associated with each of
these capabilities, singly and in combination, is given in Section 6. these capabilities, singly and in combination, is given in Section 6.
In addition to the multicast service processing behaviour just In addition to the multicast service processing behaviour just
sketched, the definition of each capability includes support for the sketched, the definition of each capability includes support for the
multicast accounting and reporting services described in Section multicast accounting and reporting services described in
3.4.3 of [RFC5851]. Because of this common content and because of Section 3.4.3 of [RFC5851]. Because of this common content and
other protocol overlaps between the different capabilities, the because of other protocol overlaps between the different
protocol descriptions for the multicast extensions specified in this capabilities, the protocol descriptions for the multicast extensions
document are merged into a single non-redundant narrative. Tables in specified in this document are merged into a single non-redundant
Section 6 then indicate the specific sub-sections of the protocol narrative. Tables in Section 6 then indicate the specific sub-
description that have to be implemented to support each capability. sections of the protocol description that have to be implemented to
support each capability.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The expression "delegated bandwidth" is used as a shorter way of The expression "delegated bandwidth" is used as a shorter way of
saying: "the total amount of video bandwidth delegated to the AN for saying: "the total amount of video bandwidth delegated to the AN for
multicast admission control". multicast admission control".
skipping to change at page 20, line 5 skipping to change at page 16, line 44
o a Command Code field; o a Command Code field;
o an Accounting field; o an Accounting field;
o an instance of the Multicast-Flow TLV. o an instance of the Multicast-Flow TLV.
Figure 5 illustrates the complete Command TLV with the contents Figure 5 illustrates the complete Command TLV with the contents
specific to the Multicast Replication Control message. specific to the Multicast Replication Control message.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type = Command | Command-TLV Length | | TLV Type = Command | Command-TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Command Code | Accounting | Reserved | |Command Code | Accounting | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast-Flow TLV | | Multicast-Flow TLV |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Other embedded TLV Type | Other embedded TLV Length | | Other embedded TLV Type | Other embedded TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Other embedded TLV data ~ ~ Other embedded TLV data ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Contents of the Command TLV in the Multicast Replication Figure 5: Contents of the Command TLV in the Multicast Replication
Control Message Control Message
Command Code: Command Code:
Command directive: Command directive:
1 - Add; 1 - Add;
2 - Delete; 2 - Delete;
3 - Delete All; 3 - Delete All;
4 - Admission Control Reject; 4 - Admission Control Reject;
5 - Conditional Access Reject; 5 - Conditional Access Reject;
6 - Admission Control and Conditional Access 6 - Admission Control and Conditional Access Reject.
Reject.
Directives 4 through 6 are used as described in Directives 4 through 6 are used as described in
Section 4.4.2. Section 4.4.2.
Accounting: Accounting:
Meaningful only when the Command Code is "Add" (1). In Meaningful only when the Command Code is "Add" (1). In
that case, 0x00 indicates no flow accounting, 0x01 that case, 0x00 indicates no flow accounting, 0x01
indicates that octet accounting for the flow is to indicates that octet accounting for the flow is to
commence. The Accounting field MUST be set to 0x00 for commence. The Accounting field MUST be set to 0x00 for
other Command Code values. other Command Code values.
skipping to change at page 21, line 16 skipping to change at page 18, line 4
Reserved for future use. MUST be set to 0x0000 by the Reserved for future use. MUST be set to 0x0000 by the
sender and ignored by the receiver. sender and ignored by the receiver.
Multicast-Flow TLV: Multicast-Flow TLV:
An instance of the Multicast-Flow TLV (Section 5.11) An instance of the Multicast-Flow TLV (Section 5.11)
specifying the flow to be added or deleted. The Multicast- specifying the flow to be added or deleted. The Multicast-
Flow TLV MUST be omitted if the Command Code has value Flow TLV MUST be omitted if the Command Code has value
"Delete All" (3). "Delete All" (3).
Other embedded TLV: Other embedded TLV:
No other embedded TLVs are currently specified within the No other embedded TLVs are currently specified within the
Multicast Replication Control message/Command TLV. Multicast Replication Control message/Command TLV.
However, see the description of the Multicast Admission However, see the description of the Multicast Admission
Control message (Section 4.4). Unrecognized embedded TLVs Control message (Section 4.4). Unrecognized embedded TLVs
SHOULD be silently discarded. SHOULD be silently discarded.
The figure below is an example of a Multicast Replication Control The figure below is an example of a Multicast Replication Control
message that would result in a swap from multicast Source-Specific message that would result in a swap from multicast Source-Specific
Multicast (SSM) flows 2001:DB8::1, FF34::2, to 2001:DB8::2, FF34::3 Multicast (SSM) flows 2001:DB8::1, FF34::2, to 2001:DB8::2, FF34::3
on the Target identified by the "Access Loop Circuit ID": on the Target identified by the "Access Loop Circuit ID":
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x880C) | Length | | Type (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | MsgType=144 | 0x02 | Result Code | | Version | MsgType=144 | 0x02 | Result Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier = 0001 | | Partition ID | Transaction Identifier = 0001 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length | |I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Target 0x1000 | Target TLV Length | | Type = Target 0x1000 | Target TLV Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Access Loop Circuit ID ~ ~ Access Loop Circuit ID ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Command TLV | Command-TLV Length = 0x0014 | | Type = Command TLV | Command-TLV Length = 0x0014 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=2 |Acctg = 0x00 | Reserved = 0x0000 | | Cmd Code=2 |Acctg = 0x00 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = Multicast-Flow | TLV Length = 0x000C | |TLV Type = Multicast-Flow | TLV Length = 0x000C |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 | |Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Multicast Group Address ~ ~ Multicast Group Address ~
| = FF34::2 | | = FF34::2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Source Address ~ ~ Source Address ~
| = 2001:DB8::1 | | = 2001:DB8::1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Command-TLV | Command-TLV Length = 0x0014 | | Type = Command-TLV | Command-TLV Length = 0x0014 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cmd Code=1 |Acctg = 0x01 | Reserved = 0x0000 | | Cmd Code=1 |Acctg = 0x01 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = Multicast-Flow | TLV Length = 0x000C | |TLV Type = Multicast-Flow | TLV Length = 0x000C |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 | |Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multicast Group Address = FF34::3 | | Multicast Group Address = FF34::3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Address = 2001:DB8::2 | | Source Address = 2001:DB8::2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
| | | |
~ Multicast Group Address ~ ~ Multicast Group Address ~
| = FF34::3 | | = FF34::3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Source Address ~ ~ Source Address ~
| = 2001:DB8::2 | | = 2001:DB8::2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.3.1. Sender Behaviour 4.3.1. Sender Behaviour
The NAS MAY issue a Multicast Replication Control message to the AN The NAS MAY issue a Multicast Replication Control message to the AN
to convey one or more directives to add (join) or delete (leave) one to convey one or more directives to add (join) or delete (leave) one
or more multicast flows. or more multicast flows.
The NAS MAY send this message on its own initiative to support the The NAS MAY send this message on its own initiative to support the
NAS initiated Multicast Control use case presented in [RFC5851] and NAS initiated Multicast Control use case presented in [RFC5851] and
summarized in Section 3.1. In that case, the NAS MUST set the Result summarized in Section 3.1. In that case, the NAS MUST set the Result
skipping to change at page 44, line 36 skipping to change at page 40, line 43
The scope of the designation may be broadened to multiple channels or The scope of the designation may be broadened to multiple channels or
groups through use of prefix length values smaller than the total groups through use of prefix length values smaller than the total
address length for the given address family. Multicast flow fields address length for the given address family. Multicast flow fields
MUST be placed consecutively within the embedded TLV without MUST be placed consecutively within the embedded TLV without
intervening padding except to round out individual addresses to the intervening padding except to round out individual addresses to the
nearest octet boundary. nearest octet boundary.
A multicast flow field consists of two single-octet prefix lengths A multicast flow field consists of two single-octet prefix lengths
followed by zero to two prefix values as shown in Figure 9: followed by zero to two prefix values as shown in Figure 9:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Group PrefLen | | Group PrefLen |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Source PrefLen| | Source PrefLen|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Group Prefix (multicast) (0 to 16 octets) | | Group Prefix (multicast) (0 to 16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Prefix (unicast, SSM only) (0 to 16 octets) | | Source Prefix (unicast, SSM only) (0 to 16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9: Organization of a Single Multicast Flow Field Figure 9: Organization of a Single Multicast Flow Field
The prefix length has its usual meaning. It is the number of most- The prefix length has its usual meaning. It is the number of most-
significant bits specified within the corresponding prefix. The significant bits specified within the corresponding prefix. The
prefix length MAY vary from 0 to 32 in the IPv4 sub-list, and from 0 prefix length MAY vary from 0 to 32 in the IPv4 sub-list, and from 0
to 128 in the IPv6 sub-list. to 128 in the IPv6 sub-list.
A value of 0x00 for either the Group PrefLen (prefix length) or the A value of 0x00 for either the Group PrefLen (prefix length) or the
Source PrefLen indicates that any value of the corresponding address Source PrefLen indicates that any value of the corresponding address
will match (wild card). If the value 0x00 is provided for a will match (wild card). If the value 0x00 is provided for a
skipping to change at page 53, line 6 skipping to change at page 49, line 4
to support each of the four multicast capabilities. Support of to support each of the four multicast capabilities. Support of
multiple multicast capabilities requires implementation of the union multiple multicast capabilities requires implementation of the union
of the sets of protocol elements applying to each of the individual of the sets of protocol elements applying to each of the individual
capabilities in the supported set. capabilities in the supported set.
In addition to the elements listed below, implementation of the In addition to the elements listed below, implementation of the
Target TLV (Section 4.3 of [RFC6320]) is REQUIRED for all of the Target TLV (Section 4.3 of [RFC6320]) is REQUIRED for all of the
capabilities specified in this document. capabilities specified in this document.
6.1.1. Protocol Requirements For NAS-Initiated Replication 6.1.1. Protocol Requirements For NAS-Initiated Replication
Table 1 specifies the protocol elements within Section 4 and Table 1 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the NAS-initiated Section 5 that MUST be implemented to support the NAS-initiated
replication multicast capability. Additionally, implementation of replication multicast capability. Additionally, implementation of
the Multicast Replication Control message requires implementation of the Multicast Replication Control message requires implementation of
the Command TLV (Section 4.4 of [RFC6320] with additional details in the Command TLV (Section 4.4 of [RFC6320] with additional details in
Section 4.3 of this document). Section 4.3 of this document).
+--------------+----------------------------------------------------+ +-----------------+-------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +-----------------+-------------------------------------------------+
| Section 4.1 | Provisioning message with MRepCtl-CAC TLV | | Section 4.1 | Provisioning message with MRepCtl-CAC TLV |
| | | | | |
| Section 4.2 | Port Management message with Bandwidth-Allocation | | Section 4.2 | Port Management message with Bandwidth- |
| | TLV. | | | Allocation TLV. |
| | | | | |
| Section 4.3 | Multicast Replication Control message | | Section 4.3 | Multicast Replication Control message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response |
| | | | | messages |
| Section 5.4 | 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.11 | Multicast-Flow TLV | | | |
+--------------+----------------------------------------------------+ | Section 5.11 | Multicast-Flow TLV |
+-----------------+-------------------------------------------------+
Table 1: Protocol Requirements For NAS-Initiated Replication Table 1: Protocol Requirements For NAS-Initiated Replication
6.1.2. Protocol Requirements For Committed Multicast Bandwidth 6.1.2. Protocol Requirements For Committed Multicast Bandwidth
Reporting Reporting
Table 2 specifies the protocol elements within Section 4 and Table 2 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the committed multicast Section 5 that MUST be implemented to support the committed multicast
bandwidth reporting capability. bandwidth reporting capability.
+--------------+----------------------------------------------------+ +-----------------+-------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +-----------------+-------------------------------------------------+
| Section 4.1 | Provisioning message with Report-Buffering-Time | | Section 4.1 | Provisioning message with Report-Buffering-Time |
| | TLV | | | TLV |
| | | | | |
| Section 4.10 | Committed Bandwidth Report message | | Section 4.10 | Committed Bandwidth Report message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response |
| | | | | messages |
| Section 5.12 | Report-Buffering-Timer TLV | | | |
| | | | Section 5.12 | Report-Buffering-Timer TLV |
| Section 5.13 | Committed-Bandwidth TLV | | | |
| | | | Section 5.13 | Committed-Bandwidth TLV |
| Section 5.11 | Multicast-Flow TLV | | | |
+--------------+----------------------------------------------------+ | Section 5.11 | Multicast-Flow TLV |
+-----------------+-------------------------------------------------+
Table 2: Protocol Requirements For Committed Multicast Bandwidth Table 2: Protocol Requirements For Committed Multicast Bandwidth
Reporting Reporting
6.1.3. Protocol Requirements For Conditional Access With White and 6.1.3. Protocol Requirements For Conditional Access With White and
Black Lists Black Lists
Table 3 specifies the protocol elements within Section 4 and Table 3 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the conditional access Section 5 that MUST be implemented to support the conditional access
with white and black lists multicast capability. with white and black lists multicast capability.
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Reference | Protocol Element | | Reference | Protocol Element |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
| Section 4.1 | Provisioning message with | | Section 4.1 | Provisioning message with Multicast-Service- |
| | Multicast-Service-Profile TLV, white and black | | | Profile TLV, white and black lists only, and |
| | lists only, and White-List-CAC TLV | | | White-List-CAC TLV |
| | | | | |
| Section 4.2 | Port Management message with | | Section 4.2 | Port Management message with Multicast-Service- |
| | Multicast-Service-Profile-Name and | | | Profile-Name and Bandwidth-Allocation TLVs. |
| | Bandwidth-Allocation TLVs. |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section 5.1 | Multicast-Service-Profile TLV | | Section 5.1 | Multicast-Service-Profile TLV |
| | | | | |
| Section 5.2 | Multicast-Service-Profile-Name TLV | | Section 5.2 | Multicast-Service-Profile-Name TLV |
| | | | | |
| Section 5.3 | List-Action TLV, white and black lists only | | Section 5.3 | List-Action TLV, white and black lists only |
| | | | | |
| Section 5.5 | Bandwidth-Allocation TLV | | Section 5.5 | Bandwidth-Allocation TLV |
skipping to change at page 55, line 35 skipping to change at page 51, line 4
| | | | | |
| Section 5.6 | White-List-CAC TLV | | Section 5.6 | White-List-CAC TLV |
| | | | | |
| Section 5.11 | Multicast-Flow TLV | | Section 5.11 | Multicast-Flow TLV |
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
Table 3: Protocol Requirements For Conditional Access with White and Table 3: Protocol Requirements For Conditional Access with White and
Black Lists Black Lists
6.1.4. Protocol Requirements For Conditional Access With Grey Lists 6.1.4. Protocol Requirements For Conditional Access With Grey Lists
Table 4 specifies the protocol elements within Section 4 and Table 4 specifies the protocol elements within Section 4 and
Section 5 that MUST be implemented to support the conditional access Section 5 that MUST be implemented to support the conditional access
with grey lists multicast capability. 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 4.1 | Provisioning message with | | Section 4.1 | Provisioning message with Multicast-Service- |
| | Multicast-Service-Profile TLV, grey lists only, | | | Profile TLV, grey lists only, and MRepCtl-CAC TLV |
| | and MRepCtl-CAC TLV |
| | | | | |
| Section 4.2 | Port Management message with | | Section 4.2 | Port Management message with Multicast-Service- |
| | Multicast-Service-Profile-Name and | | | Profile-Name and Bandwidth-Allocation TLVs. |
| | Bandwidth-Allocation TLVs. |
| | | | | |
| Section 4.3 | Multicast Replication Control message | | Section 4.3 | Multicast Replication Control message |
| | | | | |
| Section 4.4 | Multicast Admission Control Message | | Section 4.4 | Multicast Admission Control Message |
| | | | | |
| Section 4.9 | Multicast Flow Query Request and Response messages | | Section 4.9 | Multicast Flow Query Request and Response messages |
| | | | | |
| Section 5.1 | Multicast-Service-Profile TLV, grey lists only | | Section 5.1 | Multicast-Service-Profile TLV, grey lists only |
| | | | | |
| Section 5.2 | Multicast-Service-Profile-Name TLV | | Section 5.2 | Multicast-Service-Profile-Name TLV |
skipping to change at page 57, line 5 skipping to change at page 52, line 11
+--------------+----------------------------------------------------+ +--------------+----------------------------------------------------+
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- |
| | TLV. | | | Allocation TLV. |
| | | | | |
| Section 4.5 | Bandwidth Reallocation Request Message | | Section 4.5 | Bandwidth Reallocation Request Message |
| | | | | |
| Section 4.6 | Bandwidth Transfer Message | | Section 4.6 | Bandwidth Transfer Message |
| | | | | |
| 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.11 | Multicast-Flow TLV | | | |
+--------------+----------------------------------------------------+ | Section 5.11 | Multicast-Flow TLV |
+-----------------+-------------------------------------------------+
Table 5: Protocol Requirements For Delegated Bandwidth Table 5: Protocol Requirements For Delegated Bandwidth
6.2. Capability-Specific Procedures for Providing Multicast Service 6.2. Capability-Specific Procedures for Providing Multicast Service
This section describes multicast service procedures for each This section describes multicast service procedures for each
capability as if it were the only multicast capability within the capability as if it were the only multicast capability within the
negotiated set. Procedures involving combinations of multicast negotiated set. Procedures involving combinations of multicast
capabilities are described in Section 6.3. capabilities are described in Section 6.3.
skipping to change at page 67, line 33 skipping to change at page 62, line 5
| 148 | Delegated Bandwidth Query | RFC XXXX | | 148 | Delegated Bandwidth Query | RFC XXXX |
| | | | | | | |
| 149 | Multicast Flow Query | RFC XXXX | | 149 | Multicast Flow Query | RFC XXXX |
| | | | | | | |
| 150 | Committed Bandwidth Report | RFC XXXX | | 150 | Committed Bandwidth Report | RFC XXXX |
+--------------+--------------------------------+-----------+ +--------------+--------------------------------+-----------+
This document defines the following additional values for the ANCP This document defines the following additional values for the ANCP
Result Code registry: Result Code registry:
+------------+------------------------------------------+-----------+ +--------------+------------------------------------+---------------+
| Result | One-Line Description | Reference | | Result Code | One-Line Description | Reference |
| Code | | | +--------------+------------------------------------+---------------+
+------------+------------------------------------------+-----------+ | 0x64 | Command error. | RFC XXXX |
| 0x64 | Command error. | RFC XXXX | | | | |
| | | | | 0x65 | Invalid flow address. | RFC XXXX |
| 0x65 | Invalid flow address. | RFC XXXX | | | | |
| | | | | 0x66 | Multicast flow does not exist. | RFC XXXX |
| 0x66 | Multicast flow does not exist. | RFC XXXX | | | | |
| | | | | 0x67 | Invalid preferred bandwidth | RFC XXXX |
| 0x67 | Invalid preferred bandwidth amount. | RFC XXXX | | | amount. | |
| | | | | | | |
| 0x68 | Inconsistent views of delegated | RFC XXXX | | 0x68 | Inconsistent views of delegated | RFC XXXX |
| | bandwidth amount. | | | | bandwidth amount. | |
| | | | | | | |
| 0x69 | Bandwidth request conflict. | RFC XXXX | | 0x69 | Bandwidth request conflict. | RFC XXXX |
+------------+------------------------------------------+-----------+ +--------------+------------------------------------+---------------+
This document defines the following additional values for the ANCP This document defines the following additional values for the ANCP
Command Code registry: Command Code registry:
+----------------+--------------------------------------+-----------+ +-----------------+---------------------------------+---------------+
| Command Code | Command Code Directive Name | Reference | | Command Code | Command Code Directive Name | Reference |
| Value | | | | Value | | |
+----------------+--------------------------------------+-----------+ +-----------------+---------------------------------+---------------+
| 1 | Add | RFC XXXX | | 1 | Add | RFC XXXX |
| | | | | | | |
| 2 | Delete | RFC XXXX | | 2 | Delete | RFC XXXX |
| | | | | | | |
| 3 | Delete All | RFC XXXX | | 3 | Delete All | RFC XXXX |
| | | | | | | |
| 4 | Admission Control Reject | RFC XXXX | | 4 | Admission Control Reject | RFC XXXX |
| | | | | | | |
| 5 | Conditional Access Reject | RFC XXXX | | 5 | Conditional Access Reject | RFC XXXX |
| | | | | | | |
| 6 | Admission Control and Conditional | RFC XXXX | | 6 | Admission Control and | RFC XXXX |
| | Access Reject | | | | Conditional Access Reject | |
+----------------+--------------------------------------+-----------+ +-----------------+---------------------------------+---------------+
This document defines the following additional values within the ANCP This document defines the following additional values within the ANCP
TLV Type Registry: TLV Type Registry:
+-----------+--------------------------------+-----------+ +-----------+--------------------------------+-----------+
| Type Code | TLV Name | Reference | | Type Code | TLV Name | Reference |
+-----------+--------------------------------+-----------+ +-----------+--------------------------------+-----------+
| 0x0013 | Multicast-Service-Profile | RFC XXXX | | 0x0013 | Multicast-Service-Profile | RFC XXXX |
| | | | | | | |
| 0x0015 | Bandwidth-Allocation | RFC XXXX | | 0x0015 | Bandwidth-Allocation | RFC XXXX |
skipping to change at page 69, line 38 skipping to change at page 63, line 33
| 0x0093 | Request-Source-MAC | RFC XXXX | | 0x0093 | Request-Source-MAC | RFC XXXX |
| | | | | | | |
| 0x0094 | Report-Buffering-Time | RFC XXXX | | 0x0094 | Report-Buffering-Time | RFC XXXX |
| | | | | | | |
| 0x0095 | Committed-Bandwidth | RFC XXXX | | 0x0095 | Committed-Bandwidth | RFC XXXX |
+-----------+--------------------------------+-----------+ +-----------+--------------------------------+-----------+
This document defines the following additional values for the ANCP This document defines the following additional values for the ANCP
Capability Type registry: Capability Type registry:
+-------+-------------------------+--------+------------+-----------+ +-------+---------------------+--------+--------------+-------------+
| Value | Capability Type Name | Tech | Capability | Reference | | Value | Capability Type | Tech | Capability | Reference |
| | | Type | Data? | | | | Name | Type | Data? | |
+-------+-------------------------+--------+------------+-----------+ +-------+---------------------+--------+--------------+-------------+
| 3 | NAS-Initiated | 0 | No | RFC XXXX | | 3 | NAS-Initiated | 0 | No | RFC XXXX |
| | Replication | | | | | | Replication | | | |
| | | | | | | | | | | |
| 5 | Committed Bandwidth | 0 | No | RFC XXXX | | 5 | Committed Bandwidth | 0 | No | RFC XXXX |
| | Reporting | | | | | | Reporting | | | |
| | | | | | | | | | | |
| 6 | Conditional Access With | 0 | No | RFC XXXX | | 6 | Conditional Access | 0 | No | RFC XXXX |
| | White and Black Lists | | | | | | With White and | | | |
| | | | | | | | Black Lists | | | |
| 7 | Conditional Access With | 0 | No | RFC XXXX | | | | | | |
| | Grey Lists | | | | | 7 | Conditional Access | 0 | No | RFC XXXX |
| 8 | Bandwidth Delegation | 0 | No | RFC XXXX | | | With Grey Lists | | | |
+-------+-------------------------+--------+------------+-----------+ | | | | | |
| 8 | Bandwidth | 0 | No | RFC XXXX |
| | Delegation | | | |
+-------+---------------------+--------+--------------+-------------+
9. Acknowledgements 9. Acknowledgements
The authors would like to acknowledge Wojciech Dec for providing The authors would like to acknowledge Wojciech Dec for providing
useful input to this document, Robert Rennison for his help in useful input to this document, Robert Rennison for his help in
shaping the definition of the Multicast-Service-Profile TLV, Shridhar shaping the definition of the Multicast-Service-Profile TLV, Shridhar
Rao for his comments and suggestions and Aniruddha A for his proposal Rao for his comments and suggestions and Aniruddha A for his proposal
that formed the base of the Multicast Flow Reporting solution. that formed the base of the Multicast Flow Reporting solution.
Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided
substantial contributions on the solution for the NAS initiated substantial contributions on the solution for the NAS initiated
skipping to change at page 72, line 19 skipping to change at page 64, line 33
[IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ [IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
EUI48.html", 2010. EUI48.html", 2010.
[IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ [IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
EUI64.html", 2010. EUI64.html", 2010.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
Listener Discovery (MLD) for IPv6", RFC 2710, Listener Discovery (MLD) for IPv6", RFC 2710, October
October 1999. 1999.
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, October 2002. 3", RFC 3376, October 2002.
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
[RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T. [RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T.
Taylor, "Protocol for Access Node Control Mechanism in Taylor, "Protocol for Access Node Control Mechanism in
skipping to change at page 72, line 48 skipping to change at page 65, line 16
progress), November 2008. progress), November 2008.
[PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim- [PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim-
parameters.xhtml", 2005. parameters.xhtml", 2005.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006. Protocol Specification (Revised)", RFC 4601, August 2006.
[RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol
Independent Multicast (PIM) Join Attribute Format", Independent Multicast (PIM) Join Attribute Format", RFC
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
Control Mechanism in Broadband Multi-Service Networks", Control Mechanism in Broadband Multi-Service Networks",
RFC 5851, May 2010. RFC 5851, May 2010.
skipping to change at page 74, line 48 skipping to change at page 66, line 23
A.1. Provisioning Phase A.1. Provisioning Phase
Assume that capability negotiation has been completed between the AN Assume that capability negotiation has been completed between the AN
and NAS and that the set of negotiated capabilities includes the and NAS and that the set of negotiated capabilities includes the
following four multicast capabilities: NAS-initiated replication, following four multicast capabilities: NAS-initiated replication,
conditional access with white and black list, conditional access with conditional access with white and black list, conditional access with
grey list, and bandwidth delegation. At this point, the NAS can grey list, and bandwidth delegation. At this point, the NAS can
provision the service profiles on the AN and enable admission control provision the service profiles on the AN and enable admission control
at the AN for white-listed flows. To do this, the NAS sends the AN a at the AN for white-listed flows. To do this, the NAS sends the AN a
Provisioning message containing this information. An example message Provisioning message containing this information. An example message
providing the profile for our assumed subscriber is shown in providing the profile for our assumed subscriber is shown in Figure
Figure 20. The message has the following contents: 20. The message has the following contents:
o Message type is 93. o Message type is 93.
o The Result and Result Code fields in the header are set to zeroes, o The Result and Result Code fields in the header are set to zeroes,
as specified [RFC6320]. as specified [RFC6320].
o A Transaction identifier is assigned by the NAS. o A Transaction identifier is assigned by the NAS.
o The Multicast-Service-Profile TLV (of which typically there would o The Multicast-Service-Profile TLV (of which typically there would
be multiple instances) contains a Multicast-Service-Profile-Name be multiple instances) contains a Multicast-Service-Profile-Name
TLV (with a length of 20 octets assumed for the example) and three TLV (with a length of 20 octets assumed for the example) and three
List-Action TLVs, one each for the white, grey, and black lists List-Action TLVs, one each for the white, grey, and black lists
within the profile. The white list flows come in two sets of within the profile. The white list flows come in two sets of
group addresses: 233.252.0.0/29, coming from a server at group addresses: 233.252.0.0/29, coming from a server at
192.0.2.15, and 233.252.0.32/29, coming from a server at 192.0.2.15, and 233.252.0.32/29, coming from a server at
192.0.2.16. The grey-listed flows are in the band 192.0.2.16. The grey-listed flows are in the band 233.252.0.64/
233.252.0.64/29, coming from a server at 192.0.2.21. Finally, the 29, coming from a server at 192.0.2.21. Finally, the black list
black list flows are two individual flows that happen to overlap flows are two individual flows that happen to overlap with the
with the grey list band: 233.252.0.65, and 233.252.0.69, also with grey list band: 233.252.0.65, and 233.252.0.69, also with source
source 192.0.2.21. 192.0.2.21.
o The White-List-CAC TLV indicates that the AN does admission o The White-List-CAC TLV indicates that the AN does admission
control on white-listed flows. control on white-listed flows.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x880C) | Length = 132 | | Type (0x880C) | Length = 132 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type = 93 | 0x00 | Result Code = 0x000 | | Version | Msg Type = 93 | 0x00 | Result Code = 0x000 |
skipping to change at page 77, line 4 skipping to change at page 68, line 27
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 20: Example Provisioning Message Figure 20: Example Provisioning Message
TLV lengths in the figure are given in decimal for easier TLV lengths in the figure are given in decimal for easier
understanding. Note that the padding after the middle List-Action understanding. Note that the padding after the middle List-Action
TLV is counted as part of length of the Multicast-Service-Profile TLV is counted as part of length of the Multicast-Service-Profile
TLV, but is not included in the length of that List-Action TLV. Note TLV, but is not included in the length of that List-Action TLV. Note
also that the Length field in the message header, unlike those in the also that the Length field in the message header, unlike those in the
TLVs, includes the message header itself, as required by [RFC6320]. TLVs, includes the message header itself, as required by [RFC6320].
Finally, note that the Provisioning message does not include a Finally, note that the Provisioning message does not include a
MRepCtl-CAC TLV since in our example admission control for grey MRepCtl-CAC TLV since in our example admission control for grey
listed flows and for NAS-initiated replication is performed by the listed flows and for NAS-initiated replication is performed by the
NAS. 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
Figure 21. 21.
+----------+ +---------+ +-----+ +-----+ +----------+ +---------+ +-----+ +-----+
|Subscriber| | Home | | AN | | NAS | |Subscriber| | Home | | AN | | NAS |
+----------+ | Gateway | +-----+ +-----+ +----------+ | Gateway | +-----+ +-----+
| +---------+ | | | +---------+ | |
| | | | | | | |
| | | | | | | |
| | DSL Synch. | | | | DSL Synch. | |
| |--------------------->| | | |--------------------->| |
| | |(M1)PORT_UP(Port ID) | | | |(M1)PORT_UP(Port ID) |
| | |-------------------->| | | |-------------------->|
| | | (*) | | | (*)
| | |(M2) PORT_MNGT | | | |(M2) PORT_MNGT |
| | | (Port ID, | | | | (Port ID, |
| | |Mcast S Profile Name,| | | |Mcast S Profile Name,|
| | |Bandwidth Allocation)| | | |Bandwidth Allocation)|
| | |<--------------------| | | |<--------------------|
(*) The NAS may optionally seek direction from an external (*) The NAS may optionally seek direction from an external
Autorization/Policy Server Autorization/Policy Server
Figure 21: Configuring an AN Port With Multicast Service Profile ID Figure 21: Configuring an AN Port With Multicast Service Profile ID
and Delegated Bandwidth Amount and Delegated Bandwidth Amount
The Port Management message will typically contain other TLVs but our The Port Management message will typically contain other TLVs but our
example (Figure 22) just shows the Target, Multicast-Service-Profile- example (Figure 22) 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
skipping to change at page 81, line 8 skipping to change at page 72, line 4
(*) The NAS may optionally seek direction from an external (*) The NAS may optionally seek direction from an external
Authorization/Policy Server Authorization/Policy Server
Figure 23: Successful Join/Leave Operations, Grey-Listed Flow Figure 23: Successful Join/Leave Operations, Grey-Listed Flow
The Multicast Admission Control message M1 contains: The Multicast Admission Control message M1 contains:
o an ANCP Header with: o an ANCP Header with:
* Message-Type = 145 - Multicast Admission Control; * Message-Type = 145 - Multicast Admission Control;
* Result= 0x0 (Ignore); * Result= 0x0 (Ignore);
* Transaction-ID = Transaction-ID maintained by AN; * Transaction-ID = Transaction-ID maintained by AN;
o a Target TLV identifying the AN Port o a Target TLV identifying the AN Port
o a Command TLV containing: o a Command TLV containing:
* Command Code = Add (1); * Command Code = Add (1);
* Accounting = 0; * Accounting = 0;
* a Multicast-Flow embedded TLV indicating the SSM multicast flow * a Multicast-Flow embedded TLV indicating the SSM multicast flow
(Flow Type = 0x02) for which the AN received the IGMP Join: (Flow Type = 0x02) for which the AN received the IGMP Join:
IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source
Address = 192.0.2.21; Address = 192.0.2.21;
* a Request-Source-IP embedded TLV containing the IGMP join * a Request-Source-IP embedded TLV containing the IGMP join
source IP (192.0.2.100). source IP (192.0.2.100).
The Multicast Admission Control message M1 is illustrated in The Multicast Admission Control message M1 is illustrated in Figure
Figure 24: 24:
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x880C) | Length = 98 | | Type (0x880C) | Length = 98 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=145 | 0x0 | Result Code = 0x000 | | Version | Msg Type=145 | 0x0 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 83, line 19 skipping to change at page 73, line 39
* Command Code = Add (1); * Command Code = Add (1);
* Accounting = 1 (begin flow accounting), since in our example * Accounting = 1 (begin flow accounting), since in our example
the operator wants accounting on this flow. the operator wants accounting on this flow.
* a Multicast-Flow embedded TLV indicating the SSM multicast flow * a Multicast-Flow embedded TLV indicating the SSM multicast flow
(Flow Type = 0x02) that the NAS is admitting for this access (Flow Type = 0x02) that the NAS is admitting for this access
port: IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) port: IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01)
Source Address = 192.0.2.21. Source Address = 192.0.2.21.
The Multicast Admission Control message M2 is illustrated in The Multicast Admission Control message M2 is illustrated in Figure
Figure 25. 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 = 48 | | Type (0x880C) | Length = 48 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=144 | 0x1 | Result Code = 0x000 | | Version | Msg Type=144 | 0x1 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 84, line 32 skipping to change at page 75, line 5
* Accounting = 0; * Accounting = 0;
* a Multicast-Flow embedded TLV indicating the SSM multicast flow * a Multicast-Flow embedded TLV indicating the SSM multicast flow
(Flow Type = 0x02) for which the AN received the IGMP leave: (Flow Type = 0x02) for which the AN received the IGMP leave:
IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source
Address = 192.0.2.21. Address = 192.0.2.21.
* a Request-Source-IP embedded TLV containing the IGMP leave * a Request-Source-IP embedded TLV containing the IGMP leave
request source, IPv4 (0x01) address 192.0.2.100. request source, IPv4 (0x01) address 192.0.2.100.
The Multicast Admission Control message M3 is illustrated in The Multicast Admission Control message M3 is illustrated in Figure
Figure 26. 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 | | Type (0x880C) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=145 | 0x0 | Result Code = 0x000 | | Version | Msg Type=145 | 0x0 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 86, line 14 skipping to change at page 76, line 17
delegated bandwidth (2000 kbits/s). A request is received to join a delegated bandwidth (2000 kbits/s). A request is received to join a
new flow in the white list range. The AN chooses to send a Bandwidth new flow in the white list range. The AN chooses to send a Bandwidth
Reallocation Request message to the NAS, requesting that the Reallocation Request message to the NAS, requesting that the
delegated bandwidth allocation be increased to 4000 kbits/s at a delegated bandwidth allocation be increased to 4000 kbits/s at a
minimum, and preferably to 6000 kbits/s. minimum, and preferably to 6000 kbits/s.
In our example, the NAS is managing bandwidth tightly, as witnessed In our example, the NAS is managing bandwidth tightly, as witnessed
by its minimal initial allocation of just enough for one flow. It is by its minimal initial allocation of just enough for one flow. It is
willing to provide the minimum additional amount only, and therefore willing to provide the minimum additional amount only, and therefore
returns a Bandwidth Transfer message where the delegated bandwidth returns a Bandwidth Transfer message where the delegated bandwidth
value is given as 4000 kbits/s. With this amount, the AN is able to value is given as 4000 kbits/s. With this amount, the AN is able to
admit the second white-listed flow. The AN could send a similar admit the second white-listed flow. The AN could send a similar
Bandwidth Transfer message back to the NAS bringing the delegated Bandwidth Transfer message back to the NAS bringing the delegated
bandwidth amount back down to 2000 kbits/s when one of the flows is bandwidth amount back down to 2000 kbits/s when one of the flows is
terminated, but this shows nothing new and is omitted. terminated, but this shows nothing new and is omitted.
As one more point of illustration, suppose that the NAS chooses to As one more point of illustration, suppose that the NAS chooses to
audit the current amount of delegated bandwidth to ensure it is audit the current amount of delegated bandwidth to ensure it is
synchronized with the AN. It sends a Delegated Bandwidth Query synchronized with the AN. It sends a Delegated Bandwidth Query
request message to the AN, and receives a Delegated Bandwidth Query request message to the AN, and receives a Delegated Bandwidth Query
response message with the current allocation as the AN sees it. response message with the current allocation as the AN sees it.
skipping to change at page 87, line 45 skipping to change at page 77, line 22
| | |Delegated Bandwidth| | | |Delegated Bandwidth|
| | | Query response | | | | Query response |
| | |------------------>|(M4) | | |------------------>|(M4)
| | | | | | | |
(*) The NAS may optionally seek direction from an external (*) The NAS may optionally seek direction from an external
Authorization/Policy Server Authorization/Policy Server
Figure 27: Successful Join/Leave Operations, White-Listed Flow Figure 27: Successful Join/Leave Operations, White-Listed Flow
The Bandwidth Reallocation Request message (M1) is shown in The Bandwidth Reallocation Request message (M1) is shown in Figure
Figure 28. The contents require little explanation. The Message 28. The contents require little explanation. The Message Type for
Type for the Bandwidth Reallocation Request is 146. The Result field the Bandwidth Reallocation Request is 146. The Result field is set
is set to 0x0 (Ignore). Besides the Target, the message has one to 0x0 (Ignore). Besides the Target, the message has one other TLV,
other TLV, the Bandwidth-Request, with a TLV Type of 0x16. The TLV the Bandwidth-Request, with a TLV Type of 0x16. The TLV contains
contains Required Amount and Preferred Amount fields, set to 4000 and Required Amount and Preferred Amount fields, set to 4000 and 6000
6000 kbits/s respectively. kbits/s respectively.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x880C) | Length = 36 | | Type (0x880C) | Length = 36 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=146 | 0x0 | Result Code = 0x000 | | Version | Msg Type=146 | 0x0 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 89, line 29 skipping to change at page 78, line 39
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Loop Circuit ID | | Access Loop Circuit ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|BW-Allocation TLV Type = 0x15 | TLV Length = 4 | |BW-Allocation TLV Type = 0x15 | TLV Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delegated Amount = 0x00000FA0 (4000 kbits/s) | | Delegated Amount = 0x00000FA0 (4000 kbits/s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 29: NAS Response, Bandwidth Transfer Message Figure 29: NAS Response, Bandwidth Transfer Message
The Delegated Bandwidth Query request message (M3) is shown in The Delegated Bandwidth Query request message (M3) is shown in Figure
Figure 30. The Message Type for the Delegated Bandwidth Query 30. The Message Type for the Delegated Bandwidth Query request
request message is 148. The Result field is set to AckAll (0x2). message is 148. The Result field is set to AckAll (0x2). The
The message contains the Target TLV only. message contains the Target TLV only.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (0x880C) | Length = 24 | | Type (0x880C) | Length = 24 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Msg Type=148 | 0x2 | Result Code = 0x000 | | Version | Msg Type=148 | 0x2 | Result Code = 0x000 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 97, line 18 skipping to change at page 85, line 25
Cisco Systems Cisco Systems
Greenside, 400 Avenue de Roumanille Greenside, 400 Avenue de Roumanille
Sophia Antipolis 06410 Sophia Antipolis 06410
France France
Phone: +33 4 97 23 26 19 Phone: +33 4 97 23 26 19
Email: flefauch@cisco.com Email: flefauch@cisco.com
Roberta Maglione Roberta Maglione
Cisco Systems Cisco Systems
Via Reiss Romoli 274 181 Bay Street
Torino 10148 Toronto, ON M5J 2T3
Italy Canada
Phone:
Email: robmgl@cisco.com Email: robmgl@cisco.com
Tom Taylor Tom Taylor
Huawei Technologies Huawei Technologies
Ottawa Ottawa
Canada Canada
Email: tom.taylor.stds@gmail.com Email: tom.taylor.stds@gmail.com
 End of changes. 54 change blocks. 
372 lines changed or deleted 370 lines changed or added

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