BCP 53, RFC 3180 on GLOP Addressing in 233/8
RFC Editor <rfc-ed@ISI.EDU> Sat, 20 October 2001 04:06 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19041; Sat, 20 Oct 2001 00:06:44 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id XAA12015 for ietf-123-outbound.10@ietf.org; Fri, 19 Oct 2001 23:55:02 -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 SAA07734 for <all-ietf@loki.ietf.org>; Fri, 19 Oct 2001 18:47:51 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04013 for <all-ietf@ietf.org>; Fri, 19 Oct 2001 18:47:46 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id f9JMljH04911; Fri, 19 Oct 2001 15:47:45 -0700 (PDT)
Message-Id: <200110192247.f9JMljH04911@gamma.isi.edu>
To: IETF-Announce:;
Subject: BCP 53, RFC 3180 on GLOP Addressing in 233/8
Cc: rfc-ed@ISI.EDU, mboned@network-services.uoregon.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 19 Oct 2001 15:47:45 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
BCP 53
RFC 3180
Title: GLOP Addressing in 233/8
Author(s): D. Meyer, P. Lothberg
Status: Best Current Practice
Date: September 2001
Mailbox: dmm@sprint.net, roll@sprint.net
Pages: 5
Characters: 8225
Obsoletes: 2770
I-D Tag: draft-ietf-mboned-glop-update-01.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3180.txt
This document defines the policy for the use of 233/8 for statically
assigned multicast addresses.
This document is a product of the MBONE Deployment Working Group of
the
IETF.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
- BCP 53, RFC 3180 on GLOP Addressing in 233/8 RFC Editor