Re: [core] Publicly accessible Resource Directory?

Floris Van den Abeele <floris.vandenabeele@intec.ugent.be> Tue, 08 September 2015 11:06 UTC

Return-Path: <floris.vandenabeele@intec.ugent.be>
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 670E61B3C50 for <core@ietfa.amsl.com>; Tue, 8 Sep 2015 04:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.711
X-Spam-Level:
X-Spam-Status: No, score=-1.711 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 EH1TYjII9Zam for <core@ietfa.amsl.com>; Tue, 8 Sep 2015 04:06:45 -0700 (PDT)
Received: from smtp2.ugent.be (smtp2.ugent.be [157.193.49.126]) by ietfa.amsl.com (Postfix) with ESMTP id 49AAC1B2E3F for <core@ietf.org>; Tue, 8 Sep 2015 04:06:45 -0700 (PDT)
Received: from localhost (mcheck2.ugent.be [157.193.49.249]) by smtp2.ugent.be (Postfix) with ESMTP id 7186612C4A4; Tue, 8 Sep 2015 13:06:44 +0200 (CEST)
X-Virus-Scanned: by UGent DICT
Received: from smtp2.ugent.be ([IPv6:::ffff:157.193.49.126]) by localhost (mcheck2.UGent.be [::ffff:157.193.43.11]) (amavisd-new, port 10024) with ESMTP id wUuIiLvAd_kf; Tue, 8 Sep 2015 13:06:43 +0200 (CEST)
Received: from mail2.intec.ugent.be (mail2.intec.ugent.be [157.193.214.245]) by smtp2.ugent.be (Postfix) with ESMTP id 682FF12C48B; Tue, 8 Sep 2015 13:06:43 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail2.intec.ugent.be (Postfix) with ESMTP id 344F82E; Tue, 8 Sep 2015 13:06:43 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at intec.ugent.be
Received: from mail2.intec.ugent.be ([127.0.0.1]) by localhost (mail2.intec.ugent.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g7ckPiphpvnX; Tue, 8 Sep 2015 13:06:43 +0200 (CEST)
Received: from [157.193.135.182] (dhcp-zdpt-182.intec.ugent.be [157.193.135.182]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fvdabeele) by mail2.intec.ugent.be (Postfix) with ESMTPSA id 1A30D2D; Tue, 8 Sep 2015 13:06:43 +0200 (CEST)
From: Floris Van den Abeele <floris.vandenabeele@intec.ugent.be>
To: Carsten Bormann <cabo@tzi.org>
References: <55D1EB00.2050006@tzi.org>
X-Enigmail-Draft-Status: N1110
Message-ID: <55EEC142.5020303@intec.ugent.be>
Date: Tue, 08 Sep 2015 13:06:42 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55D1EB00.2050006@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Miltered: at jchkm1 with ID 55EEC143.000 by Joe's j-chkmail (http://helpdesk.ugent.be/email/)!
X-j-chkmail-Enveloppe: 55EEC143.000 from mail2.intec.ugent.be/mail2.intec.ugent.be/157.193.214.245/mail2.intec.ugent.be/<floris.vandenabeele@intec.ugent.be>
X-j-chkmail-Score: MSGID : 55EEC143.000 on smtp2.ugent.be : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/EVlp1grFfrJJ7AbJsXqDy9hAwQ8>
Cc: "core@ietf.org WG" <core@ietf.org>
Subject: Re: [core] Publicly accessible Resource Directory?
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: <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: Tue, 08 Sep 2015 11:06:47 -0000

I've put up an IPv6-only public RD at coap://rd.iot.test.iminds.be or
coap://[2001:6a8:1d80:23::155] (coaps is also supported but it is a bit
shaky).
The implementation is lagging behind the I-d quite a bit: e.g. there is
no support for groups/json/cbor/pagination at the moment, nor any other
changes since draft-shelby-core-resource-directory-04 (so beginning
2013). It is also rather picky about registration requests: you should
always specify a content-type option. I'll look into bringing the
implementation up to speed, but can't promise anything short term.

Groeten,
Floris

On 17-08-15 16:09, Carsten Bormann wrote:
> Which CoAP resource directories are out there for people to play with?
> (Sadly, coap.me doesn't have one yet.)
>
> Grüße, Carsten
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>
>
>