[core] SID open comments/discussions before WGLC2

Ivaylo Petrov <ivaylo@ackl.io> Thu, 04 June 2020 09:27 UTC

Return-Path: <ivaylo@ackl.io>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0568C3A0B97 for <core@ietfa.amsl.com>; Thu, 4 Jun 2020 02:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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=ackl-io.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 UAqDrSQSCjju for <core@ietfa.amsl.com>; Thu, 4 Jun 2020 02:26:58 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 E01A33A0B98 for <core@ietf.org>; Thu, 4 Jun 2020 02:26:57 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id r9so4518308wmh.2 for <core@ietf.org>; Thu, 04 Jun 2020 02:26:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ackl-io.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=qKgpuWPY6JoimGLHzPKCl0KHm8lVq0RpTisWWky2ieU=; b=f5VOZBlqVh6gSWPWDlAMCE6JOh4zhgdQGe0HDuAHXj2kTSrvo9FqSJ/mOFNeFII3WA X80CaM9NbKaMpBPyLvxKSRzhYQ04Y9ygosGWpL/MQ+wcs31u1g2ynlRwvAd4605fLs5t 6PD5RbgbcPp3mLoukn3tLiJQ4dboexf/R7iInUw8OEIy3LWyKRlbids4iA0RV7LkaM3y ZkCURlApZM/5/613nTOsKAC2OEoy1tNGnO8uJCcHludK8hcCqIEF+TQEFrIUL69C077F V753Pda4xJPSRBU/R5SaoN8G3RBWYidVEeTMAZIGMNhU1Woa1h9pjZ55izfUenm5uXH/ g/Kg==
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=qKgpuWPY6JoimGLHzPKCl0KHm8lVq0RpTisWWky2ieU=; b=S7f+qaHwdYNFUo2z1WDF+VKfuPUXVz4pkmNj+b7kqEza8lk4ltR0TjOzcDbRqgIfOL UDAWa0Y8VUIWciiTmnPYnZyRRzKqU/zHkGDZ4f+9e9P4o0xojROQO57v43t34QjV8Nq5 +jo7R3bX2r24m1EZXzVSzKK0G7p0SPZbuc8TApV1fmc+slxd4idBKl8iHA7MBialoW5d aw7MemBoCM7KhuZWhFBT24a++L3jaYZB2Szk/c6aNyAIFG6FklCuHsmEN3N1zmwzOMne 02Os8FI/mhY8oFRvIagqfN9Qi+3qjClV+DzjyPVBG0/BW0mz7yeNax3LA39Ue2eccN4A 2J5g==
X-Gm-Message-State: AOAM531prqIINkIGVRKus4RRxBEhGwarEfAvKn+KZgVUacBgF7pF7Z9E D3Yh8ahkD4tL4nppFVx2Vk8orRNn3L+q23tiuc4gje+G3hQ=
X-Google-Smtp-Source: ABdhPJwdSDrrymsglcOYeM2B/TsSZabKY/Tl737UxdJY7k7/ndI9+NtaytmgD0kA2EBb5+3yUlEkhGtRu5AH0odc7JU=
X-Received: by 2002:a1c:4405:: with SMTP id r5mr3312148wma.72.1591262815588; Thu, 04 Jun 2020 02:26:55 -0700 (PDT)
MIME-Version: 1.0
From: Ivaylo Petrov <ivaylo@ackl.io>
Date: Thu, 04 Jun 2020 11:26:29 +0200
Message-ID: <CAJFkdRzoF9WZT2CV_et6kfZzPp9BaUi6Wsi=-EPTsfu5J8F1tQ@mail.gmail.com>
To: core <core@ietf.org>
Cc: core-chairs@ietf.org, Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="000000000000de277e05a73ebe0f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/ROEeM0GdaOhzG87zFmRgDqWcqkY>
Subject: [core] SID open comments/discussions before WGLC2
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2020 09:27:00 -0000

Dear all,

I apologize for the delay due to unforeseen personal and work-related extra
load.

My understanding is that with the latest revision -13, we have addressed
all pending comments (most notably the early allocation one). The only
items that were mentioned and not yet in the draft are:
- SID renaming to YSID suggested here [1]. I have discussed with some of
the other authors and we believe that could have an important negative
effect on existing code, plugins and changing the name now might bring
confusion in the community. We would like to have a better sense of
people's opinion on that.
- SID registries group name (there is a separate discussion [2]). I believe
it should not prevent WGLC2, but I might be wrong.
- Moving some content type into yang-cbor and sid drafts
  Problem statement: if anyone would want to use CBOR + SID representation
or CBOR + Names representation of YANG data, they need to have normative
reference to the CoMI document, which might appear unexpected.
  Proposed solution: as discussed [3] we can either move the media type and
content format registrations in the yang-cbor draft, but then it will have
a normative reference to the SID draft that we really wanted to avoid, or
we register CBOR + names in the yang-cbor and we register CBOR + SID in the
SID draft, but then we have normative reference in the opposite direction -
SID to yang-cbor. It appeared that people were more in favor of the latter
approach, so the changes that I thought this would need could be found at
[4]. I am not perfectly happy with this, so I would like to know the WG
opinion on how important this problem is to be resolved and whether we go
with the first option or the second one.

Best regards,
Ivaylo

[1]: https://mailarchive.ietf.org/arch/msg/core/OHkeVWB-q1Hd-52JGvWg9EfG3J0/
[2]: https://mailarchive.ietf.org/arch/msg/core/qE773yHGaxEskizf0rpbzMo7D78/
[3]: https://mailarchive.ietf.org/arch/msg/core/SiMRauO85o_0kyIvXExuslvnJ5Q/
[4]:
https://github.com/core-wg/yang-cbor/compare/content-format-moving?expand=1
  and
https://github.com/core-wg/comi/compare/content-format-moving?expand=1