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: 2006-12-06

Additional information is available at tools.ietf.org/wg/mboned

Chair(s):

  • Marshall Eubanks <tme@multicasttech.com>

  • Hiroshi Ohta <ohta.hiroshi@lab.ntt.co.jp>

    Operations and Management Area Director(s):

  • Dan Romascanu <dromasca@avaya.com>
  • Ronald Bonica <rbonica@juniper.net>

    Operations and Management Area Advisor:

  • TBD <noreply@ietf.org>

    Technical Advisor(s):

  • Scott Bradner <sob@harvard.edu>

    Mailing Lists:

    General Discussion: mboned@ietf.org
    To 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 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 (10743 bytes)
    Overview of the Internet Multicast Addressing Architecture (37430 bytes)
    Requirements for Multicast AAA coordinated between Content Provider(s) and Network Service Provider(s) (49337 bytes)
    Overview of the Internet Multicast Routing Architecture (56346 bytes)
    IP Multicast MIB (122690 bytes)
    AAA Framework for Multicasting (38372 bytes)
    Lightweight IGMPv3 and MLDv2 Protocols (39780 bytes)
    Moving MCAST.NET into the ARPA infrastructure top level domain (13786 bytes)
    ssmping Protocol (23447 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)
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.