idnits 2.17.1 draft-shirasaki-isp-shared-addr-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 : ---------------------------------------------------------------------------- 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 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 (July 11, 2011) is 4665 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'PROP58' is defined on line 164, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-shirasaki-nat444-isp-shared-addr-05 ** Downref: Normative reference to an Informational draft: draft-shirasaki-nat444-isp-shared-addr (ref. 'I-D.shirasaki-nat444-isp-shared-addr') == Outdated reference: A later version (-06) exists of draft-shirasaki-nat444-03 ** Downref: Normative reference to an Informational draft: draft-shirasaki-nat444 (ref. 'I-D.shirasaki-nat444') Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force I. Yamagata 3 Internet-Draft S. Miyakawa 4 Intended status: BCP NTT Communications 5 Expires: January 12, 2012 A. Nakagawa 6 Japan Internet Exchange (JPIX) 7 J. Yamaguchi 8 IIJ 9 H. Ashida 10 iTSCOM 11 July 11, 2011 13 ISP Shared Address 14 draft-shirasaki-isp-shared-addr-06 16 Abstract 18 This document defines IPv4 ISP Shared Address to be jointly used 19 among Internet Service Providers (ISPs). This space is intended to 20 be used in NAT444 model which is used during the transition period to 21 IPv6. 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 12, 2012. 40 Copyright Notice 42 Copyright (c) 2011 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. ISP Shared Address . . . . . . . . . . . . . . . . . . . . . . 3 59 2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2.2. Details . . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 3. Size of Address Space . . . . . . . . . . . . . . . . . . . . . 4 62 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 64 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 67 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 70 1. Introduction 72 The only permanent solution of the IPv4 address exhaustion is to 73 deploy IPv6. Now, just before the exhaustion, it's time to make a 74 transition to IPv6. 76 NAT444 model [I-D.shirasaki-nat444] is one of the solutions for 77 transition to IPv6. 79 This document defines ISP Shared Address to be used in NAT444 model 80 [I-D.shirasaki-nat444-isp-shared-addr]. It is supposed to be used 81 between Customer Premises Equipment (CPE) and Carrier Grade NAT (CGN) 82 [I-D.nishitani-cgn]. 84 ISP Shared Address is needed until the IPv4 Internet fades out. 86 2. ISP Shared Address 88 2.1. Definition 90 ISP Shared Address is intended to be assigned between CPE and CGN in 91 a NAT444. 93 2.2. Details 95 - Each ISP can use ISP Shared Address without any coordination with 96 IANA or Internet registries. 98 - ISP Shared Address can be used by many ISPs. 100 - ISP has to install CGN to use ISP Shared Address. 102 - ISP Shared Address must not be used at customers' site or Internet 103 Exchanges. 105 - Routing information of ISP Shared Address must not be advertised to 106 the Internet. 108 - Reverse DNS queries for this address space must not be sent to root 109 DNS servers. 111 - Packets with this space as source address and/or destination 112 address must be filtered out at the border of each ISP. 114 - Addresses within this address space should be unique within the 115 ISP, or the set of ISPs which choose to cooperate over this space so 116 they may directly communicate with each other in their networks. 118 3. Size of Address Space 120 Because the aggregation size of Tokyo area POP is around /10 in 121 Japan, /10 should be the hard limit of minimum size ISP Shared 122 Address. We understand this can be determined by further 123 discussions. 125 4. Acknowledgements 127 Thanks for the input and review by Shirou Niinobe, Takeshi Tomochika, 128 Tomohiro Fujisaki, Dai Nishino, JP address community members, AP 129 address community members and JPNIC members. 131 5. IANA Considerations 133 IANA is to record the allocation of the IPv4 global unicast address 134 as ISP Shared Address in the IPv4 address registry. 136 6. Security Considerations 138 ISP Shared Address is supposed to be used with CGN. The Global IPv4 139 address that is assigned outside CGN may be used as source address of 140 'Denial of Service' attack. 142 7. References 144 7.1. Normative References 146 [I-D.nishitani-cgn] 147 Yamagata, I., Miyakawa, S., Nakagawa, A., and H. Ashida, 148 "Common requirements for IP address sharing schemes", 149 draft-nishitani-cgn-05 (work in progress), July 2010. 151 [I-D.shirasaki-nat444-isp-shared-addr] 152 Shirasaki, Y., Miyakawa, S., Nakagawa, A., Yamaguchi, J., 153 and H. Ashida, "NAT444 addressing models", 154 draft-shirasaki-nat444-isp-shared-addr-05 (work in 155 progress), January 2011. 157 [I-D.shirasaki-nat444] 158 Yamagata, I., Shirasaki, Y., Nakagawa, A., Yamaguchi, J., 159 and H. Ashida, "NAT444", draft-shirasaki-nat444-03 (work 160 in progress), January 2011. 162 7.2. Informative References 164 [PROP58] Niinobe, S., Tomochika, T., Yamaguchi, J., Nishino, D., 165 Ashida, H., Nakagawa, A., and T. Hosaka, "Proposal to 166 create IPv4 shared use address space among LIRs", 2008, 167 . 170 Authors' Addresses 172 Ikuhei Yamagata 173 NTT Communications Corporation 174 Gran Park Tower 17F, 3-4-1 Shibaura, Minato-ku 175 Tokyo 108-8118 176 Japan 178 Phone: +81 3 6700 8530 179 Email: ikuhei@nttv6.jp 181 Shin Miyakawa 182 NTT Communications Corporation 183 Gran Park Tower 17F, 3-4-1 Shibaura, Minato-ku 184 Tokyo 108-8118 185 Japan 187 Phone: +81 50 3812 4695 188 Email: miyakawa@nttv6.jp 190 Akira Nakagawa 191 Japan Internet Exchange Co., Ltd. (JPIX) 192 Otemachi Building 21F, 1-8-1 Otemachi, Chiyoda-ku 193 Tokyo 100-0004 194 Japan 196 Phone: +81 90 9242 2717 197 Email: a-nakagawa@jpix.ad.jp 198 Jiro Yamaguchi 199 Internet Initiative Japan Inc. 200 Kakyoin Square Bldg., 15F, 1-1-20 Kakyoin, Aoba-ku 201 Sendai 980-0013 202 Japan 204 Phone: +81 22 216 5650 205 Email: jiro-y@iij.ad.jp 207 Hiroyuki Ashida 208 its communications Inc. 209 541-1 Ichigao-cho Aoba-ku 210 Yokohama 225-0024 211 Japan 213 Email: ashida@itscom.ad.jp