IETF Logo Mail Archive

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

Nils Ohlmeier <nohlmeier@mozilla.com> Thu, 19 April 2018 16:22 UTC

Return-Path: <nohlmeier@mozilla.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 6060F12D86E for <rtcweb@ietfa.amsl.com>; Thu, 19 Apr 2018 09:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 DB27wfYT1clr for <rtcweb@ietfa.amsl.com>; Thu, 19 Apr 2018 09:22:41 -0700 (PDT)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::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 319F81200E5 for <rtcweb@ietf.org>; Thu, 19 Apr 2018 09:22:41 -0700 (PDT)
Received: by mail-pf0-x235.google.com with SMTP id z9so2878791pfe.6 for <rtcweb@ietf.org>; Thu, 19 Apr 2018 09:22:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=dZ1jhw3obYD2ak7UATdbsr5zN+MXT2cI/0xWwdr11wM=; b=FELiThm2GqEL3ahxARtBa0PLXXhz5GaHu12F/wxCJMuM2EUVxZrHSflIdbhsuHsu6B +dnHLRgdQNY4pQTPwVJhWQjgwF9QZ/Mg19w2NtyFW9mvLuGxYXuRIgeNPtsuT0hJZdH6 QGlP2MvkFKWwMarc7ylk3TSbKMX1bpDu9C/cM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=dZ1jhw3obYD2ak7UATdbsr5zN+MXT2cI/0xWwdr11wM=; b=SbGSSOJ9x70yGUQQ0lPPvojLOulGua+LwsH1c5vY1Tw3zj8Y1J1VdiBDM5iFG73Bbc Wx/XZI/Vv224ROTncZWC7dha7butl3dGyM6SI9xQtwTXpfMdwJVtk2wvFWGjcFxGx/Fy NGyhBL/tY6LEbEhcI1LuFHEqml1pt/Zvg3diLXKQXYmO5iBt8conj1Ip1wEWnLN52gsK F37WdI9cAWU/ODaEN5VRrRFFaUyw0NL0zFoVf1QP6FZ8eCQbEnKIChSkHnWy0VX18mlB OzJQ+XJkwHewuf4CmKH55oBd55xVdg/TdB4ZaRB2MCdwNlnu5ixloJk6KGSqv6a+WX6e JLFQ==
X-Gm-Message-State: ALQs6tBa+G3jdrBFBmRSrLCKdTepkvyL1MDUbYiivwr/WGJfPxrp5EKG AxM3XaOe82ytzHI/IVO7rL7Fu+OQ6dQ=
X-Google-Smtp-Source: AIpwx4/+c3bp+svIxIVNKKRJDvvaReDba3Nu4k9egR1g2xJtYY1r7+nKduiJrgl3BLj6+pGGrXBLPQ==
X-Received: by 10.98.62.87 with SMTP id l84mr6356945pfa.135.1524154960539; Thu, 19 Apr 2018 09:22:40 -0700 (PDT)
Received: from ?IPv6:2601:647:4600:3f31:3c31:4841:48d8:a161? ([2601:647:4600:3f31:3c31:4841:48d8:a161]) by smtp.gmail.com with ESMTPSA id b193sm5021618pga.7.2018.04.19.09.22.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Apr 2018 09:22:38 -0700 (PDT)
From: Nils Ohlmeier <nohlmeier@mozilla.com>
Message-Id: <C06A6EB6-5CD2-4F33-8495-4CC42FFF169B@mozilla.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_85AFA3A7-D18E-485D-A6D6-632EE842DCE2"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Thu, 19 Apr 2018 09:22:36 -0700
In-Reply-To: <CAOJ7v-3ycQH4Ho9OJsuYRR3M4GwsPGGkHzx=E0hKbFObSjRxkw@mail.gmail.com>
Cc: Sean Turner <sean@sn3rd.com>, RTCWeb IETF <rtcweb@ietf.org>
To: Justin Uberti <juberti=40google.com@dmarc.ietf.org>
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> <20180412144158.44733ac7@lminiero> <b767da79-7678-2a1c-ecb0-46a9a3bd9129@gmail.com> <CAOJ7v-2gmxpsGp=25pcJmnkYmipZdCFOqU4nLtAVSznLsZo9rQ@mail.gmail.com> <4902F7BF-0D20-4EA6-9E78-D22C90EFCE22@westhawk.co.uk> <CAOJ7v-3NsqD6pq-kkMw81+2n_D8qf558CKeCE76ZypyxwCgs9g@mail.gmail.com> <CAOJ7v-2NJ1vhVUerZ1cn8MP9hD_vgAYBurjeQKMx76Aa_U=n=Q@mail.gmail.com> <A8B32C11-30BD-4DA8-9BAB-FA26747BFF66@westhawk.co.uk> <CAOJ7v-0VNCjGdhtz56jwwksBcfPk=9wuxfMgwi8mq7ViFyWpuw@mail.gmail.com> <DDEE408B-B49E-465E-B17B-C2813AF4F2F4@westhawk.co.uk> <CAOJ7v-26f1hrujtegK6_U50E0MZPy5zmf0yDUWBY5oqrKQmGQg@mail.gmail.com> <CAOJ7v-2fn-SdR2VUbVVHbMB-_Rw9gV0nsRnc2Ace+682LBJBag@mail.gmail.com> <7E9CBD87-6C00-4CF8-AEDE-D2AEFC3213FA@westhawk.co.uk> <CAOJ7v-1sHcm46BCttHMNA4gjUTL98RwBRm-H1HGpF7Bwx2ceGA@mail.gmail.com> <03257894-7D79-463D-BC3A-5B388680A3E7@sn3rd.com> <CAOJ7v-3ycQH4Ho9OJsuYRR3M4GwsPGGkHzx=E0hKbFObSjRxkw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/QVRJBuz6aBAZh9OPGlgUJaLWi7g>
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, 19 Apr 2018 16:22:44 -0000

