idnits 2.17.1 draft-ietf-magma-mld-source-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([RFC2119], [RFC2461], [RFC2462], [RFC2710]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 2002) is 7894 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2461 (Obsoleted by RFC 4861) ** Obsolete normative reference: RFC 2462 (Obsoleted by RFC 4862) Summary: 9 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MAGMA Working Group B. Haberman 3 draft-ietf-magma-mld-source-01.txt Caspian Networks 4 Expires March 2003 September 2002 6 Source Address Selection for Multicast 7 Listener Discovery Protocol (RFC 2710) 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that other 16 groups may also distribute working documents as Internet- Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet- Drafts as reference 20 material or to cite them other than as "work in progress." 22 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt. 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 Abstract 30 It has come to light that there is an issue with the selection of a 31 suitable IPv6 source address for Multicast Listener Discovery 32 messages when a node is performing stateless address 33 autoconfiguration. This memo is intended to clarify the rules on 34 selecting an IPv6 address to use for MLD messages. 36 Introduction 38 The original specification of the Multicast Listener Discovery 39 Protocol[RFC 2710] mandated the use of a link-local IPv6 source 40 address for the transmission of MLD messages. In addition, MLD also 41 requires nodes to send MLD Report messages when joining any IPv6 42 multicast group (except the All-Nodes address and addresses of scope 43 less than 2). 45 These MLD requirements conflict with the use of IPv6 multicast within 46 the Neighbor Discovery Protocol[RFC 2461]. For stateless 47 autoconfiguration, as defined in [RFC 2462], a node is required to 48 join several IPv6 multicast groups in order to perform Duplicate 49 Address Detection prior to its use. Since the only address the node 50 has is tentative, and cannot be used for communication, it does not 51 have a suitable address to utilize as a source address. 53 This document will clarify the IPv6 source address selection rules 54 for use with MLD. 56 Terminology 58 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 59 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 60 document are to be interpreted as described in [RFC 2119]. 62 MLD Source Address Selection Guidelines 64 An MLD speaking node is required to choose a suitable IPv6 source 65 address for all MLD messages (Report, Done, and Query). 67 MLD Query messages MUST be sent with a valid link-local address as 68 the IPv6 source address. If a router receives a query message with 69 an IPv6 source address set to the unspecified address (::), it MUST 70 silently discard the message and SHOULD log a warning. 72 MLD Report and Done messages SHOULD be sent with a valid link-local 73 address as the IPv6 source address. If a valid link-local address is 74 not available, the message MAY be sent with the unspecified address 75 (::) as the IPv6 source address. 77 Security Considerations 79 Security issues related to MLD are discussed in [RFC 2710]. 81 References 83 [RFC 2710] Deering, S., Fenner, W., Haberman, B., "Multicast Listener 84 Discovery (MLD) for IPv6", RFC 2710, October 1999. 86 [RFC 2461] Narten, T., Nordmark, E., Simpson, W., "Neighbor Discovery 87 for IP Version 6 (IPv6)", RFC 2461, December 1998. 89 [RFC 2462] Thomson, S., Narten, T., "IPv6 Stateless Address 90 Autoconfiguration", RFC 2462, December 1998. 92 [RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate 93 Requirement Levels", BCP 14, RFC 2119, March 1997. 95 Author's Address 97 Brian Haberman 98 Caspian Networks 99 bkhabs@nc.rr.com 101 Full Copyright Statement 103 Copyright (C) The Internet Society (2002). All Rights Reserved. 105 This document and translations of it may be copied and furnished to 106 others, and derivative works that comment on or otherwise explain it 107 or assist in its implementation may be prepared, copied, published 108 and distributed, in whole or in part, without restriction of any 109 kind, provided that the above copyright notice and this paragraph are 110 included on all such copies and derivative works. However, this 111 document itself may not be modified in any way, such as by removing 112 the copyright notice ore references to the Internet Society or other 113 Internet organizations, except as needed for the purpose of 114 developing Internet standards in which case the procedures for 115 copyrights defined in the Internet Standards process must be 116 followed, or as required to translate it into languages other than 117 English. 119 The limited permissions granted above are perpetual and will not be 120 revoked by the Internet Society or its successors or assigns. 122 This document and the information contained herein is provided on an 123 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 124 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 125 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 126 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 127 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.