Re: you have running code ... I-D Action: draft-ietf-6man-ipv6only-flag-03.txt

"Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Thu, 01 November 2018 15:51 UTC

Return-Path: <bzeeb-lists@lists.zabbadoz.net>
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 BAE0B1252B7 for <ipv6@ietfa.amsl.com>; Thu, 1 Nov 2018 08:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 UBrCb3gDDjtb for <ipv6@ietfa.amsl.com>; Thu, 1 Nov 2018 08:51:29 -0700 (PDT)
Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE04F124BAA for <ipv6@ietf.org>; Thu, 1 Nov 2018 08:51:28 -0700 (PDT)
Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 3E9A08D4A216; Thu, 1 Nov 2018 15:51:26 +0000 (UTC)
Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 1B0EFD1F89D; Thu, 1 Nov 2018 15:51:25 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sbone.de
Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id puGpRZWj16_Q; Thu, 1 Nov 2018 15:51:23 +0000 (UTC)
Received: from [146.179.201.71] (fresh-ayiya.sbone.de [IPv6:fde9:577b:c1a9:f001::2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 88704D1F89C; Thu, 1 Nov 2018 15:51:22 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: David Farmer <farmer@umn.edu>, 6man WG <ipv6@ietf.org>
Subject: Re: you have running code ... I-D Action: draft-ietf-6man-ipv6only-flag-03.txt
Date: Thu, 01 Nov 2018 15:51:22 +0000
X-Mailer: MailMate (2.0BETAr6125)
Message-ID: <9FCDA205-A6A9-4767-8C42-5D0E1E53F33A@lists.zabbadoz.net>
In-Reply-To: <105ad6b3-52a3-d0a3-0a02-b9a88b9d9e42@gmail.com>
References: <153973137181.9473.10666616544238076833@ietfa.amsl.com> <6264F7A1-59EB-467D-A576-E5F2F0DEE7DD@lists.zabbadoz.net> <CACWOCC-xL0PfkNHgCqhB28GE-jCWUUagQE4PukdpXK+YHgWpyg@mail.gmail.com> <CAO42Z2wfjggkBOaDJBzrYJUavWhJbcn8u9Na2ScK55eFFWLnDA@mail.gmail.com> <2c63c54f-b6ee-b12e-bd72-cc6165b64f21@gmail.com> <CAN-Dau3PSNiCN7cX9+ixmi84xpK2npAQ_mHvMeTtgtvTRaA3Ug@mail.gmail.com> <105ad6b3-52a3-d0a3-0a02-b9a88b9d9e42@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GxYg_fjnMVCQ_3O6r9S6zoJgin0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Nov 2018 15:51:31 -0000

On 31 Oct 2018, at 19:45, Brian E Carpenter wrote:

>>>>> What OS vendor will go next?
>>>>>
>>>>
>>>> IANA better allocate the bit first.
>>>
>>> Yes, that's an interesting chicken/egg issue since there is no
>>> designated experimental/local use bit. But hard to avoid if people
>>> want running code before Proposed Standard.
>>>
>>
>> Regardless if this document is published and any misgivings anyone 
>> has, I
>> think we need to have IANA allocate the code point to this purpose 
>> NOW!  We
>> asked to have running code, we now have some, it is extremely 
>> dangerous to
>> have code out in the wild without some level of an official 
>> designation of
>> the code point.
>>
>> I'm not sure of the procedure, but for all effective purposes if we 
>> expect
>> there to be more running code we had better officially designate the 
>> code
>> point.
>
> There is a procedure for requesting early allocation, and of course an 
> allocation
> can always be rescinded later. Whether there's any real practical risk 
> is a
> judgment call.

I’d suggest finalise the draft and get the RFC out and not complicate 
matters by diverting energy to sort the bit out.  If we sort the bit out 
it almost means that we want this draft to go out as an RFC, so get it 
out :-)


/bz