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

Chet Ensign <chet.ensign@oasis-open.org> Thu, 06 December 2018 18:05 UTC

Return-Path: <chet.ensign@oasis-open.org>
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 <ietf-message-headers@ietfa.amsl.com>; 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 <ietf-message-headers@ietfa.amsl.com>; 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 <ietf-message-headers@ietf.org>; Thu, 6 Dec 2018 10:05:21 -0800 (PST)
Received: by mail-ed1-x52e.google.com with SMTP id f23so1543729edb.3 for <ietf-message-headers@ietf.org>; 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 <chet.ensign@oasis-open.org>
Date: Thu, 6 Dec 2018 13:05:08 -0500
Message-ID: <CAAwgnnPNNUWDPQvo5bUzpd7FQ+sSaZYNydCBPTfVV6QY5TZhEw@mail.gmail.com>
To: ietf-message-headers@ietf.org
Cc: "Mark Biamonte (Progress)" <Mark.Biamonte@progress.com>, "Ralf Handl (SAP)" <ralf.handl@sap.com>
Content-Type: multipart/alternative; boundary="00000000000073ddd4057c5e57ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-message-headers/oRU8ChCoUXV-DU5Vh6PAxKF9NZs>
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." <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, 06 Dec 2018 18:05:28 -0000

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