[netconf] type for a PSK's "id" node?

Kent Watsen <kent+ietf@watsen.net> Tue, 21 July 2020 14:44 UTC

From: Kent Watsen <kent+ietf@watsen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B5AD7110-ED08-4D09-9E2D-F2ECC91FFAC6"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Message-ID: <0100017371d59ad5-c8aa5683-34d7-4e76-b521-8482f67e33e4-000000@email.amazonses.com>
Date: Tue, 21 Jul 2020 14:44:51 +0000
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/hJG7Vly53rnFXWBVMk7B-UejKFc>
Subject: [netconf] type for a PSK's "id" node?
Precedence: list

Hi Henk,

I’m trying to close a couple issues on list before the meeting...

Below you’ll note the "is this the right type?” comment.  Currently the “id” node is type “string”, what type is used by TLS?


        case psk {
          if-feature psk-auth;
          container psk {
            description 
              "Specifies the server identity using a PSK (pre-shared
              or pairwise-symmetric key).";
            uses ks:local-or-keystore-symmetric-key-grouping {
              augment "local-or-keystore/local/local-definition" {
                if-feature "ks:local-definitions-supported";
                description
                  "Adds an 'id' value when the PSK is used by TLS.";
                leaf id {
                  type string;  // FIXME: is this the right type?
                  description
                    "The key id used in the TLS protocol for PSKs.";
                }   
              } 
            } 
          } 
        } 


K.

[netconf] type for a PSK's "id" node? Kent Watsen
Re: [netconf] type for a PSK's "id" node? Henk Birkholz