RFC 5524 on Extended URLFETCH for Binary and Converted Parts
rfc-editor@rfc-editor.org Mon, 04 May 2009 23:44 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFAE028C1B0; Mon, 4 May 2009 16:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.915
X-Spam-Level:
X-Spam-Status: No, score=-16.915 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 cEN1aF4aPuJX; Mon, 4 May 2009 16:44:29 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id E7B4828C1A5; Mon, 4 May 2009 16:44:29 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id E37B829B29C; Mon, 4 May 2009 16:42:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5524 on Extended URLFETCH for Binary and Converted Parts
From: rfc-editor@rfc-editor.org
Message-Id: <20090504234245.E37B829B29C@bosco.isi.edu>
Date: Mon, 04 May 2009 16:42:45 -0700
Cc: lemonade@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 04 May 2009 23:44:30 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 5524
Title: Extended URLFETCH for Binary and
Converted Parts
Author: D. Cridland
Status: Standards Track
Date: May 2009
Mailbox: dave.cridland@isode.com
Pages: 9
Characters: 15915
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-cridland-urlfetch-binary-03.txt
URL: http://www.rfc-editor.org/rfc/rfc5524.txt
The URLFETCH command defined as part of URLAUTH provides a mechanism
for third parties to gain access to data held within messages in a
user's private store; however, this data is sent verbatim, which is
not suitable for a number of applications. This memo specifies a
method for obtaining data in forms suitable for non-mail
applications. [STANDARDS TRACK]
This document is a product of the Enhancements to Internet email to support diverse service environments Working Group of the IETF.
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
USC/Information Sciences Institute