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

[Mark Biamonte <[e-mail]>]

Hi Ted,

I am a member of the OData Technical Committee (TC).  Chet submitted the request for OASIS on behalf of the OData TC.  You are correct, in OData 4.0 the Headers were titled OData-Isolation and OData-EntityID.  In the latest OData 4.01 spec the header name was changed to just Isolation and EntityID.  The OData- prefixed versions are still supported for backwards compatibility.  This change was made based on feedback for users and implementors of the OData standard.  I gather your preference would be that we use the OData-prefixed version for the registrations.  If so I will need to discuss that with the TC and get back to you.

Mark Biamonte
Progress Software
Morrisville, NC

---------- Forwarded message ----------
From: Ted Hardie <[e-mail]<mailto:[e-mail]>>
Date: Wed, Aug 29, 2018 at 2:58 PM
Subject: Re: [Ietf-message-headers] Registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version
To: Chet Ensign <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>, "Mark Biamonte (Progress)" <[e-mail]<mailto:[e-mail]>>

Hi Chet,

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.

regards,

Ted Hardie

On Wed, Aug 29, 2018 at 11:17 AM, Chet Ensign <[e-mail]<mailto:[e-mail]>> wrote:
This message contains the information needed for Permanent Registration of the OData specific request headers with IANA as covered in RFC 3864 - Registration Procedures for Message Header Fields.

---

PERMANENT MESSAGE HEADER FIELD REGISTRATION TEMPLATE:

Header field name:

EntityId

Applicable protocol:

OASIS Open Data Protocol (OData)

Status:

Standard

Author/Change controller:

OASIS. Michael Pizzo ([e-mail]<mailto:[e-mail]>), Microsoft primary specification editor. Mark Biamonte ([e-mail]<mailto:[e-mail]>), Progress Software editor for registration template.

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<http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol..html#sec_HeaderEntityIdODataEntityId>

Related information:
The EntityId header was named OData-EntityId in OData version 4.0.

####

Header field name:

Isolation

Applicable protocol:

OASIS Open Data Protocol (OData)

Status:

Standard

Author/Change controller:

OASIS. Michael Pizzo ([e-mail]<mailto:[e-mail]>), Microsoft primary specification editor. Mark Biamonte ([e-mail]<mailto:[e-mail]>), Progress Software editor for registration template.

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<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.


####

Header field name:

OData-MaxVersion

Applicable protocol:

OASIS Open Data Protocol (OData)

Status:

Standard

Author/Change controller:

OASIS. Michael Pizzo ([e-mail]<mailto:mikep@microsoft..com>), Microsoft primary specification editor. Mark Biamonte ([e-mail]<mailto:[e-mail]>), Progress Software editor for registration template.

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<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:

OASIS Open Data Protocol (OData)

Status:

Standard

Author/Change controller:

OASIS. Michael Pizzo ([e-mail]<mailto:[e-mail]>), Microsoft primary specification editor. Mark Biamonte ([e-mail]<mailto:[e-mail]>), Progress Software editor for registration template.

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<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<http://www.oasis-open.org>

Primary: [phone]
Mobile: [phone]

_______________________________________________
Ietf-message-headers mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/ietf-message-headers<https://www.ietf.org/mailman/listinfo/ietf-message-headers>




--

/chet
----------------

Looking forward to Borderless Cyber 2018<https://us18.borderlesscyber.org/en/>, 3-5 Oct, Washington, D.C.
Organized by The World Bank, OASIS, and Georgetown University

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

Primary: [phone]
Mobile: [phone]