2.4.7 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: 2003-04-21

David Meyer <dmm@1-4-5.net>
Operations and Management Area Director(s):
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Operations and Management Area Advisor:
Randy Bush <randy@psg.com>
Technical Advisor(s):
Scott Bradner <sob@harvard.edu>
Mailing Lists:
General Discussion: mboned@ns.uoregon.edu
To Subscribe: majordomo@ns.uoregon.edu
Archive: ftp://ftp.uoregon.edu/mailing-lists/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 to aid in the transition to native
  multicast, where appropriate.

- Develop mechanisms and procedures for sharing operational
  information to aid in operation of the multicast backbones and

This is not meant to be a protocol development Working Group.
Goals and Milestones:
Done  Submit Internet-Draft on inter-provider coordination of the deployment of pruning mrouteds.
Done  Establish initial charter, goals, and long-term group agenda.
Done  Submit Internet-Draft outlining requirements for the existing MBONE infrastructure.
Done  Submit Internet-Draft specifying the use of administratively scoped multicast addresses.
Done  Begin work, with RPS WG, on extensions to RPSL to describe multicast routing policy.
Dec 99  Submit Internet-Draft specifying the use of native multicast where appropriate (e.g. exchange points).
Dec 99  Begin work on document of co-existence strategies for IPv4 multicast and IPv6 multicast.
Dec 99  Submit final version of RP document
Dec 99  Submit Internet-Draft specifying static allocations in 233/8
Mar 00  Submit Internet-Draft on debugging multicast problems.
Mar 00  Submit final version of scope zone announcement protocol (MZAP)
Mar 00  Submit final version of scoped address discovery protocol (SADP)
Mar 00  Submit I-D describing ISP multicast deployment practices
  • - draft-ietf-mboned-ssm232-05.txt
  • - draft-ietf-mboned-msdp-deploy-03.txt
  • - draft-ietf-mboned-ipv4-mcast-bcp-01.txt
  • - draft-ietf-mboned-ipv4-mcast-unusable-00.txt
  • 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)
    Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) (RFC 3446) (14792 bytes)

    Current Meeting Report

    None received.


    None received.