Re: Stephen Farrell's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 11 October 2013 04:25 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B2711E811D; Thu, 10 Oct 2013 21:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level:
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, 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 Rm9TqGUyGDUs; Thu, 10 Oct 2013 21:25:01 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id C6EEE21E812A; Thu, 10 Oct 2013 21:24:49 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp2so3638338pbb.28 for <multiple recipients>; Thu, 10 Oct 2013 21:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9kzB8EO3d3P9YP4LLaz/5mzfSqvNZrKGRM7AJqY+/8M=; b=YHAxKcKYdNVXSoKV3zuGzpbAkAnFFretztf28gBqZ0xWpl0fXg05ZxGQsBaaBsPqYb FIASbF5mQzpoesbwxpBZ5K8MDi2LNrj8gRGXvtL78vmmGD+ktjkh8+vl2vLRuy9Iasci G9KSVady3EvM2y40VQq92zcRxTgJ4h4/ud29g5tlGpwbvwnI76TFqXSowE3bbF3kljM+ Njxhj7CRocfdr9T8XJ594uWZVSe0+bLXY86YIvmTyH65lqs/2mnNoZ8hAVnp1JMLEf0N Da4a/dNE0mt/XYKAHNsUilvo+u+bH2qHn0MZxzwu0+lVrzZ36ZJviQnFNhPuh9+ziPEq fejQ==
X-Received: by 10.66.192.132 with SMTP id hg4mr19584825pac.84.1381465489589; Thu, 10 Oct 2013 21:24:49 -0700 (PDT)
Received: from [192.168.178.20] (167.201.69.111.dynamic.snap.net.nz. [111.69.201.167]) by mx.google.com with ESMTPSA id yh1sm56802011pbc.21.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 21:24:48 -0700 (PDT)
Message-ID: <52577D97.1010009@gmail.com>
Date: Fri, 11 Oct 2013 17:24:55 +1300
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: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Stephen Farrell's No Objection on draft-ietf-6man-ext-transmit-04: (with COMMENT)
References: <20131008103111.25649.95882.idtracker@ietfa.amsl.com>
In-Reply-To: <20131008103111.25649.95882.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-ext-transmit@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Oct 2013 04:25:09 -0000

On 08/10/2013 23:31, Stephen Farrell wrote:
...
> - 2.1 says nodes SHOULD forward rfc4727 experimental
> headers, but earlier said that its ok (nodes MAY) default
> to not forwarding packets with experimental headers. I
> think you need to add an "unless otherwise stated here"
> to the statement about defaults for experimental headers.

I must be missing something, but I can't find an inconsistency.

> 
> - section 4: Is it wise to ask IANA to "redirect" users
> from one (empty) registry to another? That could be the
> start of a slippery slope turning IANA registries into a
> miasma of hypertext;-) Maybe it'd be better to ask that
> IANA mark that registry as having being replaced by this
> new one. Also - what if someone else asks IANA to add an
> entry to the currently empty registry but not the new one
> - is it clear what should happen in that case?

It does need to be clear that the old registry is closed,
but we have to leave a pointer because it's referred to
elsewhere. I think IANA can figure it out, but we should
add "close to new entries".

I think we are already in a miasma of hypertext.

     Brian
> 
> 
>