While I understand the arguments against adding more mode I still think the paragraph describing Mode 4 is missing details and causes confusion among implementers:

- It is not clear if the word “proxy” refers to a HTTP proxy or a TURN server.

This can easily be improved by replacing the word “proxy” with “HTTP proxy” everywhere in the Mode 4 paragraph.

- It is unclear how an implementation should behave in the absence of such a proxy.

I would suggest to add a sentence the implementation should not hand out any candidates in the absence of a HTTP proxy.

Best regards
  Nils Ohlmeier

> On Apr 18, 2018, at 14:08, Justin Uberti <juberti=40google.com@dmarc.ietf.org> wrote:
> 
> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-ip-handling/07/ <https://datatracker.ietf.org/doc/draft-ietf-rtcweb-ip-handling/07/>
> 
> On Wed, Apr 18, 2018 at 1:20 PM Sean Turner <sean@sn3rd.com <mailto:sean@sn3rd.com>> wrote:
> Yes please.  I think the IETF LC should be on the latest text.
> 
> Note I’ve already updated the Shepherd write-up as Stephen suggested.
> 
> spt
> 
> > On Apr 18, 2018, at 03:16, Justin Uberti <juberti=40google.com@dmarc.ietf.org <mailto:40google.com@dmarc.ietf.org>> wrote:
> >
> > OK, merged b) via https://github.com/juberti/draughts/pull/98 <https://github.com/juberti/draughts/pull/98>.
> >
> > Sean, should I produce a new version of the document?
> >
> > On Tue, Apr 17, 2018 at 5:40 AM westhawk <thp@westhawk.co..uk> wrote:
> >
> >
> >> On 16 Apr 2018, at 23:06, Justin Uberti <juberti=40google.com@dmarc.ietf.org <mailto:40google.com@dmarc.ietf.org>> wrote:
> >>
> >> Here's a specific and minimal proposal, which is a slight modification of Sean's proposal in https://github.com/juberti/draughts/pull/98/files <https://github.com/juberti/draughts/pull/98/files>:
> >>
> >> The details of this consent are left to the implementation; one potential mechanism is to tie this consent to getUserMedia consent. Alternatively implementations can provide a specific mechanism to obtain user consent where needed, e.g., when a VPN is in use.
> >>
> >> b) Sean's proposal (without the boldface)
> >
> > b)
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org <mailto:rtcweb@ietf.org>
> > https://www.ietf.org/mailman/listinfo/rtcweb <https://www.ietf.org/mailman/listinfo/rtcweb>
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org <mailto:rtcweb@ietf.org>
> > https://www.ietf.org/mailman/listinfo/rtcweb <https://www.ietf.org/mailman/listinfo/rtcweb>
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org <mailto:rtcweb@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtcweb <https://www.ietf.org/mailman/listinfo/rtcweb>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email