Re: [Ace] [core] Early media-type registration for EST over CoAP

Carsten Bormann <cabo@tzi.org> Tue, 19 June 2018 12:22 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75EBC130EA3; Tue, 19 Jun 2018 05:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 3-XqzmORSyZJ; Tue, 19 Jun 2018 05:22:46 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2CF7130E95; Tue, 19 Jun 2018 05:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w5JCMfBQ002853; Tue, 19 Jun 2018 14:22:41 +0200 (CEST)
Received: from client-0101.vpn.uni-bremen.de (client-0101.vpn.uni-bremen.de [134.102.107.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4196YF31dzzDWp6; Tue, 19 Jun 2018 14:22:41 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7198364E-F831-423F-8709-D96E152FD888@tzi.org>
Date: Tue, 19 Jun 2018 14:22:40 +0200
Cc: core <core@ietf.org>, "ace@ietf.org" <ace@ietf.org>
X-Mao-Original-Outgoing-Id: 551103759.141158-68dcec812618ae55160340b2631910a4
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC768859-DE02-4A2D-A12A-4806AD049713@tzi.org>
References: <VI1PR0801MB21122FFD4F19026259ABDF55FA930@VI1PR0801MB2112.eurprd08.prod.outlook.com> <FA41AB9E-7889-435E-A7DD-C13D2B04B3A2@tzi.org> <VI1PR0801MB21127A24E099B6337A9048D5FA920@VI1PR0801MB2112.eurprd08.prod.outlook.com> <0158C0A6-C8D5-4F19-9C12-23BDC8A7768A@tzi.org> <8976A481-6467-4DAD-A5ED-9AE05E9CC62D@tzi.org> <VI1PR0801MB21122EB265DF70E45C26BC80FA6A0@VI1PR0801MB2112.eurprd08.prod.outlook.com> <7952F818-15C7-4151-8A98-936A6250F5FB@tzi.org> <e9731b91e07cc2c450c024dae1f67b48@xs4all.nl> <VI1PR0801MB2112A35CE1169B1922B1BB9AFA700@VI1PR0801MB2112.eurprd08.prod.outlook.com> <7198364E-F831-423F-8709-D96E152FD888@tzi.org>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/3Er6AvqJqePop5MpKjM8bE76lVM>
Subject: Re: [Ace] [core] Early media-type registration for EST over CoAP
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2018 12:22:48 -0000

On Jun 19, 2018, at 14:11, Carsten Bormann <cabo@tzi.org> wrote:
> 
> Since the registry that we are registering into does not fulfill the preconditions of RFC 7120 Section 2 point (a),

(Sorry, wasn’t awake enough.  If we go for the 256-9999 space, of course it does.  And we probably do.)

So we’ll have to follow the process according to Section 3 of RFC 7120.

Starting with point (1) of Section 3.1:

   1.  The authors (editors) of the document submit a request for early
       allocation to the Working Group chairs, specifying which code
       points require early allocation and to which document they should
       be assigned.

Grüße, Carsten