Re: [rtcweb] Suresh Krishnan's No Objection on draft-ietf-rtcweb-ip-handling-11: (with COMMENT)

Justin Uberti <juberti@google.com> Thu, 07 March 2019 23:42 UTC

Return-Path: <juberti@google.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 295BD130FB8 for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2019 15:42:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.479
X-Spam-Level:
X-Spam-Status: No, score=-16.479 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 LZ-Kn2472ReW for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2019 15:42:08 -0800 (PST)
Received: from mail-it1-x144.google.com (mail-it1-x144.google.com [IPv6:2607:f8b0:4864:20::144]) (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 8D76413103D for <rtcweb@ietf.org>; Thu, 7 Mar 2019 15:42:06 -0800 (PST)
Received: by mail-it1-x144.google.com with SMTP id f186so5062788ita.0 for <rtcweb@ietf.org>; Thu, 07 Mar 2019 15:42:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:cc; bh=San+6tJEXNbIkUrVCnzOmOq/W+y21gwWr+0A2I8xpDU=; b=LBRHNqYLxidIisQzDOzwGjDRUj8loXboFTlOIz3ROHAkgoFnKgcfPBVx8l51cqgAv0 ybquAZck5pChonE7JCjW4SUAaNgMSdcM+RzrihaEC1U0ElKUz8cxHpfM6+2w7bRLsB4m LUAZZ0T1O/JEaiqrx06zbovL+UeKX56hFx5q/yuoC4XwbldZWAIkBHXcxb3ujMC6cA8X LN2GEi9B77eMTcUZIKgi9DeQm4CSOV2L5XM07cV+LgT/ovTzAOiDQCPG257dO/Nu+3nK SQyAATfyQXZIDMQEl+CPWKr3wF2yq8w0mNZS/8yI9T6u5kMzG2aUa3O9goOG77ijaRxk DXsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:cc; bh=San+6tJEXNbIkUrVCnzOmOq/W+y21gwWr+0A2I8xpDU=; b=N0TEU12T6RiR2TEnk2EdVB4T6O8efWswzOvBemnM859s2Ru0nrPWfXffqsAszbtw3V /vkLYyZgCUHMhzpQaPmDJvaf929sX1gwN1TyXcvzVvtYiTIQlM4SCtb4gRTKEASVRqZ2 hAukpMBSclblEY9qHoXX0zJGuwi1tig0GZYz3vTwAD38xRgjSrkc9MxyLKH3L/VQ+eRp hgPsNqKKpFkt/HyhwisMhlvbgZN1iw1v1TRlMVJw+2p01Bj2lEjk+20i7SsoQxq6GywM u/H4+MccpY0QC2WMBl3ixq/sCsmadHsapwMQJAIfXLZ5rO4+c2YE4wMIJ6zyTolyZSji Rgmg==
X-Gm-Message-State: APjAAAV3p8wrRPVENo1W29jHd1b8LxLqtonSsRRnhrIYi72qZJ5XF74m UqgtpsXbPmp157eq6jbLRA88P/Ly+SrrlVJup9Sxvg==
X-Received: by 2002:a24:6588:: with SMTP id u130mt6582472itb.136.1552002125525; Thu, 07 Mar 2019 15:42:05 -0800 (PST)
MIME-Version: 1.0
References: <155193259226.13743.3839965952947451511.idtracker@ietfa.amsl.com>
In-Reply-To: <155193259226.13743.3839965952947451511.idtracker@ietfa.amsl.com>
From: Justin Uberti <juberti@google.com>
Date: Thu, 7 Mar 2019 15:41:53 -0800
Message-ID: <CAOJ7v-0C8jZQc3QKOAqwW8rBmj-6JPeuKsxrR8UpmLCb_r64EQ@mail.gmail.com>
Cc: The IESG <iesg@ietf.org>, RTCWeb IETF <rtcweb@ietf.org>, draft-ietf-rtcweb-ip-handling@ietf.org, rtcweb-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000629ff4058389a7af"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/l1L3fOmLb7KmdlqY0nitAIG-N-s>
Subject: Re: [rtcweb] Suresh Krishnan's No Objection on draft-ietf-rtcweb-ip-handling-11: (with COMMENT)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Mar 2019 23:42:09 -0000

On Thu, Mar 7, 2019 at 1:50 AM Datatracker on behalf of Suresh Krishnan <
noreply@ietf.org>; wrote:

> Suresh Krishnan 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:
> ----------------------------------------------------------------------
>
> * Section 3
>   Not sure how the use of temporary addresses in IPv6 [RFC4941] is
> relevant at
>   all to a discussion of NAT usage (#2). Can you please clarify?
>
>   "#2 is a less significant but valid concern.  While the [RFC4941] IPv6
>    addresses recommended by [I-D.ietf-rtcweb-transports] are fairly
>    benign due to their intentionally short lifetimes"
>

 The most obvious case is a NAT64 scenario, where the IPv6 address is never
seen by the outside world, and therefore exposing said address to the web
site presents a potential leakage concern. This concern is significantly
mitigated if the IPv6 address is a RFC4941 ephemeral address.