Re: [tcpm] request for feedback - proposed update to draft-touch-tcpm-experimental-options

Brandon Williams <brandon.williams@akamai.com> Tue, 19 February 2013 17:55 UTC

Return-Path: <brandon.williams@akamai.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99C3B21F8D6A for <tcpm@ietfa.amsl.com>; Tue, 19 Feb 2013 09:55:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OT6HxLmVOCWR for <tcpm@ietfa.amsl.com>; Tue, 19 Feb 2013 09:55:15 -0800 (PST)
Received: from prod-mail-xrelay02.akamai.com (prod-mail-xrelay02.akamai.com [72.246.2.14]) by ietfa.amsl.com (Postfix) with ESMTP id 2D15E21F8C8D for <tcpm@ietf.org>; Tue, 19 Feb 2013 09:55:15 -0800 (PST)
Received: from prod-mail-xrelay02.akamai.com (localhost [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 933DD27C1A for <tcpm@ietf.org>; Tue, 19 Feb 2013 17:55:14 +0000 (GMT)
Received: from prod-mail-relay02.akamai.com (prod-mail-relay02.akamai.com [172.17.50.21]) by prod-mail-xrelay02.akamai.com (Postfix) with ESMTP id 812AF27C0E for <tcpm@ietf.org>; Tue, 19 Feb 2013 17:55:14 +0000 (GMT)
Received: from [0.0.0.0] (callahan.kendall.corp.akamai.com [172.17.12.11]) by prod-mail-relay02.akamai.com (Postfix) with ESMTP id 6E5E0FE18D for <tcpm@ietf.org>; Tue, 19 Feb 2013 17:55:14 +0000 (GMT)
Message-ID: <5123BC82.1010907@akamai.com>
Date: Tue, 19 Feb 2013 12:55:14 -0500
From: Brandon Williams <brandon.williams@akamai.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "tcpm@ietf.org" <tcpm@ietf.org>
References: <511E92E9.6080709@isi.edu> <51239189.2060504@akamai.com> <5123B50A.1050001@isi.edu> <5123B9A2.7000805@isi.edu>
In-Reply-To: <5123B9A2.7000805@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [tcpm] request for feedback - proposed update to draft-touch-tcpm-experimental-options
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 17:55:15 -0000

This looks good to me. I also like your suggestion (b).

--Brandon

On 02/19/2013 12:42 PM, Joe Touch wrote:
> PS - we could add the following:
>
> 	16 bits are assigned, but 32 SHOULD be used
>
> 	IANA registration will assign FCFS the first 16 bits,
> 	and record the second 16 bits if provided.
>
> That still leaves the question of squatters and/or collisions that
> request explicit registration.
>
> Clearly, IANA requests should help the applicant choose an unassigned
> codepoint rather than recording a collision. However, if they either
> refuse or didn't contact IANA (i.e., squatter), what should we ask IANA
> to do?
>
> This case comes up in the ports space. There are a few solutions:
>
> 	a) don't record or indicate collisions
> 		i.e., record only the IANA assignments
>
> 	b) record the existence of a collision, but no other info
> 		this helps users debug problems, but
> 		avoids implicit endorsement of squatter usage
>
> 	c) record the collision and all available info
> 		helps debugging the best, and allows
> 		the community to "assign blame", but
> 		might be taken as an implicit endorsement
> 		of squatter usage
>
> I'm in favor of (b) above.
>
> Joe
>
> On 2/19/2013 9:23 AM, Joe Touch wrote:
>>
>>
>> On 2/19/2013 6:51 AM, Brandon Williams wrote:
>>> On 02/15/2013 02:56 PM, Joe Touch wrote:
>>>> 1. do you agree with change (A)?
>>>
>>> Yes.
>>>
>>>>
>>>> 2. do you agree with change (B)?
>>>
>>> Yes, provided that "OK to indicate multiple assignees" means that the
>>> multiple assignees should all agree.
>>
>> So what if they don't?
>>
>> Or, more specifically, what if they:
>>
>>       - refuse
>>       - cannot be contacted
>>
>> Or should we just say that the IANA list is the 'first to file', and
>> don't really list anything else?
>>
>> Joe

-- 
Brandon Williams; Principal Software Engineer
Cloud Engineering; Akamai Technologies Inc.