[sidr] Alissa Cooper's Discuss on draft-ietf-sidr-publication-10: (with DISCUSS and COMMENT)

"Alissa Cooper" <alissa@cooperw.in> Tue, 17 January 2017 15:46 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: sidr@ietf.org
Delivered-To: sidr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A502E1294D4; Tue, 17 Jan 2017 07:46:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148466796666.31979.17532709479234975824.idtracker@ietfa.amsl.com>
Date: Tue, 17 Jan 2017 07:46:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/1CJG7zoxgyyBr_ZIVlYrkQTfySA>
Cc: morrowc@ops-netman.net, sidr-chairs@ietf.org, draft-ietf-sidr-publication@ietf.org, sidr@ietf.org
Subject: [sidr] Alissa Cooper's Discuss on draft-ietf-sidr-publication-10: (with DISCUSS and COMMENT)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2017 15:46:07 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-sidr-publication-10: Discuss

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-sidr-publication/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

What is the upgrade path for the future when new versions of this
protocol get published? How are clients and servers meant to agree on
which version to use?


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

(Hit the send button too quickly, sorry for the multiple emails.)

Although I understand why Section 6 says transport security is not
strictly required, given that the authentication and authorization
mechanisms that this protocol relies on are outside of the scope here,
isn't it possible that clients and servers may be exchanging cookies or
other headers in the course of using this protocol that would benefit
from transport encryption? It seems like mentioning that transport
security may still be beneficial although not required might be a good
idea.