idnits 2.17.1 draft-matsuhira-m46a-09.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 (December 15, 2020) is 1200 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 December 15, 2020 5 Expires: June 18, 2021 7 Multiple IPv4 - IPv6 mapped IPv6 address (M46A) 8 draft-matsuhira-m46a-09 10 Abstract 12 This document specifies Multiple IPv4 - IPv6 mapped IPv6 13 address(M46A) spefification. M46A is IPv4 mapped IPv6 address with 14 plane ID. Unique allocation of plane id value enable IPv4 private 15 address unique in IPv6 address space. This address may use IPv4 over 16 IPv6 encapsulation and IPv4 - IPv6 translation. 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 https://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 June 18, 2021. 41 Copyright Notice 43 Copyright (c) 2020 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 (https://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 . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. M46A architecture . . . . . . . . . . . . . . . . . . . . . . 2 60 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 62 5. Normative References . . . . . . . . . . . . . . . . . . . . 3 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 65 1. Introduction 67 This document specifies Multiple IPv4 - IPv6 mapped IPv6 68 address(M46A) spefification. M46A is IPv4 mapped IPv6 address with 69 plane ID. Unique allocation of plane ID value enable IPv4 private 70 address unique in IPv6 address space. 72 This address may use IPv4 over IPv6 encapsulation such as Multiple 73 IPv4 - IPv6 mapping encapsulation - fixed prefix (M46E-FP) M46E-FP 74 [I-D.draft-matsuhira-m46e-fp], Multiple IPv4 - IPv6 mapping 75 encapsulation - prefix resolution (M46E-PR)M46E-PR 76 [I-D.draft-matsuhira-m46e-pr], Multiple IPv4 - IPv6 mapping 77 encapsuration - prefix translator (M46E-PT)M46E-PT 78 [I-D.draft-matsuhira-m46e-pt] and IPv4 - IPv6 translation such as 79 Multiple IPv4 - IPv6 mapping translator (M46T)M46T 80 [I-D.draft-matsuhira-m46t]. 82 2. M46A architecture 84 Figure 1 shows M46A architecture. 86 | 96 - m bits | m bits | 32 bits | 87 +-----------------------+--------------------------+--------------+ 88 | M46A prefix | IPv4 network plane ID | IPv4 address | 89 +-----------------------+--------------------------+--------------+ 91 Figure 1 93 M46A consists of three parts as follows. 95 M46A prefix 96 M46A prefix. This value is fixed value with M46E-FP, and non 97 fixed value with M46E-PR. 99 IPv4 network plane ID 101 IPv4 network plane ID is network identification of IPv4 network 102 plane. 104 IPv4 address 106 IPv4 address 108 3. IANA Considerations 110 This document makes no request of IANA. 112 Note to RFC Editor: this section may be removed on publication as an 113 RFC. 115 4. Security Considerations 117 5. Normative References 119 [I-D.draft-matsuhira-m46e-fp] 120 Matsuhira, N., "Multiple IPv4 - IPv6 mapping encapsulation 121 - fixed prefix", June 2019. 123 [I-D.draft-matsuhira-m46e-pr] 124 Matsuhira, N., "Multiple IPv4 - IPv6 address mapping 125 encapsulation - prefix resolution", June 2019. 127 [I-D.draft-matsuhira-m46e-pt] 128 Matsuhira, N., "Multiple IPv4 - IPv6 mapping encapsulation 129 - prefix translator", June 2019. 131 [I-D.draft-matsuhira-m46t] 132 Matsuhira, N., "Multiple IPv4 - IPv6 maping translator", 133 June 2019. 135 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 136 Requirement Levels", BCP 14, RFC 2119, 137 DOI 10.17487/RFC2119, March 1997, 138 . 140 Author's Address 142 Naoki Matsuhira 143 Fujitsu Limited 144 17-25, Shinkamata 1-chome, Ota-ku 145 Tokyo 144-8588 146 Japan 148 Phone: +81-3-3735-1111 149 Email: matsuhira@fujitsu.com