[Dots] CoAP over TCP 7.0.4 release - Alternative address usage
"Jon Shallow" <supjps-ietf@jpshallow.com> Mon, 21 May 2018 07:54 UTC
Return-Path: <supjps-ietf@jpshallow.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 0F086126C83 for <dots@ietfa.amsl.com>; Mon, 21 May 2018 00:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, SPF_PASS=-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 E4NPYLO4QduU for <dots@ietfa.amsl.com>; Mon, 21 May 2018 00:54:04 -0700 (PDT)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (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 6D783126C22 for <dots@ietf.org>; Mon, 21 May 2018 00:54:04 -0700 (PDT)
Received: from [127.0.0.1] (helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.90_1) (envelope-from <jon.shallow@jpshallow.com>) id 1fKfdp-0004TU-Sc for ietf-supjps-dots@ietf.org; Mon, 21 May 2018 08:54:01 +0100
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: dots@ietf.org
Date: Mon, 21 May 2018 08:54:03 +0100
Message-ID: <13c601d3f0d8$e33a7e60$a9af7b20$@jpshallow.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_13C7_01D3F0E1.44FF5B90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdPw2OMs2S/Cxz++QK2ZFs5FzGjbSg==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/jz_QIyVV9tV7ho4V50uaJK09tto>
Subject: [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: Mon, 21 May 2018 07:54:06 -0000
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
- [Dots] CoAP over TCP 7.0.4 release - Alternative … Jon Shallow
- Re: [Dots] CoAP over TCP 7.0.4 release - Alternat… mohamed.boucadair