idnits 2.17.1 draft-ietf-mboned-glop-update-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 BCP 53 4 RFC 3180 6 Title: GLOP Addressing in 233/8 7 Author(s): D. Meyer, P. Lothberg 8 Status: Best Current Practice 9 Date: September 2001 10 Mailbox: dmm@sprint.net, roll@sprint.net 11 Pages: 5 12 Characters: 8225 13 Obsoletes: 2770 15 I-D Tag: draft-ietf-mboned-glop-update-01.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3180.txt 19 This document defines the policy for the use of 233/8 for statically 20 assigned multicast addresses. 22 This document is a product of the MBONE Deployment Working Group of the 23 IETF. 25 This document specifies an Internet Best Current Practices for the 26 Internet Community, and requests discussion and suggestions for 27 improvements. Distribution of this memo is unlimited. 29 This announcement is sent to the IETF list and the RFC-DIST list. 30 Requests to be added to or deleted from the IETF distribution list 31 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 32 added to or deleted from the RFC-DIST distribution list should 33 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 35 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 36 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 37 help: ways_to_get_rfcs. For example: 39 To: rfc-info@RFC-EDITOR.ORG 40 Subject: getting rfcs 42 help: ways_to_get_rfcs 44 Requests for special distribution should be addressed to either the 45 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 46 specifically noted otherwise on the RFC itself, all RFCs are for 47 unlimited distribution.echo 48 Submissions for Requests for Comments should be sent to 49 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 50 Authors, for further information.