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

Jim Schaad <ietf@augustcellars.com> wrote:
    > That sounds like a good plan forward. Are you also going to need an early
    > registration on the multipart-core draft as well?

yes, it would be nice, ... we think that it's CORE's problem to adopt the
draft and ask for that.

The multipart response is only need for systems where the private key will be
generated on the EST server: and a number of implementers are keen *not* to
do that, so the multipart is not urgent to as many people.

    > From: Peter van der Stok <stokcons@bbhmail.nl>
    > Sent: Wednesday, June 20, 2018 3:07 AM
    > To: Carsten Bormann <cabo@tzi.org>
    > Cc: Hannes Tschofenig <Hannes.Tschofenig@arm.com>; core <core@ietf.org>;
    > ace@ietf.org; Jim Schaad <ietf@augustcellars.com>; rdd@cert.org
    > Subject: Re: [core] [Ace] Early media-type registration for EST over CoAP

    > HI Carsten, Jim

    > Just to get this clear.

    > We will update the the est-coaps draft by referring to
    > draft-fossati-core-multipart-ct-05 for the wanted early registration of the
    > content formats specified in est-coaps.
    > Once done, we direct a request for early registration of the content-format
    > values to the ACE chairs.
    > Although the corresponding media formats have not been allocated yet for
    > multipart-ct draft, the corresponding content-format numbers can be allocated
    > already.

    > Is that the approved plan?

    > Please confirm or specify the conditions on multipart-ct draft.

    > Many thanks for your understanding,

    > Peter

    > Carsten Bormann schreef op 2018-06-19 14:22:

    > 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

    > _______________________________________________
    > core mailing list
    > core@ietf.org
    > https://www.ietf.org/mailman/listinfo/core

    > ----------------------------------------------------
    > Alternatives:

    > ----------------------------------------------------
    > _______________________________________________
    > Ace mailing list
    > Ace@ietf.org
    > https://www.ietf.org/mailman/listinfo/ace

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

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

Attachment: signature.asc