Re: [Int-area] GUE: IANA Considerations question

Tom Herbert <tom@herbertland.com> Wed, 23 October 2019 22:16 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E14EF120096 for <int-area@ietfa.amsl.com>; Wed, 23 Oct 2019 15:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 Q64EHXkKbe-O for <int-area@ietfa.amsl.com>; Wed, 23 Oct 2019 15:16:42 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 636341200D6 for <int-area@ietf.org>; Wed, 23 Oct 2019 15:16:42 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id l25so5763762edt.6 for <int-area@ietf.org>; Wed, 23 Oct 2019 15:16:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HA9B+YjBEmef16sCgUxOSVb9TmdLQV6Uy7st/PhgOQk=; b=HW96dy2YHcOKIhqCotNc2tYfU1b7/FSUmToiahbpa1Sc0Zwojlir1mWanOyV6rQHON lmjTEAmgtvxQ3X2Ge3ki/72XqZYv8WlZ+bJmxG85NzBeW7zJ6nFQB8K/QaFvlh7bEACD nc2T0gdD08lnVjkCF65Wpvrc3+a06P+7qbbzMyHosfMVsPrBW4MM2akTAPX94R+g3/r6 JdwkhT2Ylnsx5rWl8S7jXNKiVg6DWNvm/nLYJS3VDCqpf/uIpfxwz0lrNGVJ9O7aDPb2 dm4RV+ppIZEY69+E++9q/hsun9UV1IeKUSqdI6FBmE1EwnoZrJnppkFIoeCP73mADTHv aREQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HA9B+YjBEmef16sCgUxOSVb9TmdLQV6Uy7st/PhgOQk=; b=f24LcYBuus1/dWctbiX8wBLQI07CtWvOpQeQKvD50cYkrEGYWExhvw4PZeXVSfEjpN Xj1/ADiWxpqY6uWYM69qB5pjM8iafMKdVJ95Y1O4rzLZm5/3NnBemDFpodP5RN80673G RY7XYDobmMEfMBnPuUN2rNnG/3Ic4O1JlM8b0XcOVf9WrMM8L8M9v82dXy+IqsONObE5 o+csGnb9FL8YSDH0Rx0ei3uQaalAr3IGUZZgPHgkkQaq1xfhxnu/9S3bolgErcTXxq/5 xiN93vE3x71uNTfWSoyhrn/sJ/VipXiin2/FdVx+2fum+Q02zoP9rjAfc1/tjVMmUnKF hOIQ==
X-Gm-Message-State: APjAAAUivZ0wuarjh7fguvHhDsCAMZyO/lWZlT1eUXS9wFsi7D9+N/TQ OUu4rvQGo0OBLm6tpCa2GsQs84d91nAIQURhLuHQQA==
X-Google-Smtp-Source: APXvYqyRY1RWu90gI3lvSmljj9lr2QesY0OSE/xLK3wjcQXHcmFaqgweM8uoIe+7IaEaaS533bzA1rw3iDHGbcEkGlA=
X-Received: by 2002:a50:ed01:: with SMTP id j1mr40319487eds.111.1571869000774; Wed, 23 Oct 2019 15:16:40 -0700 (PDT)
MIME-Version: 1.0
References: <CA+RyBmW+XgBaYvOnKzfYiN63=JSf9Ckpe4Ga9oZtmdK+weppTQ@mail.gmail.com> <A8B171FC-77AB-49F7-9A8A-620B5671560D@gmail.com> <A4938F6F-39F4-4296-8A9C-30E17E12B173@strayalpha.com> <CA+RyBmVaYrqBpdogjZ+FB9uJoyhFm4pL117=o4gwhuCc35S6bg@mail.gmail.com>
In-Reply-To: <CA+RyBmVaYrqBpdogjZ+FB9uJoyhFm4pL117=o4gwhuCc35S6bg@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 23 Oct 2019 15:16:29 -0700
Message-ID: <CALx6S37QXt2+CMJnEQ=KPPi8nd_-o2c-JukCn3iKOYT4YWpyKQ@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: Joe Touch <touch@strayalpha.com>, Bob Hinden <bob.hinden@gmail.com>, int-area <int-area@ietf.org>, draft-ietf-intarea-gue@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006ccd0305959b4511"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/xUN2HMMD2gTAzhwwonYVmAYMhXY>
Subject: Re: [Int-area] GUE: IANA Considerations question
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2019 22:16:45 -0000

On Wed, Oct 23, 2019, 8:07 AM Greg Mirsky <gregimirsky@gmail.com> wrote:

> Hi Joe,
> I'll be happy with a single Experimental code point.
>

Okay. We can have one exp code point and define RFC6994 mechanism.

Tom


> Regards,
> Greg
>
> On Wed, Oct 23, 2019 at 10:50 AM Joe Touch <touch@strayalpha.com> wrote:
>
>> It would also be useful to understand why you think more than one code
>> point is needed for experiments (vs the RFC6994-style approach).
>>
>> Joe
>>
>> On Oct 23, 2019, at 7:36 AM, Bob Hinden <bob.hinden@gmail.com> wrote:
>>
>> Greg,
>>
>> On Oct 23, 2019, at 6:44 AM, Greg Mirsky <gregimirsky@gmail.com> wrote:
>>
>> Dear Authors, et al.,
>> I have a rather benign question the new registry requested in Section
>> 8.3. The draft states that the whole 1-127 range is "RFC required" per RFC
>> 5226. Firstly, a nit - RFC 5226 has been obsoleted by RFC 8126. My question
>> is Would you agree to split the 128-255 range and set First Come First
>> Served sub-range. For example:
>>
>>
>> Please explain why you are proposing this change.
>>
>> Thanks,
>> Bob
>>
>>
>>      +----------------+------------------+---------------+
>>      |  Control type  | Description      | Reference     |
>>      +----------------+------------------+---------------+
>>      | 0              | Control payload  | This document |
>>      |                | needs more       |               |
>>      |                | context for      |               |
>>      |                | interpretation   |               |
>>      |                |                  |               |
>>      | 1..127         | Unassigned       |               |
>>      |                |                  |               |
>>      | 128..250       | First Come       | RFC 8126      |
>>      |                | First Served     |               |
>>      | 251..254       | Experimental     | This document |
>>      |                |                  |               |
>>      | 255            | Reserved         | This document |
>>      |                |                  |               |
>>      +----------------+------------------+---------------+
>>
>> Also, you may consider updating 0 as Reserved and assigning 1 as Control
>> payload ...
>> Much appreciate your consideration.
>>
>> Regards,
>> Greg
>>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
>>
>>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
>>
>>
>>