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

Mark Nottingham <mnot@mnot.net> Thu, 20 December 2018 08:08 UTC

Return-Path: <mnot@mnot.net>
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 <ietf-message-headers@ietfa.amsl.com>; 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 <ietf-message-headers@ietfa.amsl.com>; 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 <ietf-message-headers@ietf.org>; 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: <xms:2U0bXAc-f43H_gk8wkqkL99S_I_BPd_6KmE_yPm6s1RcCHAAt6pKbg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudejvddguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecu fedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurheptggguffhjg ffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgr mhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhepohgrshhishdqohhpvg hnrdhorhhgpdhivghtfhdrohhrghdpmhhnohhtrdhnvghtpdhhthhtphhithhhihhnkhdr qddqqdhinhenucfkphepudeggedrudefiedrudejhedrvdeknecurfgrrhgrmhepmhgrih hlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:2U0bXHm1viLMQlUN8Hi0ZkebE2SAc3Lbee0eaeDQ9w0Ouwhu17_f9A> <xmx:2U0bXEmSFPsmOqSodQpEMaIt0xQeLFuheN0HDMaXBTZwOYWFwfgw_g> <xmx:2U0bXKnSTSKqTPWMaBMUOHYRenr4etm6Q70Hs6QMlobJgdTS-5kB_Q> <xmx:200bXJSv3u7R0dswntmKsXhIs39odQxlm7AvlapCJxz18tgDvFW98A>
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 <mnot@mnot.net>
In-Reply-To: <CAAwgnnPH87bFX2J6_P_0qyeRN89a05HYFyqMN0hKCrODUEqs5A@mail.gmail.com>
Date: Thu, 20 Dec 2018 19:07:49 +1100
Cc: "Handl, Ralf" <ralf.handl@sap.com>, "ietf-message-headers@ietf.org" <ietf-message-headers@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C64CDA35-3FC7-4BF1-A845-F6353CA7A799@mnot.net>
References: <CAAwgnnPNNUWDPQvo5bUzpd7FQ+sSaZYNydCBPTfVV6QY5TZhEw@mail.gmail.com> <724DB0C1-B093-46C6-B55B-A5DDE9ECACE1@mnot.net> <d2d53db904dd409cad6d845f4b58f1e7@sap.com> <CAAwgnnPH87bFX2J6_P_0qyeRN89a05HYFyqMN0hKCrODUEqs5A@mail.gmail.com>
To: Chet Ensign <chet.ensign@oasis-open.org>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-message-headers/82MUEmokcuVVZ67dP9G9GGbLuxY>
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." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-message-headers/>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=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 <chet.ensign@oasis-open.org> 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 <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 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/
> 
> 
> 
> -- 
> 
> /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/