RE: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt

Dave Thaler <dthaler@microsoft.com> Sat, 28 January 2012 01:23 UTC

Return-Path: <dthaler@microsoft.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 026ED21F84CF for <ipv6@ietfa.amsl.com>; Fri, 27 Jan 2012 17:23:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.979
X-Spam-Level:
X-Spam-Status: No, score=-103.979 tagged_above=-999 required=5 tests=[AWL=-0.380, 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 q6Mfc5pxgC7R for <ipv6@ietfa.amsl.com>; Fri, 27 Jan 2012 17:23:22 -0800 (PST)
Received: from DB3EHSOBE002.bigfish.com (db3ehsobe001.messaging.microsoft.com [213.199.154.139]) by ietfa.amsl.com (Postfix) with ESMTP id 14B0521F84C3 for <ipv6@ietf.org>; Fri, 27 Jan 2012 17:23:21 -0800 (PST)
Received: from mail71-db3-R.bigfish.com (10.3.81.245) by DB3EHSOBE002.bigfish.com (10.3.84.22) with Microsoft SMTP Server id 14.1.225.23; Sat, 28 Jan 2012 01:23:20 +0000
Received: from mail71-db3 (localhost [127.0.0.1]) by mail71-db3-R.bigfish.com (Postfix) with ESMTP id BB92F160609; Sat, 28 Jan 2012 01:23:20 +0000 (UTC)
X-SpamScore: -12
X-BigFish: VS-12(zz179dN1432Nzz1202hzzz2fhc1bhc31hc1ah2a8h668h839h944h)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14MLTC104.redmond.corp.microsoft.com; RD:none; EFVD:NLI
Received-SPF: pass (mail71-db3: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=dthaler@microsoft.com; helo=TK5EX14MLTC104.redmond.corp.microsoft.com ; icrosoft.com ;
Received: from mail71-db3 (localhost.localdomain [127.0.0.1]) by mail71-db3 (MessageSwitch) id 132771379920231_7707; Sat, 28 Jan 2012 01:23:19 +0000 (UTC)
Received: from DB3EHSMHS004.bigfish.com (unknown [10.3.81.237]) by mail71-db3.bigfish.com (Postfix) with ESMTP id E8FD7A0045; Sat, 28 Jan 2012 01:23:18 +0000 (UTC)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.8) by DB3EHSMHS004.bigfish.com (10.3.87.104) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 28 Jan 2012 01:23:16 +0000
Received: from TK5EX14MLTW653.wingroup.windeploy.ntdev.microsoft.com (157.54.24.14) by TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) with Microsoft SMTP Server (TLS) id 14.2.247.5; Fri, 27 Jan 2012 17:23:13 -0800
Received: from TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.234]) by TK5EX14MLTW653.wingroup.windeploy.ntdev.microsoft.com ([157.54.24.14]) with mapi id 14.01.0355.003; Fri, 27 Jan 2012 17:23:13 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: Chris Grundemann <cgrundemann@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
Thread-Topic: 6MAN WG Last Call: draft-ietf-6man-rfc3484-revise-05.txt
Thread-Index: AQHMmvx1vO8I87vUo0m73gUxdiNcXZXd39qAgAAf8wCAAAn2gIAAFZKAgAAYZICAABHNAIAABeSAgEMv5BA=
Date: Sat, 28 Jan 2012 01:23:13 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653B3C3777@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com> <4EEA3D20.7020603@innovationslab.net> <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com> <4EEA5793.8080800@gmail.com> <CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com> <4EEA7AF8.2090508@gmail.com> <CAC1-dtn9M8-9cPAmkhCiGV0Gi5+Gfs8GAssTOaA-ZFhyUY3feg@mail.gmail.com>
In-Reply-To: <CAC1-dtn9M8-9cPAmkhCiGV0Gi5+Gfs8GAssTOaA-ZFhyUY3feg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.90]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@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: Sat, 28 Jan 2012 01:23:23 -0000

> >> Hmm sorry for being unclear, the technical part looked okay as far as
> >> I could tell, but as the quoted words from you, it will probably be
> >> more confusing to have two documents where the last one update/change
> >> the first one. Would be much better to have just one
> >> replacing/updating the old one.
> >
> > That was my first thought, but then I realised it would cause a lot of
> > delay, and I think getting these changes deployed is quite urgent.
> 
> I must agree, there is certainly an urgent need to fix the problems in the current
> RFC 3484, particularly around the handling of ULAs, etc.
> For one example; I am currently working on sorting out proper IPv6 support in
> UPnP and DLNA (targeting CE) and we have (effectively) nothing to point to for
> dynamic source address selection procedures.
> Since there appears to be consensus on the technical changes, is there a way to
> make the needed editorial changes and then advance to IETF last call (or a
> second WG last call at least)?

Resurrecting this thread in the hopes of resurrecting some energy on this draft...

It is not correct that we have consensus on the technical changes, since
I raised a number of technical issues in my review of the document (and
since only Brian and I reviewed, that's 50% of reviewers :)

That said, I think it would be easy to get consensus since I made specific
recommendations that I don't think should be controversial.   But in any case,
this would definitely need a second WGLC.

-Dave