[CDNi] CDNI C/I Triggers RFC8007bis - "v2"suffic in objects and properties names

Nir Sopher <nirsopher@gmail.com> Mon, 05 June 2023 04:10 UTC

Return-Path: <nirsopher@gmail.com>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61D0AC14CF1A for <cdni@ietfa.amsl.com>; Sun, 4 Jun 2023 21:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.084
X-Spam-Level:
X-Spam-Status: No, score=-2.084 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZG4B01XlRe_Y for <cdni@ietfa.amsl.com>; Sun, 4 Jun 2023 21:10:48 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96E49C14CEFC for <cdni@ietf.org>; Sun, 4 Jun 2023 21:10:48 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-53fdae76f3aso4014063a12.0 for <cdni@ietf.org>; Sun, 04 Jun 2023 21:10:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685938247; x=1688530247; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=3AQaM6HbjPprvqAq7IpkguuaoUiwXHvGMd7hbVhT/KI=; b=Uy+2RzheuEEakGNVUsDL4B9RzbPsj2mFro/REcdG4Gi6PLcTp2ElYIgzuv4YWoM9Zt w41fkw0HB5W/0s4N32Q8jP0u/ZMybzZG/+0gRK7cJe0jIgdPQnz3/FsLdG77QMKqtcja 3JhAHP4fKm6br6QInbnSboz1Xh7yWBhksQYPZAb6di5ERZWtgf2BI/W4r2R3lVqDKgAG hl6SOrUy0jUCiuK0ustH94A0Jv7Eg3dYwjjN42SLjGi9vRuUC7BgepwMVOcnzu9e5AYF 4bHhPyggFh3MQyopEgWgmzFvBVUPxEsZgA/oZQ3pyjJhrFHhbBPFwJwt8ffq/q9gYQZI kxqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685938247; x=1688530247; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=3AQaM6HbjPprvqAq7IpkguuaoUiwXHvGMd7hbVhT/KI=; b=OtwjUQXY0hotJ+W+8Kjwmgg6p0YvipjfFMs9Zm0c1deHSI8D6UrVx/H/nI6PBSc9PM j/JMXHPhuu6UY5BzN1P636CFuSl+LW6AObeY1TK89N2Ru+lCN4g+BQ+FcNahdg11N7mp hTVObpjj9et9JLJYK0uq+IRlyH1vtSFEw03aRr2zPrWpTa37fJOmOYC/EWjc1Ti1c1T4 hole06scNfGy/e8o+bSCQhmQQdmg/TQN3Lrto0Zyfn4LD6TSWqzFDVGMp5xVjOmKjBWR 0tpW2eLsirIJuN/NKL0d+k5kYA7vuD/7vbPUOYBVVfCZa9FludSDVg9LoQTNAoCJW6GL OPcA==
X-Gm-Message-State: AC+VfDyqegkbJzIx8EVgfwjCbVCWevg7qUgGXfcFHwqcApEUdSqQTBAb iTvgF831bVxPf2lL7oi0qncosCuuHgkCCkmkm39hUEsQLifA0Q==
X-Google-Smtp-Source: ACHHUZ6dwcggpsCz5HVJwxoJnvMUVjjvIx6FHH0SSFvCYI5qHY2Ck79YiU0rgSVfhN8dzJpwTfXx8y8si194xcqeIDM=
X-Received: by 2002:a17:90a:192:b0:256:33ba:8f65 with SMTP id 18-20020a17090a019200b0025633ba8f65mr6076868pjc.44.1685938247196; Sun, 04 Jun 2023 21:10:47 -0700 (PDT)
MIME-Version: 1.0
From: Nir Sopher <nirsopher@gmail.com>
Date: Mon, 05 Jun 2023 07:10:37 +0300
Message-ID: <CACUa7-uPrb-PHCtO88iEtr+WMyTP_gxSaF4mkyJ2T_+aX6o4Pw@mail.gmail.com>
To: cdni@ietf.org
Content-Type: multipart/alternative; boundary="00000000000056643b05fd5a1615"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/gwmFnIwQA7KK3Z5-jmTMNItDsp8>
Subject: [CDNi] CDNI C/I Triggers RFC8007bis - "v2"suffic in objects and properties names
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cdni/>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2023 04:10:52 -0000

Hi All,

We are in the final stages of aligning the "Control Interface Triggers 2nd
Edition" draft
<https://datatracker.ietf.org/doc/draft-ietf-cdni-ci-triggers-rfc8007bis/> -
preparing it for WG last call.
This 2nd edition obsoletes RFC 8007
<https://datatracker.ietf.org/doc/html/rfc8007>, mainly changing the
different objects structure - adding much flexibility and extensibility to
the Trigger object.

The nature of the change brought us to define a few "v2" objects:
command.v2, trigger.v2, status.v2, error.v2.
Furthermore API is now loaded with ".v2" in the names of the different
properties.

E.g.

   REQUEST:

     POST /triggers HTTP/1.1

     User-Agent: example-user-agent/0.1

     Host: dcdn.example.com

     Accept: */*

     Content-Type: application/cdni; ptype=ci-trigger-command*.v2*

     Content-Length: 387

     {

       "trigger*.v2*": {

         "action": "CIT.Invalidate",

....


We believe all the ".v2" in the properties names are not really required.

They can be deduced from the MIME media type. E.g. application/cdni;
ptype=ci-trigger-command*.v2*
I.e. removing the red "v2" and leaving only the green one

More specifically. we would suggest to:

   1. Add the "".v2" only to the objects' names in definition/registration.
      1.  High level objects (also having a matching MIME media ptype) -
      section 7.1
         - ci-trigger-command.v2
         - ci-trigger-status.v2
         - Potentially for consistency: ci-trigger-collection.v2.
         Note: that this object was not changed and it may also list "v1"
         triggers.
         *Thoughts?*
      2. Main objects
         - Trigger.v2
         - Error.v2
      2. The "v2" suffix would not be added to the name of the different
   properties.
   I.e. the "command.v2" object would include a "Trigger" property and not
   a "Trigger.v2" property
   3. Identification of the objects' version would be derived from the
   ptype version (indicating the version of the high level object). I.e.
   practically from the protocol version

Before aligning the draft, we would appreciate getting the WG opinion on
the matter.
Please Share your thoughts.

Sanjay & Nir