Re: [netconf] Zaheduzzaman Sarker's No Objection on draft-ietf-netconf-crypto-types-29: (with COMMENT)

[Kent Watsen <[e-mail]>]

Hi Zaheduzzaman,

Thank you for your comment.
Please find response below.

Kent


> On Feb 1, 2024, at 6:29 AM, Zaheduzzaman Sarker via Datatracker <[e-mail]> wrote:
> 
> Zaheduzzaman Sarker has entered the following ballot position for
> draft-ietf-netconf-crypto-types-29: 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-netconf-crypto-types/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks for working on this specification. I have no objection from transport
> protocol point of view.
> 
> I was wondering if the following description is sufficiently clear to the
> implementers -
> 
> leaf public-key-format {
>      nacm:default-deny-write;
>      type identityref {
>        base public-key-format;
>      }
>      mandatory true;
>      description
>        "Identifies the public key's format. Implementations SHOULD
>         ensure that the incoming public key value is encoded in the
>         specified format.";
>    }
> 
> Which format is specified here ? and how the implementation can ensure the
> compliance to the specific format for the incoming public key value?
> 
> I am missing some reference/example/direction here.

In this case, the “identityref” is to "public-key-format”.

"public-key-format” has two sub-identities:
	- subject-public-key-info-format
	- ssh-public-key-format

For subject-public-key-info-format, the “description” statement says:

     description
       "Indicates that the public key value is a SubjectPublicKeyInfo
        structure, as described in RFC 5280 encoded using ASN.1
        distinguished encoding rules (DER), as specified in
        ITU-T X.690.";

For ssh-public-key-format, the “description” statement says:

     description
       "Indicates that the public key value is an SSH public key,
        as specified by RFC 4253, Section 6.6, i.e.:
   
          string    certificate or public key format
                    identifier
          byte[n]   key/certificate data.";


Does this answer your question?


Kent