IETF Logo Mail Archive

Re: [hybi] Artart last call review of draft-ietf-core-coap-tcp-tls-07

Carsten Bormann <cabo@tzi.org> Wed, 19 April 2017 19:22 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 591A4129C1A; Wed, 19 Apr 2017 12:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 IFzqeXD2KAZL; Wed, 19 Apr 2017 12:22:10 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB24D129557; Wed, 19 Apr 2017 12:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3JJM6VE017168; Wed, 19 Apr 2017 21:22:06 +0200 (CEST)
Received: from [192.168.217.113] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3w7X1p4yfgzDH3W; Wed, 19 Apr 2017 21:22:06 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <149179722452.3118.982908107963516290@ietfa.amsl.com>
Date: Wed, 19 Apr 2017 21:22:05 +0200
X-Mao-Original-Outgoing-Id: 514322525.709632-e6c608bc5c2ecfb6a3a2b1b6084beadb
Content-Transfer-Encoding: quoted-printable
Message-Id: <C011A48B-7865-4557-A9EA-7CE79C790762@tzi.org>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com>
To: art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org, IETF <ietf@ietf.org>, core <core@ietf.org>, hybi@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/8Hx7AMECZ7CrUhixNNrylJeqk_E>
Subject: Re: [hybi] Artart last call review of draft-ietf-core-coap-tcp-tls-07
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 19:22:12 -0000

On Apr 10, 2017, at 06:07, Mark Nottingham <mnot@mnot.net> wrote:
> 
> Section 7.4 shows how to convert a "coap+ws://" URI into a "wss://"
> URI, using a well-known URI in the "wss" scheme. However, "wss" is not
> defined to use well-known URIs, so this is an invalid use.

Clearly, this is a bug in draft-ietf-core-coap-tcp-tls-07.

I have argued that underlying this is an omission in RFC 6455:

ws:/wss: URIs are translated into http:/https: URIs, and the well-known space is already reserved in the latter, so it would be nonsensical to try to use RFC 5785 /.well-known for something else in the ws:/wss: URI schemes.

Maybe there wasn’t a use case for well-known URIs in WebSockets before, but there is one now, and we would like to remedy this omission in the procedurally simplest possibly way.

So I am proposing to add RFC 5785’s well-known URI mechanism to these URI schemes in the document that needs it, draft-ietf-core-coap-tcp-tls, which by that updates RFC 6455.

Are there any objections to this procedure?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email