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

Ted Hardie <ted.ietf@gmail.com> Fri, 31 August 2018 16:54 UTC

Return-Path: <ted.ietf@gmail.com>
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 7D662130E57 for <ietf-message-headers@ietfa.amsl.com>; Fri, 31 Aug 2018 09:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 omNeTFe5cjvg for <ietf-message-headers@ietfa.amsl.com>; Fri, 31 Aug 2018 09:54:44 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 4EEB4130E51 for <ietf-message-headers@ietf.org>; Fri, 31 Aug 2018 09:54:44 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id p84-v6so22846246oic.4 for <ietf-message-headers@ietf.org>; Fri, 31 Aug 2018 09:54:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bF2YlUVett0xEGRXBdh8MBakT+Qc0S7vx1ZiGfY0DYc=; b=c8/jzkjN4LcNiCxmtadZiziGCJjfTcrOvL8e3c1505aomlKgsZQu5IKezWAmADX5Jr 6YoB8xHmwb/VaBG0dFqF6iBzHy/u3xdNKDJuz8iosz5wft6C8igj6V0a7WJQAWE1jm5U PgvSZcpf/bS2bUnnpWGw4GOmGXcI+9lW+kARMXq8vZiVg0mfCkuI6nMxok6Mwd5Xs3kC 1n7TMfnjwmoCFFlhJEQEpxX2fqYlMMv6iu0207WMpcapRD0ERFSJopahJJe4Z93vfY7d vVh2Q65+UlxqKdzGV0Rv1NpZcfQalZXpTWxjTEzkg8+tmRw3AJRlTu3VIqSMj1TTFO5c LehQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bF2YlUVett0xEGRXBdh8MBakT+Qc0S7vx1ZiGfY0DYc=; b=ERio5qc4XNdwg7zQfDm06bAcAntHqiC0gKj2BLOzFiS/VZKzn08/Mt78kLNX0g0VYP Ec2ZCabe1/E5x6G+fqH2p7cYQ5HMre8beDbmf5daRfCHOhnmKbtFZCgSgQBo/MJ1q/WG DYL9ixVOZjmAO981Ftf9rMNW1EZpgqA+EOvcIK2qdeihUSlP98mEjURgapOGMQxcYoYX EjwjBeOm+oi2qiZkO85HkCg7FLgVO/PAW5TvlV2o4NKChanfm6vy8RxqZnkiwucAoDGR c9XNlEJc8FNyucFUTr44PLyvyIa9YOlJCxqfnxJ8h1yJkfWk1v313/uKj+rdKDHUgSuH EY8w==
X-Gm-Message-State: APzg51D9KKFQMWuKNzkPexsTJwnd+6eWFDh13PnXb9gN421RVbKl9uVo IWyGjMVe6w3Lej2JQrnsJZs30app1Pc7pOFYbCv8Rg==
X-Google-Smtp-Source: ANB0VdYsVH1RomBUk9dsOyhbW+EN377NgJbWLYr2Gvdo2EN91JIS51hXYIoR/PYPzUiYFuBBVIdIcDuWKdNHnD+Nowo=
X-Received: by 2002:aca:4e50:: with SMTP id c77-v6mr7848303oib.254.1535734483453; Fri, 31 Aug 2018 09:54:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:594a:0:0:0:0:0 with HTTP; Fri, 31 Aug 2018 09:54:12 -0700 (PDT)
In-Reply-To: <BN7PR05MB42420B1185F9CC9508B50432840F0@BN7PR05MB4242.namprd05.prod.outlook.com>
References: <CAAwgnnOSdnKMDBZFq2BzazP6eKsPpAeuEmN6qstTCFQ8nQ=1+A@mail.gmail.com> <CA+9kkMC7itwTqKEfKn=U_aM2TKTkwN+Bzp6E1aj47gp9S66YrQ@mail.gmail.com> <CAAwgnnPh9dKaadxMiOzm=ZV2N_i5WrhD3unVBJ8jVSriLNq8MA@mail.gmail.com> <BN7PR05MB42420B1185F9CC9508B50432840F0@BN7PR05MB4242.namprd05.prod.outlook.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Fri, 31 Aug 2018 09:54:12 -0700
Message-ID: <CA+9kkMAyiJvNDprx5AhjFTW9BkHy5D0vjhgVjuJzQwSC+kyujg@mail.gmail.com>
To: Mark Biamonte <Mark.Biamonte@progress.com>
Cc: "ietf-message-headers@ietf.org" <ietf-message-headers@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005b0c5f0574be0ccb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-message-headers/TeStmZtLZlgDxhbXj8qft00NN2I>
Subject: Re: [Ietf-message-headers] Registration request for EntityId, Isolation, OData-MaxVersion, and OData-Version
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 31 Aug 2018 16:54:48 -0000

Hi Mark,

On Thu, Aug 30, 2018 at 6:49 PM, Mark Biamonte <Mark.Biamonte@progress.com>
wrote:

> Hi Ted,
>
>
>
> I am a member of the OData Technical Committee (TC).  Chet submitted the
> request for OASIS on behalf of the OData TC.  You are correct, in OData 4.0
> the Headers were titled OData-Isolation and OData-EntityID.  In the latest
> OData 4.01 spec the header name was changed to just Isolation and
> EntityID.  The OData- prefixed versions are still supported for backwards
> compatibility.
>

Okay; I was probing to find out if this superseded the previous header, but
it sounds like you expect both to be used at least during the compatibility
period.


> This change was made based on feedback for users and implementors of the
> OData standard.  I gather your preference would be that we use the
> OData-prefixed version for the registrations.  If so I will need to discuss
> that with the TC and get back to you.
>
>
>

