MBONE Deployment (mboned) Internet Drafts
| Automatic IP Multicast Without Explicit Tunnels (AMT) | |||||||||||||||||
|
Automatic Multicast Tunneling (AMT) allows multicast communication amongst isolated multicast-enabled sites or hosts, attached to a network which has no native multicast support. It also enables them to exchange multicast traffic with the native multicast infrastructure and does not require any manual configuration. AMT uses an encapsulation interface so that no changes to a host stack or applications are required, all protocols (not just UDP) are handled, and there is no additional overhead in core routers. | ||||||||||||||||
| Unicast-Prefix-based IPv4 Multicast Addresses | |||||||||||||||||
|
This specification defines an extension to the multicast addressing architecture of the IP Version 4 protocol. The extension presented in this document allows for unicast-prefix-based assignment of multicast addresses. By delegating multicast addresses at the same time as unicast prefixes, network operators will be able to identify their multicast addresses without needing to run an inter-domain allocation protocol. | ||||||||||||||||
| IANA Guidelines for IPv4 Multicast Address Assignments | |||||||||||||||||
|
This document obsoletes RFC 3171. It provides guidance for the Internet Assigned Numbers Authority (IANA) in assigning IPv4 multicast addresses. | ||||||||||||||||
| Overview of the Internet Multicast Addressing Architecture | |||||||||||||||||
|
The lack of up-to-date documentation on IP multicast address allocation and assignment procedures has caused a great deal of confusion. To clarify the situation, this memo describes the allocation and assignment techniques and mechanisms currently (as of this writing) in use. | ||||||||||||||||
| Requirements for Multicast AAA coordinated between Content Provider(s) and Network Service Provider(s) | |||||||||||||||||
|
This memo presents requirements in the area of accounting and access control for IP multicasting. The scope of the requirements is limited to cases that Authentication, Accounting and Authorization (AAA) functions are coordinated between Content Provider(s) and Network Service Provider(s). General requirements for accounting and admission control capabilities including quality-of-service (QoS) related issues are listed. This memo assumes that these capabilities can be realized by functions implemented at edges of a network based on IGMP or MLD. Finally, cases for Content Delivery Services (CDS) are described as application examples which could benefit from multicasting accounting and access control capabilities as described in this memo. This memo defines requirements related to AAA issues for multi- entity provider models in which the network service provider and content provider cooperate to provide CDS and various related AAA functions for purposes such as protecting and accounting for the access to content and network resources. The requirements are generally not relevant to cases in which there is not a reason to share AAA functions between separate entities. | ||||||||||||||||
| AAA and Admission Control Framework for Multicasting | |||||||||||||||||
|
IP multicast-based services, such as TV broadcasting or videoconferencing raise the issue of making sure that potential customers are fully entitled to access the corresponding contents. There is indeed a need for service and content providers to identify users (if not authenticate, especially within the context of enforcing electronic payment schemes) and to retrieve statistical information for accounting purposes, as far as content and network usage are concerned. This memo describes the framework for specifying the Authorization, Authentication and Accounting (AAA) capabilities that could be activated within the context of the deployment and the operation of IP multicast-based services. This framework addresses the requirements presented in "Requirements for Accounting, Authentication and Authorization in Well Managed IP Multicasting Services" [I-D.mboned-maccnt-req]. The memo provides a basic AAA enabled model as well as an extended fully enabled model with resource and admission control coordination. | ||||||||||||||||
| Lightweight IGMPv3 and MLDv2 Protocols | |||||||||||||||||
|
This document describes lightweight IGMPv3 and MLDv2 protocols (LW- IGMPv3 and LW-MLDv2), which simplify the standard (full) versions of IGMPv3 and MLDv2. The interoperability with the full versions and the previous versions of IGMP and MLD is also taken into account. | ||||||||||||||||
| Multicast Ping Protocol | |||||||||||||||||
|
The Multicast Ping Protocol specified in this document allows for checking whether an endpoint can receive multicast, both Source- Specific Multicast (SSM) and Any-Source Multicast (ASM). It can also be used to obtain additional multicast related information like multicast tree setup time etc. This protocol is based on an implementation of tools called ssmping and asmping. | ||||||||||||||||
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
MBONE Deployment (mboned)
In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:
Additional MBONED Page
Last Modified: 2008-04-23
Additional information is available at tools.ietf.org/wg/mboned
Chair(s):
Operations and Management Area Director(s):
Operations and Management Area Advisor:
Technical Advisor(s):
Mailing Lists:
General Discussion: mboned@ietf.orgTo Subscribe: https://www1.ietf.org/mailman/listinfo/mboned
Archive: http://www1.ietf.org/mail-archive/web/mboned/current/index.html
Description of Working Group:
The MBONE Deployment Working Group is a forum for coordinatingthe deployment, engineering, and operation of multicast routing
protocols and procedures in the global Internet. This activity will
include, but not be limited to:
- Documenting deployment of multicast routing in the global Internet.
- Receive regular reports on the current state of the deployment of
multicast technology. Create "practice and experience" documents that
capture the experience of those who have deployed and are deploying
various multicast technologies.
- Based on reports and other information, provide feedback to other
relevant working groups.
- Develop mechanisms and procedures for sharing operational
information to aid in operation of the multicast backbones and
interconnects.
- Update RFC 3171/BCP 51 based on experience.
- Develop a roadmap informational RFC that describes the current
IPv4 and IPv6 IETF multicast architectures, including
references to the relevant IETF documents and guidance for
implementers and network operators.
- Complete the MSDP MIB
This is not meant to be a protocol development Working Group.
Goals and Milestones:
| Done | Submit I-D on inter-provider coordination of the deployment of pruning mrouteds. | |
| Done | Establish initial charter, goals, and long-term group agenda. | |
| Done | Submit I-D outlining requirements for the existing MBONE infrastructure. | |
| Done | Submit I-D specifying the use of administratively scoped multicast addresses (RFC 2365) | |
| Done | Submit I-D specifying the use of native multicast where appropriate (e.g. exchange points). | |
| Done | Submit I-D on IP Multicast and Firewalls (RFC 2588) | |
| Done | Submit I-D specifying static allocations in 233/87 (RFC 3180) | |
| Done | Submit I-D on debugging multicast problems. | |
| Done | Submit final version of scope zone announcement protocol (MZAP RFC 2776) | |
| Done | Submit final version of scoped address discovery protocol (SADP) | |
| Done | Submit I-D describing ISP multicast deployment practices | |
| Done | Submit I-D, with RPS WG, on extensions to RPSL to describe multicast routing policy | |
| Done | Submit I-D describing extended allocations in 233/8 (RFC 3138) | |
| Done | Submit I-D describing IANA Guidelines for IPv4 Multicast Address Assignments (RFC 3171) | |
| Done | Submit I-D describing IP Multicast Applications issues (RFC 3170) | |
| Done | Submit I-D describing Anycast (RP) mechanism (RFC 3446) | |
| Done | Submit I-D describing Source-Specific Protocol Independent Multicast in 232/8 | |
| Done | Submit I-D describing MSDP Deployment Scenarios | |
| Done | Submit I-D describing IPv4 Multicast Unusable Group And Source Addresses | |
| Done | Submit I-D describing Embedded RP for IPv6 Multicast Address | |
| Apr 2004 | Submit I-D on PIM-SM Multicast Routing Security Issues | |
| May 2004 | Submit I-D on IPv4/IPv6 multicast co-existence issues and strategies for IPv4 multicast and IPv6 multicast | |
| Jun 2004 | Update IANA Guidelines for IPv4 Multicast Address Assignments (RFC 3171/BCP 51) | |
| Jun 2004 | Submit PIM-SM Multicast Routing Security Issues to IESG for Informational | |
| Jun 2004 | Submit MSDP MIB to IESG for Experimental | |
| Aug 2004 | Submit IPv4 multicast address allocation procedures IESG for BCP | |
| Aug 2004 | Submit IPv4/v6 co-existence strategies to IESG for Informational | |
| Aug 2004 | Submit multicast roadmap/reference architecture document to IESG for Informational |
Internet-Drafts:
Automatic IP Multicast Without Explicit Tunnels (AMT) (70400 bytes)Unicast-Prefix-based IPv4 Multicast Addresses (13638 bytes)
IANA Guidelines for IPv4 Multicast Address Assignments (22025 bytes)
Overview of the Internet Multicast Addressing Architecture (37430 bytes)
Requirements for Multicast AAA coordinated between Content Provider(s) and Network Service Provider(s) (49734 bytes)
AAA and Admission Control Framework for Multicasting (49173 bytes)
Lightweight IGMPv3 and MLDv2 Protocols (41237 bytes)
Multicast Ping Protocol (45613 bytes)
Request For Comments:
Administratively Scoped IP Multicast (RFC 2365) (17770 bytes)IP Multicast and Firewalls (RFC 2588) (28622 bytes)
GLOP Addressing in 233/8 (RFC 2770) (8988 bytes) obsoleted by RFC 3180
Multicast-Scope Zone Announcement Protocol (MZAP) (RFC 2776) (61628 bytes)
Extended Allocations in 233/8 (RFC 3138) (6776 bytes)
IANA Guidelines for IPv4 Multicast Address Assignments (RFC 3171) (15389 bytes)
IP Multicast Applications: Challenges and Solutions (RFC 3170) (67207 bytes)
GLOP Addressing in 233/8 (RFC 3180) (8225 bytes) obsoletes RFC 2770
Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) (RFC 3446) (14792 bytes)
Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address (RFC 3956) (40136 bytes) updates RFC 3306
Multicast Source Discovery Protocol (MSDP) Deployment Scenarios (RFC 4611) (33230 bytes)
Source-Specific Protocol Independent Multicast in 232/8 (RFC 4608) (15030 bytes)
Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and Enhancements (RFC 4609) (49812 bytes)
Multicast Source Discovery Protocol (MSDP) MIB (RFC 4624) (58759 bytes)
IP Multicast MIB (RFC 5132) (120340 bytes) obsoletes RFC 2932
Overview of the Internet Multicast Routing Architecture (RFC 5110) (56217 bytes)
IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.
Return to working group directory. 
