idnits 2.17.1 draft-gundavelli-v6ops-l2-unicast-06.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 draft header indicates that this document updates RFC2464, 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 RFC2464, updated by this document, for RFC5378 checks: 1997-03-24) -- 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 (October 19, 2010) is 4935 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 (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 v6ops WG S. Gundavelli 3 Internet-Draft M. Townsley 4 Updates: 2464 (if approved) O. Troan 5 Intended status: Standards Track W. Dec 6 Expires: April 22, 2011 Cisco 7 October 19, 2010 9 Address Mapping of IPv6 multicast packets on Ethernet 10 draft-gundavelli-v6ops-l2-unicast-06.txt 12 Abstract 14 When transmitting an IPv6 packet with a multicast destination 15 address, the IPv6 destination address is mapped to an Ethernet link- 16 layer multicast address. This document clarifies that a mapping of 17 an IPv6 packet with a multicast destination address may in some 18 circumstances map to an Ethernet link-layer unicast address. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on April 22, 2011. 37 Copyright Notice 39 Copyright (c) 2010 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 1. Introduction 54 Transmission of IPv6 Packets over Ethernet [RFC2464] section 7, 55 specifies how an IPv6 packet with a multicast destination address is 56 mapped into an Ethernet link-layer address. This document extends 57 this mapping to explicitly allow for a mapping of an IPv6 packet with 58 a multicast destination address into an Ethernet link-layer unicast 59 address, when it is clear that only one address is relevant. 61 This mapping does not replace the mapping described in [RFC2464] 62 section 7. The determination of the unicast Ethernet link-layer 63 address and the construction of the outgoing IPv6 packet are out of 64 scope for this document. 66 2. Conventions 68 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 69 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 70 document are to be interpreted as described in RFC 2119 [RFC2119]. 72 3. Receiving IPv6 multicast packets 74 An IPv6 node receiving an IPv6 packet with a multicast destination 75 address and an Ethernet link-layer unicast address MUST NOT drop the 76 packet as a result of the use of this form of address mapping. 78 4. IANA Considerations 80 This specification does not require any IANA actions. 82 5. Security Considerations 84 This document does not introduce any new security vulnerabilities. 86 6. Acknowledgements 88 The authors would like to acknowledge Bernard Aboba, Fred Baker, Wes 89 Beebee, Ron Bonica, Olaf Bonness, Jean-Michel Combes, Ralph Droms, 90 Alain Durand, Suresh Krishnan, Eric Levy-Abegnoli, Phil Roberts, 91 Behcet Sarikaya, Hemant Singh, Mark Smith, Dave Thaler, Pascal 92 Thubert, Stig Venaas and Eric Voit for their contributions and 93 discussions on this topic. 95 7. Normative References 97 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 98 Requirement Levels", BCP 14, RFC 2119, March 1997. 100 [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet 101 Networks", RFC 2464, December 1998. 103 Authors' Addresses 105 Sri Gundavelli 106 Cisco 107 170 West Tasman Drive 108 San Jose, CA 95134 109 USA 111 Email: sgundave@cisco.com 113 Mark Townsley 114 Cisco 115 L'Atlantis, 11, Rue Camille Desmoulins 116 ISSY LES MOULINEAUX, ILE DE FRANCE 92782 117 France 119 Email: townsley@cisco.com 121 Ole Troan 122 Cisco 123 Oslo, 124 Norway 126 Email: ot@cisco.com 128 Wojciech Dec 129 Cisco 130 Haarlerbergweg 13-19 131 Amsterdam, Noord-Holland 1101 CH 132 Netherlands 134 Email: wdec@cisco.com