From nobody Thu Dec 6 10:05:29 2018 Return-Path: X-Original-To: ietf-message-headers@ietfa.amsl.com Delivered-To: ietf-message-headers@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96093130EF3 for ; Thu, 6 Dec 2018 10:05:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.358 X-Spam-Level: X-Spam-Status: No, score=-3.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oasis-open-org.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0mdPkYgvY9D for ; Thu, 6 Dec 2018 10:05:22 -0800 (PST) Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8266130EE1 for ; Thu, 6 Dec 2018 10:05:21 -0800 (PST) Received: by mail-ed1-x52e.google.com with SMTP id f23so1543729edb.3 for ; Thu, 06 Dec 2018 10:05:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oasis-open-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=LjY+T/q8elTNnKJFzCMxQoq12dCi744GSbUTb0MFtA8=; b=jMdo+zinbltBeDmXc2w48cQca8FxPbsnYNtrz9rj+A7ackqes+WMlvE80nOPPgZxnu ALr2CSmbRdVhOGHJGhv5MM00BKwaacVV8OBCKDvIxDWRKNI7kZUQrK6e6qXG6cfNmKLV ZU72hccSUQP6DiX72WCWjQA1q+WqsylLBUJ2kv/IROYDHqtRn+JjPbiJK0IYmZqzu24o vG0oe2vvgxvatDzNlAzFJLCAJXsvjH/8M2IVpnfwfHJdSM0sVPZKx0VEDQaQVRrltMCR kIkPluRU+eA4e03CMJC8PYb9CF6y58PQltcSh5vblSPdkXZEZ40UrgMaKT8V08rwHzLE xAeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=LjY+T/q8elTNnKJFzCMxQoq12dCi744GSbUTb0MFtA8=; b=lU5H9JXccrZO1whytDnSQCygr+H5EWOqU+WiKjH4RIIMJjAZaUvNWKVsVyBCOVftSr BCwqdwp4GEy6rLkZjnEUnw5B85SiE1sbRfOY9TwQ3D2omc8SVStJUwzxznudqIqBIX8g Wb6zpMLaFFa3b82ZsefG3M9d+UqXQzoJOf6lyLHJ9pbOKZAhD/VhKTTTAJh7k4cdeDPL AF3YIakwPFaeD+FIYAbA7DKIbnXlEa5PY9cOfT78HpU6rusdKB43+FxOspo3koQY5qBg laDbcjsc5m1WGRd3VCz0maw6FF011KEmoSI79KbtnaVnKBWGrq17B0TyGgblCRJb5TTc 8W8Q== X-Gm-Message-State: AA+aEWZfjB/GD0SlGa8cQwsdF5kPRf0magAcCnt93wDVapskew9/fiG/ CQHiYDSj7Rk0s6fY+O1vIhYwG4wMKYjeAi6DLfyYOFI7fg== X-Google-Smtp-Source: AFSGD/X3ylNqhfCL3TwnEw6mFKjM1cpGJEnWOQMe1PkG0Kuq7nLu7N8tr1h5pBxuExTcUzEPJBC6yA+8Di2MxmjedIo= X-Received: by 2002:a50:89e1:: with SMTP id h30mr26100701edh.28.1544119519527; Thu, 06 Dec 2018 10:05:19 -0800 (PST) MIME-Version: 1.0 From: Chet Ensign Date: Thu, 6 Dec 2018 13:05:08 -0500 Message-ID: To: ietf-message-headers@ietf.org Cc: "Mark Biamonte (Progress)" , "Ralf Handl (SAP)" Content-Type: multipart/alternative; boundary="00000000000073ddd4057c5e57ea" Archived-At: Subject: [Ietf-message-headers] Updates to registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version X-BeenThere: ietf-message-headers@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion list for header fields used in Internet messaging applications." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Dec 2018 18:05:28 -0000 --00000000000073ddd4057c5e57ea Content-Type: text/plain; charset="UTF-8" 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: #### 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: -- /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 --00000000000073ddd4057c5e57ea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This message contains an update to t= he registration request submitted on August 29 2018 in ht= tps://www.ietf.org/mail-archive/web/ietf-message-headers/current/msg00195.h= tml

In response to this request, on August= 29, in https://www.ietf.org/mail-archive/web/ietf-messag= e-headers/current/msg00196.html, Ted Hardie wrote:=C2=A0

=
---

I'm a little confused on one po= int.=C2=A0 The Isolation header states that it was called OData-Isolation i= n version 4.0, but the linked ABNF document says:

= isolation=C2=A0 =3D [ "OData-" ] "Isolation" ":&qu= ot; OWS "snapshot"

That seems to indicat= e that both ODate-Isolation and Isolation are expected to be valid for this= token.=C2=A0 The ABNF for EntityID is similar:

en= tityid=C2=A0 =C2=A0=3D [ "OData-" ] "EntityID" ":&= quot; OWS IRI-in-header

Can you clarify the intent= here?=C2=A0 Are both expressions of this token expected to continue?
=

In general, "Isolation" seems to be a very ge= neral concept, and the reservation of it, unadorned, for a single token use= ("snapshot") is somewhat surprising compared to the more-obvious= ly scoped OData-isolation.=C2=A0 EntityID seems similar board in possible u= sage outside the OData specification.=C2=A0=C2=A0

= ---

In response, the TC renamed EntityId header to= OData-EntityId and added additional values for the Isolation header to ali= gn with most database systems.=C2=A0


On August 30, in https://www.ietf.org/mail-archive/web/= ietf-message-headers/current/msg00197.html, Mark Nottingham wrote:=C2= =A0

---=C2=A0

"Appli= cable protocol" should be "http", I think.

---=C2=A0

In response, the TC changed the = Applicable protocol to http.=C2=A0

Below, please f= ind the revised request. I have included the prior values in [ ]s so that a= ll the changes are visible.=C2=A0

Please let us kn= ow if this addresses your comments and if you have any other questions or c= oncerns.=C2=A0

---

Open D= ata (OData) Protocol IANA Header registration request
28-Nov-2018=

This documentation contains the information neede= d for Permanent Registration of the OData specific request headers with IAN= A as called out in RFC 3864 - Registration Procedures for Message Header Fi= elds.

The OData headers to be registered as Perman= ent Headers are

OData-EntityId=C2=A0 [WAS EntityID= ]
Isolation
OData-MaxVersion
OData-Version

The details as required by RFC 3864 for these header= s are listed below
=

####
Header field name:
OData-EntityId=C2=A0 [WAS EntityID]
=
Applicable protocol:
http=C2=A0 =C2=A0[WAS OASIS Open Data Protocol (OData)]

Status:
= Standard

Author/Change controller:
OASIS

Specifica= tion document(s):
<= div>OData Version 4.01 Part 1: Protocol -=C2=A0

