IETF Logo Mail Archive

Re: [Dots] CoAP over TCP 7.0.4 release - Alternative address usage

<mohamed.boucadair@orange.com> Tue, 22 May 2018 07:46 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8293D124F57 for <dots@ietfa.amsl.com>; Tue, 22 May 2018 00:46:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, 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 mt-Hyd_0mYPH for <dots@ietfa.amsl.com>; Tue, 22 May 2018 00:46:13 -0700 (PDT)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 677C1126B6E for <dots@ietf.org>; Tue, 22 May 2018 00:46:13 -0700 (PDT)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 5FEA040716; Tue, 22 May 2018 09:46:11 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.58]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 3D0381A007C; Tue, 22 May 2018 09:46:11 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0389.001; Tue, 22 May 2018 09:46:10 +0200
From: mohamed.boucadair@orange.com
To: Jon Shallow <supjps-ietf@jpshallow.com>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] CoAP over TCP 7.0.4 release - Alternative address usage
Thread-Index: AdPw2OMs2S/Cxz++QK2ZFs5FzGjbSgAxi9eA
Date: Tue, 22 May 2018 07:46:10 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DF1E272@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <13c601d3f0d8$e33a7e60$a9af7b20$@jpshallow.com>
In-Reply-To: <13c601d3f0d8$e33a7e60$a9af7b20$@jpshallow.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93302DF1E272OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/GT_q0UdbQKAkN-VK4_Y9-WU2qlo>
Subject: Re: [Dots] CoAP over TCP 7.0.4 release - Alternative address usage
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 07:46:16 -0000

Hi Jon,

The current procedure in 4.6 is generic and allows for clients to fall back to the nominal server (ttl thing) without another yet explicit signal from the server.

Release messages do not achieve the above features (but only a subset of the redirected sign procedure).

Cheers,
Med

De : Dots [mailto:dots-bounces@ietf.org] De la part de Jon Shallow
Envoyé : lundi 21 mai 2018 09:54
À : dots@ietf.org
Objet : [Dots] CoAP over TCP 7.0.4 release - Alternative address usage

Hi there,

As "RFC 8323: 5.5 Release messages" defines Alternative addresses to use (for TCP) with 7.04 code with options, should we also be using this within the signal channel as an alternative to the "signal draft 4.6. Redirected Signaling" ?

Regards

Jon

v2.23.0 | Report a Bug | By Email