Re: [netconf] Adoption-suitability for draft-kwatsen-netconf-sztp-csr

Hi,

I am trying to understand the problem addressed in this draft.
It appears to be a well-constrained enhancement to SZTP to provide
more data in the get-bootstrapping-info RPC.

It is not clear that NETCONF WG is the right place for this draft, but
given the co-authors involved I think it will get sufficient security area
review.

I am willing to review the draft (wrt/ RESTCONF related issues).
I may implement it in the future, but no plans now.

Andy

On Wed, Aug 5, 2020 at 3:19 PM Kent Watsen <kent+ietf@watsen.net> wrote:

>
> NETCONF WG,
>
> Per the previous email sent moments ago, the chairs would like to solicit
> input on the following draft:
>
>    Title: Conveying a CSR in an SZTP Bootstrapping Request
>    Link: https://tools.ietf.org/html/draft-kwatsen-netconf-sztp-csr
>    Abstract:
>
>       This draft extends the "get-bootstrapping-data" RPC defined in
>       RFC 8572 to include an optional certificate signing request (CSR),
>       enabling a bootstrapping device to additionally obtain an identity
>       certificate (e.g., an LDevID, from IEEE 802.1AR) as part of the
>       "onboarding information" response provided in the RPC-reply.
>
>
> In particular, please discuss adoption-suitability as it regards to the
> following questions:
>
>     1) is the problem important for the NETCONF WG to solve?
>     2) is the draft a suitable basis for the work?
>
>
> PS: this message is itself not an adoption poll, but rather an attempt to
> gauge interest/support for a potential future adoption poll.
>
> NETCONF Chairs
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>