Re: [I2nsf] WGLC for draft-ietf-i2nsf-registration-dm-17

Donald Eastlake <d3e3e3@gmail.com> Fri, 05 August 2022 17:37 UTC

Return-Path: <d3e3e3@gmail.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 B05B3C157B53 for <i2nsf@ietfa.amsl.com>; Fri, 5 Aug 2022 10:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level:
X-Spam-Status: No, score=-1.855 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=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 PzlMm35hquJq for <i2nsf@ietfa.amsl.com>; Fri, 5 Aug 2022 10:36:58 -0700 (PDT)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 E81E9C14CF13 for <i2nsf@ietf.org>; Fri, 5 Aug 2022 10:36:58 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id x9so60994ljj.13 for <i2nsf@ietf.org>; Fri, 05 Aug 2022 10:36:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc; bh=vq/f82B49cJ0Xu4xALgkjS3E7E8OBi7v6xmh/53Kbb0=; b=m4dy8wqF8muS/CgtipNMDoHQCtWVng7rKZOf8sANUyv4k0vHutPXFBmJviVby/bJnr tJ7qhUpZuhPFPuT1KicsVywKVmNY3oBqQsnWCUSuaQWYZBzN+BGQlIFowRAPWqwpu170 ZZTC9ND9c5PJLWO4y987uPXc3IWerNYThLCWtGAYcTQr+xRQz10WqCoWLHYSlzRpIPni UbJtna3rZWR3mHb7I0w+ZjPRp/QxemfY1RlGwgEJzO3pOt9ZSyIgu0grSGN6Y31GE9R/ PchCCmnvRXwg9ygdOXgrjxAkVx7J4sDko9L2MpK/U0HUOLTP+lAy+tSb9L8nIge514LI eVdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc; bh=vq/f82B49cJ0Xu4xALgkjS3E7E8OBi7v6xmh/53Kbb0=; b=N5SdP/yg7ekwsbbWWs9LKy8sh8M9ujQkPhBsLHPL4mZIqsMKiRyohIdYBEEuy9UrOX 5raKKBoC8YjrABmhp3lPHDljf+Ek8xToMqFpUXhLjxzR49lh07PSehMTLdbk5hQIjUrr v55CEbUJp1+ZGr0c+AbIZ8lrnHZWjdGZDPwuWrUaucA66gfvn5tPrAvfK+5ujWvHPFWM ydZ8YNDRvjtspFx/6rhdxxAXCrFuxiEOhU0PSMz6hgpuEo9FX3Ao1wUrPq9Nc5WqEDS0 vOnoSy0u1BPNApYJ32eU1Qm8eqeNbHvGtIGIRH6SatE5Ut7Ku0aBeDa/DOCh1lcSDftc YVlQ==
X-Gm-Message-State: ACgBeo1AbNd6kRVTP1WXrUBV/RlX9h4rGKa1PICJjFcvOMONz28z0D15 q6hz4/cZ5ZpIyjx7q+8NOSdiCOWPchJEW6/8D3pYspky1pU=
X-Google-Smtp-Source: AA6agR53fXRLrab6sFzwjm5Gq+7ZLxShBWGohsVedxsLx0aQgCq/yL8twVPdRua8eUGqsstQy7hCiVKulTHT2qUfqeM=
X-Received: by 2002:a2e:83c9:0:b0:24d:a95d:7b7a with SMTP id s9-20020a2e83c9000000b0024da95d7b7amr2341157ljh.254.1659721016022; Fri, 05 Aug 2022 10:36:56 -0700 (PDT)
MIME-Version: 1.0
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 05 Aug 2022 13:36:44 -0400
Message-ID: <CAF4+nEH=1R5JNVpEc65aEGmFDQuVA0zE0g-FiTAu_ChJ12FGzg@mail.gmail.com>
To: i2nsf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000961a4405e581e9f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/PJn1vmRJetPMhN9lgFlOs9Z5sfo>
Subject: Re: [I2nsf] WGLC for draft-ietf-i2nsf-registration-dm-17
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 05 Aug 2022 17:37:02 -0000

I have looked at this draft and support publication. (Well, actually I
looked at draft-ietf-i2nsf-registration-interface-19.)

I like the clear top-down data model

Some minor suggestions:

Section 1: Expand DMS on first occurrence (it is currently expanded on 2nd
occurance)

Section 2: Maybe add a reference for OSI: "ISO/IEC 7498-4:1989 --
Information technology -- Open Systems Interconnection -- Basic Reference
Model: Naming and addressing".

Section 4.1.1.1, in the last two sentences: "two cases, outbound, inbound."
-> "two cases: outbound and inbound." and "two information can" -> "two
information items can".

Section 5.1.2, at the top of page 9: "following purposes." -> "following
purposes:"

Section 7 (three times): "illegally modifying this" -> "modifying this
without authorization".

Section 7: "deteriorate" -> "reduce"

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

On Sat, Jun 11, 2022 at 3:13 AM Linda Dunbar
<linda.dunbar@futurewei.com> <&lt;linda.dunbar@futurewei.com&gt;>
wrote:
Hello Working Group,

Many thanks to the authors of draft-ietf-i2nsf-registration-dm-17 to
address all the comments from YANG Doctor review, SecDir review and
OpsDIR review.

This email starts a three weeks Working Group Last Call on
draft-ietf-i2nsf-registration-dm-17
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-registration-interface-dm/

This poll runs until July 1, 2021.

We are also polling for knowledge of any undisclosed IPR that applies
to this Document, to ensure that IPR has been disclosed in compliance
with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more
details).
If you are listed as an Author or a Contributor of this Document,
please respond to this email and indicate whether or not you are aware
of any relevant undisclosed IPR. The Document won't progress without
answers from all the Authors and Contributors.

If you are not listed as an Author or a Contributor, then please
explicitly respond only if you are aware of any IPR that has not yet
been disclosed in conformance with IETF rules.

Thank you.

Linda