Re: Stewart Bryant's No Objection on draft-ietf-6man-ug-06: (with COMMENT)

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 17 December 2013 19:23 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A7871AE2BF; Tue, 17 Dec 2013 11:23:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UL0g6tXEX4vt; Tue, 17 Dec 2013 11:23:21 -0800 (PST)
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 BE6771AE1D2; Tue, 17 Dec 2013 11:23:21 -0800 (PST)
Received: by mail-pb0-f41.google.com with SMTP id jt11so7422646pbb.0 for <multiple recipients>; Tue, 17 Dec 2013 11:23:20 -0800 (PST)
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=exb8vO60bfUoVLj8stR1foTsfKQzGZtL3p4xdX+GcHY=; b=KAaQNXhtK3wU79UabOvHWVPAtNen28oL85MCxEYF+LjcTD0WHRjkVVW3eqnP3nS1hT rKG5v6lTq3z6JrU2/mmpSc/ptMqwwJRiHZ3vb2wjGTFu4t38X+DfwcId+ZPCPq75ML/7 Qvljc1DxJo+No9PAN/BcmEFEfwIqkHxfu5qvNwI3YAfDnlJwwZto0R/tVcr249PNlivH 2DZ0LEhsY7X82IKAZAAgHmgdu4wdwwKrilphp0rYgHnwNzorzWaRF5m96TOXMvXZ6E8q h9A3tvInQO/JsP7GAtbEUsu7FHktJpMm73FZLErjCmhT/JAttMN8BqOa92DwBtWqEnqq vUYA==
X-Received: by 10.68.194.71 with SMTP id hu7mr29235650pbc.68.1387308199786; Tue, 17 Dec 2013 11:23:19 -0800 (PST)
Received: from [192.168.178.20] (220.194.69.111.dynamic.snap.net.nz. [111.69.194.220]) by mx.google.com with ESMTPSA id q7sm19181580pbc.20.2013.12.17.11.23.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Dec 2013 11:23:19 -0800 (PST)
Message-ID: <52B0A4A7.3090802@gmail.com>
Date: Wed, 18 Dec 2013 08:23:19 +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: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Stewart Bryant's No Objection on draft-ietf-6man-ug-06: (with COMMENT)
References: <20131217125045.2313.82095.idtracker@ietfa.amsl.com>
In-Reply-To: <20131217125045.2313.82095.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, ipv6@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-6man-ug@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Dec 2013 19:23:23 -0000

Stewart,

On 18/12/2013 01:50, Stewart Bryant wrote:
...
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I have no objection to the publication of this draft.
> 
> Maybe it is just me, but it seems very strange to publish a Standards
> Track document, the substance of which seems to be to tell the reader
> that their *may* be a special meaning to two bits but they cannot  know
> for certain that this is the case. I understand that for procedural
> reasons the RFC needs to be published as ST, but perhaps the definitive
> statements should be in the normative text and the informational text
> should be an appendix.

Hmm... I think what we are telling the reader is that she must never rely
on those two bits having a special meaning, although there is pervasive
folklore that they *are* special.

> I found the document very confusing to read, but given the expertise of
> the authors, shepherd, AD and reviewers, I conclude that the text
> correct, and the IPv6 address architecture is complex. Hopefully it is
> not yet too complex for those that need to deploy and configure IPv6.

I suppose the day might come for a major revision of RFC 4291, and of
all the IPv6-over-foo documents, but until then we are stuck with
a pretty complex situation I'm afraid.

   Brian