Re: Next steps on advancing core IPv6 specifications to full Internet standard

Tim Chown <Tim.Chown@jisc.ac.uk> Thu, 17 November 2016 05:35 UTC

Return-Path: <tim.chown@jisc.ac.uk>
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 D26921295DE for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2016 21:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level:
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=jisc365.onmicrosoft.com
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 XNgisu-7LHqm for <ipv6@ietfa.amsl.com>; Wed, 16 Nov 2016 21:35:35 -0800 (PST)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCD6F1295CA for <ipv6@ietf.org>; Wed, 16 Nov 2016 21:35:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=CQuQHgM2/zR3xFPbnu9NJWrxSEU6zrz8EMSrYo1GsQY=; b=euyJerJLyELr//l7E4x+WSXkA2ogqwmKVDBPMz6JaIOai3OCi0dAdc7uqW6h3VtXUpRQPJ454LwvpgoEd8DMmJkpBpCtYFj3ZsY/n03YXbQqpZYuvK6AWyL+wyjOtSNYT+R9V1tl318HYeQUSHo/SW9o9dE5WFK4g/mBCX/5sDc=
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-db5eur03lp0085.outbound.protection.outlook.com [94.245.120.85]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-61-8PqhHJeXNy6Vy-r6_XW5TQ-1; Thu, 17 Nov 2016 05:35:28 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1138.eurprd07.prod.outlook.com (10.163.188.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.734.2; Thu, 17 Nov 2016 05:35:27 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::d9ee:f373:b37e:9c77]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::d9ee:f373:b37e:9c77%15]) with mapi id 15.01.0734.007; Thu, 17 Nov 2016 05:35:27 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Next steps on advancing core IPv6 specifications to full Internet standard
Thread-Topic: Next steps on advancing core IPv6 specifications to full Internet standard
Thread-Index: AQHSPwhaWD+1Vt3LhECpxaMTOAss3aDb/lmAgAAMMgCAAKAsgA==
Date: Thu, 17 Nov 2016 05:35:27 +0000
Message-ID: <BAE856AB-67FA-4686-8B79-FA8800B92220@jisc.ac.uk>
References: <451D4151-B805-4A2E-8BAC-B6627C0B669C@employees.org> <CAJE_bqczRSZYWC3tDLXvxRMzqnV9nDjYjUddyRHtwfpGEXvm5w@mail.gmail.com> <189a5939-71c8-f686-b34c-cbf410d55374@gmail.com>
In-Reply-To: <189a5939-71c8-f686-b34c-cbf410d55374@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3251)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [31.133.135.173]
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1138; 7:ha/kbKT5QCGgZotkdiG+SwtS0FXTwp816WD6niC/9KL+o0wdb1w7YaeTI1k01EKpi8Q7+EtNUNqGLLXbEklRFL2mYnlgy5Rz097dHWLL6OOWH3is3BYNzb45BQpLjMGEahPehBpHGzyg6jK4l7IfrXEwT+dakbiCAwvRhZfxvXRwia5S+2i/yCnoMq32xBOuo0UHNJL2ZZ6LRoqyu5x2a07Rx40iOLoAG1UcWqaCh1GfmZRZWGChvnUeFw8yO+24lWTUPuvqCr7fQjvkvmOeeS5bgem3zIDfUPVeknIKlrSxCW9jtrZEUbDOyNtY/NZOR7daXJkerbAkXwNzXXlEsR6mdavn3xKbyla+JABYZgs=; 20:NveVYPYhhLEtsXnh4IwOC/hiI5jSHQTi2cIlwxgySBgjLvvoK3VdjPiJ+riMBdCSpOoJ2ejzzPvsvEfNOqVHENIbIkMVAUn1Nqag8lm03i3P8Uz2xYU1HbfNQKbtzIEKABY63NeU5vIFByntVtDxlPPWJ1O79BwM/XxS6C2oEG0=
x-ms-office365-filtering-correlation-id: ae124de9-b26a-492d-7d33-08d40eab899c
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM3PR07MB1138;
x-microsoft-antispam-prvs: <AM3PR07MB11386D50F372DB5E7F306588D6B10@AM3PR07MB1138.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6060326)(6040281)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6061324)(6041223); SRVR:AM3PR07MB1138; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1138;
x-forefront-prvs: 01294F875B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(24454002)(189002)(199003)(76176999)(110136003)(50986999)(4326007)(189998001)(6116002)(305945005)(81156014)(81166006)(102836003)(3846002)(68736007)(8936002)(33656002)(66066001)(5660300001)(6506003)(6512003)(101416001)(5250100002)(106356001)(50226002)(36756003)(57306001)(74482002)(105586002)(106116001)(2906002)(42882006)(2950100002)(6916009)(87936001)(83716003)(86362001)(229853002)(8676002)(7846002)(2900100001)(82746002)(7736002)(3280700002)(92566002)(97736004)(3660700001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1138; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <46B231E02D82294ABB2AA247C8C3B43D@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Nov 2016 05:35:27.5093 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1138
X-MC-Unique: 8PqhHJeXNy6Vy-r6_XW5TQ-1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/suNrecdwyimgc1Lmqg6oMvSODgo>
Cc: "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>, Suresh Krishnan <suresh.krishnan@ericsson.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 17 Nov 2016 05:35:37 -0000

> On 16 Nov 2016, at 20:02, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 17/11/2016 08:18, 神明達哉 wrote:
> ...
>> Assuming so, I'd like to say I still have a serious concern with this
>> text in that it's as "ambiguous" to the extent the original RFC2460
>> was ambiguous...
> 
> I think the question of principle here is whether a document with
> a known ambguity is qualified to become an Internet Standard.
> 
> If this WG can make no more progress on that question (and I have
> sympathy with the WG Chairs on that), it becomes a question for
> the community and the IESG during IETF Last Call.
> 
> As far as I can tell, ambiguity is not mentioned explicitly in
> RFC 2026 or RFC 6410.

Presumably that manifests itself when you consider whether implementations are interoperable and have widespread deployment and successful operational experience. 

Tim