Re: [rtcweb] WGLC for draft-ietf-rtcweb-ip-handling

Sean Turner <sean@sn3rd.com> Thu, 12 April 2018 12:53 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2D112704A for <rtcweb@ietfa.amsl.com>; Thu, 12 Apr 2018 05:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 1Pz_ObqxD7It for <rtcweb@ietfa.amsl.com>; Thu, 12 Apr 2018 05:53:02 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (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 95901126579 for <rtcweb@ietf.org>; Thu, 12 Apr 2018 05:53:02 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id s78so5836955qkl.8 for <rtcweb@ietf.org>; Thu, 12 Apr 2018 05:53:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Fhfe7aRJfqCm/O6kYQGxnONVK90WlNPTffoz6ZeKk5g=; b=ktXo/jn9nULQiT2cJAUyBUYyWbcnUrB3FFa9EHpIagWTXnZrntIEeJPCKNgrgV3tz+ ZmeOcIYtKw32NNKGkBiYSkxQUqiGrFdFtmLKVtru02mhPEd/dJ3bOGaMfaXj0EuVdjqC vYwcXFleY1nPg1YRGWQFrLm4xYFQBHHQa4gsY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Fhfe7aRJfqCm/O6kYQGxnONVK90WlNPTffoz6ZeKk5g=; b=juRsy5T/e8tvywQyTGwK1BAEQO9Vb0/mnB2/v+LcercjXtZp2X2/ZAsGn9T8lUgpqc iEext4UwrhUrMD4pM+wel2K3XnS+ukQkeRYe52LNcDAUYx+18+BKFq/GacuvPGihTyXJ l8cih6TwFLz/ApIxfPeFVmOmLwhgRr/uQCUDmELI1L9Q+lG7zK4+sy0Dr8ySzZcb2Wlb 8UcGxuKZG9KLndh9exJnoanwU9vJ/UsTy6aw4I20QdybnjPolNJJm9VJs0RxZJQgY3Zq ET15G2CqE1ztSRwB67n9MhnN5BEEnT5AaEM/cgZblB9ybEfaBrEN5dZjMPoJ2EDOktta D7Nw==
X-Gm-Message-State: ALQs6tBDOEvcpEfUTQH2O0Z9ZxzRn9dskQ7Xr5ZljsupdHDznHioMdM8 +RDSJbOYNqwbu7wLNFSoM43asA==
X-Google-Smtp-Source: AIpwx49vjdzrAEHXOkQKA9/OMws+JIuhtLm1N9UTHfGil42YXf8StLEe8mqwq/SQyllCsKdBZ8iO7w==
X-Received: by 10.55.214.7 with SMTP id t7mr943008qki.341.1523537581610; Thu, 12 Apr 2018 05:53:01 -0700 (PDT)
Received: from [172.16.0.18] ([96.231.225.106]) by smtp.gmail.com with ESMTPSA id a20sm2723790qkb.17.2018.04.12.05.53.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Apr 2018 05:53:00 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <e5e2a517-d29a-117c-ab79-6f01fa62b843@gmail.com>
Date: Thu, 12 Apr 2018 08:52:59 -0400
Cc: rtcweb@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F3FF735-83FE-4B07-BBC7-02311D6DFB81@sn3rd.com>
References: <1D5B431C-801E-4F8C-8026-6BCBB72FF478@sn3rd.com> <63282b84-4493-3fcb-a95f-4afe17d96bb6@cs.tcd.ie> <CAOJ7v-1gTq+EEjb+-q-T-pABBW--rpNGegoj_d2_7f7AKGksCA@mail.gmail.com> <403713b4-31d4-9085-d639-d3f60935ed5a@cs.tcd.ie> <CAOJ7v-0ED-FK=JmSxBJYfM=PCdgY6kmbiq6aFLcP7OXugG07EA@mail.gmail.com> <e6938f7d-542d-736b-0a3d-9269d7dd06e5@cs.tcd.ie> <CAOW+2dv1ORz2tEkgDTvdM1DtgyOdgXqKU30T4QhLAp1NT+rirg@mail.gmail.com> <CAOJ7v-0tCcg3FdzyfSJ6Y3JaH-TivFf-Sey6+tD8BANJKsjqtQ@mail.gmail.com> <1fceb3c4-35f3-34f7-de1d-79d5805e6d22@gmail.com> <9517D601-D3E8-46E1-94E5-7EC29FD6319B@sn3rd.com> <b5d323ac-2205-2aee-05c9-f270e80215f5@gmail.com> <CAOJ7v-0+hr-NddbLCwgjkfyEFEzoLYW8BcE5OYZ+HUiqDRnarg@mail.gmail.com> <0dee004d-159a-a9be-a0b8-ecbfd4204d72@gmail.com> <06252a76-f12e-4d8d-4a07-5240a7605bce@gmail.com> <914e0220-e3cc-00d7-0925-e5deb8b07e75@nostrum.com> <AFDFD3F3-4798-4716-B26C-A67457BF2C65@sn3rd.com> <e5e2a517-d29a-117c-ab79-6f01fa62b843@gmail.com>
To: Lennart Grahl <lennart.grahl@gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/C02rU048Y-fblMKLeN5L8CVog7M>
Subject: Re: [rtcweb] WGLC for draft-ietf-rtcweb-ip-handling
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 12 Apr 2018 12:53:05 -0000


> On Apr 12, 2018, at 08:22, Lennart Grahl <lennart.grahl@gmail.com> wrote:
> 
> On 12.04.2018 00:31, Sean Turner wrote:
>>> On Apr 11, 2018, at 16:10, Adam Roach <adam@nostrum.com> wrote:
>>> 
>>> [as an individual]
>>> 
>>> On 4/11/18 1:15 PM, Lennart Grahl wrote:
>>>> Since I haven't seen a satisfactory response so far, let me rephrase
>>>> this as a question: Can anyone explain to me why that approach is not
>>>> considered a valid alternative to getUserMedia?
>>> 
>>> 
>>> I think you're not getting a lot of response here because what you're proposing is well within the bounds of what the current document says. gUM is offered as a non-normative example, but that's all it is. If you believe that document changes are in order, perhaps a concrete proposal along the lines of "change the text <x> to be <y> instead" or "add text <z> at the end of section <q>" would produce more conversation.
> 
> Thanks, this and the response from Bernard is good feedback that I
> should provide a more concrete proposal next time.
> 
>> As the draft’s Shepherd trying to figure out how to bring closure on this issue, I like to offer a summary:
>> 
>> There’s some discomfort with the use of the term “user consent” as well as the non-normative example provided for how to get it. The problem with changing the term to something else is "user consent" is a term of art; we can’t really qualify it with something like “informed”, because we’d need to explain what that means (and well GDPR …), and; frankly the term is used extensively in the other security draft that we pruned ip-handling from.  The problem with changing the non-normative example is that there don’t seem to be other attractive/realistic alternatives.
>> 
>> What I’d like to do is remind everybody that we pruned this draft from the other security drafts to allow it to be updated faster because it’s about a much narrower subject.  With this in mind and Bernard’s long list of questions, I would like to propose that we:*
>> 
>> 1) Add another sentence (from Tim) that indicates there are other alternatives:
>> 
>>      Alternatively implementations can provide a separate
>>      mechanism to obtain user consent.
>> 
>> 2) Progress the draft out of the WG.*
>> 
>> 3) Update/Obsolete this draft, when a much superior alternative emerges.
>> 
>> spt
>> 
>> * Also "hold your nose" if you’re sad about this proposal but are willing to begrudgingly live with the rough consensus; it’s rough and we noted this in the Shepherd write-up.
>> 
>> ** Remember that during the IETF LC we (or somebody in the wider IETF community) might come up with something during the IETF LC.
> 
> I realise I've joined a tad late and it should be clear by now that I
> have a strong reluctance when it comes to using getUserMedia for the
> purpose of getting consent to use mode 1. But you are correct, it is
> non-normative and I'm more irritated by the implementations that don't
> provide an alternative than this document. Still, I would appreciate if
> the sentence from Tim you mentioned in 1) will be added.

I already submitted a PR :)
https://github.com/juberti/draughts/pull/98

> Regarding 3): Like Bernard, I'm unsure how to determine a "superior
> alternative" (especially in the context of a non-normative section).
> 
> Cheers
> Lennart
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb