Re: [core] Editors' draft of changes to draft-ietf-core-coap-tcp-tls-08 after IESG input

Carsten Bormann <cabo@tzi.org> Mon, 15 May 2017 15:55 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9121C12E04A for <core@ietfa.amsl.com>; Mon, 15 May 2017 08:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.209
X-Spam-Level:
X-Spam-Status: No, score=-2.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3] 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 5wR1NqP2shsx for <core@ietfa.amsl.com>; Mon, 15 May 2017 08:55:27 -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 D532312E741 for <core@ietf.org>; Mon, 15 May 2017 08:45:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v4FFj0V2005549; Mon, 15 May 2017 17:45:00 +0200 (CEST)
Received: from [100.102.200.25] (ip-109-47-3-25.web.vodafone.de [109.47.3.25]) (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 3wRPzJ35XHzDGtF; Mon, 15 May 2017 17:45:00 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail-DC018F20-5785-459C-B80D-D07A1C998CE6"
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPhone Mail (14E304)
In-Reply-To: <ee31590027944221a50467618d36fb2e@FE-MBX1027.de.bosch.com>
Date: Mon, 15 May 2017 17:44:59 +0200
Cc: "core@ietf.org" <core@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <BACD0C4E-5438-46B8-ADEA-30AF44409440@tzi.org>
References: <76EA187B-4A41-4363-B49E-75064626190A@tzi.org> <ee31590027944221a50467618d36fb2e@FE-MBX1027.de.bosch.com>
To: "Kraus Achim (INST/ECS4)" <Achim.Kraus@bosch-si.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/7AHXOP0C0gMH4wNCgbVzeUJJ0SI>
Subject: Re: [core] Editors' draft of changes to draft-ietf-core-coap-tcp-tls-08 after IESG input
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 May 2017 15:55:29 -0000

Well, I just tried to realize what the IESG thought was right. But I can't fail to notice that the existing solution didn't really address the situation very well either, except where the server (or other entity supplying the link) knew exactly what the client should be doing. Section 7.8 is trying to give some guidance, but it will hardly ever be good enough to propose solutions for all possible situations. 

Sent from mobile

> On 15. May 2017, at 16:52, Kraus Achim (INST/ECS4) <Achim.Kraus@bosch-si.com> wrote:
> 
> Hi Carsten,
> 
>> IESG members have asked us to stop proliferating URI schemes, and as a result the draft remains with coap:// and coaps:// for all new transports.
> 
> Assuming a system, which supports CoAP over UDP and over TCP, how should such a system select, if UDP or TCP is intended to be used for a given destination?
> 
> Mit freundlichen Grüßen / Best regards
> 
> Achim Kraus
> 
> (INST/ECS4) 
> Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332 Waiblingen | GERMANY | www.bosch-si.com
> 
> Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B 
> Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn 
> 
> 
> 
> -----Original Message-----
> From: core [mailto:core-bounces@ietf.org] On Behalf Of Carsten Bormann
> Sent: Montag, 15. Mai 2017 16:32
> To: core <core@ietf.org>
> Subject: [core] Editors' draft of changes to draft-ietf-core-coap-tcp-tls-08 after IESG input
> 
> I have generate a first editors’ draft of what might become draft-ietf-core-coap-tcp-tls-09, addressing IESG input on the draft.
> (This draft addresses DISCUSSes, but almost no COMMENTS; see https://github.com/core-wg/coap-tcp-tls/issues for an overview what else needs to be done.)
> 
> This has a bit of Brownian motion (default ports etc.), but also one important change:
> 
> IESG members have asked us to stop proliferating URI schemes, and as a result the draft remains with coap:// and coaps:// for all new transports.
> 
> Please see:
> 
> https://tools.ietf.org/rfcdiff?url1=draft-ietf-core-coap-tcp-tls&url2=https://raw.githubusercontent.com/core-wg/coap-tcp-tls/gh-pages/iesg/draft-ietf-core-coap-tcp-tls.txt
> 
> for the changes from -08, and
> 
> https://core-wg.github.io/coap-tcp-tls/iesg/
> 
> for a full document.
> 
> For example,
> 
> https://core-wg.github.io/coap-tcp-tls/iesg/#rfc.section.7.8
> 
> is a new section, but many other sections concerned with URIs and URI schemes have received changes.
> 
> It is important if the WG can live with this change, or whether we need to incur further delay pushing back on this change.
> Please let us know!
> 
> Grüße, Carsten
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
> 
>