IETF Logo Mail Archive

[Geopriv] HELD - support question for RFC 7540 (HTTP/2)

Roger Marshall <RMarshall@telecomsys.com> Wed, 23 September 2015 22:09 UTC

Return-Path: <prvs=1708c9cfd9=RMarshall@telecomsys.com>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEE3E1B2CEC for <geopriv@ietfa.amsl.com>; Wed, 23 Sep 2015 15:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 v_a3Kqusrp5R for <geopriv@ietfa.amsl.com>; Wed, 23 Sep 2015 15:09:58 -0700 (PDT)
Received: from sea-mx-02.telecomsys.com (sea-mx-02.telecomsys.com [199.165.246.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CF031B2CDE for <geopriv@ietf.org>; Wed, 23 Sep 2015 15:09:58 -0700 (PDT)
Received: from SEA-EXCAS-2.telecomsys.com (exc2010-local2.telecomsys.com [10.32.12.187]) by sea-mx-02.telecomsys.com (8.14.7/8.14.7) with ESMTP id t8NM9rLT028904 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <geopriv@ietf.org>; Wed, 23 Sep 2015 15:09:54 -0700
Received: from SEA-EXMB-1.telecomsys.com ([169.254.1.231]) by SEA-EXCAS-2.telecomsys.com ([10.32.12.187]) with mapi id 14.03.0248.002; Wed, 23 Sep 2015 15:09:53 -0700
From: Roger Marshall <RMarshall@telecomsys.com>
To: "GEOPRIV WG (geopriv@ietf.org)" <geopriv@ietf.org>
Thread-Topic: HELD - support question for RFC 7540 (HTTP/2)
Thread-Index: AdD2TErhOh2mgxjIQ9u+MjrdWt+sVw==
Date: Wed, 23 Sep 2015 22:09:53 +0000
Message-ID: <FBD5AAFFD0978846BF6D3FAB4C892ACC28EA66A5@SEA-EXMB-1.telecomsys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.32.12.134]
Content-Type: multipart/alternative; boundary="_000_FBD5AAFFD0978846BF6D3FAB4C892ACC28EA66A5SEAEXMB1telecom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/geopriv/y7eHVe4VJPvnZyVbpuAV3oGMx1k>
Subject: [Geopriv] HELD - support question for RFC 7540 (HTTP/2)
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/geopriv/>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2015 22:10:00 -0000

What are the implications for HTTP/2 support for the HELD protocol (e.g., RFC 6155)?  Does HELD support for RFC 7540 require a new IETF Internet draft or not?

I'd be happy to hear from a minimum of 2 or 3 folks on this.

Thanks in advance.

Roger Marshall


CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.

v2.23.0 | Report a Bug | By Email