Re: [Sipbrandy] WGLC: draft-ietf-sipbrandy-osrtp-04 - Christer's review

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 24 May 2018 13:12 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipbrandy@ietfa.amsl.com
Delivered-To: sipbrandy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B2212E895 for <sipbrandy@ietfa.amsl.com>; Thu, 24 May 2018 06:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 M2jHJAnrCA0i for <sipbrandy@ietfa.amsl.com>; Thu, 24 May 2018 06:12:09 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4991B12EAA5 for <sipbrandy@ietf.org>; Thu, 24 May 2018 06:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1527167525; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=cYisoW9njFbu56qlCu3L1uQyP6bmpFYHQkDhLTieZL0=; b=dJ5xSAxKXuvD1OQFmS3DdqoqdqqugG5x9Lmbu6b3KdwsD8dsjTMpHp5RrS3/Be8L mI+5g4KUbo161RozXWVBsG6+sQH5i61e2rAW1EUHLuv/jfYHYvVUknXpeV4RhBbI YJtnacB8y7UXYUdGJeKK52Obsuv3OdWsrjCytSH5oHg=;
X-AuditID: c1b4fb3a-77c239c00000451c-37-5b06ba25aa45
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 79.8F.17692.52AB60B5; Thu, 24 May 2018 15:12:05 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.29]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0382.000; Thu, 24 May 2018 15:11:41 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Andy Hutton <andyhutton.ietf@gmail.com>
CC: "sipbrandy@ietf.org" <sipbrandy@ietf.org>
Thread-Topic: [Sipbrandy] WGLC: draft-ietf-sipbrandy-osrtp-04 - Christer's review
Thread-Index: AQHT2H1MtettfGxkckGZ8W9pjatITaQ+0HeAgAAnchD//+piAIAAJVKA///h1QCAADjngA==
Date: Thu, 24 May 2018 13:11:40 +0000
Message-ID: <D72C9473.307DE%christer.holmberg@ericsson.com>
References: <D6FF722F.2E7B0%christer.holmberg@ericsson.com> <CAB7PXwTrakvHFaLs8sR_BPGtDcrbvmz3NLw1jOBdA8KOeC=Yqg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72F05085@ESESSMB109.ericsson.se> <CAB7PXwQBHvVX_FB+O5TOT_5RM37yhOZOva-P+SePkZvjrf1D2w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72F05308@ESESSMB109.ericsson.se> <CAB7PXwSzc2CpzOm3Y9-JmanDLMQ8e3LDR9hCCpR7nZydZ1m4fg@mail.gmail.com>
In-Reply-To: <CAB7PXwSzc2CpzOm3Y9-JmanDLMQ8e3LDR9hCCpR7nZydZ1m4fg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <9EDA3E89ED005946A5F6A9DC5CC1AD13@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2K7rq7qLrZog/Or1C0urdvKZLFi3Skm ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugStj5/Z29oKH3BXv5m5naWBcy9nFyMkhIWAi MenoM8YuRi4OIYEjjBLP1/5lhnAWM0pc/LyDrYuRg4NNwEKi+582SIOIgLbEuyk7WEFsZgFd iSMfZ4DZwgJBEj1TdrNB1ARLPOo7yQJhh0l8/N0IVsMioCrx6fYXJpCRvALWEi0PqyFWzWCW OPD/IFicUyBQouFkBEg5o4CYxPdTa5ggVolL3HoynwniZgGJJXvOM0PYohIvH/8DGy8qoCex 4cRtdpAxEgJKErc3OEG06kncmDqFDcK2lvjWsYwFwtaWWLbwNdgYXgFBiZMzn7BMYBSfhWTb LCTts5C0z0LSPgtJ+wJG1lWMosWpxcW56UZGeqlFmcnFxfl5enmpJZsYgbF2cMtvqx2MB587 HmIU4GBU4uF9tYMtWog1say4MvcQowQHs5II74IkoBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFe pzSLKCGB9MSS1OzU1ILUIpgsEwenVAMj54Z61oAXdy7e/7H97c015nEHHL99uZU4Z76z9N9D z4rfp9gHaP/6FJ28SFUlfcGk0LMrbZ8+Ms/4s+VYlPZqsXkF0Wefmfmmq+nZVPoLymt1fnpz L7z6jb/QlOpZWR8alj9iXeB7eOsf05paJ/uL93cFGHctlvq06c8uK4EDnbem7pqWGfNBSYml OCPRUIu5qDgRAP06c2CxAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipbrandy/EM57fQpgNI7nphjB7IC4D8_NwT4>
Subject: Re: [Sipbrandy] WGLC: draft-ietf-sipbrandy-osrtp-04 - Christer's review
X-BeenThere: sipbrandy@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SIPBRANDY working group discussion list <sipbrandy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipbrandy/>
List-Post: <mailto:sipbrandy@ietf.org>
List-Help: <mailto:sipbrandy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 13:12:15 -0000

Hi,

>>>>Has there been discussions on whether the subsequent offer really is
>>>>the same?
>>>
>>> Not sure whether this has been discussed explicitly with regard to
>>>this draft.
>>
>> Where has it been discussed? The MMUSIC draft doesn't say anything
>>about subsequent offers either.
>>
>>>> For example, if the initial O/A has resulted in SAVP, would you still
>>>>use AVP in a subsequent offer?
>>>
>>> Yes the recommendation would be to use AVP in a subsequent offer
>>>otherwise things can go wrong when you consider things like 3PCC etc.
>>
>> What if the answerer, who included SAVP in the initial answer, sends a
>>subsequent offer? Will it keep SAVP in that offer, or will it switch to
>>AVP?
>>
>
>This really depends on the preferences of the answerer as to whether
>it requires SRTP or is willing to try OSRTP it is the same
>considerations as made when sending the initial offer.


So, that endpoint is allowed to require SRTP, but the endpoint that sent
the initial offer must try OSRTP if it sends a subsequent offer???

I think the rules for subsequent offers shall be the same for both
endpoints, i.e., either shall both endpoints be allowed to ³require² SRTP
in a subsequent offer, OR both endpoints must try OSRTP in a subsequent
offer.

In addition, if security was NOT negotiated in the in the initial o/a
exchange, then I guess each endpoint can choose whether to use OSRTP or
not in subsequent offers?

Regards,

Christer