MBONED Working Group Percy S. Tarapore
Internet Draft Robert Sayko
Intended status: BCP AT&T
Expires: August 25, 2013 Ram Krishnan
Brocade
February 25, 2013
Multicasting Applications Across Inter-Domain Peering Points
draft-tarapore-mboned-multicast-cdni-02.txt
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on August 25, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Tarapore, et al Expires August 25, 2013 [Page 1]
IETF I-D Multicasting Applications Across Peering Points February 2013
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Abstract
This document examines the process of transporting applications via
multicast across inter-domain peering points. The objective is to
describe the setup process for multicast-based delivery across
administrative domains and document supporting functionality to
enable this process.
Table of Contents
1. Introduction...................................................2
2. Overview of Inter-domain Multicast Application Transport.......3
3. Inter-domain Peering Point Requirements for Multicast..........4
3.1. Native Multicast..........................................4
3.2. Peering Point Enabled with GRE Tunnel.....................4
3.3. Peering Point Enabled with an AMT.........................4
4. Supporting Functionality.......................................5
4.1. Network Transport and Security Guidelines.................5
4.2. Routing Aspects and Related Guidelines....................5
4.3. Back Office Functions - Billing and Logging Guidelines....5
4.4. Operations - Service Performance and Monitoring Guidelines5
4.5. Reliability Models/Service Assurance Guidelines...........5
4.6. Provisioning Guidelines...................................5
4.7. Client Models.............................................6
4.8. Addressing Guidelines.....................................6
5. Security Considerations........................................6
6. IANA Considerations............................................6
7. Conclusions....................................................6
8. References.....................................................6
8.1. Normative References......................................6
8.2. Informative References....................................7
9. Acknowledgments................................................7
1. Introduction
Several types of applications (e.g., live video streaming) are well
suited for delivery via multicast means. The use of multicast for
delivering such applications offers significant savings for
utilization of resources in any given administrative domain. End
user demand for such applications is growing. Often, this requires
transporting such applications across administrative domains via
inter-domain peering points.
Tarapore, et al Expires August 25, 2013 [Page 2]
IETF I-D Multicasting Applications Across Peering Points February 2013
The objective of this Best Current Practices document is twofold:
o Describe the process and establish guidelines for setting up
multicast-based delivery of applications across inter-domain
peering points, and
o Catalog all required information exchange between the
administrative domains to support multicast-based delivery.
While there are several multicast protocols available for use, this
BCP will limit the discussion to the peering requirements of a
select set of the newer and more popular protocols including:
o Protocol Independent Multicast - Source Specific Multicast
(PIM-SSM) [RFC4607]
o Internet Group Management Protocol (IGMP) v3 [RFC4604]
o Multicast Listener Discovery (MLD) [RFC4604]
This document therefore serves the purpose of a "Gap Analysis"
exercise for this process. The rectification of any gaps identified
- whether they involve protocol extension development or otherwise -
is beyond the scope of this document and is for further study.
2. Overview of Inter-domain Multicast Application Transport
A multicast-based application delivery scenario is as follows:
o Two independent administrative domains are interconnected via a
peering point.
o The peering point is either multicast enabled (end-to-end
native multicast across the two domains) or it is connected by
one of two possible tunnel types:
o A Generic Routing Encapsulation (GRE) Tunnel [RFC2784]
allowing multicast tunneling across the peering point, or
o An Automatic Multicast Tunnel (AMT) [IETF-ID-AMT].
o The application originates at a source in Domain A
o An End User associated with Domain B requests the application
o The request is communicated to the application source which
commences the delivery via multicast
Tarapore, et al Expires August 25, 2013 [Page 3]
IETF I-D Multicasting Applications Across Peering Points February 2013
o Application is distributed via Multicast from the source in
Domain A through the Peering Point interface and then to the
End User through Domain B.
The setup of the delivery process along with associated requirements
is described in section 3. A comprehensive list of required
information that needs to be exchanged between the two domains to
support various functions enabling the application transport is
provided in section 4.
3. Inter-domain Peering Point Requirements for Multicast
The transport of applications using multicast requires that the
inter-domain peering point is enabled to support such a process.
There are three possible Use Cases for consideration.
3.1. Native Multicast
This Use Case involves end-to-end Native Multicast between the two
administrative domains and the peering point is also native
multicast enabled.
Interface requirements for this Use Case need to be described here.
3.2. Peering Point Enabled with GRE Tunnel
The peering point is not native multicast enabled in this Use Case.
There is a Generic Routing Encapsulation Tunnel provisioned over the
peering point.
Interface requirements for this Use Case need to be described here.
3.3. Peering Point Enabled with an AMT
The peering point in this Use Case is provisioned with an Automatic
Multicast Tunnel.
Interface requirements for this Use Case need to be described here.
Tarapore, et al Expires August 25, 2013 [Page 4]
IETF I-D Multicasting Applications Across Peering Points February 2013
4. Supporting Functionality
Supporting functions and related interfaces over the peering point
that enable the multicast transport of the application are listed in
this section. Critical information parameters that need to be
exchanged in support of these functions are enumerated along with
guidelines as appropriate. Specific interface functions for
consideration are as follows.
4.1. Network Transport and Security Guidelines
4.2. Routing Aspects and Related Guidelines
4.3. Back Office Functions - Billing and Logging Guidelines
4.4. Operations - Service Performance and Monitoring Guidelines
4.5. Reliability Models/Service Assurance Guidelines
4.6. Provisioning Guidelines
Tarapore, et al Expires August 25, 2013 [Page 5]
IETF I-D Multicasting Applications Across Peering Points February 2013
4.7. Client Models
4.8. Addressing Guidelines
5. Security Considerations
(Include discussion on DRM, AAA, Network Security)
6. IANA Considerations
7. Conclusions
8. References
8.1. Normative References
[RFC2784] D. Farinacci, T. Li, S. Hanks, D. Meyer, P. Traina,
"Generic Routing Encapsulation (GRE)", RFC 2784, March 2000
[IETF-ID-AMT] G. Bumgardner, "Automatic Multicast Tunneling", draft-
ietf-mboned-auto-multicast-13, April 2012, Work in progress
[RFC4604] H. Holbrook, et al, "Using Internet Group Management
Protocol Version 3 (IGMPv3) and Multicast Listener Discovery
Protocol Version 2 (MLDv2) for Source Specific Multicast", RFC 4604,
August 2006
Tarapore, et al Expires August 25, 2013 [Page 6]
IETF I-D Multicasting Applications Across Peering Points February 2013
[RFC4607] H. Holbrook, et al, "Source Specific Multicast", RFC 4607,
August 2006
8.2. Informative References
9. Acknowledgments
Tarapore, et al Expires August 25, 2013 [Page 7]
IETF I-D Multicasting Applications Across Peering Points February 2013
Authors' Addresses
Percy S. Tarapore
AT&T
Phone: 1-732-420-4172
Email: tarapore@att.com
Robert Sayko
AT&T
Phone: 1-732-420-3292
Email: rs1983@att.com
Ram Krishnan
Brocade
Phone:
Email: ramk@brocade.com
Tarapore, et al Expires August 25, 2013 [Page 8]