While that would be my personal preference, it is simply that:  my opinion
as an individual.  I'm primarily concerned that other, unregistered or
pre-registration uses of these more general concepts may occur.  While
recording them in the registry will help avoid collisions, there is always
some risk and the more general the term, the higher the risk.

regards,

Ted Hardie


> Mark Biamonte
>
> Progress Software
>
> Morrisville, NC
>
>
>
> ---------- Forwarded message ----------
> From: *Ted Hardie* <ted.ietf@gmail.com>
> Date: Wed, Aug 29, 2018 at 2:58 PM
> Subject: Re: [Ietf-message-headers] Registration request for EntityId,
> Isolation, OData-MaxVersion, and OData-Version
> To: Chet Ensign <chet.ensign@oasis-open.org>
> Cc: ietf-message-headers@ietf.org, "Mark Biamonte (Progress)" <
> Mark.Biamonte@progress.com>
>
> Hi Chet,
>
>
>
> I'm a little confused on one point.  The Isolation header states that it
> was called OData-Isolation in version 4.0, but the linked ABNF document
> says:
>
>
>
> isolation  = [ "OData-" ] "Isolation" ":" OWS "snapshot"
>
> That seems to indicate that both ODate-Isolation and Isolation are
> expected to be valid for this token.  The ABNF for EntityID is similar:
>
>
>
> entityid   = [ "OData-" ] "EntityID" ":" OWS IRI-in-header
>
>
>
> Can you clarify the intent here?  Are both expressions of this token
> expected to continue?
>
>
>
> In general, "Isolation" seems to be a very general concept, and the
> reservation of it, unadorned, for a single token use ("snapshot") is
> somewhat surprising compared to the more-obviously scoped OData-isolation.
> EntityID seems similar board in possible usage outside the OData
> specification.
>
>
>
> regards,
>
>
>
> Ted Hardie
>
>
>
> On Wed, Aug 29, 2018 at 11:17 AM, Chet Ensign <chet.ensign@oasis-open.org>
> wrote:
>
> This message contains the information needed for Permanent Registration of
> the OData specific request headers with IANA as covered in RFC 3864 -
> Registration Procedures for Message Header Fields.
>
>
>
> ---
>
>
>
> PERMANENT MESSAGE HEADER FIELD REGISTRATION TEMPLATE:
>
>
>
> Header field name:
>
>
>
> EntityId
>
>
>
> Applicable protocol:
>
>
>
> OASIS Open Data Protocol (OData)
>
>
>
> Status:
>
>
>
> Standard
>
>
>
> Author/Change controller:
>
>
>
> OASIS. Michael Pizzo (mikep@microsoft.com), Microsoft primary
> specification editor. Mark Biamonte (mark.biamonte@progress.com),
> Progress Software editor for registration template.
>
>
>
> Specification document(s):
>
> OData Version 4.01 Part 1: Protocol -
>
> http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-
> part1-protocol.html#sec_HeaderEntityIdODataEntityId
> <http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol..html#sec_HeaderEntityIdODataEntityId>
>
>
>
>
> Related information:
>
> The EntityId header was named OData-EntityId in OData version 4.0.
>
>
>
> ####
>
>
>
> Header field name:
>
>
>
> Isolation
>
>
>
> Applicable protocol:
>
>
>
> OASIS Open Data Protocol (OData)
>
>
>
> Status:
>
>
>
> Standard
>
>
>
> Author/Change controller:
>
>
>
> OASIS. Michael Pizzo (mikep@microsoft.com), Microsoft primary
> specification editor. Mark Biamonte (mark.biamonte@progress.com),
> Progress Software editor for registration template.
>
>
>
> Specification document(s):
>
> OData Version 4.01 Part 1: Protocol -
>
> http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-
> part1-protocol.html#sec_HeaderIsolationODataIsolation
>
>
>
> Related information:
>
>        The Isolation header was named OData-Isolation in OData version 4.0.
>
>
>
>
>
> ####
>
>
>
> Header field name:
>
>
>
> OData-MaxVersion
>
>
>
> Applicable protocol:
>
>
>
> OASIS Open Data Protocol (OData)
>
>
>
> Status:
>
>
>
> Standard
>
>
>
> Author/Change controller:
>
>
>
> OASIS. Michael Pizzo (mikep@microsoft.com <mikep@microsoft..com>),
> Microsoft primary specification editor. Mark Biamonte (
> mark.biamonte@progress.com), Progress Software editor for registration
> template.
>
>
>
> Specification document(s):
>
>
>
> OData Version 4.01 Part 1: Protocol -
>
> http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-
> part1-protocol.html#sec_HeaderODataMaxVersion
>
>
>
> Related information:
>
>
>
> <none>
>
>
>
> ####
>
>
>
> Header field name:
>
>
>
> OData-Version
>
>
>
> Applicable protocol:
>
>
>
> OASIS Open Data Protocol (OData)
>
>
>
> Status:
>
>
>
> Standard
>
>
>
> Author/Change controller:
>
>
>
> OASIS. Michael Pizzo (mikep@microsoft.com), Microsoft primary
> specification editor. Mark Biamonte (mark.biamonte@progress.com),
> Progress Software editor for registration template.
>
>
>
> Specification document(s):
>
>
>
> OData Version 4.01 Part 1: Protocol -
>
> http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-
> part1-protocol.html#sec_HeaderODataVersion
>
>
>
> 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
>
>
>
>
>
>
>
> --
>
>
> /chet
> ----------------
>
>
>
> Looking forward to Borderless Cyber 2018
> <https://us18.borderlesscyber.org/en/>, 3-5 Oct, Washington, D.C.
>
> *Organized by The World Bank, OASIS, and Georgetown University*
>
>
>
> Chet Ensign
> Chief Technical Community Steward
> OASIS: Advancing open standards for the information society
> http://www.oasis-open.org
>
> 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
>
>