[rtcweb] Eric Rescorla's No Objection on draft-ietf-rtcweb-ip-handling-11: (with COMMENT)

Datatracker on behalf of Eric Rescorla <ietf-secretariat-reply@ietf.org> Wed, 06 March 2019 15:03 UTC

Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: rtcweb@ietf.org
Delivered-To: rtcweb@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF3E1277D7; Wed, 6 Mar 2019 07:03:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Datatracker on behalf of Eric Rescorla <ietf-secretariat-reply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: rtcweb@ietf.org, Sean Turner <sean@sn3rd.com>, draft-ietf-rtcweb-ip-handling@ietf.org, sean@sn3rd.com, rtcweb-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.93.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155188458557.5238.17233070387773707583.idtracker@ietfa.amsl.com>
Date: Wed, 06 Mar 2019 07:03:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/SV5FU2hiZsDxOEuQufKArKBvrsM>
Subject: [rtcweb] Eric Rescorla's No Objection on draft-ietf-rtcweb-ip-handling-11: (with COMMENT)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 06 Mar 2019 15:03:06 -0000

Eric Rescorla has entered the following ballot position for
draft-ietf-rtcweb-ip-handling-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-ip-handling/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Rich version of this review at:
https://mozphab-ietf.devsvcdev.mozaws.net/D3744



COMMENTS
S 3.
>   
>      1.  If the client is multihomed, additional public IP addresses for
>          the client can be learned.  In particular, if the client tries to
>          hide its physical location through a Virtual Private Network
>          (VPN), and the VPN and local OS support routing over multiple
>          interfaces (a "split-tunnel" VPN), WebRTC will discover not only

This might be simpler if you said "route traffic over" rather than
"support routing"

Also, do you want to say "may discover" because the guidelines below
would potentially stop that.


S 6.2.
>      addresses (0.0.0.0 for IPv4, :: for IPv6), which allows the OS to
>      route WebRTC traffic the same way as it would HTTP traffic.  STUN and
>      TURN will work as usual, and host candidates can still be determined
>      as mentioned below.
>   
>   6.2.  Determining Host Candidates

This is framed a little confusingly, because all host candidates are
suitable in mode 1. Perhaps add "In modes XXX..."