[core] Which IPv6 multicast scopes for the "All CoAP Nodes" address?
"Dijk, Esko" <esko.dijk@philips.com> Wed, 27 November 2013 13:17 UTC
Return-Path: <esko.dijk@philips.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 602D11A1F19 for <core@ietfa.amsl.com>; Wed, 27 Nov 2013 05:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.947
X-Spam-Level:
X-Spam-Status: No, score=-2.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, UNRESOLVED_TEMPLATE=1.252] autolearn=ham
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 lLTO6VXnGklC for <core@ietfa.amsl.com>; Wed, 27 Nov 2013 05:17:32 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by ietfa.amsl.com (Postfix) with ESMTP id 199F91A1F00 for <core@ietf.org>; Wed, 27 Nov 2013 05:17:32 -0800 (PST)
Received: from mail36-co9-R.bigfish.com (10.236.132.249) by CO9EHSOBE035.bigfish.com (10.236.130.98) with Microsoft SMTP Server id 14.1.225.22; Wed, 27 Nov 2013 13:17:31 +0000
Received: from mail36-co9 (localhost [127.0.0.1]) by mail36-co9-R.bigfish.com (Postfix) with ESMTP id 61C7AD002B4 for <core@ietf.org>; Wed, 27 Nov 2013 13:17:31 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI
X-SpamScore: -6
X-BigFish: VPS-6(zz217bI15d6Oc85fh9251Idd85kzz1f42h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz18c673hz2dh109h2a8h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1b2fh1bceh2222h224fh1fb3h1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1fe8h1ff5h20f0h2216h22d0h1155h)
Received: from mail36-co9 (localhost.localdomain [127.0.0.1]) by mail36-co9 (MessageSwitch) id 1385558249688711_5203; Wed, 27 Nov 2013 13:17:29 +0000 (UTC)
Received: from CO9EHSMHS030.bigfish.com (unknown [10.236.132.248]) by mail36-co9.bigfish.com (Postfix) with ESMTP id A3BAC1C006B; Wed, 27 Nov 2013 13:17:29 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by CO9EHSMHS030.bigfish.com (10.236.130.40) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 27 Nov 2013 13:17:28 +0000
Received: from 011-DB3MPN2-082.MGDPHG.emi.philips.com ([169.254.2.40]) by 011-DB3MMR1-009.MGDPHG.emi.philips.com ([10.128.28.48]) with mapi id 14.03.0158.002; Wed, 27 Nov 2013 13:17:26 +0000
From: "Dijk, Esko" <esko.dijk@philips.com>
To: "core (core@ietf.org)" <core@ietf.org>
Thread-Topic: Which IPv6 multicast scopes for the "All CoAP Nodes" address?
Thread-Index: Ac7rcvvkVU2ar6eHR+2s01dMYO1xPw==
Date: Wed, 27 Nov 2013 13:17:25 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED6180CC421C2@011-DB3MPN2-082.MGDPHG.emi.philips.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [194.171.252.106]
Content-Type: multipart/alternative; boundary="_000_031DD135F9160444ABBE3B0C36CED6180CC421C2011DB3MPN2082MG_"
MIME-Version: 1.0
X-OriginatorOrg: philips.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%0$Dn%INTERDIGITAL.COM$RO%1$TLS%0$FQDN%$TlsDn%
Subject: [core] Which IPv6 multicast scopes for the "All CoAP Nodes" address?
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 27 Nov 2013 13:17:35 -0000
Dear all,
in coap-18 it mentions for the IPv6 "All CoAP Nodes" address:
Note that there is a distinct multicast address
for each scope that interested CoAP nodes should listen to; CoAP
needs the Link-Local and Site-Local scopes only.
which could raise some interoperability concerns:
- CoAP nodes are not obliged to join any of these addresses; so multicast discovery may not work in practice.
A client may be tempted to instead use the "All Nodes" link-local IPv6 multicast address to send out a CoAP request, since IPv6 / 6LoWPAN-ND requires joining this address.
- CoAP nodes only join the link-local and/or site-local scoped address, not others (admin-local, or the new "realm-local" defined in draft-droms-6man-multicast-scopes-02)
So a discovering client using e.g. admin-local may not find any CoAP nodes.
My goal was to write some guidelines in groupcomm what IPv6 / IPv4 multicast addresses a CoAP server should join, and which addresses a discovering client should use.
For now I will base on the information that core-coap provides; adding that a server SHOULD join both the link-local and site-local "All CoAP nodes" IPv6 multicast addresses.
regards,
Esko
________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.