IETF Logo Mail Archive

[rtcweb] Clarification in draft-ietf-rtcweb-transports-11

Cullen Jennings <fluffy@iii.ca> Thu, 04 February 2016 12:29 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF381B2E04 for <rtcweb@ietfa.amsl.com>; Thu, 4 Feb 2016 04:29:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.047
X-Spam-Level: *
X-Spam-Status: No, score=1.047 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DATE_IN_PAST_12_24=1.049, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 toevYLdtttwo for <rtcweb@ietfa.amsl.com>; Thu, 4 Feb 2016 04:29:17 -0800 (PST)
Received: from smtp81.iad3a.emailsrvr.com (smtp81.iad3a.emailsrvr.com [173.203.187.81]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F7501B2E03 for <rtcweb@ietf.org>; Thu, 4 Feb 2016 04:29:17 -0800 (PST)
Received: from smtp3.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp3.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id A2285300473; Thu, 4 Feb 2016 07:29:16 -0500 (EST)
X-Auth-ID: fluffy@iii.ca
Received: by smtp3.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 34FA330049C; Thu, 4 Feb 2016 07:29:16 -0500 (EST)
X-Sender-Id: fluffy@iii.ca
Received: from rtp-vpn6-1416.cisco.com ([UNAVAILABLE]. [173.38.117.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.5.4); Thu, 04 Feb 2016 07:29:16 -0500
From: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 03 Feb 2016 11:16:29 -0400
Message-Id: <F63DF3E8-51BF-4142-923A-663D053483C8@iii.ca>
To: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/9jPglE52zl5YwspPgS9fERozWqY>
Cc: Harald Alvestrand <hta@google.com>
Subject: [rtcweb] Clarification in draft-ietf-rtcweb-transports-11
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 12:29:18 -0000

I think we need to make the ALPN a bit more explicit. We agreed to include the ALPN header so that a proxy knows it might receive video packet rates tunnelled across it. However the text on this is not 100% clear. Right now it says

   If it does so, it MUST support the "ALPN" header as
   specified in [RFC7639],

But some people have posted out including this header is optional in 7639 so there might be some ubiquity here about what is meant. I think we should change the word “support” to “include” to make it clear this needs to be sent to the proxy so that it would read

    If it does so, it MUST include the "ALPN" header as
   specified in [RFC7639],

I believe that correctly reflects what we intended on this. There is no requirement for the proxy to understand or do anything with this header. Old proxies will just ignore it and cary on as if it was not there. 

Cullen

(with my individual contributor hat on)

v2.23.0 | Report a Bug | By Email