Re: [dhcwg] 3315bis use of "requesting router" term

Lorenzo Colitti <lorenzo@google.com> Thu, 24 November 2016 08:39 UTC

Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A08181299E6 for <dhcwg@ietfa.amsl.com>; Thu, 24 Nov 2016 00:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 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_LOW=-0.7, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham 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 k7UC5_qVOieJ for <dhcwg@ietfa.amsl.com>; Thu, 24 Nov 2016 00:39:20 -0800 (PST)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 0DDF5129654 for <dhcwg@ietf.org>; Thu, 24 Nov 2016 00:39:20 -0800 (PST)
Received: by mail-io0-x232.google.com with SMTP id x94so68088255ioi.3 for <dhcwg@ietf.org>; Thu, 24 Nov 2016 00:39:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=g/F2OK81B4fY2ETUVqQv3r5i+pZ75wO5mKZlfysWQwg=; b=m/OVqbQ8S2lAWRo5mQppMSpyu4W5Pf0M7fJQLj7IuNdcw4GTt8o6t/VVZGGcbKYshV EmWcsGmiPBYKzctESmcN6GEb4mnMyZw+yF1Jm3ImKTpnY11TsPnq1iM3I3fPfVujM9CZ FR7NQ87uJV1j+lDTXnsrt4n+OMHX5RWD5wHdvGkEaSmf8Oo8wyk3w8u/gb4VNjipOdew 46jdXjEFjPrptXXJiHAs6x3l9kBPDNV9G/5IlseldcYKCXyLzLxM48/XIDjxuLJd/Ml/ f6vctb1eP88jHBvNcKsmEoGhTpwVnUd70PDWgxYtLGelpDhsFeqXRX3O9JQtCy+8taxB 55bQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=g/F2OK81B4fY2ETUVqQv3r5i+pZ75wO5mKZlfysWQwg=; b=FmaWL6R4n6iqqDIdiYnlaty1BBqjknrczwOMuDrS0/7MklEAIIjSa8i03Zrd2n6crx cMWtFI0JOHqq/tTldTQf5n41RxfUuSkFPhR/YZl1Jb0dmDTEFvO2u31plemrtkb0e+kP bDImb260k9XH3/QyCBoTnikn3s7HtLZrs9xtLzKtl6rRKtj9IJY47rqdW9im8cQujgu3 89BUN1U6s2vxaI2toI1ba5cFHGf4RZISee0w8Aunb+f72cvgZ9TSyRYjScSf+hN7+s1m TswJlmE43H0KsZsLLrq1V1ik3wQUt+Bv2VvqX+h50yheVfdjwP+u+GUjFAP8sBxgyf48 pDfA==
X-Gm-Message-State: AKaTC001T7CLQbRbhPG3hnqqGCgxV5WEnXkwFaUPlQcO3mJ8KxLav5ZZA3fPlARMPnJJiv8mBBpWW+dZ4mmgcX0q
X-Received: by 10.107.136.164 with SMTP id s36mr1009691ioi.214.1479976759059; Thu, 24 Nov 2016 00:39:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.18.160 with HTTP; Thu, 24 Nov 2016 00:38:58 -0800 (PST)
In-Reply-To: <C1EA7398-C196-46F9-8339-4EA794A19298@cisco.com>
References: <CAKD1Yr0ZtfKOe9Ut7hGpr_f=ahOSEEB8VAxmUk+rRu5uPoC4+w@mail.gmail.com> <C1EA7398-C196-46F9-8339-4EA794A19298@cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 24 Nov 2016 00:38:58 -0800
Message-ID: <CAKD1Yr1ULpp-UHj8bx-0w2kwD32hOka5og=pQ_Dn=Qevbz1jTg@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary="001a113eb2c2008cec054207f1fa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/Q_6lQ7i2lSgrqVu8jk-zolOQx9U>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] 3315bis use of "requesting router" term
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2016 08:39:21 -0000

I did look at -06. My browser says there are 26 occurrences of "requesting
router" in the draft, and most of section 6.3
<https://tools.ietf.org/html/draft-ietf-dhc-rfc3315bis-06#section-6.3>
("DHCP for Prefix Delegation") talks about "requesting router" instead of
client.

Now that I look again, I do now see this new text added to the end of
section 6.3 which is similar to the wording in RFC 7934:

   While [RFC3633] assumed that the DHCPv6 client is a router (hence use
   of "requesting router") and that the DHCPv6 server was a router
   (hence use of "delegating router"), DHCPv6 prefix delegation itself
   does not require that the client forward IPv6 packets not addressed
   to itself, and thus does not require that the client (or server) be
   an IPv6 router as defined in [RFC2460].  Also, in many cases (such as
   tethering or hosting virtual machines), hosts are already forwarding
   IPv6 packets and thus operating as IPv6 routers as defined in
   [RFC2460].  Therefore, this document mostly replaces "requesting
   router" with client and "delegating router" with server.

I suppose this will work, but it's not great. It does seem that the
document would be better served if 6.3 were reworded to say "client" in
some of the places where it now says "requesting router".

On Wed, Nov 23, 2016 at 7:47 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

> See the 06 version. This ticket has been dealth with we believe.
>
> - Bernie (from iPad)
>
> On Nov 23, 2016, at 9:02 PM, Lorenzo Colitti <lorenzo@google.com> wrote:
>
> On Mon, Oct 31, 2016 at 12:50 PM, Bernie Volz (volz) <volz@cisco.com>
> wrote:
>
>> This version does NOT yet have ALL of the WGLC comments received over the
>> summer addressed - there were almost 300 of the them and we are probably
>> close to 3/4 done. (We also have a few issues in the issues tracker let to
>> resolve - see https://trac.tools.ietf.org/group/dhcpv6bis/report/1.)
>
>
> Hi,
>
> (Apologies if this was mentioned in Seoul - I couldn't make it due to a
> conflict.)
>
> I looked at the open issues discussion slides
> <https://www.ietf.org/proceedings/97/slides/slides-97-dhc-dhcpv6bis-open-issues-discussion-01.pdf>
> and I saw it wasn't mentioned, so I thought I'd ask: what's the status of ticket
> #167 <https://wiki.tools.ietf.org/group/dhcpv6bis/ticket/167> to change
> the term "requesting router" to "client"? Is this one of the issues the
> authors were planning to resolve?
>
> Since the ticket was opened, RFC 7934 was published as BCP and one of the
> options it recommends is to use DHCPv6 PD to assign prefixes to hosts, so I
> think this should be resolved before publication.
>
> Cheers,
> Lorenzo
>
>