[rfc-dist] RFC 9176 on Constrained RESTful Environments (CoRE) Resource Directory
rfc-editor@rfc-editor.org Mon, 25 April 2022 18:44 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B3FE8C2B62EB; Mon, 25 Apr 2022 11:44:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1650912251; bh=/d/TA9Z3MTwyEwRLgPEkYsvg0tWBGy0J/5tgilaCVa4=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=iGDKxhrlcDJkw3pA3/7k0rFBtLpcsLr1KaBXUErMjggQ8iLpbPHl+tg2mxrKlP49Q ZdpF03tmeQGMYvsODzVgfrsjkOfI7IvZCWHHlvCInkqtniz0fC5mMPXC8QqynIkM7P nEm+DqrL26hFn31LM/poC8FHKd2Or8m5f/dIw0Pw=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Mon Apr 25 11:44:11 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 72F3FC06DD44; Mon, 25 Apr 2022 11:44:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1650912251; bh=/d/TA9Z3MTwyEwRLgPEkYsvg0tWBGy0J/5tgilaCVa4=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=iGDKxhrlcDJkw3pA3/7k0rFBtLpcsLr1KaBXUErMjggQ8iLpbPHl+tg2mxrKlP49Q ZdpF03tmeQGMYvsODzVgfrsjkOfI7IvZCWHHlvCInkqtniz0fC5mMPXC8QqynIkM7P nEm+DqrL26hFn31LM/poC8FHKd2Or8m5f/dIw0Pw=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2759FC06DB8B; Mon, 25 Apr 2022 11:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.255
X-Spam-Level:
X-Spam-Status: No, score=0.255 tagged_above=-999 required=5 tests=[CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zz8nIUh6V2I; Mon, 25 Apr 2022 11:44:05 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83EE7C06DB82; Mon, 25 Apr 2022 11:44:05 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 51F97D80D3; Mon, 25 Apr 2022 11:44:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, core@ietf.org
Message-Id: <20220425184405.51F97D80D3@rfcpa.amsl.com>
Date: Mon, 25 Apr 2022 11:44:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/nwtBNr5IwFuG-jPUCWTtB8koiaI>
Subject: [rfc-dist] RFC 9176 on Constrained RESTful Environments (CoRE) Resource Directory
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9176
Title: Constrained RESTful Environments (CoRE) Resource
Directory
Author: C. Amsüss, Ed.,
Z. Shelby,
M. Koster,
C. Bormann,
P. van der Stok
Status: Standards Track
Stream: IETF
Date: April 2022
Mailbox: christian@amsuess.com,
zach@edgeimpulse.com,
michaeljohnkoster@gmail.com,
cabo@tzi.org,
stokcons@bbhmail.nl
Pages: 60
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-core-resource-directory-28.txt
URL: https://www.rfc-editor.org/info/rfc9176
DOI: 10.17487/RFC9176
In many Internet of Things (IoT) applications, direct discovery of
resources is not practical due to sleeping nodes or networks where
multicast traffic is inefficient. These problems can be solved by
employing an entity called a Resource Directory (RD), which contains
information about resources held on other servers, allowing lookups
to be performed for those resources. The input to an RD is composed
of links, and the output is composed of links constructed from the
information stored in the RD. This document specifies the web
interfaces that an RD supports for web servers to discover the RD and
to register, maintain, look up, and remove information on resources.
Furthermore, new target attributes useful in conjunction with an RD
are defined.
This document is a product of the Constrained RESTful Environments Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org