early allocation

[thomas-fossati]

Conditions for requesting early allocation -- see also §2 of RFC7120:

• [x] The code points must be from a space designated as "RFC Required", "IETF Review", or "Standards Action". Additionally, requests for early assignment of code points from a "Specification Required" registry are allowed if the specification will be published as an RFC.

Per Section 3.1 of [RFC6838], Standards Tree requests made through IETF documents will be reviewed and approved by the IESG.

• [x] The format, semantics, processing, and other rules related to handling the protocol entities defined by the code points (henceforth called "specifications") must be adequately described in an Internet-Draft.

draft-ietf-rats-eat-media-type is that Internet-Draft

• [x] The specifications of these code points must be stable; i.e., if there is a change, implementations based on the earlier and later specifications must be seamlessly interoperable.

we think they are stable

• [ ] The Working Group chairs and Area Directors (ADs) judge that there is sufficient interest in the community for early (pre-RFC) implementation and deployment, or that failure to make an early allocation might lead to contention for the code point in the field.

this we should ask

[thomas-fossati]

• [ ] The Working Group chairs and Area Directors (ADs) judge that there is sufficient interest in the community for early (pre-RFC) implementation and deployment, or that failure to make an early allocation might lead to contention for the code point in the field.

this we should ask

This we asked at IETF 115. The relevant record from the minutes:

** 16:50 - 16:55**
EAT Media Types
Open Issue#12 - Early Allocation
[NC] Need to check with other chairs.
[Roman] Needs to be put on mailing list for thorough review.

It seems like the action is stuck with the chairs.

[henkbirkholz]

Overtaken by events, will sync with EAT.