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

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Thu, 04 December 2014 14:43 UTC

Return-Path: <stefan.lk.hakansson@ericsson.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 435D21AD3B3 for <rtcweb@ietfa.amsl.com>; Thu, 4 Dec 2014 06:43:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level:
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 alAG9_fAbrqh for <rtcweb@ietfa.amsl.com>; Thu, 4 Dec 2014 06:43:02 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 824F61AD3AD for <rtcweb@ietf.org>; Thu, 4 Dec 2014 06:43:01 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-be-548072f3335a
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 46.CA.04076.3F270845; Thu, 4 Dec 2014 15:42:59 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0195.001; Thu, 4 Dec 2014 15:42:59 +0100
From: =?Windows-1252?Q?Stefan_H=E5kansson_LK?= <stefan.lk.hakansson@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Justin Uberti <juberti@google.com>
Thread-Topic: [rtcweb] JSEP: Why always offer actpass?
Thread-Index: AdAH/G6saC/Ce4vxTgqv23nLTon8JA==
Date: Thu, 4 Dec 2014 14:42:58 +0000
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1D0EEA4E@ESESSMB209.ericsson.se>
References: <1447FA0C20ED5147A1AA0EF02890A64B1D0D579E@ESESSMB209.ericsson.se> <CAOJ7v-1ztXies0-W3B2=zWaydeLTuR8tU7v15nqyTw+MwGE+rw@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1D0D5A4B@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E63C45B@US70UWXCHMBA02.zam.alcatel-lucent.com> <1447FA0C20ED5147A1AA0EF02890A64B1D0D5FB6@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E63C90D@US70UWXCHMBA02.zam.alcatel-lucent.com> <1447FA0C20ED5147A1AA0EF02890A64B1D0D86B9@ESESSMB209.ericsson.se> <CAD5OKxskhmnHO6rLB4t7vM6Y=fVf0PwYPXsfONJjM=wzx8vHoA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D53F719@ESESSMB209.ericsson.se> <CAD5OKxt+3Tn1SiHu7u_t7AixBVS1ev0Z=vdZg0mMwmm-Tg74yA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D54BB03@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E64233E@US70UWXCHMBA02.zam.alcatel-lucent.com> <1447FA0C20ED5147A1AA0EF02890A64B1D0E3909@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E6423CC@US70UWXCHMBA02.zam.alcatel-lucent.com> <1447FA0C20ED5147A1AA0EF02890A64B1D0E39A9@ESESSMB209.ericsson.se> <CAOJ7v-191C=Jsf0vuBomgKXMYGRakatP9QS+mMYG1Try59yYrg@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1D0EE2BC@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D577322@ESESSMB209.ericsson.se> <CAOJ7v-2d0qMaWhNThW=ywfmBMp-7LMJNhi-fj8USk5D0=2RwCA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D577B77@ESESSMB209.ericsson.se> <CAOJ7v-3u6nL5J8wYpWN9SS8DboMh4WNYznJS-24TepZRweJz0w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D577CB5@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D578C4D@ESESSMB209.ericsson.se> <1447FA0C20ED5147A1AA0EF02890A64B1D0EE9AC@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D578E30@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyM+Jvje7nooYQg/cnFS22ThWyWPuvnd2B yWPBplKPJUt+MgUwRXHZpKTmZJalFunbJXBlnN17jKXgHHvF6bctTA2Mi9i6GDk5JARMJM5O 7mSEsMUkLtxbDxTn4hASOMIo8frqNHYIZzGjxMcly4CqODjYBIIlmv66gTSICMRI/Oq7A9bM LKAucWfxOXYQW1jAVGLSxWVMEDVmEgtPTmCEsPUkbn65wAJiswioSBy72Axm8wr4Suz7f5AJ YtdvXonOL7+YQRKMQBd9P7WGCWKBuMStJ/OZIC4VkFiy5zwzhC0q8fLxP1aQ2yQEFCWW98tB lBtIvD83nxnC1pZYtvA1M8QuQYmTM5+wTGAUnYVk6iwkLbOQtMxC0rKAkWUVo2hxanFxbrqR kV5qUWZycXF+nl5easkmRmCMHNzy22oH48HnjocYBTgYlXh4Dc7VhwixJpYVV+YeYpTmYFES 5114bl6wkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsZ1Qmd5Sz/nGolc31T2qLSmaT1LvUmM 9CqZBd4a3Tl/pBZ5mmwov91SvpLxQiuf7hXlwr+z+1bvbmeW2F63Wtj2/o0b7f/OTntlH6P6 VuXXRIMLiWFeKj/Edyk+9U22OvfwxWrpAzHXr8yw+tyj5xESMTvjzBrRqSzfPvcfzJ34/3Td 3Alxf8SUWIozEg21mIuKEwE4czsWcgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/yu-HrP3n4c92rfgOLsfYuDtUOo0
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: Thu, 04 Dec 2014 14:43:04 -0000

On 04/12/14 15:08, Christer Holmberg wrote:
> Hi,

>>> Once a DTLS connection has been established, if the
>>> 'active/passive' status of the endpoints change during a session,
>>> a new DTLS connection MUST be established.  Therefore, endpoints
>>> SHOULD NOT change the ‘active/passive’ status in subsequent
>>> offers and answers,
>>
>> Did not the discussion (for rtcweb) conclude that subsequent offers
>> should offer actpass, but that subsequent answers must say the same
>> as the previous answer?
>
> In the Offer/Answer section, I can define more details regarding the
> values (actpass etc) to use.
>
> BUT, the question is whether we want to allow the endpoints to
> trigger a new DTLS connection by changing the active/passive status
> or not. The text above says SHOULD NOT change the active/passive
> status.

OK, makes sense to me.