[link-relations] Fwd: RFC 5988 on Web Linking

Mark Nottingham <mnot@mnot.net> Fri, 29 October 2010 05:34 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: link-relations@core3.amsl.com
Delivered-To: link-relations@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D5453A6A2C for <link-relations@core3.amsl.com>; Thu, 28 Oct 2010 22:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.213
X-Spam-Level:
X-Spam-Status: No, score=-105.213 tagged_above=-999 required=5 tests=[AWL=-3.214, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_WHITELIST=-100]
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 4JbfACpI1B6P for <link-relations@core3.amsl.com>; Thu, 28 Oct 2010 22:34:54 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id A2F853A6A1E for <link-relations@ietf.org>; Thu, 28 Oct 2010 22:34:03 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A941D509D9 for <link-relations@ietf.org>; Fri, 29 Oct 2010 01:35:50 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 29 Oct 2010 16:35:47 +1100
References: <20101029053328.1BE96E070C@rfc-editor.org>
To: link-relations@ietf.org
Message-Id: <AF0EA954-1B02-4325-A939-BABF3065C9FC@mnot.net>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [link-relations] Fwd: RFC 5988 on Web Linking
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/link-relations>
List-Post: <mailto:link-relations@ietf.org>
List-Help: <mailto:link-relations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 05:34:57 -0000

FYI.

Begin forwarded message:

> From: rfc-editor@rfc-editor.org
> Date: 29 October 2010 4:33:28 PM AEDT
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: rfc-editor@rfc-editor.org
> Subject: RFC 5988 on Web Linking
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 5988
> 
>        Title:      Web Linking 
>        Author:     M. Nottingham
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       October 2010
>        Mailbox:    mnot@mnot.net
>        Pages:      23
>        Characters: 46834
>        Updates:    RFC4287
> 
>        I-D Tag:    draft-nottingham-http-link-header-10.txt
> 
>        URL:        http://www.rfc-editor.org/rfc/rfc5988.txt
> 
> This document specifies relation types for Web links, and defines a
> registry for them.  It also defines the use of such links in HTTP
> headers with the Link header field.  [STANDARDS-TRACK]
> 
> This is now a Proposed Standard Protocol.
> 
> 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 Internet
> Official Protocol Standards (STD 1) 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
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
> For downloading RFCs, see http://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
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

--
Mark Nottingham   http://www.mnot.net/