RFC 7650 on A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)
rfc-editor@rfc-editor.org Wed, 23 September 2015 22:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E97FC1B2D0D for <ietf-announce@ietfa.amsl.com>; Wed, 23 Sep 2015 15:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 jhAJDoZOX0oI for <ietf-announce@ietfa.amsl.com>; Wed, 23 Sep 2015 15:21:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 888B71B2D06 for <ietf-announce@ietf.org>; Wed, 23 Sep 2015 15:21:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 842B6188CF1; Wed, 23 Sep 2015 15:20:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7650 on A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150923222056.842B6188CF1@rfc-editor.org>
Date: Wed, 23 Sep 2015 15:20:56 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/g8QBX1FHrELBe2dHJ22qkWeNg7k>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2015 22:21:52 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7650
Title: A Constrained Application Protocol (CoAP)
Usage for REsource LOcation And Discovery
(RELOAD)
Author: J. Jimenez, J. Lopez-Vega,
J. Maenpaa, G. Camarillo
Status: Standards Track
Stream: IETF
Date: September 2015
Mailbox: jaime.jimenez@ericsson.com,
jmlvega@ugr.es,
jouni.maenpaa@ericsson.com,
gonzalo.camarillo@ericsson.com
Pages: 19
Characters: 37404
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-jimenez-p2psip-coap-reload-10.txt
URL: https://www.rfc-editor.org/info/rfc7650
DOI: http://dx.doi.org/10.17487/RFC7650
This document defines a Constrained Application Protocol (CoAP) Usage
for REsource LOcation And Discovery (RELOAD). The CoAP Usage
provides the functionality to federate Wireless Sensor Networks
(WSNs) in a peer-to-peer fashion. The CoAP Usage for RELOAD allows
CoAP nodes to store resources in a RELOAD peer-to-peer overlay,
provides a lookup service, and enables the use of RELOAD overlay as a
cache for sensor data. This functionality is implemented in the
RELOAD overlay itself, without the use of centralized servers. The
RELOAD AppAttach method is used to establish a direct connection
between nodes through which CoAP messages are exchanged.
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/rfc.html
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