[TLS] TLSv1.3 - Draft 24 - small typo need correction

M K Saravanan <mksarav@gmail.com> Fri, 02 March 2018 06:50 UTC

Return-Path: <mksarav@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59C0F1241FC for <tls@ietfa.amsl.com>; Thu, 1 Mar 2018 22:50:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zcisUZZ2bnGt for <tls@ietfa.amsl.com>; Thu, 1 Mar 2018 22:50:04 -0800 (PST)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9AC4120454 for <tls@ietf.org>; Thu, 1 Mar 2018 22:50:03 -0800 (PST)
Received: by mail-lf0-x22d.google.com with SMTP id h127so10843248lfg.12 for <tls@ietf.org>; Thu, 01 Mar 2018 22:50:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=urFdxutznJ/XCMgPxA9n365nSOep2GtfCilJggaLa5U=; b=WoAs5SuHjwycDtAWK4ygAcnWN6EOB/rpzA7T9hQghRRPKK00v8z7wab+UR/ASAudbs nYx4Ff8mSMV3NdYwbAqsbZmFumgEcEy6CWQIa3Vbav8HLgF9klOQccpuhC2vtkB9wv0F vF/11l8SL9rU5tj2h1cVTPAFrrItZaxCrOHcw7CKo1Kb4MxAL/8kpNSxsK3R2qEDCwa+ XtGEy4flYU6sb+W0mndPU0IfjvzZezt6cFQx/CpwNhoe5DYyE48jpisp8wv5m//XZ+eB ZUWvWLu16ybJPwSqWvsCwn0Exw5iTlX8rU7+Q24mGRnuk86rRlQFW4a6CpDm9/PsujJM 9L8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=urFdxutznJ/XCMgPxA9n365nSOep2GtfCilJggaLa5U=; b=uRHEK758TErEuHDoa9gt7b8Qmw5RrRUDvdWi710ga19KoAqYIffdRq8/AZxB9aJlO5 eFhnMLxybo+QZtw9UmBmp94G74ysxAmT7KhxyfefDXBOXVPqfb+5FcyEv5iS4VG7PO9v UadcsNThQxCTg2bIc7CIH6QNZHqtissZMAy+xFr57NGDfDtfN0Rs1rrf3FTuqHz02WDG z/aTMEpvWbu9lp1tHdD+dtjysAUmirfw8BMuTanhQVuCkluRUUAv9lmV8rMAEKkJAJ+0 T9JUXfV/mw9xEti5J2kWMWQ2E3zsOhbuuXyIdvtDWDt/eRjAzBOruKcp8fLd6nM2lHB0 i6Rw==
X-Gm-Message-State: AElRT7E9IW12j6zkYtRhNsNMSIasXI3TRndSq/hmHEVSEg8RSPkFP33G bnLraL0YkWTKqDOBFjOqRe/0m+9CvYJj7CqsgUglEPYq
X-Google-Smtp-Source: AG47ELvajQWLUyjF71TyLRlvudR1WBDN6hpiH8iCCexb8orT3Wtj3M+KxexlvdnlOJiQ7zoF3MF770ndmFdlfd73Jvs=
X-Received: by 10.46.126.16 with SMTP id z16mr3235438ljc.103.1519973401651; Thu, 01 Mar 2018 22:50:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.26.200 with HTTP; Thu, 1 Mar 2018 22:50:00 -0800 (PST)
From: M K Saravanan <mksarav@gmail.com>
Date: Fri, 02 Mar 2018 14:50:00 +0800
Message-ID: <CAG5P2e_UxCzMgV44YzLbZ_jA+ff1x7kh9Z3jAaE9m1_RBc6WWw@mail.gmail.com>
To: tls@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Oib5Sme40b2ZOCthsU0DHe7BADg>
Subject: [TLS] TLSv1.3 - Draft 24 - small typo need correction
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 03:34:40 -0000

Hi,

In TLSv1.3, draft 24, there is a small typographical error.  It needs
to be corrected.


(1)

Appendix D.  Backward Compatibility

Second Paragraph.  Second sentence.  There is a double "and".

/* Original */
=========
Servers can also handle clients trying to use future versions of TLS as long as
the ClientHello format remains compatible and and there is at least
one protocol version supported by both the client and the server.
==========

/* Corrected */

======
Servers can also handle clients trying to use future versions of TLS as long as
the ClientHello format remains compatible and there is at least
one protocol version supported by both the client and the server.
======

(2)

Section 4.2.8.2. ECDHE Parameters

First paragraph, first sentence.  There is a double "the".

/* Original */
=========
ECDHE parameters for both clients and servers are encoded in the the
opaque key_exchange field of a KeyShareEntry in a KeyShare structure.
=========

/* Corrected */
=========
ECDHE parameters for both clients and servers are encoded in the
opaque key_exchange field of a KeyShareEntry in a KeyShare structure.
=========

(3)

Appendix E.5.  Replay Attacks on 0-RTT

Second paragraph, second line.  There is a double "the".

/* Original */
===========
If data can be replayed a large number of times, additional attacks
become possible, such as making repeated measurements of the the
speed of cryptographic operations.
===========

/* Corrected */
==========
If data can be replayed a large number of times, additional attacks
become possible, such as making repeated measurements of the
speed of cryptographic operations.
==========

Please correct them.

with regards,
Saravanan