On Mon, Jan 21, 2019 at 07:37:25PM +0000, Suresh Krishnan wrote:
> Hi Sabine,
> 
> On Jan 21, 2019, at 11:13 AM, Randriamasy, Sabine (Nokia - FR/Paris-Saclay) 
> <[email protected]<mailto:[email protected]>>
>  wrote:
> 
> Hello Suresh,
> 
> Thanks for your comments,
> Please see answers and one question on our side inline,
> 
> All the best for 2019,
> 
> Sabine
> 
> -----Original Message-----
> From: Suresh Krishnan <[email protected]<mailto:[email protected]>>
> Sent: Tuesday, December 04, 2018 8:09 AM
> To: The IESG <[email protected]<mailto:[email protected]>>
> Cc: 
> [email protected]<mailto:[email protected]>;
>  Gurbani, Vijay (Nokia - US/Naperville) 
> <[email protected]<mailto:[email protected]>>;
>  [email protected]<mailto:[email protected]>; Gurbani, Vijay (Nokia - 
> US/Naperville) 
> <[email protected]<mailto:[email protected]>>;
>  [email protected]<mailto:[email protected]>
> Subject: Suresh Krishnan's No Objection on draft-ietf-alto-cost-calendar-09: 
> (with COMMENT)
> 
> * Section 4.2.3. and 4.2.4.
> 
> This document uses addresses from the allocatable global unicast IPv6 space in
> 2000::/3 in the examples. Please use addresses from the 2001:db8::/32 
> documentation prefix instead for the examples as per RFC6890.
> [[SR]] Thanks, will be done as indicated by Mirja
> 
> Sounds good.
> 
> 
> * Section 6
> 
> Any reason this document requires the use of TLS 1.2 instead of TLS 1.3?
> [[SR]] No particular reason. In section, after quoting the RFC 7285 text, we 
> may add the text below, with one question though:
> do you see chances for TLS 1.2 to be deprecated in the near future?
> 
> I will let the SEC ADs answer this one, but my concern was more that there is 
> no pointer to a newer version (1.3) that exists now.

Barring some startling new cryptographic attack, deprecation of TLS 1.2 is
looking to be at least 5 years in the future.  TLS 1.3 gets you a
streamlined handshake for faster TTFB, and the crypto is better analyzed,
but the adoption of 1.3 is being driven by this sort of features and not by
flaws in 1.2.

-Benjamin

_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to