IETF Logo Mail Archive

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

<mohamed.boucadair@orange.com> Thu, 24 October 2019 05:48 UTC

Return-Path: <mohamed.boucadair@orange.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 71E961207FE; Wed, 23 Oct 2019 22:48:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 QxxLRVdKhjoS; Wed, 23 Oct 2019 22:48:32 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 359ED12000F; Wed, 23 Oct 2019 22:48:32 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 46zGWL736MzBrk2; Thu, 24 Oct 2019 07:48:30 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.70]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 46zGWL63qQz2xCG; Thu, 24 Oct 2019 07:48:30 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM33.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Thu, 24 Oct 2019 07:48:30 +0200
From: mohamed.boucadair@orange.com
To: Tom Herbert <tom@herbertland.com>
CC: int-area <int-area@ietf.org>, "draft-ietf-intarea-gue@ietf.org" <draft-ietf-intarea-gue@ietf.org>
Thread-Topic: [Int-area] GUE: IANA Considerations question
Thread-Index: AQHVie+TvtY9wm7qIUyuYOuMBqrUC6dpRb0A
Date: Thu, 24 Oct 2019 05:48:29 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933031344E05@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
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> <CALx6S37QXt2+CMJnEQ=KPPi8nd_-o2c-JukCn3iKOYT4YWpyKQ@mail.gmail.com>
In-Reply-To: <CALx6S37QXt2+CMJnEQ=KPPi8nd_-o2c-JukCn3iKOYT4YWpyKQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933031344E05OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/8EURSU2uWZ1euqMaIlEpHjJTLto>
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: Thu, 24 Oct 2019 05:48:34 -0000

Tom,

Now that you are on the IANA considerations, I would appreciate if you can consider updating it to request a codepoint from the tunnel registry  available at: https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-6. More rationale can be found in RFC-to-be-8675 (draft-ietf-softwire-iftunnel).

Registration guidelines are available at: https://tools.ietf.org/html/draft-thaler-iftype-reg.

Cheers,
Med

De : Int-area [mailto:int-area-bounces@ietf.org] De la part de Tom Herbert
Envoyé : jeudi 24 octobre 2019 00:16
À : Greg Mirsky
Cc : int-area; draft-ietf-intarea-gue@ietf.org
Objet : Re: [Int-area] GUE: IANA Considerations question


On Wed, Oct 23, 2019, 8:07 AM Greg Mirsky <gregimirsky@gmail.com<mailto: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<mailto: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<mailto:bob.hinden@gmail.com>> wrote:

Greg,


On Oct 23, 2019, at 6:44 AM, Greg Mirsky <gregimirsky@gmail.com<mailto: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<mailto:Int-area@ietf.org>
https://www.ietf.org/mailman/listinfo/int-area

_______________________________________________
Int-area mailing list
Int-area@ietf.org<mailto:Int-area@ietf.org>
https://www.ietf.org/mailman/listinfo/int-area

v2.23.0 | Report a Bug | By Email