Re: [rtcweb] Fwd: New Version Notification for draft-thomson-rtcweb-alpn-00.txt

Martin Thomson <martin.thomson@gmail.com> Wed, 09 April 2014 19:52 UTC

Return-Path: <martin.thomson@gmail.com>
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 E2D671A043B for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 12:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] 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 k0ZhQ8VdDqUX for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 12:52:43 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB621A03E6 for <rtcweb@ietf.org>; Wed, 9 Apr 2014 12:52:43 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id bs8so10062862wib.5 for <rtcweb@ietf.org>; Wed, 09 Apr 2014 12:52:42 -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-type; bh=cZrYAiph2nbcxfNc4O0W9F3A/lzq9kpimYXkcI7jU2o=; b=M+XYdYI0xUWCC4r5sdPETGcier51UBVenkjMLLWwR+iF6BiCG3OFbhR4yAqc/wBWAf RHC1MxEs1hyYWw253AmMvXKXxO+jkQcZmJpX+tFZmrZ1eyPl1ba92SAtunELKDYsEqXZ WtbDqHk6u6Tft2PgjxFszFLb3z8j8f4vpBKY8VaEE9tTB27inY6zkEZfgQ3Pvf6Vtpdo Ngwxcdtgy4REkzz/qC1M7nybgMu+6AeSEhp/FmNxgTlCp8v8rGDDNSjmhiEPPPC4ig31 +Tnow919Kd9auZ3/W/5s9p8ic5Fv8gc8urESYgMyJNNDIOTbgo66+yTDZyAjPthfTeGu d9Mw==
MIME-Version: 1.0
X-Received: by 10.180.89.211 with SMTP id bq19mr38714126wib.58.1397073162439; Wed, 09 Apr 2014 12:52:42 -0700 (PDT)
Received: by 10.227.144.132 with HTTP; Wed, 9 Apr 2014 12:52:42 -0700 (PDT)
In-Reply-To: <53459BBB.1080505@alum.mit.edu>
References: <20140409180350.13315.51677.idtracker@ietfa.amsl.com> <CABkgnnUfT_bRmFW7j09yWJPEOCz9xEjKjbHa=FXK284aEnyDyQ@mail.gmail.com> <53459BBB.1080505@alum.mit.edu>
Date: Wed, 9 Apr 2014 12:52:42 -0700
Message-ID: <CABkgnnUqyS71bT-PFBjJG5zSi_0Z-4E025Ez2MrbROXP7ZcH7w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/4i-8QAigTYooBHX8Kn4Xf2jGrU8
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Fwd: New Version Notification for draft-thomson-rtcweb-alpn-00.txt
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: <http://www.ietf.org/mail-archive/web/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, 09 Apr 2014 19:52:45 -0000

On 9 April 2014 12:12, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> But what is the *protocol*? I don't see that mentioned in the draft at all.

There are two.  Those two are described (perhaps not explicitly
enough) in the list in Section 2.

> IIUC it must be the multiplexing of STUN, SRTP, and SCTP over DTLS. (Maybe
> not STUN - maybe that is *below* or *beside* DTLS.) I see how it could make
> sense to use ALPN to verify that this is the intended use of the DTLS
> session. But that isn't even mentioned in the draft.

Yeah, STUN isn't inside DTLS, so it doesn't make a lot of sense to
"negotiate" its use.

> And, from a protocol perspective, what is the difference between webrtc and
> c-webrtc? AFAICT this is just two different usages of the same "protocol",
> not two different protocols.

Yep.  But that's what a protocol is.