IETF Logo Mail Archive

[core] Re: Coreconf Notifications

Alex Huang Feng <alex.huang-feng@insa-lyon.fr> Fri, 19 July 2024 22:38 UTC

Return-Path: <alex.huang-feng@insa-lyon.fr>
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 88552C14CE45; Fri, 19 Jul 2024 15:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.438
X-Spam-Level:
X-Spam-Status: No, score=-0.438 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, HTML_MESSAGE=0.001, RCVD_HELO_IP_MISMATCH=2.368, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=insa-lyon.fr
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 xA6msX4Fl5Eh; Fri, 19 Jul 2024 15:38:25 -0700 (PDT)
Received: from smtpout02-ext4.partage.renater.fr (smtpout02-ext4.partage.renater.fr [194.254.241.31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2168FC14CE3B; Fri, 19 Jul 2024 15:38:17 -0700 (PDT)
Received: from zmtaauth02.partage.renater.fr (zmtaauth02.partage.renater.fr [194.254.241.25]) by smtpout20.partage.renater.fr (Postfix) with ESMTP id 6D2DCC0266; Sat, 20 Jul 2024 00:38:10 +0200 (CEST)
Received: from zmtaauth02.partage.renater.fr (localhost [127.0.0.1]) by zmtaauth02.partage.renater.fr (Postfix) with ESMTPS id 5F113A00B4; Sat, 20 Jul 2024 00:38:10 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zmtaauth02.partage.renater.fr (Postfix) with ESMTP id 4C896A06D7; Sat, 20 Jul 2024 00:38:10 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.10.3 zmtaauth02.partage.renater.fr 4C896A06D7
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=insa-lyon.fr; s=CB289C06-95B8-49FE-9C4B-D197C6D2E7CB; t=1721428690; bh=hdRUaTaVdzmfhGiyE8cquOiQg5qACQMCv46fRxJKKKE=; h=From:Message-Id:Mime-Version:Date:To; b=ZA0B8uAW2vjjjjkd3OpUuNOgq/kic8KZ234C5YAVxThEp99eyS1c+J4kZ9fuFUwmG /2NCX0hv/5SLtD0G47VPaTxJkrsm1arXzj6Vrj64WNL3KXIqSjbUJVezno2c0tmT0V 6XL6CT18+hjAgmx+lrpKqTqbAYrz5NmbF7JeulkpionMaHGjneq0Lt35MA5WBKmAqT TWwCb0c2hHg1mc1+DWKzMhVCHfZI861pjLeOldRE8pGQ0lhOVPxOHLOy0zOLIwQQNF ysHFzBv99UsiVU4KjanGQGEEHVwmJYUIxa5v4/gXynG1re/rFyyKMcKcKrVk4u9MBd pZWHE4M9A9NMQ==
Received: from zmtaauth02.partage.renater.fr ([127.0.0.1]) by localhost (zmtaauth02.partage.renater.fr [127.0.0.1]) (amavis, port 10026) with ESMTP id Q05lLlRbzQZY; Sat, 20 Jul 2024 00:38:10 +0200 (CEST)
Received: from 24.109.167.30 (unknown [194.254.241.249]) by zmtaauth02.partage.renater.fr (Postfix) with ESMTPA id AE561A00B4; Sat, 20 Jul 2024 00:38:08 +0200 (CEST)
From: Alex Huang Feng <alex.huang-feng@insa-lyon.fr>
Message-Id: <C4AE55E1-0907-4BBD-A2BA-802063E10B50@insa-lyon.fr>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BFA49541-86FC-4095-9034-E4B93AE55A0F"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Date: Fri, 19 Jul 2024 15:37:55 -0700
In-Reply-To: <5C0595E7-2071-4A6F-A0C8-6F9DE138535F@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
References: <E2DFFA8E-9766-4CB4-BCAA-6897402B8FB2@insa-lyon.fr> <5C0595E7-2071-4A6F-A0C8-6F9DE138535F@tzi.org>
X-Mailer: Apple Mail (2.3774.600.62)
X-Virus-Scanned: clamav-milter 0.103.8 at clamav03
X-Virus-Status: Clean
X-Renater-Ptge-SpamState: clean
X-Renater-Ptge-SpamScore: -100
X-Renater-Ptge-SpamCause: gggruggvucftvghtrhhoucdtuddrgeeftddrhedvgddufecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucftgffptefvgfftnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhkfgtggfuffgjvefvfhfosegrtdhmrehhtdejnecuhfhrohhmpeetlhgvgicujfhurghnghcuhfgvnhhguceorghlvgigrdhhuhgrnhhgqdhfvghnghesihhnshgrqdhlhihonhdrfhhrqeenucggtffrrghtthgvrhhnpeekgeegveetffeitdeuueekudeivdevheefledthfeiteektefghfekgedthfehfeenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppeduleegrddvheegrddvgedurddvgeelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepudelgedrvdehgedrvdeguddrvdegledphhgvlhhopedvgedruddtledrudeijedrfedtpdhmrghilhhfrhhomheprghlvgigrdhhuhgrnhhgqdhfvghnghesihhnshgrqdhlhihonhdrfhhrpdhnsggprhgtphhtthhopeejpdhrtghpthhtoheptggrsghosehtiihirdhorhhgpdhrtghpthhtohepughrrghfthdqihgvthhfqdgtohhrvgdqtghomhhisehivghtfhdrohhrghdprhgtphhtthhopegtohhrvgesihgvthhfrdhorhhgpdhrtghpthhtohepphhivghrrhgvrdhfrhgrnhgtohhishesihhnshgrqdhlhihonhdrfhhrpdhrtghpthhtohepvhhivhgvkhgr nhgrnhgurgdrsghouhguihgrsehinhhsrgdqlhihohhnrdhfrhdprhgtphhtthhopefvhhhomhgrshdrifhrrghfsehsfihishhstghomhdrtghomh
Message-ID-Hash: MXYMMD6VMESMSEUC7AXI6FR2434V75SI
X-Message-ID-Hash: MXYMMD6VMESMSEUC7AXI6FR2434V75SI
X-MailFrom: alex.huang-feng@insa-lyon.fr
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-core.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-core-comi@ietf.org, core@ietf.org, Pierre Francois <pierre.francois@insa-lyon.fr>, Vivekananda Boudia <vivekananda.boudia@insa-lyon.fr>, "Thomas. Graf" <Thomas.Graf@swisscom.com>, Benoit Claise <benoit.claise@huawei.com>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [core] Re: Coreconf Notifications
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Nch4qaE44Uzn7D3cM4Z6VW3yAaU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Owner: <mailto:core-owner@ietf.org>
List-Post: <mailto:core@ietf.org>
List-Subscribe: <mailto:core-join@ietf.org>
List-Unsubscribe: <mailto:core-leave@ietf.org>

Dear Carsten,

Thanks for the pointers, will check out this draft. My text does not state that the timestamp needs to be encoded as text-encoded date-time.
Are you suggesting that the draft should state the usage of tags for date-times? For implementations that does not support tags, isn’t it contra-productive?

Regarding the SIDs, the .sid file proposed in https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang-05#name-sid-file isn’t it sufficient?
I recall checking with you that this was the only thing needed in terms of SID allocations.

Other than this, my main question on this thread was regarding why in CBOR, the eventTime does not exist.
I am missing some consistency between how we encode YANG data in XML, JSON and CBOR and was wondering why CBOR was not following the same structure.
- RFC7950 defines that the structure of RFC5277 is used (root container with eventTime leaf)
- RFC7951, does not address this structure
- RFC9254 notifications are container-like instances and therefore, they don’t have the eventTime leaf

Regards,
Alex

> On 18 Jul 2024, at 14:12, Carsten Bormann <cabo@tzi.org> wrote:
> 
> On 18. Jul 2024, at 17:56, Alex Huang Feng <alex.huang-feng@insa-lyon.fr> wrote:
>> 
>> In https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang-05#name-cbor-structure we define how we expect the CBOR message to be encoded.
> 
> I’d say:
> Get SIDs for all of these names.
> 
> (And read [1] for how to get rid of the text-encoded date-time.)
> 
> Grüße, Carsten
> 
> 
> [1]: https://www.ietf.org/archive/id/draft-bormann-cbor-yang-standin-00.html

v2.46.0 | Report a Bug | By Email | System Status