IETF Logo Mail Archive

[core] Anycast and CoRE

Jim Schaad <ietf@augustcellars.com> Sat, 08 December 2018 22:59 UTC

Return-Path: <ietf@augustcellars.com>
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 3D6F3130F46 for <core@ietfa.amsl.com>; Sat, 8 Dec 2018 14:59:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 OKJ7T0aFDLg4 for <core@ietfa.amsl.com>; Sat, 8 Dec 2018 14:59:03 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F761126CB6 for <core@ietf.org>; Sat, 8 Dec 2018 14:59:03 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sat, 8 Dec 2018 14:53:59 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: core@ietf.org
Date: Sat, 08 Dec 2018 14:58:54 -0800
Message-ID: <017201d48f49$99516560$cbf43020$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdSPSDJOPJliJThyS9uMRvYItj19qA==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/9V_aHdPA9ZDY1F9fhnJ0XCT5W-s>
Subject: [core] Anycast and CoRE
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 08 Dec 2018 22:59:05 -0000

I have been looking at implementing Anycast along side of Multicast.  I am
trying to figure out if Anycast is supposed to have the response on the
Anycast address like Unicast does, or if it should be returned on a Unicast
address.  There is no clear guidance on this in RFC 7252.  Among the things
that RFC 7252 says is that coaps can be implemented using Anycast.  However,
given that the routing could be changed at any time, for example in the
middle of the DTLS handshake or processing blocks, it makes any sense to
return on the Anycast address.

Is there anybody who has looked at this or wants to provide guidance?

Jim

v2.23.0 | Report a Bug | By Email