Re: Mirja Kühlewind's Discuss on draft-ietf-6man-rfc2460bis-09: (with DISCUSS and COMMENT)

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 21 April 2017 23:34 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 303AF128B93; Fri, 21 Apr 2017 16:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 RVZl_Zxhvfa3; Fri, 21 Apr 2017 16:34:30 -0700 (PDT)
Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6064120046; Fri, 21 Apr 2017 16:34:30 -0700 (PDT)
Received: by mail-it0-x241.google.com with SMTP id z67so926946itb.0; Fri, 21 Apr 2017 16:34:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=v3DOz3B2W5rloTYwkiZUCiw/g+M+/CJwyy5JJgRIQqY=; b=T2Zl73aax0nvh23g66hLjSY9NGipvlA2OdpsSBESh/rOeTQaMJXdf0SK9cObL85PFy wL6TM2Fo0CYJ0h70UyLoAYo6P3ZYar7TBtBW8K3+4Z89Kxd0r97C6nVowB/42LgSRrTe VkxXOqXFn53GvcdK6HZMlSKlUEQOHAxSRarF9CXgaxckjvrosGXcCHEOB1fqXWwfZIEN XB1gOhntPonwo6uKJtCS5EP5mqTV147wWGHrDkB85kWbA94ev/qJj7ZrvLJb7wQePEUa wtGz3ZymSeA0LNDWguDrSkM9bm6fjgK0CKN5YrHWQ/4F15Of9VHokyrgWrlnhqO4W/Wl Lqmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=v3DOz3B2W5rloTYwkiZUCiw/g+M+/CJwyy5JJgRIQqY=; b=jhcoPl8WNc3Ns2UYk9QAwjDrt15dVzwSTVZTEi5Hs8GkQSPZuewtl53nGxkr46hDLL eX7PdvLtyTQtlGXUFzrojqjAtebmt0msHScI1pWWwInoKbGgwQsILJxGranV20MOWWS/ 3zHi68IdvFPWIGDyq2jQvI0fDi1IaSHIVfFPVoQUz9tAXgqtejYKLyqpFw0m3lqzGBmd 3QtA0B7cUSAjl+iM0IfSYhir9XwoLSGLAQ2qFazVIRpVcnecCjwJmI9w8oypeiCR8g8h qbLWFn5dV0deSmCn5Xcb3mNfOgHL3jOhcw6yGDju6YDxBzRl12Cnpc7thkvej7jDK+Iy MeNQ==
X-Gm-Message-State: AN3rC/452IdUdYWkitlRHk0SqqT5aWKfU/Ccuq5JsMV20eVf9pN80KZp GVtA2QABjzn1fA==
X-Received: by 10.99.115.90 with SMTP id d26mr7375539pgn.101.1492817669880; Fri, 21 Apr 2017 16:34:29 -0700 (PDT)
Received: from ?IPv6:2406:e007:58b4:1:28cc:dc4c:9703:6781? ([2406:e007:58b4:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id w5sm6002084pfd.23.2017.04.21.16.34.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Apr 2017 16:34:28 -0700 (PDT)
Subject: Re: Mirja Kühlewind's Discuss on draft-ietf-6man-rfc2460bis-09: (with DISCUSS and COMMENT)
To: Robert Raszuk <robert@raszuk.net>, otroan@employees.org
References: <149201127005.15808.3277140025315157500.idtracker@ietfa.amsl.com> <4AE56E75-78D4-43EA-8118-8195FD8A3D08@kuehlewind.net> <4fc2ef36-cd17-58f1-8089-a5645f08ad45@gmail.com> <D7EE44C3-04DB-4CFD-836F-2BFA74A35268@employees.org> <90DFC565-B4E7-45E2-BE6A-0B67895E87F8@gmail.com> <CA+MHpBr7aeuyd8h5n6U6Q4jD_gtLCKsPJUgQqQuhgkEE3DGwqg@mail.gmail.com> <D41A10C3-74D4-45EE-8161-C344CB30329A@kuehlewind.net> <5E28EF66-7BE1-4F11-88F3-6D928870A9FE@kuehlewind.net> <616cb74d-cc15-6c26-cb1d-612dfcddd353@gmail.com> <99E119A3-4BEA-4EE4-9DC1-7B434CAAE016@kuehlewind.net> <8EF4BCDA-ADB9-4EF4-A873-95CA67C6D7F3@employees.org> <8d127de1-a1b6-8406-c234-192fcbf01ad4@si6networks.com> <65C701D2-A0FF-40E5-B88D-E2E9C7260E02@gmail.com> <f7c19564-ea23-dac4-920c-d05a3c7d0cd9@si6networks.com> <CA+b+ERkHjv=w8g1R4LDVB-+kD=dVCVgtVu_D53oAqkOPFAzDkQ@mail.gmail.com> <E2595B09-575D-49AE-92B2-0064B82772F9@employees.org> <CA+b+ERkPYQMJdUdyW+69MXLy6kVn_d==8iZ9mSF5hSCVtyb6aw@mail.gmail.com>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, IESG <iesg@ietf.org>, Fernando Gont <fgont@si6networks.com>, 6man-chairs@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <60bf60a7-269b-03c2-21c2-a00d85a2c3c4@gmail.com>
Date: Sat, 22 Apr 2017 11:34:34 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CA+b+ERkPYQMJdUdyW+69MXLy6kVn_d==8iZ9mSF5hSCVtyb6aw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aUdHV0FsiZlxfDAC7DyTJCNwzfQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 21 Apr 2017 23:34:32 -0000

On 22/04/2017 08:09, Robert Raszuk wrote:
> ​Hi Ole,​
> 
> 
>> That does in no way stop anyone from proposing _new_ work. Of any sort.
>>
>> Best regards,
>> Ole
>>
> 
> ​Very true ! Anyone can propose anything in IETF.
> 
> But with the text additions which I have seen here recently the bar to move
> from individual's draft proposal to WG doc then via all LCs to Standards
> Track RFC just went up significantly higher especially for SRH and EH
> elements. ​
> 
> And that's my point.

But *our* point, for some definition of 'our', is that by making the
Internet-wide situation clear, we are in fact clearing the way for careful
definition of local-use mechanisms. At the moment, as we've clearly seen
from discussion of the SRH, we simply can't have that discussion because
of the unfortunate ambiguity of RFC1883 and RFC2460. Truly, the quicker
we get that settled and approved by the IESG, the quicker we can look
seriously at draft-voyer-6man-extension-header-insertion.

You might ask yourself why no IPv4 options have been defined since 2007
(Quick Start) and before that, 1997 (Router Alert). The same reason: they
don't survive a trip across the Internet.

    Brian