RFC 7235 on Hypertext Transfer Protocol (HTTP/1.1): Authentication

rfc-editor@rfc-editor.org Sat, 07 June 2014 01:18 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 02C901A02CC for <ietf-announce@ietfa.amsl.com>; Fri, 6 Jun 2014 18:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 FvlofoyumNx3 for <ietf-announce@ietfa.amsl.com>; Fri, 6 Jun 2014 18:18:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 488BC1A02BE for <ietf-announce@ietf.org>; Fri, 6 Jun 2014 18:18:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 35887180479; Fri, 6 Jun 2014 18:16:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7235 on Hypertext Transfer Protocol (HTTP/1.1): Authentication
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140607011659.35887180479@rfc-editor.org>
Date: Fri, 06 Jun 2014 18:16:59 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/fN03r8rjNAwhxSuhy1sSimEUQSY
Cc: drafts-update-ref@iana.org, ietf-http-wg@w3.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: <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: Sat, 07 Jun 2014 01:18:11 -0000

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

        
        RFC 7235

        Title:      Hypertext Transfer Protocol (HTTP/1.1): Authentication 
        Author:     R. Fielding, Ed.,
                    J. Reschke, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2014
        Mailbox:    fielding@gbiv.com, 
                    julian.reschke@greenbytes.de
        Pages:      19
        Characters: 38142
        Obsoletes:  RFC 2616
        Updates:    RFC 2617

        I-D Tag:    draft-ietf-httpbis-p7-auth-26.txt

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

The Hypertext Transfer Protocol (HTTP) is a stateless application-
level protocol for distributed, collaborative, hypermedia information
systems.  This document defines the HTTP Authentication framework.

This document is a product of the Hypertext Transfer Protocol Bis 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 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/search
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