IETF Logo Mail Archive

[core] Re: Coreconf Notifications

Carsten Bormann <cabo@tzi.org> Thu, 25 July 2024 11:08 UTC

Return-Path: <cabo@tzi.org>
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 662F7C16941B; Thu, 25 Jul 2024 04:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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=ham autolearn_force=no
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 KodpzoCwLLQ6; Thu, 25 Jul 2024 04:08:43 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 A0928C18DBB8; Thu, 25 Jul 2024 04:08:37 -0700 (PDT)
Received: from [192.168.217.145] (p5dc5d6c5.dip0.t-ipconnect.de [93.197.214.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4WV7RQ5YgdzDCbv; Thu, 25 Jul 2024 13:08:34 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <0e37cbe90758409fae2a8f6763ffc986@swisscom.com>
Date: Thu, 25 Jul 2024 13:08:34 +0200
X-Mao-Original-Outgoing-Id: 743598514.331619-c077ce691e7aba2dca50d5c92ff98562
Content-Transfer-Encoding: quoted-printable
Message-Id: <C028C265-1624-4599-A0AC-64E075900275@tzi.org>
References: <E2DFFA8E-9766-4CB4-BCAA-6897402B8FB2@insa-lyon.fr> <5C0595E7-2071-4A6F-A0C8-6F9DE138535F@tzi.org> <C4AE55E1-0907-4BBD-A2BA-802063E10B50@insa-lyon.fr> <397772B6-6DAE-4A2D-BFD0-7A77ABE1415E@tzi.org> <E0D2CFE6-B0BD-4F0A-9F5C-4C29ADF16861@insa-lyon.fr> <CABCOCHT6B+9fjJL_UBArfcV1KO9SJBoV+588goWsDJ5_x_1x0A@mail.gmail.com> <0e37cbe90758409fae2a8f6763ffc986@swisscom.com>
To: "Thomas. Graf" <Thomas.Graf@swisscom.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Message-ID-Hash: ZRTI2OFCSOD7NI5T44MU2M7EDZ76BJEA
X-Message-ID-Hash: ZRTI2OFCSOD7NI5T44MU2M7EDZ76BJEA
X-MailFrom: cabo@tzi.org
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: Alex Huang Feng <alex.huang-feng@insa-lyon.fr>, draft-ietf-core-comi@ietf.org, core@ietf.org, Pierre Francois <pierre.francois@insa-lyon.fr>, Vivekananda Boudia <vivekananda.boudia@insa-lyon.fr>, 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/dttnHrOP1-w8_bjgE_RmHTaAthU>
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>

On 2024-07-24, at 21:27, Thomas.Graf@swisscom.com wrote:
> 
> We are proposing with https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang to define the transport agnostic notification header as mentioned in the last line of section 5 of charter 19.

There is a rather ominous line in the YANG:

> Implementations must support time zones.

This probably makes this YANG module inapplicable to CORECONF.

Does anyone know why this is in there?

Grüße, Carsten

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