Related information:
=C2=A0 =C2=A0 None=C2=A0 [WAS Th= e EntityId header was named OData-EntityId in OData version 4.0.]


####
Header field name:
= Isolation

= Applicable protocol:
http= =C2=A0 =C2=A0[WAS OASIS Open Data Protocol (OData)]

Status:
Standard
<= div>
Author/Change controller:
OASIS

Specification document(s= ):
OData Versi= on 4.01 Part 1: Protocol -=C2=A0
=C2= =A0 =C2=A0
Related information:
The Isolation header was named OData-Isolation = in OData version 4.0.=C2=A0 The OData Protocol document referenced above de= fines one valid value, snapshot.=C2=A0 To make this header useful to applic= ations other than OData this registration also defines the values read-unco= mmitted, read-committed, repeatable-read and serializable.=C2=A0 These corr= espond to the standard transaction isolation levels exposed by most databas= e systems.=C2=A0 =C2=A0
=C2=A0 =C2=A0[WAS The Isolation header wa= s named OData-Isolation in OData version 4.0.]

####
Header field name:
OData-MaxVersion

Applicable p= rotocol:
http=C2=A0 =C2= =A0[WAS OASIS Open Data Protocol (OData)]

Status:<= /div>
Standard

Author/Change controller:
OASIS

Specification document(s):
OData Version 4.01 Part 1: Protocol -=C2=A0
http://docs.= oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Header= ODataMaxVersion =C2=A0 =C2=A0


Related information:
<none>


####
Header field name:
OData-Version

= Applicable protocol:
http= =C2=A0 =C2=A0[WAS OASIS Open Data Protocol (OData)]

Status:
Standard
<= div>
Author/Change controller:
OASIS

Specification document(s= ):
OData Version 4.01 Par= t 1: Protocol -=C2=A0
http://docs.oasis-open.org/odata/odata/v= 4.01/odata-v4.01-part1-protocol.html#sec_HeaderODataVersion =C2=A0 =C2=A0


Related information:
<none>



