Re: [Dcrup] last call updated draft-ietf-dcrup-dkim-crypto-13

[Russ Housley <[e-mail]>]

That would resolve my issue completely.

Russ



> On Jun 18, 2018, at 5:45 PM, Scott Kitterman <[e-mail]> wrote:
> 
> OK.  Maybe added to the end of the paragraph in section 6:
> 
> Current:
> 
> 6.  Transition Considerations
> 
>   For backward compatibility, signers can add multiple signatures that
>   use old and new signing algorithms.  Since there can only be a single
>   key record in the DNS for each selector, the signatures have to use
>   different selectors, although they can use the same d= and i=
>   identifiers.
> 
> Proposed:
> 
> 6.  Transition Considerations
> 
>   For backward compatibility, signers can add multiple signatures that
>   use old and new signing algorithms.  Since there can only be a single
>   key record in the DNS for each selector, the signatures have to use
>   different selectors, although they can use the same d= and i=
>   identifiers.  Appendix A.3 shows an example message signed with both
>   ed25519-sha256 and rsa-sha256 with the same d= and i=, but unique
>   selectors (s=brisbane and s=test respectively).
> 
> Scott K
> 
> On Monday, June 18, 2018 05:38:55 PM Russ Housley wrote:
>> Frankly, I missed it.  The intro text to A.3 provides no hint that the
>> example is showing two signatures using different algorithms.
>> 
>> The text is repeated below so that other readers do not need to look it up.
>> 
>> Russ
>> 
>> = = = = = = = =
>> 
>> A.3.  Signed Message
>> 
>>   The text in each line of the message starts at the first position
>>   except for the continuation lines on the DKIM-Signature headers which
>>   start with a single space.  A blank line follows the "Joe." line.
>> 
>>   DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed;
>>    d=football.example.com; i=@football.example.com;
>>    q=dns/txt; s=brisbane; t=1528637909; h=from : to :
>>    subject : date : message-id : from : subject : date;
>>    bh=2jUSOH9NhtVGCQWNr9BrIAPreKQjO6Sn7XIkfJVOzv8=;
>>    b=/gCrinpcQOoIfuHNQIbq4pgh9kyIK3AQUdt9OdqQehSwhEIug4D11Bus
>>    Fa3bT3FY5OsU7ZbnKELq+eXdp1Q1Dw==
>>   DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>>    d=football.example.com; i=@football.example.com;
>>    q=dns/txt; s=test; t=1528637909; h=from : to : subject :
>>    date : message-id : from : subject : date;
>>    bh=2jUSOH9NhtVGCQWNr9BrIAPreKQjO6Sn7XIkfJVOzv8=;
>>    b=F45dVWDfMbQDGHJFlXUNB2HKfbCeLRyhDXgFpEL8GwpsRe0IeIixNTe3
>>    DhCVlUrSjV4BwcVcOF6+FF3Zo9Rpo1tFOeS9mPYQTnGdaSGsgeefOsk2Jz
>>    dA+L10TeYt9BgDfQNZtKdN1WO//KgIqXP7OdEFE4LjFYNcUxZQ4FADY+8=
>>   From: Joe SixPack <[e-mail]>
>>   To: Suzie Q <[e-mail]>
>>   Subject: Is dinner ready?
>>   Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
>>   Message-ID: <[e-mail]>
>> 
>>   Hi.
>> 
>>   We lost the game.  Are you hungry yet?
>> 
>>   Joe.
>> 
>>> On Jun 18, 2018, at 4:37 PM, Scott Kitterman <[e-mail]> wrote:
>>> 
>>> I think we have that in the current revision in Appendix A.3.  Do we need
>>> to specifically refer to that in Section 6?
>>> 
>>> Scott K
>>> 
>>> On Monday, June 18, 2018 04:23:09 PM Russ Housley wrote:
>>>> John:
>>>> 
>>>> How hard would it be to expand section 6 to include an example of two
>>>> selectors being used, one with RSA and one with ed25519?  If it is pretty
>>>> easy, I think it would help the reader.
>>>> 
>>>> Russ
>>>> 
>>>>> On Jun 15, 2018, at 8:19 PM, John R. Levine <[e-mail]> wrote:
>>>>> 
>>>>> I think the -13 addresses the last call comments.
>>>>> 
>>>>> Regards,
>>>>> John Levine, [e-mail], Primary Perpetrator of "The Internet for
>>>>> Dummies", Please consider the environment before reading this e-mail.
>>>>> https://jl.ly
>>>>> 
>>>>> _______________________________________________
>>>>> Dcrup mailing list
>>>>> [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/dcrup
>>>> 
>>>> _______________________________________________
>>>> Dcrup mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/dcrup
>>> 
>>> _______________________________________________
>>> Dcrup mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/dcrup
>> 
>> _______________________________________________
>> Dcrup mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/dcrup
> 
> _______________________________________________
> Dcrup mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dcrup