[tcpinc] Alexey Melnikov's Yes on draft-ietf-tcpinc-tcpeno-17: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Sun, 26 November 2017 16:54 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-tcpinc-tcpeno@ietf.org, David Black <david.black@dell.com>, tcpinc-chairs@ietf.org, david.black@dell.com, tcpinc@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151171524963.16120.9058882195648633025.idtracker@ietfa.amsl.com>
Date: Sun, 26 Nov 2017 08:54:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/uriS7-tMBt7Y3xiWYrKMZ7aW4CE>
Subject: [tcpinc] Alexey Melnikov's Yes on draft-ietf-tcpinc-tcpeno-17: (with COMMENT)

Alexey Melnikov has entered the following ballot position for
draft-ietf-tcpinc-tcpeno-17: 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
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tcpinc-tcpeno/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

In Section 10 RFC 5802 would be a better example than RFC 7616, because the
former already has a slot for "channel binding" (session-id being an example)
information and generally improves on security properties of Digest.

[tcpinc] Alexey Melnikov's Yes on draft-ietf-tcpi… Alexey Melnikov