IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Wed, 23 October 2019 14:36 UTC

Return-Path: <bob.hinden@gmail.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 4B7F6120822; Wed, 23 Oct 2019 07:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 c5wKD6cfJeuc; Wed, 23 Oct 2019 07:36:49 -0700 (PDT)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (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 101691200E6; Wed, 23 Oct 2019 07:36:49 -0700 (PDT)
Received: by mail-wm1-x32d.google.com with SMTP id q70so14354782wme.1; Wed, 23 Oct 2019 07:36:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=faEgkSw7c21w1d+z25oLdRdXwmRluswKKdoPOKqxk0U=; b=rue1Sk01ohpS7JOh7pEojjy+FC8yjSz3yLKLOy7J4MXUA8wb7STsFsp6rgSyfy2gl8 1jmZv8v8M3+KIfVoENXw1hooKH4FScemf+u+kKWyiZTwyEdFCHTU7Yz85KhrJ08aDuAq 3X+gdJdkh7dYPpQ4dAMgpVKe4/dBH/oX8KHWRl+qVslob7bnDDa+oXSeVDfke2m+/4N4 bPxtFS4+JDrMZdl9NWXxab6JYQDPGg4AkLcGz91Ra6hGRSwUUcJ0eVjHWtd/yVHKDX2m 6QtTueGK6xxKqp14KgkkFovrYc7iBZp5v4zkscUFSvQLBwtqwX0MippaVVMXe8i+10Bf Typw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=faEgkSw7c21w1d+z25oLdRdXwmRluswKKdoPOKqxk0U=; b=GomJJcgQm0G2HePQ7AhNl1QotqKLZY+ZUH9Um/VvytbNc1krwpvG5Zk91i2DnRDozO bvkbIOm2d5VmWZRC3crMJUc5G+hWC+uc9z2HOy/CHaIB2NxZfndpPLViQGEyGXTK4i6p bH3KKcB1X3VRLVgFMsXRZcLHC3EuL5rMINTMyx+hCawRt0tZNpCPdc3Uj3QXs1fdVX/a xlhNZnoc1MedHnrzlFv+6sHOsiU1LOGqAEtBOm7W5oiKHCFHHd2aDDCGyWnUOprVRrE+ FdjxsjJb74scYw/sEFRJXhpGZcFImVCFrvMP9XrU5Zvgjx6w8G9IccbNHD3n+forQwrV /gXw==
X-Gm-Message-State: APjAAAVbHCBe6v6UlWo/xDO0nQoP5d/ml/RYPLZbWY5dFcNcdTLTXVyW 4JgyDB1J+ATRTlMAE2n3J4I=
X-Google-Smtp-Source: APXvYqwG+XBkGlzFWhs2utKcRmB7xSqeJVK7sYxtmtnJLzjihCbxfZsyKExX3cp+IDcC8w61djrMsw==
X-Received: by 2002:a1c:1d41:: with SMTP id d62mr252253wmd.32.1571841407567; Wed, 23 Oct 2019 07:36:47 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:d953:ae:7b28:8326? ([2601:647:5a00:ef0b:d953:ae:7b28:8326]) by smtp.gmail.com with ESMTPSA id b7sm7314303wrn.53.2019.10.23.07.36.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Oct 2019 07:36:46 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <A8B171FC-77AB-49F7-9A8A-620B5671560D@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BAA06202-27AD-4D23-B5D5-B617CEA86FD4"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 23 Oct 2019 07:36:42 -0700
In-Reply-To: <CA+RyBmW+XgBaYvOnKzfYiN63=JSf9Ckpe4Ga9oZtmdK+weppTQ@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, draft-ietf-intarea-gue@ietf.org, int-area <int-area@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
References: <CA+RyBmW+XgBaYvOnKzfYiN63=JSf9Ckpe4Ga9oZtmdK+weppTQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/TOL7PLgCalPWlVHZQ2xyXdGBtyU>
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 14:36:51 -0000

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

v2.23.0 | Report a Bug | By Email