draft-ietf-ancp-mc-extensions-15.txt   draft-ietf-ancp-mc-extensions-16.txt 
ANCP F. Le Faucheur ANCP F. Le Faucheur
Internet-Draft Cisco Internet-Draft Cisco
Updates: 6320 (if approved) R. Maglione Updates: 6320 (if approved) R. Maglione
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: August 25, 2014 T. Taylor Expires: August 29, 2014 T. Taylor
Huawei Huawei
February 21, 2014 February 25, 2014
Multicast Control Extensions for ANCP Multicast Control Extensions for ANCP
draft-ietf-ancp-mc-extensions-15.txt draft-ietf-ancp-mc-extensions-16.txt
Abstract Abstract
This document specifies the extensions to the Access Node Control This document specifies the extensions to the Access Node Control
Protocol required for support of the multicast use cases defined in Protocol required for support of the multicast use cases defined in
the Access Node Control Protocol framework document and one the Access Node Control Protocol framework document and one
additional use case described in this document. These use cases are additional use case described in this document. These use cases are
organized into the following ANCP capabilities: organized into the following ANCP capabilities:
o NAS-initiated multicast replication; o NAS-initiated multicast replication;
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 25, 2014. This Internet-Draft will expire on August 29, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 12 skipping to change at page 4, line 12
Admission Control With Grey Lists . . . . . . . . . . 55 Admission Control With Grey Lists . . . . . . . . . . 55
6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 56 6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 56
6.2. Capability-Specific Procedures for Providing Multicast 6.2. Capability-Specific Procedures for Providing Multicast
Service . . . . . . . . . . . . . . . . . . . . . . . . . 57 Service . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.2.1. Procedures For NAS-Initiated Replication . . . . . . 57 6.2.1. Procedures For NAS-Initiated Replication . . . . . . 57
6.2.2. Procedures For Committed Bandwidth Reporting . . . . 58 6.2.2. Procedures For Committed Bandwidth Reporting . . . . 58
6.2.3. Procedures For Conditional Access and Admission 6.2.3. Procedures For Conditional Access and Admission
Control With Black and White Lists . . . . . . . . . 59 Control With Black and White Lists . . . . . . . . . 59
6.2.4. Procedures For Conditional Access and Admission 6.2.4. Procedures For Conditional Access and Admission
Control With Grey Lists . . . . . . . . . . . . . . 61 Control With Grey Lists . . . . . . . . . . . . . . . 61
6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 62 6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 62
6.3. Combinations of Multicast Capabilities . . . . . . . . . 63 6.3. Combinations of Multicast Capabilities . . . . . . . . . 63
6.3.1. Combination of Conditional Access and Admission 6.3.1. Combination of Conditional Access and Admission
Control With White and Black Lists and Conditional Control With White and Black Lists and Conditional
Access and Admission Control With Grey Lists . . . . 63 Access and Admission Control With Grey Lists . . . . 63
6.3.2. Combination of Conditional Access and Admission 6.3.2. Combination of Conditional Access and Admission
Control With Delegated Bandwidth . . . . . . . . . . 65 Control With Delegated Bandwidth . . . . . . . . . . 65
6.3.3. Combination of NAS-Initiated Replication with Other 6.3.3. Combination of NAS-Initiated Replication with Other
Capabilities . . . . . . . . . . . . . . . . . . . . 65 Capabilities . . . . . . . . . . . . . . . . . . . . 65
6.3.4. Combinations of Committed Bandwidth Reporting with 6.3.4. Combinations of Committed Bandwidth Reporting with
skipping to change at page 49, line 11 skipping to change at page 49, line 11
o The Request-Source-IP TLV Type is 0x0096. o The Request-Source-IP TLV Type is 0x0096.
o TLV length is 4. o TLV length is 4.
o Local device identifier value, known to the AN and AAA. Given o Local device identifier value, known to the AN and AAA. Given
that the scope of the identifier is a single customer network, 32 that the scope of the identifier is a single customer network, 32
bits is a more than sufficient numbering space. bits is a more than sufficient numbering space.
5.12. Multicast-Flow TLV 5.12. Multicast-Flow TLV
IGMPv3 [RFC3376] and MLDv2 [RFC3801] allow multicast listeners to IGMPv3 [RFC3376] and MLDv2 [RFC3810] allow multicast listeners to
specify multiple source addresses for the same multicast group. specify multiple source addresses for the same multicast group.
Similarly the Multicast-Flow TLV specifies a multicast flow in terms Similarly the Multicast-Flow TLV specifies a multicast flow in terms
of its multicast group address and, if applicable, one or more of its multicast group address and, if applicable, one or more
unicast source addresses. The Multicast-Flow TLV is illustrated in unicast source addresses. The Multicast-Flow TLV is illustrated in
Figure 18. Figure 18.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = Multicast-Flow 0x0019 | TLV Length | | Type = Multicast-Flow 0x0019 | TLV Length |
skipping to change at page 50, line 11 skipping to change at page 50, line 11
o Multicast Group Address: a multicast group address within the o Multicast Group Address: a multicast group address within the
given address family. The group address MUST always be present. given address family. The group address MUST always be present.
o Unicast Source Address: unicast address within the given address o Unicast Source Address: unicast address within the given address
family. If the Flow Type is "ASM" (1), a source address MUST NOT family. If the Flow Type is "ASM" (1), a source address MUST NOT
be present. If the Flow Type is "SSM" (2), the number of source be present. If the Flow Type is "SSM" (2), the number of source
addresses given by the Number of Source Addresses field MUST be addresses given by the Number of Source Addresses field MUST be
present. present.
The full versions of IGMPv3 and MLDv2 support both INCLUDE and
EXCLUDE modes for specifying the desired sources for SSM flows. The
Multicast-Flow TLV supports INCLUDE mode only. [RFC5790]
(Lightweight IGMPv3 and MLDv2) provides guidance on converting
EXCLUDE mode IGMP/MLD records to INCLUDE mode for the Multicast-Flow
TLV.
5.13. Report-Buffering-Time TLV 5.13. Report-Buffering-Time TLV
The Report-Buffering-Time TLV provides the time for which a Committed The Report-Buffering-Time TLV provides the time for which a Committed
Bandwidth Report message must be held with the intention of Bandwidth Report message must be held with the intention of
accumulating multiple reports of changed committed multicast accumulating multiple reports of changed committed multicast
bandwidth in one report, to reduce the volume of messages sent to the bandwidth in one report, to reduce the volume of messages sent to the
NAS. For further information see Section 6.2.2. The TLV is NAS. For further information see Section 6.2.2. The TLV is
illustrated in Figure 19. illustrated in Figure 19.
1 2 3 1 2 3
skipping to change at page 73, line 26 skipping to change at page 73, line 26
Listener Discovery (MLD) for IPv6", RFC 2710, October Listener Discovery (MLD) for IPv6", RFC 2710, October
1999. 1999.
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, October 2002. 3", RFC 3376, October 2002.
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
[RFC5790] Liu, H., Cao, W., and H. Asaeda, "Lightweight Internet
Group Management Protocol Version 3 (IGMPv3) and Multicast
Listener Discovery Version 2 (MLDv2) Protocols", RFC 5790,
February 2010.
[RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T. [RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T.
Taylor, "Protocol for Access Node Control Mechanism in Taylor, "Protocol for Access Node Control Mechanism in
Broadband Networks", RFC 6320, October 2011. Broadband Networks", RFC 6320, October 2011.
11.2. Informative References 11.2. Informative References
[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.
[ITU-T_G.1080] [ITU-T_G.1080]
ITU-T, "ITU-T Recommendation G.1080: Quality of experience ITU-T, "ITU-T Recommendation G.1080: Quality of experience
requirements for IPTV services", December 2008. requirements for IPTV services", December 2008.
[RFC2236] Fenner, W., "Internet Group Management Protocol, Version [RFC2236] Fenner, W., "Internet Group Management Protocol, Version
2", RFC 2236, November 1997. 2", RFC 2236, November 1997.
[RFC3801] Vaudreuil, G. and G. Parsons, "Voice Profile for Internet
Mail - version 2 (VPIMv2)", RFC 3801, June 2004.
[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.
[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
 End of changes. 9 change blocks. 
9 lines changed or deleted 18 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/