Re: [I2nsf] Request for I2NSF Draft Review

["Mr. Jaehoon Paul Jeong" <[e-mail]>]

Hi Jung-Soo,
I have posted the revision of Consumer-Facing Interface YANG Data Model
Draft
by reflecting all your comments:
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-consumer-facing-interface-dm-22

Here are my answers and actions with the prefix [PAUL] inline below.

On Mon, Jul 25, 2022 at 12:20 PM Jung-Soo Park <[e-mail]> wrote:

> Hi  All,
>
> I reviewed the "I2NSF Consumer Facing Interface YANG Data Model ."
> This draft is well done for moving forward.
>
> There are some editorial comments below:
>
> [Abstract in Page 1]
> In here, the "an administrative domain" is used just one time.
> The definition of "administrative domain" should be provided in
> appropriate chapter.
> Or please give the example like I2NSF User group.
>
>   => [PAUL] I reflect your comment as follows:
    - OLD: an administrative domain
    - NEW: an administrative domain (e.g., user group)


> [Chapter 3.2 in Page 8]
> "VoCN" acronym is used at first.
> So, full words should be provided about the "VoCN."
> and related references should be also described in the reference chapter.
>
>   => [PAUL] I reflect your comments along with references as follows:
    - OLD:
       This information can be used to filter a caller id or
       receiver id to prevent any VoIP or VoCN exploits or attack.

    - NEW:
       This information can be used to filter a caller id or
       receiver id in order to prevent any exploits (or attacks)
       of Voice over IP (VoIP) or Voice over Cellular Network
       (VoCN).  Note that VoCN can be either Voice over LTE
       (VoLTE) [TR-29.949-3GPP] or Voice over 5G (Vo5G) [TR-21.915-3GPP].

[Chapter 4.4 in Page 14]
> "The URLn-Group object SHALL have ~~~~" was described.
> "URLn-Group" is maybe typo of "URL-Group."
>
>   => [PAUL] I correct the typo.


> [Chapter 5.1 in Page 15]
> I think that "Signatures" should be kept carefully in a secure manner.
> This draft said that this issue is out of scope.
>
> Even though this issue is out of scope, this draft should show the proper
> references.
> I think that the DID, blockchain, and etc are good solutions.
>
>   => [PAUL] I reflect your comments along with references as follows:
   - OLD:
     The examples of signature types are "YARA", "SURICATA", and "SNORT"
     [YARA][SURICATA][SNORT].

   - NEW:
     The examples of signature types are "YARA", "SURICATA", and "SNORT"
     [YARA][SURICATA][SNORT].  "Signatures" should be kept carefully in
     a secure manner.  The secure keeping of "Signatures" can be
     performed by Defense in Depth (DID) [DID] or Distributed Ledger
     Technology (DLT) such as Blockchain [Bitcoin].  The details of keeping
      "Signatures" securely are out of scope in this document.


> [Chapter 12.1 in Page 69]
> - xxx-semantics-19.txt >> RFC9110
>
 => [PAUL] I reflect your comment.
    - OLD: draft-ietf-httpbis-semantics-19
    - NEW: RFC 9110

    - OLD: draft-ietf-httpbis-messaging-19
    - NEW: RFC 9112

- xxx-monitoring-data-model-19.txt >> xxx-monitoring-data-model-20.txt
>
  => [PAUL] I reflect your comment.
    - OLD: draft-ietf-i2nsf-nsf-monitoring-data-model-18
    - NEW: draft-ietf-i2nsf-nsf-monitoring-data-model-20

    - OLD: draft-ietf-i2nsf-capability-data-model-31
    - NEW: draft-ietf-i2nsf-capability-data-model-32
>
>
> [Chapter 12.1 in Page 70]
> - xxx-rfc4960-bis-19.txt >> RFC9260
>
  => [PAUL] I reflect your comment.
    - OLD: draft-ietf-httpbis-http2bis-07
    - NEW: RFC 9113

    - OLD: draft-ietf-tsvwg-rfc4960-bis-19
    - NEW: RFC 9260

   => [PAUL] Thanks for your valuable comments.

        Best Regards,
        Paul

Thanks.
>
> Best Regards,
> Jungsoo, PARK
>
>
> On Mon, Jul 25, 2022 at 10:32 PM 최윤철 <[e-mail]> wrote:
>
>> Hi  I2NSF WG,
>>
>> I reviewed the I2NSF Registration Interface YANG Data Model.
>> This draft is  well written and ready to be progressed for publication.
>>
>> One comment below.
>>
>> In '4.1.2. NSF access Information' an example of access information is
>> described by including VLAN.
>> But, in '5 Data Model' NSF access information, it was described only with
>> IP and port.
>> It would be good to add VLAN as an option in '5 Data Model' NSF access
>> information
>>
>>
>>
>> -----Original Message-----
>> From: "Mr. Jaehoon Paul Jeong" <[e-mail]>
>> To: "Penglin Yang" <[e-mail]>; "Meiling Chen" <
>> [e-mail]>;
>> Cc: "JungSoo Park" <[e-mail]>; "Yunchul Choi" <[e-mail]>;
>> "Patrick Lingga" <[e-mail]>; "Jeong Hyeon Kim" <
>> [e-mail]>; "Mr. Jaehoon Paul Jeong" <
>> [e-mail]>;
>> Sent: 2022-07-19 (화) 20:49:27 (UTC+09:00)
>> Subject: Request for I2NSF Draft Review
>>
>> Hi Penglin and Meiling,
>> How are you nowadays?
>>
>> I need reviewers for I2NSF Consumer Facing Interface YANG Data Model and
>> I2NSF Registration Interface YANG Data Model under I2NSF WGLC:
>>
>> -  I2NSF Consumer Facing Interface YANG Data Model
>>
>> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-consumer-facing-interface-dm-21
>>
>> -  I2NSF Registration Interface YANG Data Model
>>
>> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-registration-interface-dm-18
>>
>> Could each of you review one of them, respectively, this week?
>>
>> If you can do it, you can give your review comments to the I2NSF mailing
>> list.
>>
>> With this review, it will be helpful for you to proceed with
>> our I2NSF remote attestation draft.
>>
>> Thanks.
>>
>> Best Regards,
>> Paul
>> --
>> ===========================
>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>> Associate Professor
>> Department Head
>> Department of Computer Science and Engineering
>> Sungkyunkwan University
>> Office: [phone]
>> Email: [e-mail], [e-mail]
>> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>> _______________________________________________
>> I2nsf mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/i2nsf
>>
>