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

Hi Mark,

We no longer want to reserve it for single token use and instead want to register five values: read-uncommitted, read-committed, repeatable-read, snapshot, and serializable.

Thanks
Ralf

-----Original Message-----
From: Mark Nottingham <mnot@mnot.net> 
Sent: Freitag, 7. Dezember 2018 01:58
To: Chet Ensign <chet.ensign@oasis-open.org>
Cc: ietf-message-headers@ietf.org; Handl, Ralf <ralf.handl@sap.com>
Subject: Re: [Ietf-message-headers] Updates to registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version

Chet,

Can you speak to why the request is still for "Isolation", instead of "OData-Isolation"?

Cheers,

> On 7 Dec 2018, at 5:05 am, Chet Ensign <chet.ensign@oasis-open.org> wrote:
> 
> This message contains an update to the registration request submitted on August 29 2018 in https://www.ietf.org/mail-archive/web/ietf-message-headers/current/msg00195.html
> 
> In response to this request, on August 29, in https://www.ietf.org/mail-archive/web/ietf-message-headers/current/msg00196.html, Ted Hardie wrote: 
> 
> ---
> 
> I'm a little confused on one point.  The Isolation header states that it was called OData-Isolation in version 4.0, but the linked ABNF document says:
> 
> isolation  = [ "OData-" ] "Isolation" ":" OWS "snapshot"
> 
> That seems to indicate that both ODate-Isolation and Isolation are expected to be valid for this token.  The ABNF for EntityID is similar:
> 
> entityid   = [ "OData-" ] "EntityID" ":" OWS IRI-in-header
> 
> Can you clarify the intent here?  Are both expressions of this token expected to continue?
> 
> In general, "Isolation" seems to be a very general concept, and the reservation of it, unadorned, for a single token use ("snapshot") is somewhat surprising compared to the more-obviously scoped OData-isolation.  EntityID seems similar board in possible usage outside the OData specification.  
> 
> ---
> 
> In response, the TC renamed EntityId header to OData-EntityId and added additional values for the Isolation header to align with most database systems. 
> 
> 
> On August 30, in https://www.ietf.org/mail-archive/web/ietf-message-headers/current/msg00197.html, Mark Nottingham wrote: 
> 
> --- 
> 
> "Applicable protocol" should be "http", I think.
> 
> --- 
> 
> In response, the TC changed the Applicable protocol to http. 
> 
> Below, please find the revised request. I have included the prior values in [ ]s so that all the changes are visible. 
> 
> Please let us know if this addresses your comments and if you have any other questions or concerns. 
> 
> ---
> 
> Open Data (OData) Protocol IANA Header registration request
> 28-Nov-2018
> 
> 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  [WAS EntityID]
> Isolation
> OData-MaxVersion
> OData-Version
> 
> The details as required by RFC 3864 for these headers are listed below
> 	
> 
> ####
> Header field name:
> 	OData-EntityId  [WAS EntityID]
> 
> Applicable protocol:
> 	http   [WAS OASIS Open Data Protocol (OData)]
> 
> 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_HeaderEntityIdODataEntityId	   
> 
> Related information:
> 	
>     None  [WAS The EntityId header was named OData-EntityId in OData version 4.0.]
> 
> 
> ####
> Header field name:
> 	Isolation
> 
> Applicable protocol:
> 	http   [WAS OASIS Open Data Protocol (OData)]
> 
> 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:
> 	
> 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.   
>    [WAS The Isolation header was named OData-Isolation in OData version 4.0.]
> 
> 
> ####
> Header field name:
> 	OData-MaxVersion
> 
> Applicable protocol:
> 	http   [WAS OASIS Open Data Protocol (OData)]
> 
> 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   [WAS OASIS Open Data Protocol (OData)]
> 
> 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
> 
> Primary: +1 973-996-2298
> Mobile: +1 201-341-1393 
> _______________________________________________
> Ietf-message-headers mailing list
> Ietf-message-headers@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-message-headers

--
Mark Nottingham   https://www.mnot.net/