RFC 7639 on The ALPN HTTP Header Field

rfc-editor@rfc-editor.org Thu, 27 August 2015 02:56 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 F15391A86E3 for <ietf-announce@ietfa.amsl.com>; Wed, 26 Aug 2015 19:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 PTA0mwPrZM8u for <ietf-announce@ietfa.amsl.com>; Wed, 26 Aug 2015 19:56:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACF61ACDC8 for <ietf-announce@ietf.org>; Wed, 26 Aug 2015 19:56:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5980A182534; Wed, 26 Aug 2015 19:56:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7639 on The ALPN HTTP Header Field
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150827025602.5980A182534@rfc-editor.org>
Date: Wed, 26 Aug 2015 19:56:02 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/_pNPNTt07IbUDCakOmj29cP_Thg>
Cc: drafts-update-ref@iana.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: Thu, 27 Aug 2015 02:56:30 -0000

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

        
        RFC 7639

        Title:      The ALPN HTTP Header Field 
        Author:     A. Hutton, J. Uberti, M. Thomson
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2015
        Mailbox:    andrew.hutton@unify.com, 
                    justin@uberti.name, 
                    martin.thomson@gmail.com
        Pages:      7
        Characters: 14455
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-httpbis-tunnel-protocol-05.txt

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

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

This specification allows HTTP CONNECT requests to indicate what
protocol is intended to be used within the tunnel once established,
using the ALPN header field.

This document is a product of the HyperText Transfer Protocol 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