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: 2010-03-30

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.org
To Subscribe: https://www.ietf.org/mailman/listinfo/mboned
Archive: http://www.ietf.org/mail-archive/web/mboned

Description of Working Group:

The MBONE Deployment Working Group is a forum for coordinating
the 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:

Unicast-Prefix-based IPv4 Multicast Addresses (11173 bytes)
Requirements for Multicast AAA coordinated between Content Provider(s) and Network Service Provider(s) (39088 bytes)
AAA and Admission Control Framework for Multicasting (48576 bytes)
Moving MCAST.NET into the ARPA infrastructure top level domain (15001 bytes)
Mtrace Version 2: Traceroute Facility for IP Multicast (74054 bytes)
Requirements for IP Multicast Session Announcement (21794 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) obsoleted by RFC 5771
IANA Guidelines for IPv4 Multicast Address Assignments (RFC 3171) (15389 bytes) obsoleted by RFC 5771
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)
Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) Protocols (RFC 5790) (39394 bytes)
IANA Guidelines for IPv4 Multicast Address Assignments (RFC 5771) (22239 bytes) obsoletes RFC 3138,RFC 3171/ updates RFC 2780

Internet SocietyAMSHome - Tools - Datatracker - IASA - IAB - RFC Editor - IANA - IRTF - IETF Trust - ISOC - Contact Us
Secretariat services provided by Association Management Solutions, LLC (AMS).
Please send problem reports to: ietf-action@ietf.org.