idnits 2.17.1 draft-ietf-malloc-ipv6-guide-04.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 RFC 3307 5 Title: Allocation Guidelines for IPv6 Multicast Addresses 7 Author(s): B. Haberman 8 Status: Standards Track 9 Date: August 2002 10 Mailbox: bkhabs@nc.rr.com 11 Pages: 8 12 Characters: 15742 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-malloc-ipv6-guide-04.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3307.txt 19 This document specifies guidelines that must be implemented by any 20 entity responsible for allocating IPv6 multicast addresses. This 21 includes, but is not limited to, any documents or entities wishing 22 to assign permanent IPv6 multicast addresses, allocate dynamic IPv6 23 multicast addresses, and define permanent IPv6 multicast group 24 identifiers. The purpose of these guidelines is to reduce the 25 probability of IPv6 multicast address collision, not only at the 26 IPv6 layer, but also at the link-layer of media that encode portions 27 of the IP layer address into the MAC layer address. 29 This document is a product of the Multicast-Address Allocation Working 30 Group of the IETF. 32 This is now a Proposed Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.