On Thu, May 5, 2016 at 10:49 AM, Stephen Farrell
wrote:
>
> Thanks all. I updated the RFC editor note to add the FIPS
> reference.
>
You might also consider mentioning the interop problems that are going
to occur when diverging from Bernstein's reference implementation. Its
already creating open
> On 5 May 2016, at 5:14 PM, Stephen Farrell wrote:
>
>
>
> On 24/04/16 17:23, Alexey Melnikov wrote:
>> Alexey Melnikov has entered the following ballot position for
>> draft-ietf-tls-chacha20-poly1305-04: Yes
>>
>> When responding, please keep the subject line intact and reply to all
>> ema
On Thu, May 5, 2016, at 03:33 PM, Dang, Quynh (Fed) wrote:
>
> Hi Stephen,
>
> The one below can be used.
>
> [FIPS 180-4] Federal Information Processing Standards Publication
> (FIPS PUB) 180-4, Secure Hash Standard (SHS), August
> 2015.
There is also RFC 4634,
Thanks all. I updated the RFC editor note to add the FIPS
reference.
Cheers,
S.
On 05/05/16 15:45, Alexey Melnikov wrote:
> On Thu, May 5, 2016, at 03:33 PM, Dang, Quynh (Fed) wrote:
>>
>> Hi Stephen,
>>
>> The one below can be used.
>>
>> [FIPS 180-4] Federal Information Processing Standards P
Hi Stephen,
The one below can be used.
[FIPS 180-4] Federal Information Processing Standards Publication
(FIPS PUB) 180-4, Secure Hash Standard (SHS), August 2015.
Regards,
Quynh.
From: TLS on behalf of Stephen Farrell
Sent: Thursday,
On 24/04/16 17:23, Alexey Melnikov wrote:
> Alexey Melnikov has entered the following ballot position for
> draft-ietf-tls-chacha20-poly1305-04: Yes
>
> 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
