Re: [secdir] Secdir review of draft-ietf-i2nsf-consumer-facing-interface-dm-20

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Thu, 16 June 2022 13:48 UTC

Return-Path: <jaehoon.paul@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 418ACC14CF0C; Thu, 16 Jun 2022 06:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TX0X20OJ5Bdg; Thu, 16 Jun 2022 06:48:51 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 B84C1C14F741; Thu, 16 Jun 2022 06:48:51 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id o7so2928203eja.1; Thu, 16 Jun 2022 06:48:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Tpic8xiSf/aa90kowCJcNziGqNE75/KDQqdW/sJDn5Y=; b=FXF6iBWvQxD2vKFX5OTzDjUqq4hH3A5e6UfY6h9eUkP+LZOGKKR6xDQK/ALBa+cPfj Ng3cVoxBMHhrNyX73cPOwXBoJ+gpHgl8tVlkpnLRuG1rTxkxMoss92eI9JxmEEj2PISU og8KuMR+FOvJO37VttD2aB8e0aqGR4xxMgSloq01HUOTiJ5ZHF+uAPXSJ1yc8OWIJhnm j+hjaxP+ecv/ywflRbZFlQa2yf7rZb1fvqFGjx9Sz2WCAeG5Y0lW1JtSkqqcz8DdN4fY ksX5pulfgsP8mVt7s4wy25dIleh7y5NTFRNmusKM2g3WtNutc8ColotMraNZYm7NjUUB Yaig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Tpic8xiSf/aa90kowCJcNziGqNE75/KDQqdW/sJDn5Y=; b=FfQDHW9mtYkKEHUmeeg7QMQ3WGdTWfJu7KiigPYmgRhOFb62g3QxWmx/K2z28JDGAn oa56/sppqEeuonAlT6B1Nnw29Z81k0EkGom4pPvKDecrDUWaZkfhWs9PT5LREcTudO6z UZ67AvTitmOISdwacqtbHyWTZsQ4iOtPJ8JDA5ZYjlIC6nWPzejND+Y9iFgjVMaleXEz M+aiXn710WGrDyGlSDafqATCel0aZzB2BlbxUCGuufaCUrf2YoDp6EKazPa7+qZj9WaR enb6BPBVcaSbP5igCCsb0sIS7doBXJL3wEVvCc02rhytUTlSLOAgRusG1rAMiUsNyisQ V+ew==
X-Gm-Message-State: AJIora+wXXQXyeXzHXtfiYXGlYSUZrUpNWWJjUjmFbjisRamtetqMNmZ C3so424A6YG25x9SKgegsnWHPgvH98TQvrRushg=
X-Google-Smtp-Source: AGRyM1tiEsQ1E9YJtstkCaZqwEcsfeiKMY1cKA5V+uOz+hmf5U3dA6CWmI6MOHGenSgMfMFizHYj9Jw3mUXjL8Kru80=
X-Received: by 2002:a17:906:49d4:b0:6d6:e5ec:9a23 with SMTP id w20-20020a17090649d400b006d6e5ec9a23mr4624726ejv.79.1655387329564; Thu, 16 Jun 2022 06:48:49 -0700 (PDT)
MIME-Version: 1.0
References: <MW2PR1901MB4683A2797C0EFD44F403A5FFDFA89@MW2PR1901MB4683.namprd19.prod.outlook.com>
In-Reply-To: <MW2PR1901MB4683A2797C0EFD44F403A5FFDFA89@MW2PR1901MB4683.namprd19.prod.outlook.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Thu, 16 Jun 2022 22:48:12 +0900
Message-ID: <CAPK2Dexk76w1wSxeija8opbrg8eqetB0BoiwCP=rkWs=GPOFqw@mail.gmail.com>
To: Charlie Kaufman <charliekaufman@outlook.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-i2nsf-consumer-facing-interface-dm.all@ietf.org" <draft-ietf-i2nsf-consumer-facing-interface-dm.all@ietf.org>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000be943905e190e5fa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/3xdQbRl2C31N61qUf4f8MtvCtnU>
Subject: Re: [secdir] Secdir review of draft-ietf-i2nsf-consumer-facing-interface-dm-20
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2022 13:48:52 -0000

Hi Charlie,
Thanks for your in-depth review on our Consumer-Facing Interface Draft.

I will correct the typo (Page 8: interuption -> interruption) in the
revision.

Thanks.

Best Regards,
Paul


On Sun, Jun 12, 2022 at 10:51 AM Charlie Kaufman <charliekaufman@outlook.com>
wrote:

> Reviewer: Charlie Kaufman
> Review result: Has nits
>
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the IESG.
> These comments were written primarily for the benefit of the security area
> directors.  Document editors and WG chairs should treat these comments just
> like any other last call comments.
>
> This document specifies a syntax for specifying security policies that
> apply in a networked environment. It is intended that general policies
> would be fed into the system in this syntax and then some policy engine
> would determine which policies need to be enforced by which nodes in the
> system and appropriate subsets would be distributed. The syntax takes the
> form of a YANG data model.
>
> The review result I wanted to give was "Mostly Harmless". I am skeptical
> as to whether the collection of policies specifiable is flexible enough to
> be usable to manage a real network, but the syntax is easily extensible and
> this seems as good a place to start as any. If it encourages
> experimentation with management systems that distribute policies this way,
> that would be a good thing, and any deficiencies found could be fixed
> later. I could imagine other groups having very different visions as to how
> to manage this information, but I would not expect the presence of this
> document as an RFC would discourage them from experimenting with those
> visions.
>
> I'm not sufficiently familiar with YANG or with Network Functions
> Virtualization to have a useful opinion as to how good this design is.
>
> I noticed one nit, which suggests they might want to run the document
> through a spelling checker. The nit is not worth holding the document up if
> no one finds anything else.
>
> Nits:
>
> Page 8: interuption -> interruption
>
> --Charlie
>
>