IETF Logo Mail Archive

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

"Kovatsch, Matthias" <matthias.kovatsch@siemens.com> Wed, 19 April 2017 17:59 UTC

Return-Path: <matthias.kovatsch@siemens.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD70129BA3; Wed, 19 Apr 2017 10:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level:
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 RmiREgHErwgw; Wed, 19 Apr 2017 10:58:59 -0700 (PDT)
Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) (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 A23AF129B9E; Wed, 19 Apr 2017 10:58:58 -0700 (PDT)
Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id v3JHwtgX008143 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 19 Apr 2017 19:58:56 +0200
Received: from DEFTHW99ERNMSX.ww902.siemens.net (defthw99ernmsx.ww902.siemens.net [139.22.70.141]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTPS id v3JHwtvD001745 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Apr 2017 19:58:55 +0200
Received: from DENBGAT9ER2MSX.ww902.siemens.net (139.22.70.79) by DEFTHW99ERNMSX.ww902.siemens.net (139.22.70.141) with Microsoft SMTP Server (TLS) id 14.3.352.0; Wed, 19 Apr 2017 19:58:55 +0200
Received: from DEFTHW99EL4MSX.ww902.siemens.net ([169.254.5.107]) by DENBGAT9ER2MSX.ww902.siemens.net ([139.22.70.79]) with mapi id 14.03.0352.000; Wed, 19 Apr 2017 19:58:54 +0200
From: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>
To: Mark Nottingham <mnot@mnot.net>, "cabo@tzi.org" <cabo@tzi.org>
CC: "art@ietf.org" <art@ietf.org>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AQHSsbAJgy90j5EPhU2Dw058Pbi54KG+Oc0AgAD5ZgCAAiynAIAABAsAgAAA6ICACvX8kA==
Date: Wed, 19 Apr 2017 17:58:53 +0000
Message-ID: <4EBB3DDD0FBF694CA2A87838DF129B3C01B4F4F7@DEFTHW99EL4MSX.ww902.siemens.net>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <7DEDD3CB-B812-4151-97DC-403448C1080B@mnot.net> <55877B3AFB359744BA0F2140E36F52B558B2A929@MBX210.d.ethz.ch> <cc7b5d80-21f1-e38b-4739-f44d536cf260@isode.com> <E882ABDC-F4E1-4EDD-A90C-D32EB5B0A639@mnot.net>
In-Reply-To: <E882ABDC-F4E1-4EDD-A90C-D32EB5B0A639@mnot.net>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [139.22.70.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/NTz0cVhlC8L3LA6wEQonhrsXW6k>
Subject: Re: [art] [core] Artart last call review of draft-ietf-core-coap-tcp-tls-07
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 17:59:00 -0000

Hi there

I am picking up this discussion again, as I was made aware of another use case for CoAP-over-WebSockets related to firewalls or shielded networks: without having looked into the details, HTTP CONNECT apparently does not allow for OAuth, while upgrading to WebSockets can make use of OAuth to establish a secure channel between two edge CoAP proxies that, for instance, forward requests from devices behind one firewall to devices behind another firewall.

Best wishes
Matthias

v2.23.0 | Report a Bug | By Email