Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01

Erik Nordmark <nordmark@acm.org> Thu, 23 April 2015 22:47 UTC

Return-Path: <nordmark@acm.org>
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 0080B1A8A11 for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 15:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no
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 BSEVsKj3Ydon for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 15:47:37 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3EFC1A8A4F for <ipv6@ietf.org>; Thu, 23 Apr 2015 15:47:23 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3NMlJO7017804 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Apr 2015 15:47:19 -0700
Message-ID: <55397677.2040107@acm.org>
Date: Thu, 23 Apr 2015 15:47:19 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, Erik Nordmark <nordmark@acm.org>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net> <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com> <55353A60.1030701@acm.org> <CAKD1Yr19w1Uy=3VSpNua3qJ-bb1yz_zCW4L8k0FV9YJAgvOtXw@mail.gmail.com> <55368297.6080006@acm.org> <CAKD1Yr1oy4TkKvFfF05V6KsyE2xsEACNqtuhLqnbgunW2hbcdA@mail.gmail.com>
In-Reply-To: <CAKD1Yr1oy4TkKvFfF05V6KsyE2xsEACNqtuhLqnbgunW2hbcdA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVbOfBhaO4qY7SASqfMeqOSwNjPvcxC0GGmcSWFOjwSYdNaVWreDtGyQ935KDfRdXvQc38pbQdXKqY40V/bwa4ec
X-Sonic-ID: C;hBzMsgrq5BGgZIY+Bvepxg== M;ZgXjsgrq5BGgZIY+Bvepxg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1xicvC2kflvrSm1eR9DEnVb2hl0>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
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: Thu, 23 Apr 2015 22:47:38 -0000

On 4/22/15 7:19 AM, Lorenzo Colitti wrote:
>
>         Perhaps the issue here is that we don't agree on a problem
>         statement, or more accurately, what we're trying to accomplish
>         with this drafts.
>
>
>     You've said that for > 2 years now, but never provided any useful
>     suggestions.
>
>
> But it's impossible for me, or anyone else, to provide a useful 
> suggestion without a problem statement.
Lorenzo,

I hope you are seeing that you are going in circles. You ask for a 
problem statement, and when I point you at one (such as the Goals 
section in this draft), you say it is insufficient for what you think it 
should say. When I ask what you want it to include you say it is 
impossible for you to help since an acceptable (to you) problem 
statement isn't written yet.


I think the fundamental difference in opinion between you and me on this 
subject is that you don't care of communities that work on hosts that 
sleep on schedule end up doing whatever they want to IPv6 Neighbor 
Discovery (at least you have said at the mike that you don't care about 
those types of devices - and that they can go to some other WG). Thus 
time and again you dismiss any arguments relating to such hosts. Such an 
attitude is likely to cause fragmentation of the protocols and 
implementations for IPv6.

I really really really want to avoid fragmenting IPv6 and ND into 
different protocols for different types of devices. I think such 
fragmentation is harmful to IPv6 and its application across a large set 
of networks and devices - many of which do not yet use IP technology.

I hope there are others in the IPv6 working group that care about 
avoiding fragmentation while applying IPv6 to different IoT devices and 
other constrained devices, and the call for WG adoption of this draft 
seem to already have half a dozen supporters. That is promising to those 
of us that want to avoid fragmentation.

Regards,
    Erik