idnits 2.17.1 draft-matsuhira-m46a-12.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 (4 April 2022) is 745 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 WIDE Project 4 Intended status: Informational 4 April 2022 5 Expires: 6 October 2022 7 Multiple IPv4 - IPv6 mapped IPv6 address (M46A) 8 draft-matsuhira-m46a-12 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 6 October 2022. 41 Copyright Notice 43 Copyright (c) 2022 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 (https://trustee.ietf.org/ 48 license-info) in effect on the date of publication of this document. 49 Please review these documents carefully, as they describe your rights 50 and restrictions with respect to this document. Code Components 51 extracted from this document must include Revised BSD License text as 52 described in Section 4.e of the Trust Legal Provisions and are 53 provided without warranty as described in the Revised BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. M46A architecture . . . . . . . . . . . . . . . . . . . . . . 2 59 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 60 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 61 5. Normative References . . . . . . . . . . . . . . . . . . . . 3 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 64 1. Introduction 66 This document specifies Multiple IPv4 - IPv6 mapped IPv6 67 address(M46A) spefification. M46A is IPv4 mapped IPv6 address with 68 plane ID. Unique allocation of plane ID value enable IPv4 private 69 address unique in IPv6 address space. 71 This address may use IPv4 over IPv6 encapsulation such as Multiple 72 IPv4 - IPv6 mapping encapsulation - fixed prefix (M46E-FP) M46E-FP 73 [I-D.draft-matsuhira-m46e-fp], Multiple IPv4 - IPv6 mapping 74 encapsulation - prefix resolution (M46E-PR)M46E-PR 75 [I-D.draft-matsuhira-m46e-pr], Multiple IPv4 - IPv6 mapping 76 encapsuration - prefix translator (M46E-PT)M46E-PT 77 [I-D.draft-matsuhira-m46e-pt] and IPv4 - IPv6 translation such as 78 Multiple IPv4 - IPv6 mapping translator (M46T)M46T 79 [I-D.draft-matsuhira-m46t]. 81 2. M46A architecture 83 Figure 1 shows M46A architecture. 85 | 96 - m bits | m bits | 32 bits | 86 +-----------------------+--------------------------+--------------+ 87 | M46A prefix | IPv4 network plane ID | IPv4 address | 88 +-----------------------+--------------------------+--------------+ 90 Figure 1 92 M46A consists of three parts as follows. 94 M46A prefix 95 M46A prefix. This value is fixed value with M46E-FP, and non 96 fixed value with M46E-PR. 98 IPv4 network plane ID 99 IPv4 network plane ID is network identification of IPv4 network 100 plane. 102 IPv4 address 103 IPv4 address 105 3. IANA Considerations 107 This document makes no request of IANA. 109 Note to RFC Editor: this section may be removed on publication as an 110 RFC. 112 4. Security Considerations 114 5. Normative References 116 [I-D.draft-matsuhira-m46e-fp] 117 Matsuhira, N., "Multiple IPv4 - IPv6 mapping encapsulation 118 - fixed prefix", 1 June 2019. 120 [I-D.draft-matsuhira-m46e-pr] 121 Matsuhira, N., "Multiple IPv4 - IPv6 address mapping 122 encapsulation - prefix resolution", 1 June 2019. 124 [I-D.draft-matsuhira-m46e-pt] 125 Matsuhira, N., "Multiple IPv4 - IPv6 mapping encapsulation 126 - prefix translator", 1 June 2019. 128 [I-D.draft-matsuhira-m46t] 129 Matsuhira, N., "Multiple IPv4 - IPv6 maping translator", 1 130 June 2019. 132 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 133 Requirement Levels", BCP 14, RFC 2119, 134 DOI 10.17487/RFC2119, March 1997, 135 . 137 Author's Address 138 Naoki Matsuhira 139 WIDE Project 140 Japan 141 Email: naoki.matsuhira@gmail.com