--
<= div dir=3D"ltr" class=3D"gmail_signature">
/chet=C2=A0
----------------
Chet Ensign
Chief Technical Communit= y Steward
OASIS: Advancing open standards for the information soc= iety
http://www.= oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-13= 93=C2=A0
<= /div> --00000000000073ddd4057c5e57ea-- From nobody Thu Dec 6 16:58:04 2018 Return-Path: X-Original-To: ietf-message-headers@ietfa.amsl.com Delivered-To: ietf-message-headers@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36AAF12D4E8 for ; Thu, 6 Dec 2018 16:58:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=vvL/vHq2; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=mmG9ZTkm Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FmnX3lin0cfR for ; Thu, 6 Dec 2018 16:57:57 -0800 (PST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4943124BE5 for ; Thu, 6 Dec 2018 16:57:57 -0800 (PST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id AA2AA21614; Thu, 6 Dec 2018 19:57:56 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 06 Dec 2018 19:57:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=u U8HFpwlVw+eaMBGAzvGALbkBQ038p8DsEDJDdoymmM=; b=vvL/vHq2/7ZhJHc7n dVlxW2J1rxd08atw+44pRuX7EJqHjxQ+N6QKm35Caz2OTe7+wZLFe/POCm+0p0Yq ZWyiyAp4XXCYLFgS9k2g6Z9tE09vJKLXeMXCeY1X4F7yCNjR8QWl6ZVbDXGH7+D4 /4BwL1PV/8s/2zYyI0ZT0wQHqTHl9Rc0m9RSwCDazTZonbCt3TZWCUUKrJPzMIIA E539qOP1dEBI519/f/1hlOqyBLi7grm6oaXKhpKKSRFZgLzICEgn5XroF2LTlYRI woTFlawz2xkl3XWptqugXm9N/ym15BAz97SMC06N2mV/eCIiYaVPTx72egixMper zBQXQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=uU8HFpwlVw+eaMBGAzvGALbkBQ038p8DsEDJDdoym mM=; b=mmG9ZTkmf5X3/Dvk9U9oM/LSC32C8huvP21BW5hQh2izsudRv5kNP6kK6 jZoMbzT3iyPHfV64mah5kvJDnefQJeTyXSMGHNOiFrfEWn1gHYgd3zF6Zw/VIz/X 7s1t4T49kuPWpTLxaIaLjCwU6xCyLK7sf8Uhp4YOCq6B/NIFNjwS/d/eGqvpuAWp bgm6bzcBOSp6EJrJPCSiL065zi8UV5V+0Xar1WG4oZlDlfAcL3Obni3APo+Xarh8 4KHPWvkXsSNZPhifB6I/RA4ivO7vYfwDadNKgd8HvpukNEsVtHDNjNKxELJTc7TM 8ab+Scb2tms8e+9zyq/UYNJvEDXFw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudefkedgvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjff fgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghm uceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpehorghsihhsqdhophgvnh drohhrghdpihgvthhfrdhorhhgpdhmnhhothdrnhgvthdphhhtthhpihhthhhinhhkrddq qddqihhnnecukfhppedugeegrddufeeirddujeehrddvkeenucfrrghrrghmpehmrghilh hfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from attitudadjuster.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 1EF7EE4430; Thu, 6 Dec 2018 19:57:52 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) From: Mark Nottingham In-Reply-To: Date: Fri, 7 Dec 2018 11:57:33 +1100 Cc: ietf-message-headers@ietf.org, "Ralf Handl (SAP)" Content-Transfer-Encoding: quoted-printable Message-Id: <724DB0C1-B093-46C6-B55B-A5DDE9ECACE1@mnot.net> References: To: Chet Ensign X-Mailer: Apple Mail (2.3445.100.39) Archived-At: Subject: Re: [Ietf-message-headers] Updates to registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version X-BeenThere: ietf-message-headers@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion list for header fields used in Internet messaging applications." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Dec 2018 00:58:03 -0000 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 = wrote: >=20 > 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/msg0019= 5.html >=20 > In response to this request, on August 29, in = https://www.ietf.org/mail-archive/web/ietf-message-headers/current/msg0019= 6.html, Ted Hardie wrote:=20 >=20 > --- >=20 > 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: >=20 > isolation =3D [ "OData-" ] "Isolation" ":" OWS "snapshot" >=20 > That seems to indicate that both ODate-Isolation and Isolation are = expected to be valid for this token. The ABNF for EntityID is similar: >=20 > entityid =3D [ "OData-" ] "EntityID" ":" OWS IRI-in-header >=20 > Can you clarify the intent here? Are both expressions of this token = expected to continue? >=20 > 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. =20 >=20 > --- >=20 > In response, the TC renamed EntityId header to OData-EntityId and = added additional values for the Isolation header to align with most = database systems.=20 >=20 >=20 > On August 30, in = https://www.ietf.org/mail-archive/web/ietf-message-headers/current/msg0019= 7.html, Mark Nottingham wrote:=20 >=20 > ---=20 >=20 > "Applicable protocol" should be "http", I think. >=20 > ---=20 >=20 > In response, the TC changed the Applicable protocol to http.=20 >=20 > Below, please find the revised request. I have included the prior = values in [ ]s so that all the changes are visible.=20 >=20 > Please let us know if this addresses your comments and if you have any = other questions or concerns.=20 >=20 > --- >=20 > Open Data (OData) Protocol IANA Header registration request > 28-Nov-2018 >=20 > 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. >=20 > The OData headers to be registered as Permanent Headers are >=20 > OData-EntityId [WAS EntityID] > Isolation > OData-MaxVersion > OData-Version >=20 > The details as required by RFC 3864 for these headers are listed below > =09 >=20 > #### > Header field name: > OData-EntityId [WAS EntityID] >=20 > Applicable protocol: > http [WAS OASIS Open Data Protocol (OData)] >=20 > Status: > Standard >=20 > Author/Change controller: > OASIS >=20 > Specification document(s): > =09 > OData Version 4.01 Part 1: Protocol -=20 > = http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.ht= ml#sec_HeaderEntityIdODataEntityId =20 >=20 > Related information: > =09 > None [WAS The EntityId header was named OData-EntityId in OData = version 4.0.] >=20 >=20 > #### > Header field name: > Isolation >=20 > Applicable protocol: > http [WAS OASIS Open Data Protocol (OData)] >=20 > Status: > Standard >=20 > Author/Change controller: > OASIS >=20 > Specification document(s): > =09 > OData Version 4.01 Part 1: Protocol -=20 > = http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.ht= ml#sec_HeaderIsolationODataIsolation > =20 > Related information: > =09 > 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. =20 > [WAS The Isolation header was named OData-Isolation in OData = version 4.0.] >=20 >=20 > #### > Header field name: > OData-MaxVersion >=20 > Applicable protocol: > http [WAS OASIS Open Data Protocol (OData)] >=20 > Status: > Standard >=20 > Author/Change controller: > OASIS >=20 > Specification document(s): > OData Version 4.01 Part 1: Protocol -=20 > = http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.ht= ml#sec_HeaderODataMaxVersion =20 >=20 >=20 > Related information: > >=20 >=20 >=20 > #### > Header field name: > OData-Version >=20 > Applicable protocol: > http [WAS OASIS Open Data Protocol (OData)] >=20 > Status: > Standard >=20 > Author/Change controller: > OASIS >=20 > Specification document(s): > OData Version 4.01 Part 1: Protocol -=20 > = http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.ht= ml#sec_HeaderODataVersion =20 >=20 >=20 > Related information: > >=20 >=20 >=20 > --=20 >=20 > /chet=20 > ---------------- > Chet Ensign > Chief Technical Community Steward > OASIS: Advancing open standards for the information society > http://www.oasis-open.org >=20 > Primary: +1 973-996-2298 > Mobile: +1 201-341-1393=20 > _______________________________________________ > 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/ From nobody Fri Dec 7 07:23:16 2018 Return-Path: X-Original-To: ietf-message-headers@ietfa.amsl.com Delivered-To: ietf-message-headers@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B24A126BED for ; Fri, 7 Dec 2018 07:23:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.899 X-Spam-Level: X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R5hGlMTgDDSb for ; Fri, 7 Dec 2018 07:23:11 -0800 (PST) Received: from smtpgw03.sap-ag.de (smtpgw03.sap-ag.de [155.56.66.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ACC2124C04 for ; Fri, 7 Dec 2018 07:23:10 -0800 (PST) From: "Handl, Ralf" To: Mark Nottingham CC: "ietf-message-headers@ietf.org" , "Chet Ensign" Thread-Topic: [Ietf-message-headers] Updates to registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version Thread-Index: AQHUjY5O4Hw7nNEnVEe0GZJxzHEKwaVyY8uAgAD/9dA= Date: Fri, 7 Dec 2018 15:23:08 +0000 Message-ID: References: <724DB0C1-B093-46C6-B55B-A5DDE9ECACE1@mnot.net> In-Reply-To: <724DB0C1-B093-46C6-B55B-A5DDE9ECACE1@mnot.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.21.23.238] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [Ietf-message-headers] Updates to registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version X-BeenThere: ietf-message-headers@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion list for header fields used in Internet messaging applications." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Dec 2018 15:23:15 -0000 Hi Mark, We no longer want to reserve it for single token use and instead want to re= gister five values: read-uncommitted, read-committed, repeatable-read, snap= shot, and serializable. Thanks Ralf -----Original Message----- From: Mark Nottingham =20 Sent: Freitag, 7. Dezember 2018 01:58 To: Chet Ensign Cc: ietf-message-headers@ietf.org; Handl, Ralf Subject: Re: [Ietf-message-headers] Updates to registration request for Ent= ityId, Isolation, OData-MaxVersion, and OData-Version Chet, Can you speak to why the request is still for "Isolation", instead of "ODat= a-Isolation"? Cheers, > On 7 Dec 2018, at 5:05 am, Chet Ensign wrote= : >=20 > This message contains an update to the registration request submitted on = August 29 2018 in https://www.ietf.org/mail-archive/web/ietf-message-header= s/current/msg00195.html >=20 > In response to this request, on August 29, in https://www.ietf.org/mail-a= rchive/web/ietf-message-headers/current/msg00196.html, Ted Hardie wrote:=20 >=20 > --- >=20 > 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 say= s: >=20 > isolation =3D [ "OData-" ] "Isolation" ":" OWS "snapshot" >=20 > That seems to indicate that both ODate-Isolation and Isolation are expect= ed to be valid for this token. The ABNF for EntityID is similar: >=20 > entityid =3D [ "OData-" ] "EntityID" ":" OWS IRI-in-header >=20 > Can you clarify the intent here? Are both expressions of this token expe= cted to continue? >=20 > In general, "Isolation" seems to be a very general concept, and the reser= vation of it, unadorned, for a single token use ("snapshot") is somewhat su= rprising compared to the more-obviously scoped OData-isolation. EntityID s= eems similar board in possible usage outside the OData specification. =20 >=20 > --- >=20 > In response, the TC renamed EntityId header to OData-EntityId and added a= dditional values for the Isolation header to align with most database syste= ms.=20 >=20 >=20 > On August 30, in https://www.ietf.org/mail-archive/web/ietf-message-heade= rs/current/msg00197.html, Mark Nottingham wrote:=20 >=20 > ---=20 >=20 > "Applicable protocol" should be "http", I think. >=20 > ---=20 >=20 > In response, the TC changed the Applicable protocol to http.=20 >=20 > Below, please find the revised request. I have included the prior values = in [ ]s so that all the changes are visible.=20 >=20 > Please let us know if this addresses your comments and if you have any ot= her questions or concerns.=20 >=20 > --- >=20 > Open Data (OData) Protocol IANA Header registration request > 28-Nov-2018 >=20 > This documentation contains the information needed for Permanent Registra= tion of the OData specific request headers with IANA as called out in RFC 3= 864 - Registration Procedures for Message Header Fields. >=20 > The OData headers to be registered as Permanent Headers are >=20 > OData-EntityId [WAS EntityID] > Isolation > OData-MaxVersion > OData-Version >=20 > The details as required by RFC 3864 for these headers are listed below > =09 >=20 > #### > Header field name: > OData-EntityId [WAS EntityID] >=20 > Applicable protocol: > http [WAS OASIS Open Data Protocol (OData)] >=20 > Status: > Standard >=20 > Author/Change controller: > OASIS >=20 > Specification document(s): > =09 > OData Version 4.01 Part 1: Protocol -=20 > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol= .html#sec_HeaderEntityIdODataEntityId =20 >=20 > Related information: > =09 > None [WAS The EntityId header was named OData-EntityId in OData vers= ion 4.0.] >=20 >=20 > #### > Header field name: > Isolation >=20 > Applicable protocol: > http [WAS OASIS Open Data Protocol (OData)] >=20 > Status: > Standard >=20 > Author/Change controller: > OASIS >=20 > Specification document(s): > =09 > OData Version 4.01 Part 1: Protocol -=20 > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol= .html#sec_HeaderIsolationODataIsolation > =20 > Related information: > =09 > 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 registr= ation also defines the values read-uncommitted, read-committed, repeatable-= read and serializable. These correspond to the standard transaction isolat= ion levels exposed by most database systems. =20 > [WAS The Isolation header was named OData-Isolation in OData version 4= .0.] >=20 >=20 > #### > Header field name: > OData-MaxVersion >=20 > Applicable protocol: > http [WAS OASIS Open Data Protocol (OData)] >=20 > Status: > Standard >=20 > Author/Change controller: > OASIS >=20 > Specification document(s): > OData Version 4.01 Part 1: Protocol -=20 > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol= .html#sec_HeaderODataMaxVersion =20 >=20 >=20 > Related information: > >=20 >=20 >=20 > #### > Header field name: > OData-Version >=20 > Applicable protocol: > http [WAS OASIS Open Data Protocol (OData)] >=20 > Status: > Standard >=20 > Author/Change controller: > OASIS >=20 > Specification document(s): > OData Version 4.01 Part 1: Protocol -=20 > http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol= .html#sec_HeaderODataVersion =20 >=20 >=20 > Related information: > >=20 >=20 >=20 > --=20 >=20 > /chet=20 > ---------------- > Chet Ensign > Chief Technical Community Steward > OASIS: Advancing open standards for the information society > http://www.oasis-open.org >=20 > Primary: +1 973-996-2298 > Mobile: +1 201-341-1393=20 > _______________________________________________ > 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/ From nobody Tue Dec 18 13:28:29 2018 Return-Path: X-Original-To: ietf-message-headers@ietfa.amsl.com Delivered-To: ietf-message-headers@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04FD9130F63 for ; Tue, 18 Dec 2018 13:28:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oasis-open-org.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlnYF7Msy5Nv for ; Tue, 18 Dec 2018 13:28:25 -0800 (PST) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA55F1292F1 for ; Tue, 18 Dec 2018 13:28:24 -0800 (PST) Received: by mail-ed1-x534.google.com with SMTP id h50so15153026ede.5 for ; Tue, 18 Dec 2018 13:28:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oasis-open-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=h5xTQEegdBGl31vfy7oz4yey8H3CymIUMOPFrR0FyMU=; b=ci10V9eeK258dJyN+V/6+JGpagZ+ZDouhqyOqHUq5J3mSKjKM3dnuCjqcm7st864LV hdjkcg8eXNqiYfM7BNezJcd31s2GjjsoMp8D8fVbkrTT/8/9lt3xQ2SLVDD2X0hW95PA eRkgNOE6x77YYYD+dFsJl5Cnwfs5hyxMZeuKvmgnZqmeN+Lnci3mp5c2ltaNV+0cLZxc 4Wa8+5ypYacd9jXULPXKsbdzwWJRDAmKSBl/+1kPMDdO92O2x/46gjVxk/UjCJayrcNG TjBz5Yc3JYyhTFcvVGgYDZ3iCA08yv2YThE9zs+eaNysYATbyR1mIAwaOFWCD1W8jEPB ukjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=h5xTQEegdBGl31vfy7oz4yey8H3CymIUMOPFrR0FyMU=; b=JAnql74f4mUNrZuawE3sAaXOs71N6QzgfKvQeV8XAnTJK8W+1NUUSRVCgnrnfSRLQ5 dCKuOpArQtcuV5epGnCcBuyiRQHJf1HUTx3aEfYzgdRGrM7eoQoWdE21/TFVShiPf+Z5 BvOAlcRqhddF+wQLWuDaqwjUDlRzWZV1QblfHkf9Q5clOaUh1eg/7vv7kCcaYtGAk/Mw paH9u30ANjUQDR5NBG+XTFR6Cs0ZBkSVXLXCgVSDmLvGps5/5n3cRduwBhE5JNx3Ta4O i8g6bwvlDI8QmiJVunizwFZpBaaQ+r82CdSOcdyqy0c/5Cd9rcFaY7g4zxB+jz9AG0xl zVRQ== X-Gm-Message-State: AA+aEWYiTi/KEgLniHLlKdDcRhakf3a8up1fCV812dIwulseB7aK4XwK vr8No6Z1El+rAlIucQfndJSnYLgCc/yODJeZyXXM X-Google-Smtp-Source: AFSGD/WyEpUe6qsOp6BbIGdEFBVb+C26r6YrxKn8ya4iQsgPel+iECICSrAm9mAd5c//IZ+iK0nN/yqXdH5IPT225vc= X-Received: by 2002:a50:af21:: with SMTP id g30mr7120346edd.234.1545168503227; Tue, 18 Dec 2018 13:28:23 -0800 (PST) MIME-Version: 1.0 References: <724DB0C1-B093-46C6-B55B-A5DDE9ECACE1@mnot.net> In-Reply-To: From: Chet Ensign Date: Tue, 18 Dec 2018 16:28:12 -0500 Message-ID: To: "Handl, Ralf" Cc: Mark Nottingham , "ietf-message-headers@ietf.org" Content-Type: multipart/alternative; boundary="000000000000c0e14c057d529354" Archived-At: Subject: Re: [Ietf-message-headers] Updates to registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version X-BeenThere: ietf-message-headers@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion list for header fields used in Internet messaging applications." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Dec 2018 21:28:28 -0000 --000000000000c0e14c057d529354 Content-Type: text/plain; charset="UTF-8" Hi Mark, Can you advise on the best way to proceed? Should I work with the TC to draft a revised registration request? Thank you, /chet On Fri, Dec 7, 2018 at 10:23 AM Handl, Ralf wrote: > 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 > Sent: Freitag, 7. Dezember 2018 01:58 > To: Chet Ensign > Cc: ietf-message-headers@ietf.org; Handl, Ralf > 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 > 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: > > > > > > > > > > #### > > 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: > > > > > > > > > > -- > > > > /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/ > > -- /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 --000000000000c0e14c057d529354 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Mark,=C2=A0

Can you advise on the be= st way to proceed?=C2=A0Should I work with the TC to draft a revised regist= ration request?=C2=A0

Thank you,=C2=A0
<= br>
/chet=C2=A0

On Fri, Dec 7, 2018 at 10:23 AM Handl, Ralf <ralf.handl@sap.com> wrote:
Hi Mark,

We no longer want to reserve it for single token use and instead want to re= gister five values: read-uncommitted, read-committed, repeatable-read, snap= shot, 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 Ent= ityId, Isolation, OData-MaxVersion, and OData-Version

Chet,

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

Cheers,


> On 7 Dec 2018, at 5:05 am, Chet Ensign <chet.ensign@oasis-open.org> wro= te:
>
> 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/msg0019= 5.html
>
> In response to this request, on August 29, in https://www.ietf.org/mail-archive/web/ietf-m= essage-headers/current/msg00196.html, Ted Hardie wrote:
>
> ---
>
> I'm a little confused on one point.=C2=A0 The Isolation header sta= tes that it was called OData-Isolation in version 4.0, but the linked ABNF = document says:
>
> isolation=C2=A0 =3D [ "OData-" ] "Isolation" "= ;:" OWS "snapshot"
>
> That seems to indicate that both ODate-Isolation and Isolation are exp= ected to be valid for this token.=C2=A0 The ABNF for EntityID is similar: >
> entityid=C2=A0 =C2=A0=3D [ "OData-" ] "EntityID" &= quot;:" OWS IRI-in-header
>
> Can you clarify the intent here?=C2=A0 Are both expressions of this to= ken expected to continue?
>
> In general, "Isolation" seems to be a very general concept, = and the reservation of it, unadorned, for a single token use ("snapsho= t") is somewhat surprising compared to the more-obviously scoped OData= -isolation.=C2=A0 EntityID seems similar board in possible usage outside th= e OData specification.=C2=A0
>
> ---
>
> In response, the TC renamed EntityId header to OData-EntityId and adde= d additional values for the Isolation header to align with most database sy= stems.
>
>
> On August 30, in https://www.ietf.org/mail-archive/web/ietf-message-headers/current/msg001= 97.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 valu= es 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 Regis= tration of the OData specific request headers with IANA as called out in RF= C 3864 - Registration Procedures for Message Header Fields.
>
> The OData headers to be registered as Permanent Headers are
>
> OData-EntityId=C2=A0 [WAS EntityID]
> Isolation
> OData-MaxVersion
> OData-Version
>
> The details as required by RFC 3864 for these headers are listed below=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0
>
> ####
> Header field name:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0OData-EntityId=C2=A0 [WAS EntityID]
>
> Applicable protocol:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0http=C2=A0 =C2=A0[WAS OASIS Open Data Protoc= ol (OData)]
>
> Status:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Standard
>
> Author/Change controller:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0OASIS
>
> Specification document(s):
>=C2=A0 =C2=A0 =C2=A0 =C2=A0
> OData Version 4.01 Part 1: Protocol -
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http://d= ocs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_He= aderEntityIdODataEntityId=C2=A0 =C2=A0 =C2=A0 =C2=A0
>
> Related information:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0
>=C2=A0 =C2=A0 =C2=A0None=C2=A0 [WAS The EntityId header was named OData= -EntityId in OData version 4.0.]
>
>
> ####
> Header field name:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Isolation
>
> Applicable protocol:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0http=C2=A0 =C2=A0[WAS OASIS Open Data Protoc= ol (OData)]
>
> Status:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Standard
>
> Author/Change controller:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0OASIS
>
> Specification document(s):
>=C2=A0 =C2=A0 =C2=A0 =C2=A0
> OData Version 4.01 Part 1: Protocol -
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http:/= /docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_= HeaderIsolationODataIsolation
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
> Related information:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0
> The Isolation header was named OData-Isolation in OData version 4.0.= =C2=A0 The OData Protocol document referenced above defines one valid value= , snapshot.=C2=A0 To make this header useful to applications other than ODa= ta this registration also defines the values read-uncommitted, read-committ= ed, repeatable-read and serializable.=C2=A0 These correspond to the standar= d transaction isolation levels exposed by most database systems.=C2=A0 =C2= =A0
>=C2=A0 =C2=A0 [WAS The Isolation header was named OData-Isolation in OD= ata version 4.0.]
>
>
> ####
> Header field name:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0OData-MaxVersion
>
> Applicable protocol:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0http=C2=A0 =C2=A0[WAS OASIS Open Data Protoc= ol (OData)]
>
> Status:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Standard
>
> Author/Change controller:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0OASIS
>
> Specification document(s):
> OData Version 4.01 Part 1: Protocol -
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http://docs.oa= sis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_HeaderOD= ataMaxVersion=C2=A0 =C2=A0 =C2=A0
>
>
> Related information:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0<none>
>
>
>
> ####
> Header field name:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0OData-Version
>
> Applicable protocol:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0http=C2=A0 =C2=A0[WAS OASIS Open Data Protoc= ol (OData)]
>
> Status:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Standard
>
> Author/Change controller:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0OASIS
>
> Specification document(s):
>=C2=A0 =C2=A0 =C2=A0 =C2=A0OData Version 4.01 Part 1: Protocol -
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http://docs.oasis= -open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_HeaderOData= Version=C2=A0 =C2=A0 =C2=A0 =C2=A0
>
>
> Related information:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0<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
> Iet= f-message-headers@ietf.org
> https://www.ietf.org/mailman/listinfo= /ietf-message-headers

--
Mark Nottingham=C2=A0 =C2=A0https://www.mnot.net/



--

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

Primary: +1 973-996-2298
Mobile: +1 201-341-1393=C2=A0
<= /div>
--000000000000c0e14c057d529354-- From nobody Thu Dec 20 00:08:04 2018 Return-Path: X-Original-To: ietf-message-headers@ietfa.amsl.com Delivered-To: ietf-message-headers@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35F031310C2 for ; Thu, 20 Dec 2018 00:08:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=WMjpL8au; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=x4PAXC6I Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjaEUEJcKbXm for ; Thu, 20 Dec 2018 00:07:58 -0800 (PST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E3781310C1 for ; Thu, 20 Dec 2018 00:07:57 -0800 (PST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 0C58C21841; Thu, 20 Dec 2018 03:07:56 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 20 Dec 2018 03:07:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=u 5o9edPNVogQmbl+p/pJ9UFbWxjvrUNfg309CTe3n6U=; b=WMjpL8au6VqBRokKc UetVswXFKS1aTtXzCtTvvnHlnMQDOHHdr0c+5wRDyd6dM+7uT/rCEmE3WIOv1dI8 tt3gAEJ4KfYSLhDpH15uBpBUc/+Q4LgOgsWDndCyUCVNZLpm7NhLHFilfV49o3El eWXKivze8kaOmrw1EM986ks1q4oktwAM0jIft7VBpbSg2zi09FpwMqnR4kx6oahv PL0Rlc+b1+C4+EVeCXDoMJVCOsKNU3gvJm4U4eB8U0eh4OLWTQAmOMfnVkdLnVRl VO0M83aMkXJLajgQzN/CIrIzuX0RKqOmJYCoH60c469543ic2MYYM7doXTUuks4b tw3Dg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=u5o9edPNVogQmbl+p/pJ9UFbWxjvrUNfg309CTe3n 6U=; b=x4PAXC6I26FIY2RhxtpR4A1T455JuFnKBVkpSAP16b3SQxI5sb/bf213W 3Faa/vGl0eXVBgTBmYF8AVEpLoeEXeptgvrh4a8jKVX/rv1b6RQyVziuLeKF36/T MizeaR+kpF3aE7PdpqhbLsCmrUwZB+508F3bnNeAdMhnCP/f7MrS8gWytPqhs2IK GTJXoGoTTdtAqFmtMES0DQKxRWumgs0rvWiukTp6lLYQ4vNEmKqijkyFTaf6Dlas fGm0mTMNCPWwLZMEvIUsAe6o6Mik8DywlC6M+wUmZ2QUtGHAhQidbeDzw+Tr56I4 3gSWN340t7vK7H1CknwhDo7m4OfBw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudejvddguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecu fedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurheptggguffhjg ffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgr mhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhepohgrshhishdqohhpvg hnrdhorhhgpdhivghtfhdrohhrghdpmhhnohhtrdhnvghtpdhhthhtphhithhhihhnkhdr qddqqdhinhenucfkphepudeggedrudefiedrudejhedrvdeknecurfgrrhgrmhepmhgrih hlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from attitudadjuster.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 36713100BB; Thu, 20 Dec 2018 03:07:51 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) From: Mark Nottingham In-Reply-To: Date: Thu, 20 Dec 2018 19:07:49 +1100 Cc: "Handl, Ralf" , "ietf-message-headers@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <724DB0C1-B093-46C6-B55B-A5DDE9ECACE1@mnot.net> To: Chet Ensign X-Mailer: Apple Mail (2.3445.100.39) Archived-At: Subject: Re: [Ietf-message-headers] Updates to registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version X-BeenThere: ietf-message-headers@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion list for header fields used in Internet messaging applications." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 08:08:02 -0000 Hi Chet, I have to admit I was confused by Ralf's response. The purpose of asking = why "Isolation" was chosen instead of "OData-Isolation" was to draw out = how this header was potentially generic (i.e., applicable to other = things than OData). Cheers, > On 19 Dec 2018, at 8:28 am, Chet Ensign = wrote: >=20 > Hi Mark,=20 >=20 > Can you advise on the best way to proceed? Should I work with the TC = to draft a revised registration request?=20 >=20 > Thank you,=20 >=20 > /chet=20 >=20 > On Fri, Dec 7, 2018 at 10:23 AM Handl, Ralf = wrote: > Hi Mark, >=20 > 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. >=20 > Thanks > Ralf >=20 > -----Original Message----- > From: Mark Nottingham =20 > Sent: Freitag, 7. Dezember 2018 01:58 > To: Chet Ensign > Cc: ietf-message-headers@ietf.org; Handl, Ralf > Subject: Re: [Ietf-message-headers] Updates to registration request = for EntityId, Isolation, OData-MaxVersion, and OData-Version >=20 > Chet, >=20 > Can you speak to why the request is still for "Isolation", instead of = "OData-Isolation"? >=20 > Cheers, >=20 >=20 > > On 7 Dec 2018, at 5:05 am, Chet Ensign = wrote: > >=20 > > 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/msg0019= 5.html > >=20 > > In response to this request, on August 29, in = https://www.ietf.org/mail-archive/web/ietf-message-headers/current/msg0019= 6.html, Ted Hardie wrote:=20 > >=20 > > --- > >=20 > > 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: > >=20 > > isolation =3D [ "OData-" ] "Isolation" ":" OWS "snapshot" > >=20 > > That seems to indicate that both ODate-Isolation and Isolation are = expected to be valid for this token. The ABNF for EntityID is similar: > >=20 > > entityid =3D [ "OData-" ] "EntityID" ":" OWS IRI-in-header > >=20 > > Can you clarify the intent here? Are both expressions of this token = expected to continue? > >=20 > > 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. =20 > >=20 > > --- > >=20 > > In response, the TC renamed EntityId header to OData-EntityId and = added additional values for the Isolation header to align with most = database systems.=20 > >=20 > >=20 > > On August 30, in = https://www.ietf.org/mail-archive/web/ietf-message-headers/current/msg0019= 7.html, Mark Nottingham wrote:=20 > >=20 > > ---=20 > >=20 > > "Applicable protocol" should be "http", I think. > >=20 > > ---=20 > >=20 > > In response, the TC changed the Applicable protocol to http.=20 > >=20 > > Below, please find the revised request. I have included the prior = values in [ ]s so that all the changes are visible.=20 > >=20 > > Please let us know if this addresses your comments and if you have = any other questions or concerns.=20 > >=20 > > --- > >=20 > > Open Data (OData) Protocol IANA Header registration request > > 28-Nov-2018 > >=20 > > 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. > >=20 > > The OData headers to be registered as Permanent Headers are > >=20 > > OData-EntityId [WAS EntityID] > > Isolation > > OData-MaxVersion > > OData-Version > >=20 > > The details as required by RFC 3864 for these headers are listed = below > > =20 > >=20 > > #### > > Header field name: > > OData-EntityId [WAS EntityID] > >=20 > > Applicable protocol: > > http [WAS OASIS Open Data Protocol (OData)] > >=20 > > Status: > > Standard > >=20 > > Author/Change controller: > > OASIS > >=20 > > Specification document(s): > > =20 > > OData Version 4.01 Part 1: Protocol -=20 > > = http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.ht= ml#sec_HeaderEntityIdODataEntityId =20 > >=20 > > Related information: > > =20 > > None [WAS The EntityId header was named OData-EntityId in OData = version 4.0.] > >=20 > >=20 > > #### > > Header field name: > > Isolation > >=20 > > Applicable protocol: > > http [WAS OASIS Open Data Protocol (OData)] > >=20 > > Status: > > Standard > >=20 > > Author/Change controller: > > OASIS > >=20 > > Specification document(s): > > =20 > > OData Version 4.01 Part 1: Protocol -=20 > > = http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.ht= ml#sec_HeaderIsolationODataIsolation > > =20 > > Related information: > > =20 > > 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. =20 > > [WAS The Isolation header was named OData-Isolation in OData = version 4.0.] > >=20 > >=20 > > #### > > Header field name: > > OData-MaxVersion > >=20 > > Applicable protocol: > > http [WAS OASIS Open Data Protocol (OData)] > >=20 > > Status: > > Standard > >=20 > > Author/Change controller: > > OASIS > >=20 > > Specification document(s): > > OData Version 4.01 Part 1: Protocol -=20 > > = http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.ht= ml#sec_HeaderODataMaxVersion =20 > >=20 > >=20 > > Related information: > > > >=20 > >=20 > >=20 > > #### > > Header field name: > > OData-Version > >=20 > > Applicable protocol: > > http [WAS OASIS Open Data Protocol (OData)] > >=20 > > Status: > > Standard > >=20 > > Author/Change controller: > > OASIS > >=20 > > Specification document(s): > > OData Version 4.01 Part 1: Protocol -=20 > > = http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.ht= ml#sec_HeaderODataVersion =20 > >=20 > >=20 > > Related information: > > > >=20 > >=20 > >=20 > > --=20 > >=20 > > /chet=20 > > ---------------- > > Chet Ensign > > Chief Technical Community Steward > > OASIS: Advancing open standards for the information society > > http://www.oasis-open.org > >=20 > > Primary: +1 973-996-2298 > > Mobile: +1 201-341-1393=20 > > _______________________________________________ > > Ietf-message-headers mailing list > > Ietf-message-headers@ietf.org > > https://www.ietf.org/mailman/listinfo/ietf-message-headers >=20 > -- > Mark Nottingham https://www.mnot.net/ >=20 >=20 >=20 > --=20 >=20 > /chet=20 > ---------------- > Chet Ensign > Chief Technical Community Steward > OASIS: Advancing open standards for the information society > http://www.oasis-open.org >=20 > Primary: +1 973-996-2298 > Mobile: +1 201-341-1393=20 -- Mark Nottingham https://www.mnot.net/ From nobody Thu Dec 20 06:00:02 2018 Return-Path: X-Original-To: ietf-message-headers@ietfa.amsl.com Delivered-To: ietf-message-headers@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 471C1131134 for ; Thu, 20 Dec 2018 05:59:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oasis-open-org.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CtiTPKRB3dRP for ; Thu, 20 Dec 2018 05:59:43 -0800 (PST) Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFED613111B for ; Thu, 20 Dec 2018 05:59:41 -0800 (PST) Received: by mail-ed1-x530.google.com with SMTP id b14so1828420edt.6 for ; Thu, 20 Dec 2018 05:59:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oasis-open-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JcQsVP0gm0DI11v08yxa1Q5TF+frXLazKAes/5yW1CE=; b=Ea7cZOjSwD0m8lGZRJKEER5Z0tMKSjv6ccRyNSMJbk6wE5RksrIgJ+5BpzIguE5DKv j5+KbE6MggdaiOEY3+lY4ycb1UYHlrg2KU7i+h4hfzFQhCNPIBWLBVL7h/Oydb0ZUb/O 6QPcshzMMh/qSki9sw3BjceMsHw8r9/tdhCF2Gr0LZazOh/vtHbw7Mo9+L5chTFFPyqV NevmtVgKuI1l235eDAFxkNNFgH48uHrGvs3LpxqAsDqAsL3y+Dy1vqkUdUemxWB4kTkj SoS+dAan3ADK+hCi3OgCYTvzcT9yOSte7/+M63gAipI7xCNaRUJw980LBxsMKck4Tvhn cZRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JcQsVP0gm0DI11v08yxa1Q5TF+frXLazKAes/5yW1CE=; b=WSnuUQrRntsY2nByV+Tfc1DfAOV9ZoDwoCAaTf0ZF/IBq0RYgHVdtNhLpbTfTqzHGd GV5IRdSC5jrTrBRlgovhFOF8oGFtQkmkJZAObUgBo6UojD4X9ujQub/FBZe1vxJ5p30I JQTpcAVquCD6LxCOS4SGXQ0fWl9eDrJWySIH378w6tUPO35DG+3rEzse2LzWZYS0NgAy iq5p4UZfdVqvbPEdzCJH2zz0x+gM+WZhv92nj9+fzmvU8idFhkH+IcAOSWPwu3Qx8hP4 a4T81Sav2v8/5FTc02Ck5QoT1zEv2ZVuJKw+KJdYeESthkFiMsWh7A6PAVm9ORsBU0+d U38Q== X-Gm-Message-State: AA+aEWZbl/V8Q0fuB4LLDDFG4rMn0LqzHFubEflRfQpQ8j4iHipiedPE 1zzxDZ6/kqpaDI2K33oNo7WStXvaP35o/+TB3PmQLbo= X-Google-Smtp-Source: AFSGD/VJz7E0JoygkMlPw4JOwWfIg5GML/4ew2HwpyKmQWz71M4hSH6/pvyp1/jgyLBRkW4Lc8X/2IJjtBKJTOi5L7w= X-Received: by 2002:a50:af21:: with SMTP id g30mr12774732edd.234.1545314380280; Thu, 20 Dec 2018 05:59:40 -0800 (PST) MIME-Version: 1.0 References: <724DB0C1-B093-46C6-B55B-A5DDE9ECACE1@mnot.net> In-Reply-To: From: Chet Ensign Date: Thu, 20 Dec 2018 08:59:29 -0500 Message-ID: To: Mark Nottingham Cc: "Handl, Ralf" , "ietf-message-headers@ietf.org" Content-Type: multipart/alternative; boundary="000000000000b40746057d748a6a" Archived-At: Subject: Re: [Ietf-message-headers] Updates to registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version X-BeenThere: ietf-message-headers@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion list for header fields used in Internet messaging applications." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 13:59:58 -0000 --000000000000b40746057d748a6a Content-Type: text/plain; charset="UTF-8" Thanks Mark. I will follow up with Ralf and the TC and get back to you. /chet On Thu, Dec 20, 2018 at 3:07 AM Mark Nottingham wrote: > Hi Chet, > > I have to admit I was confused by Ralf's response. The purpose of asking > why "Isolation" was chosen instead of "OData-Isolation" was to draw out how > this header was potentially generic (i.e., applicable to other things than > OData). > > Cheers, > > > > On 19 Dec 2018, at 8:28 am, Chet Ensign > wrote: > > > > Hi Mark, > > > > Can you advise on the best way to proceed? Should I work with the TC to > draft a revised registration request? > > > > Thank you, > > > > /chet > > > > On Fri, Dec 7, 2018 at 10:23 AM Handl, Ralf wrote: > > 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 > > Sent: Freitag, 7. Dezember 2018 01:58 > > To: Chet Ensign > > Cc: ietf-message-headers@ietf.org; Handl, Ralf > > 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 > 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: > > > > > > > > > > > > > > > #### > > > 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: > > > > > > > > > > > > > > > -- > > > > > > /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/ > > > > > > > > -- > > > > /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 > > -- > Mark Nottingham https://www.mnot.net/ > > -- /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 --000000000000b40746057d748a6a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Mark. I will follow up with Ralf and the TC and get= back to you.=C2=A0

/chet

On Thu, Dec 20, 2018 at 3:07 AM Mark Nottingha= m <mnot@mnot.net> wrote:
Hi Chet,

I have to admit I was confused by Ralf's response. The purpose of askin= g why "Isolation" was chosen instead of "OData-Isolation&quo= t; was to draw out how this header was potentially generic (i.e., applicabl= e to other things than OData).

Cheers,


> On 19 Dec 2018, at 8:28 am, Chet Ensign <chet.ensign@oasis-open.org> wr= ote:
>
> Hi Mark,
>
> Can you advise on the best way to proceed? Should I work with the TC t= o draft a revised registration request?
>
> Thank you,
>
> /chet
>
> On Fri, Dec 7, 2018 at 10:23 AM Handl, Ralf <ralf.handl@sap.com> wrote:
> 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 fo= r EntityId, Isolation, OData-MaxVersion, and OData-Version
>
> Chet,
>
> Can you speak to why the request is still for "Isolation", i= nstead 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 submi= tted on August 29 2018 in https://www.ietf.org/mail-archive/web/ietf-message-headers/current/ms= g00195.html
> >
> > In response to this request, on August 29, in https://www.ietf.org/mail-archive/web/i= etf-message-headers/current/msg00196.html, Ted Hardie wrote:
> >
> > ---
> >
> > I'm a little confused on one point.=C2=A0 The Isolation heade= r states that it was called OData-Isolation in version 4.0, but the linked = ABNF document says:
> >
> > isolation=C2=A0 =3D [ "OData-" ] "Isolation" = ":" OWS "snapshot"
> >
> > That seems to indicate that both ODate-Isolation and Isolation ar= e expected to be valid for this token.=C2=A0 The ABNF for EntityID is simil= ar:
> >
> > entityid=C2=A0 =C2=A0=3D [ "OData-" ] "EntityID&qu= ot; ":" OWS IRI-in-header
> >
> > Can you clarify the intent here?=C2=A0 Are both expressions of th= is token expected to continue?
> >
> > In general, "Isolation" seems to be a very general conc= ept, and the reservation of it, unadorned, for a single token use ("sn= apshot") is somewhat surprising compared to the more-obviously scoped = OData-isolation.=C2=A0 EntityID seems similar board in possible usage outsi= de the OData specification.=C2=A0
> >
> > ---
> >
> > In response, the TC renamed EntityId header to OData-EntityId and= added additional values for the Isolation header to align with most databa= se systems.
> >
> >
> > On August 30, in https://www.ietf.org/mail-archive/web/ietf-message-headers/current/m= sg00197.html, Mark Nottingham wrote:
> >
> > ---
> >
> > "Applicable protocol" should be "http", I thi= nk.
> >
> > ---
> >
> > 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 hav= e 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=C2=A0 [WAS EntityID]
> > Isolation
> > OData-MaxVersion
> > OData-Version
> >
> > The details as required by RFC 3864 for these headers are listed = below
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0
> >
> > ####
> > Header field name:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0OData-EntityId=C2=A0 [WAS EntityID]
> >
> > Applicable protocol:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0http=C2=A0 =C2=A0[WAS OASIS Open Data P= rotocol (OData)]
> >
> > Status:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0Standard
> >
> > Author/Change controller:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0OASIS
> >
> > Specification document(s):
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0
> > OData Version 4.01 Part 1: Protocol -
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0htt= p://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#s= ec_HeaderEntityIdODataEntityId=C2=A0 =C2=A0 =C2=A0 =C2=A0
> >
> > Related information:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0
> >=C2=A0 =C2=A0 =C2=A0None=C2=A0 [WAS The EntityId header was named = OData-EntityId in OData version 4.0.]
> >
> >
> > ####
> > Header field name:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0Isolation
> >
> > Applicable protocol:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0http=C2=A0 =C2=A0[WAS OASIS Open Data P= rotocol (OData)]
> >
> > Status:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0Standard
> >
> > Author/Change controller:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0OASIS
> >
> > Specification document(s):
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0
> > OData Version 4.01 Part 1: Protocol -
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0h= ttp://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html= #sec_HeaderIsolationODataIsolation
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
> > Related information:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0
> > The Isolation header was named OData-Isolation in OData version 4= .0.=C2=A0 The OData Protocol document referenced above defines one valid va= lue, snapshot.=C2=A0 To make this header useful to applications other than = OData this registration also defines the values read-uncommitted, read-comm= itted, repeatable-read and serializable.=C2=A0 These correspond to the stan= dard transaction isolation levels exposed by most database systems.=C2=A0 = =C2=A0
> >=C2=A0 =C2=A0 [WAS The Isolation header was named OData-Isolation = in OData version 4.0.]
> >
> >
> > ####
> > Header field name:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0OData-MaxVersion
> >
> > Applicable protocol:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0http=C2=A0 =C2=A0[WAS OASIS Open Data P= rotocol (OData)]
> >
> > Status:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0Standard
> >
> > Author/Change controller:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0OASIS
> >
> > Specification document(s):
> > OData Version 4.01 Part 1: Protocol -
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http://do= cs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Hea= derODataMaxVersion=C2=A0 =C2=A0 =C2=A0
> >
> >
> > Related information:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0<none>
> >
> >
> >
> > ####
> > Header field name:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0OData-Version
> >
> > Applicable protocol:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0http=C2=A0 =C2=A0[WAS OASIS Open Data P= rotocol (OData)]
> >
> > Status:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0Standard
> >
> > Author/Change controller:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0OASIS
> >
> > Specification document(s):
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0OData Version 4.01 Part 1: Protocol - <= br> > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http://docs.= oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Header= ODataVersion=C2=A0 =C2=A0 =C2=A0 =C2=A0
> >
> >
> > Related information:
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0<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/lis= tinfo/ietf-message-headers
>
> --
> Mark Nottingham=C2=A0 =C2=A0https://www.mnot.net/
>
>
>
> --
>
> /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

--
Mark Nottingham=C2=A0 =C2=A0https://www.mnot.net/



--

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

Primary: +1 973-996-2298
Mobile: +1 201-341-1393=C2=A0
<= /div>
--000000000000b40746057d748a6a--