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

Klaus Hartke <hartke@tzi.org> Mon, 15 May 2017 15:21 UTC

Return-Path: <hartke@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 5857F1294BD for <core@ietfa.amsl.com>; Mon, 15 May 2017 08:21:26 -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_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5] 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 d2teDIBXqLB0 for <core@ietfa.amsl.com>; Mon, 15 May 2017 08:21:24 -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 92098127333 for <core@ietf.org>; Mon, 15 May 2017 08:16:27 -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 v4FFGOiU012892 for <core@ietf.org>; Mon, 15 May 2017 17:16:24 +0200 (CEST)
Received: from mail-it0-f51.google.com (mail-it0-f51.google.com [209.85.214.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wRPLH6rywzDGsm for <core@ietf.org>; Mon, 15 May 2017 17:16:23 +0200 (CEST)
Received: by mail-it0-f51.google.com with SMTP id g126so70543758ith.0 for <core@ietf.org>; Mon, 15 May 2017 08:16:23 -0700 (PDT)
X-Gm-Message-State: AODbwcB9zV/FSop82eKZquyDuG2zqfn8TyWAdnLMgoQuAmNOiUKkGMLn oZy5CuWHYl3Gp/LD1wpXPfESV9XFsA==
X-Received: by 10.36.75.12 with SMTP id q12mr5810897ita.34.1494861382790; Mon, 15 May 2017 08:16:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.163.87 with HTTP; Mon, 15 May 2017 08:15:42 -0700 (PDT)
In-Reply-To: <ee31590027944221a50467618d36fb2e@FE-MBX1027.de.bosch.com>
References: <76EA187B-4A41-4363-B49E-75064626190A@tzi.org> <ee31590027944221a50467618d36fb2e@FE-MBX1027.de.bosch.com>
From: Klaus Hartke <hartke@tzi.org>
Date: Mon, 15 May 2017 17:15:42 +0200
X-Gmail-Original-Message-ID: <CAAzbHvYuPZvaGP0J_4aGdQ9pMoBf0_L1qju=yd76vzO+RPf5ng@mail.gmail.com>
Message-ID: <CAAzbHvYuPZvaGP0J_4aGdQ9pMoBf0_L1qju=yd76vzO+RPf5ng@mail.gmail.com>
To: "core@ietf.org" <core@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/O8QT7D1FtE-glJp_kdJMuEuyKfo>
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:21:26 -0000

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
(there are URI parsers that accept "dotless" IPv4 addresses) or CoAP
over SMS to a server with phone number +225-949-9800?

Klaus