IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Tue, 16 May 2017 11:57 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 76BB0129BBD for <core@ietfa.amsl.com>; Tue, 16 May 2017 04:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 xu5R14ucSyTI for <core@ietfa.amsl.com>; Tue, 16 May 2017 04:57:20 -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 2CD3B129461 for <core@ietf.org>; Tue, 16 May 2017 04:53:33 -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 v4GBrUoT007409 for <core@ietf.org>; Tue, 16 May 2017 13:53:30 +0200 (CEST)
Received: from client-0191.vpn.uni-bremen.de (client-0191.vpn.uni-bremen.de [134.102.107.191]) (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 3wRwnj66R3zDHBG; Tue, 16 May 2017 13:53:29 +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: <CAAzbHvYuPZvaGP0J_4aGdQ9pMoBf0_L1qju=yd76vzO+RPf5ng@mail.gmail.com>
Date: Tue, 16 May 2017 13:53:26 +0200
Cc: "core@ietf.org" <core@ietf.org>
X-Mao-Original-Outgoing-Id: 516628406.031567-0acda348dbeef15673bb49d28fc58415
Content-Transfer-Encoding: quoted-printable
Message-Id: <228B9781-A545-4312-854E-625539545E1A@tzi.org>
References: <76EA187B-4A41-4363-B49E-75064626190A@tzi.org> <ee31590027944221a50467618d36fb2e@FE-MBX1027.de.bosch.com> <CAAzbHvYuPZvaGP0J_4aGdQ9pMoBf0_L1qju=yd76vzO+RPf5ng@mail.gmail.com>
To: Klaus Hartke <hartke@tzi.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/hgPyARDhFMYYPou1veLwYWfHuVY>
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: Tue, 16 May 2017 11:57:22 -0000

> On May 15, 2017, at 17:15, Klaus Hartke <hartke@tzi.org> wrote:
> 
> Kraus Achim (INST/ECS4) wrote:
>> 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?
> 
> This one is even more fun:
> 
>    coap://2259499800/path/to/resource
> 
> Is this CoAP over UDP or TCP to a server with IP address 134.173.59.24

Answer: No.  RFC 3986 says:

   IPv4address   = dec-octet "." dec-octet "." dec-octet "." dec-octet

   dec-octet     = DIGIT                 ; 0-9
                 / %x31-39 DIGIT         ; 10-99
                 / "1" 2DIGIT            ; 100-199
                 / "2" %x30-34 DIGIT     ; 200-249
                 / "25" %x30-35          ; 250-255


> (there are URI parsers that accept "dotless" IPv4 addresses)

That may have been an amusing quirk for a while, but is not supported by the URI standard.  
I hope people don’t start doing in the CoAP space what has been deprecated in the HTTP space for a long time...

> or CoAP over SMS to a server with phone number +225-949-9800?

I don’t think we will be able to address CoAP over SMS with the same Authority (RFC 3986) construct that we use for CoAP over IP-based transports.  The latter all are based on IP addresses and port numbers (even if the port numbers may be for different transport protocols).  But the CoAP over SMS document is not before the IESG at this point in time.  By the way, we are still looking for reviews for the latter (https://tools.ietf.org/html/draft-becker-core-coap-sms-gprs-06) so we can adopt it as a WG document.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email