Re: [Ietf-message-headers] Updates to registration request for OData-EntityId, OData-Isolation, OData-MaxVersion, and OData-Version

[Chet Ensign <[e-mail]>]

Many thanks to all who reviewed the notice for message headers whose most
recent post of August 23, 2019 is linked below [1].

We have not heard further comment resulting from the community review, so
we plan to formally make the registration requests to IANA in one week
(2019-09-17).

Please let us know if there are any other steps we should take.

[1]  subject: Updates to registration request for OData-EntityId,
OData-Isolation, OData-MaxVersion, and OData-Version
https://mailarchive.ietf.org/arch/msg/ietf-message-headers/jf0XDAqbz2PE3MPcV1dRl6ROE4U

On Fri, Aug 23, 2019 at 5:55 PM Chet Ensign <[e-mail]>
wrote:

> This message contains an update to the registration request submitted on
> 06 December 2018 in
> https://mailarchive.ietf.org/arch/msg/ietf-message-headers/oRU8ChCoUXV-DU5Vh6PAxKF9NZs
>
> In response to the feedback received, the OData Technical Committee
> updated the registration documents to include the OData prefix in the
> Header and Preference names as suggested.
>
> Below, please find the revised request. I have included the prior values
> in [ ]s so that all the changes are visible.
>
> ---
>
> Open Data (OData) Protocol IANA Header registration request
> 22-Jul-2019
> ------------------------------------------------------------
>
> This documentation contains the information needed for Permanent
> Registration of the OData specific request headers with IANA as called out
> in RFC 3864 - Registration Procedures for Message Header Fields.
>
> The OData headers to be registered as Permanent Headers are
>
> OData-EntityId
> [OData-]Isolation  [was Isolation]
> OData-MaxVersion
> OData-Version
>
> The details as required by RFC 3864 for these headers are listed below.
>
> ####
> Header field name:
> OData-EntityId
>
> Applicable protocol:
> HTTP
>
> Status:
> Standard
>
> Author/Change controller:
> OASIS
>
> Specification document(s):
> OData Version 4.01 Part 1: Protocol -
>
> http://docs.oasis-open.org/odata/odata/v4.01/csprd05/part1-protocol/odata-v4.01-csprd05-part1-protocol.html#_Toc14172735
>
>
> Related information:
> <None>
>
> ####
> Header field name:
> [OData-]Isolation  [was Isolation]
>
> Applicable protocol:
> HTTP
>
> Status:
> Standard
>
> Author/Change controller:
> OASIS
>
> Specification document(s):
> OData Version 4.01 Part 1: Protocol -
>
> http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_HeaderIsolationODataIsolation
>
> Related information:
> <none>
> [was "The Isolation header was named OData-Isolation in OData version
> 4.0.  The OData Protocol document referenced above defines one valid value,
> snapshot.  To make this header useful to applications other than OData this
> registration also defines the values read-uncommitted, read-committed,
> repeatable-read and serializable.  These correspond to the standard
> transaction isolation levels exposed by most database systems.]
>
> ####
> Header field name:
> OData-MaxVersion
>
> Applicable protocol:
> HTTP
>
> Status:
> Standard
>
> Author/Change controller:
> OASIS
>
> Specification document(s):
> OData Version 4.01 Part 1: Protocol -
>
> http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_HeaderODataMaxVersion
>
>
> Related information:
> <none>
>
> ####
> Header field name:
> OData-Version
>
> Applicable protocol:
> HTTP
>
> Status:
> Standard
>
> Author/Change controller:
> OASIS
>
> Specification document(s):
> OData Version 4.01 Part 1: Protocol -
>
> http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_HeaderODataVersion
>
>
> Related information:
> <none>
> --
>
> /chet
> ----------------
> Chet Ensign
> Chief Technical Community Steward
> OASIS: Advancing open standards for the information society
> http://www.oasis-open.org
>
> Mobile: [phone]
>


-- 

/chet
----------------
Chet Ensign
Chief Technical Community Steward
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Mobile: [phone]