Re: [rtcweb] JSEP: Why always offer actpass?

Justin Uberti <juberti@google.com> Tue, 25 November 2014 01:11 UTC

Return-Path: <juberti@google.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 627151A6F57 for <rtcweb@ietfa.amsl.com>; Mon, 24 Nov 2014 17:11:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.112
X-Spam-Level:
X-Spam-Status: No, score=0.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6, J_CHICKENPOX_57=0.6, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Hde7FM416OFF for <rtcweb@ietfa.amsl.com>; Mon, 24 Nov 2014 17:11:43 -0800 (PST)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C30521A1BF0 for <rtcweb@ietf.org>; Mon, 24 Nov 2014 17:11:42 -0800 (PST)
Received: by mail-vc0-f177.google.com with SMTP id ij19so4560713vcb.8 for <rtcweb@ietf.org>; Mon, 24 Nov 2014 17:11:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=mtZ4RjqwRbBd5mLgdk0Wmv4qB3eJIwiGGy/7wFRcv1g=; b=BE/IHBhVtLm3Q06glaKSKIeBOgykiCg6jU4qAWZ+erjZZ5KtPCn7SHbPRRmJZqJCy4 lbIpXLDswrlKW8wNMcJdaKVW4qmfCbNPEJYpWlOl/jQvqX0vnR6C1qBQSwOJbw09PNT8 GbAD3y0EuQMvy9B3hgo0NKeotJluWZHKQLf5DuryRWEFtMLgpc//kImnk4VkGbzdDZB4 EfDJlPw+VJObzwup7qEydvRkAHOqs23zaA2m6Y9k4wNV7lGzNLBZwftnoxoc9VvwNFd9 S6Pa331S9WBzwGwYfvmOwY37asF0CF1nAVc6rs1kaIkUN97T6j3vNoICVj+UVzYPeq/M S7bw==
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:from:date :message-id:subject:to:cc:content-type; bh=mtZ4RjqwRbBd5mLgdk0Wmv4qB3eJIwiGGy/7wFRcv1g=; b=XNJ99OXfvvcJ9iKZIjAarbPySfTpPrOA/v5qa+5JX8Cxz3xaB0gOzxEJX9bvf599kL Uw8aOKekbz6EQyNbrKVdbHWzPOFInGy3ou2+LyYChdyrI8TYdK+Ks1J6I62VCXruvDTi 6prkhUq1dO7EYHBX9LBhgi57REXXG5oDmE05Qm2uOkk6EqcCgJU+OUspNOhsiD4cWFBs JsB2/Yl0OVt7Uvq6yNNXMY8pPhuWGqCDvnOnwZdqqgB6HepEBknyGKH511E5elwhLuMf tAZOrkqTRfgh9gqrg4rEvwmfOYwlgTBqsYj+mPM9NzxzfxcPas8dBcfl9CyioIqqzuFI 7UDQ==
X-Gm-Message-State: ALoCoQm9jmxWv0QSfR/pXFc7kVfVrfvXAm2eec4C+3c48RjpqjE9pl+B+lFD5PJCOVGqnb6qSGFu
X-Received: by 10.53.10.65 with SMTP id dy1mr11361126vdd.51.1416877901762; Mon, 24 Nov 2014 17:11:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.237.130 with HTTP; Mon, 24 Nov 2014 17:11:21 -0800 (PST)
In-Reply-To: <1447FA0C20ED5147A1AA0EF02890A64B1D0D579E@ESESSMB209.ericsson.se>
References: <1447FA0C20ED5147A1AA0EF02890A64B1D0D579E@ESESSMB209.ericsson.se>
From: Justin Uberti <juberti@google.com>
Date: Mon, 24 Nov 2014 17:11:21 -0800
Message-ID: <CAOJ7v-1ztXies0-W3B2=zWaydeLTuR8tU7v15nqyTw+MwGE+rw@mail.gmail.com>
To: =?UTF-8?Q?Stefan_H=C3=A5kansson_LK?= <stefan.lk.hakansson@ericsson.com>
Content-Type: multipart/alternative; boundary=001a113659d0066fe50508a498db
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/1A09Uz8AkQ2CEo5Eq_NlDGD0jck
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP: Why always offer actpass?
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: Tue, 25 Nov 2014 01:11:44 -0000

Quoth RFC5763, Section 5:

   o  The endpoint MUST use the setup attribute defined in [RFC4145
<https://tools.ietf.org/html/rfc4145>].
      The endpoint that is the offerer MUST use the setup attribute
      value of setup:actpass and be prepared to receive a client_hello
      before it receives the answer.  The answerer MUST use either a
      setup attribute value of setup:active or setup:passive.  Note that
      if the answerer uses setup:passive, then the DTLS handshake will
      not begin until the answerer is received, which adds additional
      latency. setup:active allows the answer and the DTLS handshake to
      occur in parallel.  Thus, setup:active is RECOMMENDED.  Whichever
      party is active MUST initiate a DTLS handshake by sending a

      ClientHello over each flow (host/port quartet).


However I concur that the existing roles should be maintained, e.g. the
answerer must choose active or passive appropriately. Chrome will fail upon
an attempted role change.

On Mon, Nov 24, 2014 at 7:36 AM, Stefan Håkansson LK <
stefan.lk.hakansson@ericsson.com> wrote:

> Hi,
>
> I'm looking into the JSEP draft. One thing that seems strange is that in
> every offer the role offered is "actpass", also for existing
> connections. As I read section 7.3 of
> https://www.rfc-editor.org/rfc/rfc4145.txt the established roles should
> be maintained in such situations.
>
> What is the reason for the always offering "actpass" also for
> established roles/connections?
>
> Stefan
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>