Re: [Last-Call] Last Call: <draft-moskowitz-ipsecme-ipseckey-eddsa-03.txt> (EdDSA value for IPSECKEY) to Proposed Standard

[Robert Moskowitz <rgm-ietf@xxxxxxxxxxxxxxx>]

    In reviewing sec 2 per Tero's comment, I caught that although we
    changed the sub-registery format in sec 3.1, I did not change it
    here in sec 2.  Thus I propose bring all this in line with:
    
       When using the EdDSA public key in the IPSECKEY RR, then the
    value
       TBD1 is used as an algorithm and the public key is formatted as
       specified in Section 3 of the "Edwards-Curve Digital Security
       Algorithm (EdDSA) for DNSSEC" ([RFC8080]) document.
    
       Value  Description                Format description    Reference
    
       TBD1   An EdDSA Public Key        [RFC8080], Sec. 3     [ThisRFC]
    
    
    thus Tero's text change and my adjusting the subregistry entry to
    match Tero's earlier change in sec 3.1
    
    Bob

On 11/15/22 17:28, Robert Moskowitz wrote:

One open item on -03 for me to consider.

Bob

-------- Forwarded Message --------

Subject:	Fwd: Last Call: <draft-moskowitz-ipsecme-ipseckey-eddsa-03.txt> (EdDSA value for IPSECKEY) to Proposed Standard
Date:	Tue, 15 Nov 2022 02:23:26 +0200
From:	Tero Kivinen <kivinen@xxxxxx>
To:	Robert Moskowitz <rgm@xxxxxxxxxxxxxxxxxxxx>
CC:

Robert Moskowitz writes:

you had comments on -03.

Can you please file them on this last call and then I can make them?

Here is my comment:

https://mailarchive.ietf.org/arch/msg/tm-rid/d9xgH1w-yoUA54qt9e2WbKRdi5Y/

I.e., change section 2 to:
----------------------------------------------------------------------
2. IPSECKEY support for EdDSA

When using the EdDSA public key in the IPSECKEY RR, then the value
TBD1 is used as an algorithm and the public key is formatted as
specified in Section 3 of the "Edwards-Curve Digital Security
Algorithm (EdDSA) for DNSSEC" ([RFC8080]) document.

-- 
kivinen@xxxxxx

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call