draft-ietf-ancp-mc-extensions-11.txt   draft-ietf-ancp-mc-extensions-12.txt 
ANCP F. Le Faucheur ANCP F. Le Faucheur
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track R. Maglione Updates: 6320 (if approved) R. Maglione
Expires: May 18, 2014 Cisco Systems Intended status: Standards Track Cisco Systems
T. Taylor Expires: May 23, 2014 T. Taylor
Huawei Huawei
November 14, 2013 November 19, 2013
Multicast Control Extensions for ANCP Multicast Control Extensions for ANCP
draft-ietf-ancp-mc-extensions-11.txt draft-ietf-ancp-mc-extensions-12.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.
This document updates RFC 6320 by assigning capability type 3 to a
capability specified in this document and by changing the starting
point for IANA allocation of result codes determined by IETF
Consensus from 0x100 to 0x64.
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 May 18, 2014.
This Internet-Draft will expire on May 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 2, line 43 skipping to change at page 2, line 49
3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9 3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 9 3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 9
3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . 10 3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . 10
3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10 3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10 3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10
4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11 4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 11 4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 11
4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12 4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12
4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 13 4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 13
4.2. Port Management Message . . . . . . . . . . . . . . . . . 14 4.2. Port Management Message . . . . . . . . . . . . . . . . . 14
4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 14 4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 15
4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 15 4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 15
4.3. Multicast Replication Control Message . . . . . . . . . . 15 4.3. Multicast Replication Control Message . . . . . . . . . . 16
4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 19 4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 19
4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 19 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 . . . . . . . . . . . . . . . . . 23 4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 24
4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25 4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25
4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25 4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25
4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26 4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26
4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29 4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29
4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 29 4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 30
4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30 4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30
4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31 4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31
4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31 4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31
4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 31 4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 31
4.8. Delegated Bandwidth Query Response Message . . . . . . . 32 4.8. Delegated Bandwidth Query Response Message . . . . . . . 32
4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32 4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32
4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32 4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32
4.9. Multicast Flow Query Request and Response Messages . . . 33 4.9. Multicast Flow Query Request and Response Messages . . . 33
4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 33 4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 34
4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34 4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34
4.10. Committed Bandwidth Report Message . . . . . . . . . . . 35 4.10. Committed Bandwidth Report Message . . . . . . . . . . . 36
4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 36 4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 36
4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36 4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36
5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 36 5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 37
5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 36 5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 37
5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . 37 5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . 38
5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 38 5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 39
5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 40 5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 41
5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . 41 5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . 42
5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . 42 5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . 42
5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 42 5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 43
5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43 5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43
5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 43 5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 44
5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . 44 5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . 44
5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45 5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45
5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46 5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46
5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 46 5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 47
6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47 6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47
6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48 6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48
6.1.1. Protocol Requirements For NAS-Initiated Replication . 48 6.1.1. Protocol Requirements For NAS-Initiated Replication . 48
6.1.2. Protocol Requirements For Committed Multicast 6.1.2. Protocol Requirements For Committed Multicast
Bandwidth Reporting . . . . . . . . . . . . . . . . . 49 Bandwidth Reporting . . . . . . . . . . . . . . . . . 49
6.1.3. Protocol Requirements For Conditional Access With 6.1.3. Protocol Requirements For Conditional Access With
White and Black Lists . . . . . . . . . . . . . . . . 49 White and Black Lists . . . . . . . . . . . . . . . . 50
6.1.4. Protocol Requirements For Conditional Access With 6.1.4. Protocol Requirements For Conditional Access With
Grey Lists . . . . . . . . . . . . . . . . . . . . . 50 Grey Lists . . . . . . . . . . . . . . . . . . . . . 50
6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 51 6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 52
6.2. Capability-Specific Procedures for Providing Multicast 6.2. Capability-Specific Procedures for Providing Multicast
Service . . . . . . . . . . . . . . . . . . . . . . . . . 52 Service . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.2.1. Procedures For NAS-Initiated Replication . . . . . . 52 6.2.1. Procedures For NAS-Initiated Replication . . . . . . 52
6.2.2. Procedures For Committed Bandwidth Reporting . . . . 53 6.2.2. Procedures For Committed Bandwidth Reporting . . . . 53
6.2.3. Procedures For Conditional Access With Black and 6.2.3. Procedures For Conditional Access With Black and
White Lists . . . . . . . . . . . . . . . . . . . . . 54 White Lists . . . . . . . . . . . . . . . . . . . . . 54
6.2.4. Procedures For Conditional Access With Grey Lists . . 55 6.2.4. Procedures For Conditional Access With Grey Lists . . 56
6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 57 6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 57
6.3. Combinations of Multicast Capabilities . . . . . . . . . 58 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 . 58 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 . . . . . . . . . . . . . . . . . . . . . . 59 Bandwidth . . . . . . . . . . . . . . . . . . . . . . 60
6.3.3. Combination of NAS-Initiated Replication with Other 6.3.3. Combination of NAS-Initiated Replication with Other
Capabilities . . . . . . . . . . . . . . . . . . . . 59 Capabilities . . . . . . . . . . . . . . . . . . . . 60
6.3.4. Combinations of Committed Bandwidth Reporting with 6.3.4. Combinations of Committed Bandwidth Reporting with
Other Multicast Capabilities . . . . . . . . . . . . 60 Other Multicast Capabilities . . . . . . . . . . . . 61
7. Security Considerations . . . . . . . . . . . . . . . . . . . 60 7. Security Considerations . . . . . . . . . . . . . . . . . . . 61
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 63 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 64
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 63 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 64
10.1. Normative References . . . . . . . . . . . . . . . . . . 63 10.1. Normative References . . . . . . . . . . . . . . . . . . 64
10.2. Informative References . . . . . . . . . . . . . . . . . 64 10.2. Informative References . . . . . . . . . . . . . . . . . 64
Appendix A. Example of Messages and Message Flows . . . . . . . 64 Appendix A. Example of Messages and Message Flows . . . . . . . 65
A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 65 A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 65
A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 70 A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 70
A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 75 A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 75
A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 79 A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 79
A.5. Handling Of Requests To Join and Leave the On-Line Game . 79 A.5. Handling Of Requests To Join and Leave the On-Line Game . 79
A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 81 A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 81
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 84
1. Introduction 1. Introduction
skipping to change at page 6, line 16 skipping to change at page 6, line 28
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 multicast accounting and reporting services described in
Section 3.4.3 of [RFC5851]. Because of this common content and Section 3.4.3 of [RFC5851]. Because of this common content and
because of other protocol overlaps between the different because of other protocol overlaps between the different
capabilities, the protocol descriptions for the multicast extensions capabilities, the protocol descriptions for the multicast extensions
specified in this document are merged into a single non-redundant specified in this document are merged into a single non-redundant
narrative. Tables in Section 6 then indicate the specific sub- narrative. Tables in Section 6 then indicate the specific sub-
sections of the protocol description that have to be implemented to sections of the protocol description that have to be implemented to
support each capability. support each capability.
This document updates RFC 6320 by assigning capability type 3 to the
NAS-initiated multicast replication capability and by changing the
starting point for IANA allocation of result codes determined by IETF
Consensus from 0x100 to 0x64.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
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 61, line 16 skipping to change at page 61, line 49
| 147 | Bandwidth Transfer | RFC XXXX | | 147 | Bandwidth Transfer | RFC XXXX |
| | | | | | | |
| 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. In support of these assignments, IANA is
requested to change the lower limit of 0x100 specified by [RFC6320]
for assignments by IETF Consensus to 0x64.
+--------------+------------------------------------+---------------+ +--------------+------------------------------------+---------------+
| Result Code | One-Line Description | Reference | | Result Code | One-Line Description | Reference |
+--------------+------------------------------------+---------------+ +--------------+------------------------------------+---------------+
| 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 |
| | | | | | | |
 End of changes. 26 change blocks. 
35 lines changed or deleted 49 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/