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

Andy Hutton <andyhutton.ietf@gmail.com> Fri, 25 May 2018 11:06 UTC

Return-Path: <andyhutton.ietf@gmail.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 E9B7D124F57 for <sipbrandy@ietfa.amsl.com>; Fri, 25 May 2018 04:06:10 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 BH-JWdWYSbZB for <sipbrandy@ietfa.amsl.com>; Fri, 25 May 2018 04:06:09 -0700 (PDT)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::229]) (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 827C4124D68 for <sipbrandy@ietf.org>; Fri, 25 May 2018 04:06:09 -0700 (PDT)
Received: by mail-ua0-x229.google.com with SMTP id i3-v6so3196132uad.4 for <sipbrandy@ietf.org>; Fri, 25 May 2018 04:06:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=xPKDMEXgoV/Ka/ZROFiLUiX2y5Lf6x654mbfKcuJUec=; b=BsKTy3zHR1QVKkTMVmOolc6PuAhSj/rG3vVKExgfu2cloTTOpJpZa45Gz2ed+XqNUc CFG6WJ+M0c26zJpv90l8OUzVDGWf4vM6o+tiLcuKhNkt314Uu0oTDJuqcVfHpXz4ixza X5DVHQ83hpsx6UpSIBZPLk7lr8BXhYxUiU8KPW15rIQ7u4zqETaKyoF2nkC15XWZP47q K+Gy/k6IEZpLmQ9VY9C2FlEe6BNijFUu4VbDK5KhGP/TKQJLAZ2nztEkguXuyVwfyTzu L38HD+YsySz04NQ9jZxWInBGDYbLxxX//rbe6q2dFMOD1V6Ft90CdASQ8RvyXpA75k33 sewA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=xPKDMEXgoV/Ka/ZROFiLUiX2y5Lf6x654mbfKcuJUec=; b=tVEdzeK0/AQeSNeg231zxnBc4p36+95IA226Tvtak2LL8aEILEVF4dvTPoBcrgm3oP NRcvt5T1C32E5AVBte7sJDzkbGCAjVhoDuqqIp7Rg4FxcXjcKirdlPytGlyk5W/tsZ/s aknTd40sf/XYS6n3he1yS4ePnNTfBPKOwksi8MKHsr+mt+bjIVPo1K0tCI0ofpn/xEEm HKYReNViFcqfuXRr7Mws8ZKUoVaBLQLp21zvgUNvCVaczME+tMlL3Kmgu9tCHXVfpJG7 KA2XzjzNjLwC8cuoJTSwQVXdb+wH2PKKJ+0Xv07RwGiBcGcfX84oHCMM/9CqLmM7QCsL pHsQ==
X-Gm-Message-State: ALKqPwfjNGHmKLYU4XxsTwqy+1c2G9kRscnAqykx52ZPHENbBDiGIcTs 7s7UFv2ECZE1rq449rBTadCp7aH8+2IjKhzgQ5c=
X-Google-Smtp-Source: ADUXVKLuUaIiWkjCqo5UN/SM4ox6eahq3N/bl+jiDtKBAIxHls87w0wzGswNz9nIaehjP3d96EFYsodF/FHjK70YLRY=
X-Received: by 2002:a9f:3d6b:: with SMTP id m43-v6mr1080767uai.129.1527246368527; Fri, 25 May 2018 04:06:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a1f:9744:0:0:0:0:0 with HTTP; Fri, 25 May 2018 04:06:08 -0700 (PDT)
In-Reply-To: <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> <D72C9473.307DE%christer.holmberg@ericsson.com>
From: Andy Hutton <andyhutton.ietf@gmail.com>
Date: Fri, 25 May 2018 12:06:08 +0100
Message-ID: <CAB7PXwQ1SFHTrUEL4JA7CpDbEb4=jK5RhQxB2F-sRgy0tqfUZQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "sipbrandy@ietf.org" <sipbrandy@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipbrandy/wULcKhILmdbl_bDkco6y46Qu33A>
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: Fri, 25 May 2018 11:06:11 -0000

On 24 May 2018 at 14:11, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> 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???
>

The rules or probably more accurately the recommendations for both
endpoints are exactly the same in that when creating an offer the
decision on whether to try OSRTP or not depends on their own
preferences. This is true for both the initial offer and any
subsequent offers.


> 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.
>

As above the rules/recommendations for both endpoints are the same and
are dependent on their own preferences. If the endpoint is willing to
try OSRTP then it should do so in the subsequent offer for maximum
chance of interoperability but if its requires SRTP then it would not
make an OSRTP 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?
>

Absolutely yes.


> Regards,
>
> Christer
>
>