Current Meeting Report
Slides
Jabber Logs


2.4.8 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:

       http://antc.uoregon.edu/MBONED/ -- Additional MBONED Page
NOTE: This charter is a snapshot of the 55th IETF Meeting in Altanta, Georgia USA. It may now be out-of-date.

Last Modifield: 05/06/2002

Chair(s):
David Meyer <dmm@maoz.com>
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 interconnects.

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
Internet-Drafts:
  • - draft-ietf-mboned-anycast-rp-08.txt
  • - draft-ietf-mboned-ssm232-02.txt
  • - draft-ietf-mboned-auto-multicast-01.txt
  • - draft-ietf-mboned-msdp-deploy-00.txt
  • - draft-ietf-mboned-ipv4-mcast-bcp-00.txt
  • - draft-ietf-mboned-rfc3171-update-00.txt
  • - draft-ietf-mboned-ipv4-uni-based-mcast-00.txt
  • - draft-ietf-mboned-iesg-gap-analysis-00.txt
  • Request For Comments:
    RFCStatusTitle
    RFC2365BCPAdministratively Scoped IP Multicast
    RFC2588 I IP Multicast and Firewalls
    RFC2776 PS Multicast-Scope Zone Announcement Protocol (MZAP)
    RFC2770 E GLOP Addressing in 233/8
    RFC3138 I Extended Allocations in 233/8
    RFC3171BCPIANA Guidelines for IPv4 Multicast Address Assignments
    RFC3170 I IP Multicast Applications: Challenges and Solutions
    RFC3180BCPGLOP Addressing in 233/8

    Current Meeting Report

    None received.

    Slides

    Internet Multicast Gap Analysis