[Sidrops] Barry Leiba's No Objection on draft-ietf-sidrops-https-tal-07: (with COMMENT)

Barry Leiba via Datatracker <noreply@ietf.org> Mon, 08 April 2019 04:49 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 472C2120149; Sun, 7 Apr 2019 21:49:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-sidrops-https-tal@ietf.org, Chris Morrow <morrowc@ops-netman.net>, sidrops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <155469895228.18178.17765650719093981433.idtracker@ietfa.amsl.com>
Date: Sun, 07 Apr 2019 21:49:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/dYDexeyKnK_t7d0S1h-l9Luvd3E>
Subject: [Sidrops] Barry Leiba's No Objection on draft-ietf-sidrops-https-tal-07: (with COMMENT)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2019 04:49:12 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-sidrops-https-tal-07: No Objection

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-sidrops-https-tal/



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

I realize that this document inherits the text in Section 3 from RFC 6490, but
can you tell me why there are SHOULDs and not MUSTs?  Why would one NOT do it
the way Section 3 specifies?

Then I’ll ask the same question for the new https text in Section 4, especially
about TLS certificate and host name validation.