Re: [I2nsf] Murray Kucherawy's No Objection on draft-ietf-i2nsf-registration-interface-dm-25: (with COMMENT)

Hi Murray,
Thanks for your action on this draft.
Here are my answers inline below.

On Wed, May 10, 2023 at 3:06 AM Murray Kucherawy via Datatracker <
noreply@ietf.org> wrote:

> Murray Kucherawy has entered the following ballot position for
> draft-ietf-i2nsf-registration-interface-dm-25: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to
> https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
> for more information about how to handle DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
>
> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-registration-interface-dm/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> The shepherd writeup seems to have skipped answering part of the first
> question: Why is this the right document status?
>
 => [PAUL] I believe that our I2NSF Chair, Linda Dunbar, will be able to
update the writeup.

>
> I'm also confused by the answer to question 18.
>
 => [PAUL] I believe that our I2NSF Chair, Linda Dunbar, will be able to
update the writeup too.

>
> [copied from my otherwise-resolved DISCUSS]
>
> It also makes me wonder if this shouldn't be updating some other document
> if
> you're extending required behavior of an I2NSF component that was defined
> someplace else.

 => [PAUL] We proved the concept of our updates of this draft through
     the IETF-116 I2NSF Hackathon Project:

https://github.com/IETF-Hackathon/ietf116-project-presentations/blob/main/IETF116-I2NSF-Hackathon-Project.pdf

> I looked around for a document defining "security controller"
> and couldn't find an obvious one, so I'm at a loss for what to suggest.
>
 => [PAUL] Security Controller is defined as Network Management Operator
System (in RFC 8329, https://www.rfc-editor.org/rfc/rfc8329)
      in Introduction of this draft as below:

https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-registration-interface-dm-25#name-introduction

     In RFC 8329, Network Operator Management System is used, so I will
update the term for Security Controller
     with Network Operator Management System in the Introduction of this
draft.

      If you have further questions or comments, please let me know.

      Thanks for your comments.

      Best Regards,
      Paul

>
>
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>