RFC 7578 on Returning Values from Forms: multipart/form-data

rfc-editor@rfc-editor.org Wed, 15 July 2015 05:51 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 506CE1A7014; Tue, 14 Jul 2015 22:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.457
X-Spam-Level:
X-Spam-Status: No, score=-99.457 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_ADOBE2=2.455, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TwpOtBayjvtM; Tue, 14 Jul 2015 22:51:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 1829F1A6FFF; Tue, 14 Jul 2015 22:51:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3737E180478; Tue, 14 Jul 2015 22:47:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7578 on Returning Values from Forms: multipart/form-data
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150715054756.3737E180478@rfc-editor.org>
Date: Tue, 14 Jul 2015 22:47:56 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/-QrJ1ekYFn3wBVuyqZStdOX3p64>
Cc: drafts-update-ref@iana.org, apps-discuss@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 15 Jul 2015 05:51:33 -0000

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

        
        RFC 7578

        Title:      Returning Values from Forms: multipart/form-data 
        Author:     L. Masinter
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2015
        Mailbox:    masinter@adobe.com
        Pages:      15
        Characters: 30240
        Obsoletes:  RFC 2388

        I-D Tag:    draft-ietf-appsawg-multipart-form-data-11.txt

        URL:        https://www.rfc-editor.org/info/rfc7578

        DOI:        http://dx.doi.org/10.17487/RFC7578

This specification defines the multipart/form-data media type, which
can be used by a wide variety of applications and transported by a
wide variety of protocols as a way of returning a set of values as
the result of a user filling out a form.  This document obsoletes
RFC 2388.

This document is a product of the Applications Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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