Re: [I2nsf] Request for Comments, Interest and Support in I2NSF Re-Chartering
Susan Hares <shares@ndzh.com> Sat, 26 March 2022 14:49 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB1853A0C4A for <i2nsf@ietfa.amsl.com>; Sat, 26 Mar 2022 07:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.062
X-Spam-Level:
X-Spam-Status: No, score=-4.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 v1fFRurXgjEZ for <i2nsf@ietfa.amsl.com>; Sat, 26 Mar 2022 07:49:55 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 B37B93A0C3B for <i2nsf@ietf.org>; Sat, 26 Mar 2022 07:49:55 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.107.114.225;
From: Susan Hares <shares@ndzh.com>
To: 't petch' <ietfa@btconnect.com>, "'Mr. Jaehoon Paul Jeong'" <jaehoon.paul@gmail.com>, i2nsf@ietf.org
Cc: 'Roman Danyliw' <rdd@cert.org>, "'Panwei (William)'" <william.panwei@huawei.com>, 'Henk Birkholz' <henk.birkholz@sit.fraunhofer.de>, 'tom petch' <daedulus@btconnect.com>, 'yangpenglin' <yangpenglin@chinamobile.com>, 'DIEGO LOPEZ GARCIA' <diego.r.lopez@telefonica.com>
References: <CAPK2DewrhhvRbCMVPewnvj_QLtb-cE7J=ymGwQ2uBaq3sKCJeQ@mail.gmail.com> <623D85A3.5080900@btconnect.com>
In-Reply-To: <623D85A3.5080900@btconnect.com>
Date: Sat, 26 Mar 2022 10:49:17 -0400
Message-ID: <072401d84120$abe43bd0$03acb370$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQMu/UfM+LimZNCb8gb8woyF0Q2xvgGoP7/Mqhb8PwA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/Ct1ZMm7VJoah3SUO2JV9ormLc5k>
Subject: Re: [I2nsf] Request for Comments, Interest and Support in I2NSF Re-Chartering
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Mar 2022 14:49:58 -0000
Tom: Thank you for this feedback. This error in the model comes from the initial assumptions during the start of these models. This error was a design choice in the early models based on the flux in Yang during the NMDA model discussions. Benoit's advice was to try to get models out and then revise. The security ADs were pushing the working group to make progress. Benoit and the security ADs wanted progress. The tenant of "replication" works in that environment. Versioning in Yang models is still a work in progress. This round of versioning is still not complex enough for BGP policy modeling. (And IMHO/AFAIK Open Config Yang modeling is behind IETF modeling in complex versioning). Therefore, the error in that advice to Linda Dunbar and Paul Jeong is mine. Paul, his co-authors, and his students have done the best possible based on that advice. Time has moved on in both realms (netmod) and security. The current security ADs were not privy to these pieces of advice. Would you suggest going back to square-1 to rework each of these models? If so, should this be the first order of work? Just a warning, refactoring to remove the "replication" works best as Paul Jeong has done it. It is careful and precise work reviewed by a few experts. The working group reviews for high level content. Paul Jeong's presentation at IETF 113 gave that type of review. I wish we would have had a longer time period, but hybrid meetings shorten "off-line meetings". WGs focus on protocol content (routing or security WG) struggle to maintain moment cycling around refactoring. Combing the refactoring work with additional work helps keep a working group functional. Any advice? Sue Opinion: The IETF needs to strong cross-area management as we head into 5G work. Security in all areas is key for 5G needs. -----Original Message----- From: t petch [mailto:ietfa@btconnect.com] Sent: Friday, March 25, 2022 5:05 AM To: Mr. Jaehoon Paul Jeong; i2nsf@ietf.org Cc: Roman Danyliw; Panwei (William); Henk Birkholz; tom petch; yangpenglin; Susan Hares; DIEGO LOPEZ GARCIA Subject: Re: [I2nsf] Request for Comments, Interest and Support in I2NSF Re-Chartering On 24/03/2022 07:38, Mr. Jaehoon Paul Jeong wrote: > Hi I2NSF WG, > As you know, our I2NSF WG will discuss the I2NSF Re-Chartering > at IETF-113 I2NSF WG Session today. > > I attach the text of the re-chartering as pdf and txt files. Those that have worked on the current five I2NSF I-D will know that they do not subscribe to the basic tenet of 'reference not replicate' and in doing so have created many issues of lack of coherence (some of which have been resolved, some of which may never be resolved) and have created much additional work. In a sense, the current work is built on foundations of sand, which may or may not support ongoing work. What is needed, and for me it is the overwhelming priority, before any new models are crafted, is a 'common' I-D to reduce or eliminate this replication even if it cannot be applied immediately to those five I-D. The current charter hints at the need for this in its bullets and in its list of deliverables. The terminology draft might have done this but has gone in a slightly different direction. Common YANG capability statements are an obvious example but even a common base of plain text would make the work simpler, less error-prone. Tom Petch > Our five core I2NSF YANG data model drafts are almost completed. > ---------------------------------------------------------------------------- -------- > 1. Capability YANG Data Model > https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-capability-data-model -27 > > 2. NSF-Facing Interface YANG Data Model > https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-nsf-facing-interface- dm-22 > > 3. Monitoring Interface YANG Data Model > https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-nsf-monitoring-data-m odel-16 > > 4. Consumer-Facing Interface YANG Data Model > https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-consumer-facing-inter face-dm-17 > > 5. Registration Interface YANG Data Model > https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-registration-interfac e-dm-15 > ---------------------------------------------------------------------------- -------- > > The three of them (i.e., 1, 2, and 3) got the feedback of the IESG and > the revisions have been sent to the IESG reviewers. > > The remaining two (i.e., 4, 5) are well-synchronized with the others. > I will present the updates of them today's I2NSF WG. > I attach the slides for them for your easy checking. > > Our AD Roman has concerns about the low energy of our I2NSF WG for the new > work items in the I2NSF Re-chartering. > > Could you speak up your voice about your comments, interest, and support of > our I2NSF Re-Chartering? > > See you online at IETF-113 I2NSF WG Session today. > > Thanks. > > Best Regards, > Paul > > > > _______________________________________________ > I2nsf mailing list > I2nsf@ietf.org > https://www.ietf.org/mailman/listinfo/i2nsf >
- Re: [I2nsf] Request for Comments, Interest and Su… 이재훈
- [I2nsf] Request for Comments, Interest and Suppor… Mr. Jaehoon Paul Jeong
- Re: [I2nsf] Request for Comments, Interest and Su… pjs@etri.re.kr
- Re: [I2nsf] Request for Comments, Interest and Su… 안태진(AI Security Service Proje)
- Re: [I2nsf] Request for Comments, Interest and Su… hyunsikYang
- Re: [I2nsf] Request for Comments, Interest and Su… 선경재
- Re: [I2nsf] Request for Comments, Interest and Su… 이재훈
- Re: [I2nsf] Request for Comments, Interest and Su… Diego R. Lopez
- Re: [I2nsf] Request for Comments, Interest and Su… 김평수/전자공학부/교원
- Re: [I2nsf] Request for Comments, Interest and Su… byyun
- Re: [I2nsf] Request for Comments, Interest and Su… YounHee Han
- Re: [I2nsf] Request for Comments, Interest and Su… t petch
- Re: [I2nsf] Request for Comments, Interest and Su… Susan Hares
- Re: [I2nsf] Request for Comments, Interest and Su… t petch
- Re: [I2nsf] Request for Comments, Interest and Su… yangpenglin@chinamobile.com
- Re: [I2nsf] Request for Comments, Interest and Su… Yong-Geun Hong