IETF Logo Mail Archive

[core] Fwd: New Version Notification for draft-shelby-core-link-format-00

Zach Shelby <zach@sensinode.com> Tue, 28 September 2010 09:05 UTC

Return-Path: <zach@sensinode.com>
X-Original-To: core@core3.amsl.com
Delivered-To: core@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F228F3A6D37 for <core@core3.amsl.com>; Tue, 28 Sep 2010 02:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.342
X-Spam-Level:
X-Spam-Status: No, score=-3.342 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DtJ3fgisCP-w for <core@core3.amsl.com>; Tue, 28 Sep 2010 02:05:41 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id B6DCF3A6A24 for <core@ietf.org>; Tue, 28 Sep 2010 02:05:40 -0700 (PDT)
Received: from [62.145.172.52] ([62.145.172.52]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id o8S96Hco016188 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <core@ietf.org>; Tue, 28 Sep 2010 12:06:18 +0300
From: Zach Shelby <zach@sensinode.com>
Content-Type: multipart/signed; boundary="Apple-Mail-202-267417792"; protocol="application/pkcs7-signature"; micalg="sha1"
Date: Tue, 28 Sep 2010 12:06:19 +0300
References: <20100928085643.27A7C3A6C7A@core3.amsl.com>
To: core <core@ietf.org>
Message-Id: <12D57F29-D6CC-496B-B37B-519BECFD16F3@sensinode.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [core] Fwd: New Version Notification for draft-shelby-core-link-format-00
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 28 Sep 2010 09:05:48 -0000

http://www.ietf.org/id/draft-shelby-core-link-format-00.txt

This new draft specifies the link format and well-known URI interface for use in CoRE resource discovery separately from the base CoAP draft as per ticket #21. In the process of spinning this into a separate draft, several improvements were made (thanks Mark and Carsten!).  

o The link format ABNF from draft-nottingham-http-link-header was completely re-used, avoiding the need to redefine it.
o Quoted strings were added for string attributes
o Explanation of the target/context URI was added along with use of the relation attribute in-line with draft-nottingham-http-link-header
o References to DNS-SD and mDNS were completely removed as this was found to be misleading in Maastricht
o Well-known URI changed to /.well-known/core to make registration possible (/r was too short)
o Filtering was changed to a MAY
o Proper IANA section was created

I plan on making one slide capturing these changes for tomorrow's interim WG meeting, a 10 minute slot should be enough.

Zach 

Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: September 28, 2010 11:56:43 AM GMT+03:00
> To: zach@sensinode.com
> Subject: New Version Notification for draft-shelby-core-link-format-00 
> 
> 
> A new version of I-D, draft-shelby-core-link-format-00.txt has been successfully submitted by Zach Shelby and posted to the IETF repository.
> 
> Filename:	 draft-shelby-core-link-format
> Revision:	 00
> Title:		 CoRE Link Format
> Creation_date:	 2010-09-28
> WG ID:		 Independent Submission
> Number_of_pages: 10
> 
> Abstract:
> This document defines a link format for use by constrained CoAP web
> servers to describe URIs of resources offered along with other
> attributes.  Based on the HTTP Link Header format, the CoRE link
> format is carried as a payload and is assigned an Internet media
> type.  A well-known URI is defined as a default entry-point for
> requesting the list of links to resources hosted by a server.
> 
> 
> 
> The IETF Secretariat.
> 
> 

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297

v2.23.0 | Report a Bug | By Email