[TLS] Alexey Melnikov's Yes on draft-ietf-tls-dnssec-chain-extension-07: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Wed, 21 March 2018 14:56 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-tls-dnssec-chain-extension@ietf.org, Joseph Salowey <joe@salowey.net>, shuque@gmail.com, tls-chairs@ietf.org, joe@salowey.net, tls@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152164421325.7503.1182024800685143273.idtracker@ietfa.amsl.com>
Date: Wed, 21 Mar 2018 07:56:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/ol9IFlz0G20R-ruGRUYlXT0QCHo>
Subject: [TLS] Alexey Melnikov's Yes on draft-ietf-tls-dnssec-chain-extension-07: (with COMMENT)

Alexey Melnikov has entered the following ballot position for
draft-ietf-tls-dnssec-chain-extension-07: 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-tls-dnssec-chain-extension/



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

Now that TLS 1.3 is approved for publication, I think adding a Normative
Reference to TLS 1.3 is no brainer. I am clearing my DISCUSS on the assumption
that this would be fixed before publication of the RFC.

1) TLS 1.3 needs to be a normative reference, but it is not even listed in
References.

2) The first mention of NSEC3 need a normative reference.

[TLS] Alexey Melnikov's Yes on draft-ietf-tls-dns… Alexey Melnikov