Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 19 August 2011 23:05 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96D7411E8087 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 16:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HTUljAkSeOtV for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 16:05:23 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id D687511E8082 for <ietf@ietf.org>; Fri, 19 Aug 2011 16:05:22 -0700 (PDT)
Received: by fxe6 with SMTP id 6so2448492fxe.31 for <ietf@ietf.org>; Fri, 19 Aug 2011 16:06:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wXsqT6I4k7+tMPAb4FAFkqppBwMXfAErbVYr4GTSEfE=; b=KTN1P1zOq53tCbZzH0IcrAFSUmV0rDSw6S8mnWaPIM0M007QXT9eXeruV1sxK3gxOJ 3EQKPZy9gKZMPRagPXSGztUTa9wtayIXMinEqXJ4II8ZaWr8uk9oYthyjnSSWznNm5aO D457NXfRqwtnjd1QnG5eR/m6Y9eTd9bwDT9uQ=
Received: by 10.223.99.91 with SMTP id t27mr369912fan.56.1313795178011; Fri, 19 Aug 2011 16:06:18 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id b14sm2924731fab.43.2011.08.19.16.06.14 (version=SSLv3 cipher=OTHER); Fri, 19 Aug 2011 16:06:17 -0700 (PDT)
Message-ID: <4E4EEC56.2010705@gmail.com>
Date: Sat, 20 Aug 2011 11:05:58 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
References: <20110819161025.15887.78808.idtracker@ietfa.amsl.com> <20110819213005.GD25053@x27.adm.denic.de>
In-Reply-To: <20110819213005.GD25053@x27.adm.denic.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Peter Koch <pk@ISOC.DE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 23:05:23 -0000

On 2011-08-20 09:30, Peter Koch wrote:
...
> o draft-bdgks-arin-shared-transition-space-01.txt would have to be elevated 
>   to a normative reference, with all consequences

I don't think this is really required; it is after all an
explanatory document. However, I do think that *if* draft-weil-
is to be published, draft-bdgks needs to be published
simultaneously. Therefore, I think that synchronised Last Calls
are needed.

I have previously argued against draft-weil on the OPSAWG list
and lost, so I will not repeat that argument here. However, if
it is to proceed, then some of my WGLC comments have not yet
been fixed:

>> At the very minimum, if draft-weil is to proceed, it should describe the
>> phase-out plan for the proposed prefix (i.e. the phase-out plan for CGN
>> deployment). One approach to that is documented in RFC 6264.

The authors didn't agree with that comment, but since this is
essentially an operational matter, I think they are wrong. If
the IETF sticks its nose into RIR matters in this way (as the
IAB has concluded that we should*), then we should do a complete
job.

>> It is strange that draft-weil doesn't reference RFC 6319 and RFC 6269.

In other words, draft-weil doesn't recognise the
counter-arguments. That seems wrong to me.

   Brian Carpenter

*
http://www.iab.org/documents/correspondence-reports-documents/2011-2/response-to-arins-request-for-guidance-regarding-draft-policy-arin-2011-5/