Re: [ietf-types] Review of application/link-format registration
Peter Saint-Andre <stpeter@stpeter.im> Tue, 14 February 2012 20:23 UTC
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 832AB21F852A for <ietf-types@ietfa.amsl.com>; Tue, 14 Feb 2012 12:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.547
X-Spam-Level:
X-Spam-Status: No, score=-102.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vsL1XIDUamSy for <ietf-types@ietfa.amsl.com>; Tue, 14 Feb 2012 12:23:04 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 11AE421F8505 for <ietf-types@ietf.org>; Tue, 14 Feb 2012 12:23:02 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id F261540058; Tue, 14 Feb 2012 13:33:50 -0700 (MST)
Message-ID: <4F3AC2A4.8050203@stpeter.im>
Date: Tue, 14 Feb 2012 13:23:00 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Zach Shelby <zach@sensinode.com>
References: <625B50EE-D837-46C2-A5BB-1B134DC62D9E@sensinode.com>
In-Reply-To: <625B50EE-D837-46C2-A5BB-1B134DC62D9E@sensinode.com>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Review of application/link-format registration
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2012 20:23:04 -0000
<hat type='AD'/> Note: I'll request an IETF Last Call on draft-ietf-core-link-format-11 now, which will run concurrently with the expert reviews. I am doing so in order to get all the reviews finished before IETF 83. Just FYI! Peter On 2/14/12 11:47 AM, Zach Shelby wrote: > draft-ietf-core-link-format-11 has passed WGLC in the CoRE WG. This draft has a registration for a new media type in Section 7.3 (also copied below). Your comments would be appreciated. > > http://tools.ietf.org/html/draft-ietf-core-link-format-11#section-7.3 > > Thanks, > Zach Shelby > > 7.3. New link-format Internet media type > > This memo registers the a new Internet media type for the CoRE link > format, application/link-format. > > Type name: application > > Subtype name: link-format > > Required parameters: None > > Optional parameters: None > > Encoding considerations: Binary data > > Security considerations: > > Multicast requests using CoAP for the well-known link-format > resources could be used to perform denial of service on a constrained > network. A multicast request SHOULD only be accepted if the request > is sufficiently authenticated and secured using e.g. IPsec or an > appropriate object security mechanism. > > CoRE link format parsers should be aware that a link description may > be cyclical, i.e., contain a link to itself. These cyclical links > could be direct or indirect (i.e., through referenced link > resources). Care should be taken when parsing link descriptions and > accessing cyclical links. > > Interoperability considerations: > > Published specification: [[ this document ]] > > Applications that use this media type: CoAP server and client > implementations for resource discovery and HTTP applications that use > the link-format as a payload. > > Additional information: > > Magic number(s): > > File extension(s): *.wlnk > > Macintosh file type code(s): > > Intended usage: COMMON > > Restrictions on usage: None > > Author: CoRE WG > > Change controller: IETF > > > _______________________________________________ > ietf-types mailing list > ietf-types@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-types
- [ietf-types] Review of application/link-format re… Zach Shelby
- Re: [ietf-types] Review of application/link-forma… Peter Saint-Andre
- Re: [ietf-types] Review of application/link-forma… Peter Saint-Andre