Re: [OPSAWG] draft-azinger-additional-private-ipv4-space-issues
Matthew Ford <ford@isoc.org> Tue, 06 April 2010 15:11 UTC
Return-Path: <ford@isoc.org>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EC323A6988 for <opsawg@core3.amsl.com>; Tue, 6 Apr 2010 08:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.665
X-Spam-Level:
X-Spam-Status: No, score=-99.665 tagged_above=-999 required=5 tests=[BAYES_50=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ZYb06-829Ny for <opsawg@core3.amsl.com>; Tue, 6 Apr 2010 08:11:21 -0700 (PDT)
Received: from smtp118.dfw.emailsrvr.com (smtp118.dfw.emailsrvr.com [67.192.241.118]) by core3.amsl.com (Postfix) with ESMTP id 3F75F3A6989 for <opsawg@ietf.org>; Tue, 6 Apr 2010 08:11:20 -0700 (PDT)
Received: from relay11.relay.dfw.mlsrvr.com (localhost [127.0.0.1]) by relay11.relay.dfw.mlsrvr.com (SMTP Server) with ESMTP id CEEE0180053; Tue, 6 Apr 2010 11:11:17 -0400 (EDT)
Received: by relay11.relay.dfw.mlsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id D508817FF7F; Tue, 6 Apr 2010 11:11:16 -0400 (EDT)
Message-ID: <4BBB4F13.5060803@isoc.org>
Date: Tue, 06 Apr 2010 16:11:15 +0100
From: Matthew Ford <ford@isoc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Azinger, Marla" <marla.azinger@frontiercorp.com>
References: <2E2FECEBAE57CC4BAACDE67638305F104853068B84@ROCH-EXCH1.corp.pvt>
In-Reply-To: <2E2FECEBAE57CC4BAACDE67638305F104853068B84@ROCH-EXCH1.corp.pvt>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] draft-azinger-additional-private-ipv4-space-issues
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2010 15:11:23 -0000
Marla, Thanks for the continued opportunity to comment on this work. I think the document is a well-organised summary of the issues and concerns that pertain in this space. I do have a number of observations on the latest (-03) revision: Section 4.3 could also mention that any address space obtained in this way is unlikely to be contiguous, adding to the network management burden for the operator. Section 4.5 states, "Nonetheless, network operators are naturally disinclined to request unique IPv4 addresses for a purpose that could be met with private addresses were it not for the size of the network." I must admit to being a bit puzzled by this statement. You suggest the disinclination to request registered address space is 'natural', but I can't imagine why that might be the case, unless there is a significant financial disincentive to doing so. Can you shed a little more light here? Section 5.1 - I think the title could be improved - I'd suggest 'Redefining Existing Unicast Space as Additional Private Address Space' - this wording change would apply to the last para of the Section as well, and to the title of Section 5.3. Also in Section 5.1, 'It would be possible...' is a pretty opaque construction. What are you trying to say? It *is* possible? It *might be* possible? Or what? Section 5.2 could usefully include a back-reference to Section 4.4 as the issues created are very similar. Mat On 02/04/2010 22:57, Azinger, Marla wrote: > Hello- > > Leo and I are following up on the OPSWAG session at IETF 77 in Anaheim. As discussed we are requesting any final input people have for this draft. During the session there was a vote to move this forward and the majority of those people saw this draft ready for publishing. At this point only minor changes are in need of adjustment and a last call for comments. During the WG session in Anaheim there was one suggestion for some of the language in 5.1 to be tightened up a bit. We would appreciate text suggestions for this change and any other changes people would like to submit. > > Thank you everyone for your participation in regards to this document. > > Thank you Ron Bonica for stepping forward as the sponsoring Area Director for this document. > > Many thanks, > Marla& Leo > > > > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg
- [OPSAWG] draft-azinger-additional-private-ipv4-sp… Azinger, Marla
- Re: [OPSAWG] draft-azinger-additional-private-ipv… Matthew Ford
- Re: [OPSAWG] draft-azinger-additional-private-ipv… Azinger, Marla