Re: [rtcweb] Sub-protocol registry update

Martin Thomson <martin.thomson@gmail.com> Wed, 16 March 2016 01:04 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6595B12D816 for <rtcweb@ietfa.amsl.com>; Tue, 15 Mar 2016 18:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tUxrawfbk_Qk for <rtcweb@ietfa.amsl.com>; Tue, 15 Mar 2016 18:04:12 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28E6812DEBD for <rtcweb@ietf.org>; Tue, 15 Mar 2016 18:04:10 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id g203so45572903iof.2 for <rtcweb@ietf.org>; Tue, 15 Mar 2016 18:04:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=9HY6mfo6h+L/DbW0DaIQlCoUz8WvHxKSN9VRQXEyqDU=; b=IMmG1ua3Gkz3b1Hn8hgw1lRxfCgd7HoQNFTdck046hEFx9p1QdoWGn6M85J7D7+Uv2 w1IlbtEmH0rTaPiQEF3nyYNB46/13XulYYdyavjVphGO0iB9hRcf22ml2QwtLtrcdIVz 8kQXiIj1vFc4cQwphJ00Kw2IqTHKvzvL8ubyZcEeawcDTThE/9NTKolPwbL3PQYtQPRE AWGAqWLd3xmUHOTevSA1GekjENjuEnTF9Pxm1q0S86Abhuf1kC+KK6ZLsB1KkHWw2LGT BFnIlBVF2nnOXcMJWbI6y0sIk10u/zsd4OIPq0vVZPk9Tq0bAG+iN55Uc1/8mVFAbVb7 rgyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=9HY6mfo6h+L/DbW0DaIQlCoUz8WvHxKSN9VRQXEyqDU=; b=F8OBiiwqAbgXWmiAvtl73zhF3VFux12ljTEWkKm8FlPPIxJxyeUQYghoptVU2hSO44 HVt9HzvSaeOhXtKOurMT+ZbuJnfieP/Xb4DOIm46hhkZ4+zHPAR1bxL55jki/JY+SEgK C3F9H0+rLYMSlkmtyGbZnKDDErq5Pzgj2IAOCD/jmhVKn1+/t8rNvxKK1IDvgrSnKPU2 1ytCewBbW76xHFxKFxPOI3krq+9Vzx3UEcc51wtsaPwwROAkxZ32NoLYIZmpLG0WqPsn nRA+gJoZBZjn0GqAFitAwaYPZjDI8h2voDAvxHpgQNMpBktr8Jx6PVlhy9OGxCsk5r18 Ljxg==
X-Gm-Message-State: AD7BkJLGd8JKf8+c2NR6BfqIVL5Fhg+B+ucVlabpXsQQCx4eBlQITJiNb4N+/kw3KWffdgB54KYNLQbUsch47Q==
MIME-Version: 1.0
X-Received: by 10.107.131.105 with SMTP id f102mr1721518iod.190.1458090249390; Tue, 15 Mar 2016 18:04:09 -0700 (PDT)
Received: by 10.36.43.5 with HTTP; Tue, 15 Mar 2016 18:04:09 -0700 (PDT)
In-Reply-To: <56E856BB.4080502@alvestrand.no>
References: <CA+9kkMCRPACwb+SEZXy7JsRWomHq9mwEJ=CgNye8Yo6pXhCk7w@mail.gmail.com> <56E856BB.4080502@alvestrand.no>
Date: Wed, 16 Mar 2016 12:04:09 +1100
Message-ID: <CABkgnnUL+oPyCAgaiFaA+fL=Eu04QpgypdRJ73Dbu+62sV1v7g@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/7ErM6qwxA8SyK_amIYNzUeqn6jY>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Sub-protocol registry update
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 16 Mar 2016 01:04:19 -0000

This looks fine.  I checked.

I shouldn't have checked.

"(╯°□°)╯︵ ┻━┻)" is a valid subprotocol name according to both the
WebRTC spec and draft-ietf-rtcweb-data-protocol-09.  However, this is
not permitted in thewebsocketprotocol.  RFC 6455 says that I can't
register it, but what happens if I try to use it?

FWIW, I have no problem whatsoever with the protocol accepting more
values than might be permitted elsewhere.  But we should confirm that
this is fine; acknowledging the highly advanced state of the protocol
document (RFC editor queue, MISSREF).

Maybe our friends in the WebRTC WG in the W3C (whoever they are)
should address this.

On 16 March 2016 at 05:38, Harald Alvestrand <harald@alvestrand.no> wrote:
> On 03/15/2016 05:05 PM, Ted Hardie wrote:
>
> So, I'll wait a day or two more for objections, but folks on the websockets
> side seem to be generally okay with this text:
>
> "The tokens registered in the Websockets sub-protocol registry created by
> RFC 6445 Section 11.5 are matched using case-sensitive string match.  IANA
> is, however, instructed to decline registrations in the registry which
> differ only as to case, in order to minimize potential confusion among
> different registered versions.  For other useful advice on avoiding
> collision, registrants are encourage to consult the non-normative section
> 1.9 of RFC 6445."
>
> (See the thread starting here:
> https://mailarchive.ietf.org/arch/msg/hybi/Ax-UqERaQ1P8KDzroBTQYhocjt0.
> Note especially Takeshi Yoshino's note, which points out that even
> websockets needs this clarification, as the behavior of Chrome and Firefox
> differs. )
>
> I think the cleanest approach here is a very short update to RFC 6445.
> Anyone on this list have heartburn with that approach to resolving this?
>
>
> I'm very happy with this approach and resolution.
>
>
> regards,
>
> Ted
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>