Protocol Action: GLOP Addressing in 233/8 to BCP

The IESG <iesg-secretary@ietf.org> Wed, 12 September 2001 15:49 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25535; Wed, 12 Sep 2001 11:49:59 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA06193 for ietf-123-outbound.10@ietf.org; Wed, 12 Sep 2001 11:45:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id LAA06168 for <all-ietf@loki.ietf.org>; Wed, 12 Sep 2001 11:39:31 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25117; Wed, 12 Sep 2001 11:39:02 -0400 (EDT)
Message-Id: <200109121539.LAA25117@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: mboned@network-services.uoregon.edu
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: GLOP Addressing in 233/8 to BCP
Date: Wed, 12 Sep 2001 11:39:02 -0400
Sender: scoya@cnri.reston.va.us


The IESG has approved the Internet-Draft 'GLOP Addressing in 233/8'
<draft-ietf-mboned-glop-update-01.txt> as a BCP.  This document is the
product of the MBONE Deployment Working Group.
The IESG contact persons are Bert Wijnen and Randy Bush.
 
 
Technical Summary
 
   This document formalizes the policy for use of 233/8 as a statically
   assigned subset of the class D multicast address space.  This space is
   used for many to many applications such as non-broadcast applications.
   This allocation is in addition to those described by RFC 2365.  The IANA
   has allocated 223/8 per RFC 2770. This document obsoletes RFC 2770 to make
   it textually suitable to become a BCP.

Working Group Summary

 Discussion within the mboned WG reached consensus on this document.

Protocol Quality

 This document was reviewed for the IESG by Randy Bush


Note to RFC Editor

There is text in the Internet-Draft that states this document updates RFC 2770.
This document actually obsoletes RFC 2770