idnits 2.17.1 draft-droms-6man-multicast-scopes-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. -- The draft header indicates that this document updates RFC4291, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4291, updated by this document, for RFC5378 checks: 2003-10-10) -- 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 (May 22, 2013) is 3982 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force R. Droms 3 Internet-Draft Cisco 4 Updates: RFC 4291 (if approved) May 22, 2013 5 Intended status: Standards Track 6 Expires: November 23, 2013 8 IPv6 Multicast Address Scopes 9 draft-droms-6man-multicast-scopes-00.txt 11 Abstract 13 This document updates the definitions of IPv6 multicast scopes. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on November 23, 2013. 32 Copyright Notice 34 Copyright (c) 2013 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 1. Definition of IPv6 Multicast Address Scopes 48 RFC 4291 [RFC4291] defines values and semantics for the scope field 49 in IPv6 multicast addresses. The following table updates those 50 definitions: 52 0 reserved 54 1 Interface-Local scope 56 2 Link-Local scope 58 3 Network-Specific scope, greater than Link-Local scope, defined 59 automatically from the network topology 61 4 Admin-Local scope 63 5 Site-Local scope 65 6 (unassigned) 67 7 (unassigned) 69 8 Organization-Local scope 71 9 (unassigned) 73 A (unassigned) 75 B (unassigned) 77 C (unassigned) 79 D (unassigned) 81 E Global scope 83 F reserved 85 2. Definition of Network-Specific scopes 87 The definition of any Network-Specific scope for a particular network 88 technology should be published in an RFC. For example, such a scope 89 definition would be appropriate for publication in an "IPv6-over-foo" 90 RFC. 92 Any RFCs that include the definition of a Network-Specific scope will 93 be listed in the IANA "IPv6 Multicast Address Scopes" registry. 95 3. IANA Considerations 97 IANA is asked to establish a sub-registry titled "IPv6 Multicast 98 Address Scopes" in the existing "Internet Protocol version 6 (IPv6) 99 Multicast Address Allocations" registry. The "IPv6 Multicast Address 100 Scopes" is to be populated with the scope values given in section 1, 101 with a note associated with scope 3 listing all RFCs that define 102 Network-Specific scoping rules that use scope 3. 104 4. Security Considerations 106 This document has no security considerations beyond those in RFC 4291 107 [RFC4291]. 109 5. Normative References 111 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 112 Architecture", RFC 4291, February 2006. 114 Author's Address 116 Ralph Droms 117 Cisco 118 1414 Massachusetts Avenue 119 Boxborough, MA 01719 120 US 122 Phone: +1 978 936 1674 123 Email: rdroms@cisco.com