RFC 6570 on URI Template

rfc-editor@rfc-editor.org Tue, 27 March 2012 11:07 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4E721F881F for <ietf-announce@ietfa.amsl.com>; Tue, 27 Mar 2012 04:07:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.127
X-Spam-Level:
X-Spam-Status: No, score=-102.127 tagged_above=-999 required=5 tests=[AWL=-0.127, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 qtWLg3vEdcFZ for <ietf-announce@ietfa.amsl.com>; Tue, 27 Mar 2012 04:07:33 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id EEC1F21F8844 for <ietf-announce@ietf.org>; Tue, 27 Mar 2012 04:07:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 96AD572F4EE; Tue, 27 Mar 2012 04:05:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6570 on URI Template
From: rfc-editor@rfc-editor.org
Message-Id: <20120327110559.96AD572F4EE@rfc-editor.org>
Date: Tue, 27 Mar 2012 04:05:59 -0700 (PDT)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Tue, 27 Mar 2012 11:07:33 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6570

        Title:      URI Template 
        Author:     J. Gregorio, R. Fielding,
                    M. Hadley, M. Nottingham,
                    D. Orchard
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2012
        Mailbox:    joe@bitworking.org, 
                    fielding@gbiv.com, 
                    mhadley@mitre.org,  mnot@mnot.net, 
                    orchard@pacificspirit.com
        Pages:      34
        Characters: 79813
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-gregorio-uritemplate-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6570.txt

A URI Template is a compact sequence of characters for describing a
range of Uniform Resource Identifiers through variable expansion.
This specification defines the URI Template syntax and the process
for expanding a URI Template into a URI reference, along with
guidelines for the use of URI Templates on the Internet.  
[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