IETF Logo Mail Archive

Re: [core] 答复: [netmod] CORE-SID and SX:structure and draft-ietf-anima-rfc8366bis-01.txt

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 12 January 2023 16:09 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 2B4CFC153CDC; Thu, 12 Jan 2023 08:09:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=sandelman.ca
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 N0gJiCCSCqpt; Thu, 12 Jan 2023 08:09:42 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96564C153CBB; Thu, 12 Jan 2023 08:09:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 489AE38993; Thu, 12 Jan 2023 11:38:26 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wNSz0ynJvJqR; Thu, 12 Jan 2023 11:38:23 -0500 (EST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id CA7B238991; Thu, 12 Jan 2023 11:38:23 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1673541503; bh=PHFYjqK0LSQ3sWMbD0oHD5s2R4FURRYBMZIqNtMSlX8=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=uatfkra+Pr961I87QEOiebAnUDWkrFqRJdNFfzM8VqjasHeP/nXIZdaCEJkvdaot1 cAU1xEC8UU4cEn7uqKTWpE+KodrjFLgP6uyAc3Y+8l849i26mVBIN0KFY5xV1E2Ol2 QB29UaDtW7m8sd/WFwYLv29zQ2ajBB8B2qvrdq7kpKVOkol4S0TYVsKO+q69rAcAlI pgSSOX81o00AlPn2jog6Zhmhwl5eQbAViPP2Jx1S8FUHOhqSIsvk1c+///BrFNTc6g w4FX8gklhj6al+cR4rfUSKWHrlX6F5EQ2i0kXRk8Iv13tC8UFdD/g9nEPB5VPgEUIA J17rOiQuv3ziA==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E13152A2; Thu, 12 Jan 2023 11:09:36 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Fengchong (frank)" <frank.fengchong@huawei.com>
cc: "anima@ietf.org" <anima@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, "core@ietf.org" <core@ietf.org>
In-Reply-To: <d62956f1f724460bbf12291b92d43f8b@huawei.com>
References: <167345911024.15670.5822349028239537605@ietfa.amsl.com> <18071.1673461082@localhost> <d62956f1f724460bbf12291b92d43f8b@huawei.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 12 Jan 2023 11:09:36 -0500
Message-ID: <19176.1673539776@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/6JMTvWiMlh7oYNg_n3D1Ix6pQe4>
Subject: Re: [core] 答复: [netmod] CORE-SID and SX:structure and draft-ietf-anima-rfc8366bis-01.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
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, 12 Jan 2023 16:09:46 -0000

Fengchong (frank) <frank.fengchong@huawei.com> wrote:
    > Hi Michael,
    > You can use augment-structure to extend a yang structure.

You can't use augment-structure to extend in-place an existing yang structure
Augment-structure produces a new structure with a new name that has been extended.

Perhaps you'd like to go back in the archives and read my postings, and try
out the pyang scripts labelled A/B/C/D.  Perhaps you have some insight that
makes this process unneeded, and if so, great.

    > TL;DR> we can not use augment to get the behaviour that we want of being to
    > extend existing YANG modules with new attributes.  We have to revise
    > 8366 each time we want extend things.  This email details the work to
    > make that occur.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

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