idnits 2.17.1 draft-matsuhira-me6a-04.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (April 19, 2018) is 2198 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group N. Matsuhira 3 Internet-Draft Fujitsu Limited 4 Intended status: Informational April 19, 2018 5 Expires: October 21, 2018 7 Multiple Ethernet - IPv6 mapped IPv6 address (ME6A) 8 draft-matsuhira-me6a-04 10 Abstract 12 This document specifies Multiple Ethernet - IPv6 mapped IPv6 13 address(ME6A) spefification. ME6A is Ethernet mapped IPv6 address 14 with plane ID. Unique allocation of plane id value enable duplicated 15 MAC address unique in IPv6 address space. This address may use 16 Ethernet over IPv6 encapsulation. 18 Requirements Language 20 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 21 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 22 document are to be interpreted as described in RFC 2119 [RFC2119]. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on October 21, 2018. 41 Copyright Notice 43 Copyright (c) 2018 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. ME6A architecture . . . . . . . . . . . . . . . . . . . . . . . 3 60 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 62 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 5.1. Normative References . . . . . . . . . . . . . . . . . . . 4 64 5.2. References . . . . . . . . . . . . . . . . . . . . . . . . 4 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 1. Introduction 69 This document specifies Multiple Ethernet - IPv6 mapped IPv6 70 address(ME6A) spefification. ME6A is Ethernet mapped IPv6 address 71 with plane ID. Unique allocation of plane ID value enable duplicated 72 MAC address unique in IPv6 address space. 74 This address may use Ethernet over IPv6 encapsulation such as 75 Multiple Ethernet - IPv6 mapping encapsulation - fixed prefix 76 (ME6E-FP) [I-D.draft-matsuhira-me6e-fp] and Multiple Ethernet - IPv6 77 mapping encapsulation - prefix resolution (ME6E- 78 PR)[I-D.draft-matsuhira-me6e-pr]. 80 2. ME6A architecture 82 Figure 1 shows ME6A architecture. 84 | 128 - m -n bits | m bits | n bits | 85 +-----------------------+----------------------+------------------+ 86 | ME6A prefix | Ethernet plane ID | Ethernet address | 87 +-----------------------+----------------------+------------------+ 89 Figure 1 91 ME6A consists of three parts as follows. 93 ME6A prefix 95 ME6A prefix. This value is fixed value with M46E-FP, and non 96 fixed value with M46E-PR. 98 Ethernet plane ID 100 Ethernet network plane ID is network identification of Ethernet 101 network plane. 103 Ethernet address 105 Ethernet MAC address. EUI-48 address or EUI-64 address. 107 3. IANA Considerations 109 This document makes no request of IANA. 111 Note to RFC Editor: this section may be removed on publication as an 112 RFC. 114 4. Security Considerations 116 5. References 118 5.1. Normative References 120 [I-D.draft-matsuhira-me6e-fp] 121 Matsuhira, N., "Multiple Ethernet - IPv6 mapping 122 encapsulation - fixed prefix", April 2017. 124 [I-D.draft-matsuhira-me6e-pr] 125 Matsuhira, N., "Multiple Ethernet - IPv6 address mapping 126 encapsulation - prefix resolution", April 2017. 128 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 129 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 130 RFC2119, March 1997, 131 . 133 5.2. References 135 Author's Address 137 Naoki Matsuhira 138 Fujitsu Limited 139 17-25, Shinkamata 1-chome, Ota-ku 140 Tokyo, 144-8588 141 Japan 143 Phone: +81-3-3730-8386 144 Fax: 145 Email: matsuhira@jp.fujitsu.com