Apologies for top posting rather than addressing specific commentators, but there have been several misconceptions raised several times that I felt should be addressed generically:
1) "We are out of IPv4 space / There's no-where to get this /10" - There is already a /10 reserved by the ARIN community for this purpose (as long as we don't drag our feet too long), please see: https://www.arin.net/policy/proposals/2011_5.html 2) "Just use 1918 space" - I apologize for not having more data to share, but I can tell you that I have spoken with numerous network operators and NONE of them are willing to do this. ISPs will NOT use RFC 1918 space, no matter how many times folks scream it from the tops of ivory towers. Operational realities must sometimes trump ideals. 3) "CGN is bad" - This one is accurate. It has no bearing on this I-D whatsoever though. Yes, CGN sucks and we want as few networks to use it as possible. But, no matter what we do, some will have to deploy it. This I-D is about helping reduce everyone's pain when they do. Leaking squat space hurts more than just the one who leaks it... 4) "IPv6 is awesome" - Again, accurate but inconsequential here. IPv6 does not solve IPv4 connectivity issues. Operators are not solely responsible for the lack of IPv6 penetration. Rather than throw stones from our glass houses, we should focus on ensuring that the transition can happen without shattering all of them. I understand that many have strong emotional ties to their opinions. My only hope is to point those with open minds in the right direction as they seek to understand this issue more fully. Cheers, ~Chris (speaking for myself, from an ivory tower made of glass) On Mon, Jan 30, 2012 at 16:03, The IESG <iesg-secret...@ietf.org> wrote: > > The IESG has received a request from an individual submitter to consider the > following document: > - 'IANA Reserved IPv4 Prefix for Shared CGN Space' > <draft-weil-shared-transition-space-request-14.txt> as a BCP > > On its December 15, 2011 telechat, the IESG reviewed version 10 of this > document and requested various changes. These changes are reflected in > the draft version 14 and the IESG now solicits community input on the > changed text only. Please send substantive comments to the ietf@ietf.org > mailing lists by 2012-02-16. Exceptionally, comments may be sent to > i...@ietf.org instead. In either case, please retain the beginning of > the Subject line to allow automated sorting. > > Abstract > > This document requests the allocation of an IPv4 /10 address block to > be used as Shared Address Space to accommodate the needs of Carrier > Grade Network Address Translation (CGN) devices. It is anticipated > that Service Providers will use this Shared Address Space to number > the interfaces that connect CGN devices to Customer Premise Equipment > (CPE). > > Shared Address Space is distinct from RFC1918 private address space > because it is intended for use on Service Provider networks. > However, it may be used as RFC 1918 private address space in certain > circumstances. Details are provided in the text of this document. > > As this document proposes the allocation of an additional special-use > IPv4 address block, it updates RFC 5735. > > The following text captures the most salient change between version 10 and 14 > of this document: > > Shared Address Space is IPv4 address space designated for Service > Provider use with the purpose of facilitating CGN deployment. Also, > Shared Address Space can be used as additional [RFC1918] space when > at least one of the following conditions is true: > > o Shared Address Space is not also used on the Service Provider side > of the CPE. > > o CPE routers behave correctly when using the same address block on > both the internal and external interfaces. > > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-weil-shared-transition-space-request/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-weil-shared-transition-space-request/ > > > No IPR declarations have been submitted directly on this I-D. > _______________________________________________ > IETF-Announce mailing list > ietf-annou...@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce -- @ChrisGrundemann http://chrisgrundemann.com _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
