
From nobody Wed Oct  1 03:47:52 2014
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C97281A0315 for <dhcwg@ietfa.amsl.com>; Wed,  1 Oct 2014 03:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 q7IOi0BGHqOa for <dhcwg@ietfa.amsl.com>; Wed,  1 Oct 2014 03:47:49 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 745D11A0312 for <dhcwg@ietf.org>; Wed,  1 Oct 2014 03:47:49 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id n3so131045wiv.3 for <dhcwg@ietf.org>; Wed, 01 Oct 2014 03:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=QUEhLu5kZPSxCzkdwG3ocPadSPT8xX+wQTzBaTZSyH0=; b=ixgjGSGITOL6pe8cVboRl92xHpXZj/NVSDqRNgbrHuibu9bfjaFDucao/miyUB4qW+ MxtnsQ6UMtnulF/pjlLm2HwQhD+QpNQJR3nSKoUoBVzijwVZdkdAtJrsYYO+cCBgdcsB KsZX5KdleAge/RTfffHMUWNmr+ySyEAHo/9amq1kAJlh58WSZ9M5JMhdusXcfG1lYg8u A1CCFfcnK0A2J9Jv6FLqjXyuzqlzJoZq9TfjRbmVaCUpX+SdIbCDL0t6m1Qcw8hwZDYO sg9gGmmSiKBzMTXDBQmGOvIjk0sxp0AiCo7+RsFIc9wfaIfnLmqjnRCKDWEj5tZa7Irl Kg5Q==
X-Received: by 10.180.91.164 with SMTP id cf4mr13022583wib.3.1412160468081; Wed, 01 Oct 2014 03:47:48 -0700 (PDT)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id mc4sm1435346wic.6.2014.10.01.03.47.44 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Oct 2014 03:47:47 -0700 (PDT)
Message-ID: <542BDBC9.80905@gmail.com>
Date: Wed, 01 Oct 2014 12:47:37 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1B6907C0@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6907C0@xmb-rcd-x04.cisco.com>
X-TagToolbar-Keys: D20141001124737306
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/OyPVpT073iRnlMC-J4J7z-MhA2k
Subject: Re: [dhcwg] WG Adoption Call - draft-gont-dhc-stable-privacy-addresses-01 - Adopted
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 01 Oct 2014 10:47:50 -0000

On 15.09.2014 15:06, Bernie Volz (volz) wrote:
> Please state whether or not you are in favor of the adoption by
> replying to this mail. If you are not in favor, please also state
> your objections in your response. This adoption call will complete on
> September 29, 2014.
Bernie and I, as DHC WG chairs, reviewed received responses to this
adoption call and we declare that it passed. Several technical comments
were received, but they can be addressed in WG part of this document's
lifecycle. Nobody explicitly objected this work and many supported it,
hence our decision.

Authors, please re-upload this draft as
draft-ietf-dhc-stable-privacy-addresses-00.

Bernie & Tomek


From nobody Wed Oct  1 06:20:48 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 037FE1A03F9; Wed,  1 Oct 2014 06:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 rwQN34IzK0SN; Wed,  1 Oct 2014 06:20:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9407A1A03E1; Wed,  1 Oct 2014 06:20:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141001132044.1025.3195.idtracker@ietfa.amsl.com>
Date: Wed, 01 Oct 2014 06:20:44 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/dP1NYv4OCCgfVEpkptk9IrzWbmg
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-stable-privacy-addresses-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 01 Oct 2014 13:20:46 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : A Method for Generating Semantically Opaque Interface Identifiers with Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
        Authors         : Fernando Gont
                          Will(Shucheng) Liu
	Filename        : draft-ietf-dhc-stable-privacy-addresses-00.txt
	Pages           : 8
	Date            : 2014-10-01

Abstract:
   This document specifies a method for selecting IPv6 Interface
   Identifiers, to be employed by Dynamic Host Configuration Protocol
   for IPv6 (DHCPv6) servers when leasing non-temporary IPv6 addresses
   to DHCPv6 clients.  This method is a DHCPv6 server side algorithm,
   that does not require any updates to the existing DHCPv6
   specifications.  The aforementioned method results in stable
   addresses within each subnet, even in the presence of multiple DHCPv6
   servers or even DHCPv6 server reinstallments.  It is a DHCPv6-variant
   of the method specified in RFC 7217 for IPv6 Stateless Address
   Autoconfiguration.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-stable-privacy-addresses/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-stable-privacy-addresses-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Oct  2 01:39:31 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C38141A01D8; Thu,  2 Oct 2014 01:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 aT6ZqIamLNUu; Thu,  2 Oct 2014 01:39:28 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 03C301A002D; Thu,  2 Oct 2014 01:39:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141002083928.1448.63545.idtracker@ietfa.amsl.com>
Date: Thu, 02 Oct 2014 01:39:28 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/-QArB7UPvST-Ksx2sgWpm_LAjyY
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-stateful-issues-07.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 08:39:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Issues and Recommendations with Multiple Stateful DHCPv6 Options
        Authors         : Ole Troan
                          Bernie Volz
                          Marcin Siodelski
	Filename        : draft-ietf-dhc-dhcpv6-stateful-issues-07.txt
	Pages           : 21
	Date            : 2014-10-02

Abstract:
   Dynamic Host Configuration Protocol for IPv6 (DHCPv6) was not written
   with the expectation that additional stateful DHCPv6 options would be
   developed.  IPv6 Prefix Options for Dynamic Host Configuration
   Protocol (DHCP) version 6 shoe-horned the new options for Prefix
   Delegation into DHCPv6.  Implementation experience of the CPE model
   described in RFC 7084 has shown multiple issues with the DHCPv6
   protocol in supporting multiple stateful options.  This document
   updates RFC 3315 and RFC 3633.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv6-stateful-issues-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Oct  2 02:11:07 2014
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1EC1A023E for <dhcwg@ietfa.amsl.com>; Thu,  2 Oct 2014 02:11:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 FNPIWzaLcfYi for <dhcwg@ietfa.amsl.com>; Thu,  2 Oct 2014 02:10:51 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4B5E1A002D for <dhcwg@ietf.org>; Thu,  2 Oct 2014 02:10:51 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id cc10so3315058wib.5 for <dhcwg@ietf.org>; Thu, 02 Oct 2014 02:10:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=G/4Gfy7hle7RfyR93+PtRDS74EI/697MukUYmG06rKE=; b=HvL4+QtVbIZD6K/Rcha6Wsjhs+YFeUSGClwWZEyTzWBGPYKzJrePYFdvSP+FX6NmsV F7tPaEGD4BGQQXKFJloO/cpj72LYoa0PvTsERS6stpbduNw7Nb/+wqvUGFXpb+dZZQBz M1uEz0dJE/IdLFODHTzHC6zCiz5fGC1DBExA4tZE2g3weYoJmRukySy2QEAFqNKwL3m5 Lni8uNYTjekJGApId9rOTbjYBY9octpqqzyomA807jL5Sj1XM2RLCpDTRe1KveHrKd4A 1ER2j6Mgc5ENvA6yE0ShYaaQVytYmfo8lpwUPkjnje9OTnlLsVRvHBIvYKsQ6na5H/DA afbA==
X-Received: by 10.180.100.101 with SMTP id ex5mr2277803wib.79.1412241050323; Thu, 02 Oct 2014 02:10:50 -0700 (PDT)
Received: from [192.168.0.100] (89-74-55-64.dynamic.chello.pl. [89.74.55.64]) by mx.google.com with ESMTPSA id t1sm546163wiy.8.2014.10.02.02.10.49 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Oct 2014 02:10:49 -0700 (PDT)
Message-ID: <542D1698.7030203@gmail.com>
Date: Thu, 02 Oct 2014 11:10:48 +0200
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/LoGfb0UnCL9JzjTiFYXTdWZ4o-A
Subject: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 02 Oct 2014 09:11:02 -0000

Hi All,

The version -07 of the draft-ietf-dhc-dhcpv6-stateful-issues is now
available at:

http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/

This version introduces numerous changes to the draft to address "New
issues" presented on IETF in Toronto:
http://www.ietf.org/proceedings/90/slides/slides-90-dhc-2.pdf. It also
addresses some issues raised on the mailing list. Thanks to Jinmei, Cong
and others for their interest and reviews.

In the new version we try to clarify the scope of this work - the
"Introduction" has been extended to state that the goal of this work is
to address the issues related to coexistence of IA_NA and IA_PD and we
get away from attempts to provide a generalized text for all existing IA
types (including IA_TA) and future IAs, as it is impossible to know how
they will look like.

The previous version of the draft provided a "unified" text (for
Renew/Rebind processing) which was intended to be used for the
RFC3315bis work. The new version removes the "unified" text to avoid
confusion that the draft is intended to provide generalized approach for
all IA types. Instead, the new text provides respective updates to
RFC3315 and RFC3633 for IA_NA and IA_PD processing in a single DHCP session.

The more detailed list of changes between version -06 and -07 is given
below.

1. The draft title has been changed from "Issues with multiple stateful
DHCPv6 options" to "Issues and Recommendations with Multiple DHCPv6
Stateful Options", as in fact the draft not only identifies the issues
but also proposes specific solutions.

2. The Introduction has been extended to clarify the scope of the draft
as mentioned above.

3. Use "stateful options" and "resources" where appropriate.

4. Provided the updates to relevant sections of RFC3315 to mandate that
the server MUST set the T1/T2 times to the same values across all IA
options sent to a client.

5. Removed the "unified" text (intended for RFC3315bis) from the
Renew/Rebind sections. The current text only provides respective updates
for RFC3315 and RFC3633.

6. With updated Renew/Rebind processing the server returns NoAddrsAvail
status code for the IA, when the server is configured to create new
bindings for the renewing clients but the binding cannot be created
(e.g. address pool exhausted or other reasons). If the server is not
configured (or updated) to create new bindings in the Renew/Rebind time,
the NoBinding is returned which falls back to the original behavior.

7. Reworked section 18.1.8. Receipt of Reply Message in RFC3315, mainly
to account for the NoAddrsAvail/NoPrefixAvail being returned by the
server in response to Renew/Rebind.

8. Updated 18.1.8 with a note that the client must use the shortest
T1/T2 time from the same IA across all IA options to facilitate the
renewal of all bindings at the same time.

9. Updated 18.1.8. with a note that client should follow the
retransmission procedure if it finds that the IA is not in the Reply
message from the server sent in response to Renew/Rebind. The original
text stated that the client should send Renew/Rebind if the IA is not
present in the server's response. This resulted in the Renew/Rebind storm.

9. Client SHOULD (relaxed from a MUST) initiate Confirm when it may have
moved to a new link as the client may have determined whether it moved
or not by other means. A reference to RFC6059 has been added.

Please provide your comments. Note that this work builds the ground for
the RFC3315bis, so your interest is important.

Marcin


From nobody Fri Oct  3 14:21:16 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A59B11A871C for <dhcwg@ietfa.amsl.com>; Fri,  3 Oct 2014 14:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.286
X-Spam-Level: 
X-Spam-Status: No, score=-15.286 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 W_nGQm377hOs for <dhcwg@ietfa.amsl.com>; Fri,  3 Oct 2014 14:21:13 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEBCA1A710D for <dhcwg@ietf.org>; Fri,  3 Oct 2014 14:21:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10442; q=dns/txt; s=iport; t=1412371273; x=1413580873; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=DJiHpcKRwcD0XC58+ebb61Gfjnua4elSDUdFvURHTB0=; b=dRGP3F7M3KT6ttOSLUfbTlsOAa8/M/nks5aVa99Iug98ogQOHCr/wnLD PSVPX1Kv4CJ7r+Wd8iAz/7ruPtyT5kXBdC2svkcfL2OxEM3RLXKjliAc5 bUkSCkqLNN/7hEab7RAi6/oINRlGzzI3YIZzQ1rOfqEoII1NX1sGbuElo s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAIAEoSL1StJV2a/2dsb2JhbABggkhGU1gEywqHTQKBDhYBcgmEAwEBAQQtXAIBCBEEAQELHQcyFAkIAQEEEwgBiDUNvxwBF499NwGDLYEeBZF0jHeDQpERg2NsAYFHgQIBAQE
X-IronPort-AV: E=Sophos; i="5.04,650,1406592000"; d="scan'208,217"; a="83899966"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-8.cisco.com with ESMTP; 03 Oct 2014 21:21:12 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s93LLC4m029949 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Fri, 3 Oct 2014 21:21:12 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0195.001; Fri, 3 Oct 2014 16:21:12 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: IETF-91 (Honolulu) DHC WG Agenda Items
Thread-Index: Ac/HkCLoS86rZHidSOuuk32ztFklWAXv6fbg
Date: Fri, 3 Oct 2014 21:21:11 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6B5E81@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B67C40C@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B67C40C@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.240.170]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6B5E81xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/MdwJGQWtvC7Fov8bBu8cGCi5bgg
Subject: Re: [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 03 Oct 2014 21:21:15 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6B5E81xmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi:

Just a reminder to send us (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@too=
ls.ietf.org>) agenda items. Thanks!!


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, September 03, 2014 12:01 PM
To: dhcwg@ietf.org
Subject: [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items

Hi:

While it is still 2 months away, we are starting to collect agenda items fo=
r IETF-91's DHC WG session.

Please send us (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org>=
) requests for sessions and include:

Name of session:
Name of draft(s):
Time requested:
Presenter name(s):
Brief description of what issues need discussing and what you hope to accom=
plish by presenting:

More details about the Honolulu IETF can be found at http://www.ietf.org/me=
eting/91/index.html.


-          Tomek & Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1B6B5E81xmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1294478240;
	mso-list-type:hybrid;
	mso-list-template-ids:1476817810 264280828 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:2;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1400636131;
	mso-list-type:hybrid;
	mso-list-template-ids:-883011554 1226195246 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:64;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Just a reminder to sen=
d us (<a href=3D"mailto:dhc-chairs@tools.ietf.org">dhc-chairs@tools.ietf.or=
g</a>) agenda items. Thanks!!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Wednesday, September 03, 2014 12:01 PM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items<o:p></o:p></=
span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While it is still 2 months away, we are starting to =
collect agenda items for IETF-91&#8217;s DHC WG session.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please send us (<a href=3D"mailto:dhc-chairs@tools.i=
etf.org">dhc-chairs@tools.ietf.org</a>) requests for sessions and include:<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Name of session:<o:p></o:p></p>
<p class=3D"MsoNormal">Name of draft(s):<o:p></o:p></p>
<p class=3D"MsoNormal">Time requested:<o:p></o:p></p>
<p class=3D"MsoNormal">Presenter name(s):<o:p></o:p></p>
<p class=3D"MsoNormal">Brief description of what issues need discussing and=
 what you hope to accomplish by presenting:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">More details about the Honolulu IETF can be found at=
 <a href=3D"http://www.ietf.org/meeting/91/index.html">
http://www.ietf.org/meeting/91/index.html</a>.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Tomek &amp; Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6B5E81xmbrcdx04ciscoc_--


From nobody Mon Oct  6 20:07:23 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95E0B1A02F9 for <dhcwg@ietfa.amsl.com>; Mon,  6 Oct 2014 20:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.286
X-Spam-Level: 
X-Spam-Status: No, score=-15.286 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ReaKfwevCQEg for <dhcwg@ietfa.amsl.com>; Mon,  6 Oct 2014 20:07:18 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5694B1A0317 for <dhcwg@ietf.org>; Mon,  6 Oct 2014 20:07:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4757; q=dns/txt; s=iport; t=1412651235; x=1413860835; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=DqhSfcuD3VLi/sze98qcBEkyYHu2pbC+7UCiTv1NgzE=; b=ebrtzXqCldt53EBkq0ey5adN54LFXCe2ZoANtfAOFxHn1yyNMlOyV1pw gkfcYLAsXXVcSi9WnekCwV9MqR98YW/Jxg4WEhluH6z6ieb5B7wT2x9tr dfVckWCMBp6CHGMkVTjsHXwJupNHkDTlbzr3WFIDyBxPLOGYfp+viBX92 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlAGALRXM1StJV2Q/2dsb2JhbABfgkhGU1jKS4Fth00CgQ0WAXIJhAQBAQQtXAIBCDUKBzIUEQEBBBOIPg3BCQEXjQeDRYMtgR4FkXSEPIcOgS07gweHW4U3g3+BeoFpbIJKAQEB
X-IronPort-AV: E=Sophos; i="5.04,666,1406592000"; d="scan'208,217"; a="84590063"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-8.cisco.com with ESMTP; 07 Oct 2014 03:07:14 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s9737Chm015846 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 7 Oct 2014 03:07:12 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0195.001; Mon, 6 Oct 2014 22:07:12 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
Thread-Index: Ac/b8Z7zlxbYWZvpTHOHfWS5Qb+urQF6iqrU
Date: Tue, 7 Oct 2014 03:07:11 +0000
Message-ID: <492C612A-D2F6-43D3-A33A-364AFB5BC7D9@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6ABDD8@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6ABDD8@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_492C612AD2F643D3A33A364AFB5BC7D9ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/E4u0VEBMvFjj76sTkEBXS_PvndE
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 07 Oct 2014 03:07:21 -0000

--_000_492C612AD2F643D3A33A364AFB5BC7D9ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Reminder that this WGLC is in progress and needs responses to advance. Plea=
se review and provide your support or reasons as to why you feel this is no=
t ready yet or should never advance.

- Bernie (from iPad)

On Sep 29, 2014, at 10:36 AM, Bernie Volz (volz) <volz@cisco.com<mailto:vol=
z@cisco.com>> wrote:


Hi all,



This message starts the DHC working group last call to advance "Customizing=
 DHCP Configuration on the Basis of Network Topology=94, draft-ietf-dhc-top=
o-conf-03, document as an Informational RFC. The authors believe that this =
version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-topo-conf-03



Please send your comments by October 13th, 2014. If you do not feel this do=
cument should advance, please state your reasons why.



There are no IPR claims reported at this time.



Bernie Volz is the assigned shepherd for this document.



- Tomek & Bernie


--_000_492C612AD2F643D3A33A364AFB5BC7D9ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>Reminder that this WGLC is in progress and needs responses to advance.=
 Please review and provide your support or reasons as to why you feel this =
is not ready yet or should never advance.<br>
<br>
- Bernie (from iPad)</div>
<div><br>
On Sep 29, 2014, at 10:36 AM, Bernie Volz (volz) &lt;<a href=3D"mailto:volz=
@cisco.com">volz@cisco.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hi all,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This message starts the DHC working group last ca=
ll to advance &quot;Customizing DHCP Configuration on the Basis of Network =
Topology=94, draft-ietf-dhc-topo-conf-03, document as an Informational RFC.=
 The authors believe that this version is
 ready.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The draft is available here:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"http://tools.ietf.org/html/draft-ietf-=
dhc-topo-conf-03">http://tools.ietf.org/html/draft-ietf-dhc-topo-conf-03</a=
><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please send your comments by October 13th, 2014. =
If you do not feel this document should advance, please state your reasons =
why.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There are no IPR claims reported at this time.<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bernie Volz is the assigned shepherd for this doc=
ument.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</blockquote>
</body>
</html>

--_000_492C612AD2F643D3A33A364AFB5BC7D9ciscocom_--


From nobody Tue Oct  7 07:41:32 2014
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 254971ACDDF for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 07:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 aJPvK7hrZydy for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 07:41:25 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56DD31ACDD8 for <dhcwg@ietf.org>; Tue,  7 Oct 2014 07:41:23 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id k14so8236475wgh.7 for <dhcwg@ietf.org>; Tue, 07 Oct 2014 07:41:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=lEJwHA5S2p/0Z02133O0YuDB+VHf58P4gEHamE7V+eg=; b=KvsY/7OBWUTv8WWaaipWzi5FmQTWrVRLWSA2FNrzIkQZuvCSA7ZO9vYac5n5CSxIYL 7yvKq2gEW1bXdhgcUxbXbJkDb4+wDx+zZ84dHDDoC0wUuT3kcpzYTv5s3kZyBSJ4ywKb wDOZHQDKzUnNCKHWGyfQLWH/c+yiZXbocgfQ1rhIP5rhMb67BpsZWlC323G01aRGUy2i CpAodjgp+XcZSgL6Zi4QZ2GCfdE4YkNhNS5i2eTna27z0Stvc4+zOAQ9lX1n6wjy0SB0 zkuJVukuYVIPk2hoiHG9Ls9XN3W8rb6Z4H+OWSOnwTbKL0nmRKxBU8REoHZB0mxKT378 02Wg==
X-Received: by 10.194.157.10 with SMTP id wi10mr5517512wjb.66.1412692881824; Tue, 07 Oct 2014 07:41:21 -0700 (PDT)
Received: from [192.168.43.206] (37.30.102.132.nat.umts.dynamic.t-mobile.pl. [37.30.102.132]) by mx.google.com with ESMTPSA id li17sm14979986wic.13.2014.10.07.07.41.19 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 07:41:20 -0700 (PDT)
Message-ID: <5433FB8C.4010003@gmail.com>
Date: Tue, 07 Oct 2014 16:41:16 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "<dhc-chairs@tools.ietf.org>" <dhc-chairs@tools.ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1B67C40C@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B67C40C@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/ZjMwKajSaWj2qpPIyUxOV1Qxiag
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 07 Oct 2014 14:41:30 -0000

On 03/09/14 18:00, Bernie Volz (volz) wrote:
> While it is still 2 months away, we are starting to collect agenda items
> for IETF-91’s DHC WG session.
> 
> Please send us (dhc-chairs@tools.ietf.org
> <mailto:dhc-chairs@tools.ietf.org>) requests for sessions and include:
I'd like to request 2 slots:

Name: DHCPv6Bis update
I-D: draft-dhcwg-dhc-rfc3315bis-02
Time: 15 mins
Presented: TBD
Goal: Briefly present more important resolved issues, discuss
outstanding open issues, ask for adoption

Name: DHCP privacy considerations
I-D: draft-krishnan-dhc-privacy-00 (unpublished yet)
Time: 20 mins
Goal: Present summary of the privacy problems, discuss other aspects,
decide on roadmap (this is strictly problem analysis so far, need to
start taking about steps into mitigation/solution space)

The second presentation will cover krishnan-dhc-privacy, which may be
renamed to better express that it's about v6 only and possibly
complementary I-D about v4, if we manage to write it in time. Privacy
considerations seems to be a hot topic, so realistically speaking 20
minutes may be a bit short.

Tomek


From nobody Tue Oct  7 07:46:35 2014
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48BAA1ACDB3 for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 07:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 IsZc1kK28HMW for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 07:46:31 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E9671A1BB4 for <dhcwg@ietf.org>; Tue,  7 Oct 2014 07:46:31 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id x12so9663191wgg.32 for <dhcwg@ietf.org>; Tue, 07 Oct 2014 07:46:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=zkCbMZugv5smPqgEn9OlXiLsLqwkuH8OYhGdyYFtvZ4=; b=ODm5cQ719LplvQibc89USxReze/VgzpAQgmaT/RQdLWLKM3oz9rJQPd7JC9rpUUOMA tIb/6Hk5CkNRF0nh3syvguXjptTltCS0AJGMvJeH3QOxxJo+W+mFLiUJSBTpKPzmNhIi kpj1hqgbFacSnuxLGXBZQyiPLxa+ry30SFfFVXmuPlkyE10XqKr9im1+8rAHPtBuYaQU FWv0D21CUi7vWiq7MV9SUDubV/1w0B4+jFCSGLOTw0mbxWMbf0nHQHEXULrVJYv+0rtC WI8Xx+I4uv51/j+toF0Iax/cEpxhGWWngyV/MIgF+W4Q07WfjlXHvwt+HfROdmW+FpF8 21YA==
X-Received: by 10.180.78.35 with SMTP id y3mr5106444wiw.39.1412693190033; Tue, 07 Oct 2014 07:46:30 -0700 (PDT)
Received: from [192.168.43.206] (37.30.102.132.nat.umts.dynamic.t-mobile.pl. [37.30.102.132]) by mx.google.com with ESMTPSA id k2sm8393252wiz.18.2014.10.07.07.46.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 07:46:29 -0700 (PDT)
Message-ID: <5433FCC3.70800@gmail.com>
Date: Tue, 07 Oct 2014 16:46:27 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1B6ABDD8@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6ABDD8@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Q7_0UUhGcksilFS506IgjqiqctM
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 07 Oct 2014 14:46:33 -0000

On 29/09/14 16:36, Bernie Volz (volz) wrote:
> Please send your comments by October 13th, 2014. If you do not feel this
> document should advance, please state your reasons why.
As a co-author, I support this I-D moving forward.

This draft received quite a lot of reviews in its -01 version (thanks
again). Can I ask people who did the review back then (Andre, Carsten,
Simon, Jinmei and Suresh) to double check that all your comments were
addressed?

Thanks,
Tomek


From nobody Tue Oct  7 08:11:39 2014
Return-Path: <jean-francois.tremblay@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 671951A6F81 for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 08:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.687
X-Spam-Level: 
X-Spam-Status: No, score=-2.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 u0O9R-jLN3cs for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 08:11:35 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id F31961ACDFF for <dhcwg@ietf.org>; Tue,  7 Oct 2014 08:11:27 -0700 (PDT)
Received: from h200.viagenie.ca (h200.viagenie.ca [206.123.31.200]) by jazz.viagenie.ca (Postfix) with ESMTPSA id BECBA4021B for <dhcwg@ietf.org>; Tue,  7 Oct 2014 11:11:26 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: JF Tremblay <jean-francois.tremblay@viagenie.ca>
In-Reply-To: <5433FCC3.70800@gmail.com>
Date: Tue, 7 Oct 2014 11:11:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8EE89357-57AC-44EF-962A-F709F8876B7E@viagenie.ca>
References: <489D13FBFA9B3E41812EA89F188F018E1B6ABDD8@xmb-rcd-x04.cisco.com> <5433FCC3.70800@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/nKUVC7GEC-vzq0l7Lo68Y0esmWE
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 07 Oct 2014 15:11:37 -0000

I=92ve read draft-ietf-dhc-topo-conf-03 and found it useful and ready to =
go.=20

Some text (last sentence of page 5 for example) seem to imply that =
=93non-link local =3D=3D global=94 and skip cases where ULA could be =
used, but this is minor. I don=92t think anyone using ULAs on links =
would have a problem implementing this.=20

Section 9 could have been a little bit more detailed, but I guess it =
would be hard without getting the rathole of implementation specific =
details. IMHO scenarios where multiple subnets are assigned to a link =
are a bit more common that the text suggests, but I=92m not suggesting =
changing anything in this section.=20

Found a single nit, section 9, second paragraph:=20
"To support such an configuration=94: s/an/a/

Also, interesting choice of wording in the IANA section=85 ;)=20

JF

On Oct 7, 2014, at 10:46 AM, Tomek Mrugalski =
<tomasz.mrugalski@gmail.com> wrote:

> On 29/09/14 16:36, Bernie Volz (volz) wrote:
>> Please send your comments by October 13th, 2014. If you do not feel =
this
>> document should advance, please state your reasons why.
> As a co-author, I support this I-D moving forward.
>=20
> This draft received quite a lot of reviews in its -01 version (thanks
> again). Can I ask people who did the review back then (Andre, Carsten,
> Simon, Jinmei and Suresh) to double check that all your comments were
> addressed?
>=20
> Thanks,
> Tomek
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>=20


From nobody Tue Oct  7 14:02:12 2014
Return-Path: <ayourtch@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0D2F1A8871 for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 14:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 B6250IJu2R7L for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 14:02:09 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 296B81A0AFE for <dhcwg@ietf.org>; Tue,  7 Oct 2014 14:02:09 -0700 (PDT)
Received: by mail-ig0-f182.google.com with SMTP id hn18so5846914igb.9 for <dhcwg@ietf.org>; Tue, 07 Oct 2014 14:02:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=4a+5w1cjFZJebfm8cu5WHZvpMIAjE+ScQYl8GPJFjPU=; b=i39SaOF7HBjDrAVEHtkZYszDshJaN/nOfnumW6SE7qSMvPIw8v0Pw77807NP2mORcP COprmZEILIHLSjg7Wzi8pEcWaEiSnnX8Na9lfuM2c1Rn2JR44NukY4cyWPqGgMDCX3NI zgYMlT7SLam6E1IxJ0oeheDx+sZuEO4XqX9ftO5jFxRu32rmRV7wBiYjgacPfRaWl3KH pz9MiNWgQMaJrNfA8y7RyhkxL/pKOCbN3ZTuhcgqNmDkeCo5qTzBi8phhZ7AFOQMqVwT EcDDR1SH9H6IJT14U0N/xoiDkLq5Fa3j0GywGRJPJLu9PQbJq32x8IYM3x9cJlOAcsrD j6wQ==
MIME-Version: 1.0
X-Received: by 10.50.114.40 with SMTP id jd8mr35482013igb.35.1412715728592; Tue, 07 Oct 2014 14:02:08 -0700 (PDT)
Received: by 10.107.137.231 with HTTP; Tue, 7 Oct 2014 14:02:08 -0700 (PDT)
Date: Tue, 7 Oct 2014 23:02:08 +0200
Message-ID: <CAPi140NgaB86ACNrxFkZziGEpf=dEQEN9zuiukp3GipGQ0cWCw@mail.gmail.com>
From: =?UTF-8?B?QW5kcmV3IPCfkb0gIFlvdXJ0Y2hlbmtv?= <ayourtch@gmail.com>
To: dhcwg@ietf.org, Ole Troan <ot@cisco.com>, volz@cisco.com, msiodelski@gmail.com
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/kiwUceuVOEYaRrHXm3JI0XvQGUw
Subject: Re: [dhcwg] FW: Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 07 Oct 2014 21:02:10 -0000

I volunteered to review the draft, below go a couple of thoughts that
popped up while reading the document.

"4.3.  T1/T2 Timers"

the text says: "To deal
   with the case where servers have not yet been updated to do that,
   clients MUST use the shortest (explicit or implicit) T1/T2 times
   (larger than 0), from the same IA option, in the Reply.  T1/T2 times
   from other IAs are ignored.", but then at the same time mandate the
servers to set the timers equal.

Arguably the above requirement to the clients is a simple robustness
requirement which will have to always be present - the client has no
assurance in advance that the server follows the "MUST" until it
checked all T1/T2s - and selected the minimum.

Then - what is the benefit of requiring the server to recalculate the
T1/T2 ? I'd think it should be relaxed to "SHOULD".


"4.4.3.  Updates to section 18.1.3 of RFC 3315"

Record T1 and T2 times.  The client MUST use the shortest
        (explicit or implicit) T1 and T2 times (larger than 0) from the
        same IA option across all of the IA options to facilitate
        initiating the renewal process for all bindings simultaneously.
        T1/T2 times from other IAs are ignored.

What about case T1x > T1y but T2x < T2y ? Should the one with the
shortest T1 win ?

"4.4.5.  Updates to Section 18.1.8 of RFC 3315"

This text:

"
     the client retransmits the original message to the same server to
     retry the desired operation, the client MUST limit the rate at
     which it retransmits the message and limit the duration of the time
     during which it retransmits the message.
"

I think it should be more specific about the numbers. Should there be
a reference to https://tools.ietf.org/html/rfc7083 in some way as a
guidance ?

--a


From nobody Tue Oct  7 19:36:31 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB4741A02C2 for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 19:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.987
X-Spam-Level: 
X-Spam-Status: No, score=-14.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 suVxLGmq3C9z for <dhcwg@ietfa.amsl.com>; Tue,  7 Oct 2014 19:36:28 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B05751A8F4E for <dhcwg@ietf.org>; Tue,  7 Oct 2014 19:36:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4488; q=dns/txt; s=iport; t=1412735787; x=1413945387; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=36651T9y0lg9dLXK9MARkosHsouWWZ06Es9mDgc9Z6w=; b=kkhVuFO2svYgvtu0ewQavAnFpnORaGtnePdayGAjBocAHA6QUaxcuP4r E61k1exgaVLGdx4ANojQnNohSV//Xnm+2oOYPaUDeuMi4uuqhI9MNuVSk RQwIeWIvWobHL2FH0ZTt6ESiY5xZR6qfX+M5nuYTnH50bGVgSAT/Dcqmy 4=;
X-IronPort-AV: E=Sophos;i="5.04,674,1406592000"; d="scan'208";a="84927613"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-3.cisco.com with ESMTP; 08 Oct 2014 02:36:27 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s982aQnd008513 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Oct 2014 02:36:27 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0195.001; Tue, 7 Oct 2014 21:36:26 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?utf-8?B?QW5kcmV3IPCfkb0gIFlvdXJ0Y2hlbmtv?= <ayourtch@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Ole Troan <ot@cisco.com>, "msiodelski@gmail.com" <msiodelski@gmail.com>
Thread-Topic: FW: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
Thread-Index: AQHP4nH5IfZHiCjLUkOqRMmvbxIRRZwleLxQ
Date: Wed, 8 Oct 2014 02:36:25 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6BD11B@xmb-rcd-x04.cisco.com>
References: <CAPi140NgaB86ACNrxFkZziGEpf=dEQEN9zuiukp3GipGQ0cWCw@mail.gmail.com>
In-Reply-To: <CAPi140NgaB86ACNrxFkZziGEpf=dEQEN9zuiukp3GipGQ0cWCw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.227]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/x6afLnmqAHMIHCQUIYHibNapjU4
Subject: Re: [dhcwg] FW: Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 08 Oct 2014 02:36:30 -0000

SGk6DQoNClRoYW5rcyBmb3IgdGhlIGNvbW1lbnRzLg0KDQpSZWdhcmRpbmcgNC4zIFQxL1QyIHRp
bWVyczoNCg0KSXQgcmVhbGx5IGlzIHVwIHRvIHRoZSBzZXJ2ZXIgKG9yIGNsaWVudCkgdG8gcGlj
ayBvbmUgb2YgdGhlIHNldCBvZiBsaWZldGltZXMuIFdoZXRoZXIgaXQgYmFzZXMgaXRzIGRlY2lz
aW9uIG9uIFQxIG9yIFQyIChvciBzb21lIGNvbWJpbmF0aW9uKSBpcyB1cCB0aGUgY2xpZW50IG9y
IHNlcnZlci4gVGhlIGltcG9ydGFudCBwb2ludCBpcyB0aGF0IGl0IHBpY2tzIG9uZSBJQSdzIFQx
L1QyIHZhbHVlcy4gSSB3b3VsZCB0aGluayB0aGF0IHNob3J0ZXN0ICgnZWZmZWN0aXZlJykgVDEg
aXMgcHJvYmFibHkgdGhlIGJlc3QgYXBwcm9hY2guIElmIHRoZSBXRyBmZWVscyB3ZSBzaG91bGQg
bWFuZGF0ZSB0aGF0LCB3ZSBjb3VsZC4NCg0KV2hpbGUgd2UgY291bGQgcmVsYXggdGhlIHNlcnZl
cidzIE1VU1QgdG8gYSBTSE9VTEQsIHRoYXQgYWxsb3dzIG5ldyBzZXJ2ZXJzIHRvIG5vdCBmb2xs
b3cgdGhpcyB3aGljaCBwcm9iYWJseSBpcyBub3QgdGhlIGJlc3QgaWRlYS4gRXhpc3RpbmcgIjMz
MTUgY29tcGF0aWJsZSIgc2VydmVycyBjYW4gc3RpbGwgZG8gd2hhdCB0aGV5IGRvIHRvZGF5Lg0K
DQpSZWdhcmRpbmcgNC40LjUsIHRoaXMgaXMgYSByZXRyYW5zbWlzc2lvbiBvZiBSZXF1ZXN0L1Jl
bmV3L1JlYmluZCBhbmQgbm90IFNvbGljaXQuIFRoZSBpZGVhIGhlcmUgaXMgdGhhdCB3ZSBkb24n
dCB3YW50IHRoZSBjbGllbnQgdG8gdHVybiBhcm91bmQgYW5kIHJldHJhbnNtaXQgaW1tZWRpYXRl
bHkgdGhlIFJlcXVlc3QvUmVuZXcvUmViaW5kIGFzIHRoYXQgY291bGQgY3JlYXRlIGEgc3Rvcm0g
KHJlcXVlc3QgZm9sbG93ZWQgYnkgUmVwbHkgd2l0aCBVblNwZWNGYWlsKS4gVGhpcyBpcyBhbHNv
IHRoZSB0ZXh0IHRoYXQgd2FzIGNvcGllZCBESVJFQ1RMWSBmcm9tIFJGQyAzMzE1IC0gaXQgd2Fz
ICBub3QgbW9kaWZpZWQuIElmIHlvdSBmZWVsIHRoaXMgc2hvdWxkIGJlIGNoYW5nZWQgb3IgY2xh
cmlmaWVkLCBsZXQncyB0YWtlIHRoaXMgdXAgaW4gdGhlIERIQ1B2NiBiaXMgd29yayAoY3JlYXRl
IGEgdGlja2V0IGZvciBpdCkuIEkgd291bGQgcmF0aGVyIG5vdCBleHBhbmQgdGhlIGlzc3VlcyBp
biB0aGlzIGRyYWZ0Lg0KDQotIEJlcm5pZQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
RnJvbTogQW5kcmV3IPCfkb0gWW91cnRjaGVua28gW21haWx0bzpheW91cnRjaEBnbWFpbC5jb21d
IA0KU2VudDogVHVlc2RheSwgT2N0b2JlciAwNywgMjAxNCA1OjAyIFBNDQpUbzogZGhjd2dAaWV0
Zi5vcmc7IE9sZSBUcm9hbjsgQmVybmllIFZvbHogKHZvbHopOyBtc2lvZGVsc2tpQGdtYWlsLmNv
bQ0KU3ViamVjdDogUmU6IEZXOiBbZGhjd2ddIFBsZWFzZSByZXZpZXcgdmVyc2lvbiAtMDcgb2Yg
ZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXN0YXRlZnVsLWlzc3Vlcw0KDQpJIHZvbHVudGVlcmVkIHRv
IHJldmlldyB0aGUgZHJhZnQsIGJlbG93IGdvIGEgY291cGxlIG9mIHRob3VnaHRzIHRoYXQgcG9w
cGVkIHVwIHdoaWxlIHJlYWRpbmcgdGhlIGRvY3VtZW50Lg0KDQoiNC4zLiAgVDEvVDIgVGltZXJz
Ig0KDQp0aGUgdGV4dCBzYXlzOiAiVG8gZGVhbA0KICAgd2l0aCB0aGUgY2FzZSB3aGVyZSBzZXJ2
ZXJzIGhhdmUgbm90IHlldCBiZWVuIHVwZGF0ZWQgdG8gZG8gdGhhdCwNCiAgIGNsaWVudHMgTVVT
VCB1c2UgdGhlIHNob3J0ZXN0IChleHBsaWNpdCBvciBpbXBsaWNpdCkgVDEvVDIgdGltZXMNCiAg
IChsYXJnZXIgdGhhbiAwKSwgZnJvbSB0aGUgc2FtZSBJQSBvcHRpb24sIGluIHRoZSBSZXBseS4g
IFQxL1QyIHRpbWVzDQogICBmcm9tIG90aGVyIElBcyBhcmUgaWdub3JlZC4iLCBidXQgdGhlbiBh
dCB0aGUgc2FtZSB0aW1lIG1hbmRhdGUgdGhlIHNlcnZlcnMgdG8gc2V0IHRoZSB0aW1lcnMgZXF1
YWwuDQoNCkFyZ3VhYmx5IHRoZSBhYm92ZSByZXF1aXJlbWVudCB0byB0aGUgY2xpZW50cyBpcyBh
IHNpbXBsZSByb2J1c3RuZXNzIHJlcXVpcmVtZW50IHdoaWNoIHdpbGwgaGF2ZSB0byBhbHdheXMg
YmUgcHJlc2VudCAtIHRoZSBjbGllbnQgaGFzIG5vIGFzc3VyYW5jZSBpbiBhZHZhbmNlIHRoYXQg
dGhlIHNlcnZlciBmb2xsb3dzIHRoZSAiTVVTVCIgdW50aWwgaXQgY2hlY2tlZCBhbGwgVDEvVDJz
IC0gYW5kIHNlbGVjdGVkIHRoZSBtaW5pbXVtLg0KDQpUaGVuIC0gd2hhdCBpcyB0aGUgYmVuZWZp
dCBvZiByZXF1aXJpbmcgdGhlIHNlcnZlciB0byByZWNhbGN1bGF0ZSB0aGUNClQxL1QyID8gSSdk
IHRoaW5rIGl0IHNob3VsZCBiZSByZWxheGVkIHRvICJTSE9VTEQiLg0KDQoNCiI0LjQuMy4gIFVw
ZGF0ZXMgdG8gc2VjdGlvbiAxOC4xLjMgb2YgUkZDIDMzMTUiDQoNClJlY29yZCBUMSBhbmQgVDIg
dGltZXMuICBUaGUgY2xpZW50IE1VU1QgdXNlIHRoZSBzaG9ydGVzdA0KICAgICAgICAoZXhwbGlj
aXQgb3IgaW1wbGljaXQpIFQxIGFuZCBUMiB0aW1lcyAobGFyZ2VyIHRoYW4gMCkgZnJvbSB0aGUN
CiAgICAgICAgc2FtZSBJQSBvcHRpb24gYWNyb3NzIGFsbCBvZiB0aGUgSUEgb3B0aW9ucyB0byBm
YWNpbGl0YXRlDQogICAgICAgIGluaXRpYXRpbmcgdGhlIHJlbmV3YWwgcHJvY2VzcyBmb3IgYWxs
IGJpbmRpbmdzIHNpbXVsdGFuZW91c2x5Lg0KICAgICAgICBUMS9UMiB0aW1lcyBmcm9tIG90aGVy
IElBcyBhcmUgaWdub3JlZC4NCg0KV2hhdCBhYm91dCBjYXNlIFQxeCA+IFQxeSBidXQgVDJ4IDwg
VDJ5ID8gU2hvdWxkIHRoZSBvbmUgd2l0aCB0aGUgc2hvcnRlc3QgVDEgd2luID8NCg0KIjQuNC41
LiAgVXBkYXRlcyB0byBTZWN0aW9uIDE4LjEuOCBvZiBSRkMgMzMxNSINCg0KVGhpcyB0ZXh0Og0K
DQoiDQogICAgIHRoZSBjbGllbnQgcmV0cmFuc21pdHMgdGhlIG9yaWdpbmFsIG1lc3NhZ2UgdG8g
dGhlIHNhbWUgc2VydmVyIHRvDQogICAgIHJldHJ5IHRoZSBkZXNpcmVkIG9wZXJhdGlvbiwgdGhl
IGNsaWVudCBNVVNUIGxpbWl0IHRoZSByYXRlIGF0DQogICAgIHdoaWNoIGl0IHJldHJhbnNtaXRz
IHRoZSBtZXNzYWdlIGFuZCBsaW1pdCB0aGUgZHVyYXRpb24gb2YgdGhlIHRpbWUNCiAgICAgZHVy
aW5nIHdoaWNoIGl0IHJldHJhbnNtaXRzIHRoZSBtZXNzYWdlLg0KIg0KDQpJIHRoaW5rIGl0IHNo
b3VsZCBiZSBtb3JlIHNwZWNpZmljIGFib3V0IHRoZSBudW1iZXJzLiBTaG91bGQgdGhlcmUgYmUg
YSByZWZlcmVuY2UgdG8gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzcwODMgaW4gc29t
ZSB3YXkgYXMgYSBndWlkYW5jZSA/DQoNCi0tYQ0K


From nobody Wed Oct  8 04:13:00 2014
Return-Path: <ayourtch@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D3591A0271 for <dhcwg@ietfa.amsl.com>; Wed,  8 Oct 2014 04:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 L76J1bnEohOh for <dhcwg@ietfa.amsl.com>; Wed,  8 Oct 2014 04:12:55 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99E591A026E for <dhcwg@ietf.org>; Wed,  8 Oct 2014 04:12:55 -0700 (PDT)
Received: by mail-ig0-f182.google.com with SMTP id hn18so8002336igb.9 for <dhcwg@ietf.org>; Wed, 08 Oct 2014 04:12:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=6umGNM9iprGs62bzVBehifs9CeiLlElEc8niM20JHv0=; b=UfqmhVTny0hPhvaJhb5WBShVO0P+ikLgTVjDd17shje473PO7jvTPWaj2JNr9iHWOJ cej5gjGLXQm+ciZETb7U7jndm+wSQ+tmzpFhWaCx9Il2b8tZZ/5RCfQYYP3N/t6J4lcM EFE5iogjmPK8OGpjYiTIiLir5uLZ6z8SytcEYecLOKORLoZyIFRHWX0Pfal/8z61PJdi owwhPEHoAAYmMhhQp3Zi99vlH/9yzN7nBlc0EORuGGhxKi6Rt1nN4yAAd+9sc7r97gqm 5RFHrGz9B8gc9WFgX75f9/h8eFvjZqOqZKpm4b/aIBkXcEoex/rlo/OkuP9rF9wZQg42 /ytw==
MIME-Version: 1.0
X-Received: by 10.50.128.234 with SMTP id nr10mr2077487igb.30.1412766774826; Wed, 08 Oct 2014 04:12:54 -0700 (PDT)
Received: by 10.107.137.231 with HTTP; Wed, 8 Oct 2014 04:12:54 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6BD11B@xmb-rcd-x04.cisco.com>
References: <CAPi140NgaB86ACNrxFkZziGEpf=dEQEN9zuiukp3GipGQ0cWCw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6BD11B@xmb-rcd-x04.cisco.com>
Date: Wed, 8 Oct 2014 13:12:54 +0200
Message-ID: <CAPi140MSoW5yfSjc6u6qprFQrmkwqOZUgOdcEACP8th+i=bY2Q@mail.gmail.com>
From: =?UTF-8?B?QW5kcmV3IPCfkb0gIFlvdXJ0Y2hlbmtv?= <ayourtch@gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/FItOqyhotQvBCwZ9_BbnLU8oHk4
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ole Troan <ot@cisco.com>
Subject: Re: [dhcwg] FW: Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 08 Oct 2014 11:12:57 -0000

Hi Bernie,

On 10/8/14, Bernie Volz (volz) <volz@cisco.com> wrote:
> Hi:
>
> Thanks for the comments.
>
> Regarding 4.3 T1/T2 timers:
>
> It really is up to the server (or client) to pick one of the set of
> lifetimes. Whether it bases its decision on T1 or T2 (or some combination=
)
> is up the client or server. The important point is that it picks one IA's
> T1/T2 values. I would think that shortest ('effective') T1 is probably th=
e
> best approach. If the WG feels we should mandate that, we could.

I just thought it'd be a question I'd have if implementing this, and
"shortest T1" seemed an okay-ish strawman. Maybe this is a non-issue
altogether and we do not care if the client decides in a different
way.

>
> While we could relax the server's MUST to a SHOULD, that allows new serve=
rs
> to not follow this which probably is not the best idea. Existing "3315
> compatible" servers can still do what they do today.

Conceptually, with this update we want to have a single instance of
T1/T2; yet it has to be multiple instances in the PDU. We specify that
this instance is "virtually" derived as a "minimal" (cf. the comment
above) pair. So, conceptually it "feels" right as well to force the
servers to send the T1/T2 pairs identical - because conceptually they
are a duplicate of the same thing.

But, violating this requirement that the servers send the same T1/T2
for all, does not prevent the interop - this in my book makes "MUST"
too strong of a word. OTOH, we still want to make it easy to
understand the interaction and get the expected results even if the
clients somehow do not sort the T1/T2, so "MAY" is too weak. This
makes it a SHOULD in my book.

Now, an example.

Say I have two address pools A & B with different lifetimes, and one
prefix pool P.

I have different policies on the A and B - for A, I want to recycle
the addresses every day (it's a public wifi network where people come
and go), for B I want to keep them for three weeks (it's my employees,
I'd like to try keep the addresses stable even if they go for a PTO).
The prefixes, I want to keep as permanent as possible.

This "MUST" for the server means that either I will have to split the
P in two, or that the server will have to "tweak" the values from my
config before sending onto the wire.

Both of which add operational complexity and reduce transparency.

So, it's this type of a use case that made me write the comment - I
could not find a good argument to say why the servers *must* set the
T1/T2 pairs identically beyond "because conceptually it's the same
value", and that seemed too weak in comparison... What did I miss ?

>
> Regarding 4.4.5, this is a retransmission of Request/Renew/Rebind and not
> Solicit. The idea here is that we don't want the client to turn around an=
d
> retransmit immediately the Request/Renew/Rebind as that could create a st=
orm
> (request followed by Reply with UnSpecFail). This is also the text that w=
as
> copied DIRECTLY from RFC 3315 - it was  not modified. If you feel this
> should be changed or clarified, let's take this up in the DHCPv6 bis work
> (create a ticket for it). I would rather not expand the issues in this
> draft.

Makes sense, thanks!

I do not have a strong feeling about it, but it's easy to revisit &
junk the ticket later, so I tabled it at:
http://trac.tools.ietf.org/group/dhcpv6bis/ticket/122

--a


>
> - Bernie
>
> -----Original Message-----
> From: Andrew =F0=9F=91=BD Yourtchenko [mailto:ayourtch@gmail.com]
> Sent: Tuesday, October 07, 2014 5:02 PM
> To: dhcwg@ietf.org; Ole Troan; Bernie Volz (volz); msiodelski@gmail.com
> Subject: Re: FW: [dhcwg] Please review version -07 of
> draft-ietf-dhc-dhcpv6-stateful-issues
>
> I volunteered to review the draft, below go a couple of thoughts that pop=
ped
> up while reading the document.
>
> "4.3.  T1/T2 Timers"
>
> the text says: "To deal
>    with the case where servers have not yet been updated to do that,
>    clients MUST use the shortest (explicit or implicit) T1/T2 times
>    (larger than 0), from the same IA option, in the Reply.  T1/T2 times
>    from other IAs are ignored.", but then at the same time mandate the
> servers to set the timers equal.
>
> Arguably the above requirement to the clients is a simple robustness
> requirement which will have to always be present - the client has no
> assurance in advance that the server follows the "MUST" until it checked =
all
> T1/T2s - and selected the minimum.
>
> Then - what is the benefit of requiring the server to recalculate the
> T1/T2 ? I'd think it should be relaxed to "SHOULD".
>
>
> "4.4.3.  Updates to section 18.1.3 of RFC 3315"
>
> Record T1 and T2 times.  The client MUST use the shortest
>         (explicit or implicit) T1 and T2 times (larger than 0) from the
>         same IA option across all of the IA options to facilitate
>         initiating the renewal process for all bindings simultaneously.
>         T1/T2 times from other IAs are ignored.
>
> What about case T1x > T1y but T2x < T2y ? Should the one with the shortes=
t
> T1 win ?
>
> "4.4.5.  Updates to Section 18.1.8 of RFC 3315"
>
> This text:
>
> "
>      the client retransmits the original message to the same server to
>      retry the desired operation, the client MUST limit the rate at
>      which it retransmits the message and limit the duration of the time
>      during which it retransmits the message.
> "
>
> I think it should be more specific about the numbers. Should there be a
> reference to https://tools.ietf.org/html/rfc7083 in some way as a guidanc=
e
> ?
>
> --a
>


From nobody Wed Oct  8 11:23:01 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4759A1ACDB0 for <dhcwg@ietfa.amsl.com>; Wed,  8 Oct 2014 11:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 HesN9m1quAtY for <dhcwg@ietfa.amsl.com>; Wed,  8 Oct 2014 11:22:57 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC0341A86DF for <dhcwg@ietf.org>; Wed,  8 Oct 2014 11:22:56 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id a1so12054638wgh.23 for <dhcwg@ietf.org>; Wed, 08 Oct 2014 11:22:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3T6PPffym4nqLWVsijfi7CopGwDtwNBnsP/P+NQOhzk=; b=JXbdbTr32td/inknUC7fsyoygezfpAqbjKR6I5U5aOiMFkiYaaa6+uGYedX0xM5u+F m22dQGcb6x9Ds8AJyo5VZ3Bo7EhpixCIVSbcgLwASzuU6WT4vCkXO/SGSe1NHqNVXROk NWsPWQIrB2hg+u+iNO3MUuG9dLz/XrU98Xk0nnkzKCB7EGwrkyrXN9PyqLexpzgMdRRx mK0g1i2IAGUawTAG6x7kAcyssLyo6HMXCbJql9xCIXkBANH29lHx0kFuL6tMOgOkjxqZ fBzie6aX1pbnRGruxkaWDogRbn7P+gK0wjmbFoQ6ZnKJ0U8t4mD/nG+pwY5GDLg9vEqs vuHg==
MIME-Version: 1.0
X-Received: by 10.180.106.202 with SMTP id gw10mr35123971wib.62.1412792575118;  Wed, 08 Oct 2014 11:22:55 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.195.13.83 with HTTP; Wed, 8 Oct 2014 11:22:55 -0700 (PDT)
In-Reply-To: <542D1698.7030203@gmail.com>
References: <542D1698.7030203@gmail.com>
Date: Wed, 8 Oct 2014 11:22:55 -0700
X-Google-Sender-Auth: DgxfLO7KRNzSaQaVHKU1_l-XrMk
Message-ID: <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Marcin Siodelski <msiodelski@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/ZfpNpCHHcXrgXVV8v-_ejH4FyIU
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 08 Oct 2014 18:22:59 -0000

At Thu, 02 Oct 2014 11:10:48 +0200,
Marcin Siodelski <msiodelski@gmail.com> wrote:

> The version -07 of the draft-ietf-dhc-dhcpv6-stateful-issues is now
> available at:
>
> http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/
[...]
> Please provide your comments. Note that this work builds the ground for
> the RFC3315bis, so your interest is important.

Here's my review.  I almost forgot the full context of the discussion
regarding my previous review comments, so I might simply repeat some
points I made before.  Hopefully they are still valid.

First, I have a couple of higher level points to discuss:

- What's the final goal of this document?  Is it supposed to be
  published as a separate RFC, or is it just a placeholder for
  discussion for 3315bis and is supposed to be dropped once the result
  is incorporated to 3315bis?  I'm asking this because in its current
  form this document relies on the fact that readers are pretty
  familiar with the discussion context and won't be friendly for
  future readers if published as a separate document.  But if the goal
  is the latter of the above two, it's probably okay and it would be
  more constructive to just discuss purely technical matters rather
  than try to make it (more) readable for first-time readers.

- I'm not necessarily opposed to it, but why this?

> 5. Removed the "unified" text (intended for RFC3315bis) from the
> Renew/Rebind sections. The current text only provides respective updates
> for RFC3315 and RFC3633.

  If the eventual goal is to unify 3315 and 3633 in 3315bis (I
  personally didn't think it a very good idea, but I wouldn't argue on
  that point in this context), such unification will be eventually
  inevitable.  So shouldn't it rather better to discuss it sooner
  (i.e., in this draft) than later?

Specific comments to the draft text follow:

- Title: now that our main focus is the mixed use of IA_NA and IA_PD
  rather than generalizing the concept of stateful resources, I think
  it makes more sense to reflect it in the title, for example,
  "Issues and Recommendations with Multiple DHCPv6 IA Options".
  See also my comments on Section 3 (terminology) below.

- Abstract: this is more about readability (see above), but I'm afraid
  the current abstract text wouldn't be really helpful for first-time
  readers (on the other hand, it's not a problem for "me", because I
  already know what it is).  At the very least I'd briefly summarize
  the actual proposals here.  On the other hand, I don't see the
  sentence that refers to RFC 7084 in this context (it's useful in
  Introduction, but not for abstract).

- Section 1: this is not a complete sentence:

   [...] And, to provide a framework to support
   new IA option types, assuming they are similar enough.

  probably it's just expected to be a continuation of the preceding
  sentence? "requested as per [RFC7084], and to provide...".

- Section 1, regarding the same text and this one:

   [...]  Future
   documents that define new IA option types will need to specify
   whether they fit into this framework or define the DHCP operation for
   the new and existing IA option types, as appropriate.

  IMO, this document should talk a bit more about the "framework".
  I'd suggest explaining these, for example: this framework is based
  on some assumptions, including:
  - An IA option has the concept of T1/T2 values for renew and rebind,
    and the semantics is same for all these IA options types
  - The information (or a set of it) assigned in IA is associated with
    a lifetime.
  - These multiple IA options are expected to be assigned as a set,
    and it's generally considered an operator's error if a DHCPv6
    server can only provide a subset of it, even if it's not rejected
    by the protocol. (without this assumption, we could have an
    awkward situation, e.g., where a client request both IA_NA and
    IA_PD and the server only replies with IA_NA, and the client can't
    get IA_PD at least until the first renew or unless reconfigure is
    made possible)

- Section 1, on the paragraph talking about IA_TA:

   Note that while IA_TA (temporary addresses) options may be included
   with other IA option type requests, [...]

  I have a feeling that this paragraph is incomplete.  That is, I'd
  say "so what?" on reading this paragraph.  My suggestion is to
  clearly declare that the mixture of IA_TA and other types of IAs is
  out of scope of this document.  In fact, IA_TA doesn't fit in the
  framework shown in the previous bullet (as it doesn't have T1/T2),
  and we won't be able to well-define it.  And we can probably justify
  the decision based on the observation that it "has limited value".
  This paragraph would make sense if it's provided with such a
  decision.

- Section 3: now that we've limited the scope of this document
  mainly focusing on the specific case of IA_NA and IA_PD, I
  suggest simplifying the terminology.  It would be more
  reader-friendly if the reader doesn't have to understand fewer
  concepts as a prerequisite.  Specifically:
  - remove "resource".  I don't see the need for this generalized
    concept anymore.  In fact, other than in this particular section,
    this term is used only once (Section 4.1)
  - replace "stateful options" with "IA options" (and to this end we
    might not bother to list in the terminology section explicitly)

- Section 4: I suggest adding the rationale of the proposal.  In its
  current form the proposal seems to be suddenly given without
  explaining why.  Even if some hints are (seemingly) scattered in
  other sections of the document, I believe this should be the primary
  place to give it.

- Section 4.1, regarding the replacement for RFC 3315 17.2.2:

      If the server will not assign any addresses to an IA in a
      subsequent Request from the client, the server MUST include
      the IA in the Advertise message with no addresses in the IA
      and a Status Code option encapsulated in the IA containing
      status code NoAddrsAvail.

  Maybe we should also say "the server MUST NOT place a Status Code
  option for an IA at the top level".

- Section 4.2: replacement for RFC 3315 17.1.3:

     The client MUST ignore any Advertise message that contains no
     addresses (IAADDR options encapsulated in IA_NA or IA_TA options)
     and no delegated prefixes (IAPREFIX options encapsulated in IA_PD
     options, see RFC 3633) with the exception that the client
     MUST process an included SOL_MAX_RT option (RFC 7083), MUST
     process an included INF_MAX_RT option (RFC 7083), and MAY
     display any associated status message(s) to the user.

  It's awkward to see it mention prefixes while this version
  intentionally cancels the idea of "unified" text for renew/rebind.
  It's not clear to me why Section 17.1.3 (regarding advertise) still
  needs to provide "unified" text.

- Section 4.3: I don't understand the following text:

   [...] To deal
   with the case where servers have not yet been updated to do that,
   clients MUST use the shortest (explicit or implicit) T1/T2 times
   (larger than 0), from the same IA option, in the Reply.  T1/T2 times
   from other IAs are ignored.

  I guess it tries to address the corner case I pointed out for the
  previous version of the draft:
  http://www.ietf.org/mail-archive/web/dhcwg/current/msg15663.html
  but I don't even understand what the client would do in this case
  based on the new text.  To recap, what should happen if the client
  sees the following two sets of T1/T2 according to the above text?
  - T1a = 10, T2a = 20
  - T1b = 0, T2b = 5

- Section 4.4.5: does this mean, if the client has bindings of
  multiple IAs, it should (effectively) abandon all of the bindings
  and establish new bindings for all of the IAs starting from Solicit?
  If so, it makes sense to me, but it's not really clear from the
  text, and I suggest clarifying that point.

     When the client receives a NotOnLink status from the server in
     response to a Confirm message, the client performs DHCP server
     solicitation, as described in section 17, and client-initiated
     configuration as described in section 18.

- Section 4.4.5: I'm not sure if I understand this:

     -  Tries to obtain the IA from another server (by restarting the
        DHCP discovery process) if the client attempted to obtain a new
        binding in the Renew or Rebind message by sending an IA without
        any addresses and the server responded with NoBinding status
        code.

  What if the client has a binding for another IA (and it's
  successfully renewed in this response)?  If the above means the
  client starts a new DHCPv6 session for the IA that doesn't have a
  binding separately from the other IA with a binding, it seems to
  break the main idea of this draft: maintaining a single DHCPv6
  session for all IAs.  So does this mean the client terminates the
  existing DHCPv6 session and tries to establish all bindings for all
  IAs from Solicit?

--
JINMEI, Tatuya


From nobody Wed Oct  8 19:53:35 2014
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 138CD1A8A5A for <dhcwg@ietfa.amsl.com>; Wed,  8 Oct 2014 19:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level: 
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 HMCGuCRaUcBO for <dhcwg@ietfa.amsl.com>; Wed,  8 Oct 2014 19:53:32 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 604DB1A8A59 for <dhcwg@ietf.org>; Wed,  8 Oct 2014 19:53:32 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNL32204; Thu, 09 Oct 2014 02:53:30 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Oct 2014 03:53:29 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.22]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Thu, 9 Oct 2014 10:53:17 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-sedhcpv6-04.txt
Thread-Index: AQHP3H5IfTIf0zv/pUqsmp6T7lThMpwnEHBw
Date: Thu, 9 Oct 2014 02:53:16 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AF60909@nkgeml512-mbx.china.huawei.com>
References: <20140930071429.4951.26989.idtracker@ietfa.amsl.com>
In-Reply-To: <20140930071429.4951.26989.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/UtEE_6sRzPhxU_4OOeczXLdyQUs
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-sedhcpv6-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 09 Oct 2014 02:53:34 -0000

SGksIERIQywNCg0KVGhlIGF1dGhvcnMgaGF2ZSByZWNlbnRseSBzdWJtaXR0ZWQgYW4gdXBkYXRl
IHZlcnNpb24gdG8gYWRkcmVzc2VkIGNvbW1lbnRzIGZyb20gbWFpbCBsaXN0LiBUaGUgbWFqb3Ig
bW9kaWZpY2F0aW9ucyBpbmNsdWRlOg0KDQotIE1ha2luZyB0aW1lc3RhbXAgYW4gaW5kZXBlbmRl
bnQgYW5kIG9wdGlvbmFsIG9wdGlvbi4NCi0gUmVkdWNlIHRoZSBzZXJ2ZXJzaWRlIGF1dGhlbnRp
Y2F0aW9uIHRvIGJhc2Ugb24gb25seSBjbGllbnQncyBjZXJ0aWZpY2F0ZS4NCi0gUmVkdWNlIHRo
ZSBjbGllbnRzaWRlIGF1dGhlbnRpY2F0aW9uIHRvIG9ubHkgTGVhZiBvZiBGYWl0aCBiYXNlIG9u
IHNlcnZlcidzIHB1YmxpYyBrZXkuDQoNClJldmlld3MgYW5kIGNvbW1lbnRzIGFyZSBhcHByZWNp
YXRlZC4NCg0KQmVzdCByZWdhcmRzLA0KDQpTaGVuZw0KDQo+LS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj5Gcm9tOiBkaGN3ZyBbbWFpbHRvOmRoY3dnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJl
aGFsZiBPZg0KPmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZw0KPlNlbnQ6IFR1ZXNkYXksIFNlcHRl
bWJlciAzMCwgMjAxNCAzOjE0IFBNDQo+VG86IGktZC1hbm5vdW5jZUBpZXRmLm9yZw0KPkNjOiBk
aGN3Z0BpZXRmLm9yZw0KPlN1YmplY3Q6IFtkaGN3Z10gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1k
aGMtc2VkaGNwdjYtMDQudHh0DQo+DQo+DQo+QSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxh
YmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVzLg0KPiBUaGlz
IGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBEeW5hbWljIEhvc3QgQ29uZmlndXJhdGlvbiBX
b3JraW5nIEdyb3VwDQo+b2YgdGhlIElFVEYuDQo+DQo+ICAgICAgICBUaXRsZSAgICAgICAgICAg
OiBTZWN1cmUgREhDUHY2DQo+ICAgICAgICBBdXRob3JzICAgICAgICAgOiBTaGVuZyBKaWFuZw0K
PiAgICAgICAgICAgICAgICAgICAgICAgICAgU2VhbiBTaGVuDQo+ICAgICAgICAgICAgICAgICAg
ICAgICAgICBEYWNoZW5nIFpoYW5nDQo+ICAgICAgICAgICAgICAgICAgICAgICAgICBUYXR1eWEg
SmlubWVpDQo+CUZpbGVuYW1lICAgICAgICA6IGRyYWZ0LWlldGYtZGhjLXNlZGhjcHY2LTA0LnR4
dA0KPglQYWdlcyAgICAgICAgICAgOiAyMw0KPglEYXRlICAgICAgICAgICAgOiAyMDE0LTA5LTMw
DQo+DQo+QWJzdHJhY3Q6DQo+ICAgVGhlIER5bmFtaWMgSG9zdCBDb25maWd1cmF0aW9uIFByb3Rv
Y29sIGZvciBJUHY2IChESENQdjYpIGVuYWJsZXMNCj4gICBESENQdjYgc2VydmVycyB0byBwYXNz
IGNvbmZpZ3VyYXRpb24gcGFyYW1ldGVycy4gIEl0IG9mZmVycw0KPiAgIGNvbmZpZ3VyYXRpb24g
ZmxleGliaWxpdHkuICBJZiBub3QgYmVpbmcgc2VjdXJlZCwgREhDUHY2IGlzDQo+ICAgdnVsbmVy
YWJsZSB0byB2YXJpb3VzIGF0dGFja3MsIHBhcnRpY3VsYXJseSBzcG9vZmluZyBhdHRhY2tzLiAg
VGhpcw0KPiAgIGRvY3VtZW50IGFuYWx5emVzIHRoZSBzZWN1cml0eSBpc3N1ZXMgb2YgREhDUHY2
IGFuZCBzcGVjaWZpZXMgYQ0KPiAgIFNlY3VyZSBESENQdjYgbWVjaGFuaXNtIGZvciBjb21tdW5p
Y2F0aW9ucyBiZXR3ZWVuIERIQ1B2NiBjbGllbnRzDQo+YW5kDQo+ICAgREhDUHY2IHNlcnZlcnMu
ICBUaGlzIGRvY3VtZW50IHByb3ZpZGVzIGEgREhDUHY2IGNsaWVudC9zZXJ2ZXINCj4gICBhdXRo
ZW50aWNhdGlvbiBtZWNoYW5pc20gYmFzZWQgb24gc2VydmVyJ3MgcHVibGljL3ByaXZhdGUga2V5
IHBhaXJzDQo+ICAgYW5kIGNsaWVudCdzIGNlcnRpZmljYXRlcy4gIFRoZSBESENQdjYgbWVzc2Fn
ZSBleGNoYW5nZXMgYXJlDQo+ICAgcHJvdGVjdGVkIGJ5IHRoZSBzaWduYXR1cmUgb3B0aW9uIGFu
ZCB0aGUgdGltZXN0YW1wIG9wdGlvbiBuZXdseQ0KPiAgIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVu
dC4NCj4NCj4NCj5UaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFm
dCBpczoNCj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWRoYy1z
ZWRoY3B2Ni8NCj4NCj5UaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBh
dDoNCj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWRoYy1zZWRoY3B2Ni0w
NA0KPg0KPkEgZGlmZiBmcm9tIHRoZSBwcmV2aW91cyB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBhdDoN
Cj5odHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLWRoYy1zZWRoY3B2
Ni0wNA0KPg0KPg0KPlBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWlu
dXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24NCj51bnRpbCB0aGUgaHRtbGl6ZWQgdmVy
c2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPg0KPkludGVy
bmV0LURyYWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDoNCj5mdHA6
Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPg0KPl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ZGhjd2cgbWFpbGluZyBsaXN0DQo+ZGhjd2dA
aWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RoY3dnDQo=


From nobody Fri Oct 10 14:15:39 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27411AD2EC for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 14:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.688
X-Spam-Level: 
X-Spam-Status: No, score=-104.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 X55YQWo7AIFf for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 14:15:33 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 0091F1AD16B for <dhcwg@ietf.org>; Fri, 10 Oct 2014 14:15:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8FD73181C86; Fri, 10 Oct 2014 14:14:37 -0700 (PDT)
To: burcak@juniper.net, paduffy@cisco.com, brian@innovationslab.net, ted.lemon@nominum.com, volz@cisco.com, tomasz.mrugalski@gmail.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20141010211437.8FD73181C86@rfc-editor.org>
Date: Fri, 10 Oct 2014 14:14:37 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/wORp0I68fdKRxxMD2qKBYtsW4Eg
Cc: dhcwg@ietf.org, volz@cisco.com, rfc-editor@rfc-editor.org
Subject: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 10 Oct 2014 21:15:36 -0000

The following errata report has been submitted for RFC3495,
"Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3495&eid=4128

--------------------------------------
Type: Editorial
Reported by: Bernie Volz <volz@cisco.com>

Section: 5.5.

Original Text
-------------
   The PacketCable architecture requires an MTA to authenticate itself
   to the TSP's network via the Kerberos protocol.  A Kerberos Realm
   name is required at the MTA to permit a DNS lookup for the address of
   the TSP's Kerberos Key Distribution Center (KDC) entity.

   The Kerberos Realm name MUST be encoded per the domain style realm
   name described in RFC 1510 [5].  This realm name MUST be all capital
   letters and conform to the syntax described in RFC 1035 [3] section
   3.1.  The sub-option is encoded as follows:

       Code   Len   Kerberos Realm Name
      +-----+-----+-----+-----+   +-----+
      |  6  |  n  |  k1 |  k2 |...|  kn |
      +-----+-----+-----+-----+   +-----+

Corrected Text
--------------
   The PacketCable architecture requires an MTA to authenticate itself
   to the TSP's network via the Kerberos protocol.  A Kerberos Realm
   name is required at the MTA to permit a DNS lookup for the address of
   the TSP's Kerberos Key Distribution Center (KDC) entity.

   The Kerberos Realm name MUST be use a domain style realm name
   described in RFC 1510 [5].  This realm name MUST be all capital
   letters and be encoded as described in RFC 1035 [3] section 3.1.
   The sub-option is encoded as follows:

       Code   Len   Kerberos Realm Name
      +-----+-----+-----+-----+   +-----+
      |  6  |  n  |  k1 |  k2 |...|  kn |
      +-----+-----+-----+-----+   +-----+

   Where k1...kn is the "DNS wire" encoded realm name (see RFC 3315,
   section 8). Thus, the realm "BASIC.1" is encoded as
   "RFCCORRECTED_TEXT5BASICRFCCORRECTED_TEXT11RFCCORRECTED_TEXT0".

Notes
-----
This text is not completely clear about how the realm name is to be encoded - as a 'string' or 'fqdn'.

RFC 1510 states:

   Kerberos realms are encoded as GeneralStrings. Realms shall not
   contain a character with the code 0 (the ASCII NUL).  Most realms
   will usually consist of several components separated by periods (.),
   in the style of Internet Domain Names, or separated by slashes (/) in
   the style of X.500 names.

And the reference to RFC 1035 section 3.1 is "conform to the syntax" which isn't the same as use this encoding - though I do agree that section 3.1 is mostly about "DNS wire encoding". It is just the use of "encoded" and "confirm to the syntax" combination that makes this unclear.

It is believed that the intended encoding is in DNS wire format. And, this should be clarified.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC3495 (draft-ietf-dhc-packetcable-06)
--------------------------------------
Title               : Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration
Publication Date    : March 2003
Author(s)           : B. Beser, P. Duffy, Ed.
Category            : PROPOSED STANDARD
Source              : Dynamic Host Configuration
Area                : Internet
Stream              : IETF
Verifying Party     : IESG


From nobody Fri Oct 10 15:16:27 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 835081A88C8 for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 15:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.287
X-Spam-Level: 
X-Spam-Status: No, score=-17.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 FosIynQd5PdA for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 15:16:19 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9234D1A88C2 for <dhcwg@ietf.org>; Fri, 10 Oct 2014 15:16:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3112; q=dns/txt; s=iport; t=1412979379; x=1414188979; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Me3gxIX+cXHIb8GIe0LUGuZFaGoCTPeHpX14VZD8LvA=; b=RkpeneOuhGUrYiYl1tmq9As0MnH6F0VPZlMAr2ynQ7qzOp3O5qJTRUoG FbDAAahV01rGxhjTf487oUsga1SJGnaKiGc9Kjja66YylFCLCDhR2aGK5 V7GWO1/M1KSKC1Wk0jgLBO5P56YxeGp75IouRmhSZ43PwbVB1wBTmCIC6 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAGlaOFStJA2J/2dsb2JhbABGGoMOU1MFBIMCyCGHTQIZbBYBe4QDAQEBBCMRRQwEAgEIDgMEAQEBAgIGHQMCAgIfERQBCAgCBAENBQiIIgMRCAU3qkCNeQ2GaQEBAQEBAQEBAQEBAQEBAQEBAQEBAReBLItagQyCARYbBwaCcTaBHgWReYRChH+De41TA4ZRg3dsAROBNIECAQEB
X-IronPort-AV: E=Sophos;i="5.04,695,1406592000"; d="scan'208";a="362384202"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-6.cisco.com with ESMTP; 10 Oct 2014 22:16:19 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9AMGIYJ025445 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 10 Oct 2014 22:16:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Fri, 10 Oct 2014 17:16:18 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Karl Auer <kauer@biplane.com.au>, RFC Errata System <rfc-editor@rfc-editor.org>
Thread-Topic: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
Thread-Index: AQHP5M9VJeaR0oFOykC47A75UQEqQpwqNigA//+uopA=
Date: Fri, 10 Oct 2014 22:16:18 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6C3939@xmb-rcd-x04.cisco.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl>
In-Reply-To: <1412978590.20084.363.camel@karl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.253.37]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/7tGNdIAdrJLOOVcSRDWKdV4Gflc
Cc: "brian@innovationslab.net" <brian@innovationslab.net>, "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "burcak@juniper.net" <burcak@juniper.net>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 10 Oct 2014 22:16:22 -0000

WWVzLCBJIGZvcmdvdCB0byBmaXggdGhhdCBiZWZvcmUgaGl0dGluZyBzdWJtaXQgYW5kIHRoZXJl
IGlzIG5vIHdheSB0byBlZGl0LiAoSSB0aGluayBhIHNob3VsZCBiZSB0aGUgdG9vLikNCg0KSSBs
aWtlIHlvdSBjaGFuZ2UsIHNvIHRoZSAybmQgcGFyYWdyYXBoIGNvdWxkIGJlOg0KDQoJVGhlIEtl
cmJlcm9zIFJlYWxtIG5hbWUgTVVTVCB1c2UgdGhlIGRvbWFpbiBzdHlsZSByZWFsbSBuYW1lDQog
ICAJZGVzY3JpYmVkIGluIFJGQyAxNTEwIFs1XS4gVGhpcyByZWFsbSBuYW1lIE1VU1QgYmUgZW5j
b2RlZCBhcw0KCWRlc2NyaWJlZCBpbiBSRkMgMTAzNSBbM10gc2VjdGlvbiAzLjEsIHdpdGggdGhl
IGFkZGl0aW9uYWwgY29uc3RyYWludA0KCXRoYXQgYW55IGxldHRlcnMgaW4gdGhlIHJlYWxtIG5h
bWUgTVVTVCBiZSBpbiB1cHBlciBjYXNlLg0KDQpJIGRvbid0IHVuZGVyc3RhbmQgd2h5IGl0IHB1
dCB0aGUgIlJGQ0NPUlJFQ1RFRCIgaW4gdGhlcmUuIFRoZSBvbmxpbmUgdmVyc2lvbiAoVVJMKSBp
cyBjb3JyZWN0LiAgU2VlIGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvZXJyYXRhX3NlYXJjaC5w
aHA/cmZjPTM0OTUmZWlkPTQxMjg6DQoNCglUaHVzLCB0aGUgcmVhbG0gIkJBU0lDLjEiIGlzIGVu
Y29kZWQgYXMgIlwwMDVCQVNJQ1wwMDExXDAwMCIuDQoNCi0gQmVybmllDQoNCi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBLYXJsIEF1ZXIgW21haWx0bzprYXVlckBiaXBsYW5lLmNv
bS5hdV0gDQpTZW50OiBGcmlkYXksIE9jdG9iZXIgMTAsIDIwMTQgNjowMyBQTQ0KVG86IFJGQyBF
cnJhdGEgU3lzdGVtDQpDYzogYnVyY2FrQGp1bmlwZXIubmV0OyBQYXVsIER1ZmZ5IChwYWR1ZmZ5
KTsgYnJpYW5AaW5ub3ZhdGlvbnNsYWIubmV0OyB0ZWQubGVtb25Abm9taW51bS5jb207IEJlcm5p
ZSBWb2x6ICh2b2x6KTsgdG9tYXN6Lm1ydWdhbHNraUBnbWFpbC5jb207IGRoY3dnQGlldGYub3Jn
DQpTdWJqZWN0OiBSZTogW2RoY3dnXSBbRWRpdG9yaWFsIEVycmF0YSBSZXBvcnRlZF0gUkZDMzQ5
NSAoNDEyOCkNCg0KT24gRnJpLCAyMDE0LTEwLTEwIGF0IDE0OjE0IC0wNzAwLCBSRkMgRXJyYXRh
IFN5c3RlbSB3cm90ZToNCj4gVGhlIGZvbGxvd2luZyBlcnJhdGEgcmVwb3J0IGhhcyBiZWVuIHN1
Ym1pdHRlZCBmb3IgUkZDMzQ5NSwgIkR5bmFtaWMgDQo+IEhvc3QgQ29uZmlndXJhdGlvbiBQcm90
b2NvbCAoREhDUCkgT3B0aW9uIGZvciBDYWJsZUxhYnMgQ2xpZW50IENvbmZpZ3VyYXRpb24iLg0K
DQpUaGUgZmlyc3Qgc2VudGVuY2Ugb2YgdGhlIHNlY29uZCBwYXJhZ3JhcGggb2YgdGhlIGNvcnJl
Y3RlZCB0ZXh0IGlzIGJyb2tlbi4gSXQgbG9va3MgYXMgaWYgdGhlIHdvcmQgImJlIiBzaG91bGQg
YmUgcmVtb3ZlZC4NCg0KVGhlIHNhbWUgc2VudGVuY2Ugc2hvdWxkIGFsc28gY29udGFpbiB0aGUg
d29yZCAiYXMiIGltbWVkaWF0ZWx5IGJlZm9yZSB0aGUgd29yZCAiZGVzY3JpYmVkIi4NCg0KUkZD
IDEwMzUgc2VjdGlvbiAzLjEgZG9lc24ndCBtYW5kYXRlIGNhcGl0YWwgbGV0dGVycywgc28gSSBz
dWdnZXN0IHRoYXQgdGhlIHNlY29uZCBzZW50ZW5jZSBvZiB0aGUgc2Vjb25kIHBhcmFncmFwaCBv
ZiB0aGUgY29ycmVjdGVkIHRleHQgYmUgc29tZXRoaW5nIGxpa2U6ICJUaGlzIHJlYWxtIG5hbWUg
TVVTVCBiZSBlbmNvZGVkIGFzIGRlc2NyaWJlZCBpbiBSRkMNCjEwMzUgWzNdIHNlY3Rpb24gMy4x
LCB3aXRoIHRoZSBhZGRpdGlvbmFsIGNvbnN0cmFpbnQgdGhhdCBhbnkgbGV0dGVycyBpbiB0aGUg
cmVhbG0gbmFtZSBNVVNUIGJlIGluIHVwcGVyIGNhc2UuIg0KIA0KVGhlIGV4YW1wbGUgZW5jb2Rp
bmcgbG9va3Mgd3JvbmcsIGJ1dCBtYXliZSBJIGRpZG4ndCBkaWcgZGVlcCBlbm91Z2guIElzIHRo
ZSBsaXRlcmFsIHN0cmluZyAiUkZDQ09SUkVDVEVEIiByZWFsbHkgcGFydCBvZiB0aGUgZW5jb2Rp
bmc/DQoNClJlZ2FyZHMsIEsuDQoNCi0tDQp+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+
fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fg0KS2FybCBBdWVyIChrYXVl
ckBiaXBsYW5lLmNvbS5hdSkNCmh0dHA6Ly93d3cuYmlwbGFuZS5jb20uYXUva2F1ZXINCmh0dHA6
Ly90d2l0dGVyLmNvbS9rYXVlcjM4OQ0KDQpHUEcgZmluZ2VycHJpbnQ6IEVDNjcgNjFFMiBDMkY2
IEVCNTUgODg0QiBFMTI5IDA3MkIgMEFGMCA3MkFBIDk4ODIgT2xkIGZpbmdlcnByaW50OiBCODYy
IEZCMTUgRkU5NiA0OTYxIEJDNjIgMUE0MCA2MjM5IDEyMDggOTg2NSA1RjlBDQoNCg0K


From nobody Fri Oct 10 15:17:02 2014
Return-Path: <kauer@biplane.com.au>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A90C01A884D for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 15:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 EopcwKIO24-n for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 15:03:15 -0700 (PDT)
Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 3A5E51AD43C for <dhcwg@ietf.org>; Fri, 10 Oct 2014 15:03:14 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwBAHBWOFSWZX+7/2dsb2JhbAANU4NhUwWDBsgdh1ECgRsBhH8BAQQjVhALGAICJgICVwYTiEapfXiUcQEBAQEBAQQBAQEBAR2BLItagz4HgneBVAWWO4h6jVaIX4F9WIJKAQEB
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.196]) ([150.101.127.187]) by ipmail06.adl6.internode.on.net with ESMTP; 11 Oct 2014 08:33:12 +1030
Message-ID: <1412978590.20084.363.camel@karl>
From: Karl Auer <kauer@biplane.com.au>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Date: Sat, 11 Oct 2014 09:03:10 +1100
In-Reply-To: <20141010211437.8FD73181C86@rfc-editor.org>
References: <20141010211437.8FD73181C86@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4-0ubuntu2 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/4atT42RMH0gJxN9-NLYQ9TEAgYQ
X-Mailman-Approved-At: Fri, 10 Oct 2014 15:16:48 -0700
Cc: brian@innovationslab.net, volz@cisco.com, paduffy@cisco.com, burcak@juniper.net, ted.lemon@nominum.com, dhcwg@ietf.org
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 10 Oct 2014 22:03:18 -0000

On Fri, 2014-10-10 at 14:14 -0700, RFC Errata System wrote:
> The following errata report has been submitted for RFC3495,
> "Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration".

The first sentence of the second paragraph of the corrected text is
broken. It looks as if the word "be" should be removed.

The same sentence should also contain the word "as" immediately before
the word "described".

RFC 1035 section 3.1 doesn't mandate capital letters, so I suggest that
the second sentence of the second paragraph of the corrected text be
something like: "This realm name MUST be encoded as described in RFC
1035 [3] section 3.1, with the additional constraint that any letters in
the realm name MUST be in upper case."
 
The example encoding looks wrong, but maybe I didn't dig deep enough. Is
the literal string "RFCCORRECTED" really part of the encoding?

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: EC67 61E2 C2F6 EB55 884B E129 072B 0AF0 72AA 9882
Old fingerprint: B862 FB15 FE96 4961 BC62 1A40 6239 1208 9865 5F9A



From nobody Fri Oct 10 15:20:17 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB311AD455 for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 15:20:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.686
X-Spam-Level: 
X-Spam-Status: No, score=-4.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 tTsEz49MK3ET for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 15:19:52 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 759A81AD3EF for <dhcwg@ietf.org>; Fri, 10 Oct 2014 15:19:47 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4E8581B8541 for <dhcwg@ietf.org>; Fri, 10 Oct 2014 15:19:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 3628C53E081; Fri, 10 Oct 2014 15:19:47 -0700 (PDT)
Received: from [10.0.0.9] (71.194.230.170) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 10 Oct 2014 15:19:46 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <1412978590.20084.363.camel@karl>
Date: Fri, 10 Oct 2014 17:19:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl>
To: Karl Auer <kauer@biplane.com.au>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.194.230.170]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/k0xmTomzAOwBst6kOAKJdCdX9iE
Cc: Brian Haberman <brian@innovationslab.net>, Bernie Volz <volz@cisco.com>, paduffy@cisco.com, burcak@juniper.net, dhcwg@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 10 Oct 2014 22:20:07 -0000

On Oct 10, 2014, at 5:03 PM, Karl Auer <kauer@biplane.com.au> wrote:
> On Fri, 2014-10-10 at 14:14 -0700, RFC Errata System wrote:
>> The following errata report has been submitted for RFC3495,
>> "Dynamic Host Configuration Protocol (DHCP) Option for CableLabs =
Client Configuration".
>=20
> The first sentence of the second paragraph of the corrected text is
> broken. It looks as if the word "be" should be removed.
>=20
> The same sentence should also contain the word "as" immediately before
> the word "described".
>=20
> RFC 1035 section 3.1 doesn't mandate capital letters, so I suggest =
that
> the second sentence of the second paragraph of the corrected text be
> something like: "This realm name MUST be encoded as described in RFC
> 1035 [3] section 3.1, with the additional constraint that any letters =
in
> the realm name MUST be in upper case."
>=20
> The example encoding looks wrong, but maybe I didn't dig deep enough. =
Is
> the literal string "RFCCORRECTED" really part of the encoding?

RFC 1510 does mandate capital letters, so I think that base is covered.  =
 I agree with Bernie that the text here doesn't draw the reader's =
attention to the fact that the encoding is DNS wire format.   Bernie, =
can you send me corrected text?   I don't think you need to give an =
actual example, just make it clear that it's DNS wire format.   =
Unfortunately I think without updating this RFC, it's unlikely that =
anybody who would miss this detail would not fail to miss the erratum.   =
So let's keep the erratum tight and not try to add a ton of new text.


From nobody Fri Oct 10 16:01:59 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A465A1AD496 for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 16:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.287
X-Spam-Level: 
X-Spam-Status: No, score=-17.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 wUdKNM-o4G1K for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 16:01:57 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0E2F1AD495 for <dhcwg@ietf.org>; Fri, 10 Oct 2014 16:01:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2285; q=dns/txt; s=iport; t=1412982117; x=1414191717; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+TuisVUFt01xrh3Jw624O9KArME2BAOgQxOPYJuGaYw=; b=Lj4VAa43GpT4PrIUChYpoKvF8FlkJGU97uzIiV+L1faGS/e/cgWkxP48 LYDaWnXUGkE/TfA8ueJSh327GWj6i7SMUnSKN6JKve0k2Mw/ldxqgA3pz FtqzP0Wx1x5YKoL1LbIsma0AkYwmrLkE6cMvZTPy/rtFXrYPVI7B/CV/U 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAEVkOFStJA2K/2dsb2JhbABggw6BKwTScAKBAxYBe4QDAQEBBDo/DAQCAQgRBAEBAQoUCQcyFAkIAgQBDQUIiDa/dwEBAQEBAQEBAQEBAQEBAQEBAQEBAReNBoJbMjEHBoMngR4BBIRijReJAJhjg3dsgUiBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,695,1406592000"; d="scan'208";a="85966513"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-5.cisco.com with ESMTP; 10 Oct 2014 23:01:56 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s9AN1tME027248 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 10 Oct 2014 23:01:55 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0195.001; Fri, 10 Oct 2014 18:01:55 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Karl Auer <kauer@biplane.com.au>
Thread-Topic: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
Thread-Index: AQHP5M9VJeaR0oFOykC47A75UQEqQpwqNigAgAAEoQD//7eE0A==
Date: Fri, 10 Oct 2014 23:01:54 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com>
In-Reply-To: <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.253.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/ZwFp4p1cdxfoZvw3ik7O4OuFY8w
Cc: Brian Haberman <brian@innovationslab.net>, "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "burcak@juniper.net" <burcak@juniper.net>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 10 Oct 2014 23:01:58 -0000

While the extra text about an example isn't required, I think it serves a u=
seful purpose to assure people understand how it is encoded. But if you fee=
l we should not include it, I am fine with dropping it.

I don't know how to edit the ERRATA. Is this something that requires you're=
 doing? Or?

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Friday, October 10, 2014 6:20 PM
To: Karl Auer
Cc: RFC Errata System; burcak@juniper.net; Paul Duffy (paduffy); Brian Habe=
rman; Bernie Volz (volz); Tomek Mrugalski; dhcwg@ietf.org
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)

On Oct 10, 2014, at 5:03 PM, Karl Auer <kauer@biplane.com.au> wrote:
> On Fri, 2014-10-10 at 14:14 -0700, RFC Errata System wrote:
>> The following errata report has been submitted for RFC3495, "Dynamic=20
>> Host Configuration Protocol (DHCP) Option for CableLabs Client Configura=
tion".
>=20
> The first sentence of the second paragraph of the corrected text is=20
> broken. It looks as if the word "be" should be removed.
>=20
> The same sentence should also contain the word "as" immediately before=20
> the word "described".
>=20
> RFC 1035 section 3.1 doesn't mandate capital letters, so I suggest=20
> that the second sentence of the second paragraph of the corrected text=20
> be something like: "This realm name MUST be encoded as described in=20
> RFC
> 1035 [3] section 3.1, with the additional constraint that any letters=20
> in the realm name MUST be in upper case."
>=20
> The example encoding looks wrong, but maybe I didn't dig deep enough.=20
> Is the literal string "RFCCORRECTED" really part of the encoding?

RFC 1510 does mandate capital letters, so I think that base is covered.   I=
 agree with Bernie that the text here doesn't draw the reader's attention t=
o the fact that the encoding is DNS wire format.   Bernie, can you send me =
corrected text?   I don't think you need to give an actual example, just ma=
ke it clear that it's DNS wire format.   Unfortunately I think without upda=
ting this RFC, it's unlikely that anybody who would miss this detail would =
not fail to miss the erratum.   So let's keep the erratum tight and not try=
 to add a ton of new text.


From nobody Sat Oct 11 07:32:54 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 977541A1B84 for <dhcwg@ietfa.amsl.com>; Sat, 11 Oct 2014 07:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 ihqQlQHVKhvk for <dhcwg@ietfa.amsl.com>; Sat, 11 Oct 2014 07:32:50 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0BC21A1B68 for <dhcwg@ietf.org>; Sat, 11 Oct 2014 07:32:50 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 936361B85A0 for <dhcwg@ietf.org>; Sat, 11 Oct 2014 07:32:50 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 7289353E081; Sat, 11 Oct 2014 07:32:50 -0700 (PDT)
Received: from [10.0.0.9] (71.194.230.170) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sat, 11 Oct 2014 07:32:50 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com>
Date: Sat, 11 Oct 2014 09:32:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <7368350B-7786-469D-827D-516A786251F5@nominum.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.194.230.170]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/3MRWFOFgwzxflgaqLXzVOBJxfL4
Cc: Brian Haberman <brian@innovationslab.net>, "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "burcak@juniper.net" <burcak@juniper.net>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 11 Oct 2014 14:32:51 -0000

On Oct 10, 2014, at 6:01 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> While the extra text about an example isn't required, I think it =
serves a useful purpose to assure people understand how it is encoded. =
But if you feel we should not include it, I am fine with dropping it.
>=20
> I don't know how to edit the ERRATA. Is this something that requires =
you're doing? Or?

I can do the editing.   The point is that adding a lot of text in an =
erratum isn't really kosher.  An erratum is supposed to be pointing out =
an error in a document, not updating the document.   This is borderline, =
since what you are reporting isn't an error, just a lack of explicitness =
that might result in someone doing the implementation wrong.

If the document needs updated, you update it.

Personally, I think if you really care about addressing this problem, we =
should just quickly respin the document, because people hardly ever look =
at errata anyway.


From nobody Sat Oct 11 19:04:51 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 505B51A6FEB for <dhcwg@ietfa.amsl.com>; Sat, 11 Oct 2014 19:04:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.686
X-Spam-Level: 
X-Spam-Status: No, score=-14.686 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, J_CHICKENPOX_41=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 MGRMEkupYlkM for <dhcwg@ietfa.amsl.com>; Sat, 11 Oct 2014 19:04:45 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C30461A6F84 for <dhcwg@ietf.org>; Sat, 11 Oct 2014 19:04:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=33583; q=dns/txt; s=iport; t=1413079486; x=1414289086; h=from:to:subject:date:message-id:mime-version; bh=gRzIFadjlM4+mX2EhMdME3B2yWp7JxH5ICbZdf8/d50=; b=ZgRb2ju/eL/uIoA8zIFbpwwkKFk+KPw77yx57QLtqmovHECZuLW4fxjF QUoGX7oA+jjzlipCzw7h7YjelaQbodNM2Cz5fRQmNKCrRO5YNjYL94jnp pDh601uOClWn6RpmuUK41qlC0Jfc4M/+MDvuztjs7x6cKPJtnqwlBlCUT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au8FAB/hOVStJA2I/2dsb2JhbABZgkhGU1zJMYFth00CgQUWAXILhAIBAQEEDCFeAQgRBAEBCxYBBjkUCQkBBBMIiDYNnACkJAEBAQEBAQEBAgEBAQEBAQEBGopLgjyDDTcHgyeBHgWReYRCiD48gwqHYIU/g36Dd2yBSIECAQEB
X-IronPort-AV: E=Sophos;i="5.04,702,1406592000";  d="scan'208,217";a="362565939"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-5.cisco.com with ESMTP; 12 Oct 2014 02:04:44 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s9C24gVo031993 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sun, 12 Oct 2014 02:04:42 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Sat, 11 Oct 2014 21:04:42 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
Thread-Index: Ac/luOxHol1wGKq6TYi1U8lB1WWGaA==
Date: Sun, 12 Oct 2014 02:04:42 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6C63E0@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.195]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6C63E0xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/IAxMAtTI2miFn0Cm-BgfnmetJ9k
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 12 Oct 2014 02:04:50 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6C63E0xmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Below are my review comments. I think with these applied, the document shou=
ld be able to move forward (I support this work and do feel it should be ab=
le to advance) - however, given the lack of response for this Working Group=
 Last Call, it may need another. For those that support this work but have =
not yet commented, you have until the end of (your) day, Oct 13.

** General

-          Minor: There are many contractions in this document (can't, it's=
, ...). While these will be fixed by the RFC editor, best to clean them up.=
 I think the general goal is to avoid these (cannot, it is, ...). Of course=
, leave any possessive words.
** Section 2

-          Very minor: For "PE router: Provider Edge Router" wonder why not

-           just "provider edge router" as for CPE (i.e., check case).
** Section 3

-          Figure 1 title - I guess "simple" this isn't, but not sure what =
else to call it. Perhaps "Smaller hierarchical Network"?

-          After Figure 2, the paragraph starts with "This diagram" ... whi=
ch is this referring to? Perhaps both (These diagrams?) "This diagram" is a=
lso used in the next paragraph (top of page 6).

-          3rd paragraph on page 6: - "In DHCPv6 that is also possible is c=
ase[s]". Also, in this sentence, can we replace the "it" at the end of the =
sentence - use "unicast"?

-          Next sentence, "In such case[s,] once the ... to contact [the] s=
erver".

-          General comment on this paragraph, is the unicast decision here =
really worth it? Would be a lot simpler to just say "In DHCPv6, it is possi=
ble for the server to indicate to the client that it may unicast packets un=
der appropriate conditions (see RFC 3315, such as Section 22.12)."

-          Next paragraph, perhaps best to avoid "on-link"? How about "that=
 it knows is [on the] link to which the client is connected:".

-          And in the last sentence of this paragraph, the is missing ... "=
and select the appropriate subnet".

-          The discussion about interface-id on bottom of page 6/top of pag=
e 7 is a bit incorrect in that an interface-id may always be included - it =
is not just included it the link-address is not set. Also, a server could i=
gnore a link-address and use the interface-id. I'm also wondering if this e=
ntire interface-id discussion is worth it since this isn't really what this=
 draft is mostly about? Again, may be worth just to point out that other te=
chniques can be used by a server to select the prefixes from which to assig=
n address/delegate prefixes? (Technically I'm not sure 22.18 of 3315 permit=
s this - the text just says "Servers MAY use the Interface-ID for parameter=
 assignment policies." But I am less concerned about this as I don't think =
it matters what special purpose servers may do/permit.

-          I also believe the text regarding LDRA is incorrect - "in additi=
on to receiving an IPv6 address that is on-link for the link"? Huh? The LDR=
A relay sets the link-address to the "Unspecified_Address" (there is the pe=
er-address, but that is a link-local address and is the same as for non-LDR=
As).

-          Page 7, start of first full paragraph - "For completeless" shoul=
d b "For completeness".

-          At the bottom of page 7, the paragraph beings "In all cases, the=
n, the DHCP server will a link-identifying IP address" ... I think the earl=
ier text missed the case where there is no relay? In that case, the server =
would likely use the address of the interface on which the request packet w=
as received?

-          I'm also not sure what the value (at least for this work) of int=
roducing RFC 6977 is - as that deals with relay-agent to server communicati=
on.

-          Also, it seems the DHCPv4 case wasn't really covered here. GIADD=
R isn't mentioned until section 6??
** Section 4

-          For the JSON notation, is it worth to provide some kind of refer=
ence? There is RFC 7159 that defines this format.
** Section 5

-          The first 2 paragraphs should probably start with "[A] relay age=
nt ...".

-          Minor - perhaps add v6/v4 - "link-local multicast [v6] or broadc=
asts [v4]"?

-          Last paragraph/sentence, change "legal" to "a valid"? (If you le=
ave legal, a should be added before it.)
** Section 6

-          First paragraph, 1st sentence add a comma between "case, shown".

-          2nd sentence - "Not that in [this] configuration"?

-          2nd paragraph, "[The] server will send the response".

-          3rd paragraph, "Depending on the configuration[,] that can be [a=
] server's".

-          Also, "32 levels of encapsulation if [the packet] traveled".
** Section 7

-          "In this example"? Which? I think this is for Figure 2? So, "In =
Figure 2,".
** Section 9

-          2nd paragraph, "of certains optons" should be "of certain option=
s".


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Monday, September 29, 2014 10:36 AM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct =
13, 2014


Hi all,



This message starts the DHC working group last call to advance "Customizing=
 DHCP Configuration on the Basis of Network Topology", draft-ietf-dhc-topo-=
conf-03, document as an Informational RFC. The authors believe that this ve=
rsion is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-topo-conf-03



Please send your comments by October 13th, 2014. If you do not feel this do=
cument should advance, please state your reasons why.



There are no IPR claims reported at this time.



Bernie Volz is the assigned shepherd for this document.



- Tomek & Bernie


--_000_489D13FBFA9B3E41812EA89F188F018E1B6C63E0xmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1643539160;
	mso-list-type:hybrid;
	mso-list-template-ids:-1440742188 -1484986110 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:1035;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1681926332;
	mso-list-type:hybrid;
	mso-list-template-ids:1197214778 -380618802 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:1035;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2
	{mso-list-id:1942294490;
	mso-list-type:hybrid;
	mso-list-template-ids:-793881586 -343234972 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l2:level1
	{mso-level-start-at:1035;
	mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Below are my review co=
mments. I think with these applied, the document should be able to move for=
ward (I support this work and do feel it should be able to advance) &#8211;=
 however, given the lack of response for this
 Working Group Last Call, it may need another. <b>For those that support th=
is work but have not yet commented, you have until the end of (your) day, O=
ct 13.<o:p></o:p></b></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">** General<o:p></o:p><=
/span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Minor: There a=
re many contractions in this document (can&#8217;t, it&#8217;s, &#8230;). W=
hile these will be fixed by the RFC editor, best to clean them up. I think =
the general goal is to avoid these (cannot, it is, &#8230;).
 Of course, leave any possessive words.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">** Section 2<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Very minor: Fo=
r &#8220;PE router: Provider Edge Router&#8221; wonder why not<o:p></o:p></=
span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">&nbsp;just &#8=
220;provider edge router&#8221; as for CPE (i.e., check case).<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">** Section 3<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Figure 1 title=
 &#8211; I guess &#8220;simple&#8221; this isn&#8217;t, but not sure what e=
lse to call it. Perhaps &#8220;Smaller hierarchical Network&#8221;?<o:p></o=
:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">After Figure 2=
, the paragraph starts with &#8220;This diagram&#8221; &#8230; which is thi=
s referring to? Perhaps both (These diagrams?) &#8220;This diagram&#8221; i=
s also used in the next paragraph (top of page 6).<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">3<sup>rd</sup>=
 paragraph on page 6: - &#8220;In DHCPv6 that is also possible is case[s]&#=
8221;. Also, in this sentence, can we replace the &#8220;it&#8221; at the e=
nd of the sentence &#8211; use &#8220;unicast&#8221;?<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Next sentence,=
 &#8220;In such case[s,] once the &#8230; to contact [the] server&#8221;.<o=
:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">General commen=
t on this paragraph, is the unicast decision here really worth it? Would be=
 a lot simpler to just say &#8220;In DHCPv6, it is possible for the server =
to indicate to the client that it may unicast
 packets under appropriate conditions (see RFC 3315, such as Section 22.12)=
.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Next paragraph=
, perhaps best to avoid &#8220;on-link&#8221;? How about &#8220;that it kno=
ws is [on the] link to which the client is connected:&#8221;.<o:p></o:p></s=
pan></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">And in the las=
t sentence of this paragraph, the is missing &#8230; &#8220;and select the =
appropriate subnet&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">The discussion=
 about interface-id on bottom of page 6/top of page 7 is a bit incorrect in=
 that an interface-id may always be included &#8211; it is not just include=
d it the link-address is not set. Also,
 a server could ignore a link-address and use the interface-id. I&#8217;m a=
lso wondering if this entire interface-id discussion is worth it since this=
 isn&#8217;t really what this draft is mostly about? Again, may be worth ju=
st to point out that other techniques can be
 used by a server to select the prefixes from which to assign address/deleg=
ate prefixes? (Technically I&#8217;m not sure 22.18 of 3315 permits this &#=
8211; the text just says &#8220;</span><span style=3D"font-family:&quot;Cou=
rier New&quot;,&quot;serif&quot;">Servers MAY use the Interface-ID for para=
meter
 assignment policies.</span><span style=3D"color:#1F497D">&#8221; But I am =
less concerned about this as I don&#8217;t think it matters what special pu=
rpose servers may do/permit.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">I also believe=
 the text regarding LDRA is incorrect &#8211; &#8220;in addition to receivi=
ng an IPv6 address that is on-link for the link&#8221;? Huh? The LDRA relay=
 sets the link-address to the &#8220;Unspecified_Address&#8221;
 (there is the peer-address, but that is a link-local address and is the sa=
me as for non-LDRAs).<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Page 7, start =
of first full paragraph - &#8220;For completeless&#8221; should b &#8220;Fo=
r completeness&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">At the bottom =
of page 7, the paragraph beings &#8220;In all cases, then, the DHCP server =
will a link-identifying IP address&#8221; &#8230; I think the earlier text =
missed the case where there is no relay? In that case,
 the server would likely use the address of the interface on which the requ=
est packet was received?<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">I&#8217;m also=
 not sure what the value (at least for this work) of introducing RFC 6977 i=
s &#8211; as that deals with relay-agent to server communication.
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Also, it seems=
 the DHCPv4 case wasn&#8217;t really covered here. GIADDR isn&#8217;t menti=
oned until section 6??<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">** Section 4<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">For the JSON n=
otation, is it worth to provide some kind of reference? There is RFC 7159 t=
hat defines this format.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">** Section 5<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">The first 2 pa=
ragraphs should probably start with &#8220;[A] relay agent &#8230;&#8221;.<=
o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Minor &#8211; =
perhaps add v6/v4 &#8211; &#8220;link-local multicast [v6] or broadcasts [v=
4]&#8221;?<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Last paragraph=
/sentence, change &#8220;legal&#8221; to &#8220;a valid&#8221;? (If you lea=
ve legal, a should be added before it.)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">** Section 6<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">First paragrap=
h, 1<sup>st</sup> sentence add a comma between &#8220;case, shown&#8221;.<o=
:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">2<sup>nd</sup>=
 sentence &#8211; &#8220;Not that in [this] configuration&#8221;?
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">2<sup>nd</sup>=
 paragraph, &#8220;[The] server will send the response&#8221;.<o:p></o:p></=
span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">3<sup>rd</sup>=
 paragraph, &#8220;Depending on the configuration[,] that can be [a] server=
&#8217;s&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Also, &#8220;3=
2 levels of encapsulation if [the packet] traveled&#8221;.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">** Section 7<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">&#8220;In this=
 example&#8221;? Which? I think this is for Figure 2? So, &#8220;In Figure =
2,&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">** Section 9<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">2<sup>nd</sup>=
 paragraph, &#8220;of certains optons&#8221; should be &#8220;of certain op=
tions&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Monday, September 29, 2014 10:36 AM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond =
by Oct 13, 2014<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Hi all,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This message starts the DHC working group last ca=
ll to advance &quot;Customizing DHCP Configuration on the Basis of Network =
Topology&#8221;, draft-ietf-dhc-topo-conf-03, document as an Informational =
RFC. The authors believe that this version is
 ready.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The draft is available here:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"http://tools.ietf.org/html/draft-ietf-=
dhc-topo-conf-03">http://tools.ietf.org/html/draft-ietf-dhc-topo-conf-03</a=
><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please send your comments by October 13th, 2014. =
If you do not feel this document should advance, please state your reasons =
why.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There are no IPR claims reported at this time.<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bernie Volz is the assigned shepherd for this doc=
ument.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6C63E0xmbrcdx04ciscoc_--


From nobody Sun Oct 12 19:13:39 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9111A9235 for <dhcwg@ietfa.amsl.com>; Sun, 12 Oct 2014 19:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.286
X-Spam-Level: 
X-Spam-Status: No, score=-15.286 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ivNy9cbmzB1v for <dhcwg@ietfa.amsl.com>; Sun, 12 Oct 2014 19:13:35 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB5031A9234 for <dhcwg@ietf.org>; Sun, 12 Oct 2014 19:13:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4423; q=dns/txt; s=iport; t=1413166415; x=1414376015; h=from:to:subject:date:message-id:mime-version; bh=YiGPWn6uBs3UEIiXzy1JCF/pAbrk4I4oKv1FpUzV3DQ=; b=KE/UPO7Flubs9P2NHOPiwCrfWko0J7kuDvNgAPqJK4Ly3iFct5Aehr7s K2hqyu+2tXKb6wJQtjz9/iili6hm4S3h5FtsQTe8b7IMJKFWRRPMxxgo0 a0Cagod4bCprg1UVC7JaLshd4Q59ChTbA/ljJYM65Jl/HtgCH41X8WIsY E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoFAD40O1StJV2a/2dsb2JhbABbgkhGU1kDyReBb4dLAoEOFgFyC4QEAQQtXgEqViYBBBuINg2fD6QVAQEBAQYBAQEBAR2NB4MNg2WBHgWReYRCiD48gwqHYIU/g36CNIFDgjSBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,707,1406592000";  d="scan'208,217";a="362715506"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP; 13 Oct 2014 02:13:35 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s9D2DZOK012145 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Mon, 13 Oct 2014 02:13:35 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Sun, 12 Oct 2014 21:13:34 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
Thread-Index: Ac/minMIxUbYwkSiQNCrNLgZzh2MnQ==
Date: Mon, 13 Oct 2014 02:13:34 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.195]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6C78C7xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/wf7VpS2tB5VrPdccu8AH56-eXbk
Subject: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 13 Oct 2014 02:13:37 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6C78C7xmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,



This message starts the DHC working group last call to advance "Dynamic All=
ocation of Shared IPv4 Addresses", draft-ietf-dhc-dynamic-shared-v4allocati=
on-02, document as a Standards Track (Proposed Standard) RFC. The authors b=
elieve that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-02



Please send your comments by October 27th, 2014. If you do not feel this do=
cument should advance, please state your reasons why.



There are no IPR claims reported at this time.



Bernie Volz is the currently assigned shepherd for this document.



- Tomek & Bernie


--_000_489D13FBFA9B3E41812EA89F188F018E1B6C78C7xmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hi all,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This message starts the DHC working group last ca=
ll to advance &quot;Dynamic Allocation of Shared IPv4 Addresses&quot;, draf=
t-ietf-dhc-dynamic-shared-v4allocation-02, document as a Standards Track (P=
roposed Standard) RFC. The authors believe that
 this version is ready.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The draft is available here:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"http://tools.ietf.org/html/draft-ietf-=
dhc-dynamic-shared-v4allocation-02">http://tools.ietf.org/html/draft-ietf-d=
hc-dynamic-shared-v4allocation-02</a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please send your comments by October 27th, 2014. =
If you do not feel this document should advance, please state your reasons =
why.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There are no IPR claims reported at this time.<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bernie Volz is the currently assigned shepherd fo=
r this document.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6C78C7xmbrcdx04ciscoc_--


From nobody Mon Oct 13 04:51:03 2014
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE0361A8996 for <dhcwg@ietfa.amsl.com>; Mon, 13 Oct 2014 04:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 i96ulp75I3WY for <dhcwg@ietfa.amsl.com>; Mon, 13 Oct 2014 04:50:59 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C3081A8998 for <dhcwg@ietf.org>; Mon, 13 Oct 2014 04:50:59 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id em10so7189841wid.7 for <dhcwg@ietf.org>; Mon, 13 Oct 2014 04:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=elx7JCqVwND31bScpblthdfgFK0ldReYS4k/AZgYtT8=; b=qrZpHqEG74YBLCII0Vx0v5Yz+kYu0YRc5C0oR+dIwBFlGUZnj+bTuRge17VOdGeXBs kzSkV1eXoTBGgHpiEWUeLgd/w7iEz4OphO58otr8I0gzjlpuGhUUci9/yq/wc5NfeGbB XV1r6IEb1/9qpU+cXzDZ1YPmkRK32/fnnPOsLXh6VlJknG/erRhbqux71IG6+JUHNHqU 9K9aA+M8DmE4dvHxl2KLjgeUqhxGUOKo4XS1byfKUM0FTVTBa7ypRquFDenq1AdoS5h/ AgsJnqdPIlurTCKCEYHce+XrGq81MQfYPOvB+feo9jAiZbx7wBvi3yon6BlXP59TeAfZ gPIA==
X-Received: by 10.194.110.10 with SMTP id hw10mr2170998wjb.102.1413201058018;  Mon, 13 Oct 2014 04:50:58 -0700 (PDT)
Received: from [192.168.10.11] (89-79-26-47.dynamic.chello.pl. [89.79.26.47]) by mx.google.com with ESMTPSA id ji10sm11929620wid.7.2014.10.13.04.50.56 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Oct 2014 04:50:57 -0700 (PDT)
Message-ID: <543BBCA0.9010903@gmail.com>
Date: Mon, 13 Oct 2014 13:50:56 +0200
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1B6ABDD8@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6ABDD8@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/4Pf2ISozenzKLnT9ukKSOdv5QJI
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 13 Oct 2014 11:51:01 -0000

I have read the draft, I think it is useful work and I support it move
forward.

A couple of comments, mostly editorial. There is nothing really major.

Section 3: The title of this section sounds ambiguous. IMO, the better
name would be "Identifying Client's Location by DHCP servers". In case
you think the current name is better, I'd put a short paragraph
explaining the purpose of the whole section 3 at the beginning of this
section to provide a context for the analysis of the figures. Otherwise
I stare at the figures first without an understanding why I am doing it.

OLD:
"DHCP clients are assumed not to have routable IP addresses when they
are attempting to obtain configuration information".
NEW:
"It is assumed that DHCP clients may not have routable IP addresses when
they are attempting to obtain configuration information."

OLD:
"this relay agent, which has a routable IP address, then forwards the
DHCP requests to the DHCP server".
NEW:
"this relay agent, which has a routable IP address, then forwards the
DHCP requests to the DHCP server (directly or via other relays)".


The following statement:
"In DHCPv6 that is also possible in case where the server is configured
with a Server Unicast option and client's are able to take advantage of it."

contradicts with the assumption that clients don't have routable addres,
because they need to have a routable address to use unicast:

This is another reason why it should be said that the clients may not
have an routable IP address, rather than they don't have routable IP
address.


Since, the draft combines the use cases for DHCPv4 and DHCPv6 it is
sometimes not clear whether "DHCP server" refers to DHCPv4 server or
both DHCPv4 and DHCPv6. For example:

"In all cases, the DHCP server is able to obtain IP address that it
knows is on-link [...]".

>From the examples following the colon I understand that this is about
the DHCPv4 server. But, the use of DHCP term doesn't seem to be
consistent. In some cases the DHCP server refers to both. I'd suggest
that the "DHCP server" is used as a term for "any" server. And, DHCPv4
and DHCPv6 for respective servers. One may argue that RFC2131 defines a
DHCP protocol (not DHCPv4), but the use of terms could be cleared in the
topo-conf terminology.


Having said that, I think that section 3 would be far better readable if
it was split to 2 distinct sections. One for DHCPv4, another for DHCPv6.
Otherwise, the text jumps back and forth between the two contexts.

This paragraph sounds awkward:

"  In all cases, the DHCP server is able to obtain an IP address that it
   knows is on-link for the link to which the DHCP client is connected:
   either the DHCPv4 client's routable IPv4 address, or the relay
   agent's IPv4 address on the link to which the client is connected.
   So in every case the server is able to determine the client's point
   of attachment and select appropriate subnet- or link-specific
   configuration."

It would be better to say:

"  The DHCP server uses an IP address from the client's message which is
on the same link as the client to perform address assignment decisions
or to select subnet-specific configuration for the client. The address
that the server uses is the DHCP client's routable IP address or the
client facing address of the relay agent."

Or something similar. But the key is that the server extracts the IP
address for the purpose, and the purpose should be stated first. In the
original text is sounds like the ability to select a subnet or
link-specific configuration is a side effect of doing something else.


I'd remove the "Somewhat contrary to its name [...]". The name is the
name and it is not the intent of this draft to resolve issues with names
defined elsewhere.

I don't understand this: "In normal circumstances this is the solution
that is the easiest to maintain." In particular, I don't understand what
exact aspects of "maintenance" are the easiest here? Or, what the
maintenance is in this context?

Section 4: In the JSON example there is on-link["a"]. Shouldn't it be
on-link["A"] ?

Marcin




On 29/09/14 16:36, Bernie Volz (volz) wrote:
> Hi all,
> 
>  
> 
> This message starts the DHC working group last call to advance
> "Customizing DHCP Configuration on the Basis of Network Topology”,
> draft-ietf-dhc-topo-conf-03, document as an Informational RFC. The
> authors believe that this version is ready.
> 
>  
> 
> The draft is available here:
> 
> http://tools.ietf.org/html/draft-ietf-dhc-topo-conf-03
> 
>  
> 
> Please send your comments by October 13th, 2014. If you do not feel this
> document should advance, please state your reasons why.
> 
>  
> 
> There are no IPR claims reported at this time.
> 
>  
> 
> Bernie Volz is the assigned shepherd for this document.
> 
>  
> 
> - Tomek & Bernie
> 
>  
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 


From nobody Mon Oct 13 09:43:11 2014
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83B111A1B5A for <dhcwg@ietfa.amsl.com>; Mon, 13 Oct 2014 09:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 5iBZKVrH5Bl3 for <dhcwg@ietfa.amsl.com>; Mon, 13 Oct 2014 09:43:07 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19FE71A1B62 for <dhcwg@ietf.org>; Mon, 13 Oct 2014 09:43:04 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kq14so6201745pab.12 for <dhcwg@ietf.org>; Mon, 13 Oct 2014 09:43:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4mPOIcRkIJ2dYzU88JxuTC8mXaBEomSZXGkM1HTnTls=; b=oLmqFJmtVSPZ+T2aVlDeLKOmX3CuQo8/uqRJZ01Mfh8VIZBrJKgJDlkeug42ra6TH6 CNTLNcBXXFjvjrrFf2k+92XJqGVr4ENWwmkdp3ilTI9+Nw2um9TNmBFuasJeT7G7igQF idPEcviFUpZbwF80fe7SxhHtQoxHn4nUZcT1slo2i2fZI1MzNQxpfvXuiJ/trapnFAql 53Y3/xnuQUasF56C9VT05HZW4aDrtgzlMdmr8NfpnrVAQ0/DH19tChfdA+DTqjUs57y6 /WRObzeBIfsBP5Xz9sCFSUHU1bDvA1JrMis0KK8T7E+bndoZgAcfr7vrZMZ5B6sDenne ob9w==
X-Received: by 10.70.16.2 with SMTP id b2mr25032828pdd.36.1413218583592; Mon, 13 Oct 2014 09:43:03 -0700 (PDT)
Received: from [172.20.10.10] ([106.37.20.156]) by mx.google.com with ESMTPSA id al4sm9816398pbc.19.2014.10.13.09.42.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 Oct 2014 09:43:02 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <492C612A-D2F6-43D3-A33A-364AFB5BC7D9@cisco.com>
Date: Tue, 14 Oct 2014 00:42:30 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <25604FD4-3D9F-4C73-A0FD-05EA1028B617@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6ABDD8@xmb-rcd-x04.cisco.com> <492C612A-D2F6-43D3-A33A-364AFB5BC7D9@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/VGS3wvs0-Df4nf-a_JiCCSk0RI4
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 13 Oct 2014 16:43:09 -0000

Dear all,

I=92ve read this document and support its moving forward.

Here are some minor editorial comments:
1) Sec 2, Terminology
Should it be 'Shared subnet=92 or 'Shared subnets=92 ?

2) On Page 6,=20
OLD:
  In all cases, the DHCP server is able to obtain an IP address that it
  knows is on-link for the link to which the DHCP client is connected: =85=


Could I suggest s/obtain/identify/ ? The word =91obtain=92 might =
confuses the reader that the DHCP server is acquiring an IP address for =
itself.=20

Best Regards,
Qi

On Oct 7, 2014, at 11:07 AM, Bernie Volz (volz) <volz@cisco.com> wrote:

> Reminder that this WGLC is in progress and needs responses to advance. =
Please review and provide your support or reasons as to why you feel =
this is not ready yet or should never advance.
>=20
> - Bernie (from iPad)
>=20
> On Sep 29, 2014, at 10:36 AM, Bernie Volz (volz) <volz@cisco.com> =
wrote:
>=20
>> Hi all,
>> =20
>> This message starts the DHC working group last call to advance =
"Customizing DHCP Configuration on the Basis of Network Topology=94, =
draft-ietf-dhc-topo-conf-03, document as an Informational RFC. The =
authors believe that this version is ready.
>> =20
>> The draft is available here:
>> http://tools.ietf.org/html/draft-ietf-dhc-topo-conf-03
>> =20
>> Please send your comments by October 13th, 2014. If you do not feel =
this document should advance, please state your reasons why.
>> =20
>> There are no IPR claims reported at this time.
>> =20
>> Bernie Volz is the assigned shepherd for this document.
>> =20
>> - Tomek & Bernie
>> =20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Mon Oct 13 11:38:45 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2D81A87C5 for <dhcwg@ietfa.amsl.com>; Mon, 13 Oct 2014 11:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 FcEf2s66EYAX for <dhcwg@ietfa.amsl.com>; Mon, 13 Oct 2014 11:38:42 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC5FC1A87C1 for <dhcwg@ietf.org>; Mon, 13 Oct 2014 11:38:41 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id a1so9152375wgh.11 for <dhcwg@ietf.org>; Mon, 13 Oct 2014 11:38:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Qa8obmvh+IILOGlUuCLPQRRM8hJpk6bOGbCpHWXDPpA=; b=nyk4ICZHvOD7NgrPCiTtvEpz7yDoRDZZYslk8mVn8qpuQiNQXrc0dNvH3kOmRK44rc iG9KlqLmpWzEsEhcsaKvj6r60D9xHayM6pn+NoBKvzm6hKHVuL9khKm6Aa0eljc4V6vz IGUGieNeF23h8khGHRCxVFcXjmzW2MN93LjzYXQtglqcgyycYeoOVuPhORE0tbBD2ADH FLTS9Kra3yYchM/YCf5QIpQKhgEebls2R78b6UQNzdKyP74fpvq9Ury3/GD0KFebbuXD X/ISjVU/1135lttoTxKAMs8+MQSoLLuE85BrilFdWq8929PesJobgujS1EdXVGp7aeOU OnIQ==
MIME-Version: 1.0
X-Received: by 10.194.8.73 with SMTP id p9mr130575wja.87.1413225520323; Mon, 13 Oct 2014 11:38:40 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.195.13.83 with HTTP; Mon, 13 Oct 2014 11:38:40 -0700 (PDT)
In-Reply-To: <5433FCC3.70800@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6ABDD8@xmb-rcd-x04.cisco.com> <5433FCC3.70800@gmail.com>
Date: Mon, 13 Oct 2014 11:38:40 -0700
X-Google-Sender-Auth: g_ME5DcJahwZC1V9dhVMDhAtIRI
Message-ID: <CAJE_bqdRnk36bVAdJxzcfYbpxcA-AfiFiXoXJasEDmAvC4Uw_w@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/BJgJh7JFLAh9NNwl-wg1O-V1BnE
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 13 Oct 2014 18:38:43 -0000

At Tue, 07 Oct 2014 16:46:27 +0200,
Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:

> > Please send your comments by October 13th, 2014. If you do not feel this
> > document should advance, please state your reasons why.
> As a co-author, I support this I-D moving forward.
>
> This draft received quite a lot of reviews in its -01 version (thanks
> again). Can I ask people who did the review back then (Andre, Carsten,
> Simon, Jinmei and Suresh) to double check that all your comments were
> addressed?

Assuming you meant this:
http://www.ietf.org/mail-archive/web/dhcwg/current/msg15442.html
I've checked if these are addressed in the 03 version (I've not
(re-)reviewed entire text of the latest version, though).

Some of these comments don't seem to be addressed or may need some
update:

- My question on this sentence seems to still remain:

   [...]  It is
   up to administrator to make sure that the interface-id is unique
   within his administrative domain.

- Regarding this text:

   In all cases, then, the DHCP server will have a link-identifying IP
   address, and in some cases it may also have a link-specific
   identifier (e.g.  Interface-Id Option or Link Address Option defined
   in Section 5 of [RFC6977]).  It should be noted that there is no
   guarantee that the link-specific identifier will be unique outside
   the scope of the link-identifying IP address.

  My question on the second sentence seems to be still open.  Pasting
  it: 'The second sentence is also not really clear to me...what does
  "outside the scope of the link-identifying IP address" mean?
  Usually "the link-identifying IP address" should be global, so there
  is basically no "outside the scope" of it in the first place.'

- Regarding the comment on Section 8, I see an additional paragraph
  has been added, seemingly for addressing my comment.  I don't have
  an objection to the text itself, but the sense of the revised text
  is slightly different from what I would have envisioned.  I propose
  the following text instead:

   [...]  When changes
   are made to the DNS server, these changes are promptly and
   automatically adopted by the DHCP server, as long as the DNS server
   is managed appropriately (see the next paragraph).  Similarly, ...

   It should be noted that even though the DHCP server may be
   configured to query the DNS resolver every time it uses configured
   names, the changes made in the DNS zone may not be visible to the
   server until the DNS cache expires.  In general, it's the
   responsibility of the DNS zone's administrator to ensure that
   existing cache does not cause a trouble when a change is made to
   the zone; it should be usually reasonable for the DHCP server to
   rely on it.  However, if this is not desired or if the management
   of the DNS zone is not very reliable, the DHCP server can be
   configured to query the authoritative DNS server directly,
   bypassing any caching DNS servers.

--
JINMEI, Tatuya


From nobody Tue Oct 14 09:57:36 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE9A1A8BC5 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 09:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 KYY6WfJbiroz for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 09:57:32 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56DFC1A8BC4 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 09:57:31 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 812F81B83DE for <dhcwg@ietf.org>; Tue, 14 Oct 2014 09:57:29 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 65C6753E079; Tue, 14 Oct 2014 09:57:29 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 09:57:29 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <7368350B-7786-469D-827D-516A786251F5@nominum.com>
Date: Tue, 14 Oct 2014 11:57:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Kdd9ob2V0To36j8mkN6Omz4YN0o
Cc: Brian Haberman <brian@innovationslab.net>, "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "burcak@juniper.net" <burcak@juniper.net>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 16:57:33 -0000

On Oct 11, 2014, at 9:32 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> I can do the editing.   The point is that adding a lot of text in an =
erratum isn't really kosher.  An erratum is supposed to be pointing out =
an error in a document, not updating the document.   This is borderline, =
since what you are reporting isn't an error, just a lack of explicitness =
that might result in someone doing the implementation wrong.

BTW, I may have been unclear when I said this.   What I mean by "I can =
do the editing" is that if you send me text, I can edit the document in =
the errata tracker.   I wasn't offering to write the text.   :)


From nobody Tue Oct 14 10:31:56 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 051751A90D1 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 10:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.287
X-Spam-Level: 
X-Spam-Status: No, score=-17.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 U4e6akmcCMa7 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 10:31:45 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 330AD1A90B0 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 10:31:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2464; q=dns/txt; s=iport; t=1413307905; x=1414517505; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=gb0SYTIEzOubSdxiEDYsZjGjoj7RgtsvgGVaRvz4B0w=; b=ZcZLZNNedyeklvRn3S0//uaDXJd11kfNyELpPvWqWVHgm8rFPzy+LW5z HMGB34aK61qJ3S0OgMWB1NNh6OjKQZUQxkn+V0nFLzA2ESvApop0dCHZ9 9hbjVj4do4/XZ/S5Q5ekkUrGuxjcVAnjgDSGAYnW7C+PscxVQsyl8HQ4n w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAC1dPVStJA2H/2dsb2JhbABbgw6BKwTUAQKBFRYBfYQCAQEBBDo/DAQCAQgRAQMBAQEKFAkHMhQDBggCBA4FCIg2xwEBAQEBAQEBAQEBAQEBAQEBAQEBAQEXjQeDDQYrBwaDJ4EeAQSReaFjg3dsgUiBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,718,1406592000"; d="scan'208";a="363387207"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-2.cisco.com with ESMTP; 14 Oct 2014 17:31:44 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9EHViTA009372 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Oct 2014 17:31:44 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Tue, 14 Oct 2014 12:31:44 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
Thread-Index: AQHP5M9VJeaR0oFOykC47A75UQEqQpwqNigAgAAEoQD//7eE0IAF4/8KgAAHFGA=
Date: Tue, 14 Oct 2014 17:31:43 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com>
In-Reply-To: <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/fjHXCkJ-qoxi-Phe_rWmh97MKZo
Cc: "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, Karl Auer <kauer@biplane.com.au>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 17:31:48 -0000

Ted:

I'm not sure what is needed/missing. I didn't think the errata was that lon=
g (we can drop the example if people don't think it is required), so not su=
re how much it can be 'shortened'.

I think Karl had a good suggested correction. So, the "It should say:" port=
ion of the errata should be updated with the following (you can drop the ex=
ample if you don't think it is needed, though I think it adds a lot of clar=
ify - the only required change is to replace the 2nd paragraph; there is no=
 change in the first paragraph or the diagram):

   The PacketCable architecture requires an MTA to authenticate itself
   to the TSP's network via the Kerberos protocol.  A Kerberos Realm
   name is required at the MTA to permit a DNS lookup for the address of
   the TSP's Kerberos Key Distribution Center (KDC) entity.

   The Kerberos Realm name MUST be a domain style realm name
   described in RFC 1510 [5].  This realm name MUST be encoded as
   described in RFC 1035 [3] section 3.1, with the additional constraint
   that any letters in the realm name MUST be in upper case. The
   sub-option is encoded as follows:

       Code   Len   Kerberos Realm Name
      +-----+-----+-----+-----+   +-----+
      |  6  |  n  |  k1 |  k2 |...|  kn |
      +-----+-----+-----+-----+   +-----+

   Where k1...kn is the "DNS wire" encoded realm name (see RFC 3315,
   section 8). Thus, the realm "BASIC.1" is encoded as
   "\005BASIC\0011\000".

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Tuesday, October 14, 2014 12:57 PM
To: Bernie Volz (volz)
Cc: Brian Haberman; Paul Duffy (paduffy); burcak@juniper.net; Karl Auer; dh=
cwg@ietf.org; RFC Errata System
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)

On Oct 11, 2014, at 9:32 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> I can do the editing.   The point is that adding a lot of text in an erra=
tum isn't really kosher.  An erratum is supposed to be pointing out an erro=
r in a document, not updating the document.   This is borderline, since wha=
t you are reporting isn't an error, just a lack of explicitness that might =
result in someone doing the implementation wrong.

BTW, I may have been unclear when I said this.   What I mean by "I can do t=
he editing" is that if you send me text, I can edit the document in the err=
ata tracker.   I wasn't offering to write the text.   :)


From nobody Tue Oct 14 10:43:56 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D16B1A90FA for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 10:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 zFaxjm4ylODg for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 10:43:53 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B4E11A90E9 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 10:43:52 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E98411B83D9 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 10:43:51 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id D8DF353E080; Tue, 14 Oct 2014 10:43:51 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 10:43:46 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com>
Date: Tue, 14 Oct 2014 12:43:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/v9rZ36vWMUjvUO9D5c3KDRJu0QQ
Cc: "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, Karl Auer <kauer@biplane.com.au>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 17:43:54 -0000

On Oct 14, 2014, at 12:31 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
>   Where k1...kn is the "DNS wire" encoded realm name (see RFC 3315,
>   section 8). Thus, the realm "BASIC.1" is encoded as
>   "\005BASIC\0011\000".

Okay, this makes more sense now, but is it correct?   That is, given =
that the realm name doesn't end in dot, should there be a \000 at the =
end of the string?   Is "\005BASIC\0011\000" equivalent to =
"\005BASIC\0011" or different?   I question whether we actually can do =
this in an erratum: I don't think that the document as previously =
written addresses this issue.


From nobody Tue Oct 14 10:49:04 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22B861A90E9 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 10:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 TdkDO661fuAg for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 10:49:00 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FB4C1A90C4 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 10:49:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1924; q=dns/txt; s=iport; t=1413308940; x=1414518540; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=8BUqJvs2bTRrfE/s5gUy11+rJavRaMRARIs6ZQ3O9ZA=; b=C07E78wuFGmDKRGBX06N2UfWk2qN0LOnOMK1PqlI4RRnlCZHQRJpM3ro sVx0SDL3ip1C4+OaYxmTNVlScXko/nAo4ZE4tWm7cOom2TZAzfpTXw/5I BK+A+GsSm+CWSLIoOYya8KaQjVplr4QBP3W4032mVHdPSMzF285a9Tylf I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag8FAOhgPVStJA2G/2dsb2JhbABbgw5TWATMKgqHTQKBFRYBfYQCAQEBBAEBATc0CwwEAgEIEQQBAQEKFAkHJwsUCQgCBA4FCIg2DcZ8AQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSNB4JcCwYBHzEHBoMngR4FkXmHBJpfg3dsgQcIFyKBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,718,1406592000"; d="scan'208";a="363016685"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-1.cisco.com with ESMTP; 14 Oct 2014 17:48:58 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s9EHmvNG006844 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Oct 2014 17:48:57 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0195.001; Tue, 14 Oct 2014 12:48:57 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
Thread-Index: AQHP5M9VJeaR0oFOykC47A75UQEqQpwqNigAgAAEoQD//7eE0IAF4/8KgAAHFGCAAFmcAP//rITg
Date: Tue, 14 Oct 2014 17:48:56 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6CD2ED@xmb-rcd-x04.cisco.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com>
In-Reply-To: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/qW53ep8VH5qbnUJ8MSTDYfB79Tk
Cc: "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, Karl Auer <kauer@biplane.com.au>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 17:49:02 -0000

DNS wire encoding says that the dot should be there if I recall. Whether th=
at final dot is actually added to the domain name has, I believe, always be=
en "optional".

RFC 1035 says:

   Domain names in messages are expressed in terms of a sequence of labels.
   Each label is represented as a one octet length field followed by that
   number of octets.  Since every domain name ends with the null label of
   the root, a domain name is terminated by a length byte of zero.  The
   high order two bits of every length octet must be zero, and the
   remaining six bits of the length field limit the label to 63 octets or
   less.

So, I think the encoding is clear. Dropping (not adding) the final dot is f=
airly common. Look at the email list above - the domain names are not "ietf=
.org.". Thus, I don't think this is an issue?

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Tuesday, October 14, 2014 1:44 PM
To: Bernie Volz (volz)
Cc: Paul Duffy (paduffy); dhcwg@ietf.org; Brian Haberman; Karl Auer; RFC Er=
rata System
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)

On Oct 14, 2014, at 12:31 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
>   Where k1...kn is the "DNS wire" encoded realm name (see RFC 3315,
>   section 8). Thus, the realm "BASIC.1" is encoded as
>   "\005BASIC\0011\000".

Okay, this makes more sense now, but is it correct?   That is, given that t=
he realm name doesn't end in dot, should there be a \000 at the end of the =
string?   Is "\005BASIC\0011\000" equivalent to "\005BASIC\0011" or differe=
nt?   I question whether we actually can do this in an erratum: I don't thi=
nk that the document as previously written addresses this issue.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Tue Oct 14 11:05:34 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB3A21A9231 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 11:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 0y4t4ndl8h1a for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 11:05:31 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C06931A9138 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 11:05:31 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A84FC1B83BC for <dhcwg@ietf.org>; Tue, 14 Oct 2014 11:05:31 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 9D55D53E079; Tue, 14 Oct 2014 11:05:31 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 11:05:31 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6CD2ED@xmb-rcd-x04.cisco.com>
Date: Tue, 14 Oct 2014 13:05:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <74BA16B2-CA92-438D-918C-3C3A752A169C@nominum.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD2ED@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/kfoEfJkkip2OP74WiKRM51LEgkU
Cc: "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, Karl Auer <kauer@biplane.com.au>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 18:05:33 -0000

On Oct 14, 2014, at 12:48 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> So, I think the encoding is clear. Dropping (not adding) the final dot =
is fairly common. Look at the email list above - the domain names are =
not "ietf.org.". Thus, I don't think this is an issue?

Actually, the problem here is that RFC 1035 is referring to FQDNs.   =
FQDNs do end with an implicit dot, but is a realm name an FQDN, or just =
something that looks like a domain name?   I think the answer is =
probably what you said, but I think it needs to be said explicitly, and =
I think saying it in an erratum is not the right thing to do.


From nobody Tue Oct 14 12:04:53 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 296C81ACE27 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 12:04:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 tngETd3Tg8oo for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 12:04:48 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87E961ACE1F for <dhcwg@ietf.org>; Tue, 14 Oct 2014 12:04:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1539; q=dns/txt; s=iport; t=1413313487; x=1414523087; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=FEcZjv0Qm/OYGvvrrECxc6iCFyIbaTqkJwhI7yF07I0=; b=Qar9YnziNK0yqkR2UhlSFC8SIjdThkofnu2P7Y624iWhERxdhC8Ge7vC Buj84ruADR23q0NNSxZMMHB5mFfb6b6l0MXqULhNS4AAt6BZgNdi48spf SRuCLO7iybJ9PSW2RAq/Fiine1oZeEyIRj2sB2cpqAq8hlIR1r15SmJhI 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag8FAG9zPVStJA2H/2dsb2JhbABbgw5TWATMLAqHTQKBFRYBfYQCAQEBBAEBATc0CwwEAgEIEQQBAQEKFAkHJwsUCQgCBA4FCIg2DccDAQEBAQEBAQEBAQEBAQEBAQEBAQEBF40HglwRAR8xBwaDJ4EeBZF5hEKIepQng3dsgQ85gQIBAQE
X-IronPort-AV: E=Sophos;i="5.04,718,1406592000"; d="scan'208";a="363250415"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-6.cisco.com with ESMTP; 14 Oct 2014 19:04:47 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9EJ4k6J001948 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Oct 2014 19:04:46 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0195.001; Tue, 14 Oct 2014 14:04:46 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
Thread-Index: AQHP5M9VJeaR0oFOykC47A75UQEqQpwqNigAgAAEoQD//7eE0IAF4/8KgAAHFGCAAFmcAP//rITggABZkQD//7soYA==
Date: Tue, 14 Oct 2014 19:04:46 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6CDABD@xmb-rcd-x04.cisco.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD2ED@xmb-rcd-x04.cisco.com> <74BA16B2-CA92-438D-918C-3C3A752A169C@nominum.com>
In-Reply-To: <74BA16B2-CA92-438D-918C-3C3A752A169C@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/XttfBQoWN6Ne0Q2Xjre8ZaB4sh8
Cc: "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, Karl Auer <kauer@biplane.com.au>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 19:04:50 -0000

Ted:

How this issue came up is rather lengthy and I'm not sure I have the full r=
ecollection as it happened over a period of time. But I think most people g=
ot it right and are sending/expecting an FQDN. So, I'm not sure how big an =
issue this is. But it did create some confusion and it isn't as clear as it=
 could be.

I am not sure it would be worth the effort to issue an updated RFC - as tha=
t may open up more issues.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Tuesday, October 14, 2014 2:05 PM
To: Bernie Volz (volz)
Cc: Paul Duffy (paduffy); dhcwg@ietf.org; Brian Haberman; Karl Auer; RFC Er=
rata System
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)

On Oct 14, 2014, at 12:48 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> So, I think the encoding is clear. Dropping (not adding) the final dot is=
 fairly common. Look at the email list above - the domain names are not "ie=
tf.org.". Thus, I don't think this is an issue?

Actually, the problem here is that RFC 1035 is referring to FQDNs.   FQDNs =
do end with an implicit dot, but is a realm name an FQDN, or just something=
 that looks like a domain name?   I think the answer is probably what you s=
aid, but I think it needs to be said explicitly, and I think saying it in a=
n erratum is not the right thing to do.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Tue Oct 14 14:34:42 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C485C1ACD40 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 14:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 0EJ3UOKSUESE for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 14:34:39 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48CF01ACD3C for <dhcwg@ietf.org>; Tue, 14 Oct 2014 14:34:39 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id CA9801B83D2 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 14:34:38 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id B5F9053E079; Tue, 14 Oct 2014 14:34:38 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 14:34:33 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6CDABD@xmb-rcd-x04.cisco.com>
Date: Tue, 14 Oct 2014 16:34:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <2159987D-556C-4BF3-96F0-6D156EE2035C@nominum.com>
References: <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD2ED@xmb-rcd-x04.cisco.com> <74BA16B2-CA92-438D-918C-3C3A752A169C@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CDABD@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/_spvR9roT-xIuujg93o_Kt5IT8s
Cc: "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, Karl Auer <kauer@biplane.com.au>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 21:34:40 -0000

On Oct 14, 2014, at 2:04 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> How this issue came up is rather lengthy and I'm not sure I have the =
full recollection as it happened over a period of time. But I think most =
people got it right and are sending/expecting an FQDN. So, I'm not sure =
how big an issue this is. But it did create some confusion and it isn't =
as clear as it could be.
>=20
> I am not sure it would be worth the effort to issue an updated RFC - =
as that may open up more issues.

Understood.   But there is a limit to what errata can do.   If the =
errata meaningfully changes what the document actually recommends, =
you're breaking the IETF consensus process.   So as soon as you get into =
a situation like this, the errata mechanism becomes an inadequate =
choice.


From nobody Tue Oct 14 14:39:43 2014
Return-Path: <kre@munnari.OZ.AU>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EBFF1A9139 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 14:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.085
X-Spam-Level: 
X-Spam-Status: No, score=0.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_AU=0.327, HOST_MISMATCH_AU=2.444, RP_MATCHES_RCVD=-0.786] autolearn=no
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 d60yAmcKao8K for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 14:39:39 -0700 (PDT)
Received: from munnari.OZ.AU (munnari.OZ.AU [202.29.151.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD2641ACD38 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 14:39:28 -0700 (PDT)
Received: from perseus.noi.kre.to (localhost [IPv6:::1]) by munnari.OZ.AU with ESMTP id s9ELZARC011183; Wed, 15 Oct 2014 04:35:36 +0700 (ICT)
Received: from perseus.noi.kre.to (localhost [127.0.0.1]) by perseus.noi.kre.to (8.14.7/8.14.2) with ESMTP id s9ELYrHT022118; Wed, 15 Oct 2014 04:34:54 +0700 (ICT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.5
From: Robert Elz <kre@munnari.OZ.AU>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 15 Oct 2014 04:34:53 +0700
Message-ID: <21340.1413322493@perseus.noi.kre.to>
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/7xo0cLzJ13_riz7zdAJlgFTvPlU
Cc: Brian Haberman <brian@innovationslab.net>, Bernie Volz <volz@cisco.com>, "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 21:39:41 -0000

    Date:        Tue, 14 Oct 2014 12:43:42 -0500
    From:        Ted Lemon <Ted.Lemon@nominum.com>
    Message-ID:  <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com>

  |  That is, given that the realm name doesn't end in dot, should there
  | be a \000 at the end of the string?

There has to be.

  | Is "\005BASIC\0011\000" equivalent to "\005BASIC\0011" or different?

Different, obviously, but the latter isn't a valid DNS on the wire encoding,
and that is what is required, is it not?  There's no overall length field 
anywhere in DNS name encoding (whatever may be the case in DHCP), the \0 must
always be there to terminate the name.   There's no way to have a binary
encoded DNS domain name without it (and yes, they are always FQDNs, there's
no way to encode an incomplete domain name, in the DNS, it simply makes no
sense).

kre


From nobody Tue Oct 14 14:51:40 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96E61A019B for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 14:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 9RbJvsXMBXWk for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 14:51:38 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E876E1A017C for <dhcwg@ietf.org>; Tue, 14 Oct 2014 14:51:37 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id CBF521B83D9 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 14:51:37 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id B3B6953E079; Tue, 14 Oct 2014 14:51:37 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 14:51:37 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <21340.1413322493@perseus.noi.kre.to>
Date: Tue, 14 Oct 2014 16:51:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to>
To: Robert Elz <kre@munnari.OZ.AU>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/iEhEXK_pVh-RCW48goHdrgRO8-I
Cc: Brian Haberman <brian@innovationslab.net>, Bernie Volz <volz@cisco.com>, "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 21:51:39 -0000

On Oct 14, 2014, at 4:34 PM, Robert Elz <kre@munnari.OZ.AU> wrote:
> There's no overall length field=20
> anywhere in DNS name encoding (whatever may be the case in DHCP), the =
\0 must
> always be there to terminate the name.

The length of the buffer also indicates the length of the name.   Having =
a length and a NUL terminator is redundant, and indeed the RFC that is =
referenced to talk about what realm names look like says that the realm =
name is not NUL terminated.   So it's pretty easy to imagine an =
implementor interpreting this as meaning that the terminal label should =
be omitted.   Hence my claim that you have to update the document in =
order to make it clear enough to ensure interoperability.


From nobody Tue Oct 14 15:08:01 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C53CB1A1AF0 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 15:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 08jr_sBxrMpr for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 15:07:53 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7A921ACD19 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 15:07:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1954; q=dns/txt; s=iport; t=1413324472; x=1414534072; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=MI1WBa+tZbJ3+FrjKDgVAOr2yo8hTNsqC/gp9J33+Ms=; b=ALD8qzOWaTpgHEl/8BzxIx4EXxylJPh6dHc7fCfr7W+udMroTp1VkWY9 ckde3Si3HXBjESSHEFL6P4mAAu09eJguQv7PyTeRPkLaUwxy/BS9qDtuG zLRtz4i81IcqK4gtzFKa+s77J91ogRWVTNMiARxHDttsPZLfWYObqT5J3 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFANmdPVStJV2b/2dsb2JhbABbgw5TWATMLAyHSwKBFxYBfYQCAQEBAgIBAQE3NAsMBAIBCBEEAQEBChQJBycLFAkIAgQBDQUIiDYNxyoBAQEBAQEBAQEBAQEBAQEBAQEBAQEXjQd2ghcxBwaDJ4EeBZF5hwSFfI1NhxaDd2yBSIECAQEB
X-IronPort-AV: E=Sophos;i="5.04,719,1406592000"; d="scan'208";a="86976138"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP; 14 Oct 2014 22:07:52 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9EM7qDQ011500 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Oct 2014 22:07:52 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Tue, 14 Oct 2014 17:07:51 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Robert Elz <kre@munnari.OZ.AU>
Thread-Topic: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
Thread-Index: AQHP5M9VJeaR0oFOykC47A75UQEqQpwqNigAgAAEoQD//7eE0IAF4/8KgAAHFGCAAFmcAIAAQJiAgAAEpwD//7B2UA==
Date: Tue, 14 Oct 2014 22:07:50 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to> <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com>
In-Reply-To: <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/CRiAaoyN8NnweQSIOaa_ACRUWdo
Cc: "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, Karl Auer <kauer@biplane.com.au>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 22:08:01 -0000

BTW: Here's a reference to what the encoding is in CableLabs documents:

http://www.cablelabs.com/wp-content/uploads/specdocs/PKT-SP-PROV-I08-040113=
.pdf

8.1.5 Kerberos Realm of SNMP Entity (sub-option 6)=20
In conjunction with the Provisioning Entity Address, the Kerberos Realm is =
used as a means of contacting a=20
SNMP Entity in the provisioning realm. The realm name is used to perform a =
DNS SRV lookup for the=20
realm's KDC.=20
Sub-option 6 MUST be included in the DHCP OFFER/ACK to the MTA. Sub-option =
6 MUST only
contain the realm name in the format of FQDN (type=3D0 as per [13]).=20
The encoding of this sub-option is defined in [13].

(Reference [13] is to the RFC 3495. And here is does say "format of FQDN".)

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Tuesday, October 14, 2014 5:52 PM
To: Robert Elz
Cc: Brian Haberman; Bernie Volz (volz); Paul Duffy (paduffy); Karl Auer; dh=
cwg@ietf.org; RFC Errata System
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)

On Oct 14, 2014, at 4:34 PM, Robert Elz <kre@munnari.OZ.AU> wrote:
> There's no overall length field
> anywhere in DNS name encoding (whatever may be the case in DHCP), the=20
> \0 must always be there to terminate the name.

The length of the buffer also indicates the length of the name.   Having a =
length and a NUL terminator is redundant, and indeed the RFC that is refere=
nced to talk about what realm names look like says that the realm name is n=
ot NUL terminated.   So it's pretty easy to imagine an implementor interpre=
ting this as meaning that the terminal label should be omitted.   Hence my =
claim that you have to update the document in order to make it clear enough=
 to ensure interoperability.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Tue Oct 14 15:09:13 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACFD21ACD19 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 15:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 yU341bgUj-pW for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 15:09:09 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ED6D1A1AF0 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 15:09:09 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 74A571B83D6 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 15:09:09 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 6572953E079; Tue, 14 Oct 2014 15:09:09 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 15:09:09 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com>
Date: Tue, 14 Oct 2014 17:09:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <2391019F-FA02-4B69-AA41-043562E642A4@nominum.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to> <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/VkP5-kG90BAiDT34sbYyNZS8BKM
Cc: Brian Haberman <brian@innovationslab.net>, Robert Elz <kre@munnari.OZ.AU>, "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 22:09:10 -0000

On Oct 14, 2014, at 5:07 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> BTW: Here's a reference to what the encoding is in CableLabs =
documents:

Given the existence of the cablelabs doc and that this is =
cablelabs-specific, I don't think there's a need to clarify this with an =
erratum, since people are much more likely (indeed, really required) to =
read the cablelabs document.


From nobody Tue Oct 14 16:00:23 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4B431A001D for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 16:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 A6EjG8b6eIGT for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 16:00:18 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 103591A0037 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 16:00:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1323; q=dns/txt; s=iport; t=1413327618; x=1414537218; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=b7GAN+BjwHd6XNrgVilNbUYavd7NA8DPi0DETOgJmo8=; b=B+erNWgS+ArzSEuLXxtO5/zaQ2GC9MoSDpBAabja9l6PlLwhj8Iu5lyX GfMggUPaYS954wMmKqI3FE3GJcEuL0dYW9TBHenx9zE1H/g6+aOnuUXnT ga3mxUCycR49uVdkYjsDktNnrnYTRWQHZXJwZS/L3md5q0LQ+EPRk1CMU 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag8FAJKpPVStJA2B/2dsb2JhbABbgw5TWATMLAqHTQKBEhYBfYQCAQEBBAEBATc0CwwEAgEIEQQBAQEKFAkHJwsUCQgCBA4FCIg2DccjAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSNB4MNMQcGgyeBHgEEkXmNAIZzjXCDd2yBSIECAQEB
X-IronPort-AV: E=Sophos;i="5.04,719,1406592000"; d="scan'208";a="86982624"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-4.cisco.com with ESMTP; 14 Oct 2014 23:00:15 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s9EN0FlZ027264 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Oct 2014 23:00:15 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Tue, 14 Oct 2014 18:00:15 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
Thread-Index: AQHP5M9VJeaR0oFOykC47A75UQEqQpwqNigAgAAEoQD//7eE0IAF4/8KgAAHFGCAAFmcAIAAQJiAgAAEpwD//7B2UIAAVHAA//+5liA=
Date: Tue, 14 Oct 2014 23:00:14 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6CE437@xmb-rcd-x04.cisco.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to> <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com> <2391019F-FA02-4B69-AA41-043562E642A4@nominum.com>
In-Reply-To: <2391019F-FA02-4B69-AA41-043562E642A4@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/U6RT5PVPN6JN4WklHYItzGdL6bw
Cc: Brian Haberman <brian@innovationslab.net>, Robert Elz <kre@munnari.OZ.AU>, "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Oct 2014 23:00:20 -0000

Not sure why you're against an errata. It is an IETF document. And if it he=
lps one person at some point, what's the harm? If no one cares about the IE=
TF documents, then the errata will be of neither harm nor benefit.

Probably could not hurt in the justification for the errata to include the =
reference to the Cablelabs document?

But, I guess I'll leave it up to you as to whether you want to 'retract' th=
e errata or let it go forward.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Tuesday, October 14, 2014 6:09 PM
To: Bernie Volz (volz)
Cc: Brian Haberman; Robert Elz; Paul Duffy (paduffy); Karl Auer; dhcwg@ietf=
.org; RFC Errata System
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)

On Oct 14, 2014, at 5:07 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> BTW: Here's a reference to what the encoding is in CableLabs documents:

Given the existence of the cablelabs doc and that this is cablelabs-specifi=
c, I don't think there's a need to clarify this with an erratum, since peop=
le are much more likely (indeed, really required) to read the cablelabs doc=
ument.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Tue Oct 14 18:23:03 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C3CE1A0105 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 18:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 TsRJwwVxl_0w for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 18:23:00 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E62611A0104 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 18:23:00 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BA0361B83CF for <dhcwg@ietf.org>; Tue, 14 Oct 2014 18:23:00 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A1C7453E079; Tue, 14 Oct 2014 18:23:00 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 18:22:54 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6CE437@xmb-rcd-x04.cisco.com>
Date: Tue, 14 Oct 2014 20:22:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <70B6B122-2BF7-4F51-B142-DC40DA59A7D0@nominum.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to> <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com> <2391019F-FA02-4B69-AA41-043562E642A4@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE437@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/R6MjfgwrWxvOuqz8d7En_OpRouw
Cc: Brian Haberman <brian@innovationslab.net>, Robert Elz <kre@munnari.OZ.AU>, "Paul Duffy \(paduffy\)" <paduffy@cisco.com>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Oct 2014 01:23:02 -0000

On Oct 14, 2014, at 6:00 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> Not sure why you're against an errata. It is an IETF document. And if =
it helps one person at some point, what's the harm? If no one cares =
about the IETF documents, then the errata will be of neither harm nor =
benefit.

Errata aren't very useful.   Mostly people don't read them.   And this =
isn't technically an error.   And errata are outside the IETF consensus =
process.   It's not so much that I'm _against_ them, but I don't want =
there to be errata that change the meaning of a consensus document, or =
that clarify the meaning of the document in a way that doesn't clearly =
have consensus.

So I don't mind confirming the erratum, but if I'm going to confirm it =
it needs to be done carefully, so as to fit within the very constrained =
bounds of what is appropriate in an erratum.


From nobody Tue Oct 14 19:13:52 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D28F31A0147 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 19:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 g7D0QorgMAJF for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 19:13:48 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 706821A0140 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 19:13:48 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4304C1B83FD for <dhcwg@ietf.org>; Tue, 14 Oct 2014 19:13:48 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 188A253E079; Tue, 14 Oct 2014 19:13:48 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Oct 2014 19:13:42 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <543DD140.2000407@cisco.com>
Date: Tue, 14 Oct 2014 21:13:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <F91721CA-E8D3-4CDF-9CAD-7584528F6B9F@nominum.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to> <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com> <2391019F-FA02-4B69-AA41-043562E642A4@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE437@xmb-rcd-x04.cisco.com> <70B6B122-2BF7-4F51-B142-DC40DA59A7D0@nominum.com> <543DD140.2000407@cisco.com>
To: <paduffy@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/aiYuzvPYMQRbfv4yEzU8YSF5aTk
Cc: Brian Haberman <brian@innovationslab.net>, Bernie Volz <volz@cisco.com>, Robert Elz <kre@munnari.OZ.AU>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Oct 2014 02:13:50 -0000

On Oct 14, 2014, at 8:43 PM, Paul Duffy <paduffy@cisco.com> wrote:
> Bernie, if IETF is too tough sledding for this, an ECR with =
PacketCable may be an easier path.  They can rev the relevant specs.

Excuse me, but I already told you how to do this, and it's dead trivial: =
re-issue the RFC with the text corrected and do a new last call.   I can =
even AD-sponsor it if you want.   This would take about six weeks.

The reason for opposing the erratum with the change that Bernie's =
suggested is that it's not my job to second-guess the working group, nor =
is it your or Bernie's prerogative to do so.   I'm sorry if that seems =
like opposition to you, but it's not opposition.  It's me trying to =
provide guidance as to how to correctly address the problem that Bernie =
has raised.

I realize that it seems stupid that you can't say what you want in an =
erratum, but we fairly routinely have people trying to actually make =
changes to protocols by submitting errata, and setting a precedent on =
this document that could later be used in an appeal on a different =
document would be damaging, even if it seems like a no-brainer in this =
case.


From nobody Tue Oct 14 20:32:31 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20DC11A0114 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 20:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 xfmmTCtu5aoa for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 20:32:28 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D0211A0108 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 20:32:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2915; q=dns/txt; s=iport; t=1413343948; x=1414553548; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=sAWCVcHGIWvVY7rVuvmX9dpC+2eLIUVVVjOQMidfvSw=; b=aa4u9VJHdpITR9uM9tnbsijbZY+lo34bgcYGRVRqVCoo8mLUQQDTFQxm fA3a38Jt2s+1r3hFJB6QW0kULt2GZ5IwNW8YxOOsKoOWLzo7d4LzXVxm8 RQd14VJ8DPeyRkHyKoTzZV15ClXc+COsinPRhArudKOxRu4u0FKnTGUtI 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFANfpPVStJV2Q/2dsb2JhbABbgw5TUwnLdodRAoEUFgF9hAIBAQEDAToPMAwEAgEIEQQBAQEKFBAyHQgCBAENBQgBiC0ICMdUAQEBAQEBAQEBAQEBAQEBAQEBAQEBF40MgxExAgUGgyeBHgWRfY0FhnOHI4JUg36Dd2wBgUeBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,721,1406592000"; d="scan'208";a="363354308"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-8.cisco.com with ESMTP; 15 Oct 2014 03:32:28 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s9F3WRR1023961 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Oct 2014 03:32:27 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0195.001; Tue, 14 Oct 2014 22:32:27 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Paul Duffy (paduffy)" <paduffy@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
Thread-Index: AQHP5M9VJeaR0oFOykC47A75UQEqQpwqNigAgAAEoQD//7eE0IAF4/8KgAAHFGCAAFmcAIAAQJiAgAAEpwD//7B2UIAAVHAA//+5liAABdBhiwALhseAAAD4GgAACMXcUA==
Date: Wed, 15 Oct 2014 03:32:26 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6CE707@xmb-rcd-x04.cisco.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to> <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com> <2391019F-FA02-4B69-AA41-043562E642A4@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE437@xmb-rcd-x04.cisco.com> <70B6B122-2BF7-4F51-B142-DC40DA59A7D0@nominum.com> <543DD140.2000407@cisco.com> <F91721CA-E8D3-4CDF-9CAD-7584528F6B9F@nominum.com> <543DDECE.3050506@cisco.com>
In-Reply-To: <543DDECE.3050506@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.253.144]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/JH76m6dC6_lhWhR05LlTrDsKIZ8
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, Karl Auer <kauer@biplane.com.au>, Robert Elz <kre@munnari.OZ.AU>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Oct 2014 03:32:30 -0000

Paul:

If you want to re-issue that would be fine. If you need help, I can assist.

Et al:

While Ted has way more history here, I do want to point out the following f=
rom the www.ietf.org/rfc.html page (which may just be paraphrasing - there'=
s probably an RFC that describes it), but:

"RFC Errata

Published RFCs never change. Although every published RFC has been submitte=
d to careful proofreading by the RFC Editor and the author(s), errors do so=
metimes go undetected. Technical Errata are errors in the technical content=
. Editorial Errata are spelling, grammar, punctuation, or syntax errors tha=
t do not affect the technical meaning."

So, this would a Technical Errata that the CLARIFIES technical content. I a=
m not trying to change anything - just clarify. If there is still doubt as =
to the intended encoding, then let's make sure we resolve that.

- Bernie

-----Original Message-----
From: Paul Duffy (paduffy)=20
Sent: Tuesday, October 14, 2014 10:41 PM
To: Ted Lemon
Cc: Bernie Volz (volz); Brian Haberman; Robert Elz; Karl Auer; dhcwg@ietf.o=
rg; RFC Errata System
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)

On 10/14/2014 10:13 PM, Ted Lemon wrote:
> On Oct 14, 2014, at 8:43 PM, Paul Duffy <paduffy@cisco.com> wrote:
>> Bernie, if IETF is too tough sledding for this, an ECR with PacketCable =
may be an easier path.  They can rev the relevant specs.
> Excuse me, but I already told you how to do this, and it's dead trivial: =
re-issue the RFC with the text corrected and do a new last call.   I can ev=
en AD-sponsor it if you want.   This would take about six weeks.

Actually, I mis-read your statement that a CableLabs fix would be more effe=
ctive? "Given the existence of the cablelabs doc and that this is cablelabs=
-specific, I don't think there's a need to clarify this with an erratum, si=
nce people are much more likely (indeed, really required) to read the cable=
labs document."

And the six week turn is new info.  But glad to have it!  Thank you.

If six weeks is truly the turn time, Bernie ... re-issue seems reasonable t=
o me?


>
> The reason for opposing the erratum with the change that Bernie's suggest=
ed is that it's not my job to second-guess the working group, nor is it you=
r or Bernie's prerogative to do so.   I'm sorry if that seems like oppositi=
on to you, but it's not opposition.  It's me trying to provide guidance as =
to how to correctly address the problem that Bernie has raised.
>
> I realize that it seems stupid that you can't say what you want in an err=
atum, but we fairly routinely have people trying to actually make changes t=
o protocols by submitting errata, and setting a precedent on this document =
that could later be used in an appeal on a different document would be dama=
ging, even if it seems like a no-brainer in this case.
>
> .
>


From nobody Tue Oct 14 20:33:07 2014
Return-Path: <paduffy@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 226A71A010E for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 18:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 uG7CSjwgV-Iw for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 18:43:32 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6419E1A010C for <dhcwg@ietf.org>; Tue, 14 Oct 2014 18:43:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1436; q=dns/txt; s=iport; t=1413337412; x=1414547012; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=/0HpaIVmDOJvT5/fU2QZTvpai+Z2E6tUXpcuJ443p8c=; b=jNeRS8kFXprb1WYN6+mH8J3cNbfKaESMlyg/Dih1NB8ZA6xlbZiVvgMm IPmVSXfQZ+0xbA/qFcK0d5Sd3kdcwTAr2X4bdIjSSassfkfch6D1PNaCQ fXRqqlTw1gctQ/SI3g3ixm8DbmVytZObIW20T8jH/5/i6qbJoYW7DNyB5 w=;
X-IronPort-AV: E=Sophos;i="5.04,720,1406592000"; d="scan'208";a="87019204"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-5.cisco.com with ESMTP; 15 Oct 2014 01:43:30 +0000
Received: from [10.86.242.252] (che-vpn-cluster-2-252.cisco.com [10.86.242.252]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s9F1hSM1009425; Wed, 15 Oct 2014 01:43:29 GMT
Message-ID: <543DD140.2000407@cisco.com>
Date: Tue, 14 Oct 2014 21:43:28 -0400
From: Paul Duffy <paduffy@cisco.com>
Organization: Cisco Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>, Bernie Volz <volz@cisco.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to> <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com> <2391019F-FA02-4B69-AA41-043562E642A4@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE437@xmb-rcd-x04.cisco.com> <70B6B122-2BF7-4F51-B142-DC40DA59A7D0@nominum.com>
In-Reply-To: <70B6B122-2BF7-4F51-B142-DC40DA59A7D0@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/bMsEVK7P7wDAukRROTIMTZPSfmo
X-Mailman-Approved-At: Tue, 14 Oct 2014 20:33:06 -0700
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, Karl Auer <kauer@biplane.com.au>, Robert Elz <kre@munnari.OZ.AU>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: paduffy@cisco.com
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Oct 2014 01:43:34 -0000

Time for the author to chime in.

What Bernie has described is indeed what was intended and most often 
implemented in the field.  The text is remarkably confused in very few 
words.  Don't know how this got past the RFC process, CableLabs review, 
etc.  Who wrote this crap ... oh damn ... I DID!  :(

I agreed with Bernie's proposed errata.  I don't understand the opposition.

Bernie, if IETF is too tough sledding for this, an ECR with PacketCable 
may be an easier path.  They can rev the relevant specs.


On 10/14/2014 9:22 PM, Ted Lemon wrote:
> On Oct 14, 2014, at 6:00 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
>> Not sure why you're against an errata. It is an IETF document. And if it helps one person at some point, what's the harm? If no one cares about the IETF documents, then the errata will be of neither harm nor benefit.
> Errata aren't very useful.   Mostly people don't read them.   And this isn't technically an error.   And errata are outside the IETF consensus process.   It's not so much that I'm _against_ them, but I don't want there to be errata that change the meaning of a consensus document, or that clarify the meaning of the document in a way that doesn't clearly have consensus.
>
> So I don't mind confirming the erratum, but if I'm going to confirm it it needs to be done carefully, so as to fit within the very constrained bounds of what is appropriate in an erratum.
>
>


From nobody Tue Oct 14 20:33:08 2014
Return-Path: <paduffy@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73CFC1A0194 for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 19:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 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_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 B1BSKea7Kc4F for <dhcwg@ietfa.amsl.com>; Tue, 14 Oct 2014 19:41:21 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 221AB1A0195 for <dhcwg@ietf.org>; Tue, 14 Oct 2014 19:41:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1688; q=dns/txt; s=iport; t=1413340881; x=1414550481; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=uhIV2y+/yUcc/ywsqjCxAjyKWPVYSwlCmF2OwmTXt9Y=; b=S1fh/errgL6DD48TrAwwVqFv1V5ye9BAY/JnbzUiXvOZahI10TrI2OjJ TXBkbnVZDg1PaBCiJhTUkv+YeMCmGGtxSvdrWGAOosmKOpwe9zif/649O AzFL8pqhqQpi7lX3gI0/+Yjw+AtEBg77P7rSiLzLk11nfJp8Oss03/GB8 8=;
X-IronPort-AV: E=Sophos;i="5.04,720,1406592000"; d="scan'208";a="363345627"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 15 Oct 2014 02:41:20 +0000
Received: from [10.86.242.252] (che-vpn-cluster-2-252.cisco.com [10.86.242.252]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s9F2fJdX025651; Wed, 15 Oct 2014 02:41:19 GMT
Message-ID: <543DDECE.3050506@cisco.com>
Date: Tue, 14 Oct 2014 22:41:18 -0400
From: Paul Duffy <paduffy@cisco.com>
Organization: Cisco Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to> <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com> <2391019F-FA02-4B69-AA41-043562E642A4@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE437@xmb-rcd-x04.cisco.com> <70B6B122-2BF7-4F51-B142-DC40DA59A7D0@nominum.com> <543DD140.2000407@cisco.com> <F91721CA-E8D3-4CDF-9CAD-7584528F6B9F@nominum.com>
In-Reply-To: <F91721CA-E8D3-4CDF-9CAD-7584528F6B9F@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/C6scr5ovprp6NUuSPasCGJuPaII
X-Mailman-Approved-At: Tue, 14 Oct 2014 20:33:06 -0700
Cc: Brian Haberman <brian@innovationslab.net>, Bernie Volz <volz@cisco.com>, Robert Elz <kre@munnari.OZ.AU>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: paduffy@cisco.com
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Oct 2014 02:41:24 -0000

On 10/14/2014 10:13 PM, Ted Lemon wrote:
> On Oct 14, 2014, at 8:43 PM, Paul Duffy <paduffy@cisco.com> wrote:
>> Bernie, if IETF is too tough sledding for this, an ECR with PacketCable may be an easier path.  They can rev the relevant specs.
> Excuse me, but I already told you how to do this, and it's dead trivial: re-issue the RFC with the text corrected and do a new last call.   I can even AD-sponsor it if you want.   This would take about six weeks.

Actually, I mis-read your statement that a CableLabs fix would be more 
effective? "Given the existence of the cablelabs doc and that this is 
cablelabs-specific, I don't think there's a need to clarify this with an 
erratum, since people are much more likely (indeed, really required) to 
read the cablelabs document."

And the six week turn is new info.  But glad to have it!  Thank you.

If six weeks is truly the turn time, Bernie ... re-issue seems 
reasonable to me?


>
> The reason for opposing the erratum with the change that Bernie's suggested is that it's not my job to second-guess the working group, nor is it your or Bernie's prerogative to do so.   I'm sorry if that seems like opposition to you, but it's not opposition.  It's me trying to provide guidance as to how to correctly address the problem that Bernie has raised.
>
> I realize that it seems stupid that you can't say what you want in an erratum, but we fairly routinely have people trying to actually make changes to protocols by submitting errata, and setting a precedent on this document that could later be used in an appeal on a different document would be damaging, even if it seems like a no-brainer in this case.
>
> .
>


From nobody Wed Oct 15 06:07:12 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B410A1A1ABE for <dhcwg@ietfa.amsl.com>; Wed, 15 Oct 2014 06:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 FvlKxi0KZ7SY for <dhcwg@ietfa.amsl.com>; Wed, 15 Oct 2014 06:07:03 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 553F01A1B16 for <dhcwg@ietf.org>; Wed, 15 Oct 2014 06:06:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10118; q=dns/txt; s=iport; t=1413378418; x=1414588018; h=from:to:subject:date:message-id:mime-version; bh=LRaCeIyk3w+yBUOz2OhXx5ajBGDN2zhzt6xQTWR3bjg=; b=MuC4Kn11Adv3pk0l+Pmu7WlVSnNSH7/Ui+TiqSQsvj9wen2bKDZdF486 CYL8gHUYltNKE9U1jtyrnGtBe5qduQjc+qm8/U9gaUW4BgkZs5vdT1poR Y+O7+S8SnudVBs/3uW2Hkdock5vXP8VJvI/63kMK4NR0CbmJHEKXKMp14 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUGAAVxPlStJV2d/2dsb2JhbABbgkhGU1gEyhGBbodNAoESFgFyC4QCAQEBBC1eARkEAQELHTkUCQkBBBMIiDYNo0ekagEBAQEBAQEBAQEBAQEBAQEBAQEZjQyDETcHgyeBHgWRf4REiEE8gwqHZYIngxqDfoN3bIFIgQIBAQE
X-IronPort-AV: E=Sophos;i="5.04,724,1406592000";  d="scan'208,217";a="360353505"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 15 Oct 2014 13:06:57 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s9FD6vl2013221 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Wed, 15 Oct 2014 13:06:57 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Wed, 15 Oct 2014 08:06:57 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Results for WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
Thread-Index: Ac/od9zGHrs2omZ3RB2GQXvwNWs42w==
Date: Wed, 15 Oct 2014 13:06:56 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6CEA07@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.253.176]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6CEA07xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/nAaV8zmAqSOvgHwM5Lzt3n3ANSE
Subject: [dhcwg] Results for WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct 13, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Oct 2014 13:07:08 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6CEA07xmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi:

We (mostly I as Tomek is a co-author of the document, but he agreed) have d=
etermined that this document did NOT pass WGLC.

Thanks to those that reviewed it, but we feel that the level of responses w=
as a bit too low to find for "rough consensus".

There were also some good issues raised. Therefore, Tomek will update the d=
ocument and we will try for another WGLC sometime in the near future.

We really would like to see more responses from the WG to last calls.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Monday, September 29, 2014 10:36 AM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond by Oct =
13, 2014


Hi all,



This message starts the DHC working group last call to advance "Customizing=
 DHCP Configuration on the Basis of Network Topology", draft-ietf-dhc-topo-=
conf-03, document as an Informational RFC. The authors believe that this ve=
rsion is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-topo-conf-03



Please send your comments by October 13th, 2014. If you do not feel this do=
cument should advance, please state your reasons why.



There are no IPR claims reported at this time.



Bernie Volz is the assigned shepherd for this document.



- Tomek & Bernie


--_000_489D13FBFA9B3E41812EA89F188F018E1B6CEA07xmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1779988719;
	mso-list-type:hybrid;
	mso-list-template-ids:-1672319576 464787052 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:3;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We (mostly I as Tomek =
is a co-author of the document, but he agreed) have determined that this do=
cument did NOT pass WGLC.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks to those that r=
eviewed it, but we feel that the level of responses was a bit too low to fi=
nd for &#8220;rough consensus&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">There were also some g=
ood issues raised. Therefore, Tomek will update the document and we will tr=
y for another WGLC sometime in the near future.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We really would like t=
o see more responses from the WG to last calls.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Monday, September 29, 2014 10:36 AM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-topo-conf-03.txt - Respond =
by Oct 13, 2014<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Hi all,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This message starts the DHC working group last ca=
ll to advance &quot;Customizing DHCP Configuration on the Basis of Network =
Topology&#8221;, draft-ietf-dhc-topo-conf-03, document as an Informational =
RFC. The authors believe that this version is
 ready.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The draft is available here:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"http://tools.ietf.org/html/draft-ietf-=
dhc-topo-conf-03">http://tools.ietf.org/html/draft-ietf-dhc-topo-conf-03</a=
><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please send your comments by October 13th, 2014. =
If you do not feel this document should advance, please state your reasons =
why.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There are no IPR claims reported at this time.<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bernie Volz is the assigned shepherd for this doc=
ument.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6CEA07xmbrcdx04ciscoc_--


From nobody Wed Oct 15 07:54:36 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36F451A8732 for <dhcwg@ietfa.amsl.com>; Wed, 15 Oct 2014 07:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ORxpfy4dZbB8 for <dhcwg@ietfa.amsl.com>; Wed, 15 Oct 2014 07:54:27 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEB1A1A1B20 for <dhcwg@ietf.org>; Wed, 15 Oct 2014 07:54:26 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C655A1B8307 for <dhcwg@ietf.org>; Wed, 15 Oct 2014 07:54:26 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A928453E076; Wed, 15 Oct 2014 07:54:26 -0700 (PDT)
Received: from [192.168.1.63] (71.201.198.58) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 15 Oct 2014 07:54:26 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <543DDECE.3050506@cisco.com>
Date: Wed, 15 Oct 2014 09:54:20 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <8F6F240A-DE71-4E33-B66E-CC70E8BDF8A6@nominum.com>
References: <A6D69285-6823-4784-BE29-5D597C4F539A@nominum.com> <20141010211437.8FD73181C86@rfc-editor.org> <1412978590.20084.363.camel@karl> <42D40B90-D69A-4B22-B964-50A85C50C394@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6C399E@xmb-rcd-x04.cisco.com> <7368350B-7786-469D-827D-516A786251F5@nominum.com> <5C93CC08-A1F6-4245-8A82-DA3109293BEA@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CD128@xmb-rcd-x04.cisco.com> <21340.1413322493@perseus.noi.kre.to> <0663EAD1-F89C-4A00-9036-F4DF16757AF1@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE256@xmb-rcd-x04.cisco.com> <2391019F-FA02-4B69-AA41-043562E642A4@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B6CE437@xmb-rcd-x04.cisco.com> <70B6B122-2BF7-4F51-B142-DC40DA59A7D0@nominum.com> <543DD140.2000407@cisco.com> <F91721CA-E8D3-4CDF-9CAD-7584528F6B9F@nominum.com> <543DDECE.3050506@cisco.com>
To: <paduffy@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.201.198.58]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/fIwdjqKkd86oq5tCTcFJn_NDCHY
Cc: Brian Haberman <brian@innovationslab.net>, Bernie Volz <volz@cisco.com>, Robert Elz <kre@munnari.OZ.AU>, Karl Auer <kauer@biplane.com.au>, "dhcwg@ietf.org" <dhcwg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Oct 2014 14:54:28 -0000

On Oct 14, 2014, at 9:41 PM, Paul Duffy <paduffy@cisco.com> wrote:
> Actually, I mis-read your statement that a CableLabs fix would be more =
effective? "Given the existence of the cablelabs doc and that this is =
cablelabs-specific, I don't think there's a need to clarify this with an =
erratum, since people are much more likely (indeed, really required) to =
read the cablelabs document."

Ah, no, I just meant that since the cablelabs document is more explicit, =
and people are quite likely to read it, it should be sufficient.   But I =
think clarifying the RFC is also good; in particular, I think it would =
be good to be clear about the non-terminal label.   I think that's a =
change that requires a new consensus call--that's the only reason I'm =
pushing back on it.


From nobody Wed Oct 15 09:16:43 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED1F1A898F for <dhcwg@ietfa.amsl.com>; Wed, 15 Oct 2014 09:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 lqMJmgWvsyMz for <dhcwg@ietfa.amsl.com>; Wed, 15 Oct 2014 09:16:39 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D09B51A8940 for <dhcwg@ietf.org>; Wed, 15 Oct 2014 09:16:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14151; q=dns/txt; s=iport; t=1413389798; x=1414599398; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=l0txMzo6U6F+0xHc/8LYBmSn+1yFTk0s0cynDsdpFwc=; b=H7u5a3n1+TRxCyeC0hJj7ysDzMQsinCvm5RFSkMi1M7zyb9ZiCzSBiix x6h0sE7DD32zHIfcMqIQOnUBUcXL4/lauk9CV/Cq1sCxsah/wXPSgty/K dvTVj+3DQnY7iEJM3xNYRG+q5yOjYUTlIIXxZfK+24eltf85dpwzHCkgf s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFAE+dPlStJA2G/2dsb2JhbABbgw5TWASDAshzCodNAoEUFgF9hAIBAQEDAQEBAR4BTAsFBwQCAQgRBAEBAgMGHQIDAiEGCxQJCAIEAQ0FCAGIIQMJCA2WWpxIAY5gDYY9AQEBAQEBAQEBAQEBAQEBAQEBAQEBF4EpiSaDS4FcBwEBChQmCwIFBoJuOYEeBY9OgjGERIUAg0E8gwqEA4ZLgliDfoN3bAGBBQQFFwQegQIBAQE
X-IronPort-AV: E=Sophos;i="5.04,725,1406592000"; d="scan'208";a="87224640"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-5.cisco.com with ESMTP; 15 Oct 2014 16:16:37 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s9FGGarP023564 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Oct 2014 16:16:37 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Wed, 15 Oct 2014 11:16:36 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, "Marcin Siodelski" <msiodelski@gmail.com>
Thread-Topic: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
Thread-Index: AQHP4yTrEkD6ExoBZ0O6wM0stZ10wJwxXZPA
Date: Wed, 15 Oct 2014 16:16:36 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com>
In-Reply-To: <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.120]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/2aipdwabSlvTT42qacRzKBvbmr8
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Oct 2014 16:16:41 -0000

Jinmei:

Thanks much for your thorough review!

Some comments below (inline, starting with **).

We are hopeful to receive further review comments so don't plan to publish =
an 08 revision until just before the IETF-91 draft deadline (Oct 27).

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of ????
Sent: Wednesday, October 08, 2014 2:23 PM
To: Marcin Siodelski
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-sta=
teful-issues

At Thu, 02 Oct 2014 11:10:48 +0200,
Marcin Siodelski <msiodelski@gmail.com> wrote:

> The version -07 of the draft-ietf-dhc-dhcpv6-stateful-issues is now=20
> available at:
>
> http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/
[...]
> Please provide your comments. Note that this work builds the ground=20
> for the RFC3315bis, so your interest is important.

Here's my review.  I almost forgot the full context of the discussion regar=
ding my previous review comments, so I might simply repeat some points I ma=
de before.  Hopefully they are still valid.

First, I have a couple of higher level points to discuss:

- What's the final goal of this document?  Is it supposed to be
  published as a separate RFC, or is it just a placeholder for
  discussion for 3315bis and is supposed to be dropped once the result
  is incorporated to 3315bis?  I'm asking this because in its current
  form this document relies on the fact that readers are pretty
  familiar with the discussion context and won't be friendly for
  future readers if published as a separate document.  But if the goal
  is the latter of the above two, it's probably okay and it would be
  more constructive to just discuss purely technical matters rather
  than try to make it (more) readable for first-time readers.

** The goal here is for this work to be an RFC. The 3315bis work is separat=
e; obviously the 3315bis will want to incorporate the stateful issues chang=
es. But we believe leaving the merged text to 3315bis is best. 3315bis may =
have other changes that impact the text in different ways.

- I'm not necessarily opposed to it, but why this?

> 5. Removed the "unified" text (intended for RFC3315bis) from the=20
> Renew/Rebind sections. The current text only provides respective=20
> updates for RFC3315 and RFC3633.

  If the eventual goal is to unify 3315 and 3633 in 3315bis (I
  personally didn't think it a very good idea, but I wouldn't argue on
  that point in this context), such unification will be eventually
  inevitable.  So shouldn't it rather better to discuss it sooner
  (i.e., in this draft) than later?

** See above. And, yes the goal of 3315bis is to produce one document that =
unifies 3315 and 3633.

Specific comments to the draft text follow:

- Title: now that our main focus is the mixed use of IA_NA and IA_PD
  rather than generalizing the concept of stateful resources, I think
  it makes more sense to reflect it in the title, for example,
  "Issues and Recommendations with Multiple DHCPv6 IA Options".
  See also my comments on Section 3 (terminology) below.

** We will leave the title as it is.

- Abstract: this is more about readability (see above), but I'm afraid
  the current abstract text wouldn't be really helpful for first-time
  readers (on the other hand, it's not a problem for "me", because I
  already know what it is).  At the very least I'd briefly summarize
  the actual proposals here.  On the other hand, I don't see the
  sentence that refers to RFC 7084 in this context (it's useful in
  Introduction, but not for abstract).

** We will leave the abstract pretty much as is. We change last sentence to=
 mention that the (RFC) changes are to address the identified issues.

- Section 1: this is not a complete sentence:

   [...] And, to provide a framework to support
   new IA option types, assuming they are similar enough.

  probably it's just expected to be a continuation of the preceding
  sentence? "requested as per [RFC7084], and to provide...".

** See below.

- Section 1, regarding the same text and this one:

   [...]  Future
   documents that define new IA option types will need to specify
   whether they fit into this framework or define the DHCP operation for
   the new and existing IA option types, as appropriate.

  IMO, this document should talk a bit more about the "framework".
  I'd suggest explaining these, for example: this framework is based
  on some assumptions, including:
  - An IA option has the concept of T1/T2 values for renew and rebind,
    and the semantics is same for all these IA options types
  - The information (or a set of it) assigned in IA is associated with
    a lifetime.
  - These multiple IA options are expected to be assigned as a set,
    and it's generally considered an operator's error if a DHCPv6
    server can only provide a subset of it, even if it's not rejected
    by the protocol. (without this assumption, we could have an
    awkward situation, e.g., where a client request both IA_NA and
    IA_PD and the server only replies with IA_NA, and the client can't
    get IA_PD at least until the first renew or unless reconfigure is
    made possible)

** We will rework the Introduction to remove the 'framework' concept and ju=
st focus on the IA_NA/IA_PD issues. When and if there are future IA's, thos=
e documents can indicate whether they integrate into this work (i.e., add I=
A_foo to IA_NA, IA_PD in the stateful issues document) or if they are separ=
ate and independent.

- Section 1, on the paragraph talking about IA_TA:

   Note that while IA_TA (temporary addresses) options may be included
   with other IA option type requests, [...]

  I have a feeling that this paragraph is incomplete.  That is, I'd
  say "so what?" on reading this paragraph.  My suggestion is to
  clearly declare that the mixture of IA_TA and other types of IAs is
  out of scope of this document.  In fact, IA_TA doesn't fit in the
  framework shown in the previous bullet (as it doesn't have T1/T2),
  and we won't be able to well-define it.  And we can probably justify
  the decision based on the observation that it "has limited value".
  This paragraph would make sense if it's provided with such a
  decision.

** We plan on making this change.

- Section 3: now that we've limited the scope of this document
  mainly focusing on the specific case of IA_NA and IA_PD, I
  suggest simplifying the terminology.  It would be more
  reader-friendly if the reader doesn't have to understand fewer
  concepts as a prerequisite.  Specifically:
  - remove "resource".  I don't see the need for this generalized
    concept anymore.  In fact, other than in this particular section,
    this term is used only once (Section 4.1)
  - replace "stateful options" with "IA options" (and to this end we
    might not bother to list in the terminology section explicitly)

** We plan on making some of these changes (stateful options will stay).

- Section 4: I suggest adding the rationale of the proposal.  In its
  current form the proposal seems to be suddenly given without
  explaining why.  Even if some hints are (seemingly) scattered in
  other sections of the document, I believe this should be the primary
  place to give it.

** We plan on moving this rationale into section 4 (remove from section 1).

- Section 4.1, regarding the replacement for RFC 3315 17.2.2:

      If the server will not assign any addresses to an IA in a
      subsequent Request from the client, the server MUST include
      the IA in the Advertise message with no addresses in the IA
      and a Status Code option encapsulated in the IA containing
      status code NoAddrsAvail.

  Maybe we should also say "the server MUST NOT place a Status Code
  option for an IA at the top level".

** No change planned; we feel that the text is sufficiently clear on this w=
hen compared with the original RFC 3315 text.

- Section 4.2: replacement for RFC 3315 17.1.3:

     The client MUST ignore any Advertise message that contains no
     addresses (IAADDR options encapsulated in IA_NA or IA_TA options)
     and no delegated prefixes (IAPREFIX options encapsulated in IA_PD
     options, see RFC 3633) with the exception that the client
     MUST process an included SOL_MAX_RT option (RFC 7083), MUST
     process an included INF_MAX_RT option (RFC 7083), and MAY
     display any associated status message(s) to the user.

  It's awkward to see it mention prefixes while this version
  intentionally cancels the idea of "unified" text for renew/rebind.
  It's not clear to me why Section 17.1.3 (regarding advertise) still
  needs to provide "unified" text.

** While we could drop "and no delegated prefixes (...)", does that really =
help significantly especially since RFC 7083 material is being pulled in al=
ready? Also, in this case if we leave it out, people may be confused about =
what happens if there are no addresses but prefixes. (For most of the other=
 changes later, RFC 3633 already covers these changes as it generally impli=
es to replace "addresses" with "delegated prefixes" in much of the Reply pr=
ocessing. And, we've provided the revised text where needed for 3633.) Also=
, RFC 3633 already points to 17.1.3 of 3315 and this avoids having to speci=
fy replacement text for 3633.

- Section 4.3: I don't understand the following text:

   [...] To deal
   with the case where servers have not yet been updated to do that,
   clients MUST use the shortest (explicit or implicit) T1/T2 times
   (larger than 0), from the same IA option, in the Reply.  T1/T2 times
   from other IAs are ignored.

  I guess it tries to address the corner case I pointed out for the
  previous version of the draft:
  http://www.ietf.org/mail-archive/web/dhcwg/current/msg15663.html
  but I don't even understand what the client would do in this case
  based on the new text.  To recap, what should happen if the client
  sees the following two sets of T1/T2 according to the above text?
  - T1a =3D 10, T2a =3D 20
  - T1b =3D 0, T2b =3D 5

** We will include this example and explain it. Note that T1b  =3D 0 means =
that the client must calculate the T1 time (50% of lifetime) and that it ob=
viously needs to be less than T2b. So, in this case the T1b =3D0, T2b =3D 5=
 would be used but the T1b time is the 'implicit' time (we can't give the v=
alue since the lifetimes are not specified).

** There are perhaps other cases, for example T1a =3D 10, T2a =3D 20, T1b =
=3D 5, T2b =3D 25 that are a bit more interesting since picking (b) means T=
1=3D5/T2=3D25 which means T2 is longer than T2a.

** Perhaps we need to review whether the shortest 'effective' T1 and indepe=
ndently shortest 'effective' T2 are a better choice (obviously the client w=
ould have to adjust T1 if this means T1>T2, but I'm not sure that could eve=
n happen since for any individual IA, T1 must be less than or equal to T2).=
 Note that by 'effective' here I mean either the server supplied value or, =
if 0, the client determined value based on the lifetimes within that IA.  I=
f we used that algorithm, for your case the answer would not change; for my=
 example T1 would be and T2 would be 20 which are probably better values fo=
r this case.

** Comments about this issue (and perhaps additional case analysis if appro=
priate) would be useful.

- Section 4.4.5: does this mean, if the client has bindings of
  multiple IAs, it should (effectively) abandon all of the bindings
  and establish new bindings for all of the IAs starting from Solicit?
  If so, it makes sense to me, but it's not really clear from the
  text, and I suggest clarifying that point.

     When the client receives a NotOnLink status from the server in
     response to a Confirm message, the client performs DHCP server
     solicitation, as described in section 17, and client-initiated
     configuration as described in section 18.

** We will create a 3315bis ticket since this is pre-existing text used "as=
 is" from 3315. And, this is not an issue that is particular to this draft.=
 Note that Confirm is IA_NA (IA_TA) specific as IA_PD requires a Rebind; so=
 this is an open issue in the original 3315 and should be added by the bis =
document. It also is more of a clarification, rather than a "change". The b=
is document can clarify that when a client sends a Solicit, it MUST not be =
using any of the addresses or delegated prefixes for the bindings included =
in the Solicit.

** Note also that it appears the original 3315 text missed specifying the a=
ctions for NotOnLink for Renew and Rebind.

** We've opened a new DHCPv6bis ticket for this - http://trac.tools.ietf.or=
g/group/dhcpv6bis/ticket/123.

- Section 4.4.5: I'm not sure if I understand this:

     -  Tries to obtain the IA from another server (by restarting the
        DHCP discovery process) if the client attempted to obtain a new
        binding in the Renew or Rebind message by sending an IA without
        any addresses and the server responded with NoBinding status
        code.

  What if the client has a binding for another IA (and it's
  successfully renewed in this response)?  If the above means the
  client starts a new DHCPv6 session for the IA that doesn't have a
  binding separately from the other IA with a binding, it seems to
  break the main idea of this draft: maintaining a single DHCPv6
  session for all IAs.  So does this mean the client terminates the
  existing DHCPv6 session and tries to establish all bindings for all
  IAs from Solicit?

** Yes, this seems to have been done in error. We will revise. Restarting D=
HCP discovery process should only be done if there are no addresses/prefixe=
s at all.

--
JINMEI, Tatuya

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Wed Oct 15 20:52:48 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 480D91A014E for <dhcwg@ietfa.amsl.com>; Wed, 15 Oct 2014 20:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 hdDO0C064Idh for <dhcwg@ietfa.amsl.com>; Wed, 15 Oct 2014 20:52:42 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E96721A0144 for <dhcwg@ietf.org>; Wed, 15 Oct 2014 20:52:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13584; q=dns/txt; s=iport; t=1413431562; x=1414641162; h=from:to:cc:subject:date:message-id:mime-version; bh=4PT1XFA5n1AP2+28uOPoW2gucscNpqjod+fH6SzDzjg=; b=eUd8mBdLgcqBPTz0E+j1ytUiZylv0i/IkRBZAbCkxJYG4ymnLWRJJffs GxvoIw1bLWerK6tWGR9A7ErJ5f1gtYAIWJmJgrsO1dCN7zaaODw2pqrvp kwQxY/DTV61oB508xdBdNI6xrzQaNvfffnc2ivDt/52UOGk+Tj1G0ZRIP Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYFAHxAP1StJA2I/2dsb2JhbABagkhGU1gEu1+OPYFuh00CgQ8WAXILhAQBBC1MEgEqViYBBA4NARKIIw3JJQEBAQEBAQEBAgEBAQEBAQEBARmPfQEBHjGDNIEeBZF/hESBd4ZLPI0XhxiBfIF7bAGBDjmBAgEBAQ
X-IronPort-AV: E=Sophos; i="5.04,729,1406592000"; d="scan'208,217"; a="87394713"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-8.cisco.com with ESMTP; 16 Oct 2014 03:52:40 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s9G3qeDB008721 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Oct 2014 03:52:40 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Wed, 15 Oct 2014 22:52:40 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "draft-ietf-dhc-addr-registration@tools.ietf.org" <draft-ietf-dhc-addr-registration@tools.ietf.org>
Thread-Topic: More on failed WGLC for draft-ietf-dhc-addr-registration-07.txt
Thread-Index: Ac/ou1+kmd4O3Y7uSbyCYmEe83Thbg==
Date: Thu, 16 Oct 2014 03:52:39 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6CFA7A@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6CFA7Axmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/do0yqYzcotZ0tiV8REB96LxtDBY
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: [dhcwg] More on failed WGLC for draft-ietf-dhc-addr-registration-07.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 03:52:46 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6CFA7Axmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Here are my particular reasons for believing that this work is not yet read=
y. This is primarily to help the authors focus on updating the draft and to=
 provide motivation for those in the WG that feel this is important but did=
 not 'speak up'.

First, I believe this draft has a higher bar than usual because it is stand=
ard track work, defines a "new" protocol, and one that is a grey area for t=
he DHC WG - it being done here mostly because it uses the DHCPv6 protocol m=
essage and option format (and relay support). It was adopted by the DHC WG =
as there was support for doing this work, so it is important that we make s=
ure it concludes.

Jinmei raised some very good points about this work and whether it was need=
ed (see http://www.ietf.org/mail-archive/web/dhcwg/current/msg15849.html an=
d this thread as this not the first message). I did chime in during this di=
scussion to help explain why having clients update DNS directly was an issu=
e.

I also think the draft needs to answer why networks that won't or can't use=
 DHCPv6 to resolve the DNS issue would actually make use of this solution. =
The abstract states "One of the most important issues in this regard is the=
 inability to register such addresses in DNS." Why is this such an importan=
t issue; if it isn't happening today, why is this needed now (or in the fut=
ure)? In the introduction there is "One such limitation is related to the i=
nability of nodes with self-generated addresses to register their IPv6-addr=
ess-to-FQDN bindings in DNS." It goes on to explain the limitation, but not=
 say WHY this is a problem that needs to be solved. Sure, the "problem" bei=
ng solved is adding these mappings to DNS; but why is that needed in the fi=
rst place? What will this DNS information be used for (i.e., to allow incom=
ing connections, to help administrators, for 'primitive' security - if the =
host is in DNS it must be OK, or)? The Introduction does say "In several ti=
ghtly controlled networks ..." - so is this a solution for just a few netwo=
rks?

I had also raised a concern about the lack of addressing the multi-server s=
olution. Sure, RFC 3315 wasn't complete on this (i.e. the failover work). A=
nd, certainly one option is to say it is out of scope, but that has its own=
 issues. There is an individual submission draft which I had missed (it is =
in the "Related Internet-Drafts" section at the bottom of http://datatracke=
r.ietf.org/wg/dhc/documents/) - the draft-que-dhc-dns-multi-dhcp-servers-00=
 document. This is an individual submission (not adopted by the WG); it att=
empts to address the multiple servers issue. It is very preliminary. But it=
 does open the question of whether more could be done in the addr-registrat=
ion draft for this or whether the addr-registration, by declaring it out of=
 scope, might restrict possible solutions? I'm not saying that this work ne=
eds to be folded into the addr-registration draft, but it may be worth a fe=
w cycles to consider how this may be solved?

An additional nit found in re-reading parts of the draft:

   Also, there is no way to propagate the
   address of authoritative name server by any protocols.

DNS can be used for this so I think this statement is incorrect - query for=
 the SOA? (Yes, there may be cases where this isn't the 'real' server that =
will accept DNS updates - i.e., hidden primary/master.)


-          Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1B6CFA7Axmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:263270345;
	mso-list-type:hybrid;
	mso-list-template-ids:709002530 769583332 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Here are my particular reasons for believing that th=
is work is not yet ready. This is primarily to help the authors focus on up=
dating the draft and to provide motivation for those in the WG that feel th=
is is important but did not &#8216;speak
 up&#8217;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">First, I believe this draft has a higher bar than us=
ual because it is standard track work, defines a &#8220;new&#8221; protocol=
, and one that is a grey area for the DHC WG &#8211; it being done here mos=
tly because it uses the DHCPv6 protocol message and
 option format (and relay support). It was adopted by the DHC WG as there w=
as support for doing this work, so it is important that we make sure it con=
cludes.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Jinmei raised some very good points about this work =
and whether it was needed (see
<a href=3D"http://www.ietf.org/mail-archive/web/dhcwg/current/msg15849.html=
">http://www.ietf.org/mail-archive/web/dhcwg/current/msg15849.html</a> and =
this thread as this not the first message). I did chime in during this disc=
ussion to help explain why having
 clients update DNS directly was an issue.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I also think the draft needs to answer why networks =
that won't or can't use DHCPv6 to resolve the DNS issue would actually make=
 use of this solution. The abstract states &quot;One of the most important =
issues in this regard is the inability
 to register such addresses in DNS.&quot; Why is this such an important iss=
ue; if it isn't happening today, why is this needed now (or in the future)?=
 In the introduction there is &quot;One such limitation is related to the i=
nability of nodes with self-generated addresses
 to register their IPv6-address-to-FQDN bindings in DNS.&quot; It goes on t=
o explain the limitation, but not say WHY this is a problem that needs to b=
e solved. Sure, the &quot;problem&quot; being solved is adding these mappin=
gs to DNS; but why is that needed in the first
 place? What will this DNS information be used for (i.e., to allow incoming=
 connections, to help administrators, for &#8216;primitive&#8217; security =
- if the host is in DNS it must be OK, or)? The Introduction does say &#822=
0;In several tightly controlled networks &#8230;&#8221; &#8211; so is
 this a solution for just a few networks?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I had also raised a concern about the lack of addres=
sing the multi-server solution. Sure, RFC 3315 wasn&#8217;t complete on thi=
s (i.e. the failover work). And, certainly one option is to say it is out o=
f scope, but that has its own issues. There
 is an individual submission draft which I had missed (it is in the &#8220;=
Related Internet-Drafts&#8221; section at the bottom of
<a href=3D"http://datatracker.ietf.org/wg/dhc/documents/">http://datatracke=
r.ietf.org/wg/dhc/documents/</a>) &#8211; the draft-que-dhc-dns-multi-dhcp-=
servers-00 document. This is an individual submission (not adopted by the W=
G); it attempts to address the multiple
 servers issue. It is very preliminary. But it does open the question of wh=
ether more could be done in the addr-registration draft for this or whether=
 the addr-registration, by declaring it out of scope, might restrict possib=
le solutions? I&#8217;m not saying that
 this work needs to be folded into the addr-registration draft, but it may =
be worth a few cycles to consider how this may be solved?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">An additional nit found in re-reading parts of the d=
raft:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; Also, there is no way to propagate the<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; address of authoritative name server by any protocols.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">DNS can be used for this so I think this statement i=
s incorrect - query for the SOA? (Yes, there may be cases where this isn&#8=
217;t the &#8216;real&#8217; server that will accept DNS updates &#8211; i.=
e., hidden primary/master.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6CFA7Axmbrcdx04ciscoc_--


From nobody Thu Oct 16 07:53:11 2014
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC9D1A1B01 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 07:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 rBSKMsnTo5m0 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 07:53:08 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE701A1B9B for <dhcwg@ietf.org>; Thu, 16 Oct 2014 07:53:08 -0700 (PDT)
Received: from [192.168.1.63] (c-71-201-198-58.hsd1.il.comcast.net [71.201.198.58]) by toccata.fugue.com (Postfix) with ESMTPSA id E477A238050E for <dhcwg@ietf.org>; Thu, 16 Oct 2014 10:53:07 -0400 (EDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
Date: Thu, 16 Oct 2014 09:53:06 -0500
To: dhcwg <dhcwg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/g_QGDQ2DRJrcHjhcDBLXf_4kiPs
Subject: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 14:53:09 -0000

When a new router is seen that sets the 'O' bit in its RA?   When a new =
prefix is seen, for the same router?   Only when a new link is detected?

I think that it should happen whenever a new prefix is seen for a router =
that's set the O bit, but Lorenzo Colitti thinks that a new prefix =
doesn't (and shouldn't) trigger a new Information Request.

Any thoughts about this?


From nobody Thu Oct 16 08:02:01 2014
Return-Path: <twinters@iol.unh.edu>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94B531A1BC0 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 OrESoDaBorWW for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:01:53 -0700 (PDT)
Received: from mail-qg0-f99.google.com (mail-qg0-f99.google.com [209.85.192.99]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7186C1A1B2B for <dhcwg@ietf.org>; Thu, 16 Oct 2014 08:01:53 -0700 (PDT)
Received: by mail-qg0-f99.google.com with SMTP id e89so458847qgf.6 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 08:01:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=0e6/vwsuq26s8nf2zRdXHGgMYxmt+JlLNhJaKQ1vnh4=; b=GA2oV5Z5gYdLETKquHNX62yI9+kSBPChiSyH3nZngzC06xmPUvVcfyQeeIXMW9MM5e 0J8x0Kl+qzVYjK79d32JSbgJDM4+79CNM0tQfTXTocoQ7CLpoTy+IjA39ZkgCQfyX8c2 j2AHyYlMN5JErw66BZvavGLk/w0UzbdvogDA+z4JAVI0dlQZ15i2T95biiJO8i655xw7 mhr+YpVBeXCieNXi2rTBhQu96XcwcvvnUpRZ2iekaLGjSBForD/QHNvPVFujq3q+ZlQt XQHLeru9oQ+BlSrzE/me2DkKkxXgYnoXUe+IZlGLW0ut5F+TFeCh/67XbixPMFYxzQNz //XQ==
X-Gm-Message-State: ALoCoQkTsRQ689LABia0TtJqUpQ5JhpqpzU+OsO5zL5E6ywRo3Ubm7JKa+ljDZ9RxpOEn+njE6sof+lAXVF9UNzqvLuNrjwz1Q==
X-Received: by 10.140.39.11 with SMTP id u11mr2909756qgu.32.1413471712546; Thu, 16 Oct 2014 08:01:52 -0700 (PDT)
Received: from postal.iol.unh.edu ([2606:4100:3880:1234::84]) by mx.google.com with ESMTP id ig9sm4322313qcb.0.2014.10.16.08.01.51 for <multiple recipients>; Thu, 16 Oct 2014 08:01:52 -0700 (PDT)
X-Relaying-Domain: iol.unh.edu
Received: from optimus.iol.unh.edu (optimus.iol.unh.edu [132.177.118.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by postal.iol.unh.edu (Postfix) with ESMTPSA id B81F442DAF; Thu, 16 Oct 2014 11:01:51 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Timothy Winters <twinters@iol.unh.edu>
In-Reply-To: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
Date: Thu, 16 Oct 2014 11:01:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/6efyoLLSC7QliFyayP0b0TUH7II
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 15:01:56 -0000

Hi Ted,
	 At the IOL I'm not aware of many DHCPv6 clients that trigger =
the DHCPv6 Information Request based on addresses being added.  I could =
see the case of when you lose all Global address (including ULA) a =
device might send one, but I would be surprised if they send when when =
new prefixes are found.   I can look closer into this to see what =
triggers it, give me a couple of days and I'll report back.=20

~Tim

On Oct 16, 2014, at 10:53 AM, Ted Lemon <mellon@fugue.com> wrote:

> When a new router is seen that sets the 'O' bit in its RA?   When a =
new prefix is seen, for the same router?   Only when a new link is =
detected?
>=20
> I think that it should happen whenever a new prefix is seen for a =
router that's set the O bit, but Lorenzo Colitti thinks that a new =
prefix doesn't (and shouldn't) trigger a new Information Request.
>=20
> Any thoughts about this?
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Thu Oct 16 08:25:43 2014
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D88C1A1BF5 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4g0hEts_uceV for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:25:38 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 660ED1A1C02 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 08:25:37 -0700 (PDT)
Received: from [192.168.1.63] (c-71-201-198-58.hsd1.il.comcast.net [71.201.198.58]) by toccata.fugue.com (Postfix) with ESMTPSA id EA11F238050E; Thu, 16 Oct 2014 11:25:35 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu>
Date: Thu, 16 Oct 2014 10:25:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu>
To: Timothy Winters <twinters@iol.unh.edu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/E0Uh51s8r4LF1kuqmxV-EhMdr1M
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 15:25:42 -0000

On Oct 16, 2014, at 10:01 AM, Timothy Winters <twinters@iol.unh.edu> =
wrote:
> 	 At the IOL I'm not aware of many DHCPv6 clients that trigger =
the DHCPv6 Information Request based on addresses being added.  I could =
see the case of when you lose all Global address (including ULA) a =
device might send one, but I would be surprised if they send when when =
new prefixes are found.   I can look closer into this to see what =
triggers it, give me a couple of days and I'll report back.=20

That seems broken, because you probably want to refresh the source =
address selection policy table whenever you see a new prefix.


From nobody Thu Oct 16 08:42:24 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4C911A6EDA for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 JiHO5K0GmMkv for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:42:21 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 410831A3BA2 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 08:42:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1942; q=dns/txt; s=iport; t=1413474141; x=1414683741; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=0vH2WoudEC15LNaadu2DuG1KD6Jz8BziZH1i9LUz5Cg=; b=Ko520BkahQ0M1iwdr1yXcYii0BCEl/T+DGgHW+uB7F3xlftWuMEOKO1m sHEFQyKUdes0QGdwPD8Lhr+qO+4HIBJ5mNdH20MgIsUMjiuilRERz6s3D Krtj88LRW8m5npJuOiBeu1D56xXzq8TZfdqz335d3z3r0KVMsNUJEr/en I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFANvmP1StJV2P/2dsb2JhbABbDoMAU1zMFAqHTQKBFhYBfYQCAQEBBAEBATc0CwwEAgEIDgMEAQEBChQJBycLFAkIAgQBDQUIiDYNylABAQEBAQEBAQEBAQEBAQEBAQEBAQETBJAcMQcGgyeBHgWRf5hSiSKDN0BsgUiBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,732,1406592000"; d="scan'208";a="363795971"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-7.cisco.com with ESMTP; 16 Oct 2014 15:42:20 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s9GFgKYH019322 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Oct 2014 15:42:20 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0195.001; Thu, 16 Oct 2014 10:42:20 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <mellon@fugue.com>, Timothy Winters <twinters@iol.unh.edu>
Thread-Topic: [dhcwg] What triggers a DHCP Information Request?
Thread-Index: AQHP6VWrWvKHW5FHAUC5IyhH1LfPV5wy2p6Q
Date: Thu, 16 Oct 2014 15:42:19 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com>
In-Reply-To: <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/MVArRJ_c6yrEBJiNiVGZyO-CuV0
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 15:42:23 -0000

This might be a good issue to add in the 3315bis issues list - recommendati=
ons on when to initiate an Information-Request based on network changes.

I would guess that most clients trigger it when the refresh time (OPTION_IN=
FORMATION_REFRESH_TIME option) expires or when some application request som=
e data that hasn't been obtained (if the OS has this capability)?

Probably something (at least for the address selection policy table) that s=
hould have been covered in RFC 7078.

The text there is:

   The received information can be considered stale in several cases,
   e.g., when the interface goes down, the DHCP server does not respond
   for a certain amount of time, or the Information Refresh Time has
   expired.

Of course, the list is just 'e.g.' so could include more.

And, there might be some rate limiting that is applicable in case there is =
flapping of the RA prefix information.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Thursday, October 16, 2014 11:26 AM
To: Timothy Winters
Cc: dhcwg
Subject: Re: [dhcwg] What triggers a DHCP Information Request?

On Oct 16, 2014, at 10:01 AM, Timothy Winters <twinters@iol.unh.edu> wrote:
> 	 At the IOL I'm not aware of many DHCPv6 clients that trigger the DHCPv6=
 Information Request based on addresses being added.  I could see the case =
of when you lose all Global address (including ULA) a device might send one=
, but I would be surprised if they send when when new prefixes are found.  =
 I can look closer into this to see what triggers it, give me a couple of d=
ays and I'll report back.=20

That seems broken, because you probably want to refresh the source address =
selection policy table whenever you see a new prefix.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Thu Oct 16 09:28:49 2014
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAAE1A87BA for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 09:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Tgk-bWIR8vtS for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 09:28:39 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9EEEA1A877D for <dhcwg@ietf.org>; Thu, 16 Oct 2014 09:28:39 -0700 (PDT)
Received: from [192.168.1.63] (c-71-201-198-58.hsd1.il.comcast.net [71.201.198.58]) by toccata.fugue.com (Postfix) with ESMTPSA id 6EE8C238050E; Thu, 16 Oct 2014 12:28:38 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com>
Date: Thu, 16 Oct 2014 11:28:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D03DB646-2127-4212-9345-34433F274977@fugue.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/r2_4y44IEyFgksL78kUG1gCq6fU
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 16:28:41 -0000

On Oct 16, 2014, at 10:42 AM, Bernie Volz (volz) <volz@cisco.com> wrote:
> And, there might be some rate limiting that is applicable in case =
there is flapping of the RA prefix information.

I think that the fix there is to fix the RA flapping.   Having a burst =
of DHCP messages might be a useful indicator of network health.


From nobody Thu Oct 16 10:14:44 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 831561A026C for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 10:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 ObiOoe3aQ8ij for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 10:14:38 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C240F1A0282 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 10:14:38 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5362D20031 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 13:15:11 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 4F3F063B40; Thu, 16 Oct 2014 13:14:37 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 34D1963B3F for <dhcwg@ietf.org>; Thu, 16 Oct 2014 13:14:37 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: dhcwg <dhcwg@ietf.org>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 16 Oct 2014 13:14:37 -0400
Message-ID: <16238.1413479677@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/u0VH9XHtpxqIWH-WVwqzsiIIctw
Subject: [dhcwg] DHCPv6 APIs for applications
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 17:14:41 -0000

--=-=-=


Bernie Volz (volz) <volz@cisco.com> wrote:
    > I would guess that most clients trigger it when the refresh time
    > (OPTION_INFORMATION_REFRESH_TIME option) expires or when some
    > application request some data that hasn't been obtained (if the OS has
    > this capability)?

I think that maybe DHC WG should consider if having such an API defined
would be important now... I think that applications *should* be given such an
API would use it more.

I imagine that there are OS (and on Linux, distro-specific) ways to get the
information, but I know of none that let an application request new info.

(In some cases, it should be unified with a service discovery system)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVD/8/ICLcPvd0N1lAQIHMggAnRLxl+u61WHrvSw3Z0qM484Q3emNnnks
04ef53i7Nbo/ie6xIHmuyJpjyQdUGs9BQDBWd/Klsm9QM/60GcMrgQx4KFaPDhft
1Bw4CdZr5QO3NaIZJs0r1QgQTP7IFsBGX1Or4drytM6qnaXpdF/afz9KzyMG4X5C
XTEGax4YCwUS54agfr5hcz/2zM6B/SYamCB/xfeY+DzL9a5R+cCB4BoizFQsClZZ
Rnnf68/b3WKfw+yLfTW7mtSpxbplPtOlcWVZZmY8ivVrbchPJLK1dDxgi91UgGMU
7/DWFYaBjA9OGZfPqhW9T5i6TrnOfMJiGE+ts0jLxJ043wdHK4nIDA==
=Ijo2
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Oct 16 10:34:04 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 549551A1A32 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 10:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 NHIOQFj1hQVe for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 10:34:01 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D64061A03B3 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 10:34:00 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id k14so4270235wgh.19 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 10:33:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=aC3N84xl5QKKTryXgnpQqAhcE3HQdhtkwE8JmufAhsQ=; b=TMAFjEoHYHJty5io1GHcTd4fEzodTqwbddOgIrxj4UWw7X3BRjRfHCkyfjQZ7IqfKa wMRzW51BqQS9Mv6A3M1ZO9iXx3i8+WVz4OYkJWw8t6fMNENO/J9WeRCFs9vSrljxFU7I Pdd9jL5FRmTDzDjPwGm//8GKlTG7PwCXsabBKoympCXK8SV5PXhvAgxzj1yUbGoT2fFd tyxty4mqHSGqFT3NQ0z/Bvx21iBGRk22n2p8CBhbdCgT4gu16XBKkucTs1fjB7kX/97C NF9wYmSSGjQ7CuU/b07qBa1n+mwisT8OyZMm6ZZuBzPJ4D1j7BklRFbxdosMcEakPR80 IjDg==
MIME-Version: 1.0
X-Received: by 10.194.58.8 with SMTP id m8mr3882533wjq.43.1413480839400; Thu, 16 Oct 2014 10:33:59 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.195.13.83 with HTTP; Thu, 16 Oct 2014 10:33:59 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com>
Date: Thu, 16 Oct 2014 10:33:59 -0700
X-Google-Sender-Auth: HylGUTcrcFm93uwVhxGdjg7UvDU
Message-ID: <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/E4GyovFqrj74ZLKjRr_QPZ8Hh54
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 17:34:03 -0000

At Wed, 15 Oct 2014 16:16:36 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> First, I have a couple of higher level points to discuss:
>
> - What's the final goal of this document?
>
> ** The goal here is for this work to be an RFC.

Okay, in that case I'll also check overall readability as a separate
document for future versions.

> Specific comments to the draft text follow:
>
> - Title: now that our main focus is the mixed use of IA_NA and IA_PD
>   rather than generalizing the concept of stateful resources, I think
>   it makes more sense to reflect it in the title, for example,
>   "Issues and Recommendations with Multiple DHCPv6 IA Options".
>   See also my comments on Section 3 (terminology) below.
>
> ** We will leave the title as it is.

Hmm, if we are going to even more focus on the specific case of the
mix of IA_NA and IA_PD as you'll mention below, and also if it's
supposed to be published as a single document, I'd avoid making the
tile too generic.  So, I'd even make it more specific such as

    Issues and Recommendations with Mixed Use of DHCPv6 Address
    Assignment and Prefix Delegation

But it's ultimately up to the authors.  If the authors still thinks
the current title is the best, I won't insist further.

> - Abstract: this is more about readability (see above), but I'm afraid
>   the current abstract text wouldn't be really helpful for first-time
>   readers (on the other hand, it's not a problem for "me", because I
>   already know what it is). [...]
>
> ** We will leave the abstract pretty much as is. We change last sentence =
to mention that the (RFC) changes are to address the identified issues.

Ditto.  But I'll see how the abstract of the next version will look
like.

> - Section 1, regarding the same text and this one:
[...]
>   IMO, this document should talk a bit more about the "framework".
[...]
> ** We will rework the Introduction to remove the 'framework' concept and =
just focus on the IA_NA/IA_PD issues. When and if there are future IA's, th=
ose documents can indicate whether they integrate into this work (i.e., add=
 IA_foo to IA_NA, IA_PD in the stateful issues document) or if they are sep=
arate and independent.

Okay.

> - Section 4.2: replacement for RFC 3315 17.1.3:
>
>      The client MUST ignore any Advertise message that contains no
>      addresses (IAADDR options encapsulated in IA_NA or IA_TA options)
>      and no delegated prefixes (IAPREFIX options encapsulated in IA_PD
>      options, see RFC 3633) with the exception that the client
>      MUST process an included SOL_MAX_RT option (RFC 7083), MUST
>      process an included INF_MAX_RT option (RFC 7083), and MAY
>      display any associated status message(s) to the user.
>
>   It's awkward to see it mention prefixes while this version
>   intentionally cancels the idea of "unified" text for renew/rebind.
>   It's not clear to me why Section 17.1.3 (regarding advertise) still
>   needs to provide "unified" text.
>
> ** While we could drop "and no delegated prefixes (...)", does that reall=
y help significantly especially since RFC 7083 material is being pulled in =
already? Also, in this case if we leave it out, people may be confused abou=
t what happens if there are no addresses but prefixes. (For most of the oth=
er changes later, RFC 3633 already covers these changes as it generally imp=
lies to replace "addresses" with "delegated prefixes" in much of the Reply =
processing. And, we've provided the revised text where needed for 3633.) Al=
so, RFC 3633 already points to 17.1.3 of 3315 and this avoids having to spe=
cify replacement text for 3633.

I wouldn't necessarily insist on it, it just looks awkward to me but
otherwise is not really a problem.  Maybe it helps if you note that
you're providing unified text with the reason of why (e.g., because
RFC 3633 doesn't describe its own version of this behavior but just
refers to RFC 3315.)

> - Section 4.3: I don't understand the following text:
>
>    [...] To deal
>    with the case where servers have not yet been updated to do that,
>    clients MUST use the shortest (explicit or implicit) T1/T2 times
>    (larger than 0), from the same IA option, in the Reply.  T1/T2 times
>    from other IAs are ignored.
>
>   I guess it tries to address the corner case I pointed out for the
>   previous version of the draft:
>   http://www.ietf.org/mail-archive/web/dhcwg/current/msg15663.html
>   but I don't even understand what the client would do in this case
>   based on the new text.  To recap, what should happen if the client
>   sees the following two sets of T1/T2 according to the above text?
>   - T1a =3D 10, T2a =3D 20
>   - T1b =3D 0, T2b =3D 5
>
> ** We will include this example and explain it. Note that T1b  =3D 0 mean=
s that the client must calculate the T1 time (50% of lifetime) and that it =
obviously needs to be less than T2b. So, in this case the T1b =3D0, T2b =3D=
 5 would be used but the T1b time is the 'implicit' time (we can't give the=
 value since the lifetimes are not specified).

Hmm, then the phrase "(larger than 0)" can be misleading.

> ** There are perhaps other cases, for example T1a =3D 10, T2a =3D 20, T1b=
 =3D 5, T2b =3D 25 that are a bit more interesting since picking (b) means =
T1=3D5/T2=3D25 which means T2 is longer than T2a.

Personally, I'm okay with just dismissing such a case as a server
misconfiguration (as we basically require the server use the same
T1/T2 values for all IAs).  I'd be fine unless a compliant client
behavior leads to a clearly broken result, such as T1 > T2.

> ** Perhaps we need to review whether the shortest 'effective' T1 and inde=
pendently shortest 'effective' T2 are a better choice (obviously the client=
 would have to adjust T1 if this means T1>T2, but I'm not sure that could e=
ven happen since for any individual IA, T1 must be less than or equal to T2=
). Note that by 'effective' here I mean either the server supplied value or=
, if 0, the client determined value based on the lifetimes within that IA. =
 If we used that algorithm, for your case the answer would not change; for =
my example T1 would be and T2 would be 20 which are probably better values =
for this case.

See above.  IMO it doesn't have to be too complicated and we can
basically leave it to the diligence of the server
implementation/operation.  All I want to see is a clear and
well-defined client behavior.

> ** Comments about this issue (and perhaps additional case analysis if app=
ropriate) would be useful.
>
> - Section 4.4.5: does this mean, if the client has bindings of
>   multiple IAs, it should (effectively) abandon all of the bindings
>   and establish new bindings for all of the IAs starting from Solicit?
>   If so, it makes sense to me, but it's not really clear from the
>   text, and I suggest clarifying that point.
>
>      When the client receives a NotOnLink status from the server in
>      response to a Confirm message, the client performs DHCP server
>      solicitation, as described in section 17, and client-initiated
>      configuration as described in section 18.
>
> ** We will create a 3315bis ticket since this is pre-existing text used "=
as is" from 3315. And, this is not an issue that is particular to this draf=
t. Note that Confirm is IA_NA (IA_TA) specific as IA_PD requires a Rebind; =
so this is an open issue in the original 3315 and should be added by the bi=
s document. It also is more of a clarification, rather than a "change". The=
 bis document can clarify that when a client sends a Solicit, it MUST not b=
e using any of the addresses or delegated prefixes for the bindings include=
d in the Solicit.

I'm not sure if I understand this as a response to my comment...to
clarify my point, what I wanted to raise is what should happen if:

- A client with bindings for both an IA_NA and an IA_PD detects it may
  have moved to a different link, so sends a Confirm for the IA_NA.
- The client receives a NotOnLink status in response to it.

Should the client (effectively) discards the binding for IA_PD (and
for IA_NA) and try to establish new bindings for both?  Or should it
keep the binding for IA_PD (but it would break the proposed model of
this draft)?  I thought the intent is the former, and I thought it's
not clear enough and suggested to clarify it in the text.

--
JINMEI, Tatuya


From nobody Thu Oct 16 10:42:22 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 722781A1B15 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 10:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 BJBWcSim9a4m for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 10:42:19 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D6A41A1A53 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 10:42:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13692; q=dns/txt; s=iport; t=1413481339; x=1414690939; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=jEfd5txnd5VRWGm1Uubk5Km7o60NfXWgH8mn0cme7ls=; b=W5SfvwJbv1CTU9pUqTYs4cQP1cWLyWvHh3oSM1OeOh7SfTO2M8nhKY4x XVULLg/Bsai/0IalKkLfULkf1rv9tm+oH2srLcOYuTbA/2eLPBSQONFWE 42O8cbTv226Gh27ulBi/Afywclu6/OmVANE2aVXTc6SK5SaSnmDLwDpZP 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAEcCQFStJA2N/2dsb2JhbABbgkhGU1zMIIdNAoEXFgFyC4QCAQEBBC1cAgEIEQMBAQELHQcyFAkIAQEEEwgBiDUNymMBAQEBAQEBAQEBAQEBAQEBAQEBAQEXj2sRAR8gFwGDLYEeBZF/hEaIQoNGig6HGIN3bAGBDjmBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,733,1406592000";  d="scan'208,217";a="360758662"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-9.cisco.com with ESMTP; 16 Oct 2014 17:42:18 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s9GHgILp029589 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 16 Oct 2014 17:42:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Thu, 16 Oct 2014 12:42:18 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: IETF-91 (Honolulu) DHC WG Agenda Items
Thread-Index: Ac/HkCLoS86rZHidSOuuk32ztFklWAh18mCQ
Date: Thu, 16 Oct 2014 17:42:17 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6D174B@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B67C40C@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B67C40C@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6D174Bxmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/GFuatxfkS0vf50phzT3x-AUacyg
Subject: Re: [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 17:42:21 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6D174Bxmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi:

Per the preliminary agenda, we will be meeting on Thursday, November 13 fro=
m 1640-1910 HST.

We are collecting agenda items (see email below as what you should send us =
at dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org> to request t=
ime).

At present we have the following so far (this is subject to change):

DHC WG Agenda for IETF-91 (Honolulu)

Date: Thursday November 13, 1640-1910 HST, Kahili 1/2
Chairs: Tomek Mrugalski & Bernie Volz
Secretary: Sheng Jiang
Presentations materials: https://datatracker.ietf.org/meeting/91/materials.=
html#wg-dhc

1. Co-Chairs - Administrativia (Agenda Bashing, WG Status) - 10 minutes
2. Tomek Mrugalski, DHCPv6bis Update (draft-dhcwg-dhc-rfc3315bis) - 15 minu=
tes
3. Tomek Mrugalski, DHCP privacy considerations (draft TBD) - 20 minutes
4. Marcin Siodelski and Bernie Volz - draft-ietf-dhc-dhcpv6-stateful-issues=
 -15 minutes


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, September 03, 2014 12:01 PM
To: dhcwg@ietf.org
Subject: [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items

Hi:

While it is still 2 months away, we are starting to collect agenda items fo=
r IETF-91's DHC WG session.

Please send us (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org>=
) requests for sessions and include:

Name of session:
Name of draft(s):
Time requested:
Presenter name(s):
Brief description of what issues need discussing and what you hope to accom=
plish by presenting:

More details about the Honolulu IETF can be found at http://www.ietf.org/me=
eting/91/index.html.


-          Tomek & Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1B6D174Bxmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
code
	{mso-style-priority:99;
	font-family:"Courier New";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:125590465;
	mso-list-type:hybrid;
	mso-list-template-ids:-879992944 -17294522 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:3;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1294478240;
	mso-list-type:hybrid;
	mso-list-template-ids:1476817810 264280828 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:2;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Per the preliminary ag=
enda, we will be meeting on Thursday, November 13 from 1640-1910 HST.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We are collecting agen=
da items (see email below as what you should send us at
<a href=3D"mailto:dhc-chairs@tools.ietf.org">dhc-chairs@tools.ietf.org</a> =
to request time).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">At present we have the=
 following so far (this is subject to change):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">DHC WG Agenda for IETF=
-91 (Honolulu)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Date: Thursday Novembe=
r 13, 1640-1910 HST, Kahili 1/2<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Chairs: Tomek Mrugalsk=
i &amp; Bernie Volz<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Secretary: Sheng Jiang=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Presentations material=
s: https://datatracker.ietf.org/meeting/91/materials.html#wg-dhc<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">1. Co-Chairs - Adminis=
trativia (Agenda Bashing, WG Status) - 10 minutes<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">2. Tomek Mrugalski, DH=
CPv6bis Update (draft-dhcwg-dhc-rfc3315bis) - 15 minutes<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">3. Tomek Mrugalski, DH=
CP privacy considerations (draft TBD) - 20 minutes<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">4. Marcin Siodelski an=
d Bernie Volz - draft-ietf-dhc-dhcpv6-stateful-issues -15 minutes<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Wednesday, September 03, 2014 12:01 PM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items<o:p></o:p></=
span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While it is still 2 months away, we are starting to =
collect agenda items for IETF-91&#8217;s DHC WG session.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please send us (<a href=3D"mailto:dhc-chairs@tools.i=
etf.org">dhc-chairs@tools.ietf.org</a>) requests for sessions and include:<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Name of session:<o:p></o:p></p>
<p class=3D"MsoNormal">Name of draft(s):<o:p></o:p></p>
<p class=3D"MsoNormal">Time requested:<o:p></o:p></p>
<p class=3D"MsoNormal">Presenter name(s):<o:p></o:p></p>
<p class=3D"MsoNormal">Brief description of what issues need discussing and=
 what you hope to accomplish by presenting:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">More details about the Honolulu IETF can be found at=
 <a href=3D"http://www.ietf.org/meeting/91/index.html">
http://www.ietf.org/meeting/91/index.html</a>.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Tomek &amp; Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6D174Bxmbrcdx04ciscoc_--


From nobody Thu Oct 16 11:13:38 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6394B1A6FF3 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 11:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 i4TPUK-cK7gU for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 11:13:32 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30EC71A6F8F for <dhcwg@ietf.org>; Thu, 16 Oct 2014 11:13:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16176; q=dns/txt; s=iport; t=1413483212; x=1414692812; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=k2OlMbmIoZZU2EO1NMhsRIvShKttRY6ynS2zsKWOohw=; b=a4TEdqzyNM3UdxfETszKCMFrg51CUXlKV1aelKVrHXfhaYo1+PV3uvXP exN3xooBgMCjiMlI0FpNoJd7/S8KmIYnoDBOXufAotE6kIV84oniwANob 57l8Y/B13kVsYfW3kyFd9ZIIbKTmjkYGTTatdlna8v2BeHZwABXVxXiFF c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAEMKQFStJV2b/2dsb2JhbABbgw5TXIMCtxaSCIdNAht9FgF9hAIBAQEDASMRRQUHBAIBCBEEAQEDAgYdAwICAh8RFAEICAIEDgUIAYghAwkIDbVyjkANhkIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXgSyJI4NKgWMBAQoUFhAGBQcGgnE2gR4Fj2OCHIlHg0GDRopQgliDfoN3bAGBBQQFFyKBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,733,1406592000"; d="scan'208";a="363879864"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-8.cisco.com with ESMTP; 16 Oct 2014 18:13:31 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9GIDVZb018815 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Oct 2014 18:13:31 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Thu, 16 Oct 2014 13:13:30 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
Thread-Index: AQHP4yTrEkD6ExoBZ0O6wM0stZ10wJwxXZPAgAH+sYD//69owA==
Date: Thu, 16 Oct 2014 18:13:30 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com>
In-Reply-To: <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/L3xKGwo6yDKJrp0v859OA6-JiUA
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 18:13:35 -0000

SGk6DQoNClJlZ2FyZGluZzoNCg0KPkhtbSwgdGhlbiB0aGUgcGhyYXNlICIobGFyZ2VyIHRoYW4g
MCkiIGNhbiBiZSBtaXNsZWFkaW5nLg0KDQpXZWxsLCB3aGF0IHRoaXMgd2FzIHRoZXJlIGZvciB3
YXMgdG8gaW5kaWNhdGUgdGhhdCBpZiB0aGVyZSB3ZXJlIG5vIElBQUREUi9JQVBSRUZJWCBvcHRp
b25zIG9yIHRoZSBsaWZldGltZXMgd2VyZSBhbGwgMCwgdGhlICJlZmZlY3RpdmUiIFQxIChhbmQg
VDIpIGZvciB0aGlzIElBX05BIG9yIElBX1BEIHdvdWxkIGJlIDAgYW5kIHdlIHdvdWxkIE5PVCB3
YW50IHRvIHVzZSB0aGF0LiBJZiB0aGUgImVmZmVjdGl2ZSIgVDEgaXMgMCwgd2Ugd2FudCB0aGUg
Y2xpZW50IHRvIHNraXAgdGhhdCBzZXQgb2YgVDEvVDIgdmFsdWVzLg0KDQpJbiB0aGlzIGNhc2Us
IHRoZSBzZXJ2ZXIgd291bGQgaGF2ZSBoYWQgdG8gc2VuZCAwIG5vdCBiZWNhdXNlIGl0IGRpZG4n
dCBjYWxjdWxhdGUgdGhlIFQxL1QyIHZhbHVlcywgYnV0IGJlY2F1c2UgdGhhdCBpcyB3aGF0IHRo
ZSB2YWx1ZXMgYXJlLiBCdXQgdGhlIGNsaWVudCBpcyB0b2xkIHRoYXQgaWYgdGhlc2UgdmFsdWVz
IGFyZSAwLCBpdCBuZWVkcyB0byBjYWxjdWxhdGUgdGhlbSAoZnJvbSB0aGUgbGlmZXRpbWVzIGlu
IHRoYXQgSUEpLiBUaHVzIHRoZSByZXN1bHRpbmcgKCJlZmZlY3RpdmUiKSB2YWx1ZXMgYXJlIDAg
dG9vLiBBbmQgd2UgZG9uJ3Qgd2FudCB0aGUgY2xpZW50IHRvIFJlbmV3L1JlYmluZCBpbW1lZGlh
dGVseT8NCg0KDQpSZWdhcmRpbmcgeW91ciBpc3N1ZSB3aXRoIFNlY3Rpb24gNC40LjUsIGlmIGEg
Y2xpZW50IGhhcyBib3RoIGFuIElBX05BIGFuZCBJQV9QRCwgaXQgdXNlcyB0aGUgUmViaW5kIG1l
c3NhZ2UgLSBub3QgQ29uZmlybSAoc2VlIDQuNSkuDQoNClNvOg0KDQo+SSdtIG5vdCBzdXJlIGlm
IEkgdW5kZXJzdGFuZCB0aGlzIGFzIGEgcmVzcG9uc2UgdG8gbXkgY29tbWVudC4uLnRvIGNsYXJp
ZnkgbXkNCj5wb2ludCwgd2hhdCBJIHdhbnRlZCB0byByYWlzZSBpcyB3aGF0IHNob3VsZCBoYXBw
ZW4gaWY6DQo+DQo+LSBBIGNsaWVudCB3aXRoIGJpbmRpbmdzIGZvciBib3RoIGFuIElBX05BIGFu
ZCBhbiBJQV9QRCBkZXRlY3RzIGl0IG1heQ0KPiAgaGF2ZSBtb3ZlZCB0byBhIGRpZmZlcmVudCBs
aW5rLCBzbyBzZW5kcyBhIENvbmZpcm0gZm9yIHRoZSBJQV9OQS4NCj4tIFRoZSBjbGllbnQgcmVj
ZWl2ZXMgYSBOb3RPbkxpbmsgc3RhdHVzIGluIHJlc3BvbnNlIHRvIGl0Lg0KPg0KPlNob3VsZCB0
aGUgY2xpZW50IChlZmZlY3RpdmVseSkgZGlzY2FyZHMgdGhlIGJpbmRpbmcgZm9yIElBX1BEIChh
bmQgZm9yIElBX05BKQ0KPmFuZCB0cnkgdG8gZXN0YWJsaXNoIG5ldyBiaW5kaW5ncyBmb3IgYm90
aD8gIE9yIHNob3VsZCBpdCBrZWVwIHRoZSBiaW5kaW5nIGZvcg0KPklBX1BEIChidXQgaXQgd291
bGQgYnJlYWsgdGhlIHByb3Bvc2VkIG1vZGVsIG9mIHRoaXMgZHJhZnQpPyAgSSB0aG91Z2h0IHRo
ZQ0KPmludGVudCBpcyB0aGUgZm9ybWVyLCBhbmQgSSB0aG91Z2h0IGl0J3Mgbm90IGNsZWFyIGVu
b3VnaCBhbmQgc3VnZ2VzdGVkIHRvDQo+Y2xhcmlmeSBpdCBpbiB0aGUgdGV4dC4NCg0KQW5kIGZv
ciBSZWJpbmQgcHJvY2Vzc2luZyAoUkZDIDMzMTUsIGJ1dCBhbHNvIGFwcGxpZXMgdG8gMzYzMyk6
DQoNCiAgIElmIHRoZSBzZXJ2ZXIgZmluZHMgdGhhdCBhbnkgb2YgdGhlIGFkZHJlc3NlcyBhcmUg
bm8gbG9uZ2VyDQogICBhcHByb3ByaWF0ZSBmb3IgdGhlIGxpbmsgdG8gd2hpY2ggdGhlIGNsaWVu
dCBpcyBhdHRhY2hlZCwgdGhlIHNlcnZlcg0KICAgcmV0dXJucyB0aGUgYWRkcmVzcyB0byB0aGUg
Y2xpZW50IHdpdGggbGlmZXRpbWVzIG9mIDAuDQoNClRoZSBxdWVzdGlvbiB0aGVuIGlzIHdoYXQg
aGFwcGVucyBpZiB0aGUgY2xpZW50IGVuZHMgdXAgd2l0aCBvbmx5IG5vbi16ZXJvIGxpZmV0aW1l
cyBmb3IgSUFBRERSIG9yIElBUFJFRklYIG9wdGlvbnMsIGJ1dCBub3QgdGhlIG90aGVyIChvciBt
b3JlIHNpbXBseSBzb21lIElBIG9wdGlvbiBlbmRzIHVwIHdpdGggbm8gYWRkcmVzc2VzL3ByZWZp
eGVzLCBidXQgYW5vdGhlciBiaW5kaW5nIG1pZ2h0IGhhdmUgdGhlbSkuDQoNClRoaXMgbWlnaHQg
YmUgc29tZXRoaW5nIHRvIHJldmlldyBpbiB0ZXJtcyBvZiBSRkMgMzMxNSBhcyBJIGRvbid0IHRo
aW5rIGl0IGFkZHJlc3NlcyB0aGlzIHF1ZXN0aW9uLg0KDQpUaGUgcmVwbGFjZW1lbnQgdGV4dCBo
ZXJlICg0LjQuNSwgcmVwbGFjZW1lbnQgdGV4dCBmb3IgU2VjdGlvbiAxOC4xLjggb2YgUkZDIDMz
MTUpOg0KDQogICAgIElmIHRoZSBjbGllbnQgZmluZHMgbm8gdXNhYmxlIGFkZHJlc3NlcyBpbiBh
bnkgSUEsIHRoZSBjbGllbnQgTUFZDQogICAgIHVzZSB0aGUgSW5mb3JtYXRpb24tcmVxdWVzdCBt
ZXNzYWdlIHRvIG9idGFpbiBvdGhlciBjb25maWd1cmF0aW9uDQogICAgIGluZm9ybWF0aW9uIG9u
bHkuDQoNClRoZSAzMzE1IHRleHQgaXM6DQoNCiAgIElmIHRoZSBjbGllbnQgcmVjZWl2ZXMgbm8g
YWRkcmVzc2VzIGluDQogICBhbnkgb2YgdGhlIElBcywgaXQgbWF5IGVpdGhlciB0cnkgYW5vdGhl
ciBzZXJ2ZXIgKHBlcmhhcHMgcmVzdGFydGluZw0KICAgdGhlIERIQ1Agc2VydmVyIGRpc2NvdmVy
eSBwcm9jZXNzKSBvciB1c2UgdGhlIEluZm9ybWF0aW9uLXJlcXVlc3QNCiAgIG1lc3NhZ2UgdG8g
b2J0YWluIG90aGVyIGNvbmZpZ3VyYXRpb24gaW5mb3JtYXRpb24gb25seS4NCg0KU28sIHdlIGNh
biByZXZpc2l0IGhvdyBiZXN0IHRvIGFkZHJlc3MgdGhpcyBidXQgc29tZSBvZiB0aGlzIGFyZSBm
bGF3cyB0aGF0IGFyZSBpbiB0aGUgYmFzZSAzMzE1IGRvY3VtZW50Lg0KDQpUaGlzIGlzIGFsc28g
bW9yZSBzaWduaWZpY2FudCBub3cgdGhhdCBhbGxvY2F0aW5nIG5ldyBhZGRyZXNzZXMgb3IgZGVs
ZWdhdGluZyBuZXcgcHJlZml4ZXMgaXMgcHJvYmxlbWF0aWMgZm9yIGEgUmViaW5kIChzZWUgNC40
LjcuICBVcGRhdGVzIHRvIFNlY3Rpb24gMTguMi40IG9mIFJGQyAzMzE1KSBiZWNhdXNlIG9mIG11
bHRpcGxlIHNlcnZlcnMgcHJvY2Vzc2luZyB0aGUgUmViaW5kLg0KDQpNYXJjaW4gYW5kIEkgd2ls
bCBkaXNjdXNzIHRvIHNlZSB3aGF0IHdlIG1pZ2h0IGRvIGFib3V0IHRoaXMgaXNzdWUuDQoNCi0g
QmVybmllDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBqaW5tZWkudGF0dXlh
QGdtYWlsLmNvbSBbbWFpbHRvOmppbm1laS50YXR1eWFAZ21haWwuY29tXSBPbiBCZWhhbGYgT2Yg
Pz8/Pw0KU2VudDogVGh1cnNkYXksIE9jdG9iZXIgMTYsIDIwMTQgMTozNCBQTQ0KVG86IEJlcm5p
ZSBWb2x6ICh2b2x6KQ0KQ2M6IE1hcmNpbiBTaW9kZWxza2k7IGRoY3dnQGlldGYub3JnDQpTdWJq
ZWN0OiBSZTogW2RoY3dnXSBQbGVhc2UgcmV2aWV3IHZlcnNpb24gLTA3IG9mIGRyYWZ0LWlldGYt
ZGhjLWRoY3B2Ni1zdGF0ZWZ1bC1pc3N1ZXMNCg0KQXQgV2VkLCAxNSBPY3QgMjAxNCAxNjoxNjoz
NiArMDAwMCwNCiJCZXJuaWUgVm9seiAodm9seikiIDx2b2x6QGNpc2NvLmNvbT4gd3JvdGU6DQoN
Cj4gRmlyc3QsIEkgaGF2ZSBhIGNvdXBsZSBvZiBoaWdoZXIgbGV2ZWwgcG9pbnRzIHRvIGRpc2N1
c3M6DQo+DQo+IC0gV2hhdCdzIHRoZSBmaW5hbCBnb2FsIG9mIHRoaXMgZG9jdW1lbnQ/DQo+DQo+
ICoqIFRoZSBnb2FsIGhlcmUgaXMgZm9yIHRoaXMgd29yayB0byBiZSBhbiBSRkMuDQoNCk9rYXks
IGluIHRoYXQgY2FzZSBJJ2xsIGFsc28gY2hlY2sgb3ZlcmFsbCByZWFkYWJpbGl0eSBhcyBhIHNl
cGFyYXRlIGRvY3VtZW50IGZvciBmdXR1cmUgdmVyc2lvbnMuDQoNCj4gU3BlY2lmaWMgY29tbWVu
dHMgdG8gdGhlIGRyYWZ0IHRleHQgZm9sbG93Og0KPg0KPiAtIFRpdGxlOiBub3cgdGhhdCBvdXIg
bWFpbiBmb2N1cyBpcyB0aGUgbWl4ZWQgdXNlIG9mIElBX05BIGFuZCBJQV9QRA0KPiAgIHJhdGhl
ciB0aGFuIGdlbmVyYWxpemluZyB0aGUgY29uY2VwdCBvZiBzdGF0ZWZ1bCByZXNvdXJjZXMsIEkg
dGhpbmsNCj4gICBpdCBtYWtlcyBtb3JlIHNlbnNlIHRvIHJlZmxlY3QgaXQgaW4gdGhlIHRpdGxl
LCBmb3IgZXhhbXBsZSwNCj4gICAiSXNzdWVzIGFuZCBSZWNvbW1lbmRhdGlvbnMgd2l0aCBNdWx0
aXBsZSBESENQdjYgSUEgT3B0aW9ucyIuDQo+ICAgU2VlIGFsc28gbXkgY29tbWVudHMgb24gU2Vj
dGlvbiAzICh0ZXJtaW5vbG9neSkgYmVsb3cuDQo+DQo+ICoqIFdlIHdpbGwgbGVhdmUgdGhlIHRp
dGxlIGFzIGl0IGlzLg0KDQpIbW0sIGlmIHdlIGFyZSBnb2luZyB0byBldmVuIG1vcmUgZm9jdXMg
b24gdGhlIHNwZWNpZmljIGNhc2Ugb2YgdGhlIG1peCBvZiBJQV9OQSBhbmQgSUFfUEQgYXMgeW91
J2xsIG1lbnRpb24gYmVsb3csIGFuZCBhbHNvIGlmIGl0J3Mgc3VwcG9zZWQgdG8gYmUgcHVibGlz
aGVkIGFzIGEgc2luZ2xlIGRvY3VtZW50LCBJJ2QgYXZvaWQgbWFraW5nIHRoZSB0aWxlIHRvbyBn
ZW5lcmljLiAgU28sIEknZCBldmVuIG1ha2UgaXQgbW9yZSBzcGVjaWZpYyBzdWNoIGFzDQoNCiAg
ICBJc3N1ZXMgYW5kIFJlY29tbWVuZGF0aW9ucyB3aXRoIE1peGVkIFVzZSBvZiBESENQdjYgQWRk
cmVzcw0KICAgIEFzc2lnbm1lbnQgYW5kIFByZWZpeCBEZWxlZ2F0aW9uDQoNCkJ1dCBpdCdzIHVs
dGltYXRlbHkgdXAgdG8gdGhlIGF1dGhvcnMuICBJZiB0aGUgYXV0aG9ycyBzdGlsbCB0aGlua3Mg
dGhlIGN1cnJlbnQgdGl0bGUgaXMgdGhlIGJlc3QsIEkgd29uJ3QgaW5zaXN0IGZ1cnRoZXIuDQoN
Cj4gLSBBYnN0cmFjdDogdGhpcyBpcyBtb3JlIGFib3V0IHJlYWRhYmlsaXR5IChzZWUgYWJvdmUp
LCBidXQgSSdtIGFmcmFpZA0KPiAgIHRoZSBjdXJyZW50IGFic3RyYWN0IHRleHQgd291bGRuJ3Qg
YmUgcmVhbGx5IGhlbHBmdWwgZm9yIGZpcnN0LXRpbWUNCj4gICByZWFkZXJzIChvbiB0aGUgb3Ro
ZXIgaGFuZCwgaXQncyBub3QgYSBwcm9ibGVtIGZvciAibWUiLCBiZWNhdXNlIEkNCj4gICBhbHJl
YWR5IGtub3cgd2hhdCBpdCBpcykuIFsuLi5dDQo+DQo+ICoqIFdlIHdpbGwgbGVhdmUgdGhlIGFi
c3RyYWN0IHByZXR0eSBtdWNoIGFzIGlzLiBXZSBjaGFuZ2UgbGFzdCBzZW50ZW5jZSB0byBtZW50
aW9uIHRoYXQgdGhlIChSRkMpIGNoYW5nZXMgYXJlIHRvIGFkZHJlc3MgdGhlIGlkZW50aWZpZWQg
aXNzdWVzLg0KDQpEaXR0by4gIEJ1dCBJJ2xsIHNlZSBob3cgdGhlIGFic3RyYWN0IG9mIHRoZSBu
ZXh0IHZlcnNpb24gd2lsbCBsb29rIGxpa2UuDQoNCj4gLSBTZWN0aW9uIDEsIHJlZ2FyZGluZyB0
aGUgc2FtZSB0ZXh0IGFuZCB0aGlzIG9uZToNClsuLi5dDQo+ICAgSU1PLCB0aGlzIGRvY3VtZW50
IHNob3VsZCB0YWxrIGEgYml0IG1vcmUgYWJvdXQgdGhlICJmcmFtZXdvcmsiLg0KWy4uLl0NCj4g
KiogV2Ugd2lsbCByZXdvcmsgdGhlIEludHJvZHVjdGlvbiB0byByZW1vdmUgdGhlICdmcmFtZXdv
cmsnIGNvbmNlcHQgYW5kIGp1c3QgZm9jdXMgb24gdGhlIElBX05BL0lBX1BEIGlzc3Vlcy4gV2hl
biBhbmQgaWYgdGhlcmUgYXJlIGZ1dHVyZSBJQSdzLCB0aG9zZSBkb2N1bWVudHMgY2FuIGluZGlj
YXRlIHdoZXRoZXIgdGhleSBpbnRlZ3JhdGUgaW50byB0aGlzIHdvcmsgKGkuZS4sIGFkZCBJQV9m
b28gdG8gSUFfTkEsIElBX1BEIGluIHRoZSBzdGF0ZWZ1bCBpc3N1ZXMgZG9jdW1lbnQpIG9yIGlm
IHRoZXkgYXJlIHNlcGFyYXRlIGFuZCBpbmRlcGVuZGVudC4NCg0KT2theS4NCg0KPiAtIFNlY3Rp
b24gNC4yOiByZXBsYWNlbWVudCBmb3IgUkZDIDMzMTUgMTcuMS4zOg0KPg0KPiAgICAgIFRoZSBj
bGllbnQgTVVTVCBpZ25vcmUgYW55IEFkdmVydGlzZSBtZXNzYWdlIHRoYXQgY29udGFpbnMgbm8N
Cj4gICAgICBhZGRyZXNzZXMgKElBQUREUiBvcHRpb25zIGVuY2Fwc3VsYXRlZCBpbiBJQV9OQSBv
ciBJQV9UQSBvcHRpb25zKQ0KPiAgICAgIGFuZCBubyBkZWxlZ2F0ZWQgcHJlZml4ZXMgKElBUFJF
RklYIG9wdGlvbnMgZW5jYXBzdWxhdGVkIGluIElBX1BEDQo+ICAgICAgb3B0aW9ucywgc2VlIFJG
QyAzNjMzKSB3aXRoIHRoZSBleGNlcHRpb24gdGhhdCB0aGUgY2xpZW50DQo+ICAgICAgTVVTVCBw
cm9jZXNzIGFuIGluY2x1ZGVkIFNPTF9NQVhfUlQgb3B0aW9uIChSRkMgNzA4MyksIE1VU1QNCj4g
ICAgICBwcm9jZXNzIGFuIGluY2x1ZGVkIElORl9NQVhfUlQgb3B0aW9uIChSRkMgNzA4MyksIGFu
ZCBNQVkNCj4gICAgICBkaXNwbGF5IGFueSBhc3NvY2lhdGVkIHN0YXR1cyBtZXNzYWdlKHMpIHRv
IHRoZSB1c2VyLg0KPg0KPiAgIEl0J3MgYXdrd2FyZCB0byBzZWUgaXQgbWVudGlvbiBwcmVmaXhl
cyB3aGlsZSB0aGlzIHZlcnNpb24NCj4gICBpbnRlbnRpb25hbGx5IGNhbmNlbHMgdGhlIGlkZWEg
b2YgInVuaWZpZWQiIHRleHQgZm9yIHJlbmV3L3JlYmluZC4NCj4gICBJdCdzIG5vdCBjbGVhciB0
byBtZSB3aHkgU2VjdGlvbiAxNy4xLjMgKHJlZ2FyZGluZyBhZHZlcnRpc2UpIHN0aWxsDQo+ICAg
bmVlZHMgdG8gcHJvdmlkZSAidW5pZmllZCIgdGV4dC4NCj4NCj4gKiogV2hpbGUgd2UgY291bGQg
ZHJvcCAiYW5kIG5vIGRlbGVnYXRlZCBwcmVmaXhlcyAoLi4uKSIsIGRvZXMgdGhhdCByZWFsbHkg
aGVscCBzaWduaWZpY2FudGx5IGVzcGVjaWFsbHkgc2luY2UgUkZDIDcwODMgbWF0ZXJpYWwgaXMg
YmVpbmcgcHVsbGVkIGluIGFscmVhZHk/IEFsc28sIGluIHRoaXMgY2FzZSBpZiB3ZSBsZWF2ZSBp
dCBvdXQsIHBlb3BsZSBtYXkgYmUgY29uZnVzZWQgYWJvdXQgd2hhdCBoYXBwZW5zIGlmIHRoZXJl
IGFyZSBubyBhZGRyZXNzZXMgYnV0IHByZWZpeGVzLiAoRm9yIG1vc3Qgb2YgdGhlIG90aGVyIGNo
YW5nZXMgbGF0ZXIsIFJGQyAzNjMzIGFscmVhZHkgY292ZXJzIHRoZXNlIGNoYW5nZXMgYXMgaXQg
Z2VuZXJhbGx5IGltcGxpZXMgdG8gcmVwbGFjZSAiYWRkcmVzc2VzIiB3aXRoICJkZWxlZ2F0ZWQg
cHJlZml4ZXMiIGluIG11Y2ggb2YgdGhlIFJlcGx5IHByb2Nlc3NpbmcuIEFuZCwgd2UndmUgcHJv
dmlkZWQgdGhlIHJldmlzZWQgdGV4dCB3aGVyZSBuZWVkZWQgZm9yIDM2MzMuKSBBbHNvLCBSRkMg
MzYzMyBhbHJlYWR5IHBvaW50cyB0byAxNy4xLjMgb2YgMzMxNSBhbmQgdGhpcyBhdm9pZHMgaGF2
aW5nIHRvIHNwZWNpZnkgcmVwbGFjZW1lbnQgdGV4dCBmb3IgMzYzMy4NCg0KSSB3b3VsZG4ndCBu
ZWNlc3NhcmlseSBpbnNpc3Qgb24gaXQsIGl0IGp1c3QgbG9va3MgYXdrd2FyZCB0byBtZSBidXQg
b3RoZXJ3aXNlIGlzIG5vdCByZWFsbHkgYSBwcm9ibGVtLiAgTWF5YmUgaXQgaGVscHMgaWYgeW91
IG5vdGUgdGhhdCB5b3UncmUgcHJvdmlkaW5nIHVuaWZpZWQgdGV4dCB3aXRoIHRoZSByZWFzb24g
b2Ygd2h5IChlLmcuLCBiZWNhdXNlIFJGQyAzNjMzIGRvZXNuJ3QgZGVzY3JpYmUgaXRzIG93biB2
ZXJzaW9uIG9mIHRoaXMgYmVoYXZpb3IgYnV0IGp1c3QgcmVmZXJzIHRvIFJGQyAzMzE1LikNCg0K
PiAtIFNlY3Rpb24gNC4zOiBJIGRvbid0IHVuZGVyc3RhbmQgdGhlIGZvbGxvd2luZyB0ZXh0Og0K
Pg0KPiAgICBbLi4uXSBUbyBkZWFsDQo+ICAgIHdpdGggdGhlIGNhc2Ugd2hlcmUgc2VydmVycyBo
YXZlIG5vdCB5ZXQgYmVlbiB1cGRhdGVkIHRvIGRvIHRoYXQsDQo+ICAgIGNsaWVudHMgTVVTVCB1
c2UgdGhlIHNob3J0ZXN0IChleHBsaWNpdCBvciBpbXBsaWNpdCkgVDEvVDIgdGltZXMNCj4gICAg
KGxhcmdlciB0aGFuIDApLCBmcm9tIHRoZSBzYW1lIElBIG9wdGlvbiwgaW4gdGhlIFJlcGx5LiAg
VDEvVDIgdGltZXMNCj4gICAgZnJvbSBvdGhlciBJQXMgYXJlIGlnbm9yZWQuDQo+DQo+ICAgSSBn
dWVzcyBpdCB0cmllcyB0byBhZGRyZXNzIHRoZSBjb3JuZXIgY2FzZSBJIHBvaW50ZWQgb3V0IGZv
ciB0aGUNCj4gICBwcmV2aW91cyB2ZXJzaW9uIG9mIHRoZSBkcmFmdDoNCj4gICBodHRwOi8vd3d3
LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvZGhjd2cvY3VycmVudC9tc2cxNTY2My5odG1sDQo+
ICAgYnV0IEkgZG9uJ3QgZXZlbiB1bmRlcnN0YW5kIHdoYXQgdGhlIGNsaWVudCB3b3VsZCBkbyBp
biB0aGlzIGNhc2UNCj4gICBiYXNlZCBvbiB0aGUgbmV3IHRleHQuICBUbyByZWNhcCwgd2hhdCBz
aG91bGQgaGFwcGVuIGlmIHRoZSBjbGllbnQNCj4gICBzZWVzIHRoZSBmb2xsb3dpbmcgdHdvIHNl
dHMgb2YgVDEvVDIgYWNjb3JkaW5nIHRvIHRoZSBhYm92ZSB0ZXh0Pw0KPiAgIC0gVDFhID0gMTAs
IFQyYSA9IDIwDQo+ICAgLSBUMWIgPSAwLCBUMmIgPSA1DQo+DQo+ICoqIFdlIHdpbGwgaW5jbHVk
ZSB0aGlzIGV4YW1wbGUgYW5kIGV4cGxhaW4gaXQuIE5vdGUgdGhhdCBUMWIgID0gMCBtZWFucyB0
aGF0IHRoZSBjbGllbnQgbXVzdCBjYWxjdWxhdGUgdGhlIFQxIHRpbWUgKDUwJSBvZiBsaWZldGlt
ZSkgYW5kIHRoYXQgaXQgb2J2aW91c2x5IG5lZWRzIHRvIGJlIGxlc3MgdGhhbiBUMmIuIFNvLCBp
biB0aGlzIGNhc2UgdGhlIFQxYiA9MCwgVDJiID0gNSB3b3VsZCBiZSB1c2VkIGJ1dCB0aGUgVDFi
IHRpbWUgaXMgdGhlICdpbXBsaWNpdCcgdGltZSAod2UgY2FuJ3QgZ2l2ZSB0aGUgdmFsdWUgc2lu
Y2UgdGhlIGxpZmV0aW1lcyBhcmUgbm90IHNwZWNpZmllZCkuDQoNCkhtbSwgdGhlbiB0aGUgcGhy
YXNlICIobGFyZ2VyIHRoYW4gMCkiIGNhbiBiZSBtaXNsZWFkaW5nLg0KDQo+ICoqIFRoZXJlIGFy
ZSBwZXJoYXBzIG90aGVyIGNhc2VzLCBmb3IgZXhhbXBsZSBUMWEgPSAxMCwgVDJhID0gMjAsIFQx
YiA9IDUsIFQyYiA9IDI1IHRoYXQgYXJlIGEgYml0IG1vcmUgaW50ZXJlc3Rpbmcgc2luY2UgcGlj
a2luZyAoYikgbWVhbnMgVDE9NS9UMj0yNSB3aGljaCBtZWFucyBUMiBpcyBsb25nZXIgdGhhbiBU
MmEuDQoNClBlcnNvbmFsbHksIEknbSBva2F5IHdpdGgganVzdCBkaXNtaXNzaW5nIHN1Y2ggYSBj
YXNlIGFzIGEgc2VydmVyIG1pc2NvbmZpZ3VyYXRpb24gKGFzIHdlIGJhc2ljYWxseSByZXF1aXJl
IHRoZSBzZXJ2ZXIgdXNlIHRoZSBzYW1lDQpUMS9UMiB2YWx1ZXMgZm9yIGFsbCBJQXMpLiAgSSdk
IGJlIGZpbmUgdW5sZXNzIGEgY29tcGxpYW50IGNsaWVudCBiZWhhdmlvciBsZWFkcyB0byBhIGNs
ZWFybHkgYnJva2VuIHJlc3VsdCwgc3VjaCBhcyBUMSA+IFQyLg0KDQo+ICoqIFBlcmhhcHMgd2Ug
bmVlZCB0byByZXZpZXcgd2hldGhlciB0aGUgc2hvcnRlc3QgJ2VmZmVjdGl2ZScgVDEgYW5kIGlu
ZGVwZW5kZW50bHkgc2hvcnRlc3QgJ2VmZmVjdGl2ZScgVDIgYXJlIGEgYmV0dGVyIGNob2ljZSAo
b2J2aW91c2x5IHRoZSBjbGllbnQgd291bGQgaGF2ZSB0byBhZGp1c3QgVDEgaWYgdGhpcyBtZWFu
cyBUMT5UMiwgYnV0IEknbSBub3Qgc3VyZSB0aGF0IGNvdWxkIGV2ZW4gaGFwcGVuIHNpbmNlIGZv
ciBhbnkgaW5kaXZpZHVhbCBJQSwgVDEgbXVzdCBiZSBsZXNzIHRoYW4gb3IgZXF1YWwgdG8gVDIp
LiBOb3RlIHRoYXQgYnkgJ2VmZmVjdGl2ZScgaGVyZSBJIG1lYW4gZWl0aGVyIHRoZSBzZXJ2ZXIg
c3VwcGxpZWQgdmFsdWUgb3IsIGlmIDAsIHRoZSBjbGllbnQgZGV0ZXJtaW5lZCB2YWx1ZSBiYXNl
ZCBvbiB0aGUgbGlmZXRpbWVzIHdpdGhpbiB0aGF0IElBLiAgSWYgd2UgdXNlZCB0aGF0IGFsZ29y
aXRobSwgZm9yIHlvdXIgY2FzZSB0aGUgYW5zd2VyIHdvdWxkIG5vdCBjaGFuZ2U7IGZvciBteSBl
eGFtcGxlIFQxIHdvdWxkIGJlIGFuZCBUMiB3b3VsZCBiZSAyMCB3aGljaCBhcmUgcHJvYmFibHkg
YmV0dGVyIHZhbHVlcyBmb3IgdGhpcyBjYXNlLg0KDQpTZWUgYWJvdmUuICBJTU8gaXQgZG9lc24n
dCBoYXZlIHRvIGJlIHRvbyBjb21wbGljYXRlZCBhbmQgd2UgY2FuIGJhc2ljYWxseSBsZWF2ZSBp
dCB0byB0aGUgZGlsaWdlbmNlIG9mIHRoZSBzZXJ2ZXIgaW1wbGVtZW50YXRpb24vb3BlcmF0aW9u
LiAgQWxsIEkgd2FudCB0byBzZWUgaXMgYSBjbGVhciBhbmQgd2VsbC1kZWZpbmVkIGNsaWVudCBi
ZWhhdmlvci4NCg0KPiAqKiBDb21tZW50cyBhYm91dCB0aGlzIGlzc3VlIChhbmQgcGVyaGFwcyBh
ZGRpdGlvbmFsIGNhc2UgYW5hbHlzaXMgaWYgYXBwcm9wcmlhdGUpIHdvdWxkIGJlIHVzZWZ1bC4N
Cj4NCj4gLSBTZWN0aW9uIDQuNC41OiBkb2VzIHRoaXMgbWVhbiwgaWYgdGhlIGNsaWVudCBoYXMg
YmluZGluZ3Mgb2YNCj4gICBtdWx0aXBsZSBJQXMsIGl0IHNob3VsZCAoZWZmZWN0aXZlbHkpIGFi
YW5kb24gYWxsIG9mIHRoZSBiaW5kaW5ncw0KPiAgIGFuZCBlc3RhYmxpc2ggbmV3IGJpbmRpbmdz
IGZvciBhbGwgb2YgdGhlIElBcyBzdGFydGluZyBmcm9tIFNvbGljaXQ/DQo+ICAgSWYgc28sIGl0
IG1ha2VzIHNlbnNlIHRvIG1lLCBidXQgaXQncyBub3QgcmVhbGx5IGNsZWFyIGZyb20gdGhlDQo+
ICAgdGV4dCwgYW5kIEkgc3VnZ2VzdCBjbGFyaWZ5aW5nIHRoYXQgcG9pbnQuDQo+DQo+ICAgICAg
V2hlbiB0aGUgY2xpZW50IHJlY2VpdmVzIGEgTm90T25MaW5rIHN0YXR1cyBmcm9tIHRoZSBzZXJ2
ZXIgaW4NCj4gICAgICByZXNwb25zZSB0byBhIENvbmZpcm0gbWVzc2FnZSwgdGhlIGNsaWVudCBw
ZXJmb3JtcyBESENQIHNlcnZlcg0KPiAgICAgIHNvbGljaXRhdGlvbiwgYXMgZGVzY3JpYmVkIGlu
IHNlY3Rpb24gMTcsIGFuZCBjbGllbnQtaW5pdGlhdGVkDQo+ICAgICAgY29uZmlndXJhdGlvbiBh
cyBkZXNjcmliZWQgaW4gc2VjdGlvbiAxOC4NCj4NCj4gKiogV2Ugd2lsbCBjcmVhdGUgYSAzMzE1
YmlzIHRpY2tldCBzaW5jZSB0aGlzIGlzIHByZS1leGlzdGluZyB0ZXh0IHVzZWQgImFzIGlzIiBm
cm9tIDMzMTUuIEFuZCwgdGhpcyBpcyBub3QgYW4gaXNzdWUgdGhhdCBpcyBwYXJ0aWN1bGFyIHRv
IHRoaXMgZHJhZnQuIE5vdGUgdGhhdCBDb25maXJtIGlzIElBX05BIChJQV9UQSkgc3BlY2lmaWMg
YXMgSUFfUEQgcmVxdWlyZXMgYSBSZWJpbmQ7IHNvIHRoaXMgaXMgYW4gb3BlbiBpc3N1ZSBpbiB0
aGUgb3JpZ2luYWwgMzMxNSBhbmQgc2hvdWxkIGJlIGFkZGVkIGJ5IHRoZSBiaXMgZG9jdW1lbnQu
IEl0IGFsc28gaXMgbW9yZSBvZiBhIGNsYXJpZmljYXRpb24sIHJhdGhlciB0aGFuIGEgImNoYW5n
ZSIuIFRoZSBiaXMgZG9jdW1lbnQgY2FuIGNsYXJpZnkgdGhhdCB3aGVuIGEgY2xpZW50IHNlbmRz
IGEgU29saWNpdCwgaXQgTVVTVCBub3QgYmUgdXNpbmcgYW55IG9mIHRoZSBhZGRyZXNzZXMgb3Ig
ZGVsZWdhdGVkIHByZWZpeGVzIGZvciB0aGUgYmluZGluZ3MgaW5jbHVkZWQgaW4gdGhlIFNvbGlj
aXQuDQoNCkknbSBub3Qgc3VyZSBpZiBJIHVuZGVyc3RhbmQgdGhpcyBhcyBhIHJlc3BvbnNlIHRv
IG15IGNvbW1lbnQuLi50byBjbGFyaWZ5IG15IHBvaW50LCB3aGF0IEkgd2FudGVkIHRvIHJhaXNl
IGlzIHdoYXQgc2hvdWxkIGhhcHBlbiBpZjoNCg0KLSBBIGNsaWVudCB3aXRoIGJpbmRpbmdzIGZv
ciBib3RoIGFuIElBX05BIGFuZCBhbiBJQV9QRCBkZXRlY3RzIGl0IG1heQ0KICBoYXZlIG1vdmVk
IHRvIGEgZGlmZmVyZW50IGxpbmssIHNvIHNlbmRzIGEgQ29uZmlybSBmb3IgdGhlIElBX05BLg0K
LSBUaGUgY2xpZW50IHJlY2VpdmVzIGEgTm90T25MaW5rIHN0YXR1cyBpbiByZXNwb25zZSB0byBp
dC4NCg0KU2hvdWxkIHRoZSBjbGllbnQgKGVmZmVjdGl2ZWx5KSBkaXNjYXJkcyB0aGUgYmluZGlu
ZyBmb3IgSUFfUEQgKGFuZCBmb3IgSUFfTkEpIGFuZCB0cnkgdG8gZXN0YWJsaXNoIG5ldyBiaW5k
aW5ncyBmb3IgYm90aD8gIE9yIHNob3VsZCBpdCBrZWVwIHRoZSBiaW5kaW5nIGZvciBJQV9QRCAo
YnV0IGl0IHdvdWxkIGJyZWFrIHRoZSBwcm9wb3NlZCBtb2RlbCBvZiB0aGlzIGRyYWZ0KT8gIEkg
dGhvdWdodCB0aGUgaW50ZW50IGlzIHRoZSBmb3JtZXIsIGFuZCBJIHRob3VnaHQgaXQncyBub3Qg
Y2xlYXIgZW5vdWdoIGFuZCBzdWdnZXN0ZWQgdG8gY2xhcmlmeSBpdCBpbiB0aGUgdGV4dC4NCg0K
LS0NCkpJTk1FSSwgVGF0dXlhDQo=


From nobody Thu Oct 16 11:33:33 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B49371A6FE8 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 11:33:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 NC71YaXZ2tgg for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 11:33:30 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 645271A011E for <dhcwg@ietf.org>; Thu, 16 Oct 2014 11:33:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1281; q=dns/txt; s=iport; t=1413484410; x=1414694010; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=a0aUmFT5J/GqLmlyQwTEWpRJjh26UJgeEZvqDMbSX6A=; b=Js6tn1kdjjpnddJ1m/PwHDLOafgOcuGxtDf0vPyX5YQUuRWByKV5QBdX fKDpp88nvl/anYV6e955GYD/V3IqB6iYYmuN9XkjqcMBqSg3ZdVgGmDHA YLZHHVdyAsQH4ZO2JlN6tgKELphvxXvOixLA0e8OvKWBbS/35YF2CyZad Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAPMOQFStJV2T/2dsb2JhbABbgw5TXMwihndUAoEYFgF9hAIBAQEEOksEAgEIEQQBAQEKFAkHMhQJCAIEARIIiDYNyxUBAQEBAQEBAQEBAQEBAQEBAQEBARiQHDgGgyeBHgWFFYxqhEaIfpQwg3dsAYFHgQIBAQE
X-IronPort-AV: E=Sophos;i="5.04,733,1406592000"; d="scan'208";a="360772438"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-9.cisco.com with ESMTP; 16 Oct 2014 18:33:29 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s9GIXTph030554 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Oct 2014 18:33:29 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Thu, 16 Oct 2014 13:33:29 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHCPv6 APIs for applications
Thread-Index: AQHP6W+u4wpxJvcEy0W8Xyt1F0dl1w==
Date: Thu, 16 Oct 2014 18:33:29 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6D1A47@xmb-rcd-x04.cisco.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com> <16238.1413479677@sandelman.ca>
In-Reply-To: <16238.1413479677@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/SEcniRfCY3hiB0T67dHWLDKFdio
Subject: Re: [dhcwg] DHCPv6 APIs for applications
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 18:33:31 -0000

Here's a link to Microsoft's - http://msdn.microsoft.com/en-us/library/wind=
ows/desktop/aa363351(v=3Dvs.85).aspx.

If you know of others, perhaps worth providing those links.

Perhaps someone has interest in working to define such an API.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Michael Richardson
Sent: Thursday, October 16, 2014 1:15 PM
To: dhcwg
Subject: [dhcwg] DHCPv6 APIs for applications


Bernie Volz (volz) <volz@cisco.com> wrote:
    > I would guess that most clients trigger it when the refresh time
    > (OPTION_INFORMATION_REFRESH_TIME option) expires or when some
    > application request some data that hasn't been obtained (if the OS ha=
s
    > this capability)?

I think that maybe DHC WG should consider if having such an API defined wou=
ld be important now... I think that applications *should* be given such an =
API would use it more.

I imagine that there are OS (and on Linux, distro-specific) ways to get the=
 information, but I know of none that let an application request new info.

(In some cases, it should be unified with a service discovery system)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -=3D =
IPv6 IoT consulting =3D-




From nobody Thu Oct 16 12:08:22 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAFBA1A8707 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 12:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Mp0LJz3D4Qoo for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 12:08:09 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB3711A01D6 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 12:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16106; q=dns/txt; s=iport; t=1413486490; x=1414696090; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=K6Qywo1nRVbo6gA+TnnGV2awIxb9yMOCilaEL1jdnZQ=; b=dm1agZVZ/9WLSz0y1UwwsW8xxUocKP8PkFewklkZNveHXxwKWzirEdCJ e8rQoO57jnpyjOTBzvYQjR9voMn2SVzG5BuoYxxSmX265TJ8iEzDkh4Xn T3QR3wIBtqUQaMstq0mARFXnpAPtW+31bQ7HmP6gXZhTrkyuWpHz0Iwl5 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAG8WQFStJA2D/2dsb2JhbABbgw5TXIMCtxaRfgqHTQKBGBYBfYQCAQEBAwEBAQEeAUwLBQcEAgEIEQQBAQIDBgUYAgMCIQYLFAkIAgQOBQgBEogPAwkIDZlSnEoBjj4NhkIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXgSmJJoNKgV0GAQEKFCYGBQIFBoJuOYEeBY9jghyJR4NBg0aKUIJYg36Dd2wBgQUBAwUXIoECAQEB
X-IronPort-AV: E=Sophos;i="5.04,733,1406592000"; d="scan'208";a="87640402"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-4.cisco.com with ESMTP; 16 Oct 2014 19:08:09 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s9GJ881d028848 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Oct 2014 19:08:08 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Thu, 16 Oct 2014 14:08:08 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
Thread-Index: AQHP4yTrEkD6ExoBZ0O6wM0stZ10wJwxXZPAgAH+sYD//69owIAADawA
Date: Thu, 16 Oct 2014 19:08:07 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6D1B3A@xmb-rcd-x04.cisco.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/uwbqwojX20-IZhniWCegKqeDPLM
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Oct 2014 19:08:14 -0000

I forgot to mention that both of these issues are related - since the issue=
 you raised for 4.4.5 can result in the 0 lifetimes (hence 0 T1/T2).

And, perhaps a result of whatever we work out is that whatever T1/T2 times =
are determined may not be used in this case - if the client, for example, i=
s supposed to take some other action (return to Renew or perhaps restart th=
e configuration process).


Part of the problem with this stateful issues work is that it has exposed a=
 lot of issues that have existed in RFC 3315. And, it seems that the choice=
s at this time are:
1. Ignore some of those issues for now and address in 3315bis (limit scope =
of stateful issues draft),
2. Drop the stateful issues and work only on 3315 bis to fix (hopefully) al=
l of these issues.

The original plan was for the stateful issues draft to provide interim chan=
ges and guidance mostly for the CPE issues, not to correct all of the 3315.=
 This would also be good input to the 3315bis work and we would have agreed=
 upon solutions (and not be debating these during the bis work - of course,=
 the stateful issues turned out to be much more complex and not as quick as=
 we had hoped).


My own feeling is that:
- If a server receives a Solicit or Request, it SHOULD assume that the clie=
nt is NOT using the addresses or prefixes therein.
- If a server receives a Renew or Rebind, it MUST assume that the client is=
 presently using the addresses or prefixes therein.
- Confirm is close to Renew/Rebind.

So let's take the case where a client has an IA_NA with one or more address=
es and a IA_PD with one or more prefixes.

If the client sent a Renew and the Reply has 0 lifetimes for EITHER (but no=
t both) the IA_NA or IA_PD. What should the client do?
- If it sends another Renew, that probably won't get it anywhere since what=
 would have changed?
- If it sends a Request, that probably won't get it anywhere either? (And t=
his might mean it has to 'drop' what it can still use as we generally want =
to the client to "request" everything at once - not just a single IA option=
 as that leads to the split state machine.)
- So, that leaves the client with two choices:
1) Use what it has and at T1, send a Renew with both IA_NA and IA_PD again =
(one will be 'empty').
2) Return to Solicit (and since we want the client to have one state machin=
e), that means it MUST stop using anything left from either IA and Solicit =
for both (in this case, it could provide its "old" addresses/prefixes as hi=
nts).

If the client sent a Rebind (either because it has reached T2 or this is a =
"confirm") and the Reply has 0 lifetimes for EITHER (but not both) the IA_N=
A or IA_PD:
- In this case, sending a Renew [to the server that replied] might help sin=
ce perhaps the server may not have been able to assign new addresses/prefix=
es. This is also the reason we wanted this case to be communicated to the c=
lient by sending it NoAddrsAvail/NoPrefixAvail. Though looking back at that=
 changed text, it only covers the case when the server didn't find the bind=
ing - not when it had the binding but might have had new addresses (prefixe=
s) to assign so we may want to clarify that. In this case, the IA in the Re=
ply would include both IAADDR/IAPREFIX options and a Status Code of NoAddrs=
Avail/NoPrefixAvail. But perhaps we don't need a change to the text and can=
 just have the client determine that the IA ended up empty and to try the R=
enew.
- Otherwise, I think that leaves the client the same choices as with Renew =
(1 & 2).

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Thursday, October 16, 2014 2:14 PM
To: =1B$B?@L@C#:H=1B(B
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-sta=
teful-issues

Hi:

Regarding:

>Hmm, then the phrase "(larger than 0)" can be misleading.

Well, what this was there for was to indicate that if there were no IAADDR/=
IAPREFIX options or the lifetimes were all 0, the "effective" T1 (and T2) f=
or this IA_NA or IA_PD would be 0 and we would NOT want to use that. If the=
 "effective" T1 is 0, we want the client to skip that set of T1/T2 values.

In this case, the server would have had to send 0 not because it didn't cal=
culate the T1/T2 values, but because that is what the values are. But the c=
lient is told that if these values are 0, it needs to calculate them (from =
the lifetimes in that IA). Thus the resulting ("effective") values are 0 to=
o. And we don't want the client to Renew/Rebind immediately?


Regarding your issue with Section 4.4.5, if a client has both an IA_NA and =
IA_PD, it uses the Rebind message - not Confirm (see 4.5).

So:

>I'm not sure if I understand this as a response to my comment...to=20
>clarify my point, what I wanted to raise is what should happen if:
>
>- A client with bindings for both an IA_NA and an IA_PD detects it may
>  have moved to a different link, so sends a Confirm for the IA_NA.
>- The client receives a NotOnLink status in response to it.
>
>Should the client (effectively) discards the binding for IA_PD (and for=20
>IA_NA) and try to establish new bindings for both?  Or should it keep=20
>the binding for IA_PD (but it would break the proposed model of this=20
>draft)?  I thought the intent is the former, and I thought it's not=20
>clear enough and suggested to clarify it in the text.

And for Rebind processing (RFC 3315, but also applies to 3633):

   If the server finds that any of the addresses are no longer
   appropriate for the link to which the client is attached, the server
   returns the address to the client with lifetimes of 0.

The question then is what happens if the client ends up with only non-zero =
lifetimes for IAADDR or IAPREFIX options, but not the other (or more simply=
 some IA option ends up with no addresses/prefixes, but another binding mig=
ht have them).

This might be something to review in terms of RFC 3315 as I don't think it =
addresses this question.

The replacement text here (4.4.5, replacement text for Section 18.1.8 of RF=
C 3315):

     If the client finds no usable addresses in any IA, the client MAY
     use the Information-request message to obtain other configuration
     information only.

The 3315 text is:

   If the client receives no addresses in
   any of the IAs, it may either try another server (perhaps restarting
   the DHCP server discovery process) or use the Information-request
   message to obtain other configuration information only.

So, we can revisit how best to address this but some of this are flaws that=
 are in the base 3315 document.

This is also more significant now that allocating new addresses or delegati=
ng new prefixes is problematic for a Rebind (see 4.4.7.  Updates to Section=
 18.2.4 of RFC 3315) because of multiple servers processing the Rebind.

Marcin and I will discuss to see what we might do about this issue.

- Bernie

-----Original Message-----
From: jinmei.tatuya@gmail.com [mailto:jinmei.tatuya@gmail.com] On Behalf Of=
 ????
Sent: Thursday, October 16, 2014 1:34 PM
To: Bernie Volz (volz)
Cc: Marcin Siodelski; dhcwg@ietf.org
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-sta=
teful-issues

At Wed, 15 Oct 2014 16:16:36 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> First, I have a couple of higher level points to discuss:
>
> - What's the final goal of this document?
>
> ** The goal here is for this work to be an RFC.

Okay, in that case I'll also check overall readability as a separate docume=
nt for future versions.

> Specific comments to the draft text follow:
>
> - Title: now that our main focus is the mixed use of IA_NA and IA_PD
>   rather than generalizing the concept of stateful resources, I think
>   it makes more sense to reflect it in the title, for example,
>   "Issues and Recommendations with Multiple DHCPv6 IA Options".
>   See also my comments on Section 3 (terminology) below.
>
> ** We will leave the title as it is.

Hmm, if we are going to even more focus on the specific case of the mix of =
IA_NA and IA_PD as you'll mention below, and also if it's supposed to be pu=
blished as a single document, I'd avoid making the tile too generic.  So, I=
'd even make it more specific such as

    Issues and Recommendations with Mixed Use of DHCPv6 Address
    Assignment and Prefix Delegation

But it's ultimately up to the authors.  If the authors still thinks the cur=
rent title is the best, I won't insist further.

> - Abstract: this is more about readability (see above), but I'm afraid
>   the current abstract text wouldn't be really helpful for first-time
>   readers (on the other hand, it's not a problem for "me", because I
>   already know what it is). [...]
>
> ** We will leave the abstract pretty much as is. We change last sentence =
to mention that the (RFC) changes are to address the identified issues.

Ditto.  But I'll see how the abstract of the next version will look like.

> - Section 1, regarding the same text and this one:
[...]
>   IMO, this document should talk a bit more about the "framework".
[...]
> ** We will rework the Introduction to remove the 'framework' concept and =
just focus on the IA_NA/IA_PD issues. When and if there are future IA's, th=
ose documents can indicate whether they integrate into this work (i.e., add=
 IA_foo to IA_NA, IA_PD in the stateful issues document) or if they are sep=
arate and independent.

Okay.

> - Section 4.2: replacement for RFC 3315 17.1.3:
>
>      The client MUST ignore any Advertise message that contains no
>      addresses (IAADDR options encapsulated in IA_NA or IA_TA options)
>      and no delegated prefixes (IAPREFIX options encapsulated in IA_PD
>      options, see RFC 3633) with the exception that the client
>      MUST process an included SOL_MAX_RT option (RFC 7083), MUST
>      process an included INF_MAX_RT option (RFC 7083), and MAY
>      display any associated status message(s) to the user.
>
>   It's awkward to see it mention prefixes while this version
>   intentionally cancels the idea of "unified" text for renew/rebind.
>   It's not clear to me why Section 17.1.3 (regarding advertise) still
>   needs to provide "unified" text.
>
> ** While we could drop "and no delegated prefixes (...)", does that reall=
y help significantly especially since RFC 7083 material is being pulled in =
already? Also, in this case if we leave it out, people may be confused abou=
t what happens if there are no addresses but prefixes. (For most of the oth=
er changes later, RFC 3633 already covers these changes as it generally imp=
lies to replace "addresses" with "delegated prefixes" in much of the Reply =
processing. And, we've provided the revised text where needed for 3633.) Al=
so, RFC 3633 already points to 17.1.3 of 3315 and this avoids having to spe=
cify replacement text for 3633.

I wouldn't necessarily insist on it, it just looks awkward to me but otherw=
ise is not really a problem.  Maybe it helps if you note that you're provid=
ing unified text with the reason of why (e.g., because RFC 3633 doesn't des=
cribe its own version of this behavior but just refers to RFC 3315.)

> - Section 4.3: I don't understand the following text:
>
>    [...] To deal
>    with the case where servers have not yet been updated to do that,
>    clients MUST use the shortest (explicit or implicit) T1/T2 times
>    (larger than 0), from the same IA option, in the Reply.  T1/T2 times
>    from other IAs are ignored.
>
>   I guess it tries to address the corner case I pointed out for the
>   previous version of the draft:
>   http://www.ietf.org/mail-archive/web/dhcwg/current/msg15663.html
>   but I don't even understand what the client would do in this case
>   based on the new text.  To recap, what should happen if the client
>   sees the following two sets of T1/T2 according to the above text?
>   - T1a =3D 10, T2a =3D 20
>   - T1b =3D 0, T2b =3D 5
>
> ** We will include this example and explain it. Note that T1b  =3D 0 mean=
s that the client must calculate the T1 time (50% of lifetime) and that it =
obviously needs to be less than T2b. So, in this case the T1b =3D0, T2b =3D=
 5 would be used but the T1b time is the 'implicit' time (we can't give the=
 value since the lifetimes are not specified).

Hmm, then the phrase "(larger than 0)" can be misleading.

> ** There are perhaps other cases, for example T1a =3D 10, T2a =3D 20, T1b=
 =3D 5, T2b =3D 25 that are a bit more interesting since picking (b) means =
T1=3D5/T2=3D25 which means T2 is longer than T2a.

Personally, I'm okay with just dismissing such a case as a server misconfig=
uration (as we basically require the server use the same
T1/T2 values for all IAs).  I'd be fine unless a compliant client behavior =
leads to a clearly broken result, such as T1 > T2.

> ** Perhaps we need to review whether the shortest 'effective' T1 and inde=
pendently shortest 'effective' T2 are a better choice (obviously the client=
 would have to adjust T1 if this means T1>T2, but I'm not sure that could e=
ven happen since for any individual IA, T1 must be less than or equal to T2=
). Note that by 'effective' here I mean either the server supplied value or=
, if 0, the client determined value based on the lifetimes within that IA. =
 If we used that algorithm, for your case the answer would not change; for =
my example T1 would be and T2 would be 20 which are probably better values =
for this case.

See above.  IMO it doesn't have to be too complicated and we can basically =
leave it to the diligence of the server implementation/operation.  All I wa=
nt to see is a clear and well-defined client behavior.

> ** Comments about this issue (and perhaps additional case analysis if app=
ropriate) would be useful.
>
> - Section 4.4.5: does this mean, if the client has bindings of
>   multiple IAs, it should (effectively) abandon all of the bindings
>   and establish new bindings for all of the IAs starting from Solicit?
>   If so, it makes sense to me, but it's not really clear from the
>   text, and I suggest clarifying that point.
>
>      When the client receives a NotOnLink status from the server in
>      response to a Confirm message, the client performs DHCP server
>      solicitation, as described in section 17, and client-initiated
>      configuration as described in section 18.
>
> ** We will create a 3315bis ticket since this is pre-existing text used "=
as is" from 3315. And, this is not an issue that is particular to this draf=
t. Note that Confirm is IA_NA (IA_TA) specific as IA_PD requires a Rebind; =
so this is an open issue in the original 3315 and should be added by the bi=
s document. It also is more of a clarification, rather than a "change". The=
 bis document can clarify that when a client sends a Solicit, it MUST not b=
e using any of the addresses or delegated prefixes for the bindings include=
d in the Solicit.

I'm not sure if I understand this as a response to my comment...to clarify =
my point, what I wanted to raise is what should happen if:

- A client with bindings for both an IA_NA and an IA_PD detects it may
  have moved to a different link, so sends a Confirm for the IA_NA.
- The client receives a NotOnLink status in response to it.

Should the client (effectively) discards the binding for IA_PD (and for IA_=
NA) and try to establish new bindings for both?  Or should it keep the bind=
ing for IA_PD (but it would break the proposed model of this draft)?  I tho=
ught the intent is the former, and I thought it's not clear enough and sugg=
ested to clarify it in the text.

--
JINMEI, Tatuya
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Fri Oct 17 01:49:27 2014
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 547BA1A9135 for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 01:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 grzzLzaSwvLC for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 01:49:24 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ECFC1A9134 for <dhcwg@ietf.org>; Fri, 17 Oct 2014 01:49:24 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s9H8nMI0019971 for <dhcwg@ietf.org>; Fri, 17 Oct 2014 10:49:22 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A2008201B95 for <dhcwg@ietf.org>; Fri, 17 Oct 2014 10:50:40 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 90CCF201B48 for <dhcwg@ietf.org>; Fri, 17 Oct 2014 10:50:40 +0200 (CEST)
Received: from [10.8.33.116] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s9H8nMxu019398 for <dhcwg@ietf.org>; Fri, 17 Oct 2014 10:49:22 +0200
Message-ID: <5440D812.1050908@gmail.com>
Date: Fri, 17 Oct 2014 10:49:22 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
In-Reply-To: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/KbVG0kXsSe-2juC7IWef8Imin_U
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Oct 2014 08:49:26 -0000

Le 16/10/2014 16:53, Ted Lemon a écrit :
> When a new router is seen that sets the 'O' bit in its RA?   When a
> new prefix is seen, for the same router?   Only when a new link is
> detected?
>
> I think that it should happen whenever a new prefix is seen for a
> router that's set the O bit, but Lorenzo Colitti thinks that a new
> prefix doesn't (and shouldn't) trigger a new Information Request.
>
> Any thoughts about this?

Along these lines, in Mobile IP implementations, a mobile node triggers 
a BU when a new prefix is received in the RA. (because it thinks that if 
a new prefix is in the RA then it must form a new Care-of Address, and 
supposedly it moved towards a new attachment point).

It makes sense that a new prefix shows up, and has O bit set, the node 
should trigger an Information Request.

This would be desirable tandem working between RA and DHCP, if possible.

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>


From nobody Fri Oct 17 10:27:30 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1DB81A001D for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 10:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 u20fYnv_BsHy for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 10:27:26 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A67A1A000F for <dhcwg@ietf.org>; Fri, 17 Oct 2014 10:27:26 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hi2so4309564wib.3 for <dhcwg@ietf.org>; Fri, 17 Oct 2014 10:27:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=mvCCcHUyp0wWELnBG64Wqs2UZXeiC19PWrjwggp0cNg=; b=Iq0Ql2kN/ynJmzVq+XgxyOPBdoW/vO30CRiNYwuTX6BO/DLQ4sgP1vn5kUAW280rN0 XEuomVogfQ5WLyBINpZ3EXmkWURLdvLzY6WXsmcaeSZlXBQf8H4rhTznmYGZ15CUZRdZ ebTR+Z11nzfL6MrBzyc+dzRV0s57eWy+afrOpn//zAPZmPq2JS7NHN2YX1Ho7zN3cF7n J4kDuattgeStPgrTXgbqA7Te/awyXpXubdW4TxyEr0BFoK7dNnLZvNzXb3SjBJk1HtH2 tD1VkBy6/HyvlYmuUTe4NYeHnq/i1th0Hw+WEPN+8IiLqiPjlph6gM8XMwD4hDmoMXmt UHYA==
MIME-Version: 1.0
X-Received: by 10.180.149.130 with SMTP id ua2mr347301wib.31.1413566845138; Fri, 17 Oct 2014 10:27:25 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.195.13.83 with HTTP; Fri, 17 Oct 2014 10:27:25 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com>
Date: Fri, 17 Oct 2014 10:27:25 -0700
X-Google-Sender-Auth: 0mf4emAQC6pqL3Iyy6VIKQgSbTw
Message-ID: <CAJE_bqffHJfaYPcmt5GygpDn6Hb+2BWqejsvA0imD09ONorMmw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/TiSPWWUOG-wIFtzZgsOQam4EUqo
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Oct 2014 17:27:28 -0000

At Thu, 16 Oct 2014 18:13:30 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> Well, what this was there for was to indicate that if there were no IAADD=
R/IAPREFIX options or the lifetimes were all 0, the "effective" T1 (and T2)=
 for this IA_NA or IA_PD would be 0 and we would NOT want to use that. If t=
he "effective" T1 is 0, we want the client to skip that set of T1/T2 values=
.
>
> In this case, the server would have had to send 0 not because it didn't c=
alculate the T1/T2 values, but because that is what the values are. But the=
 client is told that if these values are 0, it needs to calculate them (fro=
m the lifetimes in that IA). Thus the resulting ("effective") values are 0 =
too. And we don't want the client to Renew/Rebind immediately?

To be accurate: "if these values are 0", the client can send next
renew at any timing (slightly different from "the client is told to
calculate it") per Section 18.1.3 of RFC 3315:

   If T1 or T2 is set to 0 by the server (for an IA_NA) or there are no
   T1 or T2 times (for an IA_TA), the client may send a Renew or Rebind
   message, respectively, at the client's discretion.

And, since it's up to the client how to calculate the value, the
"effective" value is not necessarily 0.

Obviously, we wouldn't want immediate (and repeated) renew/rebind if
the calculated value is somehow 0.  RFC 3315 is just silent about
these corner cases, and in my understanding it's left to implementor's
choice.  In a DHCPv6 client I'm relatively familiar with, it sets T2 to
30 (sec) and T1 to 18:

        /*
         * Be proactive for too-small timeout values.  Note that
         * the adjusted values may make some information expire
         * without renewal.
         */
        if (ia->t2 < DHCP6_DURATION_MIN) { /* DHCP6_DURATION_MIN=3D30*/
            ia->t2 =3D DHCP6_DURATION_MIN;
            ia->t1 =3D ia->t2 * 5 / 8;
        }

Anyway, these are minor technicality in this context.  As I said
in my previous message, I'm okay with any sensible and clearly-written
behavior since the basic assumption is T1/T2 and lifetimes should be
same for all IAs and other cases are exceptions.  I just tried to say
that the current text of the draft is not clear enough.

--
JINMEI, Tatuya


From nobody Fri Oct 17 10:32:56 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968971A0067 for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 10:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 1FTnwkoobGKI for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 10:32:48 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F2811A004B for <dhcwg@ietf.org>; Fri, 17 Oct 2014 10:32:48 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id h11so4671871wiw.0 for <dhcwg@ietf.org>; Fri, 17 Oct 2014 10:32:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=+OoVV2SJlgBukGIPv2mvnFPKE4sCRP09aoFbuwiC3J0=; b=fzjoWekRxdICQBtF5oYHjD+0YJREuFElC7Wov/cyPjoBtDIXbco3/8Pv3NBEU1/73e eKpIneZdyUj0JthnjfYYxuhkxgCJS0qUyQ3Ksbm1HIKFtfZu/Rvd1jX7wG1r/BfdeObk fl4qggHfiyAxNcKvkIEhpqn5ew+XIu0KIB/NS4i+7c9MfVIZ1nOaanVKOcDEeP6v5xD8 /Zm1lF2cOSTCym/1UPx1qLhJmyYWr5qNTHtRr8KA/1NeHtbnr0Z9kQeoLPbqfVWrjHg5 099jKTyOCgweJ887FH0XuG5b5SyQ0Kk8pSYKHXGGn2NFpf8OdWSu0nVNHtvoIRbSiOwB bTPw==
MIME-Version: 1.0
X-Received: by 10.194.48.116 with SMTP id k20mr12495485wjn.7.1413567167281; Fri, 17 Oct 2014 10:32:47 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.195.13.83 with HTTP; Fri, 17 Oct 2014 10:32:47 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D1B3A@xmb-rcd-x04.cisco.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6D1B3A@xmb-rcd-x04.cisco.com>
Date: Fri, 17 Oct 2014 10:32:47 -0700
X-Google-Sender-Auth: AE18zK9NTNj12YBPECDVRwhkSXg
Message-ID: <CAJE_bqe4xsP7eHBpvTZsw0VobpMnnG2MvYuMgXvKF+nrUS2yDw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/1ZFDPE9vn6DqVy7PSorEd7Uvq3M
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Oct 2014 17:32:50 -0000

At Thu, 16 Oct 2014 19:08:07 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> If the client sent a Renew and the Reply has 0 lifetimes for EITHER (but not both) the IA_NA or IA_PD. What should the client do?

I've not considered all of the ramifications (and, frankly, I've not
read all of this response closely), this breaks basic operational
assumption (i.e., all lifetimes and T1/T2 should be same for all IAs),
right?  If so, we might rather not try to be perfect but just make
sure that client ends up with a valid state (like having T2 < T1) and
leave other details open.

--
JINMEI, Tatuya


From nobody Fri Oct 17 11:03:22 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBC261A007E for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 11:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 40PHVvri1Wzc for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 11:03:17 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6436B1A00BF for <dhcwg@ietf.org>; Fri, 17 Oct 2014 11:03:17 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id hi2so1919614wib.2 for <dhcwg@ietf.org>; Fri, 17 Oct 2014 11:03:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=udiEEURGlVMtx4oVNIFXYYSzOovnzkI2y7N9vB/BUIA=; b=FcPuH4zsuyWdalFjWwcTHvitnSfUVhkI3zFe3SvQG3GNOKRN1I9wsUqYgy1rmdJ4iM YC2RxnfyCqI1rFIJYttY2s3vIyD/P0mLxlvGmIVYBOP9sgK6KKecTspg3J+kxiRr0HHu KJJT+lXRXIiT6NzUCWYXlfoOTruInytEWISXszxOcW6aEQdGmEpkdMVHpYKw4tlKxafo sYqLL1TF//G1Dtsw3/M0iU7TLLwvgmCGE9/NDlQ3EZK27zu/Jysegk9t8FNZxr933xbN 6Mz4BfyOxIVx6GxWDWoycC4FbxrlBnuhJhVqxtDpPE0pfJ4To2A7quc8hUGRO50O7BLw hmQw==
MIME-Version: 1.0
X-Received: by 10.194.58.8 with SMTP id m8mr12602460wjq.43.1413568996063; Fri, 17 Oct 2014 11:03:16 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.195.13.83 with HTTP; Fri, 17 Oct 2014 11:03:16 -0700 (PDT)
In-Reply-To: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
Date: Fri, 17 Oct 2014 11:03:16 -0700
X-Google-Sender-Auth: odjBOXxdgnS38HB9qkkOS26KsY0
Message-ID: <CAJE_bqeX8ztZhHfZn=qXovL4MyXoJ8z5zYDgg70sdbG0otorWg@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/yociHG097b-VD196VvUVLdSEB5Y
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Oct 2014 18:03:21 -0000

At Thu, 16 Oct 2014 09:53:06 -0500,
Ted Lemon <mellon@fugue.com> wrote:

> When a new router is seen that sets the 'O' bit in its RA?   When a new prefix is seen, for the same router?   Only when a new link is detected?
>
> I think that it should happen whenever a new prefix is seen for a router that's set the O bit, but Lorenzo Colitti thinks that a new prefix doesn't (and shouldn't) trigger a new Information Request.
>
> Any thoughts about this?

Are you asking what should happen per the protocol specification
(RFCs), or what should happen operationally?  Or what actual
implementations do, or something else?

Regarding the first, my understanding is that this is actually open.
As you probably know, the semantics of 'O' bit is way too unclear
(partially intentionally so at the time of RFC 4861, and has never
been clarified sufficiently).  So, for example, triggering DHCPv6
information request based on seeing a new IPv6 prefix is not a
protocol-defined behavior, but wouldn't break the protocol either.

I don't know whether there's a commonly agreed behavior of different
implementations.

--
JINMEI, Tatuya


From nobody Fri Oct 17 11:45:31 2014
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ADF91A1A63 for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 11:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.611
X-Spam-Level: 
X-Spam-Status: No, score=-1.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 63cruIUIWpTb for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 11:45:27 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 0ADFE1A1A4D for <dhcwg@ietf.org>; Fri, 17 Oct 2014 11:45:14 -0700 (PDT)
Received: from [192.168.1.63] (c-71-201-198-58.hsd1.il.comcast.net [71.201.198.58]) by toccata.fugue.com (Postfix) with ESMTPSA id 4D8E7238050E; Fri, 17 Oct 2014 14:45:13 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAJE_bqeX8ztZhHfZn=qXovL4MyXoJ8z5zYDgg70sdbG0otorWg@mail.gmail.com>
Date: Fri, 17 Oct 2014 13:45:07 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDD3DBF1-F4EA-4428-BDF1-0B4A16069B7A@fugue.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <CAJE_bqeX8ztZhHfZn=qXovL4MyXoJ8z5zYDgg70sdbG0otorWg@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/LnofdNyIzd7cFJHInJ1jnvfjKEo
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Oct 2014 18:45:29 -0000

On Oct 17, 2014, at 1:03 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> Are you asking what should happen per the protocol specification
> (RFCs), or what should happen operationally?  Or what actual
> implementations do, or something else?
>=20
The middle two.

> Regarding the first, my understanding is that this is actually open.
> As you probably know, the semantics of 'O' bit is way too unclear
> (partially intentionally so at the time of RFC 4861, and has never
> been clarified sufficiently).  So, for example, triggering DHCPv6
> information request based on seeing a new IPv6 prefix is not a
> protocol-defined behavior, but wouldn't break the protocol either.

Yes.  I think it should be a protocol-defined behavior, at least as =
recommended behavior.



From nobody Fri Oct 17 12:01:46 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 549ED1A1B17 for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 12:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Kpot3URcHXoV for <dhcwg@ietfa.amsl.com>; Fri, 17 Oct 2014 12:01:43 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 007C41A0154 for <dhcwg@ietf.org>; Fri, 17 Oct 2014 12:01:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3346; q=dns/txt; s=iport; t=1413572492; x=1414782092; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=DtSNqVRVitd66VOEmYJZZFAdBGMy5RuRkaebXvfbqd4=; b=TQ5IJgdBaHJFUp0l1RmYGszqmRmQq/OFi1fQxtA4wMPG16CNTfxfu+gd OXMmBe9UiixYytPniZGTcO2cgBc1jA1YRjMuCJOMohwTpeNtPAmqzr7G5 8nQ5CTeszQ4jOf0QIJ7MzsrcZTrij62CnppgJ0OSvL3cUb6yCijo9+KI4 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAPtmQVStJV2T/2dsb2JhbABbgw6BKwSDAtEKAht5FgF9hAIBAQEDASMRRQUHBAIBCBEEAQEDAgYdAwICAh8RFAEICAIEDgUIiCMDCQi5M44rDYYvAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4EsjG2CAxYQCwcGgnE2gR4BBJIAiUiDQYNGgy2HJYZdg3dsgUiBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,740,1406592000"; d="scan'208";a="87990996"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-5.cisco.com with ESMTP; 17 Oct 2014 19:01:31 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s9HJ1ViE026269 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 17 Oct 2014 19:01:31 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Fri, 17 Oct 2014 14:01:31 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
Thread-Index: AQHP4yTrEkD6ExoBZ0O6wM0stZ10wJwxXZPAgAH+sYD//69owIAADawAgAHU64D//8JP0A==
Date: Fri, 17 Oct 2014 19:01:30 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6D4548@xmb-rcd-x04.cisco.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6D1B3A@xmb-rcd-x04.cisco.com> <CAJE_bqe4xsP7eHBpvTZsw0VobpMnnG2MvYuMgXvKF+nrUS2yDw@mail.gmail.com>
In-Reply-To: <CAJE_bqe4xsP7eHBpvTZsw0VobpMnnG2MvYuMgXvKF+nrUS2yDw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/4UvmSputxTc1LzAPQDEw_mub5Rc
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 17 Oct 2014 19:01:45 -0000

SmlubWVpOg0KDQpXZSBoYXZlIHRvIGhhbmRsZSBFWElTVElORyBzZXJ2ZXJzIHdoaWNoIEkgYmVs
aWV2ZSBiYXNlIHRoZSBUMS9UMiB0aW1lcyBvbiBlYWNoIElBIHNlcGFyYXRlbHkgLSB0aG91Z2gg
dGhhdCBpcyBqdXN0IG15IGFzc3VtcHRpb24gLS0gSSBoYXZlbid0IGFuYWx5emVkIGFsbCBvZiB0
aGUgc2VydmVycy4gT2J2aW91c2x5IHRoaXMgYWxzbyBkZXBlbmRzIG9uIHRoZSBsaWZldGltZXMg
Y29uZmlndXJlZCAoaS5lLiwgaWYgdGhleSBhcmUgYWxsIHRoZSBzYW1lIGFuZCB0aGUgc2VydmVy
IGFzc2lnbnMgdGhlIGFkZHJlc3Nlcy9QRHMgYXJlIHRoZSBzYW1lIHRpbWUsIHRoZSBsaWZldGlt
ZXMgc2hvdWxkIGdlbmVyYWxseSBhbGwgYmUgaWRlbnRpY2FsIGFuZCBoZW5jZSBzbyBzaG91bGQg
dGhlIFQxL1QyIHRpbWVzKS4NCg0KVGhpcyBpcyB0aGUgcG9pbnQgYWJvdXQgdGhlIGNsaWVudCB0
ZXh0IC0gaXQgaXMgdGhlcmUgdG8gaGFuZGxlIHRoZSBjYXNlIHdoZXJlIHRoZSBjbGllbnQgaXMg
Y29tbXVuaWNhdGluZyB3aXRoIGFuIG9sZGVyICgzMzE1IGNvbXBsaWFudCkgc2VydmVyLiBJZiB3
ZSByZXF1aXJlZCBhbGwgc2VydmVycyB0byBiZSBtYWdpY2FsbHkgdXBkYXRlZCwgd2Ugd291bGRu
J3QgbmVlZCB0aGUgY2xpZW50IHRleHQuDQoNCkFuZCwgeWVzLCBJIHdhcyBub3QgdHJ5aW5nIHRv
IGJlIHRvbyBleHBsaWNpdCBhYm91dCB0aGlzIGJlY2F1c2UgaG93IGEgY2xpZW50IGNob3NlcyB0
byBpbXBsZW1lbnQgdGhpcyBpcyB1cCB0byBpdC4gRm9yIGV4YW1wbGUsIGl0IG1pZ2h0IGp1c3Qg
c2NoZWR1bGUgdGltZXJzIHRvIGV4cGlyZSBmb3IgZWFjaCBJQSBiYXNlZCBvbiBpdHMgVDEvVDIg
dGltZXMuIEJ1dCB3aGVuIHRoZSBmaXJzdCB0aW1lciBnb2VzIG9mZiwgaXQgaW5jbHVkZXMgYWxs
IGJpbmRpbmdzIGZyb20gdGhhdCBzZXJ2ZXIgaW4gdGhlIFJlbmV3LiBTbywgaW4gdGhpcyBjYXNl
IHRoZSBjbGllbnQgaGFzIG5vIG5lZWQgdG8gImNvbXBhcmUiIHRoZSBUMS9UMiB0aW1lcyBhdCBh
bGwuDQoNClBlcmhhcHMgdGhhdCBpcyBhIHdheSB0byBzb2x2ZSB0aGlzIHByb2JsZW0gLSBwZXJo
YXBzIHRoZSB0ZXh0IHNob3VsZCBmb2N1cyBvbiB0aGUgYmVoYXZpb3IgdG8gc2F5IHRoYXQ6DQoN
CiJUaGUgY2xpZW50IFNIT1VMRCBSZW5ldyAob3IgUmViaW5kKSBhbGwgb2YgdGhlIGJpbmRpbmdz
IGF0IG9uY2UsIHdoYXRldmVyIHRoZSBpbmRpdmlkdWFsIElBIFQxL1QyIHRpbWVzIG1pZ2h0IGhh
dmUgYmVlbi4gSG93IGEgY2xpZW50IGhhbmRsZXMgdGhpcyAod2hldGhlciBpdCBkZXRlcm1pbmVz
IG9uZSBzZXQgb2YgVDEvVDIgdmFsdWVzIHRvIHVzZSBhY3Jvc3MgYWxsIGJpbmRpbmdzLCBpbml0
aWF0ZXMgaW5kZXBlbmRlbnQgdGltZXJzIGFuZCB0aGUgZmlyc3Qgb25lIHRvIGdvIG9mZiByZXN1
bHRzIGluIGEgUmVuZXcgKG9yIFJlYmluZCkgd2l0aCBhbGwgYmluZGluZ3MsIG9yIHNvbWUgb3Ro
ZXIgYXBwcm9hY2gpLCBpcyB1cCB0byB0aGUgY2xpZW50IGltcGxlbWVudGF0aW9uLiINCg0KLSBC
ZXJuaWUNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGppbm1laS50YXR1eWFA
Z21haWwuY29tIFttYWlsdG86amlubWVpLnRhdHV5YUBnbWFpbC5jb21dIE9uIEJlaGFsZiBPZiA/
Pz8/DQpTZW50OiBGcmlkYXksIE9jdG9iZXIgMTcsIDIwMTQgMTozMyBQTQ0KVG86IEJlcm5pZSBW
b2x6ICh2b2x6KQ0KQ2M6IGRoY3dnQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW2RoY3dnXSBQbGVh
c2UgcmV2aWV3IHZlcnNpb24gLTA3IG9mIGRyYWZ0LWlldGYtZGhjLWRoY3B2Ni1zdGF0ZWZ1bC1p
c3N1ZXMNCg0KQXQgVGh1LCAxNiBPY3QgMjAxNCAxOTowODowNyArMDAwMCwNCiJCZXJuaWUgVm9s
eiAodm9seikiIDx2b2x6QGNpc2NvLmNvbT4gd3JvdGU6DQoNCj4gSWYgdGhlIGNsaWVudCBzZW50
IGEgUmVuZXcgYW5kIHRoZSBSZXBseSBoYXMgMCBsaWZldGltZXMgZm9yIEVJVEhFUiAoYnV0IG5v
dCBib3RoKSB0aGUgSUFfTkEgb3IgSUFfUEQuIFdoYXQgc2hvdWxkIHRoZSBjbGllbnQgZG8/DQoN
CkkndmUgbm90IGNvbnNpZGVyZWQgYWxsIG9mIHRoZSByYW1pZmljYXRpb25zIChhbmQsIGZyYW5r
bHksIEkndmUgbm90IHJlYWQgYWxsIG9mIHRoaXMgcmVzcG9uc2UgY2xvc2VseSksIHRoaXMgYnJl
YWtzIGJhc2ljIG9wZXJhdGlvbmFsIGFzc3VtcHRpb24gKGkuZS4sIGFsbCBsaWZldGltZXMgYW5k
IFQxL1QyIHNob3VsZCBiZSBzYW1lIGZvciBhbGwgSUFzKSwgcmlnaHQ/ICBJZiBzbywgd2UgbWln
aHQgcmF0aGVyIG5vdCB0cnkgdG8gYmUgcGVyZmVjdCBidXQganVzdCBtYWtlIHN1cmUgdGhhdCBj
bGllbnQgZW5kcyB1cCB3aXRoIGEgdmFsaWQgc3RhdGUgKGxpa2UgaGF2aW5nIFQyIDwgVDEpIGFu
ZCBsZWF2ZSBvdGhlciBkZXRhaWxzIG9wZW4uDQoNCi0tDQpKSU5NRUksIFRhdHV5YQ0K


From nobody Sun Oct 19 13:11:50 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 118341A6F6F for <dhcwg@ietfa.amsl.com>; Sun, 19 Oct 2014 13:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 jWncVQCUyLfA for <dhcwg@ietfa.amsl.com>; Sun, 19 Oct 2014 13:11:46 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38D0B1A6F63 for <dhcwg@ietf.org>; Sun, 19 Oct 2014 13:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3416; q=dns/txt; s=iport; t=1413749506; x=1414959106; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=EyytuxLA4H0TWb3f20HBn2FJhrjLsXjDmi1cirXhxto=; b=k3h5IhboBK1+XWDM/NATVAVAkZXwIgfRn8WUtTOPg8LmWvGwh5fE7DMO QS2B6+QItYmgVzXyP+ryKE4PDYdLb6x6S/lYxZyA2LSE0qNi8LwABaLXO 6gIhmwT3eqtw9n3W8UNsqarmULt4i9YQwhnfHjzOlULPZ+4WBxxhiMiw2 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmgFAO4ZRFStJA2H/2dsb2JhbABbgw5TWMongWYBCYdOAoEOFgFyC4QCAQEBBAEBAWsLEAIBDA0DAQIoBycLFAcCCAIEDgWIPw2/XwEBAQEBAQEBAQEBAQEBAQEBAQEBAReQQA0EBgEGhEUFkgCERocTgTA8gwqDLYl+hAGDd2yCSwEBAQ
X-IronPort-AV: E=Sophos; i="5.04,749,1406592000"; d="scan'208,217"; a="88421272"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-6.cisco.com with ESMTP; 19 Oct 2014 20:11:45 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9JKBjG6020811 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sun, 19 Oct 2014 20:11:45 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0195.001; Sun, 19 Oct 2014 15:11:45 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [v6ops] draft-ietf-v6ops-dhcpv6-slaac-problem WGLC
Thread-Index: AQHP68aR+NvJtuMsYE6PXoOSNM+7F5w32kHm
Date: Sun, 19 Oct 2014 20:11:44 +0000
Message-ID: <DAA8D8B5-9AB7-455C-950C-263701345FAD@cisco.com>
References: <201410191800.s9JI02XP029920@irp-lnx1.cisco.com>
In-Reply-To: <201410191800.s9JI02XP029920@irp-lnx1.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_DAA8D8B59AB7455C950C263701345FADciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/TMSEcC2kjEDI4GmaUwXIzXJXArk
Cc: "Fred Baker \(fred\)" <fred@cisco.com>
Subject: [dhcwg] Fwd: [v6ops] draft-ietf-v6ops-dhcpv6-slaac-problem WGLC
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 19 Oct 2014 20:11:48 -0000

--_000_DAA8D8B59AB7455C950C263701345FADciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

This WG last call may be of interest to DHC wg folks.

- Bernie (from iPad)

Begin forwarded message:

From: <fred@cisco.com<mailto:fred@cisco.com>>
Date: October 19, 2014 at 2:00:02 PM EDT
To: <v6ops@ietf.org<mailto:v6ops@ietf.org>>
Subject: [v6ops] draft-ietf-v6ops-dhcpv6-slaac-problem WGLC

This is to initiate a two week working group last call of
http://tools.ietf.org/html/draft-ietf-v6ops-dhcpv6-slaac-problem.
Please read it now. If you find nits (spelling errors, minor suggested
wording changes, etc), comment to the authors; if you find greater
issues, such as disagreeing with a statement or finding additional
issues that need to be addressed, please post your comments to the
list.

We are looking specifically for comments on the importance of the
document as well as its content. If you have read the document and
believe it to be of operational utility, that is also an important
comment to make.

_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops

--_000_DAA8D8B59AB7455C950C263701345FADciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>This WG last call may be of interest to DHC wg folks.<br>
<br>
- Bernie (from iPad)</div>
<div><br>
Begin forwarded message:<br>
<br>
</div>
<blockquote type=3D"cite">
<div><b>From:</b> &lt;<a href=3D"mailto:fred@cisco.com">fred@cisco.com</a>&=
gt;<br>
<b>Date:</b> October 19, 2014 at 2:00:02 PM EDT<br>
<b>To:</b> &lt;<a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a>&gt;<br>
<b>Subject:</b> <b>[v6ops] draft-ietf-v6ops-dhcpv6-slaac-problem WGLC</b><b=
r>
<br>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>This is to initiate a two week working group last call of</span>=
<br>
<span><a href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-dhcpv6-slaac-p=
roblem">http://tools.ietf.org/html/draft-ietf-v6ops-dhcpv6-slaac-problem</a=
>. &nbsp;</span><br>
<span>Please read it now. If you find nits (spelling errors, minor suggeste=
d</span><br>
<span>wording changes, etc), comment to the authors; if you find greater</s=
pan><br>
<span>issues, such as disagreeing with a statement or finding additional</s=
pan><br>
<span>issues that need to be addressed, please post your comments to the</s=
pan><br>
<span>list.</span><br>
<span></span><br>
<span>We are looking specifically for comments on the importance of the</sp=
an><br>
<span>document as well as its content. If you have read the document and</s=
pan><br>
<span>believe it to be of operational utility, that is also an important</s=
pan><br>
<span>comment to make.</span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>v6ops mailing list</span><br>
<span><a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/v6ops">https://www.i=
etf.org/mailman/listinfo/v6ops</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_DAA8D8B59AB7455C950C263701345FADciscocom_--


From nobody Sun Oct 19 15:51:54 2014
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 497271A0276 for <dhcwg@ietfa.amsl.com>; Sun, 19 Oct 2014 15:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.169
X-Spam-Level: 
X-Spam-Status: No, score=0.169 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 1UGK7vzdZy9J for <dhcwg@ietfa.amsl.com>; Sun, 19 Oct 2014 15:51:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE7FF1A0673 for <dhcwg@ietf.org>; Sun, 19 Oct 2014 15:51:49 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s9JMpXPY001516; Sun, 19 Oct 2014 23:51:33 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s9JMpXPY001516
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1413759094; bh=vmqW58Pj7amcB8euF9beW1Ue6T4=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=d5hJunWVTpPYEKwEfgVAD0RsJq/7AO7hnF6CTZu8cEUK3P6RFkVp6AC7PB01QNnCl R/ORrhK2n1HP8w+UytumNtudNyaEFOtRlQKgSFgGRpxcEWsL4sZ3TVgV50yOP8gYDI xwhy8A463auJuBB8P4s7f80nWQcgB02/8xNEBpiQ=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id q9INpX0490104094Kp ret-id none; Sun, 19 Oct 2014 23:51:34 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s9JMoCgL021930 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 19 Oct 2014 23:50:12 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com>
Date: Sun, 19 Oct 2014 23:50:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|a3691409b8087136c49e06c0136831b0q9INpX03tjc|ecs.soton.ac.uk|BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com> <BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q9INpX049010409400; tid=q9INpX0490104094Kp; client=relay,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s9JMpXPY001516
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/wEDad18ttkxQ2QYpCWun8qZtpes
Cc: dhcwg <dhcwg@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 19 Oct 2014 22:51:53 -0000

Hi,

On 16 Oct 2014, at 16:42, Bernie Volz (volz) <volz@cisco.com> wrote:

> This might be a good issue to add in the 3315bis issues list - =
recommendations on when to initiate an Information-Request based on =
network changes.
>=20
> I would guess that most clients trigger it when the refresh time =
(OPTION_INFORMATION_REFRESH_TIME option) expires or when some =
application request some data that hasn't been obtained (if the OS has =
this capability)?
>=20
> Probably something (at least for the address selection policy table) =
that should have been covered in RFC 7078.
>=20
> The text there is:
>=20
>   The received information can be considered stale in several cases,
>   e.g., when the interface goes down, the DHCP server does not respond
>   for a certain amount of time, or the Information Refresh Time has
>   expired.
>=20
> Of course, the list is just 'e.g.' so could include more.
>=20
> And, there might be some rate limiting that is applicable in case =
there is flapping of the RA prefix information.

I agree with Bernie and Ted.=20

It would make sense to fetch at the very least a (potentially) new =
policy table when a new prefix is advertised.=20

With hindsight I wish we=92d added, or proposed adding, =93or a new =
prefix information is received=94 in the RFC 7078 text above while it =
was still in draft status, at least to flush out consensus on the =
question back then. =20

But we should get a clear recommendation somewhere to maximise =
consistency in behaviour. If a 3315-bis is in the works, that seems as =
good a place as any, given that also obviously predates RFC 4242 on the =
refresh timer.

Tim

> - Bernie
>=20
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
> Sent: Thursday, October 16, 2014 11:26 AM
> To: Timothy Winters
> Cc: dhcwg
> Subject: Re: [dhcwg] What triggers a DHCP Information Request?
>=20
> On Oct 16, 2014, at 10:01 AM, Timothy Winters <twinters@iol.unh.edu> =
wrote:
>> 	 At the IOL I'm not aware of many DHCPv6 clients that trigger =
the DHCPv6 Information Request based on addresses being added.  I could =
see the case of when you lose all Global address (including ULA) a =
device might send one, but I would be surprised if they send when when =
new prefixes are found.   I can look closer into this to see what =
triggers it, give me a couple of days and I'll report back.=20
>=20
> That seems broken, because you probably want to refresh the source =
address selection policy table whenever you see a new prefix.
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Mon Oct 20 01:17:12 2014
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D6C21A6FE3 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 01:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 iHTlmgVywIP0 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 01:17:06 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id E68721A6FDD for <dhcwg@ietf.org>; Mon, 20 Oct 2014 01:17:04 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 958D71BC3E for <dhcwg@ietf.org>; Mon, 20 Oct 2014 08:16:57 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <EMEW3|a3691409b8087136c49e06c0136831b0q9INpX03tjc|ecs.soton.ac.uk|BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk>
Date: Mon, 20 Oct 2014 09:17:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD83BDF3-C35B-4DCD-B32D-090BFF4AB149@thehobsons.co.uk>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com> <BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk> <EMEW3|a3691409b8087136c49e06c0136831b0q9INpX03tjc|ecs.soton.ac.uk|BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk>
To: dhcwg <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/g2FbwZkslvNx8T5aXmWc5dn9iqw
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Oct 2014 08:17:09 -0000

Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> I agree with Bernie and Ted.=20
>=20
> It would make sense to fetch at the very least a (potentially) new =
policy table when a new prefix is advertised.=20

+1
IMO if the RAs being advertised change - whether that's a router =
appearing or disappearing, or a prefix being added or deleted - then =
that means "something" has changed on the network. When that happens it =
makes sense to ask what the current config for our devide looks like - =
even if the current config is "no change" from the previous config.


From nobody Mon Oct 20 04:25:55 2014
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A5C1A7022 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 04:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 uW8ryHghlGxL for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 04:25:45 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BF711A86FE for <dhcwg@ietf.org>; Mon, 20 Oct 2014 04:25:45 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id d1so6008800wiv.6 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 04:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ypKIbJ4/fkhYB+zHVZM/fpEe8ZNw8dUR7OfSU1iuWIQ=; b=Ows9j7ZIV1D29IwvS8bUZrXJfWWvVgmUYsI+G2NMAw9M5h8bAeZe9p0M77dbwG8XJW 0wGmXjIoFXE4EOrIHDsn1G3eHZIgJ6PBI4/AG/PVQH+TviEOnO0iMV9OA/gfkKUL0KOP ZHekrWOdiF+J6qO243M1zzYippeXLczEi1k8SK1y3yq+24OXo5do25Vqj3t/rro36tbz 6zVkpWwdkzBNrTfx+Cj5UBvpjfV4Gs6NX0IwKkMBh0Bx2CvskVnuwbdPm1n295vlZ3pk YVSjVmGy2XPAauYqK4bjLPDvydKwWO2a0Xr74H+aDPfKphb6//PU/se0ZWWLW+xqIP4y BwUQ==
X-Received: by 10.180.73.134 with SMTP id l6mr19098161wiv.14.1413804344082; Mon, 20 Oct 2014 04:25:44 -0700 (PDT)
Received: from [192.168.10.12] (89-79-26-47.dynamic.chello.pl. [89.79.26.47]) by mx.google.com with ESMTPSA id ws2sm11536952wjc.32.2014.10.20.04.25.43 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Oct 2014 04:25:43 -0700 (PDT)
Message-ID: <5444F104.1060009@gmail.com>
Date: Mon, 20 Oct 2014 13:24:52 +0200
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6D1B3A@xmb-rcd-x04.cisco.com> <CAJE_bqe4xsP7eHBpvTZsw0VobpMnnG2MvYuMgXvKF+nrUS2yDw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D4548@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D4548@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/h7Hs5SD_lvcZgqe1-hHKeILte84
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Oct 2014 11:25:47 -0000

How about this text:

   "To deal with the case where servers have not yet been updated
    to that, clients MUST select the T1/T2 times from a single IA
    option and the selected T1/T2 times must guarantee that the client
    will send Renew/Rebind messages not later than at T1/T2 times associated
    with any of the client's bindings. The details how the server
    chooses IA with the candidate T1/T2 times is out of scope for
    this document."

?

Marcin

On 10/17/14 21:01, Bernie Volz (volz) wrote:
> Jinmei:
>
> We have to handle EXISTING servers which I believe base the T1/T2 times on each IA separately - though that is just my assumption -- I haven't analyzed all of the servers. Obviously this also depends on the lifetimes configured (i.e., if they are all the same and the server assigns the addresses/PDs are the same time, the lifetimes should generally all be identical and hence so should the T1/T2 times).
>
> This is the point about the client text - it is there to handle the case where the client is communicating with an older (3315 compliant) server. If we required all servers to be magically updated, we wouldn't need the client text.
>
> And, yes, I was not trying to be too explicit about this because how a client choses to implement this is up to it. For example, it might just schedule timers to expire for each IA based on its T1/T2 times. But when the first timer goes off, it includes all bindings from that server in the Renew. So, in this case the client has no need to "compare" the T1/T2 times at all.
>
> Perhaps that is a way to solve this problem - perhaps the text should focus on the behavior to say that:
>
> "The client SHOULD Renew (or Rebind) all of the bindings at once, whatever the individual IA T1/T2 times might have been. How a client handles this (whether it determines one set of T1/T2 values to use across all bindings, initiates independent timers and the first one to go off results in a Renew (or Rebind) with all bindings, or some other approach), is up to the client implementation."
>
> - Bernie
>
> -----Original Message-----
> From: jinmei.tatuya@gmail.com [mailto:jinmei.tatuya@gmail.com] On Behalf Of ????
> Sent: Friday, October 17, 2014 1:33 PM
> To: Bernie Volz (volz)
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
>
> At Thu, 16 Oct 2014 19:08:07 +0000,
> "Bernie Volz (volz)" <volz@cisco.com> wrote:
>
>> If the client sent a Renew and the Reply has 0 lifetimes for EITHER (but not both) the IA_NA or IA_PD. What should the client do?
> I've not considered all of the ramifications (and, frankly, I've not read all of this response closely), this breaks basic operational assumption (i.e., all lifetimes and T1/T2 should be same for all IAs), right?  If so, we might rather not try to be perfect but just make sure that client ends up with a valid state (like having T2 < T1) and leave other details open.
>
> --
> JINMEI, Tatuya
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Mon Oct 20 04:49:41 2014
Return-Path: <dhcp1@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2442D1A6FC8 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 00:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 nu4AAXhOO3pl for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 00:03:58 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id B04D41A6FC7 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 00:03:58 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.3] (88-111-167-49.dynamic.dsl.as9105.com [88.111.167.49]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 3DDCE1BC3E for <dhcwg@ietf.org>; Mon, 20 Oct 2014 07:03:52 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <dhcp1@thehobsons.co.uk>
In-Reply-To: <EMEW3|a3691409b8087136c49e06c0136831b0q9INpX03tjc|ecs.soton.ac.uk|BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk>
Date: Mon, 20 Oct 2014 08:03:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CBB1B29-B5BA-46B2-8E16-6CE22D0396A7@thehobsons.co.uk>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com> <BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk> <EMEW3|a3691409b8087136c49e06c0136831b0q9INpX03tjc|ecs.soton.ac.uk|BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk>
To: dhcwg <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/bzNFfN3CBeot1SUUlCN0RAdxiq4
X-Mailman-Approved-At: Mon, 20 Oct 2014 04:49:40 -0700
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Oct 2014 07:04:01 -0000

Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> I agree with Bernie and Ted.=20
>=20
> It would make sense to fetch at the very least a (potentially) new =
policy table when a new prefix is advertised.=20

+1
IMO if the RAs being advertised change - whether that's a router =
appearing or disappearing, or a prefix being added or deleted - then =
that means "something" has changed on the network. When that happens it =
makes sense to ask what the current config for our devide looks like - =
even if the current config is "no change" from the previous config.


From nobody Mon Oct 20 06:06:25 2014
Return-Path: <twinters@iol.unh.edu>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8101A8729 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 06:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 M0OY7PI1MnEq for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 06:06:21 -0700 (PDT)
Received: from mail-qg0-f98.google.com (mail-qg0-f98.google.com [209.85.192.98]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C8AE1A8722 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 06:06:20 -0700 (PDT)
Received: by mail-qg0-f98.google.com with SMTP id q108so651056qgd.5 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 06:06:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=dkwSFjKUEnuTxDtCw+8G/3adtE6gsOfhZMiNKRzxKQw=; b=hz0n3JB2hsb40dTSVewShEQ0czbapBhlw1LquczgIKZCCrqMA9TmcW38UhO1BdmJv9 THjp13/Zr0eU4FWLLriYyqQmGo/0fvGchq9bz2hrD7RzRmX69Lcu5AaejBfx4U8m+tbv ZRcN8jqq+Ki9BrTf622hJhTHAoSAsaVtTdIhrBX4c9kXSkWDqc/Sd3ybHf4tQisMCWXr uMFwsCUXvGTQqFI136KYIPBbtgG+l8y2b/oWCARVnyC+EIXXzbA9vUmy3NmBAou6Dfw8 ap33DdZHuAlqQR1D00whIC5tnbC0cf0DzsRPiQlTnR+FAJhR3ArF/+TdEHM/mDV0Vw0e dq9w==
X-Gm-Message-State: ALoCoQmWwPgpbFhSk3RRYnMGrP3DdZJ9OcgYNcVNCRvZUVw25r5Eu9pcbX07iEa42Wzv3jE+mFA8XJG4qFUAV++GqooEPxqhcg==
X-Received: by 10.202.1.80 with SMTP id 77mr21908131oib.31.1413810379342; Mon, 20 Oct 2014 06:06:19 -0700 (PDT)
Received: from postal.iol.unh.edu ([2606:4100:3880:1234::84]) by mx.google.com with ESMTP id n4sm1687060qcq.2.2014.10.20.06.06.18 for <multiple recipients>; Mon, 20 Oct 2014 06:06:19 -0700 (PDT)
X-Relaying-Domain: iol.unh.edu
Received: from [IPv6:2606:4100:3880:1270:5829:fcbc:d0c2:d8] (unknown [IPv6:2606:4100:3880:1270:5829:fcbc:d0c2:d8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by postal.iol.unh.edu (Postfix) with ESMTPSA id 7723E441E9; Mon, 20 Oct 2014 09:06:18 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Timothy Winters <twinters@iol.unh.edu>
In-Reply-To: <4CBB1B29-B5BA-46B2-8E16-6CE22D0396A7@thehobsons.co.uk>
Date: Mon, 20 Oct 2014 09:06:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <909EC0B6-9EBE-45E3-8CD2-1AC7C1FA0984@iol.unh.edu>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com> <BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk> <EMEW3|a3691409b8087136c49e06c0136831b0q9INpX03tjc|ecs.soton.ac.uk|BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk> <4CBB1B29-B5BA-46B2-8E16-6CE22D0396A7@thehobsons.co.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/PakR9Zln_QFqjB4-fJ4hZgcTsYY
Cc: dhcwg <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Oct 2014 13:06:24 -0000

Hi Ted,
	After some quick research here at the UNH-IOL, we don=E2=80=99t =
have any OS that will send a DHCPv6 Information Request when a new =
prefix arrives in an RA.   It would seem that most implementations only =
trigger it when the O flag changes.   There might be some other cases =
that send DHCPv6 Information Request depending on what parameters =
change, Router lifetime for example.   Let me know if you want us to =
look into other things.

~Tim

> On Oct 20, 2014, at 3:03 AM, Simon Hobson <dhcp1@thehobsons.co.uk> =
wrote:
>=20
> Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>=20
>> I agree with Bernie and Ted.=20
>>=20
>> It would make sense to fetch at the very least a (potentially) new =
policy table when a new prefix is advertised.=20
>=20
> +1
> IMO if the RAs being advertised change - whether that's a router =
appearing or disappearing, or a prefix being added or deleted - then =
that means "something" has changed on the network. When that happens it =
makes sense to ask what the current config for our devide looks like - =
even if the current config is "no change" from the previous config.
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Mon Oct 20 06:31:44 2014
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C49521A87AF for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 06:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 xkVHCVaDrTLG for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 06:31:40 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 561A41A87D2 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 06:27:39 -0700 (PDT)
Received: from [10.0.10.40] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 2578E2380481; Mon, 20 Oct 2014 09:27:37 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <909EC0B6-9EBE-45E3-8CD2-1AC7C1FA0984@iol.unh.edu>
Date: Mon, 20 Oct 2014 09:27:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F50C0AF9-10E0-47EC-9EF1-4115FAA25325@fugue.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com> <BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk> <EMEW3|a3691409b8087136c49e06c0136831b0q9INpX03tjc|ecs.soton.ac.uk|BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk> <4CBB1B29-B5BA-46B2-8E16-6CE22D0396A7@thehobsons.co.uk> <909EC0B6-9EBE-45E3-8CD2-1AC7C1FA0984@iol.unh.edu>
To: Timothy Winters <twinters@iol.unh.edu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/VdOxc0H_Xt1aZ8iQlh6sePwjuZ0
Cc: dhcwg <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Oct 2014 13:31:42 -0000

On Oct 20, 2014, at 9:06 AM, Timothy Winters <twinters@iol.unh.edu> =
wrote:
> 	After some quick research here at the UNH-IOL, we don=92t have =
any OS that will send a DHCPv6 Information Request when a new prefix =
arrives in an RA.   It would seem that most implementations only trigger =
it when the O flag changes.   There might be some other cases that send =
DHCPv6 Information Request depending on what parameters change, Router =
lifetime for example.   Let me know if you want us to look into other =
things.

Wow, thanks for the quick response!   I guess we have our work cut out =
for us!


From nobody Mon Oct 20 10:20:20 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6AC81A6F52 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 10:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 m1MWbuCd7v9g for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 10:20:15 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 523DA1A875A for <dhcwg@ietf.org>; Mon, 20 Oct 2014 10:17:42 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id h11so8607156wiw.7 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 10:17:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=nHnu1LeXC+0wkb84XVBju48306TYikSYDeb/8Tg1BCs=; b=eD+ICN1LEtD1sUMqQ/E3vrabh3idrxa4PDDBzisJv4tB73nog1DwFBGV+NwtpCmYZ3 5LHDqlApbgWAZszZe+zLBYtTw3dJx/vUuFIdBKineCXABjoy3ktJDKC9gV3GcJgfWxql en1siCP7NTm2IMUlGSf6/XtoTYopyss5hc/lg2rcm3qrOU3kdzjjIANIGaK+5xylc8hQ UpQBkfEyrLOAKYLvdLFPu595iqmlEegHogFhCUvUSgyZ+Zpql2PlrIXCes/K20rk5pPJ QaHkPUTFvDTpudF2+/B9q3CI1ViUaf/j9x9nR/O0ChuU4lSt8X8vn66PCrtX8waBmNfU cYDw==
MIME-Version: 1.0
X-Received: by 10.180.82.105 with SMTP id h9mr5274764wiy.62.1413825460685; Mon, 20 Oct 2014 10:17:40 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.79.202 with HTTP; Mon, 20 Oct 2014 10:17:40 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D4548@xmb-rcd-x04.cisco.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6D1B3A@xmb-rcd-x04.cisco.com> <CAJE_bqe4xsP7eHBpvTZsw0VobpMnnG2MvYuMgXvKF+nrUS2yDw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D4548@xmb-rcd-x04.cisco.com>
Date: Mon, 20 Oct 2014 10:17:40 -0700
X-Google-Sender-Auth: qz0lf1gK0knWkl_VOwzBFm7Fzeg
Message-ID: <CAJE_bqfU3V5z8bMuwfqC8RdKUnpqQgOb5ME_ND5ZmeQEWnXccw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/z-5x8tvKeypSTBlZ_5npI9vwSj0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Oct 2014 17:20:18 -0000

At Fri, 17 Oct 2014 19:01:30 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> We have to handle EXISTING servers which I believe base the T1/T2 times o=
n each IA separately - though that is just my assumption -- I haven't analy=
zed all of the servers. Obviously this also depends on the lifetimes config=
ured (i.e., if they are all the same and the server assigns the addresses/P=
Ds are the same time, the lifetimes should generally all be identical and h=
ence so should the T1/T2 times).
>
> This is the point about the client text - it is there to handle the case =
where the client is communicating with an older (3315 compliant) server. If=
 we required all servers to be magically updated, we wouldn't need the clie=
nt text.

I thought the mixed use of different IAs (especially of different
types) is largely unspecified and we cannot reasonably expect
interoperability anyway (in fact, hence this draft, right?).  And, if
we cannot expect a specific behavior from the server side, I don't see
much point in trying to specify how the client should deal with them.
It seems to be simpler if we just say

- if you want to deploy mixed use of IAs in an interoperable manner,
  make sure all servers and clients are updated according to this
  clarification.
- otherwise, such mixed use may or may not work.  do it at your own
  risk.

> Perhaps that is a way to solve this problem - perhaps the text should foc=
us on the behavior to say that:
>
> "The client SHOULD Renew (or Rebind) all of the bindings at once, whateve=
r the individual IA T1/T2 times might have been. How a client handles this =
(whether it determines one set of T1/T2 values to use across all bindings, =
initiates independent timers and the first one to go off results in a Renew=
 (or Rebind) with all bindings, or some other approach), is up to the clien=
t implementation."

Looks good (enough) to me.  I'd also note that as long as servers are
implemented (and operated) based on this update (and that's the
recommended way of operation with mixed use of IAs), T1 and T2 should
have the same values for all IAs, and the client behavior should be
trivial and deterministic.

--
jinmei


From nobody Mon Oct 20 10:21:05 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD9AC1A8035 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 10:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 1RSXAmffKSmK for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 10:20:54 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 397C81A6F28 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 10:18:34 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id em10so7786277wid.4 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 10:18:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Wxohf7+pkCF130OenSKYbgJRTcbVjY6GaT5CMaqNBbU=; b=a2C14jZMWOtd0CyVSBR4V/PMvRUtkLxmYclHsfIijKktojs5AR+ETL5ieUfCLbnqzT CaVOb/1RBPvqsydinnRVae/l4p11nXWSSXG9wl3WsymUUFYziBGgZwZoud827sVFYn9e 8lLKakZZ+Q1y/A0EW7Z1RrrECME4mqKyEvlqATRXYJ8RMRMVaEagVcmd1eF6PtEp+4hd idr1vK3zzzNnkeIt7yBSDWXsdV34n/hJ0A3CCDlaqtFT0NfScKyEwUzvzWHgFArXcuEo eZN2blUpQuBPkV38bFq9sirLl/hSSwIrDp/WSBFiLj5W7Of9AC0ILfoeYK6rAs0TgIzt jHLg==
MIME-Version: 1.0
X-Received: by 10.180.82.105 with SMTP id h9mr5280297wiy.62.1413825512634; Mon, 20 Oct 2014 10:18:32 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.79.202 with HTTP; Mon, 20 Oct 2014 10:18:32 -0700 (PDT)
In-Reply-To: <5444F104.1060009@gmail.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6D1B3A@xmb-rcd-x04.cisco.com> <CAJE_bqe4xsP7eHBpvTZsw0VobpMnnG2MvYuMgXvKF+nrUS2yDw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D4548@xmb-rcd-x04.cisco.com> <5444F104.1060009@gmail.com>
Date: Mon, 20 Oct 2014 10:18:32 -0700
X-Google-Sender-Auth: BQpSq9k0z47Sxw2cDqMQ0yVeLCQ
Message-ID: <CAJE_bqe9gG1QYNm2Vq1vhnw5VRhSEUFd_P-fM2ayKDbB17TAQQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Marcin Siodelski <msiodelski@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/4GO8D4Z_En8kjJR3p84hjFgCDyo
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Oct 2014 17:20:56 -0000

At Mon, 20 Oct 2014 13:24:52 +0200,
Marcin Siodelski <msiodelski@gmail.com> wrote:

> How about this text:
>
>    "To deal with the case where servers have not yet been updated
>     to that, clients MUST select the T1/T2 times from a single IA
>     option and the selected T1/T2 times must guarantee that the client
>     will send Renew/Rebind messages not later than at T1/T2 times associated
>     with any of the client's bindings. The details how the server
>     chooses IA with the candidate T1/T2 times is out of scope for
>     this document."

This also looks fine to me.

--
JINMEI, Tatuya


From nobody Mon Oct 20 18:15:40 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C09E1ACFFB for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 18:15:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 O7SfjalZr2Uu for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 18:15:36 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0B951ACFF1 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 18:15:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2237; q=dns/txt; s=iport; t=1413854135; x=1415063735; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=YqtAMQ189qNnHj3/YeyYcDiN41cX3tN9KvOWFVSl9Kk=; b=g2H022wg9MvVZu0lNP3qiEKVDvxW9Pe+s541MuodEE2rbCtLpyzmsUt5 91UssDHQQjb5DQhP59GUAynTvlb0cEIhMpwlIdeE4t+CBPyyIJns4mtH5 R/b4HdTJwLQgnpZVNAx/d2TWRpLipV+GESpbivzMUUo3QMh0xQo+IY7d0 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AscFAGKzRVStJV2R/2dsb2JhbABcgw5TWATMLodRAoEQFgFyC4QCAQEBBDpLBAIBCBEEAQELFAkHMhQHAQEFAwIEEwiINw3FHgEBAQEBAQEBAgEBAQEBAQEBGo9vEQEfOAaDJ4EeAQSGLItVhEaIQzyGN4Zyhw2Dd2yBDzmBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,759,1406592000"; d="scan'208";a="365008368"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-4.cisco.com with ESMTP; 21 Oct 2014 01:15:29 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s9L1FTNx022301 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 21 Oct 2014 01:15:29 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Mon, 20 Oct 2014 20:15:29 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Experimental writing lab sessions at IETF 91
Thread-Index: AQHP6YqI5p0yXQr+p0CdLTBd+cMJTJwzRpYQgAZ+4vA=
Date: Tue, 21 Oct 2014 01:15:29 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6EB355@xmb-rcd-x04.cisco.com>
References: <20141016214527.GC2919@rfc-editor.org> <4F4E0084-69F1-47C4-8132-466CFD325476@cisco.com>
In-Reply-To: <4F4E0084-69F1-47C4-8132-466CFD325476@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.194]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/7lIWNON_uD_ajPVHWLpgwkkIO0E
Subject: [dhcwg] FW: Experimental writing lab sessions at IETF 91
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 21 Oct 2014 01:15:38 -0000

I tried sending this to a list of WG drafts (@tools.ietf.org), but for some=
 reason they are not going out. So, sending to dhcwg and hopefully that wil=
l reach the intended audience. Sorry if the delay meant all the slots are f=
ull.

- Bernie

-----Original Message-----
From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of RFC Editor
Sent: Thursday, October 16, 2014 5:45 PM
To: <wgchairs@ietf.org>; irsg@irtf.org
Cc: RFC Editor
Subject: Experimental writing lab sessions at IETF 91

Greetings WG and RG Chairs,

The RFC Editor Production Center (RPC) will be hosting an experimental writ=
ing lab aimed at helping authors improve their documents during IETF 91.  W=
e are hoping that you will distribute this message to authors who might ben=
efit from individual sessions with the RPC.  The authors that sign up will =
meet with one or two members of the editorial staff and will have 30 minute=
s to go through selected text from the document.  The editors will have rea=
d the selected text prior to the meeting and will go over any issues their =
review may reveal, for example, unclear passages, terminology inconsistenci=
es, and grammar and punctuation choices.

Authors may sign up for a time slot using the following Doodle poll (sign u=
ps are on a first-come, first-served basis):

http://doodle.com/icxnmct9krap798f

Note that this is not a technical review, nor is it an end-to-end review.  =
Questions of a technical nature may be redirected to the WG/RG or relevant =
chairs.  Because of the time constraints and the preparation time required =
for each session, it is not possible to review documents in their entirety.=
 =20

Once an author has signed up for a time slot, the RPC will send a confirmat=
ion email with a request for some additional information specific to the gi=
ven document and the author's goals for attending the session.  We ask that=
 the authors sign up for a session by
26 October, so the RFC Editor has enough time to review the document before=
 IETF 91.  The authors will be notified of the location for these sessions =
once the details have been solidified; the sessions will be in the hotel. =
=20

Thank you,
RFC Editor Team


From nobody Tue Oct 21 08:18:37 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DAAA1A875E for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 08:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 TcpAvOjIVXdQ for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 08:18:25 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F0061A7007 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 08:18:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8795; q=dns/txt; s=iport; t=1413904696; x=1415114296; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=yXU+JKDg/yofzuLy9CW0j2KSyOrg6n3YOuz+Za9bvPI=; b=g50MH2n1HZYlNqfiGFNR1Apt/b8GSGBdIhfoayGF/5igDiQpLWfJaKZ+ fgaGEG4YRTQpyQEozLAntTKVPct3YNRQ71K6UH30F9TYelopmiBtsJv2o 30NxZtorVTK00y0mHiCVfKTQWQAaVGdR+37Ze3VdXePsQi79Mhw+tze82 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFADJxRlStJA2B/2dsb2JhbABcgkhGU1gEyjSBcodLAoERFgFyC4QCAQEBBC1cAgEIEQQBAQsdBzIUCQgBAQQTCIg3DcNqAQEBAQEBAQEBAQEBAQEBAQEBAQEBF40OgxI3AQaDJ4EeBZIBhEaIQzyDCodlhUaEAYI0gUNsgUiBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,762,1406592000";  d="scan'208,217";a="365123274"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-6.cisco.com with ESMTP; 21 Oct 2014 15:18:15 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s9LFIFZ8004153 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 21 Oct 2014 15:18:15 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0195.001; Tue, 21 Oct 2014 10:18:15 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
Thread-Index: Ac/minMIxUbYwkSiQNCrNLgZzh2MnQGt7IhA
Date: Tue, 21 Oct 2014 15:18:14 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6ED689@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.120]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6ED689xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/UPQ4TmyEEisOaMAuQKEDFkePnNw
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 21 Oct 2014 15:18:33 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6ED689xmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Reminder - this WGLC is in progress and you have until Oct 27th to respond.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, October 12, 2014 10:14 PM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - R=
espond by Oct 27, 2014


Hi all,



This message starts the DHC working group last call to advance "Dynamic All=
ocation of Shared IPv4 Addresses", draft-ietf-dhc-dynamic-shared-v4allocati=
on-02, document as a Standards Track (Proposed Standard) RFC. The authors b=
elieve that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-02



Please send your comments by October 27th, 2014. If you do not feel this do=
cument should advance, please state your reasons why.



There are no IPR claims reported at this time.



Bernie Volz is the currently assigned shepherd for this document.



- Tomek & Bernie


--_000_489D13FBFA9B3E41812EA89F188F018E1B6ED689xmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1101993397;
	mso-list-type:hybrid;
	mso-list-template-ids:1383377822 -1324717298 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:23;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Reminder &#8211; this =
WGLC is in progress and you have until Oct 27<sup>th</sup> to respond.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Sunday, October 12, 2014 10:14 PM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation=
-02 - Respond by Oct 27, 2014<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Hi all,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This message starts the DHC working group last ca=
ll to advance &quot;Dynamic Allocation of Shared IPv4 Addresses&quot;, draf=
t-ietf-dhc-dynamic-shared-v4allocation-02, document as a Standards Track (P=
roposed Standard) RFC. The authors believe that
 this version is ready.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The draft is available here:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"http://tools.ietf.org/html/draft-ietf-=
dhc-dynamic-shared-v4allocation-02">http://tools.ietf.org/html/draft-ietf-d=
hc-dynamic-shared-v4allocation-02</a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please send your comments by October 27th, 2014. =
If you do not feel this document should advance, please state your reasons =
why.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There are no IPR claims reported at this time.<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bernie Volz is the currently assigned shepherd fo=
r this document.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6ED689xmbrcdx04ciscoc_--


From nobody Tue Oct 21 14:04:38 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA9D61A8547 for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 14:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 fTxgMzcv5F5z for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 14:04:35 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0A101A8703 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 14:04:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s9LL4YMc032610; Tue, 21 Oct 2014 14:04:34 -0700
Received: from XCH-PHX-109.sw.nos.boeing.com (xch-phx-109.sw.nos.boeing.com [130.247.25.36]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s9LL4Pi9032494 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for <dhcwg@ietf.org>; Tue, 21 Oct 2014 14:04:25 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.62]) by XCH-PHX-109.sw.nos.boeing.com ([169.254.9.87]) with mapi id 14.03.0181.006; Tue, 21 Oct 2014 14:04:24 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
Thread-Index: AQHP7IpE86ufnSyb5Um4uSjfpy56qZw7Cxlg
Date: Tue, 21 Oct 2014 21:04:24 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832D49C76@XCH-BLV-504.nw.nos.boeing.com>
References: <542D1698.7030203@gmail.com> <CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D18F3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6D1B3A@xmb-rcd-x04.cisco.com> <CAJE_bqe4xsP7eHBpvTZsw0VobpMnnG2MvYuMgXvKF+nrUS2yDw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B6D4548@xmb-rcd-x04.cisco.com> <5444F104.1060009@gmail.com> <CAJE_bqe9gG1QYNm2Vq1vhnw5VRhSEUFd_P-fM2ayKDbB17TAQQ@mail.gmail.com>
In-Reply-To: <CAJE_bqe9gG1QYNm2Vq1vhnw5VRhSEUFd_P-fM2ayKDbB17TAQQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Yt9F6Cm8pDeVAbps1KHnNUgfrCI
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 21 Oct 2014 21:04:37 -0000

I have been asleep at the wheel and should have posted this a long time ago=
.
Below are my comments based on the state of the document immediately
after the Toronto meeting. Not sure whether some/all of these are OBE.

Thanks - Fred
fred.l.templin@boeing.com



Comments:
*********
1) Abstract, would it be better to say:

  "IPv6 Prefix Options for Dynamic Host Configuration Protocol
   (DHCP) version 6 has since shoe-horned a new option for Prefix
   Delegation into DHCPv6." ?

2) Introduction, first paragraph, same suggestion as 1).

3) Section 4.2, suggested replacement text for Section 17.1.3,
   should it also say:

     ...that contains no
     addresses (IAADDR options encapsulated in IA_NA or IA_TA options),
     no delegated prefixes (IAPREFIX options encapsulated in IA_PD
     options, see RFC 3633) nor any future options ...

4) Section 4.2, final paragraph, I notice in several places the
   document says "without any addresses and delegated prefixes".
   Would it be better at the top of the document to define
   "stateful information" as something like: "addresses, prefixes,
   and/or any future options". Then throughout the document, you
   can just talk about "stateful information" when you want to
   include all of the above. Just an organizational thought - not
   critical to the understanding of the document.

5) Section 4.4.3, third paragraph, again it says "for all IA_NA
   and IA_PD options" - should it also say "for all future
   options of this nature" ? Same as with comments 3) and 4),
   should the document as a whole be reworded to be more
   inclusive to talk about future options in addition to
   IA_NA and IA_PD? (Maybe not - up to you.)

6) Final paragraph of P.10 has text very much like what I was
   trying to infer in comments 3), 4), and 5) above where it
   says:

   "the
   server sends back the IA with the corresponding IA Address (for
   inappropriate address), IA Prefix option (for inappropriate prefix)
   or other option appropriate for the type of the resource"

   Throughout the rest of the document, saying "or other option
   appropriate for the type of the resource" would satisfy the
   "future options" forward compatibility.

7) Near the bottom of page 13, I am having trouble parsing the
   following sentence:

     "In the case when the client included addresses in the IA,
     included addresses are appropriate for the link to which the
     client's interface is attached according to the server's explicit
     configuration information and they are not in use, the server MAY
     allocate these addresses to the client. "

   it looks like it is missing conjunctions, punctuation, or both,
   but it just doesn't "read well" to me. Could be a matter of
   personal opinion.

8) Section 4.5.2, final paragraph where it says:

                       "If the IA_PD contains no prefixes or
                       the prefixes are appropriate for the link to
                       which the requesting router's interface is
                       attached according to the delegating router's
                       explicit configuration information and if
                       prefixes are not in use, the delegating router
                       MAY assign prefixes to this IA_PD."

  Is "MAY" strong enough here? What if the client is depending
  on this particular type of behavior. Should it be a "SHOULD"
  instead?

9) Section 4.5.3, editorial, first sentence of paragraph 2 should
   say "The client also includes *an* IA option...".


From nobody Tue Oct 21 14:53:58 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59E2A1A87D2 for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 14:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.698
X-Spam-Level: 
X-Spam-Status: No, score=0.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_92=0.6, MIME_NO_TEXT=1.999, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 pMW_i6CQUTy1 for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 14:53:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 115B31A87C4 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 14:53:56 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 544E720012 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 17:54:46 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 69F7863A84; Tue, 21 Oct 2014 17:53:54 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 506DB63A82 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 17:53:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: dhcwg <dhcwg@ietf.org>
X-Attribution: mcr
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 21 Oct 2014 17:53:54 -0400
Message-ID: <4117.1413928434@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/SpvLb1ZqG8lJmIEIIXqfbWEuOS0
Subject: [dhcwg] RFC3315 and Hop Limit
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 21 Oct 2014 21:53:57 -0000

--=-=-=


I could not find any advice in RFC3315 as to what to set the IPv6
HOP Limit to for multicast'ed DHCPv6 messages.

I would have thought that the sender should set it to 255, and the
sender should validate that it is 255, to be sure that it's onlink.
This is what mDNS/Bonjour does, but maybe 3315 predates that thinking.

Should 3315bis say something different?
(Clearly, it has to be backwards compatible for awhile)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVEbV74CLcPvd0N1lAQIY2Af8DsQQmwsrHW3J9r0cngk6NLe4brawukFH
6g6oT2qxHq6E/bZfqmuHgHseUcpR6PTejh884LQgqbawkvJjktzEnevkY6vqYO4l
cWWxRsSdZDbvZeXJdPmLBg70nUd9raO1KXDdX9Pv02K0YV8VeY7sm62SnkKRTqJB
OTlEwNAtHG/6GObs0XpSq893ABiVjBnQQmhXwFkSBzdAxFHrqk9LWv3Jz+tkxwQZ
pyd1+qJNccPw2Z7h1kMq7kGuiLQB3Y6co22nmJNmhbjtdDq95wCPTWDDWz4IBLS0
tez4r/sqz+rsOjAt4Mm7J32T3LIOh0bfhFHWbkH27B5MSGWf2Dfasw==
=lrxZ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Oct 21 15:31:02 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55E0A1A8773 for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 15:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_92=0.6, SPF_PASS=-0.001] autolearn=no
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 PH7_PHQ8mKck for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 15:31:00 -0700 (PDT)
Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DAF21A876F for <dhcwg@ietf.org>; Tue, 21 Oct 2014 15:30:59 -0700 (PDT)
Received: by mail-qc0-f177.google.com with SMTP id i8so438287qcq.36 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 15:30:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=l6ltruVEAZOGlDWpcQhYBwnPYPdohtPzeNTDzYPhas4=; b=xYejUV5mwnycXHsk7D+1d6mDr+c9WCRDriCbrEKKymviiRu8G3aRejZ3BrsDxQuACq VxjmYKl/AUILqKuSGeMRbYAwfVyjg7CdRqMU0WOi4CtVh791e/eip7OO7IHEYLaZXTQX IwusTO7bU9y1t3IyUELi5bfkrZz6Gh+zFvzI6RvLic8RFCZNeunj658sCO2OkwVrAS+h L2NeysiKMNd9qhfVylmo+h7cv8ufqWooTnf6r7fq5cqz1qw8z3olGI5qIj1JG8QFLbIX w0FIm9bDsVkqMqbAcPbYeTMleY8yg/EF+/MIVHWzMzlF6nPDa7CAZrIktmgADp8Auy9z A7ow==
X-Received: by 10.229.244.1 with SMTP id lo1mr1720289qcb.29.1413930659201; Tue, 21 Oct 2014 15:30:59 -0700 (PDT)
Received: from [10.86.253.23] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id l2sm11897841qao.34.2014.10.21.15.30.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 15:30:58 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <4117.1413928434@sandelman.ca>
Date: Tue, 21 Oct 2014 18:31:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9BCD98C-990B-4F13-AD88-014C4711BB2E@gmail.com>
References: <4117.1413928434@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/lNTqvqkZh46CVcefwk4QiFkeDmY
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] RFC3315 and Hop Limit
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 21 Oct 2014 22:31:01 -0000

On Oct 21, 2014, at 5:53 PM 10/21/14, Michael Richardson =
<mcr+ietf@sandelman.ca> wrote:

>=20
> I could not find any advice in RFC3315 as to what to set the IPv6
> HOP Limit to for multicast'ed DHCPv6 messages.
>=20
> I would have thought that the sender should set it to 255, and the
> sender should validate that it is 255, to be sure that it's onlink.
> This is what mDNS/Bonjour does, but maybe 3315 predates that thinking.

I don't think the 255 hop count limit from RFC 6762 applies.  RFC 6762 =
mentions the use of the 255 hop count limit, but only for backward =
compatibility.  RFC 6762 does not mandate the use of the 255 hop count =
limit as a mandatory requirement of mDNS.  I read RFC 6762 to specify =
that mDNS depends on the network infrastructure for limiting the =
distance of over which datagrams with a link-scope multicast address are =
forwarded.

DHCPv6 uses a link-scope multicast address for All_DHCP_Relay_Agents and =
a site-scope multicast address for All_DHCP_Servers.  In my opinion, it =
is fine for DHCPv6 to trust the network infrastructure to limit the =
forwarding of datagrams sent to both of those multicast addresses.

- Ralph

> Should 3315bis say something different?
> (Clearly, it has to be backwards compatible for awhile)
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Tue Oct 21 20:38:52 2014
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2745C1A8A77 for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 20:38:50 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 zN3R08L-pwbx for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 20:38:48 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D7901A8A75 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 20:38:48 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id bj1so2787659pad.15 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 20:38:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=NeKdS2dwCPTfMqHl3gJHG7bT6xWNRmSx29BPv09RF+w=; b=J4NibHGARdAgw1u34ApjnEQ0VXemSv+eUx0sO879saaecG34p4V0DhmTmfasQA8Vy0 UE0w5MZZT2zpcu8czSr3Ysjt317TQDEWE8NTvo8gUf0Wq5SVygs/i73lKvYDJC/x63N6 I2mzthvcB62R0+i1lyKiVwJ5O568AIRikZ5ocAyuAdcif0WUR77fuJYikSsYac+9EM6K rirqn4XNLK1rLXhFMmK0RNptDxNJSxywgIChBFT+e8et74tauGxZs96GKtWk8oubByZY k5mIwidz+e36rm3AvyoZ7d3eNgm4NvsznZWsvvCXn1itgwGXJV9yPVb00Tp1LAqj7St6 c92A==
X-Received: by 10.66.243.3 with SMTP id wu3mr39570844pac.87.1413949127776; Tue, 21 Oct 2014 20:38:47 -0700 (PDT)
Received: from [10.2.1.205] ([58.205.200.20]) by mx.google.com with ESMTPSA id u6sm13166185pdi.61.2014.10.21.20.38.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 20:38:47 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_1E5CBED3-5645-4748-A070-30E293768267"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6ED689@xmb-rcd-x04.cisco.com>
Date: Wed, 22 Oct 2014 11:38:37 +0800
Message-Id: <45B6B62C-FE51-41D9-8300-0D210D691D0A@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6ED689@xmb-rcd-x04.cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/x45taF_O7zXrFKR-yV-D1FwibjY
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Oct 2014 03:38:50 -0000

--Apple-Mail=_1E5CBED3-5645-4748-A070-30E293768267
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Dear all,=20

As one of the co-authors, I support this document to move forward. This =
draft describes how to allocate port-set based on the DHCP 4o6 with a =
newly defined DHCPv4 option. The comments from the mailing list has been =
addressed, and I think it ready to go.=20

Thanks,=20
Qi


On Oct 21, 2014, at 11:18 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

> Reminder =96 this WGLC is in progress and you have until Oct 27th to =
respond.
> =20
> -          Bernie
> =20
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz =
(volz)
> Sent: Sunday, October 12, 2014 10:14 PM
> To: dhcwg@ietf.org
> Subject: [dhcwg] WGLC for =
draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
> =20
> Hi all,
> =20
> This message starts the DHC working group last call to advance =
"Dynamic Allocation of Shared IPv4 Addresses", =
draft-ietf-dhc-dynamic-shared-v4allocation-02, document as a Standards =
Track (Proposed Standard) RFC. The authors believe that this version is =
ready.
> =20
> The draft is available here:
> =
http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-02
> =20
> Please send your comments by October 27th, 2014. If you do not feel =
this document should advance, please state your reasons why.
> =20
> There are no IPR claims reported at this time.
> =20
> Bernie Volz is the currently assigned shepherd for this document.
> =20
> - Tomek & Bernie
> =20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


--Apple-Mail=_1E5CBED3-5645-4748-A070-30E293768267
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Dear =
all,&nbsp;<div><br></div><div>As one of the co-authors, I support this =
document to move forward. This draft describes how to allocate port-set =
based on the DHCP 4o6 with a newly defined DHCPv4 option. The comments =
from the mailing list has been addressed, and I think it ready to =
go.&nbsp;</div><div><br></div><div>Thanks,&nbsp;</div><div>Qi</div><div><b=
r></div><div><br><div><div>On Oct 21, 2014, at 11:18 PM, Bernie Volz =
(volz) &lt;<a href=3D"mailto:volz@cisco.com">volz@cisco.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;"><div class=3D"WordSection1" =
style=3D"page: WordSection1;"><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span style=3D"color: =
rgb(31, 73, 125);">Reminder =96 this WGLC is in progress and you have =
until Oct 27<sup>th</sup><span =
class=3D"Apple-converted-space">&nbsp;</span>to =
respond.<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span style=3D"color: =
rgb(31, 73, 125);">&nbsp;</span></div><div style=3D"margin: 0in 0in =
0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif; =
text-indent: -0.25in;"><span style=3D"color: rgb(31, 73, =
125);"><span>-<span style=3D"font-style: normal; font-variant: normal; =
font-weight: normal; font-size: 7pt; line-height: normal; font-family: =
'Times New =
Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
style=3D"color: rgb(31, 73, 125);">Bernie<o:p></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"color: rgb(31, 73, =
125);">&nbsp;</span></div><div><div style=3D"border-style: solid none =
none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; =
padding: 3pt 0in 0in;"><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><b><span =
style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif;"><span =
class=3D"Apple-converted-space">&nbsp;</span>dhcwg [<a =
href=3D"mailto:dhcwg-bounces@ietf.org">mailto:dhcwg-bounces@ietf.org</a>]<=
span class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Bernie Volz =
(volz)<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Sunday, October 12, 2014 =
10:14 PM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[dhcwg] WGLC for =
draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, =
2014<o:p></o:p></span></div></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Hi =
all,<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;"><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;">This message starts the DHC working group last =
call to advance "Dynamic Allocation of Shared IPv4 Addresses", =
draft-ietf-dhc-dynamic-shared-v4allocation-02, document as a Standards =
Track (Proposed Standard) RFC. The authors believe that this version is =
ready.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The draft =
is available here:<o:p></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><a =
href=3D"http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocat=
ion-02" style=3D"color: purple; text-decoration: =
underline;">http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4all=
ocation-02</a><o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Please =
send your comments by October 27th, 2014. If you do not feel this =
document should advance, please state your reasons =
why.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;"><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;">There are no IPR claims reported at this =
time.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;"><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;">Bernie Volz is the currently assigned shepherd for =
this document.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">- Tomek =
&amp; Bernie<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div></div>________________________________=
_______________<br>dhcwg mailing list<br><a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/dhcwg</div></blockquote></div><br></div></body></html>=

--Apple-Mail=_1E5CBED3-5645-4748-A070-30E293768267--


From nobody Tue Oct 21 20:55:00 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5631A8A7C for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 20:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 XT2tjNlfuo1t for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 20:54:57 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFECB1A8A7A for <dhcwg@ietf.org>; Tue, 21 Oct 2014 20:54:57 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id CBF20DA01B5 for <dhcwg@ietf.org>; Wed, 22 Oct 2014 03:57:25 +0000 (UTC)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 5008953E080; Tue, 21 Oct 2014 20:54:27 -0700 (PDT)
Received: from vpna-167.vpn.nominum.com (64.89.227.167) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 21 Oct 2014 20:54:26 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6ED689@xmb-rcd-x04.cisco.com>
Date: Tue, 21 Oct 2014 23:54:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <8B0C75DA-A7AB-4EE3-931D-ECEB3F6A9E39@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6ED689@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [64.89.227.167]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/VfJ4VNuZo4q6pWyUGTcJolYmCyI
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Oct 2014 03:54:59 -0000

On Oct 21, 2014, at 11:18 AM, Bernie Volz (volz) <volz@cisco.com> wrote:
> Reminder =96 this WGLC is in progress and you have until Oct 27th to =
respond.

The document has some bugs and isn't ready to be published, IMHO.   =
E.g., the mention of INIT-REBOOT suggests that the clients sends a =
DHCPDISCOVER, which is wrong.   I think it needs a close review, but I =
don't have time right now.  I don't think there's anything really major, =
but it would be good to get it right.


From nobody Wed Oct 22 09:43:30 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A36811ACDDA for <dhcwg@ietfa.amsl.com>; Wed, 22 Oct 2014 09:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_92=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
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 QxNB0leD6z92 for <dhcwg@ietfa.amsl.com>; Wed, 22 Oct 2014 09:43:27 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A87C1ACDCC for <dhcwg@ietf.org>; Wed, 22 Oct 2014 09:43:26 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 34036200A7; Wed, 22 Oct 2014 12:44:05 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 73E4263A84; Wed, 22 Oct 2014 12:43:10 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 627A763A21; Wed, 22 Oct 2014 12:43:10 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <B9BCD98C-990B-4F13-AD88-014C4711BB2E@gmail.com>
References: <4117.1413928434@sandelman.ca> <B9BCD98C-990B-4F13-AD88-014C4711BB2E@gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 22 Oct 2014 12:43:10 -0400
Message-ID: <10209.1413996190@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/n0LdDUf7I7CIkcACeHzHY5q5Te8
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] RFC3315 and Hop Limit
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Oct 2014 16:43:28 -0000

--=-=-=


Ralph Droms <rdroms.ietf@gmail.com> wrote:
    >> I could not find any advice in RFC3315 as to what to set the IPv6 HOP
    >> Limit to for multicast'ed DHCPv6 messages.
    >>
    >> I would have thought that the sender should set it to 255, and the
    >> sender should validate that it is 255, to be sure that it's onlink.
    >> This is what mDNS/Bonjour does, but maybe 3315 predates that thinking.

    > I don't think the 255 hop count limit from RFC 6762 applies.  RFC 6762
    > mentions the use of the 255 hop count limit, but only for backward
    > compatibility.  RFC 6762 does not mandate the use of the 255 hop count

Ah, I know that we argued back and forth about whether or not HOP Limit=1,
or HOP Limit=255 was a better way to keep things link-local, and I was
surprised upon examining 3315 that there was no talk at all about that,
then I realized that it predated that discussion.

I'd always figured that if someone was going to screw up routing so much,
as to wind up forwarding multicast is if it was unicast, that they likely
also didn't decrement the TTL either....

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVEfenoCLcPvd0N1lAQISMQgAuMZCr2a75hzDzLzNHwhdGbus8lZKsKK/
ShdCbGrL09QL3H+mH5vIDR92qQyLk2X4NBeHqYgwELTTYjWCFhus+7PcQvm//xzS
McPm/6m2/3vWpY+K4sfr7u2WecG7rw8W3FEXvtemUNojeK0boapxSf6MK2Njz05C
2TVOc+wPSvgTUbTIDeDW9b90Kw1lV/0PNY0A/3kV7Qa9K1HIn5x6JIAuGvlmVuss
ECOlHvnpFF5JJTMkSj+eFOqwMZjqeHUbtYDfNWEDhmD4d9usJlmIWeVw3PlgEUr1
xUImywvIu3h5ZDZbY2sKJGeFlG3QKk/VW2RRAT1GCKUrqX9ZqTtRWw==
=/yFB
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Oct 22 13:23:10 2014
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE9A51A1A04 for <dhcwg@ietfa.amsl.com>; Wed, 22 Oct 2014 13:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 GsBrDy02ukn0 for <dhcwg@ietfa.amsl.com>; Wed, 22 Oct 2014 13:23:05 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 467191A0372 for <dhcwg@ietf.org>; Wed, 22 Oct 2014 13:23:05 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id a1so4727935wgh.9 for <dhcwg@ietf.org>; Wed, 22 Oct 2014 13:23:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=rWLs5ckKvMM1VE/CjjZFXtpgDKkDFZdnOEJbQ9092qA=; b=DPUwpDymkE6tX5tVDYm1BA8/O+HN7TwCiz8OAkGwFJ0rGHVyoHwdSXTLDDygKy0arn IjJUXXyom0nYgsm6SW8Gp9pcl6JTzR62f/NSKQ2G18hqroDirmr91/nDFcXBTqxmBHCF YH1PC8PPrwhMast3v9qj3tEXtfDsVc3xF+WyruXtCvLdrHUngi7YOzDrhyjBrBs9vLKH NUkPqWKs2YDoTDtkKl/hYUlAHxArGJsqATQhhFzu4mI5zili1CNe6NFidEFUEmLHjdL0 cK1nMogFWW1um1t2KLGm0Fpla2iWUgl3GAzAvCugLKyu70kH9HFCl9c2nsPPl95r5zhl x6MA==
X-Received: by 10.194.189.82 with SMTP id gg18mr226275wjc.115.1414009383884; Wed, 22 Oct 2014 13:23:03 -0700 (PDT)
Received: from [192.168.10.11] (89-79-26-47.dynamic.chello.pl. [89.79.26.47]) by mx.google.com with ESMTPSA id ky3sm20039453wjb.39.2014.10.22.13.23.02 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Oct 2014 13:23:03 -0700 (PDT)
Message-ID: <54481226.7040700@gmail.com>
Date: Wed, 22 Oct 2014 22:23:02 +0200
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>,  "Bernie Volz (volz)" <volz@cisco.com>
References: <542D1698.7030203@gmail.com>	<CAJE_bqcJS45ULDLaGgzgE5ZeS-hFZhWUX4819-T_jObroJnv4Q@mail.gmail.com>	<489D13FBFA9B3E41812EA89F188F018E1B6CEE2D@xmb-rcd-x04.cisco.com> <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com>
In-Reply-To: <CAJE_bqeNyWa=hxyaaDRqUR0zgnfQCSZZOnToXSaSWm0m4CjUYg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/_wOUWQ1HYY5USFPfTCV2QM8y82U
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Please review version -07 of draft-ietf-dhc-dhcpv6-stateful-issues
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Oct 2014 20:23:08 -0000

On 16/10/14 19:33, ç¥žæ˜Žé�”å“‰ wrote:
> At Wed, 15 Oct 2014 16:16:36 +0000,
> "Bernie Volz (volz)" <volz@cisco.com> wrote:
> 
>> First, I have a couple of higher level points to discuss:
>>
>> - What's the final goal of this document?
>>
>> ** The goal here is for this work to be an RFC.
> 
> Okay, in that case I'll also check overall readability as a separate
> document for future versions.
> 
>> Specific comments to the draft text follow:
>>
>> - Title: now that our main focus is the mixed use of IA_NA and IA_PD
>>   rather than generalizing the concept of stateful resources, I think
>>   it makes more sense to reflect it in the title, for example,
>>   "Issues and Recommendations with Multiple DHCPv6 IA Options".
>>   See also my comments on Section 3 (terminology) below.
>>
>> ** We will leave the title as it is.
> 
> Hmm, if we are going to even more focus on the specific case of the
> mix of IA_NA and IA_PD as you'll mention below, and also if it's
> supposed to be published as a single document, I'd avoid making the
> tile too generic.  So, I'd even make it more specific such as
> 
>     Issues and Recommendations with Mixed Use of DHCPv6 Address
>     Assignment and Prefix Delegation
> 
> But it's ultimately up to the authors.  If the authors still thinks
> the current title is the best, I won't insist further.
> 
>> - Abstract: this is more about readability (see above), but I'm afraid
>>   the current abstract text wouldn't be really helpful for first-time
>>   readers (on the other hand, it's not a problem for "me", because I
>>   already know what it is). [...]
>>
>> ** We will leave the abstract pretty much as is. We change last sentence to mention that the (RFC) changes are to address the identified issues.
> 
> Ditto.  But I'll see how the abstract of the next version will look
> like.
> 
>> - Section 1, regarding the same text and this one:
> [...]
>>   IMO, this document should talk a bit more about the "framework".
> [...]
>> ** We will rework the Introduction to remove the 'framework' concept and just focus on the IA_NA/IA_PD issues. When and if there are future IA's, those documents can indicate whether they integrate into this work (i.e., add IA_foo to IA_NA, IA_PD in the stateful issues document) or if they are separate and independent.
> 
> Okay.
> 
>> - Section 4.2: replacement for RFC 3315 17.1.3:
>>
>>      The client MUST ignore any Advertise message that contains no
>>      addresses (IAADDR options encapsulated in IA_NA or IA_TA options)
>>      and no delegated prefixes (IAPREFIX options encapsulated in IA_PD
>>      options, see RFC 3633) with the exception that the client
>>      MUST process an included SOL_MAX_RT option (RFC 7083), MUST
>>      process an included INF_MAX_RT option (RFC 7083), and MAY
>>      display any associated status message(s) to the user.
>>
>>   It's awkward to see it mention prefixes while this version
>>   intentionally cancels the idea of "unified" text for renew/rebind.
>>   It's not clear to me why Section 17.1.3 (regarding advertise) still
>>   needs to provide "unified" text.
>>
>> ** While we could drop "and no delegated prefixes (...)", does that really help significantly especially since RFC 7083 material is being pulled in already? Also, in this case if we leave it out, people may be confused about what happens if there are no addresses but prefixes. (For most of the other changes later, RFC 3633 already covers these changes as it generally implies to replace "addresses" with "delegated prefixes" in much of the Reply processing. And, we've provided the revised text where needed for 3633.) Also, RFC 3633 already points to 17.1.3 of 3315 and this avoids having to specify replacement text for 3633.
> 
> I wouldn't necessarily insist on it, it just looks awkward to me but
> otherwise is not really a problem.  Maybe it helps if you note that
> you're providing unified text with the reason of why (e.g., because
> RFC 3633 doesn't describe its own version of this behavior but just
> refers to RFC 3315.)
> 
>> - Section 4.3: I don't understand the following text:
>>
>>    [...] To deal
>>    with the case where servers have not yet been updated to do that,
>>    clients MUST use the shortest (explicit or implicit) T1/T2 times
>>    (larger than 0), from the same IA option, in the Reply.  T1/T2 times
>>    from other IAs are ignored.
>>
>>   I guess it tries to address the corner case I pointed out for the
>>   previous version of the draft:
>>   http://www.ietf.org/mail-archive/web/dhcwg/current/msg15663.html
>>   but I don't even understand what the client would do in this case
>>   based on the new text.  To recap, what should happen if the client
>>   sees the following two sets of T1/T2 according to the above text?
>>   - T1a = 10, T2a = 20
>>   - T1b = 0, T2b = 5
>>
>> ** We will include this example and explain it. Note that T1b  = 0 means that the client must calculate the T1 time (50% of lifetime) and that it obviously needs to be less than T2b. So, in this case the T1b =0, T2b = 5 would be used but the T1b time is the 'implicit' time (we can't give the value since the lifetimes are not specified).
> 
> Hmm, then the phrase "(larger than 0)" can be misleading.
> 
>> ** There are perhaps other cases, for example T1a = 10, T2a = 20, T1b = 5, T2b = 25 that are a bit more interesting since picking (b) means T1=5/T2=25 which means T2 is longer than T2a.
> 
> Personally, I'm okay with just dismissing such a case as a server
> misconfiguration (as we basically require the server use the same
> T1/T2 values for all IAs).  I'd be fine unless a compliant client
> behavior leads to a clearly broken result, such as T1 > T2.
> 
>> ** Perhaps we need to review whether the shortest 'effective' T1 and independently shortest 'effective' T2 are a better choice (obviously the client would have to adjust T1 if this means T1>T2, but I'm not sure that could even happen since for any individual IA, T1 must be less than or equal to T2). Note that by 'effective' here I mean either the server supplied value or, if 0, the client determined value based on the lifetimes within that IA.  If we used that algorithm, for your case the answer would not change; for my example T1 would be and T2 would be 20 which are probably better values for this case.
> 
> See above.  IMO it doesn't have to be too complicated and we can
> basically leave it to the diligence of the server
> implementation/operation.  All I want to see is a clear and
> well-defined client behavior.
> 
>> ** Comments about this issue (and perhaps additional case analysis if appropriate) would be useful.
>>
>> - Section 4.4.5: does this mean, if the client has bindings of
>>   multiple IAs, it should (effectively) abandon all of the bindings
>>   and establish new bindings for all of the IAs starting from Solicit?
>>   If so, it makes sense to me, but it's not really clear from the
>>   text, and I suggest clarifying that point.
>>
>>      When the client receives a NotOnLink status from the server in
>>      response to a Confirm message, the client performs DHCP server
>>      solicitation, as described in section 17, and client-initiated
>>      configuration as described in section 18.
>>
>> ** We will create a 3315bis ticket since this is pre-existing text used "as is" from 3315. And, this is not an issue that is particular to this draft. Note that Confirm is IA_NA (IA_TA) specific as IA_PD requires a Rebind; so this is an open issue in the original 3315 and should be added by the bis document. It also is more of a clarification, rather than a "change". The bis document can clarify that when a client sends a Solicit, it MUST not be using any of the addresses or delegated prefixes for the bindings included in the Solicit.
> 
> I'm not sure if I understand this as a response to my comment...to
> clarify my point, what I wanted to raise is what should happen if:
> 
> - A client with bindings for both an IA_NA and an IA_PD detects it may
>   have moved to a different link, so sends a Confirm for the IA_NA.
> - The client receives a NotOnLink status in response to it.
> 
> Should the client (effectively) discards the binding for IA_PD (and
> for IA_NA) and try to establish new bindings for both?  Or should it
> keep the binding for IA_PD (but it would break the proposed model of
> this draft)?  I thought the intent is the former, and I thought it's
> not clear enough and suggested to clarify it in the text.
> 
> --
> JINMEI, Tatuya
> 

Jinmei,

To clarify your example. In case the client has both IA_NA and IA_PD,
the client will not send a Confirm message, but will rather use a Rebind
message and include both IA_NA and IA_PD in this Rebind message. From
the stateful issues draft:

"IA_PD requires verification that the server has the binding for the
   IAs.  In that case a client MUST use the Rebind message in place of
   the Confirm message and it MUST include all of its bindings, even
   address IAs."

As a result, the client will not receive a NotOnLink status code in this
case, because NotOnLink is not sent in response to a Rebind message.

Nevertheless, we agree that there are other cases when the client should
or must "restart the server discovery process" and RFC3315 is not
specific what the client should do with the valid bindings that the
client has been using so far. We believe that this is a generic problem
in the RFC3315 (not really specific to the scope of the stateful issues
draft) and the RFC3315bis is the best place to clarify it. I submitted
the ticket to cover it in the RFC3315bis doc:
http://trac.tools.ietf.org/group/dhcpv6bis/ticket/126

Marcin


From nobody Wed Oct 22 13:31:17 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EDC41A1AD9; Wed, 22 Oct 2014 13:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 3kMowP_Gp20x; Wed, 22 Oct 2014 13:31:10 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0320F1A1AF5; Wed, 22 Oct 2014 13:31:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141022203109.15132.28672.idtracker@ietfa.amsl.com>
Date: Wed, 22 Oct 2014 13:31:09 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/dp111TMXRqZY1yQ1ZppyxUK828M
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-stateful-issues-08.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Oct 2014 20:31:11 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Issues and Recommendations with Multiple Stateful DHCPv6 Options
        Authors         : Ole Troan
                          Bernie Volz
                          Marcin Siodelski
	Filename        : draft-ietf-dhc-dhcpv6-stateful-issues-08.txt
	Pages           : 21
	Date            : 2014-10-22

Abstract:
   Dynamic Host Configuration Protocol for IPv6 (DHCPv6) was not written
   with the expectation that additional stateful DHCPv6 options would be
   developed.  IPv6 Prefix Options for Dynamic Host Configuration
   Protocol (DHCP) version 6 shoe-horned the new options for Prefix
   Delegation into DHCPv6.  Implementation experience of the CPE model
   described in RFC 7084 has shown multiple issues with the DHCPv6
   protocol in supporting multiple stateful options.  This document
   updates RFC 3315 and RFC 3633 to address the identified issues.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv6-stateful-issues-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Oct 22 14:09:46 2014
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E64771A1B6F for <dhcwg@ietfa.amsl.com>; Wed, 22 Oct 2014 14:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 UCu0Ls1qlm6B for <dhcwg@ietfa.amsl.com>; Wed, 22 Oct 2014 14:09:26 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0E5B1A1B92 for <dhcwg@ietf.org>; Wed, 22 Oct 2014 14:09:25 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id z12so4662325wgg.13 for <dhcwg@ietf.org>; Wed, 22 Oct 2014 14:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=vivdU9JcHso83yZ0ieq15e5ZUlTjcDbcfcN3hV7T/kU=; b=Ut98SEH/EhXi39q+1a28jtKLOxDT7Z3AS7399HoSqNcb3b4ogkwFhOj374/JiUlbe8 722Iz5EOptw1JrhpB17dhhMJ6Njb92knZVxz3rAQo7iE3S3szDOYin5xzIrx8d7DynZZ tSKEq7WWo5588XoNV93M4QzV1z+6mwOonCY10SSqTK9EGzihaXPe4q4zKGbQTvx5lgTj CRGJAcIO0CpxulMmtPDfUSLYDv5MnClxwzIT5gX5khLUP/PKnIrp2Xbi+jxgzfBT3MFS KUlqMpKf+RtXIwW6+toe9/7Rr2c3R/RyAEV16e4hghIsmuEl8+TOY/Q24Ea99zMXC7Jz P/dg==
X-Received: by 10.180.9.65 with SMTP id x1mr8312807wia.30.1414012164531; Wed, 22 Oct 2014 14:09:24 -0700 (PDT)
Received: from [192.168.10.11] (89-79-26-47.dynamic.chello.pl. [89.79.26.47]) by mx.google.com with ESMTPSA id u2sm20174659wjz.11.2014.10.22.14.09.23 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Oct 2014 14:09:23 -0700 (PDT)
Message-ID: <54481D03.4040408@gmail.com>
Date: Wed, 22 Oct 2014 23:09:23 +0200
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/UU_uSpk5X4Ptgh7Dqn3pmo1LDMc
Subject: [dhcwg] Version -08 of draft-ietf-dhc-dhcpv6-stateful-issues posted
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 22 Oct 2014 21:09:37 -0000

Hi All,

The version -08 of the draft-ietf-dhc-dhcpv6-stateful-issues has been
published. And, it is available here:

https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/

This version incorporates updates to address the most recent comments we
received on the mailing list (within the last month, I guess). Thanks to
Jinmei and Andrew Y. for reviewing the draft. We are also hoping to
receive some more comments from other DHC folks.

Summary of changes:
- Minor update to the abstract: added "to address the identified issues"
at the end, to make it clear that the intent of the document is not only
to identify issues, but also to resolve them
- Removed the concept of "framework for future IAs" in the introduction,
as it turned out to be unclear what the "framework" was intended to be.
Also, with this change we want to be clear that the draft is intended to
resolve the problem of coexistence of IA_NA and IA_PD in a single DHCP
session, rather than be a generic text to address the problem of
coexistence of any IAs.
- Clarified that IA_TA is out of scope for the document.
- Terminology: removed redundant "Resource" and clarified that IA in
this context is IA_NA or/and IA_PD.
- Moved the text about motivation for keeping single session (rather
than multiple sessions) for multiple IA options from the introduction to
the "Handling of Multiple IA Options Types".
- Edits to the "Placement of Status Codes" section to limit the scope to
IA_NA and IA_PD only.
- New text about the client behavior when the server sends different
T1/T2 times for different IAs. The previous text appeared to be too
specific about the selection of T1/T2 and there were concerns about some
corner cases that it didn't cover well. The new text gives a more
general guideline for selecting T1/T2 times from multiple IAs and leaves
the details up to the implementations.
- Fixes in the Reply message handling.
- Minor changes to acknowledgments.

Please review.

Marcin


From nobody Wed Oct 22 19:36:20 2014
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 938E91A6F32 for <dhcwg@ietfa.amsl.com>; Wed, 22 Oct 2014 19:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 0V3M2Fvbk33r for <dhcwg@ietfa.amsl.com>; Wed, 22 Oct 2014 19:36:16 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F34F01A3BA3 for <dhcwg@ietf.org>; Wed, 22 Oct 2014 19:36:15 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNY28416; Thu, 23 Oct 2014 02:36:13 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Oct 2014 03:36:12 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.22]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Thu, 23 Oct 2014 10:36:07 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
Thread-Index: Ac/minMIxUbYwkSiQNCrNLgZzh2MnQGt7IhAAElmUFA=
Date: Thu, 23 Oct 2014 02:36:06 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AF6812F@nkgeml512-mbx.china.huawei.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6ED689@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6ED689@xmb-rcd-x04.cisco.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923AF6812Fnkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/H7BFvkFIwfEGlFa0yozz2xHP2UI
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 23 Oct 2014 02:36:18 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B923AF6812Fnkgeml512mbxchi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNCkkgaGF2ZSByZXZpZXdlZCB0aGlzIGRvY3VtZW50IGFuZCBzdXBwb3J0IHRvIG1vdmUg
aXQgZm9yd2FyZC4gVGhpcyBkcmFmdCBzb2x2ZXMgYSByZWFsIGlzc3VlIG9uIGhvdyB0byBhbGxv
Y2F0ZSBwb3J0LXNldCBiYXNlZCBvbiB0aGUgREhDUCA0bzYuIFRoZSBkb2N1bWVudCBoYXZlIG5v
IG1ham9yIGlzc3VlIGFsdGhvdWdoIHRoZXJlIGFyZSBhIGZldyBuaXRzLCB3aGljaCBjYW4gYmUg
c29sdmVkIGJ5IGEgcXVpY2sgdXBkYXRlIHZlcnNpb24uDQoNCkFsc28sIHRoZSBzZWN1cml0eSBj
b25zaWRlcmF0aW9uIGhhcyBhIHJlZmVyZW5jZSB0byBhbiBpbmRpdmlkdWFsIGRyYWZ0LiBJdCBt
YXkgbm90IGJlIHByb3Blci4NCg0KVW51c2VkIFJlZmVyZW5jZTogJ0ktRC5pZXRmLXNvZnR3aXJl
LWx3NG92ZXI2Jw0KVW51c2VkIFJlZmVyZW5jZTogJ1JGQzMzMTUnDQpVbnVzZWQgUmVmZXJlbmNl
OiAnUkZDMzkyNycNCkRvd25yZWY6IE5vcm1hdGl2ZSByZWZlcmVuY2UgdG8gYW4gSW5mb3JtYXRp
b25hbCBSRkM6IFJGQyA2MjY5DQoNCkJlc3QgcmVnYXJkcywNCg0KU2hlbmcNCg0KRnJvbTogZGhj
d2cgW21haWx0bzpkaGN3Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQmVybmllIFZv
bHogKHZvbHopDQpTZW50OiBUdWVzZGF5LCBPY3RvYmVyIDIxLCAyMDE0IDExOjE4IFBNDQpUbzog
ZGhjd2dAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYt
ZGhjLWR5bmFtaWMtc2hhcmVkLXY0YWxsb2NhdGlvbi0wMiAtIFJlc3BvbmQgYnkgT2N0IDI3LCAy
MDE0DQoNClJlbWluZGVyIOKAkyB0aGlzIFdHTEMgaXMgaW4gcHJvZ3Jlc3MgYW5kIHlvdSBoYXZl
IHVudGlsIE9jdCAyN3RoIHRvIHJlc3BvbmQuDQoNCg0KLSAgICAgICAgQmVybmllDQoNCkZyb206
IGRoY3dnIFttYWlsdG86ZGhjd2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEJlcm5p
ZSBWb2x6ICh2b2x6KQ0KU2VudDogU3VuZGF5LCBPY3RvYmVyIDEyLCAyMDE0IDEwOjE0IFBNDQpU
bzogZGhjd2dAaWV0Zi5vcmc8bWFpbHRvOmRoY3dnQGlldGYub3JnPg0KU3ViamVjdDogW2RoY3dn
XSBXR0xDIGZvciBkcmFmdC1pZXRmLWRoYy1keW5hbWljLXNoYXJlZC12NGFsbG9jYXRpb24tMDIg
LSBSZXNwb25kIGJ5IE9jdCAyNywgMjAxNA0KDQoNCkhpIGFsbCwNCg0KDQoNClRoaXMgbWVzc2Fn
ZSBzdGFydHMgdGhlIERIQyB3b3JraW5nIGdyb3VwIGxhc3QgY2FsbCB0byBhZHZhbmNlICJEeW5h
bWljIEFsbG9jYXRpb24gb2YgU2hhcmVkIElQdjQgQWRkcmVzc2VzIiwgZHJhZnQtaWV0Zi1kaGMt
ZHluYW1pYy1zaGFyZWQtdjRhbGxvY2F0aW9uLTAyLCBkb2N1bWVudCBhcyBhIFN0YW5kYXJkcyBU
cmFjayAoUHJvcG9zZWQgU3RhbmRhcmQpIFJGQy4gVGhlIGF1dGhvcnMgYmVsaWV2ZSB0aGF0IHRo
aXMgdmVyc2lvbiBpcyByZWFkeS4NCg0KDQoNClRoZSBkcmFmdCBpcyBhdmFpbGFibGUgaGVyZToN
Cg0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kaGMtZHluYW1pYy1zaGFy
ZWQtdjRhbGxvY2F0aW9uLTAyDQoNCg0KDQpQbGVhc2Ugc2VuZCB5b3VyIGNvbW1lbnRzIGJ5IE9j
dG9iZXIgMjd0aCwgMjAxNC4gSWYgeW91IGRvIG5vdCBmZWVsIHRoaXMgZG9jdW1lbnQgc2hvdWxk
IGFkdmFuY2UsIHBsZWFzZSBzdGF0ZSB5b3VyIHJlYXNvbnMgd2h5Lg0KDQoNCg0KVGhlcmUgYXJl
IG5vIElQUiBjbGFpbXMgcmVwb3J0ZWQgYXQgdGhpcyB0aW1lLg0KDQoNCg0KQmVybmllIFZvbHog
aXMgdGhlIGN1cnJlbnRseSBhc3NpZ25lZCBzaGVwaGVyZCBmb3IgdGhpcyBkb2N1bWVudC4NCg0K
DQoNCi0gVG9tZWsgJiBCZXJuaWUNCg0K

--_000_5D36713D8A4E7348A7E10DF7437A4B923AF6812Fnkgeml512mbxchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTrlrovkvZM7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1
IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBh
bm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
VGFob21hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6IlxA5a6L5L2TIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30N
Ci8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYu
TXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpi
bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5
cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7
DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb1BsYWluVGV4dCwgbGkuTXNvUGxh
aW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28t
c3R5bGUtbGluazoi57qv5paH5pysIENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRv
bTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJz
YW5zLXNlcmlmIjt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1s
aW5rOiJIVE1MIOmihOiuvuagvOW8jyBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OuWui+S9kzt9DQpw
Lk1zb0FjZXRhdGUsIGxpLk1zb0FjZXRhdGUsIGRpdi5Nc29BY2V0YXRlDQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoi5om55rOo5qGG5paH5pysIENoYXIiOw0KCW1h
cmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTo5LjBwdDsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnAuTXNvTGlzdFBhcmFncmFwaCwg
bGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGNtOw0KCW1hcmdpbi1yaWdodDowY207DQoJbWFyZ2lu
LWJvdHRvbTowY207DQoJbWFyZ2luLWxlZnQ6MzYuMHB0Ow0KCW1hcmdpbi1ib3R0b206LjAwMDFw
dDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp
ZiI7fQ0Kc3Bhbi5DaGFyDQoJe21zby1zdHlsZS1uYW1lOiLnuq/mlofmnKwgQ2hhciI7DQoJbXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOue6r+aWh+acrDsNCglmb250LWZh
bWlseTrlrovkvZM7fQ0KcC5QbGFpblRleHQsIGxpLlBsYWluVGV4dCwgZGl2LlBsYWluVGV4dA0K
CXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCI7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRl
eHQgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1z
aXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNwYW4u
UGxhaW5UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCBDaGFyIjsNCgltc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQiOw0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjINCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
IjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uRW1haWxTdHlsZTIzDQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29s
b3I6IzFGNDk3RDt9DQpzcGFuLkNoYXIwDQoJe21zby1zdHlsZS1uYW1lOiLmibnms6jmoYbmlofm
nKwgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOuaJueaz
qOahhuaWh+acrDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNwYW4u
RW1haWxTdHlsZTI2DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkhUTUxD
aGFyDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIOmihOiuvuagvOW8jyBDaGFyIjsNCgltc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwg6aKE6K6+5qC85byPIjsNCglm
b250LWZhbWlseTrlrovkvZM7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhw
b3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6
ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9
DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5p
dGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjExMDE5OTMzOTc7DQoJbXNvLWxpc3Qt
dHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjEzODMzNzc4MjIgLTEzMjQ3MTcy
OTggNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkg
Njc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1zdGFydC1h
dDoyMzsNCgltc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
LTsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNh
bnMtc2VyaWYiOw0KCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJbXNvLWJpZGkt
Zm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJe21zby1s
ZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZl
bC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0
LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6
bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2Rpbmdz
O30NCkBsaXN0IGwwOmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJ
bXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZl
bC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFt
aWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6
YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJ
Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVs
LW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7
DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0
IGwwOmxldmVsOA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVs
LXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ291cmll
ciBOZXciO30NCkBsaXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxs
ZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZv
bnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQp1bA0KCXtt
YXJnaW4tYm90dG9tOjBjbTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwh
W2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9
ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlv
dXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJaSC1DTiIgbGluaz0i
Ymx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2NvbG9yOiMxRjQ5N0QiPkhpLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzFGNDk3
RCI+SSBoYXZlIHJldmlld2VkIHRoaXMgZG9jdW1lbnQgYW5kIHN1cHBvcnQgdG8gbW92ZSBpdCBm
b3J3YXJkLiBUaGlzIGRyYWZ0IHNvbHZlcyBhIHJlYWwgaXNzdWUgb24gaG93IHRvIGFsbG9jYXRl
IHBvcnQtc2V0IGJhc2VkIG9uIHRoZSBESENQIDRvNi4gVGhlIGRvY3VtZW50IGhhdmUgbm8gbWFq
b3IgaXNzdWUgYWx0aG91Z2gNCiB0aGVyZSBhcmUgYSBmZXcgbml0cywgd2hpY2ggY2FuIGJlIHNv
bHZlZCBieSBhIHF1aWNrIHVwZGF0ZSB2ZXJzaW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Y29sb3I6IzFGNDk3RCI+QWxzbywgdGhlIHNlY3VyaXR5IGNvbnNpZGVyYXRpb24gaGFzIGEgcmVm
ZXJlbmNlIHRvIGFuIGluZGl2aWR1YWwgZHJhZnQuIEl0IG1heSBub3QgYmUgcHJvcGVyLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzFGNDk3RCI+VW51c2VkIFJlZmVyZW5jZTogJ0kt
RC5pZXRmLXNvZnR3aXJlLWx3NG92ZXI2JzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtj
b2xvcjojMUY0OTdEIj5VbnVzZWQgUmVmZXJlbmNlOiAnUkZDMzMxNSc8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC41cHQ7Y29sb3I6IzFGNDk3RCI+VW51c2VkIFJlZmVyZW5jZTogJ1JGQzM5Mjcn
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5N0QiPkRvd25yZWY6IE5v
cm1hdGl2ZSByZWZlcmVuY2UgdG8gYW4gSW5mb3JtYXRpb25hbCBSRkM6IFJGQyA2MjY5PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjojMUY0OTdEIj5CZXN0IHJlZ2FyZHMsPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtjb2xvcjojMUY0OTdEIj5TaGVuZzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRp
bmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+IGRoY3dnIFttYWlsdG86ZGhjd2ctYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJl
aGFsZiBPZiA8L2I+QmVybmllIFZvbHogKHZvbHopPGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXks
IE9jdG9iZXIgMjEsIDIwMTQgMTE6MTggUE08YnI+DQo8Yj5Ubzo8L2I+IGRoY3dnQGlldGYub3Jn
PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhj
LWR5bmFtaWMtc2hhcmVkLXY0YWxsb2NhdGlvbi0wMiAtIFJlc3BvbmQgYnkgT2N0IDI3LCAyMDE0
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PlJlbWluZGVyIOKAkyB0aGlzIFdHTEMgaXMgaW4gcHJvZ3Jlc3MgYW5kIHlvdSBoYXZlIHVudGls
IE9jdCAyNzxzdXA+dGg8L3N1cD4gdG8gcmVzcG9uZC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5
N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdy
YXBoIiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMiI+
PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj4tPHNwYW4gc3R5bGU9ImZvbnQ6Ny4w
cHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkJlcm5pZTxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMu
MHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IGRoY3dnIFs8YSBocmVmPSJtYWlsdG86ZGhjd2ct
Ym91bmNlc0BpZXRmLm9yZyI+bWFpbHRvOmRoY3dnLWJvdW5jZXNAaWV0Zi5vcmc8L2E+XQ0KPGI+
T24gQmVoYWxmIE9mIDwvYj5CZXJuaWUgVm9seiAodm9seik8YnI+DQo8Yj5TZW50OjwvYj4gU3Vu
ZGF5LCBPY3RvYmVyIDEyLCAyMDE0IDEwOjE0IFBNPGJyPg0KPGI+VG86PC9iPiA8YSBocmVmPSJt
YWlsdG86ZGhjd2dAaWV0Zi5vcmciPmRoY3dnQGlldGYub3JnPC9hPjxicj4NCjxiPlN1YmplY3Q6
PC9iPiBbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhjLWR5bmFtaWMtc2hhcmVkLXY0YWxs
b2NhdGlvbi0wMiAtIFJlc3BvbmQgYnkgT2N0IDI3LCAyMDE0PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
c3BhbiBsYW5nPSJFTi1VUyI+SGkgYWxsLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+VGhpcyBt
ZXNzYWdlIHN0YXJ0cyB0aGUgREhDIHdvcmtpbmcgZ3JvdXAgbGFzdCBjYWxsIHRvIGFkdmFuY2Ug
JnF1b3Q7RHluYW1pYyBBbGxvY2F0aW9uIG9mIFNoYXJlZCBJUHY0IEFkZHJlc3NlcyZxdW90Oywg
ZHJhZnQtaWV0Zi1kaGMtZHluYW1pYy1zaGFyZWQtdjRhbGxvY2F0aW9uLTAyLCBkb2N1bWVudCBh
cyBhIFN0YW5kYXJkcyBUcmFjayAoUHJvcG9zZWQgU3RhbmRhcmQpIFJGQy4gVGhlDQogYXV0aG9y
cyBiZWxpZXZlIHRoYXQgdGhpcyB2ZXJzaW9uIGlzIHJlYWR5LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJF
Ti1VUyI+VGhlIGRyYWZ0IGlzIGF2YWlsYWJsZSBoZXJlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48YSBocmVmPSJodHRw
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWRoYy1keW5hbWljLXNoYXJlZC12NGFs
bG9jYXRpb24tMDIiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtZGhjLWR5
bmFtaWMtc2hhcmVkLXY0YWxsb2NhdGlvbi0wMjwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
PlBsZWFzZSBzZW5kIHlvdXIgY29tbWVudHMgYnkgT2N0b2JlciAyN3RoLCAyMDE0LiBJZiB5b3Ug
ZG8gbm90IGZlZWwgdGhpcyBkb2N1bWVudCBzaG91bGQgYWR2YW5jZSwgcGxlYXNlIHN0YXRlIHlv
dXIgcmVhc29ucyB3aHkuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5UaGVyZSBhcmUgbm8gSVBS
IGNsYWltcyByZXBvcnRlZCBhdCB0aGlzIHRpbWUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5C
ZXJuaWUgVm9seiBpcyB0aGUgY3VycmVudGx5IGFzc2lnbmVkIHNoZXBoZXJkIGZvciB0aGlzIGRv
Y3VtZW50LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxz
cGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+LSBUb21layAmYW1wOyBCZXJuaWU8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4N
CjwvaHRtbD4NCg==

--_000_5D36713D8A4E7348A7E10DF7437A4B923AF6812Fnkgeml512mbxchi_--


From nobody Fri Oct 24 01:31:59 2014
Return-Path: <ian.farrer@telekom.de>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF6E1A1A24 for <dhcwg@ietfa.amsl.com>; Fri, 24 Oct 2014 01:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.859
X-Spam-Level: 
X-Spam-Status: No, score=-3.859 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 wn_cQqpbrns4 for <dhcwg@ietfa.amsl.com>; Fri, 24 Oct 2014 01:31:55 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FD351A19E5 for <dhcwg@ietf.org>; Fri, 24 Oct 2014 01:31:53 -0700 (PDT)
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by tcmail21.telekom.de with ESMTP; 24 Oct 2014 10:31:22 +0200
X-IronPort-AV: E=Sophos;i="5.04,779,1406584800";  d="scan'208,217";a="552622457"
Received: from he113675.emea1.cds.t-internal.com ([10.134.99.28]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES128-SHA; 24 Oct 2014 10:31:22 +0200
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113675.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 24 Oct 2014 10:31:21 +0200
From: <ian.farrer@telekom.de>
To: <volz@cisco.com>, <dhcwg@ietf.org>
Date: Fri, 24 Oct 2014 10:31:19 +0200
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
Thread-Index: Ac/vZOQl7DRnKimeR/aDyAwrOlxRoA==
Message-ID: <D06FDAB2.DFAAE%ian.farrer@telekom.de>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.4.140807
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_D06FDAB2DFAAEianfarrertelekomde_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/WvDFcpdOowp0p_sWzBn5fel6T4Y
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 24 Oct 2014 08:31:58 -0000

--_000_D06FDAB2DFAAEianfarrertelekomde_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

HI Bernie,

I support this moving forward, but I agree with Ted, it would  benefit from=
 first having a review from someone in the WG.

Cheers,
Ian



From: "Bernie Volz (volz)" <volz@cisco.com<mailto:volz@cisco.com>>
Date: Tuesday, 21 October 2014 17:18
To: "dhcwg@ietf.org<mailto:dhcwg@ietf.org>" <dhcwg@ietf.org<mailto:dhcwg@ie=
tf.org>>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02=
 - Respond by Oct 27, 2014

Reminder =96 this WGLC is in progress and you have until Oct 27th to respon=
d.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, October 12, 2014 10:14 PM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - R=
espond by Oct 27, 2014


Hi all,



This message starts the DHC working group last call to advance "Dynamic All=
ocation of Shared IPv4 Addresses", draft-ietf-dhc-dynamic-shared-v4allocati=
on-02, document as a Standards Track (Proposed Standard) RFC. The authors b=
elieve that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-02



Please send your comments by October 27th, 2014. If you do not feel this do=
cument should advance, please state your reasons why.



There are no IPR claims reported at this time.



Bernie Volz is the currently assigned shepherd for this document.



- Tomek & Bernie


--_000_D06FDAB2DFAAEianfarrertelekomde_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
 -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14p=
x; font-family: Calibri, sans-serif;"><div><div>HI Bernie,</div><div><br></=
div><div>I support this moving forward, but I agree with Ted, it would &nbs=
p;benefit from first having a review from someone in the WG.</div><div><br>=
</div><div>Cheers,</div><div>Ian</div><div><div><font class=3D"Apple-style-=
span" face=3D"Arial,sans-serif" style=3D"font-size: 12px; "><br></font></di=
v><div><div style=3D"font-family: Calibri; "><font class=3D"Apple-style-spa=
n" face=3D"Arial,sans-serif" style=3D"font-size: 12px; "><br></font></div><=
span class=3D"Apple-style-span" style=3D"font-family: Arial, sans-serif;"><=
div style=3D"font-size: small;"><br></div></span></div></div></div><span id=
=3D"OLK_SRC_BODY_SECTION"><div style=3D"font-family:Calibri; font-size:11pt=
; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: me=
dium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORD=
ER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><sp=
an style=3D"font-weight:bold">From: </span> &quot;Bernie Volz   (volz)&quot=
; &lt;<a href=3D"mailto:volz@cisco.com">volz@cisco.com</a>&gt;<br><span sty=
le=3D"font-weight:bold">Date: </span> Tuesday, 21 October 2014 17:18<br><sp=
an style=3D"font-weight:bold">To: </span> &quot;<a href=3D"mailto:dhcwg@iet=
f.org">dhcwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:dhcwg@ietf.org">dhcwg=
@ietf.org</a>&gt;<br><span style=3D"font-weight:bold">Subject: </span> Re: =
[dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by=
 Oct 27, 2014<br></div><div><br></div><div xmlns:v=3D"urn:schemas-microsoft=
-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"ur=
n:schemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.co=
m/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><meta name=
=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1101993397;
	mso-list-type:hybrid;
	mso-list-template-ids:1383377822 -1324717298 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:23;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal"><span style=
=3D"color:#1F497D">Reminder =96 this WGLC is in progress and you have until=
 Oct 27<sup>th</sup> to respond.<o:p></o:p></span></p><p class=3D"MsoNormal=
"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p><p class=3D"Mso=
ListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if=
 !supportLists]--><span style=3D"color:#1F497D"><span style=3D"mso-list:Ign=
ore">-<span style=3D"font-style: normal; font-variant: normal; font-weight:=
 normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman=
';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><!--[endif]--><span style=3D"color:#1F497D">Bernie<o:p=
></o:p></span></p><p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p=
>&nbsp;</o:p></span></p><div><div style=3D"border:none;border-top:solid #B5=
C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=
=3D"font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><spa=
n style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;"> dhcwg [<a hr=
ef=3D"mailto:dhcwg-bounces@ietf.org">mailto:dhcwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Bernie Volz (volz)<br><b>Sent:</b> Sunday, October 12, =
2014 10:14 PM<br><b>To:</b> <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.or=
g</a><br><b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4a=
llocation-02 - Respond by Oct 27, 2014<o:p></o:p></span></p></div></div><p =
class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p class=3D"MsoPlainText">Hi all,<=
o:p></o:p></p><p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p><p class=3D"Ms=
oPlainText">This message starts the DHC working group last call to advance =
&quot;Dynamic Allocation of Shared IPv4 Addresses&quot;, draft-ietf-dhc-dyn=
amic-shared-v4allocation-02, document as a Standards Track (Proposed Standa=
rd) RFC. The authors believe that
 this version is ready.<o:p></o:p></p><p class=3D"MsoPlainText"><o:p>&nbsp;=
</o:p></p><p class=3D"MsoPlainText">The draft is available here:<o:p></o:p>=
</p><p class=3D"MsoPlainText"><a href=3D"http://tools.ietf.org/html/draft-i=
etf-dhc-dynamic-shared-v4allocation-02">http://tools.ietf.org/html/draft-ie=
tf-dhc-dynamic-shared-v4allocation-02</a><o:p></o:p></p><p class=3D"MsoPlai=
nText"><o:p>&nbsp;</o:p></p><p class=3D"MsoPlainText">Please send your comm=
ents by October 27th, 2014. If you do not feel this document should advance=
, please state your reasons why.<o:p></o:p></p><p class=3D"MsoPlainText"><o=
:p>&nbsp;</o:p></p><p class=3D"MsoPlainText">There are no IPR claims report=
ed at this time.<o:p></o:p></p><p class=3D"MsoPlainText"><o:p>&nbsp;</o:p><=
/p><p class=3D"MsoPlainText">Bernie Volz is the currently assigned shepherd=
 for this document.<o:p></o:p></p><p class=3D"MsoPlainText"><o:p>&nbsp;</o:=
p></p><p class=3D"MsoPlainText">- Tomek &amp; Bernie<o:p></o:p></p><p class=
=3D"MsoNormal"><o:p>&nbsp;</o:p></p></div></div></div></span></body></html>

--_000_D06FDAB2DFAAEianfarrertelekomde_--


From nobody Sun Oct 26 15:11:29 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 852091A1A2F for <dhcwg@ietfa.amsl.com>; Sun, 26 Oct 2014 15:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 gwex5p_EEXWW for <dhcwg@ietfa.amsl.com>; Sun, 26 Oct 2014 15:11:27 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF9C21A1A17 for <dhcwg@ietf.org>; Sun, 26 Oct 2014 15:11:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4561; q=dns/txt; s=iport; t=1414361486; x=1415571086; h=from:to:subject:date:message-id:mime-version; bh=mYpsAzRn+DbzMQ0VIpaUYTzrUyb3ZmSUsgi8/WY8cBA=; b=AKPkQAgcwspfFIncmtaFvweVm1YtdaxnmonkfblMrOMgf6DUUYg5AjL3 6GZEIAuWm6ZMAgl7p6BIw+W8DsrAt+Ok+4mcbNnTHARpC+niADTT4w4qr mXlCL2mjUennuiAVoKTGmkwbr7w6gFF+c9fMehWfbPFa2MBrY8oGMBejg I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AscFANJwTVStJV2b/2dsb2JhbABcgkhGVFkDywaBcIdNAoEKFgFyC4QEAQQtXgEqViYBBBuIOQ2kG6M5AQEBAQYBAQEBAR2NOoMdg2WBHgWSB4RIiEM8gw2HZ4VNhACDeII0gQMBAQE
X-IronPort-AV: E=Sophos; i="5.04,791,1406592000"; d="scan'208,217"; a="90486290"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-6.cisco.com with ESMTP; 26 Oct 2014 22:11:26 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9QMBQYZ005223 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sun, 26 Oct 2014 22:11:26 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Sun, 26 Oct 2014 17:11:26 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
Thread-Index: Ac/xaWYb7j/iiP3ISmCf+ekbUUcpTQ==
Date: Sun, 26 Oct 2014 22:11:25 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6F6882xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/JRkpIXkb0AQmqDidTN4nAc6zlhg
Subject: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 26 Oct 2014 22:11:28 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6F6882xmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,



This message starts the (short) DHC working group last call to advance "Sec=
ure DHCPv6", draft-ietf-dhc-sedhcpv6-04, document as a Standards Track (Pro=
posed Standard) RFC. The authors believe that this version is ready. We had=
 a WGLC earlier (May 2014 for the -02 version) and there were some comments=
, so this is primarily to assure that those comments were addressed.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-04



Please send your comments by November 3rd, 2014. If you do not feel this do=
cument should advance, please state your reasons why.



There are no IPR claims reported at this time.



Tomek is the assigned shepherd for this document.



- Tomek & Bernie


--_000_489D13FBFA9B3E41812EA89F188F018E1B6F6882xmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hi all,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This message starts the (short) DHC working group=
 last call to advance &quot;Secure DHCPv6&quot;, draft-ietf-dhc-sedhcpv6-04=
, document as a Standards Track (Proposed Standard) RFC. The authors believ=
e that this version is ready. We had a WGLC
 earlier (May 2014 for the -02 version) and there were some comments, so th=
is is primarily to assure that those comments were addressed.<o:p></o:p></p=
>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The draft is available here:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"http://tools.ietf.org/html/draft-ietf-=
dhc-sedhcpv6-04">http://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-04</a><=
o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please send your comments by November 3rd, 2014. =
If you do not feel this document should advance, please state your reasons =
why.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There are no IPR claims reported at this time.<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Tomek is the assigned shepherd for this document.=
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6F6882xmbrcdx04ciscoc_--


From nobody Sun Oct 26 20:07:46 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D53891A6F91 for <dhcwg@ietfa.amsl.com>; Sun, 26 Oct 2014 20:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 YyqjpFc1v4jo for <dhcwg@ietfa.amsl.com>; Sun, 26 Oct 2014 20:07:38 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39E811A1A8A for <dhcwg@ietf.org>; Sun, 26 Oct 2014 20:07:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20151; q=dns/txt; s=iport; t=1414379258; x=1415588858; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=nEZKShuTq2E5x+KtyXIWAzsG3T5Uk6rVLgVFdxhmQFE=; b=g4jgwjB6GdpZS4+TBqeThp7wsxpyf2DmBis4ljA9jLQw1obMwHEwYLCe piaEiL5JA8CO6i+vL2+6PhRrcmi82JR5MTlDPPnOt5RoYeVVbeokZmT28 f4gQ7kob0hodmdLZ/N/bGLTk87fODfqme4M/o8mLi+IxhquKIWEjW8dQk w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgFACi2TVStJA2B/2dsb2JhbABSCoJIRlRYBMsMgXKHSwKBDRYBcguEAgEBAQQtXAIBCBEEAQELHQcyFAkIAQEEEwiIOQ3IOQEBAQEBAQEBAQEBAQEBAQEBAQEBAReNOoJyBCc3AQaDJ4EeBYRijSWESIJDgX2EAzyDDYdnhU2EAII0gURsgQZCgQMBAQE
X-IronPort-AV: E=Sophos;i="5.04,792,1406592000";  d="scan'208,217";a="366633483"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-8.cisco.com with ESMTP; 27 Oct 2014 03:07:37 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s9R37af6021099 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Mon, 27 Oct 2014 03:07:36 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Sun, 26 Oct 2014 22:07:36 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
Thread-Index: Ac/minMIxUbYwkSiQNCrNLgZzh2MnQLAB7Kg
Date: Mon, 27 Oct 2014 03:07:36 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6F6B1D@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6F6B1Dxmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/yAC5tu38etobun0YkJXhqc7zcN4
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 27 Oct 2014 03:07:43 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6F6B1Dxmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

While I am ok advancing this work if someone feels they need it (I would pr=
efer we not deploy this technology and just move to IPv6 - especially as th=
is requires making changes to hosts), I do have review comments that I beli=
eve need to be addressed:

In 1. Introduction, why reference ietf-dhc-dhcpv4-over-ip6v4? That work was=
 an alternative to what became RFC 7341 and the WG decided that dhpv4-over-=
dhcpv6 was the way forward. Perhaps just drop "such as DHCPv4 over IPv6 [re=
ference]"?

In the next paragraph, RFC 6346 is mentioned - this is an Experimental docu=
ment. It is only an informational reference, so at least that may be OK. Bu=
t it seems a bit odd that the text here is "This extension is only suitable=
 for specific architectures based on Address plus Port model" when that is =
experimental? Even draft-ietf-softwire-map-t (-06) is going for Experimenta=
l, not standards track. (Though draft-ietf-softwire-map is going for Standa=
rds Track.)

In 4. Functional Overview:

-          In the 2nd paragraph, this option is only used in the PRL in the=
 DHCPDISCOVER? It is send by the client in DHCPREQUEST (DHCPRELEASE) messag=
es. Perhaps this should be indicated?

-          I think in the last paragraph, first sentence, which should be t=
hat? ... to identify clients that support?

In 5. Client-Server Interactions:

-          In #1, there is an opened parenthesis that is never closed.

-          In #3, what if the client receives offers without the OPTION_V4_=
PORTPARAMS? Should it prefer that (I would think so)? (You do mention this =
later in section 7.)

-          Ted already pointed out the issue in the last paragraph with RFC=
 2131 3.2 and that a DHCPREQUEST is sent, not a DHCPDISCOVER. I think this =
will also need some careful attention as this could result in problems if t=
he client ends up on a different network and a server decides to allocate t=
he requested address but doesn't support OPTION_V4_PORTPARAMs? First, I thi=
nk perhaps using input from the IPv6 layer (i.e., as this is using RFC7341)=
 can help since if the V6 stack determines the location has changed, then o=
bviously going to DHCPDISCOVER is the better choice? (Not sure if perhaps w=
e should recommend that existing "traditional" DHCP servers that receive a =
DHCPREQUEST (init-reboot) with an OPTION_V4_PORTPARAMS should either drop t=
he packet or send a DHCPNAK it?

In 6. Server Behavior, un the 2nd paragraph "server MUST run an address and=
 port-set" is rather odd wording? Do you implemented instead of run?

Section 7. Client Behavior is rather similar to section 5. Kind of a bit od=
d order (perhaps Client-Server Interactions, Client Behavior, Server Behavi=
or would be a bit better, but not a big deal).

In 7.1, is there any RFC to reference here that describes the limitations f=
or a node with a limited port set? For the first bulleted item, do we know =
what "port-aware" protocols are? I think this is not a common term, so it w=
ill have to be defined? Also for the sentence that introduces the list "Cli=
ent MUST apply ... to ... the shared address"? I think what you mean here i=
s if it provides information to another node to make connections back (into=
) the client, it must use its port range?

In 9.1, isn't there also a problem if a malicious client doesn't follow the=
 rules in section 7.1 if there isn't proper filtering in place (i.e., egres=
s filtering).


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, October 12, 2014 10:14 PM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - R=
espond by Oct 27, 2014


Hi all,



This message starts the DHC working group last call to advance "Dynamic All=
ocation of Shared IPv4 Addresses", draft-ietf-dhc-dynamic-shared-v4allocati=
on-02, document as a Standards Track (Proposed Standard) RFC. The authors b=
elieve that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-02



Please send your comments by October 27th, 2014. If you do not feel this do=
cument should advance, please state your reasons why.



There are no IPR claims reported at this time.



Bernie Volz is the currently assigned shepherd for this document.



- Tomek & Bernie


--_000_489D13FBFA9B3E41812EA89F188F018E1B6F6B1Dxmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:366874819;
	mso-list-type:hybrid;
	mso-list-template-ids:904667800 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1171064775;
	mso-list-type:hybrid;
	mso-list-template-ids:988594168 -1603473238 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">While I am ok advancin=
g this work if someone feels they need it (I would prefer we not deploy thi=
s technology and just move to IPv6 &#8211; especially as this requires maki=
ng changes to hosts), I do have review comments
 that I believe need to be addressed:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In 1. Introduction, wh=
y reference ietf-dhc-dhcpv4-over-ip6v4? That work was an alternative to wha=
t became RFC 7341 and the WG decided that dhpv4-over-dhcpv6 was the way for=
ward. Perhaps just drop &#8220;such as DHCPv4
 over IPv6 [reference]&#8221;?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In the next paragraph,=
 RFC 6346 is mentioned &#8211; this is an Experimental document. It is only=
 an informational reference, so at least that may be OK. But it seems a bit=
 odd that the text here is &#8220;This extension
 is only suitable for specific architectures based on Address plus Port mod=
el&#8221; when that is experimental? Even draft-ietf-softwire-map-t (-06) i=
s going for Experimental, not standards track. (Though draft-ietf-softwire-=
map is going for Standards Track.)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In 4. Functional Overv=
iew:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">In the 2<sup>n=
d</sup> paragraph, this option is only used in the PRL in the DHCPDISCOVER?=
 It is send by the client in DHCPREQUEST (DHCPRELEASE) messages. Perhaps th=
is should be indicated?<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">I think in the=
 last paragraph, first sentence, which should be that? &#8230; to identify =
clients that support?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In 5. Client-Server In=
teractions:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">In #1, there i=
s an opened parenthesis that is never closed.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">In #3, what if=
 the client receives offers without the OPTION_V4_PORTPARAMS? Should it pre=
fer that (I would think so)? (You do mention this later in section 7.)<o:p>=
</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Ted already po=
inted out the issue in the last paragraph with RFC 2131 3.2 and that a DHCP=
REQUEST is sent, not a DHCPDISCOVER. I think this will also need some caref=
ul attention as this could result
 in problems if the client ends up on a different network and a server deci=
des to allocate the requested address but doesn&#8217;t support OPTION_V4_P=
ORTPARAMs? First, I think perhaps using input from the IPv6 layer (i.e., as=
 this is using RFC7341) can help since
 if the V6 stack determines the location has changed, then obviously going =
to DHCPDISCOVER is the better choice? (Not sure if perhaps we should recomm=
end that existing &#8220;traditional&#8221; DHCP servers that receive a DHC=
PREQUEST (init-reboot) with an OPTION_V4_PORTPARAMS
 should either drop the packet or send a DHCPNAK it?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In 6. Server Behavior,=
 un the 2<sup>nd</sup> paragraph &#8220;server MUST run an address and port=
-set&#8221; is rather odd wording? Do you implemented instead of run?<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Section 7. Client Beha=
vior is rather similar to section 5. Kind of a bit odd order (perhaps Clien=
t-Server Interactions, Client Behavior, Server Behavior would be a bit bett=
er, but not a big deal).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In 7.1, is there any R=
FC to reference here that describes the limitations for a node with a limit=
ed port set? For the first bulleted item, do we know what &#8220;port-aware=
&#8221; protocols are? I think this is not a common
 term, so it will have to be defined? Also for the sentence that introduces=
 the list &#8220;Client MUST apply &#8230; to &#8230; the shared address&#8=
221;? I think what you mean here is if it provides information to another n=
ode to make connections back (into) the client, it must
 use its port range?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In 9.1, isn&#8217;t th=
ere also a problem if a malicious client doesn&#8217;t follow the rules in =
section 7.1 if there isn&#8217;t proper filtering in place (i.e., egress fi=
ltering).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Sunday, October 12, 2014 10:14 PM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation=
-02 - Respond by Oct 27, 2014<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Hi all,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This message starts the DHC working group last ca=
ll to advance &quot;Dynamic Allocation of Shared IPv4 Addresses&quot;, draf=
t-ietf-dhc-dynamic-shared-v4allocation-02, document as a Standards Track (P=
roposed Standard) RFC. The authors believe that
 this version is ready.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The draft is available here:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"http://tools.ietf.org/html/draft-ietf-=
dhc-dynamic-shared-v4allocation-02">http://tools.ietf.org/html/draft-ietf-d=
hc-dynamic-shared-v4allocation-02</a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please send your comments by October 27th, 2014. =
If you do not feel this document should advance, please state your reasons =
why.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There are no IPR claims reported at this time.<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bernie Volz is the currently assigned shepherd fo=
r this document.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6F6B1Dxmbrcdx04ciscoc_--


From nobody Sun Oct 26 21:10:55 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01A3D1A6FBB for <dhcwg@ietfa.amsl.com>; Sun, 26 Oct 2014 21:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 a5tYLZCmMjZ8 for <dhcwg@ietfa.amsl.com>; Sun, 26 Oct 2014 21:10:51 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7045F1A1A93 for <dhcwg@ietf.org>; Sun, 26 Oct 2014 21:10:51 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 352D4DA0085 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 04:13:49 +0000 (UTC)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id C0C9553E07D; Sun, 26 Oct 2014 21:10:20 -0700 (PDT)
Received: from [10.0.20.107] (71.233.43.215) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sun, 26 Oct 2014 21:10:20 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6F6B1D@xmb-rcd-x04.cisco.com>
Date: Mon, 27 Oct 2014 00:10:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <A784CAC3-911E-419F-8ED3-0EBC09DD68C4@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6F6B1D@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/O_61_H1qq5S000gqSAqH8AoDPyY
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 27 Oct 2014 04:10:53 -0000

On Oct 26, 2014, at 11:07 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> While I am ok advancing this work if someone feels they need it (I =
would prefer we not deploy this technology and just move to IPv6 =96 =
especially as this requires making changes to hosts),

It's needed for a softwires document that's going through IESG review =
this week.

> In the next paragraph, RFC 6346 is mentioned =96 this is an =
Experimental document. It is only an informational reference, so at =
least that may be OK. But it seems a bit odd that the text here is =93This=
 extension is only suitable for specific architectures based on Address =
plus Port model=94 when that is experimental? Even =
draft-ietf-softwire-map-t (-06) is going for Experimental, not standards =
track. (Though draft-ietf-softwire-map is going for Standards Track.)

The IESG is in the process of promoting that to standards track.   It's =
not experimental anymore.

Thanks for doing a more thorough technical review than I've yet had time =
for.


From nobody Mon Oct 27 07:45:15 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 602F51A87EE for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 olyk9mAxeEQ7 for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:44:31 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F8D21A87E2 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 07:44:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4680; q=dns/txt; s=iport; t=1414421072; x=1415630672; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=poGNmom7Tr0Fca2fwi9id3/uH6ecJNpng8bF7RBBUxQ=; b=frJzn+sSxxspFONyJncnh2/VDpQUAsHdk9iOrMBtS6SAPm180znSUoDd HLZRx6KHcQrO4lp/aTZ8tIjlRon8OUv9HuvP+JlAmAJhJDE4+RPFVPlFQ 9BE668m0nK5uLlwXC2MVhyiNIhlS2SqWhcuh5gqyjvY4O7MjHLewQSV4e Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArMGAElZTlStJA2M/2dsb2JhbABcgw5UUwUEgwLKOodNAhuBARYBcguEAgEBAQQjEUMOBgEZBAEBAwIGHQMCBDAUAQgJAQQTCAGIOAgFpwePQpRLAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4EsjA6DCRQWKIJxNoEeBZIHhEiIQzyDDYoVhx+CNIFEbAGBR4EDAQEB
X-IronPort-AV: E=Sophos;i="5.04,796,1406592000"; d="scan'208";a="366852403"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-4.cisco.com with ESMTP; 27 Oct 2014 14:44:31 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s9REiUkd019370 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Mon, 27 Oct 2014 14:44:30 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Mon, 27 Oct 2014 09:44:30 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: RFC 3315 Bis Update (& New Version Notification for draft-dhcwg-dhc-rfc3315bis-03.txt)
Thread-Index: Ac/x9IOEHPk6gLsLTfi6awL5bD/Jow==
Date: Mon, 27 Oct 2014 14:44:30 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6F7B72@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/7tULwOr_2vlNuT1BecnxO5Jen9I
Subject: [dhcwg] RFC 3315 Bis Update (& New Version Notification for draft-dhcwg-dhc-rfc3315bis-03.txt)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 27 Oct 2014 14:44:33 -0000

Rm9yIHRob3NlIGludGVyZXN0ZWQgaW4gdGhpcyB3b3JrLCBoZXJlJ3MgYSBicmllZiB1cGRhdGU6
DQoNCjEuIFRoZXJlIHdpbGwgYmUgYSBESENQdjZiaXMgdGVhbSBtZWV0aW5nIGF0IElFVEYtOTEu
IEl0IHdpbGwgYmU6DQoNClR1ZXNkYXksIDExLzExIGZyb20gMDkwMC0xMTMwIChIU1QsIFVUQyAt
IDEwaCkgaW4gU291dGggUGFjaWZpYyAyLg0KDQpUaGlzIGlzIGEgd29ya2luZyBzZXNzaW9uIHRv
IHJldmlldyBvcGVuIGlzc3VlcywgYXNzaWduIHdvcmssIGFuZCBkaXNjdXNzIG91dHN0YW5kaW5n
IHdvcmsgaXRlbXMgdG8gbW92ZSB0aGVtIGZvcndhcmQuIFRoaXMgbWVldGluZyBpcyBvcGVuIHRv
IGFueW9uZSwgYnV0IGlzIHByZWxpbWluYXJ5IGZvciB0aGUgREhDUHY2YmlzIHRlYW0gdG8gbWVl
dCBmYWNlLXRvLWZhY2UuIChBbiBhZ2VuZGEgc2hvdWxkIGJlIGF2YWlsYWJsZSBzaG9ydGx5LikN
Cg0KV2Ugd2lsbCB1cGRhdGUgdGhlIERIQyBXRyBvbiB0aGUgc3RhdHVzIGF0IHRoZSBESEMgV0cg
c2Vzc2lvbiAobGF0ZSBUaHVyc2RheSBhZnRlcm5vb24pLg0KDQoyLiBXZSBoYXZlIHB1Ymxpc2hl
ZCBhbiB1cGRhdGVkIFJGQy0zMzE1YmlzIGRvY3VtZW50IChzZWUgYW5ub3VuY2VtZW50IGJlbG93
KS4gVGhpcyBpbmNsdWRlIHNvbWUgYWRkaXRpb25hbCBjaGFuZ2VzIGJ1dCBpcyBub3QgeWV0ICJj
b21wbGV0ZSIgKHNlZSBodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy9ncm91cC9kaGNwdjZiaXMv
cmVwb3J0LzMgZm9yIHRoZSBvcGVuIHRpY2tldHMpLg0KDQpBcHBlbmRpeCBBIGluIHRoZSBkb2N1
bWVudCB0cmFja3MgbW9zdCBvZiB0aGUgY2hhbmdlcywgYW5kIHRoZSBuZXcgZW50cmllcyBzaW5j
ZSB0aGUgMDIgdmVyc2lvbiBhcmU6DQoNCiAgIDMwLiAgQ2xhcmlmaWVkIHRoYXQgZW5jYXBzdWxh
dGVkIG9wdGlvbnMgbXVzdCBiZSByZXF1ZXN0ZWQgdXNpbmcgdG9wCSAJCQ0KICAgICAgICBsZXZl
bCBPUk8gKHRpY2tldCAjMzgpLgkgCQkNCiAJCQ0KICAgMzEuICBDbGFyaWZpZWQgdGhhdCBjb25m
aWd1cmF0aW9uIGZvciBpbnRlcmZhY2UgWCBzaG91bGQgYmUgcmVxdWVzdGVkCSAJCQ0KICAgICAg
ICBvdmVyIGludGVyZmFjZSBYICh0aWNrZXQgIzQ4KS4JIAkJDQogCQkNCiAgIDMyLiAgQ09ORklS
TSBpcyBub3cgYW4gb3B0aW9uYWwgbWVzc2FnZSAoTVVTVCBzZW5kIENvbmZpcm0gZWFzZWQgdG8J
IAkJDQogICAgICAgIFNIT1VMRCkgKHRpY2tldCAjMTIwKS4JIAkJDQogCQkNCiAgIDMzLiAgQWRk
ZWQgcmVmZXJlbmNlIHRvIFJGQzcyMjc6IERIQ1B2NiBPcHRpb24gR3VpZGVsaW5lcyAodGlja2V0
CSAJCQ0KICAgICAgICAjMTIxKS4JIAkJDQogCQkNCiAgIDM0LiAgQWRkZWQgbmV3IHNlY3Rpb24g
NSBwcm92aWRpbmcgYW4gb3ZlcnZpZXcgb2YgREhDUHY2IG9wZXJhdGlvbmFsCSAJCQ0KICAgICAg
ICBtb2RlcyBhbmQgcmVtb3ZlZCB0d28gcHJlZml4IGRlbGVnYXRpb24gc2VjdGlvbnMgZnJvbSBz
ZWN0aW9uIDEuCSAJCQ0KICAgICAgICBTZWUgdGlja2V0cyAjNTMsICMxMDAsIGFuZCAjMTAyLgkg
CQkNCiAJCQ0KICAgMzUuICBBZGRyZXNzZWQgdGlja2V0ICMxMTUgLSBkb24ndCB1c2UgREhDUHY2
IGZvciBESENQdjQJIAkJDQogICAgICAgIGNvbmZpZ3VyYXRpb24uDQoNClRoaXMgdmVyc2lvbiBh
bHNvIGluY2x1ZGVzIGEgZmV3IHVuZmluaXNoZWQgaXRlbXMuIFByb2dyZXNzIGhhcyBiZWVuIGEg
Yml0IHNsb3dlciB0aGFuIGhvcGVkIGluIHRoZSBwYXN0IHNldmVyYWwgbW9udGhzLg0KDQotIEJl
cm5pZQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQtZHJhZnRz
QGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6IE1vbmRh
eSwgT2N0b2JlciAyNywgMjAxNCAxMDowMiBBTQ0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZp
Y2F0aW9uIGZvciBkcmFmdC1kaGN3Zy1kaGMtcmZjMzMxNWJpcy0wMy50eHQNCg0KDQpBIG5ldyB2
ZXJzaW9uIG9mIEktRCwgZHJhZnQtZGhjd2ctZGhjLXJmYzMzMTViaXMtMDMudHh0DQpoYXMgYmVl
biBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEJlcm5pZSBWb2x6IGFuZCBwb3N0ZWQgdG8gdGhl
DQpJRVRGIHJlcG9zaXRvcnkuDQoNCk5hbWU6CQlkcmFmdC1kaGN3Zy1kaGMtcmZjMzMxNWJpcw0K
UmV2aXNpb246CTAzDQpUaXRsZToJCUR5bmFtaWMgSG9zdCBDb25maWd1cmF0aW9uIFByb3RvY29s
IGZvciBJUHY2IChESENQdjYpIGJpcw0KRG9jdW1lbnQgZGF0ZToJMjAxNC0xMC0yNw0KR3JvdXA6
CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NClBhZ2VzOgkJMTIzDQpVUkw6ICAgICAgICAgICAgaHR0
cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtZGhjd2ctZGhjLXJmYzMzMTVi
aXMtMDMudHh0DQpTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtZGhjd2ctZGhjLXJmYzMzMTViaXMvDQpIdG1saXplZDogICAgICAgaHR0cDovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtZGhjd2ctZGhjLXJmYzMzMTViaXMtMDMNCkRpZmY6ICAg
ICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1kaGN3Zy1kaGMt
cmZjMzMxNWJpcy0wMw0KDQpBYnN0cmFjdDoNCiAgIFRoZSBEeW5hbWljIEhvc3QgQ29uZmlndXJh
dGlvbiBQcm90b2NvbCBmb3IgSVB2NiAoREhDUCkgZW5hYmxlcyBESENQDQogICBzZXJ2ZXJzIHRv
IHBhc3MgY29uZmlndXJhdGlvbiBwYXJhbWV0ZXJzIHN1Y2ggYXMgSVB2NiBuZXR3b3JrDQogICBh
ZGRyZXNzZXMgdG8gSVB2NiBub2Rlcy4gIEl0IG9mZmVycyB0aGUgY2FwYWJpbGl0eSBvZiBhdXRv
bWF0aWMNCiAgIGFsbG9jYXRpb24gb2YgcmV1c2FibGUgbmV0d29yayBhZGRyZXNzZXMgYW5kIGFk
ZGl0aW9uYWwgY29uZmlndXJhdGlvbg0KICAgZmxleGliaWxpdHkuICBUaGlzIHByb3RvY29sIGlz
IGEgc3RhdGVmdWwgY291bnRlcnBhcnQgdG8gIklQdjYNCiAgIFN0YXRlbGVzcyBBZGRyZXNzIEF1
dG9jb25maWd1cmF0aW9uIiAoUkZDIDQ4NjIpLCBhbmQgY2FuIGJlIHVzZWQNCiAgIHNlcGFyYXRl
bHkgb3IgY29uY3VycmVudGx5IHdpdGggdGhlIGxhdHRlciB0byBvYnRhaW4gY29uZmlndXJhdGlv
bg0KICAgcGFyYW1ldGVycy4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClBsZWFz
ZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1l
IG9mIHN1Ym1pc3Npb24NCnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBh
dmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==


From nobody Mon Oct 27 12:23:14 2014
Return-Path: <ian.farrer@telekom.de>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D41B21AD062 for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 12:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.859
X-Spam-Level: 
X-Spam-Status: No, score=-3.859 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 VFa9GICQKlkU for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 12:22:42 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 459011AD045 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 12:22:03 -0700 (PDT)
Received: from q4de8psa169.blf.telekom.de ([10.151.13.200]) by tcmail11.telekom.de with ESMTP; 27 Oct 2014 20:22:00 +0100
X-IronPort-AV: E=Sophos;i="5.04,797,1406584800";  d="scan'208,217";a="688651428"
Received: from he111629.emea1.cds.t-internal.com ([10.134.93.21]) by q4de8psazkj.blf.telekom.de with ESMTP/TLS/AES128-SHA; 27 Oct 2014 20:22:00 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111629.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 27 Oct 2014 20:22:00 +0100
From: <ian.farrer@telekom.de>
To: <volz@cisco.com>, <dhcwg@ietf.org>
Date: Mon, 27 Oct 2014 20:21:58 +0100
Thread-Topic: WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
Thread-Index: Ac/minMIxUbYwkSiQNCrNLgZzh2MnQLAB7KgACCNBVA=
Message-ID: <8A1B81989BCFAE44A22B2B86BF2B76318B33AEA6C9@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6F6B1D@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6F6B1D@xmb-rcd-x04.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_8A1B81989BCFAE44A22B2B86BF2B76318B33AEA6C9HE111643EMEA1_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/-fkQqbFS0xjzGbeG0VRqVzQgZ1Q
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 27 Oct 2014 19:22:55 -0000

--_000_8A1B81989BCFAE44A22B2B86BF2B76318B33AEA6C9HE111643EMEA1_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Bernie,

Many thanks for the review. Please see inline.

Cheers,
Ian

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Montag, 27. Oktober 2014 04:08
To: dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02=
 - Respond by Oct 27, 2014

While I am ok advancing this work if someone feels they need it (I would pr=
efer we not deploy this technology and just move to IPv6 - especially as th=
is requires making changes to hosts), I do have review comments that I beli=
eve need to be addressed:

In 1. Introduction, why reference ietf-dhc-dhcpv4-over-ip6v4? That work was=
 an alternative to what became RFC 7341 and the WG decided that dhpv4-over-=
dhcpv6 was the way forward. Perhaps just drop "such as DHCPv4 over IPv6 [re=
ference]"?

[if] I'm happy to remove this. IIRC, the ref was left in there when DHCPv4o=
IPv6 was intended to be an experimental RFC, but as it's no longer being up=
dated, then it can go.

In the next paragraph, RFC 6346 is mentioned - this is an Experimental docu=
ment. It is only an informational reference, so at least that may be OK. Bu=
t it seems a bit odd that the text here is "This extension is only suitable=
 for specific architectures based on Address plus Port model" when that is =
experimental? Even draft-ietf-softwire-map-t (-06) is going for Experimenta=
l, not standards track. (Though draft-ietf-softwire-map is going for Standa=
rds Track.)

[if] How about updating that sentence to read:
This extension is only suitable for specific architectures based on the Add=
ress plus Port model (A+P) [RFC6346], such as [I-D.ietf-softwire-lw4o6] and=
 [I-D.ieft-softwire-map].

In 4. Functional Overview:

-          In the 2nd paragraph, this option is only used in the PRL in the=
 DHCPDISCOVER? It is send by the client in DHCPREQUEST (DHCPRELEASE) messag=
es. Perhaps this should be indicated?
[if] Propose the sentence with the wording
The client includes this option within the Parameter Request List option [R=
FC2132] in its DHCPv4 request, indicating its support for shared, dynamic a=
ddress leasing to the DHCP 4o6 server.
Is updated to:
The client includes this option within the Parameter Request List option [R=
FC2132] in DHCPv4 DHCPDISCOVER and DHCPREQUEST messages, indicating its sup=
port for shared, dynamic address leasing to the DHCP 4o6 server.

>From my reading of RFC2131 (sec 4.4.1), PRL is not included in the DHCPRELE=
ASE message.


-          I think in the last paragraph, first sentence, which should be t=
hat? ... to identify clients that support?

[if] New wording proposal:
OPTION_V4_PORTPARAMS is also implemented by the server so that clients supp=
orting shared, dynamic address leasing can be
identified and so that shared IPv4 address and PSID leases can be  allocate=
d and maintained.

In 5. Client-Server Interactions:

-          In #1, there is an opened parenthesis that is never closed.

[if] Will fix.


-          In #3, what if the client receives offers without the OPTION_V4_=
PORTPARAMS? Should it prefer that (I would think so)? (You do mention this =
later in section 7.)

[if] OK, I'll add some text to prefer the full address.


-          Ted already pointed out the issue in the last paragraph with RFC=
 2131 3.2 and that a DHCPREQUEST is sent, not a DHCPDISCOVER. I think this =
will also need some careful attention as this could result in problems if t=
he client ends up on a different network and a server decides to allocate t=
he requested address but doesn't support OPTION_V4_PORTPARAMs? First, I thi=
nk perhaps using input from the IPv6 layer (i.e., as this is using RFC7341)=
 can help since if the V6 stack determines the location has changed, then o=
bviously going to DHCPDISCOVER is the better choice? (Not sure if perhaps w=
e should recommend that existing "traditional" DHCP servers that receive a =
DHCPREQUEST (init-reboot) with an OPTION_V4_PORTPARAMS should either drop t=
he packet or send a DHCPNAK it?

[if] I can add some text into the client behavior section saying:
"In the event that the client's DHCPv4o6 IPv6 source address is  changed fo=
r any reason, the client MUST re-initiate the DHCPv4o6 shared-address provi=
sioning process by sending a DHCPDISCOVER message".

For recommending that 'traditional' DHCP servers, can we meaningfully do th=
at in this spec? Surely existing server implementations will behave as they=
 do, unless this is positioned as an update to RFC7341?
In 6. Server Behavior, un the 2nd paragraph "server MUST run an address and=
 port-set" is rather odd wording? Do you implemented instead of run?

[if] Agreed. Will change.

Section 7. Client Behavior is rather similar to section 5. Kind of a bit od=
d order (perhaps Client-Server Interactions, Client Behavior, Server Behavi=
or would be a bit better, but not a big deal).

[if] OK. I'll reorder them.

In 7.1, is there any RFC to reference here that describes the limitations f=
or a node with a limited port set? For the first bulleted item, do we know =
what "port-aware" protocols are? I think this is not a common term, so it w=
ill have to be defined? Also for the sentence that introduces the list "Cli=
ent MUST apply ... to ... the shared address"? I think what you mean here i=
s if it provides information to another node to make connections back (into=
) the client, it must use its port range?

[if] We could reword to: Only port-aware protocols (e.g TCP, UDP, DCCP etc.=
) or ICMP implementing [RFC5508] MUST be used.
For the second point, the intention is to restrict outgoing connection's so=
urce port and service listeners to being initiated only with protocols that=
 have L4 ports, and only to use the specific range of ports which have been=
 provisioned to it. Can this be clarified by changing the intro sentence to=
?:

The client MUST apply the following rules for all traffic destined to or or=
iginating from the shared IPv4 address

In 9.1, isn't there also a problem if a malicious client doesn't follow the=
 rules in section 7.1 if there isn't proper filtering in place (i.e., egres=
s filtering).

[if] For this to be a problem, there would need to be operator mis-configur=
ation in the A+P border router, and matching malicious configuration on the=
 client. As lw4o6 & MAP implement ingress and egress checks that the packet=
s received are valid (i.e. there must be a match between the v6 address, an=
d source IPv4 address and L4 ports for decap and a valid IPv4 address and d=
st port for encap).  As this is data-plane functionality, and this draft is=
 concerned with provisioning, do you think this needs to be re-iterated her=
e?


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, October 12, 2014 10:14 PM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - R=
espond by Oct 27, 2014


Hi all,



This message starts the DHC working group last call to advance "Dynamic All=
ocation of Shared IPv4 Addresses", draft-ietf-dhc-dynamic-shared-v4allocati=
on-02, document as a Standards Track (Proposed Standard) RFC. The authors b=
elieve that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-02



Please send your comments by October 27th, 2014. If you do not feel this do=
cument should advance, please state your reasons why.



There are no IPR claims reported at this time.



Bernie Volz is the currently assigned shepherd for this document.



- Tomek & Bernie


--_000_8A1B81989BCFAE44A22B2B86BF2B76318B33AEA6C9HE111643EMEA1_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1171064775;
	mso-list-type:hybrid;
	mso-list-template-ids:988594168 -1603473238 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Hi Bernie,<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'color:#1F497D'>Many thanks for the review. Please see inline.<o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>=
&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>C=
heers,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F49=
7D'>Ian<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F4=
97D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border-top:=
solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><spa=
n lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'=
>From:</span></b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"=
Tahoma","sans-serif"'> dhcwg [mailto:dhcwg-bounces@ietf.org] <b>On Behalf O=
f </b>Bernie Volz (volz)<br><b>Sent:</b> Montag, 27. Oktober 2014 04:08<br>=
<b>To:</b> dhcwg@ietf.org<br><b>Subject:</b> Re: [dhcwg] WGLC for draft-iet=
f-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014<o:p></o:p></=
span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DM=
soNormal><span lang=3DEN-US style=3D'color:#1F497D'>While I am ok advancing=
 this work if someone feels they need it (I would prefer we not deploy this=
 technology and just move to IPv6 &#8211; especially as this requires makin=
g changes to hosts), I do have review comments that I believe need to be ad=
dressed:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=
=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span l=
ang=3DEN-US style=3D'color:#1F497D'>In 1. Introduction, why reference ietf-=
dhc-dhcpv4-over-ip6v4? That work was an alternative to what became RFC 7341=
 and the WG decided that dhpv4-over-dhcpv6 was the way forward. Perhaps jus=
t drop &#8220;such as DHCPv4 over IPv6 [reference]&#8221;?<o:p></o:p></span=
></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'><o:p>&=
nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'colo=
r:#1F497D'>[if] I&#8217;m happy to remove this. IIRC, the ref was left in t=
here when DHCPv4oIPv6 was intended to be an experimental RFC, but as it&#82=
17;s no longer being updated, then it can go.<o:p></o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>In=
 the next paragraph, RFC 6346 is mentioned &#8211; this is an Experimental =
document. It is only an informational reference, so at least that may be OK=
. But it seems a bit odd that the text here is &#8220;This extension is onl=
y suitable for specific architectures based on Address plus Port model&#822=
1; when that is experimental? Even draft-ietf-softwire-map-t (-06) is going=
 for Experimental, not standards track. (Though draft-ietf-softwire-map is =
going for Standards Track.)<o:p></o:p></span></p><p class=3DMsoNormal><span=
 lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>[if] How about upda=
ting that sentence to read:<o:p></o:p></span></p><p class=3DMsoNormal><span=
 lang=3DEN-US style=3D'color:#1F497D'>This extension is only suitable for s=
pecific architectures based on the Address plus Port model (A+P) [RFC6346],=
 such as [I-D.ietf-softwire-lw4o6] and [I-D.ieft-softwire-map].<o:p></o:p><=
/span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D=
'color:#1F497D'>In 4. Functional Overview:<o:p></o:p></span></p><p class=3D=
MsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![i=
f !supportLists]><span lang=3DEN-US style=3D'color:#1F497D'><span style=3D'=
mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><=
span lang=3DEN-US style=3D'color:#1F497D'>In the 2<sup>nd</sup> paragraph, =
this option is only used in the PRL in the DHCPDISCOVER? It is send by the =
client in DHCPREQUEST (DHCPRELEASE) messages. Perhaps this should be indica=
ted?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'=
color:#1F497D'>[if] Propose the sentence with the wording<o:p></o:p></span>=
</p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>The cli=
ent includes this option within the Parameter Request List option [RFC2132]=
 in its DHCPv4 request, indicating its support for shared, dynamic address =
leasing to the DHCP 4o6 server.<o:p></o:p></span></p><p class=3DMsoNormal><=
span lang=3DEN-US style=3D'color:#1F497D'>Is updated to:<o:p></o:p></span><=
/p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>The clie=
nt includes this option within the Parameter Request List option [RFC2132] =
in DHCPv4 DHCPDISCOVER and DHCPREQUEST messages, indicating its support for=
 shared, dynamic address leasing to the DHCP 4o6 server.<o:p></o:p></span><=
/p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:=
#1F497D'>From my reading of RFC2131 (sec 4.4.1), PRL is not included in the=
 DHCPRELEASE message.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=
=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
ListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !=
supportLists]><span lang=3DEN-US style=3D'color:#1F497D'><span style=3D'mso=
-list:Ignore'>-<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><spa=
n lang=3DEN-US style=3D'color:#1F497D'>I think in the last paragraph, first=
 sentence, which should be that? &#8230; to identify clients that support?<=
o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color=
:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-=
US style=3D'color:#1F497D'>[if] New wording proposal:<o:p></o:p></span></p>=
<p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>OPTION_V4_P=
ORTPARAMS is also implemented by the server so that clients supporting shar=
ed, dynamic address leasing can be<o:p></o:p></span></p><p class=3DMsoNorma=
l><span lang=3DEN-US style=3D'color:#1F497D'>identified and so that shared =
IPv4 address and PSID leases can be&nbsp; allocated and maintained.<o:p></o=
:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US styl=
e=3D'color:#1F497D'>In 5. Client-Server Interactions:<o:p></o:p></span></p>=
<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1=
 lfo2'><![if !supportLists]><span lang=3DEN-US style=3D'color:#1F497D'><spa=
n style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New Roman"'>&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>=
<![endif]><span lang=3DEN-US style=3D'color:#1F497D'>In #1, there is an ope=
ned parenthesis that is never closed.<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>[if] Will =
fix.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'=
color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph styl=
e=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><spa=
n lang=3DEN-US style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<sp=
an style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US sty=
le=3D'color:#1F497D'>In #3, what if the client receives offers without the =
OPTION_V4_PORTPARAMS? Should it prefer that (I would think so)? (You do men=
tion this later in section 7.)<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p cla=
ss=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>[if] OK, I&#8217;=
ll add some text to prefer the full address.<o:p></o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:=
l0 level1 lfo2'><![if !supportLists]><span lang=3DEN-US style=3D'color:#1F4=
97D'><span style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></spa=
n></span><![endif]><span lang=3DEN-US style=3D'color:#1F497D'>Ted already p=
ointed out the issue in the last paragraph with RFC 2131 3.2 and that a DHC=
PREQUEST is sent, not a DHCPDISCOVER. I think this will also need some care=
ful attention as this could result in problems if the client ends up on a d=
ifferent network and a server decides to allocate the requested address but=
 doesn&#8217;t support OPTION_V4_PORTPARAMs? First, I think perhaps using i=
nput from the IPv6 layer (i.e., as this is using RFC7341) can help since if=
 the V6 stack determines the location has changed, then obviously going to =
DHCPDISCOVER is the better choice? (Not sure if perhaps we should recommend=
 that existing &#8220;traditional&#8221; DHCP servers that receive a DHCPRE=
QUEST (init-reboot) with an OPTION_V4_PORTPARAMS should either drop the pac=
ket or send a DHCPNAK it?<o:p></o:p></span></p><p class=3DMsoNormal><span l=
ang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3D=
MsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>[if] I can add some te=
xt into the client behavior section saying:<o:p></o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>&#8220;In the event=
 that the client&#8217;s DHCPv4o6 IPv6 source address is&nbsp; changed for =
any reason, the client MUST re-initiate the DHCPv4o6 shared-address provisi=
oning process by sending a DHCPDISCOVER message&#8221;.<o:p></o:p></span></=
p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbs=
p;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#=
1F497D'>For recommending that &#8216;traditional&#8217; DHCP servers, can w=
e meaningfully do that in this spec? Surely existing server implementations=
 will behave as they do, unless this is positioned as an update to RFC7341?=
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'colo=
r:#1F497D'> <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US s=
tyle=3D'color:#1F497D'>In 6. Server Behavior, un the 2<sup>nd</sup> paragra=
ph &#8220;server MUST run an address and port-set&#8221; is rather odd word=
ing? Do you implemented instead of run?<o:p></o:p></span></p><p class=3DMso=
Normal><span lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>[if] Agr=
eed. Will change.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN=
-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorma=
l><span lang=3DEN-US style=3D'color:#1F497D'>Section 7. Client Behavior is =
rather similar to section 5. Kind of a bit odd order (perhaps Client-Server=
 Interactions, Client Behavior, Server Behavior would be a bit better, but =
not a big deal).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-=
US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><span lang=3DEN-US style=3D'color:#1F497D'>[if] OK. I&#8217;ll reorder the=
m.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'co=
lor:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3D=
EN-US style=3D'color:#1F497D'>In 7.1, is there any RFC to reference here th=
at describes the limitations for a node with a limited port set? For the fi=
rst bulleted item, do we know what &#8220;port-aware&#8221; protocols are? =
I think this is not a common term, so it will have to be defined? Also for =
the sentence that introduces the list &#8220;Client MUST apply &#8230; to &=
#8230; the shared address&#8221;? I think what you mean here is if it provi=
des information to another node to make connections back (into) the client,=
 it must use its port range?<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>[if] We could rewor=
d to: Only port-aware protocols (e.g TCP, UDP, DCCP etc.) or ICMP implement=
ing [RFC5508] MUST be used.<o:p></o:p></span></p><p class=3DMsoNormal><span=
 lang=3DEN-US style=3D'color:#1F497D'>For the second point, the intention i=
s to restrict outgoing connection&#8217;s source port and service listeners=
 to being initiated only with protocols that have L4 ports, and only to use=
 the specific range of ports which have been provisioned to it. Can this be=
 clarified by changing the intro sentence to?:<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p><=
/span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>T=
he client MUST apply the following rules for all traffic destined to or ori=
ginating from the shared IPv4 address<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>In 9.1, is=
n&#8217;t there also a problem if a malicious client doesn&#8217;t follow t=
he rules in section 7.1 if there isn&#8217;t proper filtering in place (i.e=
., egress filtering).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=
=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
Normal><span lang=3DEN-US style=3D'color:#1F497D'>[if] For this to be a pro=
blem, there would need to be operator mis-configuration in the A+P border r=
outer, and matching malicious configuration on the client. As lw4o6 &amp; M=
AP implement ingress and egress checks that the packets received are valid =
(i.e. there must be a match between the v6 address, and source IPv4 address=
 and L4 ports for decap and a valid IPv4 address and dst port for encap).&n=
bsp; As this is data-plane functionality, and this draft is concerned with =
provisioning, do you think this needs to be re-iterated here?<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'><o:=
p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph style=3D'text-indent:-=
18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span lang=3DEN-US sty=
le=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<span style=3D'font:7=
.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; </span></span></span><![endif]><span lang=3DEN-US style=3D'color:#1F497=
D'>Bernie<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US styl=
e=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:n=
one;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMs=
oNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span lang=3DEN-US style=3D'font-size:10.0p=
t;font-family:"Tahoma","sans-serif"'> dhcwg [<a href=3D"mailto:dhcwg-bounce=
s@ietf.org">mailto:dhcwg-bounces@ietf.org</a>] <b>On Behalf Of </b>Bernie V=
olz (volz)<br><b>Sent:</b> Sunday, October 12, 2014 10:14 PM<br><b>To:</b> =
<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br><b>Subject:</b> [dh=
cwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oc=
t 27, 2014<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span lang=
=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DE=
N-US>Hi all,<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-U=
S><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>Th=
is message starts the DHC working group last call to advance &quot;Dynamic =
Allocation of Shared IPv4 Addresses&quot;, draft-ietf-dhc-dynamic-shared-v4=
allocation-02, document as a Standards Track (Proposed Standard) RFC. The a=
uthors believe that this version is ready.<o:p></o:p></span></p><p class=3D=
MsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoP=
lainText><span lang=3DEN-US>The draft is available here:<o:p></o:p></span><=
/p><p class=3DMsoPlainText><span lang=3DEN-US><a href=3D"http://tools.ietf.=
org/html/draft-ietf-dhc-dynamic-shared-v4allocation-02">http://tools.ietf.o=
rg/html/draft-ietf-dhc-dynamic-shared-v4allocation-02</a><o:p></o:p></span>=
</p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>=
<p class=3DMsoPlainText><span lang=3DEN-US>Please send your comments by Oct=
ober 27th, 2014. If you do not feel this document should advance, please st=
ate your reasons why.<o:p></o:p></span></p><p class=3DMsoPlainText><span la=
ng=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=
=3DEN-US>There are no IPR claims reported at this time.<o:p></o:p></span></=
p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoPlainText><span lang=3DEN-US>Bernie Volz is the currently assig=
ned shepherd for this document.<o:p></o:p></span></p><p class=3DMsoPlainTex=
t><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><s=
pan lang=3DEN-US>- Tomek &amp; Bernie<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>=

--_000_8A1B81989BCFAE44A22B2B86BF2B76318B33AEA6C9HE111643EMEA1_--


From nobody Mon Oct 27 13:49:28 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABBF61AD3E9 for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 13:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Xi9aeK8JF8ay for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 13:49:03 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 333441ACE48 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 13:49:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s9RKn2DN027542; Mon, 27 Oct 2014 13:49:02 -0700
Received: from XCH-BLV-102.nw.nos.boeing.com (xch-blv-102.nw.nos.boeing.com [130.247.25.117]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s9RKmxeB027036 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 27 Oct 2014 13:48:59 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.66]) by XCH-BLV-102.nw.nos.boeing.com ([169.254.2.221]) with mapi id 14.03.0210.002; Mon, 27 Oct 2014 13:48:58 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
Thread-Index: Ac/xaWYb7j/iiP3ISmCf+ekbUUcpTQAvYnEA
Date: Mon, 27 Oct 2014 20:48:58 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/-Dlqy2pmafd8pcecqJJyn0_lc_k
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 27 Oct 2014 20:49:08 -0000

Hi,

I am quite fine with the Client trusting the Server by leap of faith. In th=
e other
direction, I need some way for the Client to prove to the Server that it is=
 the
authentic owner of the claimed Client ID.

Does this new document version provide that?

Thanks - Fred
fred.l.templin@boeing.com


---
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, October 26, 2014 3:11 PM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 20=
14

Hi all,

This message starts the (short) DHC working group last call to advance "Sec=
ure DHCPv6", draft-ietf-dhc-sedhcpv6-04, document as a Standards Track (Pro=
posed Standard) RFC. The authors believe that this version is ready. We had=
 a WGLC earlier (May 2014 for the -02 version) and there were some comments=
, so this is primarily to assure that those comments were addressed.

The draft is available here:
http://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-04

Please send your comments by November 3rd, 2014. If you do not feel this do=
cument should advance, please state your reasons why.

There are no IPR claims reported at this time.

Tomek is the assigned shepherd for this document.

- Tomek & Bernie


From nobody Mon Oct 27 15:14:52 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05B981A19F3; Mon, 27 Oct 2014 15:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 dyyNHn1YAiRW; Mon, 27 Oct 2014 15:14:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE281A19EB; Mon, 27 Oct 2014 15:14:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141027221439.23942.50419.idtracker@ietfa.amsl.com>
Date: Mon, 27 Oct 2014 15:14:39 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/510dHu2V7u7rP30pyBdMtc1TjYk
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-access-network-identifier-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 27 Oct 2014 22:14:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Access Network Identifier Option in DHCP
        Authors         : Shwetha Bhandari
                          Sri Gundavelli
                          Jouni Korhonen
                          Mark Grayson
	Filename        : draft-ietf-dhc-access-network-identifier-04.txt
	Pages           : 20
	Date            : 2014-10-27

Abstract:
   This document specifies the format and mechanism that is to be used
   for encoding access network identifiers in DHCPv4 and DHCPv6 messages
   by defining new access network identifier options and sub-options.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-access-network-identifier/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-access-network-identifier-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-access-network-identifier-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Oct 27 19:45:34 2014
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 997F11A1B74 for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 19:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 BqzWc-V2WcPP for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 19:45:32 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5AD21A1B60 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 19:45:31 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOC63065; Tue, 28 Oct 2014 02:45:30 +0000 (GMT)
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 28 Oct 2014 02:45:13 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.22]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Tue, 28 Oct 2014 10:45:05 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3,	2014
Thread-Index: AQHP8ieJJUcfEK8wIkyxJXJN27K0dpxEsZ9Q
Date: Tue, 28 Oct 2014 02:45:05 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com> <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/t4RXqiuWg9OHaWHpEKBsjn327o0
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 28 Oct 2014 02:45:33 -0000

PkkgYW0gcXVpdGUgZmluZSB3aXRoIHRoZSBDbGllbnQgdHJ1c3RpbmcgdGhlIFNlcnZlciBieSBs
ZWFwIG9mIGZhaXRoLiBJbiB0aGUgb3RoZXINCj5kaXJlY3Rpb24sIEkgbmVlZCBzb21lIHdheSBm
b3IgdGhlIENsaWVudCB0byBwcm92ZSB0byB0aGUgU2VydmVyIHRoYXQgaXQgaXMgdGhlDQo+YXV0
aGVudGljIG93bmVyIG9mIHRoZSBjbGFpbWVkIENsaWVudCBJRC4NCj4NCj5Eb2VzIHRoaXMgbmV3
IGRvY3VtZW50IHZlcnNpb24gcHJvdmlkZSB0aGF0Pw0KDQpIaSwgRnJlZCwNCg0KVGhpcyB2ZXJz
aW9uIGhhcyBwcm92aWRlZCBhIGNlcnRpZmljYXRlLWJhc2VkIG1lY2hhbmlzbSBmb3IgdGhlIGNs
aWVudCB0byBhdXRoZW50aWNhdGVkIGJ5IHRoZSBzZXJ2ZXIuIEl0IGlzIGFzc3VtaW5nIHRoZSBj
bGllbnQgaGFzIGEgY2VydGlmaWNhdGUgaG9ub3JlZCBieSB0aGUgc2VydmVyLg0KDQpCZXN0IHJl
Z2FyZHMsDQoNClNoZW5nDQoNCj5UaGFua3MgLSBGcmVkDQo+ZnJlZC5sLnRlbXBsaW5AYm9laW5n
LmNvbQ0KPg0KPg0KPi0tLQ0KPkZyb206IGRoY3dnIFttYWlsdG86ZGhjd2ctYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmIE9mIEJlcm5pZSBWb2x6DQo+KHZvbHopDQo+U2VudDogU3VuZGF5LCBP
Y3RvYmVyIDI2LCAyMDE0IDM6MTEgUE0NCj5UbzogZGhjd2dAaWV0Zi5vcmcNCj5TdWJqZWN0OiBb
ZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhjLXNlZGhjcHY2LTA0IC0gUmVzcG9uZCBieSBO
b3YgMywNCj4yMDE0DQo+DQo+SGkgYWxsLA0KPg0KPlRoaXMgbWVzc2FnZSBzdGFydHMgdGhlIChz
aG9ydCkgREhDIHdvcmtpbmcgZ3JvdXAgbGFzdCBjYWxsIHRvIGFkdmFuY2UNCj4iU2VjdXJlIERI
Q1B2NiIsIGRyYWZ0LWlldGYtZGhjLXNlZGhjcHY2LTA0LCBkb2N1bWVudCBhcyBhIFN0YW5kYXJk
cyBUcmFjaw0KPihQcm9wb3NlZCBTdGFuZGFyZCkgUkZDLiBUaGUgYXV0aG9ycyBiZWxpZXZlIHRo
YXQgdGhpcyB2ZXJzaW9uIGlzIHJlYWR5LiBXZQ0KPmhhZCBhIFdHTEMgZWFybGllciAoTWF5IDIw
MTQgZm9yIHRoZSAtMDIgdmVyc2lvbikgYW5kIHRoZXJlIHdlcmUgc29tZQ0KPmNvbW1lbnRzLCBz
byB0aGlzIGlzIHByaW1hcmlseSB0byBhc3N1cmUgdGhhdCB0aG9zZSBjb21tZW50cyB3ZXJlDQo+
YWRkcmVzc2VkLg0KPg0KPlRoZSBkcmFmdCBpcyBhdmFpbGFibGUgaGVyZToNCj5odHRwOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWRoYy1zZWRoY3B2Ni0wNA0KPg0KPlBsZWFzZSBz
ZW5kIHlvdXIgY29tbWVudHMgYnkgTm92ZW1iZXIgM3JkLCAyMDE0LiBJZiB5b3UgZG8gbm90IGZl
ZWwgdGhpcw0KPmRvY3VtZW50IHNob3VsZCBhZHZhbmNlLCBwbGVhc2Ugc3RhdGUgeW91ciByZWFz
b25zIHdoeS4NCj4NCj5UaGVyZSBhcmUgbm8gSVBSIGNsYWltcyByZXBvcnRlZCBhdCB0aGlzIHRp
bWUuDQo+DQo+VG9tZWsgaXMgdGhlIGFzc2lnbmVkIHNoZXBoZXJkIGZvciB0aGlzIGRvY3VtZW50
Lg0KPg0KPi0gVG9tZWsgJiBCZXJuaWUNCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPmRoY3dnIG1haWxpbmcgbGlzdA0KPmRoY3dnQGlldGYub3Jn
DQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaGN3Zw0K


From nobody Mon Oct 27 22:25:44 2014
Return-Path: <liuzilong8266@163.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 018E01A0358 for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 22:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.109
X-Spam-Level: **
X-Spam-Status: No, score=2.109 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_MISSP_XPRIO=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, RELAY_IS_220=2.118, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 m67zXy0zIVGQ for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 22:25:41 -0700 (PDT)
Received: from m13-244.163.com (m13-244.163.com [220.181.13.244]) by ietfa.amsl.com (Postfix) with ESMTP id 5AF6A1A0277 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 22:25:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Message-ID:Subject:MIME-Version; bh=8umWN 0a+BYXN8RJlWBMcY2hGHxho72Q2+atqoOs/Aok=; b=cOwGu95aAu/RKDI6bCNTM gR3txNz9vGSdNyxZwSMXU5GgPP6nhX6MyADjtijc6TpoUc9f3P2ZLcCGKgQvkt47 4Z3qh6tDNtBLFwv1GnLEVOV39ALZxFRSK0QM2Cn0ON0v6DrjBPKSifeS+ZxRmBWB IkOqmlNBLsiGGIr742PZlI=
Received: from liuzilong8266$163.com ( [166.111.68.231] ) by ajax-webmail-sdy10 (Coremail) ; Tue, 28 Oct 2014 13:25:35 +0800 (GMT+08:00)
Date: Tue, 28 Oct 2014 13:25:07 +0800
From: "liuzilong8266"<liuzilong8266@163.com>
To: "dhcwg"<dhcwg@ietf.org>
Message-ID: <75621680.2ae0.14955376acd.Coremail.liuzilong8266@163.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="__=_Part_Boundary_006_027835.001427"
X-Mailer: NetEase Flash Mail 2.4.0.11
X-Priority: 3 (Normal)
X-Originating-IP: [166.111.68.231]
X-CM-TRANSID: 68KowGApGkHQKE9UbekMAA--.13135W
X-CM-SenderInfo: xolx6xporqwmqswwqiywtou0bp/xtbBZAgzmFQGwLs5xwABsR
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/ggP7yKI1e5rsK4X65ojOA5tIiTE
Cc: =?UTF-8?B?546L5piK?= <wangh13@mails.tsinghua.edu.cn>, =?UTF-8?B?5p2O5aSp57+U?= <1515452578@qq.com>, =?UTF-8?B?5bSU5YuH?= <cuiyong@tsinghua.edu.cn>, =?UTF-8?B?5p2O5Li95aeX?= <lilishan9248@126.com>, =?UTF-8?B?5a2Z55Cq?= <sunqibupt@gmail.com>
Subject: [dhcwg] Fw: New Version Notification for draft-cui-dhc-dhcp4o6-active-leasequery-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 28 Oct 2014 05:25:43 -0000

--__=_Part_Boundary_006_027835.001427
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

SGkgYWxsLA0KICAgICAgICAgV2Ugc3VibWl0dGVkIGEgbmV3IGRyYWZ0IGFib3V0IERIQ1A0bzYg
QWN0aXZlIExlYXNlcXVlcnkuIEl0IGV4dGVuZHMgdGhlIERIQ1B2NiBBY3RpdmUgTGVhc2VxdWVy
eSB0byBwcm92aWRlIGFuIG1lY2hhbmlzbSB0byBnZXR0aW5nIHJlYWwtdGltZSBESENQdjQgb3Zl
ciBESENQdjYgbGVhc2UgaW5mb3JtYXRpb24oREhDUHY0IGxlYXNlIGFuZCByZWxhdGVkIERIQ1B2
NiBpbmZvcm1hdGlvbikuIEl0IGNhbiBiZSB1c2VkIGluIExpZ2h0d2VpZ2h0IDRvdmVyNiBkeW5h
bWljIHByb3Zpc2lvbmluZyB0aGF0IGx3QUZUUiBjYW4gZ2V0IGx3QjRzJyBESENQdjQgb3ZlciBE
SENQdjYgbGVhc2UgaW5mb3JtYXRpb24gZm9yIG1hcHBpbmcgdGFibGUuDQoNClBsZWFzZSBjb3Vs
ZCB5b3UgcmV2aWV3IHRoZSBkcmFmdCBhbmQgYW55IGNvbW1lbnRzIGFyZSBtb3JlIHRoYW4gd2Vs
Y29tZS4NCg0KDQpCZXN0IFJlZ2FyZHMsDQoNClppbG9uZw0KDQoyMDE0LTEwLTI4IA0KDQpsaXV6
aWxvbmc4MjY2IA0KDQoNCg0K5Y+R5Lu25Lq677yaaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnDQrl
j5HpgIHml7bpl7TvvJoyMDE0LTEwLTI3IDIxOjUxDQrkuLvpopjvvJpOZXcgVmVyc2lvbiBOb3Rp
ZmljYXRpb24gZm9yIGRyYWZ0LWN1aS1kaGMtZGhjcDRvNi1hY3RpdmUtbGVhc2VxdWVyeS0wMC50
eHQNCuaUtuS7tuS6uu+8miJDb25nIExpdSI8Z25vY3VpbEBnbWFpbC5jb20+LCJZb25nIEN1aSI8
eW9uZ0Bjc25ldDEuY3MudHNpbmdodWEuZWR1LmNuPiwiWmlMb25nIExpdSI8bGl1emlsb25nODI2
NkAxMjYuY29tPiwiWmlMb25nIExpdSI8bGl1emlsb25nODI2NkAxMjYuY29tPiwiWW9uZyBDdWki
PHlvbmdAY3NuZXQxLmNzLnRzaW5naHVhLmVkdS5jbj4sIkNvbmcgTGl1Ijxnbm9jdWlsQGdtYWls
LmNvbT4NCuaKhOmAge+8mg0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1jdWktZGhj
LWRoY3A0bzYtYWN0aXZlLWxlYXNlcXVlcnktMDAudHh0IA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5
IHN1Ym1pdHRlZCBieSBaaUxvbmcgTGl1IGFuZCBwb3N0ZWQgdG8gdGhlIA0KSUVURiByZXBvc2l0
b3J5LiANCg0KTmFtZTogICAgICAgIGRyYWZ0LWN1aS1kaGMtZGhjcDRvNi1hY3RpdmUtbGVhc2Vx
dWVyeSANClJldmlzaW9uOiAgICAwMCANClRpdGxlOiAgICAgICAgREhDUDRvNiBBY3RpdmUgTGVh
c2VxdWVyeSANCkRvY3VtZW50IGRhdGU6ICAgIDIwMTQtMTAtMjYgDQpHcm91cDogICAgICAgIElu
ZGl2aWR1YWwgU3VibWlzc2lvbiANClBhZ2VzOiAgICAgICAgNyANClVSTDogICAgICAgICAgICBo
dHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1jdWktZGhjLWRoY3A0bzYt
YWN0aXZlLWxlYXNlcXVlcnktMDAudHh0IA0KU3RhdHVzOiAgICAgICAgIGh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWN1aS1kaGMtZGhjcDRvNi1hY3RpdmUtbGVhc2VxdWVy
eS8gDQpIdG1saXplZDogICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtY3Vp
LWRoYy1kaGNwNG82LWFjdGl2ZS1sZWFzZXF1ZXJ5LTAwIA0KDQoNCkFic3RyYWN0OiANCiAgIEFz
IG5ldHdvcmtzIG1pZ3JhdGUgdG93YXJkcyBJUHY2LCBzb21lIGVudGl0aWVzIHN0aWxsIGhhdmUg
dGhlIA0KICAgcmVxdWlyZW1lbnQgZm9yIElQdjQgY29uZmlndXJhdGlvbi4gIERIQ1B2NCBvdmVy
IERIQ1B2NiBbUkZDNzM0MV0gDQogICBwcm92aWRlcyBhIG1lY2hhbmlzbSBmb3Igb2J0YWluaW5n
IElQdjQgY29uZmlndXJhdGlvbiBpbmZvcm1hdGlvbiANCiAgIGR5bmFtaWNhbGx5IGluIElQdjYg
bmV0d29ya3MuICBESENQdjQvREhDUHY2IEFjdGl2ZSBMZWFzZXF1ZXJ5IGFsbG93cyANCiAgIGEg
Y2xpZW50IHRvIGdldCByZWFsLXRpbWUgREhDUCBhZGRyZXNzIGJpbmRpbmcgaW5mb3JtYXRpb24g
ZGF0YSB2aWEgDQogICBUQ1AuICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhbiBleHRlbnNpb24g
b2YgREhDUHY2IEFjdGl2ZSANCiAgIExlYXNlcXVlcnkgdG8gcHJvdmlkZSBhbiBtZWNoYW5pc20g
dG8gZ2V0dGluZyByZWFsLXRpbWUgREhDUHY0IG92ZXIgDQogICBESENQdjYgbGVhc2UgaW5mb3Jt
YXRpb24uIA0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClBsZWFzZSBub3RlIHRo
YXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1p
c3Npb24gDQp1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxl
IGF0IHRvb2xzLmlldGYub3JnLiANCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQg
--__=_Part_Boundary_006_027835.001427
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0
Zi04IiBodHRwLWVxdWl2PWNvbnRlbnQtdHlwZT4NCjxNRVRBIG5hbWU9R0VORVJBVE9SIGNvbnRl
bnQ9Ik1TSFRNTCAxMS4wMC45NjAwLjE3MzQ0Ij48IS0tIGZsYXNobWFpbCBzdHlsZSBiZWdpbiAt
LT4NCjxTVFlMRSB0eXBlPXRleHQvY3NzPgpib2R5IHtib3JkZXItd2lkdGg6MDttYXJnaW46MH0K
aW1nIHtib3JkZXI6MDttYXJnaW46MDtwYWRkaW5nOjB9CjwvU1RZTEU+DQo8QkFTRSB0YXJnZXQ9
X2JsYW5rPjwhLS0gZmxhc2htYWlsIHN0eWxlIGVuZCAtLT48L0hFQUQ+DQo8Qk9EWSANCnN0eWxl
PSJCT1JERVItTEVGVC1XSURUSDogMHB4OyBGT05ULVNJWkU6IDEwLjVwdDsgRk9OVC1GQU1JTFk6
IOW+rui9r+mbhem7kTsgQk9SREVSLVJJR0hULVdJRFRIOiAwcHg7IEJPUkRFUi1CT1RUT00tV0lE
VEg6IDBweDsgQ09MT1I6ICMwMDAwMDA7IE1BUkdJTjogMTJweDsgTElORS1IRUlHSFQ6IDEuNTsg
Qk9SREVSLVRPUC1XSURUSDogMHB4IiANCm1hcmdpbndpZHRoPSIwIiBtYXJnaW5oZWlnaHQ9IjAi
Pg0KPERJVj5IaSBhbGwsPC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyBXZSBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQgDQphYm91dCBESENQ
NG82IEFjdGl2ZSBMZWFzZXF1ZXJ5LiBJdCBleHRlbmRzIHRoZSBESENQdjYgQWN0aXZlIExlYXNl
cXVlcnkgdG8gDQpwcm92aWRlIGFuIG1lY2hhbmlzbSB0byBnZXR0aW5nIHJlYWwtdGltZSBESENQ
djQgb3ZlciBESENQdjYgbGVhc2UgDQppbmZvcm1hdGlvbihESENQdjQgbGVhc2UgYW5kIHJlbGF0
ZWQgREhDUHY2IGluZm9ybWF0aW9uKS4gSXQgY2FuIGJlIHVzZWQgaW4gDQpMaWdodHdlaWdodCA0
b3ZlcjYgZHluYW1pYyBwcm92aXNpb25pbmcmbmJzcDt0aGF0IGx3QUZUUiBjYW4gZ2V0IGx3QjRz
JyBESENQdjQgDQpvdmVyIERIQ1B2NiBsZWFzZSBpbmZvcm1hdGlvbiBmb3IgbWFwcGluZyB0YWJs
ZS48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPg0KPERJViBzdHlsZT0iRk9OVC1TSVpF
OiAxNHB4OyBGT05ULUZBTUlMWTogYXJpYWwsc2Fucy1zZXJpZiI+PFNQQU4gDQpzdHlsZT0iRk9O
VC1TSVpFOiAxZW07IENPTE9SOiByZ2IoMCwwLDApIj5QbGVhc2UgY291bGQgeW91IHJldmlldyB0
aGUgZHJhZnQgYW5kIA0KYW55IGNvbW1lbnRzIGFyZSBtb3JlIHRoYW4gd2VsY29tZS48L1NQQU4+
PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE0cHg7IEZPTlQtRkFNSUxZOiBhcmlhbCxz
YW5zLXNlcmlmIj48U1BBTiANCnN0eWxlPSJGT05ULVNJWkU6IDFlbTsgQ09MT1I6IHJnYigwLDAs
MCkiPjxCUj48L1NQQU4+PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE0cHg7IEZPTlQt
RkFNSUxZOiBhcmlhbCxzYW5zLXNlcmlmIj48U1BBTiANCnN0eWxlPSJGT05ULVNJWkU6IDFlbTsg
Q09MT1I6IHJnYigwLDAsMCkiPkJlc3QgUmVnYXJkcyw8L1NQQU4+PC9ESVY+DQo8RElWIHN0eWxl
PSJGT05ULVNJWkU6IDE0cHg7IEZPTlQtRkFNSUxZOiBhcmlhbCxzYW5zLXNlcmlmIj48U1BBTiAN
CnN0eWxlPSJGT05ULVNJWkU6IDFlbTsgQ09MT1I6IHJnYigwLDAsMCkiPjwvU1BBTj4mbmJzcDs8
L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtU0laRTogMTRweDsgRk9OVC1GQU1JTFk6IGFyaWFsLHNh
bnMtc2VyaWYiPjxTUEFOIA0Kc3R5bGU9IkZPTlQtU0laRTogMWVtOyBDT0xPUjogcmdiKDAsMCww
KSI+Wmlsb25nPC9TUEFOPjwvRElWPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVYgc3R5
bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IFZlcmRhbmE7IENPTE9SOiAjYzBjMGMw
IiANCmFsaWduPWxlZnQ+MjAxNC0xMC0yOCANCjxIUiBpZD1TaWduTmFtZUhSIA0Kc3R5bGU9IkJP
UkRFUi1UT1A6ICNjMGMwYzAgMXB4IHNvbGlkOyBIRUlHSFQ6IDFweDsgQk9SREVSLVJJR0hUOiAw
cHg7IFdJRFRIOiAxMjJweDsgQk9SREVSLUJPVFRPTTogMHB4OyBCT1JERVItTEVGVDogMHB4IiAN
CmFsaWduPWxlZnQ+DQo8U1BBTiBpZD1fRmxhc2hTaWduTmFtZT5saXV6aWxvbmc4MjY2PC9TUEFO
PiA8L0RJVj4NCjxIUiANCnN0eWxlPSJCT1JERVItVE9QOiAjYzBjMGMwIDFweCBzb2xpZDsgSEVJ
R0hUOiAxcHg7IEJPUkRFUi1SSUdIVDogMHB4OyBCT1JERVItQk9UVE9NOiAwcHg7IEJPUkRFUi1M
RUZUOiAwcHgiPg0KDQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBW
ZXJkYW5hIj4NCjxESVY+PFNUUk9ORz7lj5Hku7bkurrvvJo8L1NUUk9ORz5pbnRlcm5ldC1kcmFm
dHNAaWV0Zi5vcmc8L0RJVj4NCjxESVY+PFNUUk9ORz7lj5HpgIHml7bpl7TvvJo8L1NUUk9ORz4y
MDE0LTEwLTI3Jm5ic3A7MjE6NTE8L0RJVj4NCjxESVY+PFNUUk9ORz7kuLvpopjvvJo8L1NUUk9O
Rz5OZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIA0KZHJhZnQtY3VpLWRoYy1kaGNwNG82LWFj
dGl2ZS1sZWFzZXF1ZXJ5LTAwLnR4dDwvRElWPg0KPERJVj48U1RST05HPuaUtuS7tuS6uu+8mjwv
U1RST05HPiJDb25nIExpdSImbHQ7Z25vY3VpbEBnbWFpbC5jb20mZ3Q7LCJZb25nIA0KQ3VpIiZs
dDt5b25nQGNzbmV0MS5jcy50c2luZ2h1YS5lZHUuY24mZ3Q7LCJaaUxvbmcgDQpMaXUiJmx0O2xp
dXppbG9uZzgyNjZAMTI2LmNvbSZndDssIlppTG9uZyANCkxpdSImbHQ7bGl1emlsb25nODI2NkAx
MjYuY29tJmd0OywiWW9uZyANCkN1aSImbHQ7eW9uZ0Bjc25ldDEuY3MudHNpbmdodWEuZWR1LmNu
Jmd0OywiQ29uZyANCkxpdSImbHQ7Z25vY3VpbEBnbWFpbC5jb20mZ3Q7PC9ESVY+DQo8RElWPjxT
VFJPTkc+5oqE6YCB77yaPC9TVFJPTkc+PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj4N
CjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPkEmbmJzcDtuZXcmbmJzcDt2ZXJzaW9uJm5ic3A7b2Ym
bmJzcDtJLUQsJm5ic3A7ZHJhZnQtY3VpLWRoYy1kaGNwNG82LWFjdGl2ZS1sZWFzZXF1ZXJ5LTAw
LnR4dCZuYnNwOzwvRElWPg0KPERJVj5oYXMmbmJzcDtiZWVuJm5ic3A7c3VjY2Vzc2Z1bGx5Jm5i
c3A7c3VibWl0dGVkJm5ic3A7YnkmbmJzcDtaaUxvbmcmbmJzcDtMaXUmbmJzcDthbmQmbmJzcDtw
b3N0ZWQmbmJzcDt0byZuYnNwO3RoZSZuYnNwOzwvRElWPg0KPERJVj5JRVRGJm5ic3A7cmVwb3Np
dG9yeS4mbmJzcDs8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPk5hbWU6Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ZHJhZnQtY3VpLWRoYy1kaGNw
NG82LWFjdGl2ZS1sZWFzZXF1ZXJ5Jm5ic3A7PC9ESVY+DQo8RElWPlJldmlzaW9uOiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOzAwJm5ic3A7PC9ESVY+DQo8RElWPlRpdGxlOiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0RIQ1A0bzYmbmJzcDtBY3RpdmUmbmJz
cDtMZWFzZXF1ZXJ5Jm5ic3A7PC9ESVY+DQo8RElWPkRvY3VtZW50Jm5ic3A7ZGF0ZTombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsyMDE0LTEwLTI2Jm5ic3A7PC9ESVY+DQo8RElWPkdyb3VwOiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0luZGl2aWR1YWwmbmJz
cDtTdWJtaXNzaW9uJm5ic3A7PC9ESVY+DQo8RElWPlBhZ2VzOiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzcmbmJzcDs8L0RJVj4NCjxESVY+VVJMOiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwO2h0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWN1aS1k
aGMtZGhjcDRvNi1hY3RpdmUtbGVhc2VxdWVyeS0wMC50eHQmbmJzcDs8L0RJVj4NCjxESVY+U3Rh
dHVzOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
O2h0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWN1aS1kaGMtZGhjcDRvNi1h
Y3RpdmUtbGVhc2VxdWVyeS8mbmJzcDs8L0RJVj4NCjxESVY+SHRtbGl6ZWQ6Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtY3VpLWRoYy1kaGNwNG82LWFjdGl2ZS1sZWFzZXF1ZXJ5LTAwJm5ic3A7PC9ESVY+DQo8
RElWPiZuYnNwOzwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+QWJzdHJhY3Q6Jm5ic3A7
PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwO0FzJm5ic3A7bmV0d29ya3MmbmJzcDttaWdy
YXRlJm5ic3A7dG93YXJkcyZuYnNwO0lQdjYsJm5ic3A7c29tZSZuYnNwO2VudGl0aWVzJm5ic3A7
c3RpbGwmbmJzcDtoYXZlJm5ic3A7dGhlJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZu
YnNwO3JlcXVpcmVtZW50Jm5ic3A7Zm9yJm5ic3A7SVB2NCZuYnNwO2NvbmZpZ3VyYXRpb24uJm5i
c3A7Jm5ic3A7REhDUHY0Jm5ic3A7b3ZlciZuYnNwO0RIQ1B2NiZuYnNwO1tSRkM3MzQxXSZuYnNw
OzwvRElWPg0KPERJVj4mbmJzcDsmbmJzcDsmbmJzcDtwcm92aWRlcyZuYnNwO2EmbmJzcDttZWNo
YW5pc20mbmJzcDtmb3ImbmJzcDtvYnRhaW5pbmcmbmJzcDtJUHY0Jm5ic3A7Y29uZmlndXJhdGlv
biZuYnNwO2luZm9ybWF0aW9uJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwO2R5
bmFtaWNhbGx5Jm5ic3A7aW4mbmJzcDtJUHY2Jm5ic3A7bmV0d29ya3MuJm5ic3A7Jm5ic3A7REhD
UHY0L0RIQ1B2NiZuYnNwO0FjdGl2ZSZuYnNwO0xlYXNlcXVlcnkmbmJzcDthbGxvd3MmbmJzcDs8
L0RJVj4NCjxESVY+Jm5ic3A7Jm5ic3A7Jm5ic3A7YSZuYnNwO2NsaWVudCZuYnNwO3RvJm5ic3A7
Z2V0Jm5ic3A7cmVhbC10aW1lJm5ic3A7REhDUCZuYnNwO2FkZHJlc3MmbmJzcDtiaW5kaW5nJm5i
c3A7aW5mb3JtYXRpb24mbmJzcDtkYXRhJm5ic3A7dmlhJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNw
OyZuYnNwOyZuYnNwO1RDUC4mbmJzcDsmbmJzcDtUaGlzJm5ic3A7ZG9jdW1lbnQmbmJzcDtkZXNj
cmliZXMmbmJzcDthbiZuYnNwO2V4dGVuc2lvbiZuYnNwO29mJm5ic3A7REhDUHY2Jm5ic3A7QWN0
aXZlJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwO0xlYXNlcXVlcnkmbmJzcDt0
byZuYnNwO3Byb3ZpZGUmbmJzcDthbiZuYnNwO21lY2hhbmlzbSZuYnNwO3RvJm5ic3A7Z2V0dGlu
ZyZuYnNwO3JlYWwtdGltZSZuYnNwO0RIQ1B2NCZuYnNwO292ZXImbmJzcDs8L0RJVj4NCjxESVY+
Jm5ic3A7Jm5ic3A7Jm5ic3A7REhDUHY2Jm5ic3A7bGVhc2UmbmJzcDtpbmZvcm1hdGlvbi4mbmJz
cDs8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOzwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+Jm5ic3A7
PC9ESVY+DQo8RElWPlBsZWFzZSZuYnNwO25vdGUmbmJzcDt0aGF0Jm5ic3A7aXQmbmJzcDttYXkm
bmJzcDt0YWtlJm5ic3A7YSZuYnNwO2NvdXBsZSZuYnNwO29mJm5ic3A7bWludXRlcyZuYnNwO2Zy
b20mbmJzcDt0aGUmbmJzcDt0aW1lJm5ic3A7b2YmbmJzcDtzdWJtaXNzaW9uJm5ic3A7PC9ESVY+
DQo8RElWPnVudGlsJm5ic3A7dGhlJm5ic3A7aHRtbGl6ZWQmbmJzcDt2ZXJzaW9uJm5ic3A7YW5k
Jm5ic3A7ZGlmZiZuYnNwO2FyZSZuYnNwO2F2YWlsYWJsZSZuYnNwO2F0Jm5ic3A7dG9vbHMuaWV0
Zi5vcmcuJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5UaGUmbmJzcDtJRVRG
Jm5ic3A7U2VjcmV0YXJpYXQmbmJzcDs8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+PC9ESVY+PC9E
SVY+PC9CT0RZPjwvSFRNTD4=
--__=_Part_Boundary_006_027835.001427--


From liuzilong8266@126.com  Mon Oct 27 22:19:20 2014
Return-Path: <liuzilong8266@126.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C32D31A1B01 for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 22:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.709
X-Spam-Level: 
X-Spam-Status: No, score=0.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_MISSP_XPRIO=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, RELAY_IS_220=2.118, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 AiIwo85R2iWH for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 22:19:19 -0700 (PDT)
Received: from m15-233.126.com (m15-233.126.com [220.181.15.233]) by ietfa.amsl.com (Postfix) with ESMTP id 791371A0382 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 22:19:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=126.com; s=s110527; h=Date:From:Message-ID:Subject:MIME-Version; bh=bbeFu ZtXQtofIyEKI1tt4ZaEbiWby8bTYpDHrO5FM0c=; b=V2Hq9iq2bFuEwjMb8r1l2 jzHSvpBE5XrkZ1SZTtQrNG0+ZCxphFsCOjuG8I9gDsO1Wc9AMJT0p1dMf0imc/9q OP95bRVP6aQmEi98Q0+G/su8XlFRcJYcN6llFubeByVvIo8GD7PdK9dQRnRRlF9y pFFXmiAtCCN6aDp8Rziun8=
Received: from liuzilong8266$126.com ( [166.111.68.231] ) by ajax-webmail-sdy6 (Coremail) ; Tue, 28 Oct 2014 13:19:05 +0800 (GMT+08:00)
Date: Tue, 28 Oct 2014 13:18:37 +0800
From: "liuzilong8266"<liuzilong8266@126.com>
To: "dhcwg"<dhcwg@ietf.org>
Message-ID: <5452d077.321e.149553175df.Coremail.liuzilong8266@126.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="__=_Part_Boundary_004_032518.027148"
X-Mailer: NetEase Flash Mail 2.4.0.11
X-Priority: 3 (Normal)
X-Originating-IP: [166.111.68.231]
X-CM-TRANSID: 38qowGBZAEJKJ09Uu5YPAA--.3198W
X-CM-SenderInfo: xolx6xporqwmqswwqiyswou0bp/1tbi7hUzMU0va2h1ZAACsL
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/GRiUBmS97RQlPu3q4kRERTW_Gng
X-Mailman-Approved-At: Tue, 28 Oct 2014 04:07:14 -0700
Cc: =?UTF-8?B?546L5piK?= <wangh13@mails.tsinghua.edu.cn>, =?UTF-8?B?5p2O5aSp57+U?= <1515452578@qq.com>, =?UTF-8?B?5bSU5YuH?= <cuiyong@tsinghua.edu.cn>, =?UTF-8?B?5p2O5Li95aeX?= <lilishan9248@126.com>, =?UTF-8?B?5a2Z55Cq?= <sunqibupt@gmail.com>
Subject: [dhcwg] Fw: New Version Notification for draft-cui-dhc-dhcp4o6-active-leasequery-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 28 Oct 2014 05:23:50 -0000
X-List-Received-Date: Tue, 28 Oct 2014 05:23:50 -0000

--__=_Part_Boundary_004_032518.027148
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

SGkgYWxsLA0KICAgICAgICAgV2Ugc3VibWl0dGVkIGEgbmV3IGRyYWZ0IGFib3V0IERIQ1A0bzYg
QWN0aXZlIExlYXNlcXVlcnkuIEl0IGV4dGVuZHMgdGhlIERIQ1B2NiBBY3RpdmUgTGVhc2VxdWVy
eSB0byBwcm92aWRlIGFuIG1lY2hhbmlzbSB0byBnZXR0aW5nIHJlYWwtdGltZSBESENQdjQgb3Zl
ciBESENQdjYgbGVhc2UgaW5mb3JtYXRpb24oREhDUHY0IGxlYXNlIGFuZCByZWxhdGVkIERIQ1B2
NiBpbmZvcm1hdGlvbikuIEl0IGNhbiBiZSB1c2VkIGluIExpZ2h0d2VpZ2h0IDRvdmVyNiBkeW5h
bWljIHByb3Zpc2lvbmluZyB0aGF0IGx3QUZUUiBjYW4gZ2V0IGx3QjRzJyBESENQdjQgb3ZlciBE
SENQdjYgbGVhc2UgaW5mb3JtYXRpb24gZm9yIG1hcHBpbmcgdGFibGUuDQoNClBsZWFzZSBjb3Vs
ZCB5b3UgcmV2aWV3IHRoZSBkcmFmdCBhbmQgYW55IGNvbW1lbnRzIGFyZSBtb3JlIHRoYW4gd2Vs
Y29tZS4NCg0KDQpCZXN0IFJlZ2FyZHMsDQoNClppbG9uZw0KDQoyMDE0LTEwLTI4IA0KDQpsaXV6
aWxvbmc4MjY2IA0KDQoNCg0K5Y+R5Lu25Lq677yaaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnDQrl
j5HpgIHml7bpl7TvvJoyMDE0LTEwLTI3IDIxOjUxDQrkuLvpopjvvJpOZXcgVmVyc2lvbiBOb3Rp
ZmljYXRpb24gZm9yIGRyYWZ0LWN1aS1kaGMtZGhjcDRvNi1hY3RpdmUtbGVhc2VxdWVyeS0wMC50
eHQNCuaUtuS7tuS6uu+8miJDb25nIExpdSI8Z25vY3VpbEBnbWFpbC5jb20+LCJZb25nIEN1aSI8
eW9uZ0Bjc25ldDEuY3MudHNpbmdodWEuZWR1LmNuPiwiWmlMb25nIExpdSI8bGl1emlsb25nODI2
NkAxMjYuY29tPiwiWmlMb25nIExpdSI8bGl1emlsb25nODI2NkAxMjYuY29tPiwiWW9uZyBDdWki
PHlvbmdAY3NuZXQxLmNzLnRzaW5naHVhLmVkdS5jbj4sIkNvbmcgTGl1Ijxnbm9jdWlsQGdtYWls
LmNvbT4NCuaKhOmAge+8mg0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1jdWktZGhj
LWRoY3A0bzYtYWN0aXZlLWxlYXNlcXVlcnktMDAudHh0IA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5
IHN1Ym1pdHRlZCBieSBaaUxvbmcgTGl1IGFuZCBwb3N0ZWQgdG8gdGhlIA0KSUVURiByZXBvc2l0
b3J5LiANCg0KTmFtZTogICAgICAgIGRyYWZ0LWN1aS1kaGMtZGhjcDRvNi1hY3RpdmUtbGVhc2Vx
dWVyeSANClJldmlzaW9uOiAgICAwMCANClRpdGxlOiAgICAgICAgREhDUDRvNiBBY3RpdmUgTGVh
c2VxdWVyeSANCkRvY3VtZW50IGRhdGU6ICAgIDIwMTQtMTAtMjYgDQpHcm91cDogICAgICAgIElu
ZGl2aWR1YWwgU3VibWlzc2lvbiANClBhZ2VzOiAgICAgICAgNyANClVSTDogICAgICAgICAgICBo
dHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1jdWktZGhjLWRoY3A0bzYt
YWN0aXZlLWxlYXNlcXVlcnktMDAudHh0IA0KU3RhdHVzOiAgICAgICAgIGh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWN1aS1kaGMtZGhjcDRvNi1hY3RpdmUtbGVhc2VxdWVy
eS8gDQpIdG1saXplZDogICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtY3Vp
LWRoYy1kaGNwNG82LWFjdGl2ZS1sZWFzZXF1ZXJ5LTAwIA0KDQoNCkFic3RyYWN0OiANCiAgIEFz
IG5ldHdvcmtzIG1pZ3JhdGUgdG93YXJkcyBJUHY2LCBzb21lIGVudGl0aWVzIHN0aWxsIGhhdmUg
dGhlIA0KICAgcmVxdWlyZW1lbnQgZm9yIElQdjQgY29uZmlndXJhdGlvbi4gIERIQ1B2NCBvdmVy
IERIQ1B2NiBbUkZDNzM0MV0gDQogICBwcm92aWRlcyBhIG1lY2hhbmlzbSBmb3Igb2J0YWluaW5n
IElQdjQgY29uZmlndXJhdGlvbiBpbmZvcm1hdGlvbiANCiAgIGR5bmFtaWNhbGx5IGluIElQdjYg
bmV0d29ya3MuICBESENQdjQvREhDUHY2IEFjdGl2ZSBMZWFzZXF1ZXJ5IGFsbG93cyANCiAgIGEg
Y2xpZW50IHRvIGdldCByZWFsLXRpbWUgREhDUCBhZGRyZXNzIGJpbmRpbmcgaW5mb3JtYXRpb24g
ZGF0YSB2aWEgDQogICBUQ1AuICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhbiBleHRlbnNpb24g
b2YgREhDUHY2IEFjdGl2ZSANCiAgIExlYXNlcXVlcnkgdG8gcHJvdmlkZSBhbiBtZWNoYW5pc20g
dG8gZ2V0dGluZyByZWFsLXRpbWUgREhDUHY0IG92ZXIgDQogICBESENQdjYgbGVhc2UgaW5mb3Jt
YXRpb24uIA0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClBsZWFzZSBub3RlIHRo
YXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1p
c3Npb24gDQp1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxl
IGF0IHRvb2xzLmlldGYub3JnLiANCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQg
--__=_Part_Boundary_004_032518.027148
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0
Zi04IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT48IS0tIGZsYXNobWFpbCBzdHlsZSBiZWdpbiAt
LT4NCjxTVFlMRSB0eXBlPXRleHQvY3NzPgpib2R5IHtib3JkZXItd2lkdGg6MDttYXJnaW46MH0K
aW1nIHtib3JkZXI6MDttYXJnaW46MDtwYWRkaW5nOjB9CjwvU1RZTEU+DQo8QkFTRSB0YXJnZXQ9
X2JsYW5rPjwhLS0gZmxhc2htYWlsIHN0eWxlIGVuZCAtLT4NCjxNRVRBIG5hbWU9R0VORVJBVE9S
IGNvbnRlbnQ9Ik1TSFRNTCAxMS4wMC45NjAwLjE3MzQ0Ij48L0hFQUQ+DQo8Qk9EWSANCnN0eWxl
PSJCT1JERVItTEVGVC1XSURUSDogMHB4OyBGT05ULVNJWkU6IDEwLjVwdDsgRk9OVC1GQU1JTFk6
IOW+rui9r+mbhem7kTsgQk9SREVSLVJJR0hULVdJRFRIOiAwcHg7IEJPUkRFUi1CT1RUT00tV0lE
VEg6IDBweDsgQ09MT1I6ICMwMDAwMDA7IE1BUkdJTjogMTJweDsgTElORS1IRUlHSFQ6IDEuNTsg
Qk9SREVSLVRPUC1XSURUSDogMHB4IiANCm1hcmdpbmhlaWdodD0iMCIgbWFyZ2lud2lkdGg9IjAi
Pg0KPERJVj5IaSBhbGwsPC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyBXZSBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQgDQphYm91dCBESENQ
NG82IEFjdGl2ZSBMZWFzZXF1ZXJ5LiBJdCBleHRlbmRzIHRoZSBESENQdjYgQWN0aXZlIExlYXNl
cXVlcnkgdG8gDQpwcm92aWRlIGFuIG1lY2hhbmlzbSB0byBnZXR0aW5nIHJlYWwtdGltZSBESENQ
djQgb3ZlciBESENQdjYgbGVhc2UgDQppbmZvcm1hdGlvbihESENQdjQgbGVhc2UgYW5kIHJlbGF0
ZWQgREhDUHY2IGluZm9ybWF0aW9uKS4gSXQgY2FuIGJlIHVzZWQgaW4gDQpMaWdodHdlaWdodCA0
b3ZlcjYgZHluYW1pYyBwcm92aXNpb25pbmcmbmJzcDt0aGF0IGx3QUZUUiBjYW4gZ2V0IGx3QjRz
JyBESENQdjQgDQpvdmVyIERIQ1B2NiBsZWFzZSBpbmZvcm1hdGlvbiBmb3IgbWFwcGluZyB0YWJs
ZS48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPg0KPERJViBzdHlsZT0iRk9OVC1TSVpF
OiAxNHB4OyBGT05ULUZBTUlMWTogYXJpYWwsc2Fucy1zZXJpZiI+PFNQQU4gDQpzdHlsZT0iRk9O
VC1TSVpFOiAxZW07IENPTE9SOiByZ2IoMCwwLDApIj5QbGVhc2UgY291bGQgeW91IHJldmlldyB0
aGUgZHJhZnQgYW5kIA0KYW55IGNvbW1lbnRzIGFyZSBtb3JlIHRoYW4gd2VsY29tZS48L1NQQU4+
PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE0cHg7IEZPTlQtRkFNSUxZOiBhcmlhbCxz
YW5zLXNlcmlmIj48U1BBTiANCnN0eWxlPSJGT05ULVNJWkU6IDFlbTsgQ09MT1I6IHJnYigwLDAs
MCkiPjxCUj48L1NQQU4+PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDE0cHg7IEZPTlQt
RkFNSUxZOiBhcmlhbCxzYW5zLXNlcmlmIj48U1BBTiANCnN0eWxlPSJGT05ULVNJWkU6IDFlbTsg
Q09MT1I6IHJnYigwLDAsMCkiPkJlc3QgUmVnYXJkcyw8L1NQQU4+PC9ESVY+DQo8RElWIHN0eWxl
PSJGT05ULVNJWkU6IDE0cHg7IEZPTlQtRkFNSUxZOiBhcmlhbCxzYW5zLXNlcmlmIj48U1BBTiAN
CnN0eWxlPSJGT05ULVNJWkU6IDFlbTsgQ09MT1I6IHJnYigwLDAsMCkiPjwvU1BBTj4mbmJzcDs8
L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtU0laRTogMTRweDsgRk9OVC1GQU1JTFk6IGFyaWFsLHNh
bnMtc2VyaWYiPjxTUEFOIA0Kc3R5bGU9IkZPTlQtU0laRTogMWVtOyBDT0xPUjogcmdiKDAsMCww
KSI+Wmlsb25nPC9TUEFOPjwvRElWPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVYgc3R5
bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IFZlcmRhbmE7IENPTE9SOiAjYzBjMGMw
IiANCmFsaWduPWxlZnQ+MjAxNC0xMC0yOCANCjxIUiBpZD1TaWduTmFtZUhSIA0Kc3R5bGU9IkJP
UkRFUi1UT1A6ICNjMGMwYzAgMXB4IHNvbGlkOyBIRUlHSFQ6IDFweDsgQk9SREVSLVJJR0hUOiAw
cHg7IFdJRFRIOiAxMjJweDsgQk9SREVSLUJPVFRPTTogMHB4OyBCT1JERVItTEVGVDogMHB4IiAN
CmFsaWduPWxlZnQ+DQo8U1BBTiBpZD1fRmxhc2hTaWduTmFtZT5saXV6aWxvbmc4MjY2PC9TUEFO
PiA8L0RJVj4NCjxIUiANCnN0eWxlPSJCT1JERVItVE9QOiAjYzBjMGMwIDFweCBzb2xpZDsgSEVJ
R0hUOiAxcHg7IEJPUkRFUi1SSUdIVDogMHB4OyBCT1JERVItQk9UVE9NOiAwcHg7IEJPUkRFUi1M
RUZUOiAwcHgiPg0KDQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBW
ZXJkYW5hIj4NCjxESVY+PFNUUk9ORz7lj5Hku7bkurrvvJo8L1NUUk9ORz5pbnRlcm5ldC1kcmFm
dHNAaWV0Zi5vcmc8L0RJVj4NCjxESVY+PFNUUk9ORz7lj5HpgIHml7bpl7TvvJo8L1NUUk9ORz4y
MDE0LTEwLTI3Jm5ic3A7MjE6NTE8L0RJVj4NCjxESVY+PFNUUk9ORz7kuLvpopjvvJo8L1NUUk9O
Rz5OZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIA0KZHJhZnQtY3VpLWRoYy1kaGNwNG82LWFj
dGl2ZS1sZWFzZXF1ZXJ5LTAwLnR4dDwvRElWPg0KPERJVj48U1RST05HPuaUtuS7tuS6uu+8mjwv
U1RST05HPiJDb25nIExpdSImbHQ7Z25vY3VpbEBnbWFpbC5jb20mZ3Q7LCJZb25nIA0KQ3VpIiZs
dDt5b25nQGNzbmV0MS5jcy50c2luZ2h1YS5lZHUuY24mZ3Q7LCJaaUxvbmcgDQpMaXUiJmx0O2xp
dXppbG9uZzgyNjZAMTI2LmNvbSZndDssIlppTG9uZyANCkxpdSImbHQ7bGl1emlsb25nODI2NkAx
MjYuY29tJmd0OywiWW9uZyANCkN1aSImbHQ7eW9uZ0Bjc25ldDEuY3MudHNpbmdodWEuZWR1LmNu
Jmd0OywiQ29uZyANCkxpdSImbHQ7Z25vY3VpbEBnbWFpbC5jb20mZ3Q7PC9ESVY+DQo8RElWPjxT
VFJPTkc+5oqE6YCB77yaPC9TVFJPTkc+PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj4N
CjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPkEmbmJzcDtuZXcmbmJzcDt2ZXJzaW9uJm5ic3A7b2Ym
bmJzcDtJLUQsJm5ic3A7ZHJhZnQtY3VpLWRoYy1kaGNwNG82LWFjdGl2ZS1sZWFzZXF1ZXJ5LTAw
LnR4dCZuYnNwOzwvRElWPg0KPERJVj5oYXMmbmJzcDtiZWVuJm5ic3A7c3VjY2Vzc2Z1bGx5Jm5i
c3A7c3VibWl0dGVkJm5ic3A7YnkmbmJzcDtaaUxvbmcmbmJzcDtMaXUmbmJzcDthbmQmbmJzcDtw
b3N0ZWQmbmJzcDt0byZuYnNwO3RoZSZuYnNwOzwvRElWPg0KPERJVj5JRVRGJm5ic3A7cmVwb3Np
dG9yeS4mbmJzcDs8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPk5hbWU6Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ZHJhZnQtY3VpLWRoYy1kaGNw
NG82LWFjdGl2ZS1sZWFzZXF1ZXJ5Jm5ic3A7PC9ESVY+DQo8RElWPlJldmlzaW9uOiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOzAwJm5ic3A7PC9ESVY+DQo8RElWPlRpdGxlOiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0RIQ1A0bzYmbmJzcDtBY3RpdmUmbmJz
cDtMZWFzZXF1ZXJ5Jm5ic3A7PC9ESVY+DQo8RElWPkRvY3VtZW50Jm5ic3A7ZGF0ZTombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsyMDE0LTEwLTI2Jm5ic3A7PC9ESVY+DQo8RElWPkdyb3VwOiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0luZGl2aWR1YWwmbmJz
cDtTdWJtaXNzaW9uJm5ic3A7PC9ESVY+DQo8RElWPlBhZ2VzOiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzcmbmJzcDs8L0RJVj4NCjxESVY+VVJMOiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwO2h0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWN1aS1k
aGMtZGhjcDRvNi1hY3RpdmUtbGVhc2VxdWVyeS0wMC50eHQmbmJzcDs8L0RJVj4NCjxESVY+U3Rh
dHVzOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
O2h0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWN1aS1kaGMtZGhjcDRvNi1h
Y3RpdmUtbGVhc2VxdWVyeS8mbmJzcDs8L0RJVj4NCjxESVY+SHRtbGl6ZWQ6Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtY3VpLWRoYy1kaGNwNG82LWFjdGl2ZS1sZWFzZXF1ZXJ5LTAwJm5ic3A7PC9ESVY+DQo8
RElWPiZuYnNwOzwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+QWJzdHJhY3Q6Jm5ic3A7
PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwO0FzJm5ic3A7bmV0d29ya3MmbmJzcDttaWdy
YXRlJm5ic3A7dG93YXJkcyZuYnNwO0lQdjYsJm5ic3A7c29tZSZuYnNwO2VudGl0aWVzJm5ic3A7
c3RpbGwmbmJzcDtoYXZlJm5ic3A7dGhlJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZu
YnNwO3JlcXVpcmVtZW50Jm5ic3A7Zm9yJm5ic3A7SVB2NCZuYnNwO2NvbmZpZ3VyYXRpb24uJm5i
c3A7Jm5ic3A7REhDUHY0Jm5ic3A7b3ZlciZuYnNwO0RIQ1B2NiZuYnNwO1tSRkM3MzQxXSZuYnNw
OzwvRElWPg0KPERJVj4mbmJzcDsmbmJzcDsmbmJzcDtwcm92aWRlcyZuYnNwO2EmbmJzcDttZWNo
YW5pc20mbmJzcDtmb3ImbmJzcDtvYnRhaW5pbmcmbmJzcDtJUHY0Jm5ic3A7Y29uZmlndXJhdGlv
biZuYnNwO2luZm9ybWF0aW9uJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwO2R5
bmFtaWNhbGx5Jm5ic3A7aW4mbmJzcDtJUHY2Jm5ic3A7bmV0d29ya3MuJm5ic3A7Jm5ic3A7REhD
UHY0L0RIQ1B2NiZuYnNwO0FjdGl2ZSZuYnNwO0xlYXNlcXVlcnkmbmJzcDthbGxvd3MmbmJzcDs8
L0RJVj4NCjxESVY+Jm5ic3A7Jm5ic3A7Jm5ic3A7YSZuYnNwO2NsaWVudCZuYnNwO3RvJm5ic3A7
Z2V0Jm5ic3A7cmVhbC10aW1lJm5ic3A7REhDUCZuYnNwO2FkZHJlc3MmbmJzcDtiaW5kaW5nJm5i
c3A7aW5mb3JtYXRpb24mbmJzcDtkYXRhJm5ic3A7dmlhJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNw
OyZuYnNwOyZuYnNwO1RDUC4mbmJzcDsmbmJzcDtUaGlzJm5ic3A7ZG9jdW1lbnQmbmJzcDtkZXNj
cmliZXMmbmJzcDthbiZuYnNwO2V4dGVuc2lvbiZuYnNwO29mJm5ic3A7REhDUHY2Jm5ic3A7QWN0
aXZlJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwO0xlYXNlcXVlcnkmbmJzcDt0
byZuYnNwO3Byb3ZpZGUmbmJzcDthbiZuYnNwO21lY2hhbmlzbSZuYnNwO3RvJm5ic3A7Z2V0dGlu
ZyZuYnNwO3JlYWwtdGltZSZuYnNwO0RIQ1B2NCZuYnNwO292ZXImbmJzcDs8L0RJVj4NCjxESVY+
Jm5ic3A7Jm5ic3A7Jm5ic3A7REhDUHY2Jm5ic3A7bGVhc2UmbmJzcDtpbmZvcm1hdGlvbi4mbmJz
cDs8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOzwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+Jm5ic3A7
PC9ESVY+DQo8RElWPlBsZWFzZSZuYnNwO25vdGUmbmJzcDt0aGF0Jm5ic3A7aXQmbmJzcDttYXkm
bmJzcDt0YWtlJm5ic3A7YSZuYnNwO2NvdXBsZSZuYnNwO29mJm5ic3A7bWludXRlcyZuYnNwO2Zy
b20mbmJzcDt0aGUmbmJzcDt0aW1lJm5ic3A7b2YmbmJzcDtzdWJtaXNzaW9uJm5ic3A7PC9ESVY+
DQo8RElWPnVudGlsJm5ic3A7dGhlJm5ic3A7aHRtbGl6ZWQmbmJzcDt2ZXJzaW9uJm5ic3A7YW5k
Jm5ic3A7ZGlmZiZuYnNwO2FyZSZuYnNwO2F2YWlsYWJsZSZuYnNwO2F0Jm5ic3A7dG9vbHMuaWV0
Zi5vcmcuJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5UaGUmbmJzcDtJRVRG
Jm5ic3A7U2VjcmV0YXJpYXQmbmJzcDs8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+PC9ESVY+PC9E
SVY+PC9CT0RZPjwvSFRNTD4=
--__=_Part_Boundary_004_032518.027148--


From nobody Tue Oct 28 07:56:45 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 333ED1A89E0 for <dhcwg@ietfa.amsl.com>; Tue, 28 Oct 2014 07:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 y-ORhO4_9raD for <dhcwg@ietfa.amsl.com>; Tue, 28 Oct 2014 07:56:42 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A923C1A8A27 for <dhcwg@ietf.org>; Tue, 28 Oct 2014 07:56:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s9SEugW5011066; Tue, 28 Oct 2014 07:56:42 -0700
Received: from XCH-BLV-508.nw.nos.boeing.com (xch-blv-508.nw.nos.boeing.com [130.247.25.198]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s9SEuag9010553 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 28 Oct 2014 07:56:37 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.66]) by XCH-BLV-508.nw.nos.boeing.com ([169.254.8.95]) with mapi id 14.03.0210.002; Tue, 28 Oct 2014 07:56:36 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3,	2014
Thread-Index: AQHP8r9eCYTydk8op0Cn7mdDfCs8pQ==
Date: Tue, 28 Oct 2014 14:56:35 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832D6E707@XCH-BLV-504.nw.nos.boeing.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com> <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com> <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/VuewKYWMND7VJBJT6oYBEEBWTJk
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 28 Oct 2014 14:56:44 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogU2hlbmcgSmlhbmcgW21h
aWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb21dDQo+IFNlbnQ6IE1vbmRheSwgT2N0b2JlciAyNywg
MjAxNCA3OjQ1IFBNDQo+IFRvOiBUZW1wbGluLCBGcmVkIEw7IEJlcm5pZSBWb2x6ICh2b2x6KTsg
ZGhjd2dAaWV0Zi5vcmcNCj4gQ2M6IFpoYW5nZGFjaGVuZyAoRGFjaGVuZykNCj4gU3ViamVjdDog
UkU6IFtkaGN3Z10gV0dMQyBmb3IgZHJhZnQtaWV0Zi1kaGMtc2VkaGNwdjYtMDQgLSBSZXNwb25k
IGJ5IE5vdiAzLCAyMDE0DQo+IA0KPiA+SSBhbSBxdWl0ZSBmaW5lIHdpdGggdGhlIENsaWVudCB0
cnVzdGluZyB0aGUgU2VydmVyIGJ5IGxlYXAgb2YgZmFpdGguIEluIHRoZSBvdGhlcg0KPiA+ZGly
ZWN0aW9uLCBJIG5lZWQgc29tZSB3YXkgZm9yIHRoZSBDbGllbnQgdG8gcHJvdmUgdG8gdGhlIFNl
cnZlciB0aGF0IGl0IGlzIHRoZQ0KPiA+YXV0aGVudGljIG93bmVyIG9mIHRoZSBjbGFpbWVkIENs
aWVudCBJRC4NCj4gPg0KPiA+RG9lcyB0aGlzIG5ldyBkb2N1bWVudCB2ZXJzaW9uIHByb3ZpZGUg
dGhhdD8NCj4gDQo+IEhpLCBGcmVkLA0KPiANCj4gVGhpcyB2ZXJzaW9uIGhhcyBwcm92aWRlZCBh
IGNlcnRpZmljYXRlLWJhc2VkIG1lY2hhbmlzbSBmb3IgdGhlIGNsaWVudCB0byBhdXRoZW50aWNh
dGVkIGJ5IHRoZSBzZXJ2ZXIuIEl0IGlzIGFzc3VtaW5nIHRoZSBjbGllbnQgaGFzIGENCj4gY2Vy
dGlmaWNhdGUgaG9ub3JlZCBieSB0aGUgc2VydmVyLg0KDQpSaWdodCwgSSBzYXcgdGhhdCBidXQg
aGVscCBtZSBvdXQgaGVyZS4gSWYgdGhlIGNsaWVudCBjbGFpbXMgYSBEVUlEIGlzIHRoZSBjZXJ0
aWZpY2F0ZQ0KcHJvb2YgZW5vdWdoIHRoYXQgdGhlIGNsaWVudCBpcyB0aGUgYXV0aG9yaXplZCBv
d25lciBvZiB0aGUgRFVJRD8NCg0KVGhhbmtzIC0gRnJlZA0KZnJlZC5sLnRlbXBsaW5AYm9laW5n
LmNvbQ0KDQo+IEJlc3QgcmVnYXJkcywNCj4gDQo+IFNoZW5nDQo+IA0KPiA+VGhhbmtzIC0gRnJl
ZA0KPiA+ZnJlZC5sLnRlbXBsaW5AYm9laW5nLmNvbQ0KPiA+DQo+ID4NCj4gPi0tLQ0KPiA+RnJv
bTogZGhjd2cgW21haWx0bzpkaGN3Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQmVy
bmllIFZvbHoNCj4gPih2b2x6KQ0KPiA+U2VudDogU3VuZGF5LCBPY3RvYmVyIDI2LCAyMDE0IDM6
MTEgUE0NCj4gPlRvOiBkaGN3Z0BpZXRmLm9yZw0KPiA+U3ViamVjdDogW2RoY3dnXSBXR0xDIGZv
ciBkcmFmdC1pZXRmLWRoYy1zZWRoY3B2Ni0wNCAtIFJlc3BvbmQgYnkgTm92IDMsDQo+ID4yMDE0
DQo+ID4NCj4gPkhpIGFsbCwNCj4gPg0KPiA+VGhpcyBtZXNzYWdlIHN0YXJ0cyB0aGUgKHNob3J0
KSBESEMgd29ya2luZyBncm91cCBsYXN0IGNhbGwgdG8gYWR2YW5jZQ0KPiA+IlNlY3VyZSBESENQ
djYiLCBkcmFmdC1pZXRmLWRoYy1zZWRoY3B2Ni0wNCwgZG9jdW1lbnQgYXMgYSBTdGFuZGFyZHMg
VHJhY2sNCj4gPihQcm9wb3NlZCBTdGFuZGFyZCkgUkZDLiBUaGUgYXV0aG9ycyBiZWxpZXZlIHRo
YXQgdGhpcyB2ZXJzaW9uIGlzIHJlYWR5LiBXZQ0KPiA+aGFkIGEgV0dMQyBlYXJsaWVyIChNYXkg
MjAxNCBmb3IgdGhlIC0wMiB2ZXJzaW9uKSBhbmQgdGhlcmUgd2VyZSBzb21lDQo+ID5jb21tZW50
cywgc28gdGhpcyBpcyBwcmltYXJpbHkgdG8gYXNzdXJlIHRoYXQgdGhvc2UgY29tbWVudHMgd2Vy
ZQ0KPiA+YWRkcmVzc2VkLg0KPiA+DQo+ID5UaGUgZHJhZnQgaXMgYXZhaWxhYmxlIGhlcmU6DQo+
ID5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWRoYy1zZWRoY3B2Ni0wNA0K
PiA+DQo+ID5QbGVhc2Ugc2VuZCB5b3VyIGNvbW1lbnRzIGJ5IE5vdmVtYmVyIDNyZCwgMjAxNC4g
SWYgeW91IGRvIG5vdCBmZWVsIHRoaXMNCj4gPmRvY3VtZW50IHNob3VsZCBhZHZhbmNlLCBwbGVh
c2Ugc3RhdGUgeW91ciByZWFzb25zIHdoeS4NCj4gPg0KPiA+VGhlcmUgYXJlIG5vIElQUiBjbGFp
bXMgcmVwb3J0ZWQgYXQgdGhpcyB0aW1lLg0KPiA+DQo+ID5Ub21layBpcyB0aGUgYXNzaWduZWQg
c2hlcGhlcmQgZm9yIHRoaXMgZG9jdW1lbnQuDQo+ID4NCj4gPi0gVG9tZWsgJiBCZXJuaWUNCj4g
Pg0KPiA+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4g
PmRoY3dnIG1haWxpbmcgbGlzdA0KPiA+ZGhjd2dAaWV0Zi5vcmcNCj4gPmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhjd2cNCg==


From nobody Tue Oct 28 14:15:28 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E2FA1AC44D for <dhcwg@ietfa.amsl.com>; Tue, 28 Oct 2014 14:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 GuLyFGmp0KZd for <dhcwg@ietfa.amsl.com>; Tue, 28 Oct 2014 14:15:20 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C65151ACFC1 for <dhcwg@ietf.org>; Tue, 28 Oct 2014 14:15:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18015; q=dns/txt; s=iport; t=1414530919; x=1415740519; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=mgC+L7gIha4cVvyHqd7+ceytda9iVLV3h3eVbZD0qVE=; b=gVa4VoX8PfrbVZYjx56hRgePebEFuLHiNsESFk/OJkzmmTDzb6COAPc/ Dzo7ODB8llSgJESbkbhivno5kWbhURR0TroQGI2xb5kDekhXAklPABIGZ 6LrKHcYEKC/X5Mq+nhQPjNrBlw+gw1o8deXhmXW29TE4Zg4AimubLqSDp Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0FAMIGUFStJV2T/2dsb2JhbABcgkhGVFgEzkKHTQKBIhYBAQEBAXILhAIBAQEELVwCAQgRAwEBAQsdBzIUCQgBAQQTCAGIOA3GWwEBAQEBAQEBAQEBAQEBAQEBAQEBAReQJxEBHyANCgGDLYEeBZILhEqIRINJihmHI4N4bAGBDjmBAwEBAQ
X-IronPort-AV: E=Sophos; i="5.04,805,1406592000"; d="scan'208,217"; a="91167335"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-4.cisco.com with ESMTP; 28 Oct 2014 21:15:18 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s9SLFIq8014219 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 28 Oct 2014 21:15:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0195.001; Tue, 28 Oct 2014 16:15:18 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: IETF-91 (Honolulu) DHC WG Agenda Items
Thread-Index: Ac/HkCLoS86rZHidSOuuk32ztFklWAh18mCQAmLylZA=
Date: Tue, 28 Oct 2014 21:15:17 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6FAD8D@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B67C40C@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6D174B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D174B@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.159]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B6FAD8Dxmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/-VYs-TnwURmg6LxBzcd6cgetdvI
Subject: Re: [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 28 Oct 2014 21:15:25 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B6FAD8Dxmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

A reminder that we're still looking for agenda items. Our current agenda sh=
ows us using only about half of the 150 minutes we have (though that may be=
 a good sign that the WGs workload is decreasing).

https://datatracker.ietf.org/meeting/91/agenda/dhc/


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Thursday, October 16, 2014 1:42 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items

Hi:

Per the preliminary agenda, we will be meeting on Thursday, November 13 fro=
m 1640-1910 HST.

We are collecting agenda items (see email below as what you should send us =
at dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org> to request t=
ime).

At present we have the following so far (this is subject to change):

DHC WG Agenda for IETF-91 (Honolulu)

Date: Thursday November 13, 1640-1910 HST, Kahili 1/2
Chairs: Tomek Mrugalski & Bernie Volz
Secretary: Sheng Jiang
Presentations materials: https://datatracker.ietf.org/meeting/91/materials.=
html#wg-dhc

1. Co-Chairs - Administrativia (Agenda Bashing, WG Status) - 10 minutes
2. Tomek Mrugalski, DHCPv6bis Update (draft-dhcwg-dhc-rfc3315bis) - 15 minu=
tes
3. Tomek Mrugalski, DHCP privacy considerations (draft TBD) - 20 minutes
4. Marcin Siodelski and Bernie Volz - draft-ietf-dhc-dhcpv6-stateful-issues=
 -15 minutes


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, September 03, 2014 12:01 PM
To: dhcwg@ietf.org
Subject: [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items

Hi:

While it is still 2 months away, we are starting to collect agenda items fo=
r IETF-91's DHC WG session.

Please send us (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org>=
) requests for sessions and include:

Name of session:
Name of draft(s):
Time requested:
Presenter name(s):
Brief description of what issues need discussing and what you hope to accom=
plish by presenting:

More details about the Honolulu IETF can be found at http://www.ietf.org/me=
eting/91/index.html.


-          Tomek & Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1B6FAD8Dxmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
code
	{mso-style-priority:99;
	font-family:"Courier New";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:125590465;
	mso-list-type:hybrid;
	mso-list-template-ids:-879992944 -17294522 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:3;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:807086860;
	mso-list-type:hybrid;
	mso-list-template-ids:-1753567334 2141229588 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:7;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2
	{mso-list-id:1294478240;
	mso-list-type:hybrid;
	mso-list-template-ids:1476817810 264280828 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l2:level1
	{mso-level-start-at:2;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">A reminder that we&#82=
17;re still looking for agenda items. Our current agenda shows us using onl=
y about half of the 150 minutes we have (though that may be a good sign tha=
t the WGs workload is decreasing).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><a href=3D"https://dat=
atracker.ietf.org/meeting/91/agenda/dhc/">https://datatracker.ietf.org/meet=
ing/91/agenda/dhc/</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo5"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Thursday, October 16, 2014 1:42 PM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> Re: [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items<o:p></o:=
p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Per the preliminary ag=
enda, we will be meeting on Thursday, November 13 from 1640-1910 HST.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We are collecting agen=
da items (see email below as what you should send us at
<a href=3D"mailto:dhc-chairs@tools.ietf.org">dhc-chairs@tools.ietf.org</a> =
to request time).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">At present we have the=
 following so far (this is subject to change):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">DHC WG Agenda for IETF=
-91 (Honolulu)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Date: Thursday Novembe=
r 13, 1640-1910 HST, Kahili 1/2<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Chairs: Tomek Mrugalsk=
i &amp; Bernie Volz<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Secretary: Sheng Jiang=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Presentations material=
s: https://datatracker.ietf.org/meeting/91/materials.html#wg-dhc<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">1. Co-Chairs - Adminis=
trativia (Agenda Bashing, WG Status) - 10 minutes<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">2. Tomek Mrugalski, DH=
CPv6bis Update (draft-dhcwg-dhc-rfc3315bis) - 15 minutes<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">3. Tomek Mrugalski, DH=
CP privacy considerations (draft TBD) - 20 minutes<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">4. Marcin Siodelski an=
d Bernie Volz - draft-ietf-dhc-dhcpv6-stateful-issues -15 minutes<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Wednesday, September 03, 2014 12:01 PM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] IETF-91 (Honolulu) DHC WG Agenda Items<o:p></o:p></=
span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While it is still 2 months away, we are starting to =
collect agenda items for IETF-91&#8217;s DHC WG session.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please send us (<a href=3D"mailto:dhc-chairs@tools.i=
etf.org">dhc-chairs@tools.ietf.org</a>) requests for sessions and include:<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Name of session:<o:p></o:p></p>
<p class=3D"MsoNormal">Name of draft(s):<o:p></o:p></p>
<p class=3D"MsoNormal">Time requested:<o:p></o:p></p>
<p class=3D"MsoNormal">Presenter name(s):<o:p></o:p></p>
<p class=3D"MsoNormal">Brief description of what issues need discussing and=
 what you hope to accomplish by presenting:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">More details about the Honolulu IETF can be found at=
 <a href=3D"http://www.ietf.org/meeting/91/index.html">
http://www.ietf.org/meeting/91/index.html</a>.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo4"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Tomek &amp; Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B6FAD8Dxmbrcdx04ciscoc_--


From nobody Wed Oct 29 10:58:49 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF2051A8745 for <dhcwg@ietfa.amsl.com>; Wed, 29 Oct 2014 10:58:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 UoHQnXXuZYhy for <dhcwg@ietfa.amsl.com>; Wed, 29 Oct 2014 10:58:46 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 874311A01EA for <dhcwg@ietf.org>; Wed, 29 Oct 2014 10:58:26 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id d1so5324202wiv.9 for <dhcwg@ietf.org>; Wed, 29 Oct 2014 10:58:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=IqmcMSN2qqYaExpSC7QIzfldTjs2v9Xx5QhXmo9ZwzU=; b=vgbBrGFx5/P0RZZL0Z+35HHbeNRfvsL6riLi3h12KmpL0Meiy3F4fuhlHoJ0x1W44M Ei8aYaCDvt6WwoZDqljp3h6QkcRa7FRfkeqTbSWncpUR/qNiDEglGNLbs6tNcbOZhmJB hpvChcnVh72ANxBlgJGCLhGzswLw1X3fwFYZsWqKL0IYyC6AkkSxkQN9PvssfvoRz1Mo UIRP2+ai//a/Hm8mT7bFgDoDGIvOBYUQISbIunKUM3azD7fHrLm5v6b8gYzI5wEAaIIm Kl20AqQhpauSyAFyzF/uK9MF4FWMsRLMdq42Ozj8ZidFRUPQPuF2r7XzQ7HZy2UWZaEv C4vw==
MIME-Version: 1.0
X-Received: by 10.194.8.73 with SMTP id p9mr14461297wja.87.1414605505038; Wed, 29 Oct 2014 10:58:25 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.19.136 with HTTP; Wed, 29 Oct 2014 10:58:24 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831832D6E707@XCH-BLV-504.nw.nos.boeing.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com> <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com> <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.com> <2134F8430051B64F815C691A62D9831832D6E707@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 29 Oct 2014 10:58:24 -0700
X-Google-Sender-Auth: b_9EIL0OZGSqH4EZdVNvGXiJR0U
Message-ID: <CAJE_bqeLugy4UuJdT2wLYN6Kr_B-WGBnqXo5x5j0iNGAmCqNCA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/vHOfaXt-KyFfRGFI8mWp5v5fsLI
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 29 Oct 2014 17:58:48 -0000

At Tue, 28 Oct 2014 14:56:35 +0000,
"Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:

> > This version has provided a certificate-based mechanism for the client to authenticated by the server. It is assuming the client has a
> > certificate honored by the server.
>
> Right, I saw that but help me out here. If the client claims a DUID is the certificate
> proof enough that the client is the authorized owner of the DUID?

In my understanding it's not guaranteed by the described protocol: any
client that has a valid certificate can "steal" someone else's DUID
in a signed DHCPv6 message that will be validated.

Enforcing it could be part of the server implementation/configuration,
though.

--
JINMEI, Tatuya


From nobody Wed Oct 29 13:03:57 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D9B71A8907 for <dhcwg@ietfa.amsl.com>; Wed, 29 Oct 2014 13:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 6hHuAwA4XnM6 for <dhcwg@ietfa.amsl.com>; Wed, 29 Oct 2014 13:03:53 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9961E1A87AD for <dhcwg@ietf.org>; Wed, 29 Oct 2014 13:03:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s9TK3rKB026863; Wed, 29 Oct 2014 13:03:53 -0700
Received: from XCH-BLV-107.nw.nos.boeing.com (xch-blv-107.nw.nos.boeing.com [130.247.25.123]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s9TK3gUe026757 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 29 Oct 2014 13:03:43 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.66]) by XCH-BLV-107.nw.nos.boeing.com ([169.254.7.99]) with mapi id 14.03.0210.002; Wed, 29 Oct 2014 13:03:42 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
Thread-Index: AQHP86H7PwFak2fyckefZB8F6L6EcZxHfJFg
Date: Wed, 29 Oct 2014 20:03:42 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832D6FD2C@XCH-BLV-504.nw.nos.boeing.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com> <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com> <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.com> <2134F8430051B64F815C691A62D9831832D6E707@XCH-BLV-504.nw.nos.boeing.com> <CAJE_bqeLugy4UuJdT2wLYN6Kr_B-WGBnqXo5x5j0iNGAmCqNCA@mail.gmail.com>
In-Reply-To: <CAJE_bqeLugy4UuJdT2wLYN6Kr_B-WGBnqXo5x5j0iNGAmCqNCA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/nYWAmY7j2a6aU1MQi7LY0k-wD-I
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 29 Oct 2014 20:03:55 -0000

SGksDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogamlubWVpLnRhdHV5
YUBnbWFpbC5jb20gW21haWx0bzpqaW5tZWkudGF0dXlhQGdtYWlsLmNvbV0gT24gQmVoYWxmIE9m
ID8/Pz8NCj4gU2VudDogV2VkbmVzZGF5LCBPY3RvYmVyIDI5LCAyMDE0IDEwOjU4IEFNDQo+IFRv
OiBUZW1wbGluLCBGcmVkIEwNCj4gQ2M6IFNoZW5nIEppYW5nOyBCZXJuaWUgVm9seiAodm9seik7
IGRoY3dnQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWll
dGYtZGhjLXNlZGhjcHY2LTA0IC0gUmVzcG9uZCBieSBOb3YgMywgMjAxNA0KPiANCj4gQXQgVHVl
LCAyOCBPY3QgMjAxNCAxNDo1NjozNSArMDAwMCwNCj4gIlRlbXBsaW4sIEZyZWQgTCIgPEZyZWQu
TC5UZW1wbGluQGJvZWluZy5jb20+IHdyb3RlOg0KPiANCj4gPiA+IFRoaXMgdmVyc2lvbiBoYXMg
cHJvdmlkZWQgYSBjZXJ0aWZpY2F0ZS1iYXNlZCBtZWNoYW5pc20gZm9yIHRoZSBjbGllbnQgdG8g
YXV0aGVudGljYXRlZCBieSB0aGUgc2VydmVyLiBJdCBpcyBhc3N1bWluZyB0aGUgY2xpZW50IGhh
cw0KPiBhDQo+ID4gPiBjZXJ0aWZpY2F0ZSBob25vcmVkIGJ5IHRoZSBzZXJ2ZXIuDQo+ID4NCj4g
PiBSaWdodCwgSSBzYXcgdGhhdCBidXQgaGVscCBtZSBvdXQgaGVyZS4gSWYgdGhlIGNsaWVudCBj
bGFpbXMgYSBEVUlEIGlzIHRoZSBjZXJ0aWZpY2F0ZQ0KPiA+IHByb29mIGVub3VnaCB0aGF0IHRo
ZSBjbGllbnQgaXMgdGhlIGF1dGhvcml6ZWQgb3duZXIgb2YgdGhlIERVSUQ/DQo+IA0KPiBJbiBt
eSB1bmRlcnN0YW5kaW5nIGl0J3Mgbm90IGd1YXJhbnRlZWQgYnkgdGhlIGRlc2NyaWJlZCBwcm90
b2NvbDogYW55DQo+IGNsaWVudCB0aGF0IGhhcyBhIHZhbGlkIGNlcnRpZmljYXRlIGNhbiAic3Rl
YWwiIHNvbWVvbmUgZWxzZSdzIERVSUQNCj4gaW4gYSBzaWduZWQgREhDUHY2IG1lc3NhZ2UgdGhh
dCB3aWxsIGJlIHZhbGlkYXRlZC4NCg0KVGhhbmtzIGZvciB0aGlzIHVzZWZ1bCBleHBsYW5hdGlv
bi4gIEluIG15IHNjZW5hcmlvLCBjbGllbnRzIGNhbiB0cnVzdCB0aGVpciBzZXJ2ZXJzDQpieSBs
ZWFwLW9mLWZhaXRoIGJlY2F1c2UgdGhlcmUgaXMgYW5vdGhlciB0cnVzdCBiYXNpcyBmb3IgYXNz
dXJpbmcgdGhlIENsaWVudCB0aGF0DQp0aGUgc2VydmVyIGlzIGF1dGhvcml6ZWQgdG8gYWN0IGFz
IGEgc2VydmVyLiBIb3dldmVyLCB0aGUgc2VydmVyIG5lZWRzIHNvbWUgd2F5DQpvZiBrbm93aW5n
IHRoYXQgY2xpZW50cyB0aGF0IHBhc3MgYXV0aGVudGljYXRpb24gYXJlIGFjdHVhbGx5IGF1dGhv
cml6ZWQgdG8gcmVjZWl2ZQ0KdGhlIHJlc291cmNlcyB0aGV5IGFyZSBhc2tpbmcgZm9yLg0KDQpU
YWtlIGZvciBleGFtcGxlIGEgY2xpZW50IEMxIHRoYXQgcHJvdmlkZXMgYSB2YWxpZCBjZXJ0aWZp
Y2F0ZSBidXQgaW5jbHVkZXMgYSBEVUlEDQpjb3JyZXNwb25kaW5nIHRvIGNsaWVudCBDMiBpbiBh
IERIQ1B2NiBQRCBSZXF1ZXN0LiBXaWxsIHRoZSBzZXJ2ZXIgcmV0dXJuIGFuDQpJQV9QRCB0byBj
bGllbnQgQzEgdGhhdCBpbmNsdWRlcyBhIHByZWZpeCB0aGF0IGlzIGludGVuZGVkIGZvciBjbGll
bnQgQzI/IFRoYXQgaXMNCnRoZSBzY2VuYXJpbyBJIG5lZWQgdG8gZGVmZW5kIGFnYWluc3QuDQoN
Cj4gRW5mb3JjaW5nIGl0IGNvdWxkIGJlIHBhcnQgb2YgdGhlIHNlcnZlciBpbXBsZW1lbnRhdGlv
bi9jb25maWd1cmF0aW9uLA0KPiB0aG91Z2guDQoNCkVuZm9yY2UgYnkgbGlua2luZyB0aGUgY2xp
ZW50J3MgY2VydGlmaWNhdGUgdG8gaXRzIERVSUQ/IFNvbWV0aGluZyBlbHNlPw0KDQpUaGFua3Mg
LSBGcmVkDQpmcmVkLmwudGVtcGxpbkBib2VpbmcuY29tDQoNCj4gLS0NCj4gSklOTUVJLCBUYXR1
eWENCg==


From nobody Thu Oct 30 09:54:17 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8334A1A1A64 for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 09:54:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 Z-49tdqhKpkX for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 09:54:13 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBFB11A040C for <dhcwg@ietf.org>; Thu, 30 Oct 2014 09:53:28 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id h11so7981558wiw.6 for <dhcwg@ietf.org>; Thu, 30 Oct 2014 09:53:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=cb2QnWgko0pZQ355GXTyunIrpUwhQAxogUkCXcENI90=; b=YGXSR2l6GcoTp2FfiJ9Nph3F9Zefiah55s4yjgPKENvMxHTSJGenA1MWwU7Hdr1cQb wRx6AQIz1RUNpgnGwOvaNm6MVhuIZeQeN/Scbp/dnAfS7Bext7Gt/cLEEQitrw/cFW44 JWEdOw45hwocYRB4yECaErNkIvwSxw7u08p93m466lD09r75wsW1dTd+pWyJ9qNvR3LY I4CgEKX8LU4jSqf9Cae2qLSvJ5fGTrdneknLUlKZ4VKo6bTc0N4jYgK5XpWQkFUASUsY PpRzNFA+L6YiZezmXvehmOhy5VDGBtJmgNjOiU7EpQSIEWdwSk5i1M3idOFciXpYvJb2 LJEQ==
MIME-Version: 1.0
X-Received: by 10.180.94.138 with SMTP id dc10mr45598820wib.31.1414688006768;  Thu, 30 Oct 2014 09:53:26 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.19.136 with HTTP; Thu, 30 Oct 2014 09:53:26 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831832D6FD2C@XCH-BLV-504.nw.nos.boeing.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com> <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com> <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.com> <2134F8430051B64F815C691A62D9831832D6E707@XCH-BLV-504.nw.nos.boeing.com> <CAJE_bqeLugy4UuJdT2wLYN6Kr_B-WGBnqXo5x5j0iNGAmCqNCA@mail.gmail.com> <2134F8430051B64F815C691A62D9831832D6FD2C@XCH-BLV-504.nw.nos.boeing.com>
Date: Thu, 30 Oct 2014 09:53:26 -0700
X-Google-Sender-Auth: 1QvWzIk6GAV6Sjf0QG9dUIu3a88
Message-ID: <CAJE_bqd54u_msDjwO0Khaz3o+vTe=wbPjOCSAPSr=_gBbzaHgw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/sUgPn1Iz1FfzLTcp39cIApQEip8
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 16:54:14 -0000

At Wed, 29 Oct 2014 20:03:42 +0000,
"Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:

> Take for example a client C1 that provides a valid certificate but includes a DUID
> corresponding to client C2 in a DHCPv6 PD Request. Will the server return an
> IA_PD to client C1 that includes a prefix that is intended for client C2? That is
> the scenario I need to defend against.

Again just in my understanding, the protocol described in the sedhcpv6
draft wouldn't be able to prevent it by itself.  I suspect it's a
matter of the server implementation/operation.  In practice, the
server should maintain some relationship between the certificate's
subject (i.e., that particular client, whether it's in the form of
DUID or of an FQDN or something else) and information (address,
prefix, etc) that the server would assign to the client; otherwise,
just validating the certificate wouldn't be much useful.  I believe
your goal can be achieved by using sedhcpv6 with this setup.

> > Enforcing it could be part of the server implementation/configuration,
> > though.
>
> Enforce by linking the client's certificate to its DUID? Something else?

Enforce by linking the client's certificate to *some ID* of the client
(which might be the DUID or something else).  See above.

--
JINMEI, Tatuya


From nobody Thu Oct 30 12:02:16 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13CA11A1AF7 for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 12:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 EF1xsug-0zyE for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 12:02:08 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70D0E1A1B39 for <dhcwg@ietf.org>; Thu, 30 Oct 2014 12:01:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s9UJ1c64025191; Thu, 30 Oct 2014 14:01:38 -0500
Received: from XCH-PHX-112.sw.nos.boeing.com (xch-phx-112.sw.nos.boeing.com [130.247.25.134]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s9UJ1Sme024966 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 30 Oct 2014 14:01:29 -0500
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.66]) by XCH-PHX-112.sw.nos.boeing.com ([169.254.12.92]) with mapi id 14.03.0210.002; Thu, 30 Oct 2014 12:01:28 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
Thread-Index: AQHP86H7PwFak2fyckefZB8F6L6EcZxHfJFggAHVjwD//64P0A==
Date: Thu, 30 Oct 2014 19:01:27 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832D70B85@XCH-BLV-504.nw.nos.boeing.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B6F6882@xmb-rcd-x04.cisco.com> <2134F8430051B64F815C691A62D9831832D5B51E@XCH-BLV-504.nw.nos.boeing.com> <5D36713D8A4E7348A7E10DF7437A4B923AF6A5C0@nkgeml512-mbx.china.huawei.com> <2134F8430051B64F815C691A62D9831832D6E707@XCH-BLV-504.nw.nos.boeing.com> <CAJE_bqeLugy4UuJdT2wLYN6Kr_B-WGBnqXo5x5j0iNGAmCqNCA@mail.gmail.com> <2134F8430051B64F815C691A62D9831832D6FD2C@XCH-BLV-504.nw.nos.boeing.com> <CAJE_bqd54u_msDjwO0Khaz3o+vTe=wbPjOCSAPSr=_gBbzaHgw@mail.gmail.com>
In-Reply-To: <CAJE_bqd54u_msDjwO0Khaz3o+vTe=wbPjOCSAPSr=_gBbzaHgw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/mVir2BzxFDu0P0CMuky-IeOml0o
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 19:02:12 -0000

SGksDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogamlubWVpLnRhdHV5
YUBnbWFpbC5jb20gW21haWx0bzpqaW5tZWkudGF0dXlhQGdtYWlsLmNvbV0gT24gQmVoYWxmIE9m
ID8/Pz8NCj4gU2VudDogVGh1cnNkYXksIE9jdG9iZXIgMzAsIDIwMTQgOTo1MyBBTQ0KPiBUbzog
VGVtcGxpbiwgRnJlZCBMDQo+IENjOiBkaGN3Z0BpZXRmLm9yZzsgQmVybmllIFZvbHogKHZvbHop
DQo+IFN1YmplY3Q6IFJlOiBbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhjLXNlZGhjcHY2
LTA0IC0gUmVzcG9uZCBieSBOb3YgMywgMjAxNA0KPiANCj4gQXQgV2VkLCAyOSBPY3QgMjAxNCAy
MDowMzo0MiArMDAwMCwNCj4gIlRlbXBsaW4sIEZyZWQgTCIgPEZyZWQuTC5UZW1wbGluQGJvZWlu
Zy5jb20+IHdyb3RlOg0KPiANCj4gPiBUYWtlIGZvciBleGFtcGxlIGEgY2xpZW50IEMxIHRoYXQg
cHJvdmlkZXMgYSB2YWxpZCBjZXJ0aWZpY2F0ZSBidXQgaW5jbHVkZXMgYSBEVUlEDQo+ID4gY29y
cmVzcG9uZGluZyB0byBjbGllbnQgQzIgaW4gYSBESENQdjYgUEQgUmVxdWVzdC4gV2lsbCB0aGUg
c2VydmVyIHJldHVybiBhbg0KPiA+IElBX1BEIHRvIGNsaWVudCBDMSB0aGF0IGluY2x1ZGVzIGEg
cHJlZml4IHRoYXQgaXMgaW50ZW5kZWQgZm9yIGNsaWVudCBDMj8gVGhhdCBpcw0KPiA+IHRoZSBz
Y2VuYXJpbyBJIG5lZWQgdG8gZGVmZW5kIGFnYWluc3QuDQo+IA0KPiBBZ2FpbiBqdXN0IGluIG15
IHVuZGVyc3RhbmRpbmcsIHRoZSBwcm90b2NvbCBkZXNjcmliZWQgaW4gdGhlIHNlZGhjcHY2DQo+
IGRyYWZ0IHdvdWxkbid0IGJlIGFibGUgdG8gcHJldmVudCBpdCBieSBpdHNlbGYuICBJIHN1c3Bl
Y3QgaXQncyBhDQo+IG1hdHRlciBvZiB0aGUgc2VydmVyIGltcGxlbWVudGF0aW9uL29wZXJhdGlv
bi4gIEluIHByYWN0aWNlLCB0aGUNCj4gc2VydmVyIHNob3VsZCBtYWludGFpbiBzb21lIHJlbGF0
aW9uc2hpcCBiZXR3ZWVuIHRoZSBjZXJ0aWZpY2F0ZSdzDQo+IHN1YmplY3QgKGkuZS4sIHRoYXQg
cGFydGljdWxhciBjbGllbnQsIHdoZXRoZXIgaXQncyBpbiB0aGUgZm9ybSBvZg0KPiBEVUlEIG9y
IG9mIGFuIEZRRE4gb3Igc29tZXRoaW5nIGVsc2UpIGFuZCBpbmZvcm1hdGlvbiAoYWRkcmVzcywN
Cj4gcHJlZml4LCBldGMpIHRoYXQgdGhlIHNlcnZlciB3b3VsZCBhc3NpZ24gdG8gdGhlIGNsaWVu
dDsgb3RoZXJ3aXNlLA0KPiBqdXN0IHZhbGlkYXRpbmcgdGhlIGNlcnRpZmljYXRlIHdvdWxkbid0
IGJlIG11Y2ggdXNlZnVsLiAgSSBiZWxpZXZlDQo+IHlvdXIgZ29hbCBjYW4gYmUgYWNoaWV2ZWQg
YnkgdXNpbmcgc2VkaGNwdjYgd2l0aCB0aGlzIHNldHVwLg0KPiANCj4gPiA+IEVuZm9yY2luZyBp
dCBjb3VsZCBiZSBwYXJ0IG9mIHRoZSBzZXJ2ZXIgaW1wbGVtZW50YXRpb24vY29uZmlndXJhdGlv
biwNCj4gPiA+IHRob3VnaC4NCj4gPg0KPiA+IEVuZm9yY2UgYnkgbGlua2luZyB0aGUgY2xpZW50
J3MgY2VydGlmaWNhdGUgdG8gaXRzIERVSUQ/IFNvbWV0aGluZyBlbHNlPw0KPiANCj4gRW5mb3Jj
ZSBieSBsaW5raW5nIHRoZSBjbGllbnQncyBjZXJ0aWZpY2F0ZSB0byAqc29tZSBJRCogb2YgdGhl
IGNsaWVudA0KPiAod2hpY2ggbWlnaHQgYmUgdGhlIERVSUQgb3Igc29tZXRoaW5nIGVsc2UpLiAg
U2VlIGFib3ZlLg0KDQpPSywgdGhhdCBzb3VuZHMgZ29vZCBidXQgY291bGQgcGVyaGFwcyBjb3Vs
ZCB1c2Ugc29tZSBjb25jbHVkaW5nIGRpc2N1c3Npb24NCmF0IHRoZSB1cGNvbWluZyBtZWV0aW5n
LiBJIGhhdmUgYSBidWxsZXQgb24gdGhpcyBvbiBteSBwcmVzZW50YXRpb24gY2hhcnRzLg0KDQpU
aGFua3MgLSBGcmVkDQpmcmVkLmwudGVtcGxpbkBib2VpbmcuY29tDQoNCj4gLS0NCj4gSklOTUVJ
LCBUYXR1eWENCg==


From nobody Thu Oct 30 12:41:11 2014
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A8801A2119 for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 12:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Za81ix_zJuW6 for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 12:41:07 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 833491A1B92 for <dhcwg@ietf.org>; Thu, 30 Oct 2014 12:41:07 -0700 (PDT)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id E84412380340 for <dhcwg@ietf.org>; Thu, 30 Oct 2014 15:41:06 -0400 (EDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_ADC8E321-3643-427B-B904-2C1A51FB4CC8"
Message-Id: <10DCB24C-3A07-4171-B49E-026BC1DB14D8@fugue.com>
Date: Thu, 30 Oct 2014 15:41:04 -0400
To: dhcwg <dhcwg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/2tMDOizTmeSMQ4ArGfydyeVrRWk
Subject: [dhcwg] Update to status of RFC3315 option code registry?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 19:41:10 -0000

--Apple-Mail=_ADC8E321-3643-427B-B904-2C1A51FB4CC8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Currently RFC 3315 says this about registering option codes:

  New DHCP option codes are tentatively assigned after the
  specification for the associated option, published as an Internet
  Draft, has received expert review by a designated expert [11].  The
  final assignment of DHCP option codes is through Standards Action, as
  defined in RFC 2434 [11].

This led to the registry being marked as requiring _both_ expert review =
and standards action.   The original context in which this text was =
written, as I recall, was that we had had a big problem with vendors =
camping on DHCPv4 option codes and not telling us, and we wanted this to =
not happen for DHCPv6.   So we carved out an exception to incentivize =
vendors to document their use of option codes, and to get legitimate =
option code allocations, rather than just picking a number and hoping =
for the best.

So I think what the above language intends is:

If there is a standards-track document published that allocates option =
codes, then they should get expert review, but the presence of the =
standards track document means that there is a presumption that once the =
document describes something that is acceptable, it definitely gets an =
option code.
If there is a non-standards-track use for an option, we can allocate an =
option code for that use, but this allocation requires expert approval, =
and is tentative.   What it means for it to be tentative is that if it =
turns out that whatever use the option code had doesn't see widespread =
deployment, then at some point the option code is returned to the free =
pool.   The mechanism whereby that happens is likely some sort of =
working group action and expert review.

This came up recently in the context of draft-ietf-softwire-4rd, which =
is an experimental document, yet defines new DHCP option codes.   I =
think in principle we want to be able to allocate options in this case, =
but the current registry language prevents us from doing so.   So Adrian =
raised a DISCUSS on this.   I explained the context for the registry =
language, and he asked me to do a document that updates the registry =
status, in exchange for which he cleared his DISCUSS.

By "me" here, of course, he means the DHC working group, or so I'm going =
to claim, for two reasons.   First, it's less work for me, which I =
always like.   Second, the working group is in the process of updating =
RFC 3315.   Maybe we can fold this change into the updated document.   =
Or maybe that will take too long and we should do a short document.

Thoughts?


--Apple-Mail=_ADC8E321-3643-427B-B904-2C1A51FB4CC8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Currently RFC 3315 says this about registering =
option codes:<div><br></div><div>&nbsp; New DHCP option codes are =
tentatively assigned after the<br>&nbsp; specification for the =
associated option, published as an Internet<br>&nbsp; Draft, has =
received expert review by a designated expert [11]. &nbsp;The<br>&nbsp; =
final assignment of DHCP option codes is through Standards Action, =
as<br>&nbsp; defined in RFC 2434 [11].</div><div><br></div><div>This led =
to the registry being marked as requiring _both_ expert review and =
standards action. &nbsp; The original context in which this text was =
written, as I recall, was that we had had a big problem with vendors =
camping on DHCPv4 option codes and not telling us, and we wanted this to =
not happen for DHCPv6. &nbsp; So we carved out an exception to =
incentivize vendors to document their use of option codes, and to get =
legitimate option code allocations, rather than just picking a number =
and hoping for the best.</div><div><br></div><div>So I think what the =
above language intends is:</div><div><br></div><div><ul =
class=3D"MailOutline"><li>If there is a standards-track document =
published that allocates option codes, then they should get expert =
review, but the presence of the standards track document means that =
there is a presumption that once the document describes something that =
is acceptable, it definitely gets an option code.</li><li>If there is a =
non-standards-track use for an option, we can allocate an option code =
for that use, but this allocation requires expert approval, and is =
tentative. &nbsp; What it means for it to be tentative is that if it =
turns out that whatever use the option code had doesn't see widespread =
deployment, then at some point the option code is returned to the free =
pool. &nbsp; The mechanism whereby that happens is likely some sort of =
working group action and expert =
review.</li></ul><div><br></div><div>This came up recently in the =
context of draft-ietf-softwire-4rd, which is an experimental document, =
yet defines new DHCP option codes. &nbsp; I think in principle we want =
to be able to allocate options in this case, but the current registry =
language prevents us from doing so. &nbsp; So Adrian raised a DISCUSS on =
this. &nbsp; I explained the context for the registry language, and he =
asked me to do a document that updates the registry status, in exchange =
for which he cleared his DISCUSS.</div></div><div><br></div><div>By "me" =
here, of course, he means the DHC working group, or so I'm going to =
claim, for two reasons. &nbsp; First, it's less work for me, which I =
always like. &nbsp; Second, the working group is in the process of =
updating RFC 3315. &nbsp; Maybe we can fold this change into the updated =
document. &nbsp; Or maybe that will take too long and we should do a =
short =
document.</div><div><br></div><div>Thoughts?</div><div><br></div></body></=
html>=

--Apple-Mail=_ADC8E321-3643-427B-B904-2C1A51FB4CC8--


From nobody Thu Oct 30 16:20:59 2014
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3F4A1A896C for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 16:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 eMd31qRHGsxK for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 16:20:54 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AD941A8983 for <dhcwg@ietf.org>; Thu, 30 Oct 2014 16:19:25 -0700 (PDT)
Received: by mail-ig0-f180.google.com with SMTP id h3so6113009igd.13 for <dhcwg@ietf.org>; Thu, 30 Oct 2014 16:19:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=g/Pj88KJ4f0hfYCfIQ+nv5X+H8I6L4IZxcx+x7Kyol0=; b=eBnrcAUhZs1Y6ETxkf+r68ma9uXOTXYC+uTajvPd/CrCMJUvF67yy3Wv4eRluM8mYT NlmFFp6h6wD5PjshMX+jNEzazhiXpaT8aSf7XDUyG1e5e7DuUux5n+EieByqFzRyhX70 4/VgsJX9FVjC6PyXMNuIIDujKmw+in0RU6vJHq8YciWw8IuwMSr1NKhEo/vEDhoKVtY6 4b2EiON6bfgAv02Vi7JqEjElxMBGJJOWsWtJfco+lDB+izfmEkqdFrk3Dbqqc5DWk9JN C2J886eXZm+yZUzQll5w9O9b9fDGXdgfOnFSMx159BLHjOQOUov80WGBmDtkkKvolLHW nkgw==
X-Received: by 10.50.134.131 with SMTP id pk3mr594125igb.6.1414711164633; Thu, 30 Oct 2014 16:19:24 -0700 (PDT)
Received: from [192.168.0.102] ([64.56.252.129]) by mx.google.com with ESMTPSA id 131sm86095ioo.8.2014.10.30.16.19.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Oct 2014 16:19:24 -0700 (PDT)
Message-ID: <5452C77D.2080108@gmail.com>
Date: Thu, 30 Oct 2014 19:19:25 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>,  draft-ietf-dhc-dynamic-shared-v4allocation.authors@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/EmR_1Us1VTFHNnRVWeRz03XjtJo
Subject: [dhcwg] Review of draft-ietf-dhc-dynamic-shared-v4allocation-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Oct 2014 23:20:57 -0000

Hi. Thought I'd respond to the call for review.

Tom Taylor

Summary:

Major issues:

Minor issues:

1) There seems to be an inconsistency between Section 5 and 7 and 
Section 6 on the other:

Sec. 5 and 7: The client MAY insert an
        OPTION_V4_PORTPARAMS with a non-zero value in the PSID-Len field
        to indicate a preferred size for the restricted port set to the
        DHCP 4o6 Server.

Sec. 6, third bullet:
     o  The address requested in the 'Requested IP Address' option along
       with the PSID in the OPTION_V4_PORTPARAMS, if the requested pair
       of address and PSID is valid and not already allocated

So which is it, PSID value or (much trickier to manage) PSID length? In 
the latter case, I can see garbage collection issues, as the PSID space 
gets fragmented by repeated client attachments and detachments from the 
network.

2) The operator configures a reserved set of ports. The advice on PSID 
assignment to exclude these ports at the end of Section 8 has a SHOULD 
NOT. Under what circumstances would the server violate its configured 
policy?


Editorial and nits:

1) Abstract, first sentence of second paragraph:

OLD

    Due to the nature of IP addresses sharing, some limitations to their
    applicability are necessary.

NEW

    Due to the nature of IP address sharing, some limitations to its
    applicability are necessary.  ^^                             ^^^

In English, "address" is sort of a kludged noun-turned-adjective 
modifying "sharing" and "IP address sharing" is a singular subject.

2) Section 2, RFC 2119 reference is duplicated.

3) Section 6, end of second last paragraph: s/messages/message/.

4) Section 7.1, first bullet, rewrite in active voice:

OLD

    o  Only port-aware protocols or ICMP implementing [RFC5508] MUST be
       used.
  (Doesn't quite say what you want.)

NEW

    o  The client MUST use only port-aware protocols or ICMP 
implementing [RFC5508].

5) Section 8, fourth bullet below Figure 1, s/valid/the value/

6) Section 8, final paragraph, for accuracy and consistency with 
previous text. The SHOULD NOT as opposed to MUST NOT is questioned above 
as a minor issue.

OLD

  In order to exclude the system ports ([RFC6335]) or ports saved by
    ISPs, the former port-sets that contain well-known ports SHOULD NOT
    be assigned.

NEW

Some PSIDs may include ports within ranges excluded by the operator 
(e.g., the well-known ports 0-1023). These SHOULD NOT be assigned to any 
client.


From nobody Thu Oct 30 19:49:53 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F7C1A8A9C for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 19:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 t8SRBtEhDUQZ for <dhcwg@ietfa.amsl.com>; Thu, 30 Oct 2014 19:49:47 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 051291A8AB0 for <dhcwg@ietf.org>; Thu, 30 Oct 2014 19:49:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19305; q=dns/txt; s=iport; t=1414723787; x=1415933387; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=DWwHhQTF6Iz/Rdzj39fuTAE5cTpG7VWNkPIqVVb0HR4=; b=D3XXOv+2Kx0/ErLNq+oblqSvEFheTQ//HyrRgDxiYkRO2lK2brBuqv/z OXNFWhxQc9VySE641yroV2ZWlZSHS65DPFEcXk7CL5GrfjeIjgIP0BOY+ uLSliNQE/Sb3he+0BtvEY+xzUbRRz24sxYvUbyrV3Ct9Cp0ClMm3VJN/4 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFALT3UlStJV2a/2dsb2JhbABcgkhGVFgEyyyBbYdRAoEcFgEBAQEBfYQCAQEBBC0+HgIBCA4DBAEBCx0HMhQJCAIEARIIiDkNyhoBAQEBAQEBAQEBAQEBAQEBAQEBAQEXjUCDChQ3AYMtgR4FkhCESohHPI0qhy2DeGyBSIEDAQEB
X-IronPort-AV: E=Sophos; i="5.07,291,1413244800"; d="scan'208,217"; a="91959480"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-3.cisco.com with ESMTP; 31 Oct 2014 02:49:46 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s9V2nihJ019433 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 Oct 2014 02:49:44 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0195.001; Thu, 30 Oct 2014 21:49:44 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <mellon@fugue.com>, dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Update to status of RFC3315 option code registry?
Thread-Index: AQHP9HmDXa3AxofgOEWGgLpwYzzxypxJfwfA
Date: Fri, 31 Oct 2014 02:49:44 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B700424@xmb-rcd-x04.cisco.com>
References: <10DCB24C-3A07-4171-B49E-026BC1DB14D8@fugue.com>
In-Reply-To: <10DCB24C-3A07-4171-B49E-026BC1DB14D8@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B700424xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/9Uv1MzmkKHoS1Jfe8z1WmZ9kA8I
Subject: Re: [dhcwg] Update to status of RFC3315 option code registry?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 31 Oct 2014 02:49:51 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1B700424xmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

We can definitely roll this into RFC3315bis. I will open up a ticket for it=
 so we at least track it (even if alternative approaches are used, as the t=
ext will need to be updated).

But, yes it may take a while.

I know you don't seem to favor errata, but perhaps adding you explanation a=
s to what the intent of the RFC 3315 text (in Section 24) was via that mech=
anism might be acceptable?

The other option would be to write a document, such as http://tools.ietf.or=
g/html/rfc2939 (though hopefully not as long). But as we're only trying to =
clarify what the existing text is, rather than 'change' the procedure, that=
 is a bit of a heavy process (yes, I know you can probably expedite it)?

Does IANA have an "Expert Review or Standards Action" (rather than the "Exp=
ert Review and Standards Action" it is now)?


And, I guess given the various values in RFC 2434, perhaps we should revisi=
t what we use and try to stick to one of the standard ones, rather than com=
ing up with something else? We could go for IESG Approval or IETF Consensus=
? (I guess we could do Expert Review AND one of these, though that might be=
 overkill). Given the choices, I'd probably suggest IETF Consensus (without=
 Expert Review, since this would typically be used based on the definition)=
.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Thursday, October 30, 2014 3:41 PM
To: dhcwg
Subject: [dhcwg] Update to status of RFC3315 option code registry?

Currently RFC 3315 says this about registering option codes:

  New DHCP option codes are tentatively assigned after the
  specification for the associated option, published as an Internet
  Draft, has received expert review by a designated expert [11].  The
  final assignment of DHCP option codes is through Standards Action, as
  defined in RFC 2434 [11].

This led to the registry being marked as requiring _both_ expert review and=
 standards action.   The original context in which this text was written, a=
s I recall, was that we had had a big problem with vendors camping on DHCPv=
4 option codes and not telling us, and we wanted this to not happen for DHC=
Pv6.   So we carved out an exception to incentivize vendors to document the=
ir use of option codes, and to get legitimate option code allocations, rath=
er than just picking a number and hoping for the best.

So I think what the above language intends is:


  *   If there is a standards-track document published that allocates optio=
n codes, then they should get expert review, but the presence of the standa=
rds track document means that there is a presumption that once the document=
 describes something that is acceptable, it definitely gets an option code.
  *   If there is a non-standards-track use for an option, we can allocate =
an option code for that use, but this allocation requires expert approval, =
and is tentative.   What it means for it to be tentative is that if it turn=
s out that whatever use the option code had doesn't see widespread deployme=
nt, then at some point the option code is returned to the free pool.   The =
mechanism whereby that happens is likely some sort of working group action =
and expert review.

This came up recently in the context of draft-ietf-softwire-4rd, which is a=
n experimental document, yet defines new DHCP option codes.   I think in pr=
inciple we want to be able to allocate options in this case, but the curren=
t registry language prevents us from doing so.   So Adrian raised a DISCUSS=
 on this.   I explained the context for the registry language, and he asked=
 me to do a document that updates the registry status, in exchange for whic=
h he cleared his DISCUSS.

By "me" here, of course, he means the DHC working group, or so I'm going to=
 claim, for two reasons.   First, it's less work for me, which I always lik=
e.   Second, the working group is in the process of updating RFC 3315.   Ma=
ybe we can fold this change into the updated document.   Or maybe that will=
 take too long and we should do a short document.

Thoughts?


--_000_489D13FBFA9B3E41812EA89F188F018E1B700424xmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:14815918;
	mso-list-template-ids:-1656204244;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:410272958;
	mso-list-type:hybrid;
	mso-list-template-ids:896562028 -216640250 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:3;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">We can definitely roll th=
is into RFC3315bis. I will open up a ticket for it so we at least track it =
(even if alternative approaches are used, as the text will
 need to be updated).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">But, yes it may take a wh=
ile.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I know you don&#8217;t se=
em to favor errata, but perhaps adding you explanation as to what the inten=
t of the RFC 3315 text (in Section 24) was via that mechanism
 might be acceptable?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The other option would be=
 to write a document, such as
<a href=3D"http://tools.ietf.org/html/rfc2939">http://tools.ietf.org/html/r=
fc2939</a> (though hopefully not as long). But as we&#8217;re only trying t=
o clarify what the existing text is, rather than &#8216;change&#8217; the p=
rocedure, that is a bit of a heavy process (yes, I know
 you can probably expedite it)?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Does IANA have an &#8220;=
Expert Review or Standards Action&#8221; (rather than the &#8220;Expert Rev=
iew and Standards Action&#8221; it is now)?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">And, I guess given the va=
rious values in RFC 2434, perhaps we should revisit what we use and try to =
stick to one of the standard ones, rather than coming up
 with something else? We could go for IESG Approval or IETF Consensus? (I g=
uess we could do Expert Review AND one of these, though that might be overk=
ill). Given the choices, I&#8217;d probably suggest IETF Consensus (without=
 Expert Review, since this would typically
 be used based on the definition).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Ted Lemon<br>
<b>Sent:</b> Thursday, October 30, 2014 3:41 PM<br>
<b>To:</b> dhcwg<br>
<b>Subject:</b> [dhcwg] Update to status of RFC3315 option code registry?<o=
:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Currently RFC 3315 says this about registering optio=
n codes:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; New DHCP option codes are tentatively assigne=
d after the<br>
&nbsp; specification for the associated option, published as an Internet<br=
>
&nbsp; Draft, has received expert review by a designated expert [11]. &nbsp=
;The<br>
&nbsp; final assignment of DHCP option codes is through Standards Action, a=
s<br>
&nbsp; defined in RFC 2434 [11].<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This led to the registry being marked as requiring _=
both_ expert review and standards action. &nbsp; The original context in wh=
ich this text was written, as I recall, was that we had had a big problem w=
ith vendors camping on DHCPv4 option codes
 and not telling us, and we wanted this to not happen for DHCPv6. &nbsp; So=
 we carved out an exception to incentivize vendors to document their use of=
 option codes, and to get legitimate option code allocations, rather than j=
ust picking a number and hoping for the
 best.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">So I think what the above language intends is:<o:p><=
/o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
If there is a standards-track document published that allocates option code=
s, then they should get expert review, but the presence of the standards tr=
ack document means that there is a presumption that once the document descr=
ibes something that is acceptable,
 it definitely gets an option code.<o:p></o:p></li><li class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 lev=
el1 lfo1">
If there is a non-standards-track use for an option, we can allocate an opt=
ion code for that use, but this allocation requires expert approval, and is=
 tentative. &nbsp; What it means for it to be tentative is that if it turns=
 out that whatever use the option code
 had doesn't see widespread deployment, then at some point the option code =
is returned to the free pool. &nbsp; The mechanism whereby that happens is =
likely some sort of working group action and expert review.<o:p></o:p></li>=
</ul>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This came up recently in the context of draft-ietf-s=
oftwire-4rd, which is an experimental document, yet defines new DHCP option=
 codes. &nbsp; I think in principle we want to be able to allocate options =
in this case, but the current registry
 language prevents us from doing so. &nbsp; So Adrian raised a DISCUSS on t=
his. &nbsp; I explained the context for the registry language, and he asked=
 me to do a document that updates the registry status, in exchange for whic=
h he cleared his DISCUSS.<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">By &quot;me&quot; here, of course, he means the DHC =
working group, or so I'm going to claim, for two reasons. &nbsp; First, it'=
s less work for me, which I always like. &nbsp; Second, the working group i=
s in the process of updating RFC 3315. &nbsp; Maybe we can
 fold this change into the updated document. &nbsp; Or maybe that will take=
 too long and we should do a short document.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thoughts?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B700424xmbrcdx04ciscoc_--


From nobody Fri Oct 31 03:22:13 2014
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77EE51A7034 for <dhcwg@ietfa.amsl.com>; Fri, 31 Oct 2014 03:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 EZPS2ABgrrvj for <dhcwg@ietfa.amsl.com>; Fri, 31 Oct 2014 03:22:09 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9892E1A1AE9 for <dhcwg@ietf.org>; Fri, 31 Oct 2014 03:22:06 -0700 (PDT)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 545282380340; Fri, 31 Oct 2014 06:22:05 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B700424@xmb-rcd-x04.cisco.com>
Date: Fri, 31 Oct 2014 06:21:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8AC9C84B-5AC4-4D8A-9623-C93F65466E8C@fugue.com>
References: <10DCB24C-3A07-4171-B49E-026BC1DB14D8@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B700424@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/gdPWpvaoSfrmedUn3LgNEHNk4ks
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Update to status of RFC3315 option code registry?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 31 Oct 2014 10:22:11 -0000

On Oct 30, 2014, at 10:49 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I know you don=92t seem to favor errata, but perhaps adding you =
explanation as to what the intent of the RFC 3315 text (in Section 24) =
was via that mechanism might be acceptable?

I don't think it is an error, and furthermore errata can't change the =
outcome of consensus calls, so an erratum would not work for this.

> The other option would be to write a document, such as =
http://tools.ietf.org/html/rfc2939 (though hopefully not as long). But =
as we=92re only trying to clarify what the existing text is, rather than =
=91change=92 the procedure, that is a bit of a heavy process (yes, I =
know you can probably expedite it)?

I can.   I'm not convinced there's that much of a rush, though.

> Does IANA have an =93Expert Review or Standards Action=94 (rather than =
the =93Expert Review and Standards Action=94 it is now)?

It does, but then we wouldn't get expert review on RFCs, and I think we =
want that as a stopgap to prevent options from going all the way through =
to RFC without review by any DHCP experts.   Bear in mind that any =
working group can write a document!   :)

So I guess the real question is, is the timeline for RFC3315bis too long =
to wait?   I'm not personally feeling a need for a tearing rush, but I =
think it should happen sooner than a year, six months at the outside.

