
From nobody Thu Dec  4 08:22:35 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 9B74D1AD48E for <dhcwg@ietfa.amsl.com>; Thu,  4 Dec 2014 08:22:33 -0800 (PST)
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 r2_xlgjqn8ui for <dhcwg@ietfa.amsl.com>; Thu,  4 Dec 2014 08:22:31 -0800 (PST)
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 57AD51A0164 for <dhcwg@ietf.org>; Thu,  4 Dec 2014 08:22:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5400; q=dns/txt; s=iport; t=1417710151; x=1418919751; h=from:to:subject:date:message-id:mime-version; bh=PESHRO+iA2oIst/sWmg19FfsH6Xe3g9tkfItjVS4hac=; b=MTp2t9KkhC1yIrEmcVi+XSCbWzTfnBITxerISe3YQZI0EQtAKaQswikS CcutmDvAYXfAPcCCZ9iSHM1imJ62+3fahDeBUfSma0h5CFCd+LpFuPD1H X+XvY/dVNVTpUfXAoyHJmFpIeAGHiLZWBCTUGbAj00Q3nOWP6ddNWBlwF c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ar8GAISJgFStJA2B/2dsb2JhbABZgkNDUlkDxlGBewGEGgKBHRYBAQEBAX2EBAEELV4BKlYmAQQbAYg1DbBlpiEBAQEBBgEBAQEekDWDXIEeBZAQi22DLY9Ig3mCNIEAAQEB
X-IronPort-AV: E=Sophos;i="5.07,516,1413244800";  d="scan'208,217";a="377650921"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-4.cisco.com with ESMTP; 04 Dec 2014 16:22:30 +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 sB4GMUxw001935 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 4 Dec 2014 16:22:30 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.11]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0195.001; Thu, 4 Dec 2014 10:22:30 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Minutes from IETF-91 (Honolulu) - Please review!
Thread-Index: AdAP3oGxXYt90H80Tr6zQv75qAjkmw==
Date: Thu, 4 Dec 2014 16:22:29 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B74FEF1@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.254.5]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B74FEF1xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/FDDGUT68RpGaNKK-vwTEOAZfZwc
Subject: [dhcwg] Minutes from IETF-91 (Honolulu) - Please review!
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, 04 Dec 2014 16:22:33 -0000

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

Hi:

Please review the draft minutes at http://www.ietf.org/proceedings/91/minut=
es/minutes-91-dhc if you were present or participated otherwise. Thanks to =
Sheng (and others that may have added comments to etherpad) for the minutes=
.


-          Tomek & Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1B74FEF1xmbrcdx04ciscoc_
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.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.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	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:1745033178;
	mso-list-type:hybrid;
	mso-list-template-ids:-1092842372 -1939957000 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	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">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please review the draft minutes at http://www.ietf.o=
rg/proceedings/91/minutes/minutes-91-dhc if you were present or participate=
d otherwise. Thanks to Sheng (and others that may have added comments to et=
herpad) for the minutes.<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 lfo1"><![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_489D13FBFA9B3E41812EA89F188F018E1B74FEF1xmbrcdx04ciscoc_--


From nobody Thu Dec  4 10:07:37 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 459291A1B4E for <dhcwg@ietfa.amsl.com>; Thu,  4 Dec 2014 10:07:36 -0800 (PST)
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 lHcMi6NrPTQH for <dhcwg@ietfa.amsl.com>; Thu,  4 Dec 2014 10:07:34 -0800 (PST)
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 C5A1E1A1AE3 for <dhcwg@ietf.org>; Thu,  4 Dec 2014 10:07:33 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id h11so35614158wiw.13 for <dhcwg@ietf.org>; Thu, 04 Dec 2014 10:07:32 -0800 (PST)
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=eCQeEdaksF4TFW1syM8LCsWnNQNepjM7HgSISYKThQY=; b=nKc1lGaMGTOdeX+logCaL6zbBizld+uNx5vjaVvsiH4oW7NmYFiP9QVNeB06aNtaXj qRkrctudPN9InulFQ2fCbbgv/wX9xpfcUUKeLpqOa7NVDIezmfC9HJswTQY/cwldMe5I +YazaFe91jsL6LeQNTqdprRmf9d2g3GHzKSF+bOm2+FbwqaU4JtPJWkddhKASQV87cVG d33/ZHKlKd5k8ImVdzkbH4qtCS4Os1829PqdX7Yam0u32LIYTb5PDX495UQZXsxOJMad HTxzg5mwh+mxrhrfbNw3MVMhXOaFZM/9YZWGgcjSZpNPhw4yzBnuzMNwccoynACSZXiA yH/g==
MIME-Version: 1.0
X-Received: by 10.180.74.146 with SMTP id t18mr94130322wiv.62.1417716452440; Thu, 04 Dec 2014 10:07:32 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.19.136 with HTTP; Thu, 4 Dec 2014 10:07:32 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com>
Date: Thu, 4 Dec 2014 10:07:32 -0800
X-Google-Sender-Auth: qFB8BvbiNhmCNDrnSZseZr6vxLQ
Message-ID: <CAJE_bqdxyKqNN5R60991pC81_-jCtg1bX91-NeZX0tMvNC_86w@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/HJ3pCSa05eS-zTlL4zDB7buV5hk
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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, 04 Dec 2014 18:07:36 -0000

At Wed, 26 Nov 2014 14:59:10 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> This message starts the DHC working group last call to advance
> "Issues and Recommendations with Multiple Stateful DHCPv6 Options",
> draft-ietf-dhc-dhcpv6-stateful-issues-09.txt, document as a
> Standards Track (Proposed Standard) RFC. The authors believe that
> this version is ready.

I see this version has been improved quite a lot.  But I think we
still need some more discussion and, possibly, revisions before
publication.

One main issue is that there still seem to be cases where we (might)
end up having multiple DHCPv6 sessions for different IAs.  I thought
that's not the intention of this proposal, and assuming this
understanding correct: if the currently described proposal can lead to
that situation, we should definitely fix that; if this is because I
misunderstood what's written in the document, it may suggest the need
for some editorial clarification.  I'll make specific comments on the
relevant text of the draft below.

Specific comments on the draft text:

- Abstract: I still think this could be a bit more friendly,
  especially for first time readers.  Specifically, I'd suggest
  including major recommendation(s) in the abstract, rather than just
  stating that it updates some RFCs.  My specific suggested text is
  something like this:

   [...]  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.
   Specifically, it requires multiple stateful options be handled
   in a single DHCPv6 session as a set, and makes clarifications and
   changes to the prior RFCs to meet the requirement.

- Section 4: I wouldn't be opposed to the decision itself, but the
  justification doesn't seem to be strong enough:

   This leaves a single DHCP session and state machine which is the
   proposed solution.  Here, the client can use what it is able to
   obtain and can continue to request what it was previously unable to
   obtain while maintaining a single session and state machine.

  Simply because other options has drawbacks doesn't automatically
  mean a single DHCP session is inevitably the solution, unless that
  solution has no drawback.  In fact, it does: for example, we could
  end up having an incomplete set of bindings (only one of IA_NA or
  IA_PD has a binding), while we could have bindings for both from
  different servers if we use multiple DHCPv6 sessions.  Likewise, if
  either IA_NA or IA_BD is temporarily unavailable, the client will
  need to wait until the first RENEW/REPLY exchange; with
  multiple-session approach we may be able to get both binding much
  quicker.  I would probably buy the conclusion if all these pros and
  cons are listed and considered, but it's just unconvincing to jump
  to a conclusion by simply listing drawbacks for other options.

- Section 4.4.3:

     The server controls the time at which the client contacts the
     server to extend the lifetimes on assigned addresses through the T1
     and T2 parameters assigned to an IA.  However, as the client
     Renews/Rebinds all IAs from the server at the same time, the client
     MUST select a T1 and T2 time from all IA options which will
     guarantee that the client will send Renew/Rebind messages not later
     than at the T1/T2 times associated with any of the client's
     bindings.

  I'd suggest adding a note that with the updated protocol T1 and T2
  are expected to be the same for all IAs and the choice at the client
  side should be trivial, referring to (the replaced version of)
  RFC3315 Section 18.2.3.

- Section 4.4.5: my previous comment on this doesn't seem to be
  addressed.

     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.

  See http://www.ietf.org/mail-archive/web/dhcwg/current/msg15934.html
  This is related to the "main issue" I mentioned at the top of my
  comments above.

- Section 4.4.5: Likewise.

     -  Tries another server (by restarting the DHCP server discovery
        process).

- Section 4.4.5:

     When the client receives a Reply message in response to a Renew or
     Rebind message, for each IA in the original Renew or Rebind
     message, the client:

     -  Sends a Request message [...]

     -  Sends a Renew/Rebind [...]

  What exactly does "for each IA, ...sends a Request message" mean?
  Would the client sends a Request containing only that specific IA?
  If so, isn't it against the sense of managing all IAs in a single
  DHCPv6 session?  For example, the client could send multiple such
  Renews, and different Replys to them may have different other (so
  called stateless, such as DNS server address) options.  Section 4
  seems to argue that avoiding these is actually the point of this
  proposal.

- Section 4.4.8: this paragraph doesn't make sense to me, or is so
  confusing that I totally misunderstand it:

      For the Renew or Rebind, if the IA_PD contains no prefixes, i.e.
      contains no IA Prefix option or the IPv6 prefix field in the IA
      Prefix option is set to 0, the delegating router SHOULD assign
      prefixes to the IA_PD according to the delegating router's
      explicit configuration information.  In this case, when the server
      assigns new prefixes to the IA_PD, the server MAY use the value in
      the prefix-length field of the IA Prefix option as a hint for the
      length of the prefixes being assigned.

  It says: "if the IA_PD contains no prefixes" and then "the server
  MAY use the value in the prefix-length field of the IA Prefix
  option".  If the assumption is IA_PD contains no prefixes (which I
  interpret means no IA prefix option), how would the server find the
  "prefix-length" field?

  BTW: if this is a replacement for RFC3633, "server" would have to be
  "delegating router".

- Section 4.5: s/server/delegating router/, s/client/requesting router/?

   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.

   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.

 (Unlike the case of replacement text for RFC3633, "server"/"client"
 might be a better choice for the body of this document for
 consistency.  But I'm pointing it out just in case).

--
JINMEI, Tatuya


From nobody Fri Dec  5 20:59: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 E2F441A8AC0 for <dhcwg@ietfa.amsl.com>; Fri,  5 Dec 2014 20:59:19 -0800 (PST)
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 PA5UerisTQSM for <dhcwg@ietfa.amsl.com>; Fri,  5 Dec 2014 20:59:17 -0800 (PST)
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 B9C871A8ABF for <dhcwg@ietf.org>; Fri,  5 Dec 2014 20:59:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9962; q=dns/txt; s=iport; t=1417841957; x=1419051557; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=fHNhqFCyV5txumENCLTzM4HvUtYq8GoE4Vac3HXWn+o=; b=fUgmLh8H8GYIKWEDYcH7JewGDe1qlE/ugmTPjE1GWI8518mf3wrzj8LR Z6ig+6uAn0Ds6zgDQn1S6vudLgUvwOXLlGFbE4zY5lNRnBQQT1TBCt+eA S+V1dedl7g+ecsToSwvKxvO1v2rXChtcc232qHn+2k3lSd49sn+Mnw00P g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlEFAOKMglStJV2S/2dsb2JhbABZgkNDUlgExGOBaoF7AYQXAoERFgEBAQEBfYQCAQEBBC1cAgEIEQQBAQsdBzIUCQgBAQQTCAGIMg3VUQEBAQEBAQEBAQEBAQEBAQEBAQEBAReNFoMINwEGgxuBFQWPRoN+hz00gl6GRIRlg2KCMIE/b4FFfgEBAQ
X-IronPort-AV: E=Sophos;i="5.07,527,1413244800";  d="scan'208,217";a="378005658"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-7.cisco.com with ESMTP; 06 Dec 2014 04:59:16 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id sB64xGxe018312 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sat, 6 Dec 2014 04:59:16 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.111]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0195.001; Fri, 5 Dec 2014 22:59:16 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 2014
Thread-Index: AdAJiVYGp4FUbQo5T+qdYaKm1ensDgHh7VCA
Date: Sat, 6 Dec 2014 04:59:14 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B754171@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B744D04@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.250.157]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B754171xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/TkjQGeQ977l-RGeQPg69KWWAXus
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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: Sat, 06 Dec 2014 04:59:20 -0000

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

Reminder regarding this WGLC. Please review.

>From the IETF-91 minutes (http://www.ietf.org/proceedings/91/minutes/minute=
s-91-dhc):

Asking for additional reviewers: Suresh Krishnan, Ted Lemon, Tim Winters an=
d Tomek Mrugalski signed up.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, November 26, 2014 9:59 AM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respon=
d by December 12th, 2014


Hi all,



This message starts the DHC working group last call to advance "Issues and =
Recommendations with Multiple Stateful DHCPv6 Options", draft-ietf-dhc-dhcp=
v6-stateful-issues-09.txt, document as a Standards Track (Proposed Standard=
) RFC. The authors believe that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09



Please send your comments by December 12th, 2014. If you do not feel this d=
ocument 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_489D13FBFA9B3E41812EA89F188F018E1B754171xmbrcdx04ciscoc_
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";}
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.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;}
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:1504052267;
	mso-list-type:hybrid;
	mso-list-template-ids:-477201226 -1527995754 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	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 regarding thi=
s WGLC. Please review.<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">From the IETF-91 minut=
es (<a href=3D"http://www.ietf.org/proceedings/91/minutes/minutes-91-dhc">h=
ttp://www.ietf.org/proceedings/91/minutes/minutes-91-dhc</a>):<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Asking for additional reviewers: Suresh Krishn=
an, Ted Lemon, Tim Winters and Tomek Mrugalski signed up.<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> Wednesday, November 26, 2014 9:59 AM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 -=
 Respond by December 12th, 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;Issues and Recommendations with Multiple Stateful DHCPv=
6 Options&#8221;, draft-ietf-dhc-dhcpv6-stateful-issues-09.txt, document as=
 a Standards Track (Proposed 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-dhcpv6-stateful-issues-09">http://tools.ietf.org/html/draft-ietf-dhc-dh=
cpv6-stateful-issues-09</a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><b>Please send your comments by December 12th, 20=
14. If you do not feel this document should advance, please state your reas=
ons why.<o:p></o:p></b></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_489D13FBFA9B3E41812EA89F188F018E1B754171xmbrcdx04ciscoc_--


From nobody Mon Dec  8 21:58:12 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 94E721A1DBD; Mon,  8 Dec 2014 21:58:10 -0800 (PST)
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 v4qg8-7oh9V8; Mon,  8 Dec 2014 21:58:09 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5071C1A1BF8; Mon,  8 Dec 2014 21:58:09 -0800 (PST)
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.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141209055809.4375.53418.idtracker@ietfa.amsl.com>
Date: Mon, 08 Dec 2014 21:58:09 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/c74FWcHBUzaOwTiJm7m63HxG42k
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-sedhcpv6-05.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: Tue, 09 Dec 2014 05:58:10 -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           : Secure DHCPv6
        Authors         : Sheng Jiang
                          Sean Shen
                          Dacheng Zhang
                          Tatuya Jinmei
	Filename        : draft-ietf-dhc-sedhcpv6-05.txt
	Pages           : 24
	Date            : 2014-12-08

Abstract:
   The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) enables
   DHCPv6 servers to pass configuration parameters.  It offers
   configuration flexibility.  If not being secured, DHCPv6 is
   vulnerable to various attacks, particularly spoofing attacks.  This
   document analyzes the security issues of DHCPv6 and specifies a
   Secure DHCPv6 mechanism for communications between DHCPv6 clients and
   DHCPv6 servers.  This document provides a DHCPv6 client/server
   authentication mechanism based on server's public/private key pairs
   and client's certificates.  The DHCPv6 message exchanges are
   protected by the signature option and the timestamp option newly
   defined in this document.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-sedhcpv6-05


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 Dec 10 08:05:25 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 A308C1A802D for <dhcwg@ietfa.amsl.com>; Wed, 10 Dec 2014 08:05:21 -0800 (PST)
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 kE1VvoDo7Lpc for <dhcwg@ietfa.amsl.com>; Wed, 10 Dec 2014 08:05:19 -0800 (PST)
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 D004F1A7D84 for <dhcwg@ietf.org>; Wed, 10 Dec 2014 08:05:18 -0800 (PST)
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by tcmail21.telekom.de with ESMTP; 10 Dec 2014 17:05:16 +0100
X-IronPort-AV: E=Sophos;i="5.07,553,1413237600";  d="scan'208,217";a="582366538"
Received: from he113676.emea1.cds.t-internal.com ([10.134.99.29]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES128-SHA; 10 Dec 2014 17:05:16 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113676.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 10 Dec 2014 17:05:16 +0100
From: <ian.farrer@telekom.de>
To: <dhcwg@ietf.org>
Date: Wed, 10 Dec 2014 17:05:12 +0100
Thread-Topic: Request for DHC review of draft-fsc-softwire-dhcp4o6-saddr-opt
Thread-Index: AdAUkxaz7aLzQUTMSya+jdsCz41iIQ==
Message-ID: <D0AE2DC8.E652A%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.6.141106
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_D0AE2DC8E652Aianfarrertelekomde_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/MkGN0sFx1HMqRd8A4KY75Dlq8A0
Subject: [dhcwg] Request for DHC review of draft-fsc-softwire-dhcp4o6-saddr-opt
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, 10 Dec 2014 16:05:22 -0000

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

Hi,

Can I request DHC review of http://datatracker.ietf.org/doc/draft-fsc-softw=
ire-dhcp4o6-saddr-opt/?

The draft started life in DHC, but as the mechanism that it defines are Sof=
twire specific, it was relocated to the SW WG. However, as it defines some =
new DHCP options and server mechanisms, (specifically for use with DHCPv4 o=
ver DHCPv6), any comments from DHC would be welcome.

Thanks,
Ian



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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-si=
ze: 14px; font-family: Calibri, sans-serif;"><div>Hi,</div><div><br></div><=
div>Can I request DHC review of&nbsp;<a href=3D"http://datatracker.ietf.org=
/doc/draft-fsc-softwire-dhcp4o6-saddr-opt">http://datatracker.ietf.org/doc/=
draft-fsc-softwire-dhcp4o6-saddr-opt</a>/?</div><div><br></div><div>The dra=
ft started life in DHC, but as the mechanism that it defines are Softwire s=
pecific, it was relocated to the SW WG. However, as it defines some new DHC=
P options and server mechanisms, (specifically for use with DHCPv4 over DHC=
Pv6), any comments from DHC would be welcome.</div><div><br></div><div>Than=
ks,</div><div>Ian</div><div><br></div><div><br></div></body></html>

--_000_D0AE2DC8E652Aianfarrertelekomde_--


From nobody Thu Dec 11 13:50: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 300EB1A00BF for <dhcwg@ietfa.amsl.com>; Thu, 11 Dec 2014 13:50:25 -0800 (PST)
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 wbb56IUlRfHc for <dhcwg@ietfa.amsl.com>; Thu, 11 Dec 2014 13:50:23 -0800 (PST)
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 B8E0C1A0032 for <dhcwg@ietf.org>; Thu, 11 Dec 2014 13:50:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13683; q=dns/txt; s=iport; t=1418334622; x=1419544222; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=yRA8CZWcHmWbZTjKsQtA/ltJj3TcCNtZUA0gWwLJzOY=; b=EiJkLkiTfEPC8J+jt3bBLUkaDhImYqa1YyUzWCxnyWXgGvgVF7IMIAb0 ThzjJbgbmyN20OpN8fuYTUlypOBpPF6m5YqLjZEUlEmom4899qg1eR+2W lIKxBvpoqlcuEyc2BeId74N3jBJbyBMS71FIZ+JI31goZHPalgQkajxIr s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmQHAKcQilStJA2F/2dsb2JhbABZgkNDUlgExAmBaYVuAoEfFgEBAQEBfYQMAQEBBC1cAgEIEQQBAQsdBzIUCQgBAQQTCAGIIw3YLQEBAQEBAQEBAQEBAQEBAQEBAQEBAReMRIJ9NwEGgxCBEwWNf4M+hj0wgi2FYYQygzcigjCBPG6BRX4BAQE
X-IronPort-AV: E=Sophos;i="5.07,560,1413244800";  d="scan'208,217";a="379556832"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-8.cisco.com with ESMTP; 11 Dec 2014 21:50:20 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id sBBLoKS2029220 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 11 Dec 2014 21:50:20 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.111]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Thu, 11 Dec 2014 15:50:20 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 2014
Thread-Index: AdAJiVYGp4FUbQo5T+qdYaKm1ensDgHh7VCAAR7VpjA=
Date: Thu, 11 Dec 2014 21:50:19 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B7600FB@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B754171@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B754171@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.40.135]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B7600FBxmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/EkRYHVT5wsvToR9ZFxWZBc77eeQ
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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, 11 Dec 2014 21:50:25 -0000

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

Final reminder - PLEASE Review!


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Friday, December 05, 2014 11:59 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Re=
spond by December 12th, 2014

Reminder regarding this WGLC. Please review.

>From the IETF-91 minutes (http://www.ietf.org/proceedings/91/minutes/minute=
s-91-dhc):

Asking for additional reviewers: Suresh Krishnan, Ted Lemon, Tim Winters an=
d Tomek Mrugalski signed up.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, November 26, 2014 9:59 AM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respon=
d by December 12th, 2014


Hi all,



This message starts the DHC working group last call to advance "Issues and =
Recommendations with Multiple Stateful DHCPv6 Options", draft-ietf-dhc-dhcp=
v6-stateful-issues-09.txt, document as a Standards Track (Proposed Standard=
) RFC. The authors believe that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09



Please send your comments by December 12th, 2014. If you do not feel this d=
ocument 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_489D13FBFA9B3E41812EA89F188F018E1B7600FBxmbrcdx04ciscoc_
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";}
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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{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:1378431861;
	mso-list-type:hybrid;
	mso-list-template-ids:-1214626008 738613330 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	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:1504052267;
	mso-list-type:hybrid;
	mso-list-template-ids:-477201226 -1527995754 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	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">Final reminder &#8211;=
 PLEASE Review!<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> Friday, December 05, 2014 11:59 PM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-=
09 - Respond by December 12th, 2014<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">Reminder regarding thi=
s WGLC. Please review.<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">From the IETF-91 minut=
es (<a href=3D"http://www.ietf.org/proceedings/91/minutes/minutes-91-dhc">h=
ttp://www.ietf.org/proceedings/91/minutes/minutes-91-dhc</a>):<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Asking for additional reviewers: Suresh Krishn=
an, Ted Lemon, Tim Winters and Tomek Mrugalski signed up.<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> Wednesday, November 26, 2014 9:59 AM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 -=
 Respond by December 12th, 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;Issues and Recommendations with Multiple Stateful DHCPv=
6 Options&#8221;, draft-ietf-dhc-dhcpv6-stateful-issues-09.txt, document as=
 a Standards Track (Proposed 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-dhcpv6-stateful-issues-09">http://tools.ietf.org/html/draft-ietf-dhc-dh=
cpv6-stateful-issues-09</a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><b>Please send your comments by December 12th, 20=
14. If you do not feel this document should advance, please state your reas=
ons why.<o:p></o:p></b></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_489D13FBFA9B3E41812EA89F188F018E1B7600FBxmbrcdx04ciscoc_--


From nobody Thu Dec 11 22:11:42 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 DD6E71A040B for <dhcwg@ietfa.amsl.com>; Thu, 11 Dec 2014 22:11:40 -0800 (PST)
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 sA7GO0AhViGe for <dhcwg@ietfa.amsl.com>; Thu, 11 Dec 2014 22:11:38 -0800 (PST)
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 965011A8A50 for <dhcwg@ietf.org>; Thu, 11 Dec 2014 22:11:37 -0800 (PST)
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 BPY71721; Fri, 12 Dec 2014 06:11:35 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 12 Dec 2014 06:11:35 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.128]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Fri, 12 Dec 2014 14:11:30 +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-dhcpv6-stateful-issues-09 - Respond by December 12th, 2014
Thread-Index: AdAJiVYGp4FUbQo5T+qdYaKm1ensDgMRniWw
Date: Fri, 12 Dec 2014 06:11:29 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AFEF045@nkgeml512-mbx.china.huawei.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B744D04@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_5D36713D8A4E7348A7E10DF7437A4B923AFEF045nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/ro_IAmnz105Q8bel0PFG0_zjUnQ
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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, 12 Dec 2014 06:11:41 -0000

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

SSBhbSBub3QgaW4gdGhlIHZvbHVudGVlciByZXZpZXdlciBsaXN0IHNpbmNlIEkga25vdyBJIGRv
buKAmXQgaGF2ZSB0aW1lIHRvIHJldmlldyB0aGUgd2hvbGUgZG9jdW1lbnQgaW4gZGV0YWlscy4g
SSBkbyBoYXZlIGEgcXVpY2sgbG9vayB0aHJvdWdoIHRvZGF5IGFuZCBmZWVsIGdvb2QgZm9yIHRo
aXMgZG9jdW1lbnQuIFNvLCBJIHN1cHBvcnQgdG8gbW92ZSBpdCBmb3J3YXJkLg0KDQpIb3dldmVy
LCBJIGRvIGhhdmUgYSBjb3VwbGUgb2YgcXVlc3Rpb25zIGZvciB0aGUgZm9sbG93LXVwIHJlZ2Fy
ZGluZyB0byAzMzE1YmlzLiBUaGUgZG9jdW1lbnQgc3RhdGUg4oCcdGhlIGNoYW5nZXMgZGVzY3Jp
YmVkIGluIHRoaXMgZG9jdW1lbnQgYXJlIGludGVuZGVkIHRvIGJlICBpbmNvcnBvcmF0ZWQgaW4g
YSBuZXcgcmV2aXNpb24gb2YgdGhlIERIQ1B2NiBwcm90b2NvbCBzcGVjaWZpY2F0aW9uIDMzMTVi
aXPigJ0sIGFuZCBJIGtub3cgdGhlIDMzMTViaXMgdGVhbSBkb2VzIGhhdmUgcGxhbiB0byBpbmNs
dWRlIHRoZW0uDQoNCldpbGwgMzMxNWJpcyBvYnNvbGV0ZSB0aGlzIGRvY3VtZW50PyBNeSB1bmRl
cnN0YW5kIGlzIHllcy4gVGhlbiB0aGlzIGRvY3VtZW50IHdvdWxkIGhhdmUgYSB2ZXJ5IHNob3J0
IGxpZmUgdGltZSBsaWtlIG9uZSB5ZWFyLg0KDQpUaGUgbWF0dXJlIG9mIHRoaXMgZG9jdW1lbnQg
aW1wbGllcyB0aGF0IHdlIGhhdmUgc29sdmVkIHRoZXNlIHN0YXRlZnVsIGlzc3Vlcy4gV2h5IHRo
ZXJlIGFyZSBzdGlsbCBvcGVuIHRpY2tldHMgaW4gMzMxNWJpcyBpc3N1ZSB0cmFja2VyPyBUaGVy
ZSBhcmUgOSBvZiB0aWNrZXRzIHRpdGxlZCB3aXRoIOKAnHN0YXRlZnVsIGlzc3Vlc+KAnSBhbmQg
YWxsIG9mIHRoZW0gYXJlIGluIEMgY2F0ZWdvcnkg4oCcYXdhaXRpbmcgY29uc2Vuc3Vz4oCdLiBC
eSBub3csIHNob3VsZG7igJl0IHRoZXkgYmUgY2xvc2VkIG9yIGF0IGxlYXN0IG1vdmVkIGludG8g
QS9CIGNhdGVnb3J5Pw0KDQpCZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQoNCkZyb206IGRoY3dnIFtt
YWlsdG86ZGhjd2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEJlcm5pZSBWb2x6ICh2
b2x6KQ0KU2VudDogV2VkbmVzZGF5LCBOb3ZlbWJlciAyNiwgMjAxNCAxMDo1OSBQTQ0KVG86IGRo
Y3dnQGlldGYub3JnDQpTdWJqZWN0OiBbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhjLWRo
Y3B2Ni1zdGF0ZWZ1bC1pc3N1ZXMtMDkgLSBSZXNwb25kIGJ5IERlY2VtYmVyIDEydGgsIDIwMTQN
Cg0KDQpIaSBhbGwsDQoNCg0KDQpUaGlzIG1lc3NhZ2Ugc3RhcnRzIHRoZSBESEMgd29ya2luZyBn
cm91cCBsYXN0IGNhbGwgdG8gYWR2YW5jZSAiSXNzdWVzIGFuZCBSZWNvbW1lbmRhdGlvbnMgd2l0
aCBNdWx0aXBsZSBTdGF0ZWZ1bCBESENQdjYgT3B0aW9uc+KAnSwgZHJhZnQtaWV0Zi1kaGMtZGhj
cHY2LXN0YXRlZnVsLWlzc3Vlcy0wOS50eHQsIGRvY3VtZW50IGFzIGEgU3RhbmRhcmRzIFRyYWNr
IChQcm9wb3NlZCBTdGFuZGFyZCkgUkZDLiBUaGUgYXV0aG9ycyBiZWxpZXZlIHRoYXQgdGhpcyB2
ZXJzaW9uIGlzIHJlYWR5Lg0KDQoNCg0KVGhlIGRyYWZ0IGlzIGF2YWlsYWJsZSBoZXJlOg0KDQpo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWRoYy1kaGNwdjYtc3RhdGVmdWwt
aXNzdWVzLTA5DQoNCg0KDQpQbGVhc2Ugc2VuZCB5b3VyIGNvbW1lbnRzIGJ5IERlY2VtYmVyIDEy
dGgsIDIwMTQuIElmIHlvdSBkbyBub3QgZmVlbCB0aGlzIGRvY3VtZW50IHNob3VsZCBhZHZhbmNl
LCBwbGVhc2Ugc3RhdGUgeW91ciByZWFzb25zIHdoeS4NCg0KDQoNClRoZXJlIGFyZSBubyBJUFIg
Y2xhaW1zIHJlcG9ydGVkIGF0IHRoaXMgdGltZS4NCg0KDQoNClRvbWVrIGlzIHRoZSBhc3NpZ25l
ZCBzaGVwaGVyZCBmb3IgdGhpcyBkb2N1bWVudC4NCg0KDQoNCi0gVG9tZWsgJiBCZXJuaWUNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QOWui+S9kyI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dl
ZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxpLk1zb1BsYWluVGV4dCwgZGl2Lk1z
b1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6Iue6
r+aWh+acrCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm
b250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K
cC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5Nc29MaXN0UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBhcmFn
cmFwaA0KCXttc28tc3R5bGUtcHJpb3JpdHk6MzQ7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJdGV4dC1pbmRlbnQ6MjEuMHB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkNoYXINCgl7bXNvLXN0
eWxlLW5hbWU6Iue6r+aWh+acrCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNv
LXN0eWxlLWxpbms657qv5paH5pysOw0KCWZvbnQtZmFtaWx5OuWui+S9kzt9DQpzcGFuLkVtYWls
U3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KcC5QbGFpblRleHQsIGxpLlBs
YWluVGV4dCwgZGl2LlBsYWluVGV4dA0KCXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCI7DQoJ
bXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4t
Ym90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsInNhbnMtc2VyaWYiO30NCnNwYW4uUGxhaW5UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToi
UGxhaW4gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxp
bms6IlBsYWluIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K
c3Bhbi5FbWFpbFN0eWxlMjINCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29D
aHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4w
cHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdp
bjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdl
OldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25zICovDQpAbGlzdCBsMA0KCXttc28t
bGlzdC1pZDoyMTM0NjczNjA7DQoJbXNvLWxpc3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVt
cGxhdGUtaWRzOi0xMjk5ODE0MTk0IC0xOTQ3Njc3OTU2IDY3Njk4NzEzIDY3Njk4NzE1IDY3Njk4
NzAzIDY3Njk4NzEzIDY3Njk4NzE1IDY3Njk4NzAzIDY3Njk4NzEzIDY3Njk4NzE1O30NCkBsaXN0
IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDphbHBoYS11cHBlcjsNCgltc28t
bGV2ZWwtdGV4dDoiJTFcKSI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjE4LjBwdDsNCgl0ZXh0LWluZGVu
dDotMTguMHB0O30NCm9sDQoJe21hcmdpbi1ib3R0b206MGNtO30NCnVsDQoJe21hcmdpbi1ib3R0
b206MGNtO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRl
ZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8
bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48
IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGlu
az0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzFG
NDk3RCI+SSBhbSBub3QgaW4gdGhlIHZvbHVudGVlciByZXZpZXdlciBsaXN0IHNpbmNlIEkga25v
dyBJIGRvbuKAmXQgaGF2ZSB0aW1lIHRvIHJldmlldyB0aGUgd2hvbGUgZG9jdW1lbnQgaW4gZGV0
YWlscy4gSSBkbyBoYXZlIGEgcXVpY2sgbG9vayB0aHJvdWdoIHRvZGF5IGFuZCBmZWVsIGdvb2Qg
Zm9yIHRoaXMgZG9jdW1lbnQuDQogU28sIEkgc3VwcG9ydCB0byBtb3ZlIGl0IGZvcndhcmQuIDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzFGNDk3RCI+SG93ZXZlciwgSSBkbyBoYXZl
IGEgY291cGxlIG9mIHF1ZXN0aW9ucyBmb3IgdGhlIGZvbGxvdy11cCByZWdhcmRpbmcgdG8gMzMx
NWJpcy4gVGhlIGRvY3VtZW50IHN0YXRlIOKAnHRoZSBjaGFuZ2VzIGRlc2NyaWJlZCBpbiB0aGlz
IGRvY3VtZW50IGFyZSBpbnRlbmRlZCB0byBiZSZuYnNwOyBpbmNvcnBvcmF0ZWQgaW4gYQ0KIG5l
dyByZXZpc2lvbiBvZiB0aGUgREhDUHY2IHByb3RvY29sIHNwZWNpZmljYXRpb24gMzMxNWJpc+KA
nSwgYW5kIEkga25vdyB0aGUgMzMxNWJpcyB0ZWFtIGRvZXMgaGF2ZSBwbGFuIHRvIGluY2x1ZGUg
dGhlbS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzFGNDk3RCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5N0QiPldpbGwgMzMxNWJp
cyBvYnNvbGV0ZSB0aGlzIGRvY3VtZW50PyBNeSB1bmRlcnN0YW5kIGlzIHllcy4gVGhlbiB0aGlz
IGRvY3VtZW50IHdvdWxkIGhhdmUgYSB2ZXJ5IHNob3J0IGxpZmUgdGltZSBsaWtlIG9uZSB5ZWFy
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzFGNDk3RCI+VGhlIG1hdHVyZSBvZiB0
aGlzIGRvY3VtZW50IGltcGxpZXMgdGhhdCB3ZSBoYXZlIHNvbHZlZCB0aGVzZSBzdGF0ZWZ1bCBp
c3N1ZXMuIFdoeSB0aGVyZSBhcmUgc3RpbGwgb3BlbiB0aWNrZXRzIGluIDMzMTViaXMgaXNzdWUg
dHJhY2tlcj8gVGhlcmUgYXJlIDkgb2YgdGlja2V0cyB0aXRsZWQgd2l0aCDigJxzdGF0ZWZ1bA0K
IGlzc3Vlc+KAnSBhbmQgYWxsIG9mIHRoZW0gYXJlIGluIEMgY2F0ZWdvcnkg4oCcYXdhaXRpbmcg
Y29uc2Vuc3Vz4oCdLiBCeSBub3csIHNob3VsZG7igJl0IHRoZXkgYmUgY2xvc2VkIG9yIGF0IGxl
YXN0IG1vdmVkIGludG8gQS9CIGNhdGVnb3J5PzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29s
b3I6IzFGNDk3RCI+QmVzdCByZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6
IzFGNDk3RCI+U2hlbmc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzFGNDk3
RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYg
MS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFuPjwv
Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBkaGN3ZyBbbWFpbHRv
OmRoY3dnLWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPkJlcm5pZSBWb2x6
ICh2b2x6KTxicj4NCjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIE5vdmVtYmVyIDI2LCAyMDE0IDEw
OjU5IFBNPGJyPg0KPGI+VG86PC9iPiBkaGN3Z0BpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9i
PiBbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhjLWRoY3B2Ni1zdGF0ZWZ1bC1pc3N1ZXMt
MDkgLSBSZXNwb25kIGJ5IERlY2VtYmVyIDEydGgsIDIwMTQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxz
cGFuIGxhbmc9IkVOLVVTIj5IaSBhbGwsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5UaGlzIG1l
c3NhZ2Ugc3RhcnRzIHRoZSBESEMgd29ya2luZyBncm91cCBsYXN0IGNhbGwgdG8gYWR2YW5jZSAm
cXVvdDtJc3N1ZXMgYW5kIFJlY29tbWVuZGF0aW9ucyB3aXRoIE11bHRpcGxlIFN0YXRlZnVsIERI
Q1B2NiBPcHRpb25z4oCdLCBkcmFmdC1pZXRmLWRoYy1kaGNwdjYtc3RhdGVmdWwtaXNzdWVzLTA5
LnR4dCwgZG9jdW1lbnQgYXMgYSBTdGFuZGFyZHMgVHJhY2sgKFByb3Bvc2VkDQogU3RhbmRhcmQp
IFJGQy4gVGhlIGF1dGhvcnMgYmVsaWV2ZSB0aGF0IHRoaXMgdmVyc2lvbiBpcyByZWFkeS48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJF
Ti1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRoZSBkcmFmdCBpcyBhdmFpbGFibGUgaGVyZTo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1V
UyI+PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kaGMtZGhj
cHY2LXN0YXRlZnVsLWlzc3Vlcy0wOSI+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
aWV0Zi1kaGMtZGhjcHY2LXN0YXRlZnVsLWlzc3Vlcy0wOTwvYT48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PGI+PHNwYW4gbGFu
Zz0iRU4tVVMiPlBsZWFzZSBzZW5kIHlvdXIgY29tbWVudHMgYnkgRGVjZW1iZXIgMTJ0aCwgMjAx
NC4gSWYgeW91IGRvIG5vdCBmZWVsIHRoaXMgZG9jdW1lbnQgc2hvdWxkIGFkdmFuY2UsIHBsZWFz
ZSBzdGF0ZSB5b3VyIHJlYXNvbnMgd2h5LjxvOnA+PC9vOnA+PC9zcGFuPjwvYj48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRo
ZXJlIGFyZSBubyBJUFIgY2xhaW1zIHJlcG9ydGVkIGF0IHRoaXMgdGltZS48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4g
bGFuZz0iRU4tVVMiPlRvbWVrIGlzIHRoZSBhc3NpZ25lZCBzaGVwaGVyZCBmb3IgdGhpcyBkb2N1
bWVudC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3Bh
biBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPi0gVG9tZWsgJmFtcDsgQmVybmllPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8
L2h0bWw+DQo=

--_000_5D36713D8A4E7348A7E10DF7437A4B923AFEF045nkgeml512mbxchi_--


From nobody Fri Dec 12 00:11:50 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 6FF341AC420 for <dhcwg@ietfa.amsl.com>; Fri, 12 Dec 2014 00:11:48 -0800 (PST)
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 6T0O0qoZVePG for <dhcwg@ietfa.amsl.com>; Fri, 12 Dec 2014 00:11:47 -0800 (PST)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBD291A0058 for <dhcwg@ietf.org>; Fri, 12 Dec 2014 00:11:46 -0800 (PST)
Received: by mail-wg0-f43.google.com with SMTP id l18so8380821wgh.30 for <dhcwg@ietf.org>; Fri, 12 Dec 2014 00:11:45 -0800 (PST)
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=7SfVV5OJYJ8tstMtMvOJDX7Lg2Cgr9KlVXvJ4XUEYbI=; b=qTqBmY8rkgmep11d6O0hVgfTLdoCWRH/sBpmKfgtGgvEOqScqKmCnuEgxcukHKFvVY 78MzbuDkC61YWlakRiKhRNof1BL0IzobHWhhPOyXhsyyO6wqz7Icd84ovHBtTcbawTWE HHhpo40YeJZZhDe64FA+l1bFoF86Irr3EVfP6Ww6a0NrhEwnpCqXr8QGHZdHYuJTVOvI 7jeeBYkipeXiiWh+K6Qf1K4VUtX+tgFeGvxTjsvuMHvcbJf6VSsvi7+yeLlBUl+IrCer uIZaK0/GPe/wEIXoazEPwekaIQ0Yua5sin9BGLHsU43bE4TVuq1qnKoEZPZOaDjfaZgv 8fNg==
X-Received: by 10.180.99.163 with SMTP id er3mr5284464wib.18.1418371905627; Fri, 12 Dec 2014 00:11:45 -0800 (PST)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id ex8sm793638wjd.41.2014.12.12.00.11.44 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Dec 2014 00:11:44 -0800 (PST)
Message-ID: <548AA33D.8060003@gmail.com>
Date: Fri, 12 Dec 2014 09:11:41 +0100
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: Sheng Jiang <jiangsheng@huawei.com>,  "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com> <5D36713D8A4E7348A7E10DF7437A4B923AFEF045@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AFEF045@nkgeml512-mbx.china.huawei.com>
X-TagToolbar-Keys: D20141212091141165
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/rMlh6iJ3u50pXvK12P79E2HNnqE
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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, 12 Dec 2014 08:11:48 -0000

On 12.12.2014 07:11, Sheng Jiang wrote:
> I am not in the volunteer reviewer list since I know I don’t have time
> to review the whole document in details. I do have a quick look through
> today and feel good for this document. So, I support to move it forward.
Thanks a lot for your support.

> Will 3315bis obsolete this document? My understand is yes. Then this
> document would have a very short life time like one year.
Yes. My understanding is that the idea here is to solve the stateful as
soon as possible and have them published, so vendors can start
implementing them. Once we incorporate them into 3315bis and publish it,
then we'll obsolete stateful-issues RFC, but the nature of those
improvements will not change.

> The mature of this document implies that we have solved these stateful
> issues. Why there are still open tickets in 3315bis issue tracker? There
> are 9 of tickets titled with “stateful issues” and all of them are in C
> category “awaiting consensus”. By now, shouldn’t they be closed or at
> least moved into A/B category?
We'll move them to B category as soon as stateful-issues passes WGLC and
is sent to IESG. That's a realistic point at which we can assume that
the changes have consensus and the text will not change much anymore.
Hopefully that will happen before end of 2014.

If you (generic you) would like to see this happen, please review
stateful-issues and comment on it. If you don't have time, at least take
a quick look and say whether you'd like this work to move forward.

Tomek


From nobody Fri Dec 12 06:27:41 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 45CE21A8A51 for <dhcwg@ietfa.amsl.com>; Fri, 12 Dec 2014 06:27:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 SkKu6DgnvKr3 for <dhcwg@ietfa.amsl.com>; Fri, 12 Dec 2014 06:27:34 -0800 (PST)
Received: from mail-oa0-f98.google.com (mail-oa0-f98.google.com [209.85.219.98]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05E721ACD32 for <dhcwg@ietf.org>; Fri, 12 Dec 2014 06:27:18 -0800 (PST)
Received: by mail-oa0-f98.google.com with SMTP id jd19so5523oac.5 for <dhcwg@ietf.org>; Fri, 12 Dec 2014 06:27:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:message-id:mime-version :subject:date:references:to:in-reply-to; bh=SXEWM0uKtVttAg5s1obEdFqf453BE9zah/lD5oOavws=; b=PcJ+wAhpXaFNOfe5owB/LSiZGF/zIfIHM9uzEOvHXdM2DCqZxapKuHZmUmFXunQlwO /wa6JksXV9lo18lxGJmxEvowCU1Be02bl+lvddYha+CvtxMqmWSSZdfDjHtWEvZDvLKh NuNe6DXSK3OsQZg6a2FUaPbMMt9LictjrSf/jHrdw7GatOY+63KHlgGaiUrIczg5VBhs z6N0emeVX6IB1CfTwAEln+q2ECC0H7s1gJTzXqx6+HjQ5srli2lU4NiuYMbqbMtHXukS wpTQhJHu96wERdbX7pszUDT48RRgYjCVwFEWjjFBGwG4Q6AXAXWo5C1mKLFdbw80XEII wJ8Q==
X-Gm-Message-State: ALoCoQnjWUQHbCqYf3PYaSe1STPrIydZCxq5McJyYqfLW9+9qzvmh+eQZsyGOvNTc31s0oF3oBK3hRs6oo1fNRSQiXVf7HxVOJX9KROgMnv3bD6vP1JmFHg=
X-Received: by 10.224.66.200 with SMTP id o8mr15368821qai.13.1418394438439; Fri, 12 Dec 2014 06:27:18 -0800 (PST)
Received: from postal.iol.unh.edu ([2606:4100:3880:1234::84]) by mx.google.com with ESMTP id mp9sm369461qcb.1.2014.12.12.06.27.17 for <dhcwg@ietf.org>; Fri, 12 Dec 2014 06:27:18 -0800 (PST)
X-Relaying-Domain: iol.unh.edu
Received: from [10.0.1.29] (c-71-200-190-116.hsd1.md.comcast.net [71.200.190.116]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by postal.iol.unh.edu (Postfix) with ESMTPSA id 4DAC842B1D for <dhcwg@ietf.org>; Fri, 12 Dec 2014 09:27:17 -0500 (EST)
From: Timothy Winters <twinters@iol.unh.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DA1C4B9D-D618-4E40-B8C7-5E9F84080949"
Message-Id: <3B3F5A2A-ED1E-4563-A6BB-A4C815A818B2@iol.unh.edu>
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Date: Fri, 12 Dec 2014 09:27:16 -0500
References: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B754171@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B7600FB@xmb-rcd-x04.cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B7600FB@xmb-rcd-x04.cisco.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Sfa6XppyruT0argx19zukwAhWBo
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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, 12 Dec 2014 14:27:37 -0000

--Apple-Mail=_DA1C4B9D-D618-4E40-B8C7-5E9F84080949
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I volunteered to review draft-ietf-dhc-dhcpv6-stateful-issues-09 during =
IETF-91.

Overall I support this going forward, I do have a some areas were we =
might want to clarify some text.

1) Section 4 Last paragraph:
"Proposed solution: the client should keep a single session with the
   server and include the missing options in subsequent messages
   (Request, Renew, and Rebind) to the server."

Is there a reason this is a should?  The rest of document seems to be =
built on premise so MUST might make more sense, unless we have a good =
reason for the should.

2) Section 4.1:
Is says clients MUST handle...Advertise containing a top-level Status =
Code option (of
       NoAddrsAvail) and IA_NAs and/or IA_TAs with a Status Code option
       (of NoAddrsAvail).

How?  Are they suppose to ignore IA_PDs in this case?   I'm wondering =
what a client should do when a legacy server that still puts the =
NoAddrsAvail top-level?

3) Section 4.4.3
"The message exchange is terminated when the valid lifetimes of all =
addresses across all IAs have expired, at which time the client may use =
a Solicit message to locate a new DHCP server and send a
     Request for the expired IAs to the new server."

Client may choose to use a Solicit, what are the other options?   Is do =
nothing ok?

~Tim

> On Dec 11, 2014, at 4:50 PM, Bernie Volz (volz) <volz@cisco.com> =
wrote:
>=20
> Final reminder =E2=80=93 PLEASE Review!
> =20
> -          Bernie
> =20
> From: dhcwg [mailto:dhcwg-bounces@ietf.org =
<mailto:dhcwg-bounces@ietf.org>] On Behalf Of Bernie Volz (volz)
> Sent: Friday, December 05, 2014 11:59 PM
> To: dhcwg@ietf.org <mailto:dhcwg@ietf.org>
> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 =
- Respond by December 12th, 2014
> =20
> Reminder regarding this WGLC. Please review.
> =20
> =46rom the IETF-91 minutes =
(http://www.ietf.org/proceedings/91/minutes/minutes-91-dhc =
<http://www.ietf.org/proceedings/91/minutes/minutes-91-dhc>):
> =20
> Asking for additional reviewers: Suresh Krishnan, Ted Lemon, Tim =
Winters and Tomek Mrugalski signed up.
> =20
> -          Bernie
> =20
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz =
(volz)
> Sent: Wednesday, November 26, 2014 9:59 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - =
Respond by December 12th, 2014
> =20
> Hi all,
> =20
> This message starts the DHC working group last call to advance "Issues =
and Recommendations with Multiple Stateful DHCPv6 Options=E2=80=9D, =
draft-ietf-dhc-dhcpv6-stateful-issues-09.txt, 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-dhcpv6-stateful-issues-09 =
<http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09>
> =20
> Please send your comments by December 12th, 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
> Tomek is the assigned shepherd for this document.
> =20
> - Tomek & Bernie
> =20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


--Apple-Mail=_DA1C4B9D-D618-4E40-B8C7-5E9F84080949
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">I volunteered to review&nbsp;<span style=3D"font-family: =
'Helvetica Neue';" class=3D"">draft-ietf-dhc-dhcpv6-stateful-issues-09 =
during IETF-91.</span><div class=3D""><font face=3D"Helvetica Neue" =
class=3D""><br class=3D""></font></div><div class=3D""><font =
face=3D"Helvetica Neue" class=3D"">Overall I support this going forward, =
I do have a some areas were we might want to clarify some text.<br =
class=3D""></font><div class=3D""><font face=3D"Helvetica Neue" =
class=3D""><br class=3D""></font></div><div class=3D""><font =
face=3D"Helvetica Neue" class=3D"">1) Section 4 Last =
paragraph:</font></div><div class=3D"">"Proposed solution: the client =
should keep a single session with the</div><div class=3D"">&nbsp; =
&nbsp;server and include the missing options in subsequent =
messages</div><div class=3D"">&nbsp; &nbsp;(Request, Renew, and Rebind) =
to the server."</div><div class=3D""><br class=3D""></div><div =
class=3D"">Is there a reason this is a should? &nbsp;The rest of =
document seems to be built on premise so MUST might make more sense, =
unless we have a good reason for the should.</div><div class=3D""><br =
class=3D""></div><div class=3D"">2) Section 4.1:</div><div class=3D"">Is =
says clients MUST handle...Advertise containing a top-level Status Code =
option (of</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp;NoAddrsAvail) =
and IA_NAs and/or IA_TAs with a Status Code option</div><div =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp;(of NoAddrsAvail).</div><div =
class=3D""><br class=3D""></div><div class=3D"">How? &nbsp;Are they =
suppose to ignore IA_PDs in this case? &nbsp; I'm wondering what a =
client should do when a legacy server that still puts the NoAddrsAvail =
top-level?</div><div class=3D""><br class=3D""></div><div class=3D"">3) =
Section 4.4.3</div><div class=3D"">"The message exchange is terminated =
when the valid lifetimes of all addresses across all IAs have expired, =
at which time the client may use a Solicit message to locate a new DHCP =
server and send a</div><div class=3D"">&nbsp; &nbsp; &nbsp;Request for =
the expired IAs to the new server."</div><div class=3D""><br =
class=3D""></div><div class=3D"">Client may choose to use a Solicit, =
what are the other options? &nbsp; Is do nothing ok?</div><div =
class=3D""><div class=3D""><font face=3D"Helvetica Neue" class=3D""><br =
class=3D""></font></div><div class=3D""><font face=3D"Helvetica Neue" =
class=3D"">~Tim</font></div><div class=3D""><font face=3D"Helvetica =
Neue" class=3D""><br class=3D""></font><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On Dec 11, 2014, at 4:50 PM, Bernie Volz =
(volz) &lt;<a href=3D"mailto:volz@cisco.com" =
class=3D"">volz@cisco.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; font-family: =
Helvetica; font-size: 12px; 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 style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: rgb(31, 73, 125);" class=3D"">Final reminder =E2=80=93 =
PLEASE Review!<o:p class=3D""></o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: rgb(31, 73, 125);" =
class=3D"">&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;" class=3D""><span style=3D"color: rgb(31, 73, 125);" =
class=3D""><span class=3D"">-<span style=3D"font-style: normal; =
font-variant: normal; font-weight: normal; font-size: 7pt; line-height: =
normal; font-family: 'Times New Roman';" =
class=3D"">&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);" class=3D"">Bernie<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: rgb(31, 73, 125);" class=3D"">&nbsp;</span></div><div =
class=3D""><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0in 0in;" class=3D""><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><b =
class=3D""><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;" class=3D"">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif;" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>dhcwg [<a =
href=3D"mailto:dhcwg-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">mailto:dhcwg-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Bernie Volz =
(volz)<br class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Friday, December 05, 2014 =
11:59 PM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dhcwg@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">dhcwg@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [dhcwg] WGLC for =
draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, =
2014<o:p class=3D""></o:p></span></div></div></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: rgb(31, 73, 125);" class=3D"">Reminder =
regarding this WGLC. Please review.<o:p class=3D""></o:p></span></div><div=
 style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"color: rgb(31, 73, =
125);" class=3D"">&nbsp;</span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: rgb(31, 73, 125);" class=3D"">=46rom =
the IETF-91 minutes (<a =
href=3D"http://www.ietf.org/proceedings/91/minutes/minutes-91-dhc" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">http://www.ietf.org/proceedings/91/minutes/minutes-91-dhc</a>):=
<o:p class=3D""></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;</span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 10pt; font-family: 'Courier New';" class=3D"">Asking =
for additional reviewers: Suresh Krishnan, Ted Lemon, Tim Winters and =
Tomek Mrugalski signed up.<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"color: rgb(31, 73, =
125);" class=3D"">&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;" class=3D""><span style=3D"color: rgb(31, 73, =
125);" class=3D""><span class=3D"">-<span style=3D"font-style: normal; =
font-variant: normal; font-weight: normal; font-size: 7pt; line-height: =
normal; font-family: 'Times New Roman';" =
class=3D"">&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);" class=3D"">Bernie<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: rgb(31, 73, 125);" class=3D"">&nbsp;</span></div><div =
class=3D""><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0in 0in;" class=3D""><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><b =
class=3D""><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;" class=3D"">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif;" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>dhcwg [<a =
href=3D"mailto:dhcwg-bounces@ietf.org" =
class=3D"">mailto:dhcwg-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Bernie Volz =
(volz)<br class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Wednesday, November 26, =
2014 9:59 AM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dhcwg@ietf.org" class=3D"">dhcwg@ietf.org</a><br =
class=3D""><b class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[dhcwg] WGLC for =
draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, =
2014<o:p class=3D""></o:p></span></div></div></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Hi all,<o:p class=3D""></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">This message starts the DHC working group last call to =
advance "Issues and Recommendations with Multiple Stateful DHCPv6 =
Options=E2=80=9D, draft-ietf-dhc-dhcpv6-stateful-issues-09.txt, document =
as a Standards Track (Proposed Standard) RFC. The authors believe that =
this version is ready.<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">The draft is available here:<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><a =
href=3D"http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-0=
9" style=3D"color: purple; text-decoration: underline;" =
class=3D"">http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issue=
s-09</a><o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D"">Please send your comments by December 12th, =
2014. If you do not feel this document should advance, please state your =
reasons why.<o:p class=3D""></o:p></b></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">There are no IPR claims reported at this time.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Tomek is =
the assigned shepherd for this document.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">- Tomek &amp; Bernie<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><span style=3D"font-family: =
Helvetica; font-size: 12px; 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; float: none; display: inline =
!important;" =
class=3D"">_______________________________________________</span><br =
style=3D"font-family: Helvetica; font-size: 12px; 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;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; 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; float: none; display: inline =
!important;" class=3D"">dhcwg mailing list</span><br style=3D"font-family:=
 Helvetica; font-size: 12px; 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;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; 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; float: none; display: inline =
!important;" class=3D""><a href=3D"mailto:dhcwg@ietf.org" =
class=3D"">dhcwg@ietf.org</a></span><br style=3D"font-family: Helvetica; =
font-size: 12px; 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;" class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
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; float: =
none; display: inline !important;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" =
class=3D"">https://www.ietf.org/mailman/listinfo/dhcwg</a></span></div></b=
lockquote></div><br class=3D""></div></div></div></body></html>=

--Apple-Mail=_DA1C4B9D-D618-4E40-B8C7-5E9F84080949--


From nobody Fri Dec 12 06:44:02 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 34FF01A8856 for <dhcwg@ietfa.amsl.com>; Fri, 12 Dec 2014 06:44:01 -0800 (PST)
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 VaZTaE4zjNmG for <dhcwg@ietfa.amsl.com>; Fri, 12 Dec 2014 06:43:57 -0800 (PST)
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 924341A8700 for <dhcwg@ietf.org>; Fri, 12 Dec 2014 06:43:57 -0800 (PST)
Received: by mail-wg0-f52.google.com with SMTP id x12so9239318wgg.11 for <dhcwg@ietf.org>; Fri, 12 Dec 2014 06:43:56 -0800 (PST)
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=T7kKxCFnR4mvx0NqCpDGpSPgy6eoeHOTyu89dJZCLh8=; b=NvAcDR62wOlmIpQZ17i9KL5GUwAxF0Bp07mY3KTrD7sTOrXR05/gtFQLLfSmGVK4jf S6C1IaOtGmEz2SoZGRkGX+MakEh+eq9zhj3avFIh48bT2B0ZIiHxd+8vhB3jrpF/Qkmj 4zO1FZaeF/p8M2MAvdpUtf2zn0CVGHjvyN17bz4fl5/edutncSTArxtO2ExbGf3f0AgI 2Xn5YJKZqsgA2x6jS3J3q6bbQ77UH/lJZSfH+Hd/QM8LUPQPF4LcbZ2FUXns7gXc07T2 xwK8Ufk+IP9AdyjmOTrsrtAN/tejJ0cVVcBQAYRBaYVNNoCcER0gT/AXkN7J4FV/N3n1 2clA==
X-Received: by 10.180.126.37 with SMTP id mv5mr8311043wib.2.1418395436285; Fri, 12 Dec 2014 06:43:56 -0800 (PST)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id n3sm2082331wjz.21.2014.12.12.06.43.54 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Dec 2014 06:43:55 -0800 (PST)
Message-ID: <548AFF26.6040205@gmail.com>
Date: Fri, 12 Dec 2014 15:43:50 +0100
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" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com>
X-TagToolbar-Keys: D20141212154350516
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/iLigaY_xx4iboiQdDx-7VN8UHQI
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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, 12 Dec 2014 14:44:01 -0000

On 26.11.2014 15:59, Bernie Volz (volz) wrote:
> The draft is available here:
> http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09
> 
> *Please send your comments by December 12th, 2014. If you do not feel
> this document should advance, please state your reasons why.*
I reviewed version -09 of this draft and I strongly support it moving
forward. I do have several comments, but they minor and should not hold
this document.

Abstract (also repeated in Section 1):
"since shoe-horned a new option" =>
"since shoe-horned new options" (there are two: 25 and 26)

Section 1:
"modify the DHCP protocol" => "modify the DHCPv6 protocol". You're not
trying to put IA_PD in DHCPv4, are you? ;)

Section 1:
"The changes described in this document are intended to be
incorporated in a new revision of the DHCPv6 protocol specification
([I-D.dhcwg-dhc-rfc3315bis]).". You should add something along the lines
of "Until 3315bis is published, this document should stand on its own."
Otherwise IESG may think that they are not expected to send this draft
to RFC editor on its own.

Section 4, the last paragraph. This looks like a left-over and it states
the same as the previous one. If you want to keep it, I think it would
be good to remove "proposed" out of it. Once it is published as RFC,
this will no longer be a proposal.

Section 4.1 has a list of 3 choices the client must be able to handle.
I'd reorder them. The number two is the proposed way forward, so it
should be listed first. The other two (current #1 and #3) should be
marked as "This is backward compatibility with servers that hasn't been
updated to this change.".

Section 4.1 (paragraph starting with "Servers MUST return the Status
Code option...") also mentions where the server should put the status
codes when something fails. There are implementations that put status
code = Success in their responses. They should also be bound by the
rules you define here.

Section 4.2, the last proposed replacement proposes to replace the text
with "...such as the available options advertised in IAs.". Maybe it
would be better to say "...such as the available resources advertised in
IAs.". The "resources" naming convention is something we decided to use
in 3315bis. Maybe it's a good time to start using it? You could add it
to the terminology and explain that an allocatable resource is an
address, a prefix or any other resource governed by the server that is
assignable on a per client basis. (It's just an idea. I don't insist on
it. If you don't like it, it will wait till 3315bis is released.)

Section 4.3: "client MUST select a T1 and T2 time from all IA options
which will guarantee that the client will send Renew/Rebind messages not
later than at the T1/T2 times associated with any of the client's
bindings.". In simpler language, "use the smallest T1/T2 values.". Is
that what you want to say?

I don't like the idea of using 0s in the example in Section 4.3. There
was a discussion in 3315bis whether we should forbid 0 as that was
confusing to implementors and packet storms were observed. This brings
the topic of T1 set to 0. Since you mentioned 0 times, have you
considered adding a clarification that "at client's discretion"
explicitly excludes "immediately".

Section 4.4.3. The part that explains what T1=T2=0 means, after " should
add after "...at the client's discretion.": Client MUST NOT initiate the
transmission immediately. (In my opinion it is ok to point it out in
several places. It should be obvious, yet several implementors missed
that point.)

Section 4.4.5 says "If the client finds no usable addresses in any of
the IAs, it may either try another server (by restarting the DHCP server
discovery process) or use the Information-request message to obtain
other configuration information only.". That's not the only option. It's
possible that the client received additional Advertises from other
servers, just the server it picked didn't return anything useful. This
is somewhat obscure, but valid scenario. See Section 17.1.3 of RFC3315,
the paragraph starting with "If the client needs to select an alternate
server...".

Section 4.4.5 also says "The client uses addresses and other information
from any IAs that do not contain a Status Code option with the
NoAddrsAvail code.". I think it would be better to say non-success
status code. That blank statement would cover valid cases like
NoPrefixAvail in IA_PD, UnspecFail or NoBinding in IA_NA, but also
server bugs like when a server sets other error code that is not allowed
here.

Section 4.4.7 says "If the server finds the addresses in the IA for the
client and the server determines that the addresses in the IA are
appropriate for the link to which the client's interface is attached
according to the server's explicit configuration information, the server
SHOULD send back the IA to the client with new lifetimes and, if
applicable, T1/T2 times." What do you mean by "the server finds the
addresses in the IA"? That there are IA address options in the client's
message or that the server found those addresses in its lease database?

Editorial comment: links in section 4.4.8 should say Section 12.1 of RFC
3633. Right now the html version attempts to link to section 12.1 of
stateful-issues.

Section 4.7 may bring to the reader's attention a somewhat obscure
feature mentioned in RFC3315, section 17.1.3. It say says that the
client picks one *or more* Advertise messages. Obviously, how to use
that capability is outside of scope here.

Ok, that's it. Thanks a lot for doing this work. I find those
corrections very useful.

Tomek


From nobody Fri Dec 12 08:07:11 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 2AEC31ACE9F for <dhcwg@ietfa.amsl.com>; Fri, 12 Dec 2014 08:07:09 -0800 (PST)
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 7M0OUVMtlzKW for <dhcwg@ietfa.amsl.com>; Fri, 12 Dec 2014 08:07:06 -0800 (PST)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 881C71ACE74 for <dhcwg@ietf.org>; Fri, 12 Dec 2014 08:07:05 -0800 (PST)
Received: from q4de8psa169.blf.telekom.de ([10.151.13.200]) by tcmail91.telekom.de with ESMTP; 12 Dec 2014 17:07:03 +0100
X-IronPort-AV: E=Sophos;i="5.07,564,1413237600";  d="scan'208,217";a="723296978"
Received: from he110890.emea1.cds.t-internal.com ([10.134.92.131]) by q4de8psazkj.blf.telekom.de with ESMTP/TLS/AES128-SHA; 12 Dec 2014 17:07:02 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by he110890 ([10.134.92.131]) with mapi; Fri, 12 Dec 2014 17:07:02 +0100
From: <ian.farrer@telekom.de>
To: <volz@cisco.com>, <dhcwg@ietf.org>
Date: Fri, 12 Dec 2014 17:06:54 +0100
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 2014
Thread-Index: AdAWJao3aLAdNit+QOuqDrDcpo70LQ==
Message-ID: <D0B0D0F6.E7352%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.6.141106
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_D0B0D0F6E7352ianfarrertelekomde_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Fb4rgF7TAtgti8IDJBEtZ2XLZHE
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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, 12 Dec 2014 16:07:09 -0000

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

Hi,

A quick review of the document. Generally I think it=92s in good shape and =
support it moving forward.  A couple of small comments from my review:

Section 1
Suggested re-word;
Old:
DHCPv6 [RFC3315] was not written with the expectation that additional state=
ful DHCPv6 options would be developed.
New:
DHCPv6 [RFC3315] was written without the expectation that additional statef=
ul DHCPv6 options would be developed.

Section 4 Para 4
The behaviour of creating separate DHCP state machines is also listed as th=
e first item in the issue with no reason given as to why it is a problem.
'multiple instances of the state machine in clients' could be replaced with=
 'additional host resources required to create/maintain multiple instances =
of the state machine in clients'.

Section 4.4.1
The content first paragraph seems at odds with the second and third paragra=
ph.
Para 1 is about a limitation on how leases can be renewed, but then para 2 =
describes
extending the function of the renew message to also request bindings for ot=
her IAs
Para 3 then provides a solution for the problem in para 2, but nothing for =
the
problem described in para 1.
Suggest that Para 3 is updated to say that the Renew message would also be =
able to renew bindings that have been allocated via a Renew message.

One additional comment which I raised in Honolulu, is regarding RFC3633 and=
 the 'NoBinding'
error message, sent to the client when a renew message
However, client behaviour on receipt of this message is not specified. It w=
ould seem
logical that this was interpreted by the client as a reset of its DHCP stat=
e machine.
Should this be dealt with in this document (it is a DHCP state issue), or s=
hould it go into the RFC3315-bis?

Cheers,
Ian

From: "Bernie Volz (volz)" <volz@cisco.com<mailto:volz@cisco.com>>
Date: Thursday, 11 December 2014 22:50
To: "dhcwg@ietf.org<mailto:dhcwg@ietf.org>" <dhcwg@ietf.org<mailto:dhcwg@ie=
tf.org>>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Re=
spond by December 12th, 2014

Final reminder =96 PLEASE Review!


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Friday, December 05, 2014 11:59 PM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Re=
spond by December 12th, 2014

Reminder regarding this WGLC. Please review.

>From the IETF-91 minutes (http://www.ietf.org/proceedings/91/minutes/minute=
s-91-dhc):

Asking for additional reviewers: Suresh Krishnan, Ted Lemon, Tim Winters an=
d Tomek Mrugalski signed up.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, November 26, 2014 9:59 AM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respon=
d by December 12th, 2014


Hi all,



This message starts the DHC working group last call to advance "Issues and =
Recommendations with Multiple Stateful DHCPv6 Options=94, draft-ietf-dhc-dh=
cpv6-stateful-issues-09.txt, document as a Standards Track (Proposed Standa=
rd) RFC. The authors believe that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09



Please send your comments by December 12th, 2014. If you do not feel this d=
ocument 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_D0B0D0F6E7352ianfarrertelekomde_
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><div><div>Hi,</div><div><br=
></div><div>A quick review of the document. Generally I think it=92s in goo=
d shape and support it moving forward. &nbsp;A couple of small comments fro=
m my review:</div><div><div><br></div><div>Section 1</div><div>Suggested re=
-word;</div><div>Old:</div><div>DHCPv6 [RFC3315] was not written with the e=
xpectation that additional stateful DHCPv6 options would be developed.</div=
><div>New:</div><div>DHCPv6 [RFC3315] was written without the expectation t=
hat additional stateful DHCPv6 options would be developed.</div><div><br></=
div><div>Section 4 Para 4</div><div>The behaviour of creating separate DHCP=
 state machines is also listed as the first item in the issue with no reaso=
n given as to why it is a problem.</div><div>'multiple instances of the sta=
te machine in clients' could be replaced with 'additional host resources re=
quired to create/maintain multiple instances of the state machine in client=
s'.</div><div><br></div><div>Section 4.4.1</div><div>The content first para=
graph seems at odds with the second and third paragraph.</div><div>Para 1 i=
s about a limitation on how leases can be renewed, but then para 2 describe=
s</div><div>extending the function of the renew message to also request bin=
dings for other IAs</div><div>Para 3 then provides a solution for the probl=
em in para 2, but nothing for the</div><div>problem described in para 1.</d=
iv><div>Suggest that Para 3 is updated to say that the Renew message would =
also be able to renew bindings that have been allocated via a Renew message=
.</div><div><br></div><div>One additional comment which I raised in Honolul=
u, is regarding RFC3633 and the 'NoBinding'</div><div>error message, sent t=
o the client when a renew message&nbsp;</div><div>However, client behaviour=
 on receipt of this message is not specified. It would seem</div><div>logic=
al that this was interpreted by the client as a reset of its DHCP state mac=
hine.</div></div><div>Should this be dealt with in this document (it is a D=
HCP state issue), or should it go into the RFC3315-bis?</div><div><br></div=
><div>Cheers,</div><div>Ian</div></div></div></div><div><br></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> Thursday, 11 December 2014 22:50<br><=
span style=3D"font-weight:bold">To: </span> &quot;<a href=3D"mailto:dhcwg@i=
etf.org">dhcwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:dhcwg@ietf.org">dhc=
wg@ietf.org</a>&gt;<br><span style=3D"font-weight:bold">Subject: </span> Re=
: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by De=
cember 12th, 2014<br></div><div><br></div><div xmlns:v=3D"urn:schemas-micro=
soft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=
=3D"urn:schemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.micros=
oft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><met=
a 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";}
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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{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:1378431861;
	mso-list-type:hybrid;
	mso-list-template-ids:-1214626008 738613330 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	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:1504052267;
	mso-list-type:hybrid;
	mso-list-template-ids:-477201226 -1527995754 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	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]--><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal"><span style=
=3D"color:#1F497D">Final reminder =96 PLEASE Review!<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"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 =
level1 lfo3"><!--[if !supportLists]--><span style=3D"color:#1F497D"><span s=
tyle=3D"mso-list:Ignore">-<span style=3D"font-style: normal; font-variant: =
normal; font-weight: normal; font-size: 7pt; line-height: normal; font-fami=
ly: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
</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> Friday, December 05,=
 2014 11:59 PM<br><b>To:</b> <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.o=
rg</a><br><b>Subject:</b> Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-statef=
ul-issues-09 - Respond by December 12th, 2014<o:p></o:p></span></p></div></=
div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p class=3D"MsoNormal"><spa=
n style=3D"color:#1F497D">Reminder regarding this WGLC. Please review.<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"MsoNormal"><span style=3D"color:#1F497D"=
>From the IETF-91 minutes (<a href=3D"http://www.ietf.org/proceedings/91/mi=
nutes/minutes-91-dhc">http://www.ietf.org/proceedings/91/minutes/minutes-91=
-dhc</a>):<o:p></o:p></span></p><p class=3D"MsoNormal"><span style=3D"font-=
size: 10pt; font-family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></s=
pan></p><p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family:=
 'Courier New'; color: black;">Asking for additional reviewers: Suresh Kris=
hnan, Ted Lemon, Tim Winters and Tomek Mrugalski signed up.<o:p></o:p></spa=
n></p><p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p=
></span></p><p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-l=
ist:l1 level1 lfo2"><!--[if !supportLists]--><span style=3D"color:#1F497D">=
<span style=3D"mso-list:Ignore">-<span style=3D"font-style: normal; font-va=
riant: normal; font-weight: normal; font-size: 7pt; line-height: normal; fo=
nt-family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&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> Wednesday, November =
26, 2014 9:59 AM<br><b>To:</b> <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf=
.org</a><br><b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful=
-issues-09 - Respond by December 12th, 2014<o:p></o:p></span></p></div></di=
v><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 call to ad=
vance &quot;Issues and Recommendations with Multiple Stateful DHCPv6 Option=
s=94, draft-ietf-dhc-dhcpv6-stateful-issues-09.txt, document as a Standards=
 Track (Proposed Standard) RFC. The
 authors believe that this version is ready.<o:p></o:p></p><p class=3D"MsoP=
lainText"><o:p>&nbsp;</o:p></p><p class=3D"MsoPlainText">The draft is avail=
able here:<o:p></o:p></p><p class=3D"MsoPlainText"><a href=3D"http://tools.=
ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09">http://tools.ietf.o=
rg/html/draft-ietf-dhc-dhcpv6-stateful-issues-09</a><o:p></o:p></p><p class=
=3D"MsoPlainText"><o:p>&nbsp;</o:p></p><p class=3D"MsoPlainText"><b>Please =
send your comments by December 12th, 2014. If you do not feel this document=
 should advance, please state your reasons why.<o:p></o:p></b></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 shep=
herd 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 c=
lass=3D"MsoNormal"><o:p>&nbsp;</o:p></p></div></div></div></span></body></h=
tml>

--_000_D0B0D0F6E7352ianfarrertelekomde_--


From nobody Sat Dec 13 17:18:04 2014
Return-Path: <suresh.krishnan@ericsson.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 221AF1A19F4 for <dhcwg@ietfa.amsl.com>; Sat, 13 Dec 2014 17:18:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 BsTH6IN5XVN1 for <dhcwg@ietfa.amsl.com>; Sat, 13 Dec 2014 17:18:00 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AC471A0A85 for <dhcwg@ietf.org>; Sat, 13 Dec 2014 17:18:00 -0800 (PST)
X-AuditID: c6180641-f79916d00000623a-b9-548c88816ebb
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id FE.35.25146.1888C845; Sat, 13 Dec 2014 19:42:10 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0195.001; Sat, 13 Dec 2014 20:17:51 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 2014
Thread-Index: AdAJiVYGp4FUbQo5T+qdYaKm1ensDg==
Date: Sun, 14 Dec 2014 01:17:50 +0000
Message-ID: <E87B771635882B4BA20096B589152EF6289C56A0@eusaamb107.ericsson.se>
References: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGLMWRmVeSWpSXmKPExsUyuXRPlG5TR0+Iwf3LghZ3O1oYLZbP0HRg 8pjyeyOrx5IlP5kCmKK4bFJSczLLUov07RK4MqZ+WMVU0KdaMeOvUgPjbrkuRk4OCQETifal 09ggbDGJC/fWA9lcHEICRxgleh/DOMsZJS6fWMUIUsUG1LFh52cmEFtEwEfizsHXYN3CApkS v84eBKrhAIpnSbxYXQpRoiexbM07VhCbRUBV4t6sv2CtvAK+Er/ffQRrFQIa03niFguIzQh0 xPdTa8BqmAXEJW49mc8EcZyAxJI955khbFGJl4//sULYShJzXl9jhqg3kHh/bj6UrS2xbOFr ZohdghInZz5hmcAoMgvJ2FlIWmYhaZmFpGUBI8sqRo7S4tSy3HQjw02MwIA/JsHmuINxwSfL Q4wCHIxKPLwG1t0hQqyJZcWVuYcYpTlYlMR5NavnBQsJpCeWpGanphakFsUXleakFh9iZOLg lGpgrF69Z/mN5i67JqfDLhtdl06LD52/dKn/tZjV73IMWXhuv9E3k+61K7ZePNvw4EHnI1+6 mhltYhdt2FlWVb3w1etUkdy+LZft8iMN5zSoNrjF94jzPw3mcTYUem5xa8NW7Vn18wTLfmby zeNWisi/tNp0qaZQsl7Zsk2Zx6/Xbz4pINHg8LlAiaU4I9FQi7moOBEAQY+XTlkCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/UXg45OpW3CmXqdJJ8BWrpizuX6k
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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, 14 Dec 2014 01:18:02 -0000

Hi all,=0A=
   I went through this document and I support this work moving forward. =0A=
The document is easy to read and understand. I do have a few comments =0A=
and proposed text changes and would appreciate it if the authors can go =0A=
over them. Most of them are clarity related but I do have two material =0A=
issues that would probably require WG discussion.=0A=
=0A=
=0A=
Section 1:=0A=
=0A=
s/stateless address assignment/stateless address auto-configuration/=0A=
=0A=
Section 4:=0A=
=0A=
OLD:=0A=
DHCPv6 was written=0A=
=0A=
NEW:=0A=
The original DHCPv6 specification [RFC3315] was written=0A=
=0A=
OLD:=0A=
=0A=
DHCPv6 PD describes how to extend the DHCPv6 protocol to handle=0A=
prefix delegation, but [RFC3633] did not consider how DHCP=0A=
address assignment and prefix delegation could co- exist.=0A=
=0A=
NEW:=0A=
=0A=
DHCPv6 Prefix Delegation (PD) [RFC3633] describes how to extend=0A=
the DHCPv6 protocol to handle prefix delegation, but does not=0A=
clearly specify how DHCP address assignment and prefix delegation=0A=
co-exist.=0A=
=0A=
s/has a number/causes a number/=0A=
=0A=
OLD:=0A=
'collisions' between other configuration options=0A=
=0A=
NEW:=0A=
=0A=
unnecessary duplication of other configuration options and=0A=
potential for conflict.=0A=
=0A=
Section 4.1=0A=
=0A=
OLD:=0A=
=0A=
In Advertise messages the Status Code option with the=0A=
NoAddrsAvail code is in the top level.=0A=
=0A=
NEW:=0A=
=0A=
In Advertise messages though, the NoAddrsAvail code is returned=0A=
at the top level.=0A=
=0A=
Why do we need option 3 of the client behavior? Neither existing =0A=
compliant servers and new servers following this spec will send such =0A=
messages=0A=
=0A=
Section 4.2:=0A=
=0A=
OLD:=0A=
=0A=
A client requesting both IA_NA and IA_PD, with a server that only=0A=
offers one of them, is not supported in the current protocol=0A=
specification.=0A=
=0A=
NEW:=0A=
=0A=
Thus a client requesting both IA_NA and IA_PD, from a server that=0A=
only offers an IA_PD is not supported in the current protocol=0A=
specifications.=0A=
=0A=
=0A=
OLD:=0A=
=0A=
A client SHOULD only ignore an Advertise message when all IA=0A=
options include no offered addresses or delegated prefixes.=0A=
=0A=
NEW:=0A=
=0A=
A client SHOULD only ignore an Advertise message when none of the=0A=
requested IA options are offered by the server.=0A=
=0A=
* The text change for Section 17.1.3 of RFC3315 is ambiguous. I=0A=
   think it incorrectly associates displaying of status messages=0A=
   with the presence of the RFC7083 options.=0A=
=0A=
* Section 4.3=0A=
=0A=
I think we need an additional restriction on the server side=0A=
regarding the T1 and T2 times.=0A=
=0A=
The T2 times for all of the IA options need to be larger than the=0A=
T1 times for all of the IA options. This is required to ensure=0A=
that the client does not try to contact other servers before=0A=
trying renewal.=0A=
=0A=
* Section 4.4.1=0A=
=0A=
What subsquent messages?=0A=
=0A=
* Section 4.4.3.=0A=
=0A=
Please see my comment on Section 4.3. My contention is that=0A=
=0A=
"the client MUST select a T1 and T2 time from all IA options=0A=
which will guarantee that the client will send Renew/Rebind=0A=
messages not later than at the T1/T2 times associated with any of=0A=
the client's bindings."=0A=
=0A=
cannot always be satisfied until we put in a restriction on the=0A=
T1/T2 times.=0A=
=0A=
* Section 4.7=0A=
=0A=
Does it make sense to add a reference to=0A=
draft-ietf-mif-mpvd-arch-07 and/or=0A=
draft-ietf-mif-mpvd-dhcp-support-00 here?=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=
=0A=
On 11/26/2014 09:59 AM, Bernie Volz (volz) wrote:=0A=
> Hi all,=0A=
>=0A=
> This message starts the DHC working group last call to advance "Issues=0A=
> and Recommendations with Multiple Stateful DHCPv6 Options=94,=0A=
> draft-ietf-dhc-dhcpv6-stateful-issues-09.txt, document as a Standards=0A=
> Track (Proposed Standard) RFC. The authors believe that this version is=
=0A=
> ready.=0A=
>=0A=
> The draft is available here:=0A=
>=0A=
> http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09=0A=
>=0A=
> *Please send your comments by December 12th, 2014. If you do not feel=0A=
> this document should advance, please state your reasons why.*=0A=
>=0A=
> There are no IPR claims reported at this time.=0A=
>=0A=
> Tomek is the assigned shepherd for this document.=0A=
>=0A=
> - Tomek & Bernie=0A=
>=0A=
>=0A=
>=0A=
> _______________________________________________=0A=
> dhcwg mailing list=0A=
> dhcwg@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/dhcwg=0A=
>=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=


From nobody Mon Dec 15 11:15:14 2014
Return-Path: <ietf-ipr@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 58C6D1A8744; Mon, 15 Dec 2014 10:27:37 -0800 (PST)
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 J137VnDdYr5o; Mon, 15 Dec 2014 10:27:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0769E1A872E; Mon, 15 Dec 2014 10:27:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-ipr@ietf.org>
To: yong@csnet1.cs.tsinghua.edu.cn, sunqiong@ctbri.com.cn, ian.farrer@telekom.de, yiu_lee@cable.comcast.com, sunqi@csnet1.cs.tsinghua.edu.cn, mohamed.boucadair@orange.com
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141215182735.15405.94647.idtracker@ietfa.amsl.com>
Date: Mon, 15 Dec 2014 10:27:35 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/WjduZ6VjiGC0s6pymv3Vt8x0w7Y
X-Mailman-Approved-At: Mon, 15 Dec 2014 11:15:09 -0800
Cc: brian@innovationslab.net, volz@cisco.com, ted.lemon@nominum.com, dhcwg@ietf.org, ipr-announce@ietf.org
Subject: [dhcwg] IPR Disclosure: Orange's Statement about IPR related to draft-ietf-dhc-dynamic-shared-v4allocation-02
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, 15 Dec 2014 18:27:38 -0000

Dear Yong Cui, Qiong Sun, Ian Farrer, Yiu Lee, Qi Sun, Mohamed Boucadair:

 An IPR disclosure that pertains to your Internet-Draft entitled "Dynamic
Allocation of Shared IPv4 Addresses" (draft-ietf-dhc-dynamic-shared-
v4allocation) was submitted to the IETF Secretariat on 2014-12-15 and has been
posted on the "IETF Page of Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/2502/). The title of the IPR disclosure is
"Orange's Statement about IPR related to draft-ietf-dhc-dynamic-shared-
v4allocation-02."");

The IETF Secretariat


From nobody Mon Dec 15 11:36:50 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 E90141A8782 for <dhcwg@ietfa.amsl.com>; Mon, 15 Dec 2014 11:36:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level: 
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_20=-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 Cgm2pTLZ3eUV for <dhcwg@ietfa.amsl.com>; Mon, 15 Dec 2014 11:36:44 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 81E331A8778 for <dhcwg@ietf.org>; Mon, 15 Dec 2014 11:36:34 -0800 (PST)
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 BF87D23805E2 for <dhcwg@ietf.org>; Mon, 15 Dec 2014 14:36:32 -0500 (EST)
From: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <3480FD7D-80E9-47B9-852B-0EDD2F887BF1@fugue.com>
Date: Mon, 15 Dec 2014 14:35:40 -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/iBi51sMvoaE6R27f2pqt4OTZisM
Subject: [dhcwg] WGLC review 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, 15 Dec 2014 19:36:49 -0000

Aside from this rather voluminous set of nits and comments, the document =
looks good and I support advancing it.   Thanks for the hard work on =
this.   I will become less and less available between now and 1/5, so =
please don't delay updating the document while waiting for a response =
from me.   I will review whatever comments follow when I get back as =
part of what I assume will be a request for publication.

My comments/nits:

The abstract is a bit colloquial and contains references to other =
documents that I don't think are necessary to understand what this =
document does, and actually prevent people who don't already know what =
the document does from quickly figuring it out.   I'm a bit on the =
warpath about long abstracts: they should really be the elevator pitch =
for your document.   Suggestion:

OLD:
   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 has since shoe-horned a new option 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.

NEW:
   The DHCPv6 specification defines two stateful options, IA_NA
   and IA_TA, but does not anticipate the development of additional
   stateful options.  DHCPv6 Prefix Delegation adds the IA_PD option,
   which is stateful.  Applications that use IA_NA and IA_PD
   together have revealed issues that need to be addressed.  This
   document updates RFC 3315 and RFC 3633 to address these issues.

In the introduction, don't use "shoe-horned."   Just say "added."   The =
RFC editor would probably ding you on this, but I'm saying it now in =
hopes that more people will read this review than would read the =
interaction with the RFC editor.   Colloquialisms make documents harder =
to read for anyone who is not familiar with the colloquialism, which is =
at present the majority of readers of RFCs.

OLD:
   This document describes a number of problems encountered with
   coexistence of the IA_NA and IA_PD option types and changes to the
   DHCPv6 protocol specifications to address these problems.
NEW:
   This document describes a number of problems encountered with
   coexistence of the IA_NA and IA_PD option types and specifies=20
   changes to the DHCPv6 protocol to address these problems.

(making it a compound sentence instead of a sentence with a compound =
phrase makes it less ambiguous and hence easier to understand.)

This doesn't make sense:
   DHCPv6 assigned temporary addresses also
   have limited value when DHCPv6 is used for non-temporary address
   assignment, as the privacy issues identified for IPv6 stateless
   address assignment ([RFC4941]) do not apply to DHCPv6 assignments.

The expected use of IA_TA is that you would acquire temporary addresses =
and a non-temporary address; the temporary addresses are used for =
outgoing connections; the non-temporary address is used for incoming =
connections and is optionally entered in the DNS.   As long as the host =
enforces the separate uses of temporary and non-temporary addresses, it =
all works: an off-network listener will not know that the IA_TA and =
IA_NA addresses belong to the same host.   That's a big if, but that's =
not our problem.

I think the gist of this paragraph is correct, but the sentence above is =
incorrect and should just be deleted.  I also think IA_TA is completely =
out of scope for this document, not just mostly out of scope, for the =
reason stated in the first sentence in the paragraph.   I notice that =
IA_TA is referenced throughout the document as equivalent to IA_NA; if =
indeed the assertion here is correct, then it shouldn't be mentioned =
again in the document.   I think that would make the document a bit =
clearer.

Maybe make the second sentence a bulleted list:

   If a client requests multiple IA option types, but the server is
   configured to only offer a subset of them, the client could react in
   several ways.  Reset the state machine and continue to send Solicit
   messages, create separate DHCP sessions for each IA option type and
   continue to Solicit for the unfulfilled IA options, or it could
   continue with the single session, and include the unfulfilled IA
   options in subsequent messages to the server.

The case mentioned in the second sentence would happen whenever such a =
broken client is on a network with no DHCP server.   Does it really need =
to be mentioned here?

   Reseting the state machine and continuing to send Solicit messages
   may result in the client never completing DHCP and is generally not
   considered a good solution.  It can also result in a request storm if
   the client does not appropriately rate limit its sending of Solicit
   messages.

OLD:
   This leaves a single DHCP session and state machine which is the
   proposed solution.  Here, the client can use what it is able to
   obtain and can continue to request what it was previously unable to
   obtain while maintaining a single session and state machine.

   Proposed solution: the client should keep a single session with the
   server and include the missing options in subsequent messages
   (Request, Renew, and Rebind) to the server.
NEW:
   We have chosen the remaining option: a single DHCP session and state
   machine.  The client maintains a single session and state machine.
   It uses the best configuration it is able to obtain during any
   configuration exchange.   But it continues, in each subsequent
   configuration exchange, to request all the configuration information
   it is programmed to try to obtain, including any stateful =
configuration
   options for which no results were returned in previous exchanges.

In 4.1 paragraph 1 you use the terms "encapsulation" and "top level".   =
These should be defined in the glossary, ideally by referring to their =
definitions either in RFC3315, if possible, or in RFC 7227, which has a =
really good discussion in section 9 on the topic of encapsulation, =
although it doesn't explicitly hit on the topic of "top level" options.  =
 Actually, the term top level is used but not defined in 7227, and =
vaguely referenced, but never named nor discussed explicitly that I can =
see in 3315, so this should just be explained in the glossary.  I would =
say something like this:

   Top Level options
      Top level options are DHCPv6 options that are not encapsulated
      within other options, excluding the Relay-Message option.   =
Options
      encapsulated by Relay-message options, but not by any other =
option,
      are still top-level options, whether they appear in a relay agent
      message or a server message.

If this is an update to a standard, then we have chosen a solution--we =
aren't just proposing one.  The phrasing you are using here would be =
appropriate in an experimental doc, but (ironically) is not appropriate =
in a proposed standard:

OLD:
   Therefore, the proposed solution is:
NEW:
   We have chosen the following solution:

However, this seems like it's part of the update.   Is there a place in =
RFC 3315 where this could be said to be added?   This is clearly =
normative text.

I don't think this is quite right:

     -  The client MAY choose a less-preferred server if that server
        has a better set of advertised parameters, such as the
        available options advertised in IAs.

I suggest:

     -  The client MAY choose a less-preferred server if that server
        has a better set of advertised parameters, such as the
        available set of IAs, as well as the set of non-IA options
        advertised.

You could leave out the final dependent clause if you like, but I think =
the way I've restated it is closer to combining what was previously =
intended with what you need to change.

Shouldn't the following text be normative?

   It is important to note that the receipt of an Advertise message
   without any addresses and delegated prefixes does not imply that the
   client should restart the Solicit retransmissions timers.  Doing so
   would lead to a Solicit/Advertise storm.

There's quite a bit of text in subsequent sections that looks something =
like this:

   Proposed solution: The server MUST set the T1/T2 times in all IA

The same comment I made earlier applies here.   You should just =
substitude "Solution: " in place of "Proposed Solution" in each of these =
instances.

This is really confusing, so I suggest changing it:
OLD:
     To extend the valid and preferred lifetimes for the addresses
     associated with an IA, the client sends a Renew message to the
     server from which the client obtained the addresses in the IA
     containing an IA option for the IA.  The client includes IA Address
     options in the IA option for the addresses associated with the IA.
     The server determines new lifetimes for the addresses in the IA
     according to the administrative configuration of the server.  The
     server may also add new addresses to the IA.  The server may remove
     addresses from the IA by setting the preferred and valid lifetimes
     of those addresses to zero.
NEW:
     To extend the valid and preferred lifetimes for the addresses
     assigned to an IA, the client sends a Renew message to the
     server from which the addresses were obtained,
     which includes an IA option for the IA whose whose address
     lifetimes are to be extended.  The client includes IA Address
     options within the IA option for the addresses assigned to the IA.
     The server determines new lifetimes for these addresses
     according to the administrative configuration of the server.  The
     server may also add new addresses to the IA.  The server can remove
     addresses from the IA by returning IA Address options for such
     addresses with preferred and valid lifetimes set to zero.

I think this is bad advice:

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

Can the client send a Renew or Rebind after zero seconds?   That would =
be at its discretion, but obviously bad.   I think the right advice is =
to say that the client should choose a renew and rebind interval that is =
consistent with the valid and preferred times of all the addresses and =
prefixes received: if there are addresses and/or prefixes with preferred =
times, then the renewal and rebind times should result in those =
addresses and/or prefixes being renewed well before the preferred =
lifetime expires; if there are addresses with preferred lifetimes of =
zero, but residual valid lifetimes, these should not be renewed.   That =
might be too complicated for this document, though--if you prefer, you =
could just say "at the client's discretion, but no sooner than X," but =
then we'd have to argue about what X should be.

I think the following is unclear.   I've proposed a clearer version that =
I think says what was intended, but it was unclear, so I don't know if I =
correctly understood what was intended.   Also, I think this applies to =
Renew and Rebind messages, according to the preceding text, so the =
specific mention of Reply messages seems wrong, and I left it out of my =
proposed text:

OLD:
     The client includes an IA option with all addresses currently
     assigned to the IA in its Renew message.  The client also includes
     IA options for all other bindings for which the client desires to
     extend the lifetimes of addresses.  The client MUST only include
     addresses in the IA that the client obtained from the server and
     are still valid (have non-zero lifetime).
NEW:
     For IAs to which addresses have been assigned, the client includes
     a corresponding IA option containing an IA Address option for each
     address assigned to the IA.   For IAs to which prefixes have been
     assigned, the client includes a corresponding IA option containing
     an IA Prefix option for each prefix assigned to the IA.   The =
client
     MUST NOT include addresses or prefixes in any IA option that the
     client did not obtain from the server or that are no longer valid
     (that have have a zero valid lifetime).

You'll probably get a DISCUSS on this:

     If the client receives a Reply message with a Status Code
     containing UnspecFail, the server is indicating that it was unable
     to process the message due to an unspecified failure condition.  If
     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.

You really need to say something about how this rate limiting is done, =
or else it's too vague to really be meaningful.   For example, the =
client could send no more frequently than every thirty seconds, and on a =
small network this would be no problem, but it would be absolutely nuts =
on a really big network.

In the following text, I am left wondering on what basis the client =
should choose between the two alternatives:

     The client uses addresses and other information from any IAs that
     do not contain a Status Code option with the NoAddrsAvail code.
     For each IA for which the client receives NoAddrsAvail status code
     the client has the following choices:

     -  The client includes the IA with no addresses in subsequent Renew
        and Rebind messages sent to the server, to request creation of
        the binding for the IA.

     -  Tries another server (by restarting the DHCP server discovery
        process).

I think it's that if the client can't continue to operate without the =
resource it's trying to renew, it will choose to restart the process; if =
it can, it doesn't restart the process.   Also, does this text apply =
just to addresses, or also to prefixes?

What if the server has no record that it sent a unicast option, but is =
configured to support unicast?

     When the server receives a Renew message via unicast from a client
     to which the server has not sent a unicast option, the server
     discards the Renew message and responds with a Reply message

In 4.6, it might be worth adding that the client should treat the =
failure to acquire an address as a result of a DaD conflict to be =
equivalent to not having received that address, insofar as it determined =
how it behaves when renewing/rebinding/confirming.


From nobody Mon Dec 15 14:39: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 30FD31A1DE2 for <dhcwg@ietfa.amsl.com>; Mon, 15 Dec 2014 14:39:55 -0800 (PST)
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 j-4ExI5ddMwz for <dhcwg@ietfa.amsl.com>; Mon, 15 Dec 2014 14:39:52 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B3981A0248 for <dhcwg@ietf.org>; Mon, 15 Dec 2014 14:39:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8416; q=dns/txt; s=iport; t=1418683192; x=1419892792; h=from:to:subject:date:message-id:mime-version; bh=Yqg85D0mS3X+7Hz9pHdPtVacJfoHMQ47m1yySaaA2jc=; b=ibMpdp6uVcl5UQqFMWSqg5vO+UZ385N2OjnzMhxM6AhFczKB5HENZdTe 6GnglKaI+svCnXCr4n6EFE1RDs0VNRKHc6f42L/QinjrspjrxVec5VXE3 AGpeco3kN47322DZoWAObeejCaOw27N0UwjAUe/+kIKoQEecUjaNIEKU2 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcGAOdhj1StJssW/2dsb2JhbABagkOBFVkDtjiNOYFphXICgTYBAQEBAX2EDgEEJwIERhgBAihWJgEEG4gkDa5vpgYBAQEBBgIBH48QEQEfg06BEwWOAoM+hjwwgi6IAIIWgzgig2yBejl+AQEB
X-IronPort-AV: E=Sophos;i="5.07,582,1413244800";  d="scan'208,217";a="275493431"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 15 Dec 2014 22:39:50 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id sBFMdlnJ004874 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Mon, 15 Dec 2014 22:39:48 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.111]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0195.001; Mon, 15 Dec 2014 16:39:47 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: IPR Issue with draft-ietf-dhc-dynamic-shared-v4allocation-02
Thread-Index: AdAYtc5tpXN/TkdVRMmnz/BsAx6fUw==
Importance: high
X-Priority: 1
Date: Mon, 15 Dec 2014 22:39:46 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B7676C8@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.196]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B7676C8xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/dsro5v3smhB-BgNooQUJ0_5Dj3k
Subject: [dhcwg] IPR Issue with 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: Mon, 15 Dec 2014 22:39:55 -0000

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

Hi:



We recently concluded a WGLC on the draft-ietf-dhc-dynamic-shared-v4allocat=
ion-02 where Bernie Volz had written in the WGLC initiation (on Oct 12): "T=
here are no IPR claims reported at this time." This was based on what was i=
n the datatracker at that time.



We're not exactly sure of the changes made, but prior to the "IPR Disclosur=
e: Orange's Statement about IPR related to draft-ietf-dhc-dynamic-shared-v4=
allocation-02" email from the IEFT Secretariat on Dec 15th, the datatracker=
 was showing two IPR claims - now it is up to 3 with this latest notificati=
on.



I believe that what happened here was because of the various changes to the=
 document's name as it worked its way through the IETF, the original IPR cl=
aims were lost and only recently re-associated with the later documents. An=
d, that recent queries to the authors regarding IPR for the WGLC triggered =
the latest IPR filing.



Two of the IPR notifications were filed many years ago against an earlier d=
raft, http://datatracker.ietf.org/doc/draft-bajko-pripaddrassign/. The docu=
ment chain now is:

--> draft-bajko-pripaddrassign

--> Replaced by: draft-sun-dhc-port-set-option

--> Replaced by: draft-csf-dhc-dynamic-shared-v4allocation

--> Replaced by: draft-ietf-dhc-dynamic-shared-v4allocation



And, from my understanding, the latest IPR notification updates the earlier=
 http://datatracker.ietf.org/ipr/1119/ with US and Japan patent numbers (I =
am not saying that is the only change; please view all the declarations for=
 yourself)!!



Thus, the question to the WG is whether or not your position on this work w=
ould have been different had you been aware of the IPR claims. If it would =
have affected your position negatively (i.e., you would not have indicated =
that the work should advance), please let the WG know that so we can re-eva=
luate.



Everyone is reminded that IETF intellectual property rights rules are defin=
ed in RFC 3979, "Intellectual Property Rights in IETF Technology." See http=
://datatracker.ietf.org/ipr/.



Also, please be sure that as a document changes its name during its journey=
 through the IETF, that the IPR notifications keep up with the document (if=
 you need assistance here, please let us know).



Sincerely,



- Tomek & Bernie


--_000_489D13FBFA9B3E41812EA89F188F018E1B7676C8xmbrcdx04ciscoc_
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;
	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;}
--></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:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">We recently concluded a WGLC on the draft-ietf-dh=
c-dynamic-shared-v4allocation-02 where Bernie Volz had written in the WGLC =
initiation (on Oct 12): &quot;There are no IPR claims reported at this time=
.&quot; This was based on what was in the datatracker
 at that time.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">We&#8217;re not exactly sure of the changes made,=
 but prior to the &quot;IPR Disclosure: Orange's Statement about IPR relate=
d to draft-ietf-dhc-dynamic-shared-v4allocation-02&quot; email from the IEF=
T Secretariat on Dec 15th, the datatracker was showing
 two IPR claims - now it is up to 3 with this latest notification.<o:p></o:=
p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I believe that what happened here was because of =
the various changes to the document&#8217;s name as it worked its way throu=
gh the IETF, the original IPR claims were lost and only recently re-associa=
ted with the later documents. And, that
 recent queries to the authors regarding IPR for the WGLC triggered the lat=
est IPR filing.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Two of the IPR notifications were filed many year=
s ago against an earlier draft,
<a href=3D"http://datatracker.ietf.org/doc/draft-bajko-pripaddrassign/">htt=
p://datatracker.ietf.org/doc/draft-bajko-pripaddrassign/</a>. The document =
chain now is:<o:p></o:p></p>
<p class=3D"MsoPlainText">--&gt; draft-bajko-pripaddrassign<o:p></o:p></p>
<p class=3D"MsoPlainText">--&gt; Replaced by: draft-sun-dhc-port-set-option=
<o:p></o:p></p>
<p class=3D"MsoPlainText">--&gt; Replaced by: draft-csf-dhc-dynamic-shared-=
v4allocation<o:p></o:p></p>
<p class=3D"MsoPlainText">--&gt; Replaced by: draft-ietf-dhc-dynamic-shared=
-v4allocation<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">And, from my understanding, the latest IPR notifi=
cation updates the earlier
<a href=3D"http://datatracker.ietf.org/ipr/1119/">http://datatracker.ietf.o=
rg/ipr/1119/</a> with US and Japan patent numbers (I am not saying that is =
the only change; please view all the declarations for yourself)!!<o:p></o:p=
></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><b>Thus, the question to the WG is whether or not=
 your position on this work would have been different had you been aware of=
 the IPR claims. If it would have affected your position negatively (i.e., =
you would not have indicated that
 the work should advance), please let the WG know that so we can re-evaluat=
e.<o:p></o:p></b></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Everyone is reminded that IETF intellectual prope=
rty rights rules are defined in RFC 3979, &quot;Intellectual Property Right=
s in IETF Technology.&quot; See
<a href=3D"http://datatracker.ietf.org/ipr/">http://datatracker.ietf.org/ip=
r/</a>.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Also, please be sure that as a document changes i=
ts name during its journey through the IETF, that the IPR notifications kee=
p up with the document (if you need assistance here, please let us know).<o=
:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Sincerely,<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_489D13FBFA9B3E41812EA89F188F018E1B7676C8xmbrcdx04ciscoc_--


From nobody Mon Dec 15 22:42:45 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 AED6D1ACD2E; Mon, 15 Dec 2014 22:42:42 -0800 (PST)
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 TXsPHmXgltYK; Mon, 15 Dec 2014 22:42:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B7C01ACD2B; Mon, 15 Dec 2014 22:42:35 -0800 (PST)
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.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141216064235.5220.77737.idtracker@ietfa.amsl.com>
Date: Mon, 15 Dec 2014 22:42:35 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/oos0aIFZTAXJ9MmBuWZ3ACcSeAE
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-access-network-identifier-05.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: Tue, 16 Dec 2014 06:42: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-05.txt
	Pages           : 20
	Date            : 2014-12-15

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-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-access-network-identifier-05


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 Dec 17 12:04:20 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 EE3911A047A for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 12:04:17 -0800 (PST)
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 aV9oQQCIXInt for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 12:04:16 -0800 (PST)
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 B4F9F1A7001 for <dhcwg@ietf.org>; Wed, 17 Dec 2014 12:04:16 -0800 (PST)
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 20C5DDA0107 for <dhcwg@ietf.org>; Wed, 17 Dec 2014 20:04:20 +0000 (UTC)
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 Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 4468B53E07D for <dhcwg@ietf.org>; Wed, 17 Dec 2014 12:03:46 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 17 Dec 2014 12:03:46 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <0FE7102D-39A6-4245-A07A-B70C945FAE8F@nominum.com>
Date: Wed, 17 Dec 2014 15:03:28 -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)
X-Originating-IP: [71.233.43.215]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/km0eGopxCGFGMWkW_D56eVw3oiI
Subject: [dhcwg] AD review of draft-ietf-dhc-dhcpv6-load-balancing
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, 17 Dec 2014 20:04:18 -0000

This document is not ready for publication as a proposed standard.   The =
main problem is that it's woefully underspecified, because RFC 3074 was =
woefully underspecified, and so it gets some key points wrong.

In section 3.2, the text appears to be saying that in a DHCPv6 failover =
setup, a RENEW with a server identifier should be ignored if the load =
balancing algorithm doesn't identify the client as belonging to that =
server.   This is problematic, for two reasons.   First, it leads to the =
client attempting to renew multiple times, resulting in an increased =
load on the server.   Second, a REBIND would presumably be answered by =
both servers, so it wouldn't necessarily correct the problem.

But this leads to the reason I think this is not ready for publication: =
RFC 3074 never actually specifies under what circumstances load =
balancing is done: it leaves it up to the implementation.   It kind of =
implies that load balancing should be done on all requests.   But in =
fact it only ever mentions DHCPDISCOVER.   And indeed, I just looked at =
the ISC implementation, and it only does load balancing on DHCPDISCOVER.

Section 2 of this document suggests that load balancing is done for =
_all_ client-sourced messages, but that would mean that a REBIND message =
wouldn't get a response from the non-balancing server, which in turn =
would mean that the client's lease would have to expire before it could =
rebind to the correct server.

There are a couple of ways this could be addressed.   One way would be =
to just take out section 3.2.  Another would be to say in section 3.2 =
that if the server identifier doesn't match the recipient's server =
identifier, but the load balancing algorithm says that the server should =
answer for this client, and the server can answer, it should answer, and =
leave the rest of the text the same.   Of course, there's no way to be =
sure the _client_ will do the right thing with such a response.

Do we have any data about operational problems in this scenario with =
DHCPv4?

Anyway, this needs to be resolved before I can last-call the document.   =
Sorry for not catching this in previous reviews.


From nobody Wed Dec 17 14:18:52 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 01AE81A8736 for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 14:18:50 -0800 (PST)
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 tmQpChO593sl for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 14:18:47 -0800 (PST)
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 8019B1A87C5 for <dhcwg@ietf.org>; Wed, 17 Dec 2014 14:18:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6855; q=dns/txt; s=iport; t=1418854728; x=1420064328; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ID/x48tCjyO9a2kp8Y5nmJmUy8WVEerVDWPP0B63U5g=; b=ldmdzPkBpFUR4CwFeECFUyXgw8U4manEcoji17m50VYjUs+P5JKPWxPG vKXK0qdE7qfVJa0tjkThX5uwKtHbKlmz8Pp6Yf4nbw8g5kK4PClUz+ARq UuhhblUz/MNV/Hm3LFyAAE/jrDzQVQ53ZU7dqY57s/KIMvo9MaZRD1xjb 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApkFADcAklStJV2P/2dsb2JhbABQCoMGUlgExXMKhXICgSMWAQEBAQF9hAwBAQEDAQEBATc0Aw0HBAIBCBEEAQELFAkHJwsUCQgCBAESCBOICQgN1RoBAQEBAQEBAQEBAQEBAQEBAQEBAQETBI8WKzgGgxCBEwWMMoFWiXuMfYM4IoIAHIFQb4FFfgEBAQ
X-IronPort-AV: E=Sophos;i="5.07,596,1413244800"; d="scan'208";a="106434984"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-2.cisco.com with ESMTP; 17 Dec 2014 22:18:46 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id sBHMIjPq017183 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Dec 2014 22:18:45 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.84]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Wed, 17 Dec 2014 16:18:45 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] AD review of draft-ietf-dhc-dhcpv6-load-balancing
Thread-Index: AQHQGjSrui+8J4NAqkiN107VmBn0eJyUTGIQ
Date: Wed, 17 Dec 2014 22:18:45 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B7828B1@xmb-rcd-x04.cisco.com>
References: <0FE7102D-39A6-4245-A07A-B70C945FAE8F@nominum.com>
In-Reply-To: <0FE7102D-39A6-4245-A07A-B70C945FAE8F@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.209]
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/cjMlL3-wkciiXnokLut9WW21S50
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-dhcpv6-load-balancing
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, 17 Dec 2014 22:18:50 -0000

Ted:

While I'd "vote" to remove Section 3.2 ... (personally) I didn't like this =
concept. If I recall, Andre (perhaps others) wanted this to move the client=
's interaction to the "correct" server. But I always felt that having the c=
lient retransmit Renews and having the elements (relay, servers) have to pr=
ocess these far outweighed any benefit from it -- obviously this happens wh=
en that server is down, but then only one server is dropping the packets.

The server I work on does not do this for v4 (or v6) - for packets where th=
e Server-ID is included (and mandated by RFC 3315), load balancing doesn't =
apply and the requested server answers - period -- this is as described in =
3.1 (without the exception).

But I think your statement "Second, a REBIND would presumably be answered b=
y both servers, so it wouldn't necessarily correct the problem." is not cor=
rect. See section 3.1 - a REBIND does not contain a Server ID option so the=
 server that is supposed to respond to this client's hash bucket is the onl=
y that responds. So, both server would NOT answer this request. (This does =
assume that the servers know when each other is operational - hence why thi=
s load-balancing feature is tied to failover -- and it says as much "Since =
the servers were exchanging lease information,". When the failover communic=
ation is interrupted, both servers would indeed be likely to respond as loa=
d balancing would not be used.)

Also, at least in a failover situation, even if all clients were serviced b=
y only one of the servers (say they all obtained their lease when only one =
of the servers was running and are happily renewing their leases), what's t=
he harm? Failover doesn't mean you have twice the throughput - since you mu=
st have proper server capacity to handle all of the clients from a single s=
erver (the partner server may be down for an extended period). And, eventua=
lly clients will SOLICIT and then move to the proper server.

If section 3.2 is dropped, I also think we should fix 3.1 to change the SHO=
ULD into a MUST, and drop ", with the exception of RENEWs." Perhaps the MUS=
T should be used anyway?



I'd just like to also confirm:

>The main problem is that it's woefully underspecified

Is there more than what followed (Section 2 & 3.2) that needs to be "specif=
ied"?

And:

> Section 2 of this document suggests that load balancing is done for _all_=
 client-sourced messages

   2.  Background and External Requirements

      The requirements for DHCPv6 are substantially the same as for DHCPv4,
      replacing DHCPDISCOVER with SOLICIT, DHCPREQUEST with REQUEST,
      CONFIRM, RENEW, or REBIND (as appropriate), etc.

Did you have any suggestion for how to deal with this? It was I believe int=
ended to indicate that DHCPREQUEST in v4 could mean multiple things. Note t=
hat this is addressing the requirements, not the operation (though it is in=
teresting that this section in 3074 doesn't mention DHCPREQUEST). Perhaps t=
his can just be: "The requirements for DHCPv6 are substantially the same as=
 for DHCPv4."?



Note that when 3074 was done, we were thinking there were two models for lo=
ad balancing:
- One is that you had a server (or pair of failover partners) that answered=
 DHCP requests for a subset of the client pool. In this model, there was no=
 desire to have a server (or failover partners) handle clients from another=
 hash bucket. Ignoring failover, suppose you had 4 servers - each would tak=
e 1/4 the clients. You could replace those 4 servers with 4 failover -pairs=
 (each failover pair handling its 1/4 of the clients -- note that you could=
 do load balancing between the 1/4 clients (each servicing 1/8) when using =
failover).=20
- The other is that you had one failover pair servicing your clients and yo=
u wanted to load balancing between these two failover servers (when they we=
re both running and in communication).

I think the first model is probably of much less interest these days (thoug=
h it may be interesting for a scalable cloud solution where the hash bucket=
 is managed dynamically to distribute the load to various "request" process=
ors.)



Thanks for your review!

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Wednesday, December 17, 2014 3:03 PM
To: dhcwg
Subject: [dhcwg] AD review of draft-ietf-dhc-dhcpv6-load-balancing

This document is not ready for publication as a proposed standard.   The ma=
in problem is that it's woefully underspecified, because RFC 3074 was woefu=
lly underspecified, and so it gets some key points wrong.

In section 3.2, the text appears to be saying that in a DHCPv6 failover set=
up, a RENEW with a server identifier should be ignored if the load balancin=
g algorithm doesn't identify the client as belonging to that server.   This=
 is problematic, for two reasons.   First, it leads to the client attemptin=
g to renew multiple times, resulting in an increased load on the server.   =
Second, a REBIND would presumably be answered by both servers, so it wouldn=
't necessarily correct the problem.

But this leads to the reason I think this is not ready for publication: RFC=
 3074 never actually specifies under what circumstances load balancing is d=
one: it leaves it up to the implementation.   It kind of implies that load =
balancing should be done on all requests.   But in fact it only ever mentio=
ns DHCPDISCOVER.   And indeed, I just looked at the ISC implementation, and=
 it only does load balancing on DHCPDISCOVER.

Section 2 of this document suggests that load balancing is done for _all_ c=
lient-sourced messages, but that would mean that a REBIND message wouldn't =
get a response from the non-balancing server, which in turn would mean that=
 the client's lease would have to expire before it could rebind to the corr=
ect server.

There are a couple of ways this could be addressed.   One way would be to j=
ust take out section 3.2.  Another would be to say in section 3.2 that if t=
he server identifier doesn't match the recipient's server identifier, but t=
he load balancing algorithm says that the server should answer for this cli=
ent, and the server can answer, it should answer, and leave the rest of the=
 text the same.   Of course, there's no way to be sure the _client_ will do=
 the right thing with such a response.

Do we have any data about operational problems in this scenario with DHCPv4=
?

Anyway, this needs to be resolved before I can last-call the document.   So=
rry for not catching this in previous reviews.

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


From nobody Wed Dec 17 18:49:47 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 8430A1A006F for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 18:49:46 -0800 (PST)
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 CiL8rAegmprr for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 18:49:45 -0800 (PST)
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 3D70D1A0029 for <dhcwg@ietf.org>; Wed, 17 Dec 2014 18:49:45 -0800 (PST)
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 27B54DA0108 for <dhcwg@ietf.org>; Thu, 18 Dec 2014 02:49:50 +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 Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 13A3F53E084; Wed, 17 Dec 2014 18:49:14 -0800 (PST)
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; Wed, 17 Dec 2014 18:49:13 -0800
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: <489D13FBFA9B3E41812EA89F188F018E1B7828B1@xmb-rcd-x04.cisco.com>
Date: Wed, 17 Dec 2014 21:48:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <F3B109F2-52EA-4305-BAA2-4DB3C6C4CEDC@nominum.com>
References: <0FE7102D-39A6-4245-A07A-B70C945FAE8F@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B7828B1@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/V5TxVhdOe0PQzpymXU_wb9OBpx4
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-dhcpv6-load-balancing
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, 18 Dec 2014 02:49:46 -0000

On Dec 17, 2014, at 5:18 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> See section 3.1 - a REBIND does not contain a Server ID option so the =
server that is supposed to respond to this client's hash bucket is the =
only that responds.

Right, but that behavior is incorrect.   If a client is sending REBINDs, =
it might be because the server it's bound to is refusing to answer due =
to load balancing.  But it also might also be because it's bound to the =
correct server, and that other server is no longer reachable by the =
client.   In that case, the client will fail to renew its lease, because =
the backup server won't answer.   Not only that, but in this case the =
client would simply fail to get a lease until the problem with the =
unreachable server is corrected.

Of course, Delayed Service is supposed to take care of that, but if =
Delayed Service is configured, then presumably the server that is =
refusing service under 3.2 will allow service once the Delayed Service =
interval has elapsed.   And so the whole thing will have been for =
naught.

> Also, at least in a failover situation, even if all clients were =
serviced by only one of the servers (say they all obtained their lease =
when only one of the servers was running and are happily renewing their =
leases), what's the harm? Failover doesn't mean you have twice the =
throughput - since you must have proper server capacity to handle all of =
the clients from a single server (the partner server may be down for an =
extended period). And, eventually clients will SOLICIT and then move to =
the proper server.

Right.

> Is there more than what followed (Section 2 & 3.2) that needs to be =
"specified"?

Well, it's pretty clear that the logic of doing load balancing on =
non-solicit messages hasn't been explored in any depth... :)

> Did you have any suggestion for how to deal with this? It was I =
believe intended to indicate that DHCPREQUEST in v4 could mean multiple =
things. Note that this is addressing the requirements, not the operation =
(though it is interesting that this section in 3074 doesn't mention =
DHCPREQUEST). Perhaps this can just be: "The requirements for DHCPv6 are =
substantially the same as for DHCPv4."?

Only do load balancing on solicits.   The problem isn't actually in this =
document; it's that this document relies on 3074, which is =
underspecified.   So this document needs to correct for that.


From nobody Wed Dec 17 19:32:07 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 890CE1A011D for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 19:32:05 -0800 (PST)
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 q1bak40kn7j9 for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 19:32:03 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E1EE1A0110 for <dhcwg@ietf.org>; Wed, 17 Dec 2014 19:32:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6685; q=dns/txt; s=iport; t=1418873524; x=1420083124; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=t5kggCYcIp/Ch80g2d96K0TgBg889JYhUgj/8OqKlKQ=; b=m03zukkSfkyewgvRFwGwhUpqWOCX/588mfe4W695L8zsEYGJzEjgN7Ha gO99TOwuu6JJEPspxs34UFy/7kYE4FhH35AkY2hVBqsXi2yvvoVFpG7aS kTO2GK0uSydwXitA+uzbf9WQFdnesqPwSPzkmXORoKnKQ/MQ7SJArt8PA M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AssEAFJJklStJssW/2dsb2JhbABahDAEzAACgTIBAQEBAX2EDAEBAQMBOisMCAUHBAIBCBEEAQEBChQJBzIUCQgCBA4FCIgcCNUUAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4oKhH06MQcGgxCBEwEEjDGBVpovIoIAHIFQb4FFfgEBAQ
X-IronPort-AV: E=Sophos;i="5.07,598,1413244800"; d="scan'208";a="274251736"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 18 Dec 2014 03:32:02 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sBI3Vxap015069 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Dec 2014 03:32:00 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.84]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Wed, 17 Dec 2014 21:31:58 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] AD review of draft-ietf-dhc-dhcpv6-load-balancing
Thread-Index: AQHQGjSrui+8J4NAqkiN107VmBn0eJyUTGIQgAC+FwD//5z4sA==
Date: Thu, 18 Dec 2014 03:31:58 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B782FE0@xmb-rcd-x04.cisco.com>
References: <0FE7102D-39A6-4245-A07A-B70C945FAE8F@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B7828B1@xmb-rcd-x04.cisco.com> <F3B109F2-52EA-4305-BAA2-4DB3C6C4CEDC@nominum.com>
In-Reply-To: <F3B109F2-52EA-4305-BAA2-4DB3C6C4CEDC@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.252.248]
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/NdFQN1skx7sN-BLMr7RQURF66OA
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-dhcpv6-load-balancing
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, 18 Dec 2014 03:32:05 -0000

>Only do load balancing on solicits.   The problem isn't actually in this d=
ocument; it's that this document relies on 3074, which is underspecified.  =
 So this document needs to correct for that.

There's also Information-Request.

And, there's Confirm that is not sent to a specific server and having both =
respond is probably unnecessary (it may not do any harm since they should g=
ive the same answer).

I also think that Rebinds are fine to do load balancing on - at least when =
failover is present (i.e. that the partner is alive). A client that arrives=
 at Rebind might have done so because the failover partner that was to serv=
ice it just came back up (i.e., since the last Renew retransmission). Yes, =
there are isolated cases where this ends up in not given the client service=
, but in that case other things are broken (such as Relays are not forwardi=
ng the packets to both servers and best to learn that earlier).

So, we're really back to all the messages that don't specify a server-id op=
tion?

>Well, it's pretty clear that the logic of doing load balancing on non-soli=
cit messages hasn't been explored in any depth... :)

Hum ... we've being doing that for DHCPv4 for many years with it deployed i=
n large SP networks and also are doing it for DHCPv6 - we do more than just=
 DHCPDISCOVER and Solicit. Things have been working quiet well (these are w=
ith failover and we use information about the failover state when deciding =
whether to process the received packet or not).

We do not do Renews and don't intend to.


Looking back at the draft, I do see that we are conflating the two differen=
t architectures I had outlined earlier and that is probably where things go=
 bad as the rules are a bit different.

In the case were you want a server (or failover partners) to process only a=
 subset of the clients, the rules can be very simple - discard packets are =
not in the server's hash bucket assignments. This can be done regardless of=
 the packet type and whether the server-id option is present. Though it als=
o means you only need to apply the logic to packets where the server-id opt=
ion is not present (since the server-id option will suffice in dropping all=
 other packets not for the server).

In the case of failover load balancing (i.e., where you want each server to=
 handle "half" of the clients), the rules are different depending on the fa=
ilover state. In normal failover communication state, load balancing applie=
s; when not in normal communication, load balancing must be disabled.


And, if the goal is for use with failover, we should wait until failover is=
 available (or further along)?

And, if the goal is general load balancing (not tied to failover), then any=
thing to do with failover (or any redundancy) should be removed.

In the case where there isn't any common database (whether failover or not)=
, you really have to have the client stick with the server that is to servi=
ce it - there is no redundancy goal. So whether you do the hashing on some =
or all client packets doesn't really matter. In principle though, it seems =
that doing those where there is no server id option is simpler and better a=
s it allows a client that previously communicated with a server (regardless=
 of load balancing) to keep working what that server (if the server is stil=
l present). But when that client gets to a packet which is not directed at =
a specific server, then doing the load balancing is appropriate (Solicit, I=
nformation-Request, Rebind, Confirm).

If there is a common backing store (whether failover or otherwise), clients=
 can be serviced by a different server when that server is known not to be =
response - those load balancing should only be done when the partner is kno=
wn to be up and fully responsive. But it turns out the same packets are loa=
d balanced (Solicit, Information-Request, Rebind, Confirm).

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Wednesday, December 17, 2014 9:49 PM
To: Bernie Volz (volz)
Cc: dhcwg
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-dhcpv6-load-balancing

On Dec 17, 2014, at 5:18 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> See section 3.1 - a REBIND does not contain a Server ID option so the ser=
ver that is supposed to respond to this client's hash bucket is the only th=
at responds.

Right, but that behavior is incorrect.   If a client is sending REBINDs, it=
 might be because the server it's bound to is refusing to answer due to loa=
d balancing.  But it also might also be because it's bound to the correct s=
erver, and that other server is no longer reachable by the client.   In tha=
t case, the client will fail to renew its lease, because the backup server =
won't answer.   Not only that, but in this case the client would simply fai=
l to get a lease until the problem with the unreachable server is corrected=
.

Of course, Delayed Service is supposed to take care of that, but if Delayed=
 Service is configured, then presumably the server that is refusing service=
 under 3.2 will allow service once the Delayed Service interval has elapsed=
.   And so the whole thing will have been for naught.

> Also, at least in a failover situation, even if all clients were serviced=
 by only one of the servers (say they all obtained their lease when only on=
e of the servers was running and are happily renewing their leases), what's=
 the harm? Failover doesn't mean you have twice the throughput - since you =
must have proper server capacity to handle all of the clients from a single=
 server (the partner server may be down for an extended period). And, event=
ually clients will SOLICIT and then move to the proper server.

Right.

> Is there more than what followed (Section 2 & 3.2) that needs to be "spec=
ified"?

Well, it's pretty clear that the logic of doing load balancing on non-solic=
it messages hasn't been explored in any depth... :)

> Did you have any suggestion for how to deal with this? It was I believe i=
ntended to indicate that DHCPREQUEST in v4 could mean multiple things. Note=
 that this is addressing the requirements, not the operation (though it is =
interesting that this section in 3074 doesn't mention DHCPREQUEST). Perhaps=
 this can just be: "The requirements for DHCPv6 are substantially the same =
as for DHCPv4."?

Only do load balancing on solicits.   The problem isn't actually in this do=
cument; it's that this document relies on 3074, which is underspecified.   =
So this document needs to correct for that.


From nobody Wed Dec 17 19:48: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 1626F1A0154 for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 19:48:26 -0800 (PST)
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 h3APsg6xUf0O for <dhcwg@ietfa.amsl.com>; Wed, 17 Dec 2014 19:48:22 -0800 (PST)
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 DEEC01A014C for <dhcwg@ietf.org>; Wed, 17 Dec 2014 19:48:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17529; q=dns/txt; s=iport; t=1418874502; x=1420084102; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=+dgFwuEN+IkBJGgQGXK+2GFA96fQEkQaQVW0S2TP+8M=; b=YxQjTvTin3FhXEJJ69vpW8Z6CJaB+rREBQKNf18RM3J/B1hnhv+OdMdP RfH2B1212cQr8bawCkFX2NcsUEr4b0WB9dzXy+OivrjctC6UskDXWFhMX DebR51P+kFnEfOewwNOwHNoZxC7lVsvriVsMri0RZjGu8ZFIuVSGoDtCs U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYFAP9NklStJV2c/2dsb2JhbABagwZSWAS1JJBgCoVyAoEcFgEBAQEBfYQMAQEBBAEBATcNJxcEAgEIDgMEAQELFAkHJwsUCQgCBAESCBOIEQ3DWZEwAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSKCoUQARIUJhIGgxCBEwWOB4R9gX+Cfg2CVIIxhRaCVYM4IoNsb4EDAR8EHn4BAQE
X-IronPort-AV: E=Sophos;i="5.07,598,1413244800"; d="scan'208";a="380910877"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 18 Dec 2014 03:48:20 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id sBI3mKX4020690 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Dec 2014 03:48:20 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.84]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0195.001; Wed, 17 Dec 2014 21:48:20 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <mellon@fugue.com>, dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC review of draft-ietf-dhc-dhcpv6-stateful-issues
Thread-Index: AQHQGJ6ImPQt3L8YuUS0fS8iJRAS6JyUtlJA
Date: Thu, 18 Dec 2014 03:48:20 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B783037@xmb-rcd-x04.cisco.com>
References: <3480FD7D-80E9-47B9-852B-0EDD2F887BF1@fugue.com>
In-Reply-To: <3480FD7D-80E9-47B9-852B-0EDD2F887BF1@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.252.248]
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/R89KHExecnzr4_wmCFOwH8lYfr8
Subject: Re: [dhcwg] WGLC review 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, 18 Dec 2014 03:48:26 -0000

Ted:

Thanks for your careful review (and to the others that provided comments, w=
e are being to work through these).

I do have some comments  (I have not yet had an opportunity to review the i=
ssues with Marcin):

For 4.4.3, your comment:

I think this is bad advice:

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

Applies to text which we did not change and was copied directly from RFC 33=
15. While I think the original assumption agrees with your thoughts, it cle=
arly isn't written that way. But we are trying to minimize the fixes to 331=
5 here to those related to the issue. So, this one is better handled (if no=
t already) in the RFC 3315bis work.


The same issue exists for the text in section 4.4.6 on which you commented =
- What if the server has no record that it sent a unicast option, but is co=
nfigured to support unicast? We again can raise this as a ticket for RFC 33=
15bis.


And, in another comment regarding text in 4.4.3, you  suggested revised tex=
t for RFC 3315. But that text specifically includes PD related text which R=
FC 3315 does not have. So, adding that text would be rather strange? Your p=
roposed text would be more appropriate for RFC 3315 bis work. Your text was=
, and the 2nd sentence is the issue related to PD.

NEW: For IAs to which addresses have been assigned, the client includes a c=
orresponding IA option containing an IA Address option for each address ass=
igned to the IA.   For IAs to which prefixes have been assigned, the client=
 includes a corresponding IA option containing an IA Prefix option for each=
 prefix assigned to the IA.   The client MUST NOT include addresses or pref=
ixes in any IA option that the client did not obtain from the server or tha=
t are no longer valid (that have have a zero valid lifetime).


- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Monday, December 15, 2014 2:36 PM
To: dhcwg
Subject: [dhcwg] WGLC review of draft-ietf-dhc-dhcpv6-stateful-issues

Aside from this rather voluminous set of nits and comments, the document lo=
oks good and I support advancing it.   Thanks for the hard work on this.   =
I will become less and less available between now and 1/5, so please don't =
delay updating the document while waiting for a response from me.   I will =
review whatever comments follow when I get back as part of what I assume wi=
ll be a request for publication.

My comments/nits:

The abstract is a bit colloquial and contains references to other documents=
 that I don't think are necessary to understand what this document does, an=
d actually prevent people who don't already know what the document does fro=
m quickly figuring it out.   I'm a bit on the warpath about long abstracts:=
 they should really be the elevator pitch for your document.   Suggestion:

OLD:
   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 has since shoe-horned a new option 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.

NEW:
   The DHCPv6 specification defines two stateful options, IA_NA
   and IA_TA, but does not anticipate the development of additional
   stateful options.  DHCPv6 Prefix Delegation adds the IA_PD option,
   which is stateful.  Applications that use IA_NA and IA_PD
   together have revealed issues that need to be addressed.  This
   document updates RFC 3315 and RFC 3633 to address these issues.

In the introduction, don't use "shoe-horned."   Just say "added."   The RFC=
 editor would probably ding you on this, but I'm saying it now in hopes tha=
t more people will read this review than would read the interaction with th=
e RFC editor.   Colloquialisms make documents harder to read for anyone who=
 is not familiar with the colloquialism, which is at present the majority o=
f readers of RFCs.

OLD:
   This document describes a number of problems encountered with
   coexistence of the IA_NA and IA_PD option types and changes to the
   DHCPv6 protocol specifications to address these problems.
NEW:
   This document describes a number of problems encountered with
   coexistence of the IA_NA and IA_PD option types and specifies=20
   changes to the DHCPv6 protocol to address these problems.

(making it a compound sentence instead of a sentence with a compound phrase=
 makes it less ambiguous and hence easier to understand.)

This doesn't make sense:
   DHCPv6 assigned temporary addresses also
   have limited value when DHCPv6 is used for non-temporary address
   assignment, as the privacy issues identified for IPv6 stateless
   address assignment ([RFC4941]) do not apply to DHCPv6 assignments.

The expected use of IA_TA is that you would acquire temporary addresses and=
 a non-temporary address; the temporary addresses are used for outgoing con=
nections; the non-temporary address is used for incoming connections and is=
 optionally entered in the DNS.   As long as the host enforces the separate=
 uses of temporary and non-temporary addresses, it all works: an off-networ=
k listener will not know that the IA_TA and IA_NA addresses belong to the s=
ame host.   That's a big if, but that's not our problem.

I think the gist of this paragraph is correct, but the sentence above is in=
correct and should just be deleted.  I also think IA_TA is completely out o=
f scope for this document, not just mostly out of scope, for the reason sta=
ted in the first sentence in the paragraph.   I notice that IA_TA is refere=
nced throughout the document as equivalent to IA_NA; if indeed the assertio=
n here is correct, then it shouldn't be mentioned again in the document.   =
I think that would make the document a bit clearer.

Maybe make the second sentence a bulleted list:

   If a client requests multiple IA option types, but the server is
   configured to only offer a subset of them, the client could react in
   several ways.  Reset the state machine and continue to send Solicit
   messages, create separate DHCP sessions for each IA option type and
   continue to Solicit for the unfulfilled IA options, or it could
   continue with the single session, and include the unfulfilled IA
   options in subsequent messages to the server.

The case mentioned in the second sentence would happen whenever such a brok=
en client is on a network with no DHCP server.   Does it really need to be =
mentioned here?

   Reseting the state machine and continuing to send Solicit messages
   may result in the client never completing DHCP and is generally not
   considered a good solution.  It can also result in a request storm if
   the client does not appropriately rate limit its sending of Solicit
   messages.

OLD:
   This leaves a single DHCP session and state machine which is the
   proposed solution.  Here, the client can use what it is able to
   obtain and can continue to request what it was previously unable to
   obtain while maintaining a single session and state machine.

   Proposed solution: the client should keep a single session with the
   server and include the missing options in subsequent messages
   (Request, Renew, and Rebind) to the server.
NEW:
   We have chosen the remaining option: a single DHCP session and state
   machine.  The client maintains a single session and state machine.
   It uses the best configuration it is able to obtain during any
   configuration exchange.   But it continues, in each subsequent
   configuration exchange, to request all the configuration information
   it is programmed to try to obtain, including any stateful configuration
   options for which no results were returned in previous exchanges.

In 4.1 paragraph 1 you use the terms "encapsulation" and "top level".   The=
se should be defined in the glossary, ideally by referring to their definit=
ions either in RFC3315, if possible, or in RFC 7227, which has a really goo=
d discussion in section 9 on the topic of encapsulation, although it doesn'=
t explicitly hit on the topic of "top level" options.   Actually, the term =
top level is used but not defined in 7227, and vaguely referenced, but neve=
r named nor discussed explicitly that I can see in 3315, so this should jus=
t be explained in the glossary.  I would say something like this:

   Top Level options
      Top level options are DHCPv6 options that are not encapsulated
      within other options, excluding the Relay-Message option.   Options
      encapsulated by Relay-message options, but not by any other option,
      are still top-level options, whether they appear in a relay agent
      message or a server message.

If this is an update to a standard, then we have chosen a solution--we aren=
't just proposing one.  The phrasing you are using here would be appropriat=
e in an experimental doc, but (ironically) is not appropriate in a proposed=
 standard:

OLD:
   Therefore, the proposed solution is:
NEW:
   We have chosen the following solution:

However, this seems like it's part of the update.   Is there a place in RFC=
 3315 where this could be said to be added?   This is clearly normative tex=
t.

I don't think this is quite right:

     -  The client MAY choose a less-preferred server if that server
        has a better set of advertised parameters, such as the
        available options advertised in IAs.

I suggest:

     -  The client MAY choose a less-preferred server if that server
        has a better set of advertised parameters, such as the
        available set of IAs, as well as the set of non-IA options
        advertised.

You could leave out the final dependent clause if you like, but I think the=
 way I've restated it is closer to combining what was previously intended w=
ith what you need to change.

Shouldn't the following text be normative?

   It is important to note that the receipt of an Advertise message
   without any addresses and delegated prefixes does not imply that the
   client should restart the Solicit retransmissions timers.  Doing so
   would lead to a Solicit/Advertise storm.

There's quite a bit of text in subsequent sections that looks something lik=
e this:

   Proposed solution: The server MUST set the T1/T2 times in all IA

The same comment I made earlier applies here.   You should just substitude =
"Solution: " in place of "Proposed Solution" in each of these instances.

This is really confusing, so I suggest changing it:
OLD:
     To extend the valid and preferred lifetimes for the addresses
     associated with an IA, the client sends a Renew message to the
     server from which the client obtained the addresses in the IA
     containing an IA option for the IA.  The client includes IA Address
     options in the IA option for the addresses associated with the IA.
     The server determines new lifetimes for the addresses in the IA
     according to the administrative configuration of the server.  The
     server may also add new addresses to the IA.  The server may remove
     addresses from the IA by setting the preferred and valid lifetimes
     of those addresses to zero.
NEW:
     To extend the valid and preferred lifetimes for the addresses
     assigned to an IA, the client sends a Renew message to the
     server from which the addresses were obtained,
     which includes an IA option for the IA whose whose address
     lifetimes are to be extended.  The client includes IA Address
     options within the IA option for the addresses assigned to the IA.
     The server determines new lifetimes for these addresses
     according to the administrative configuration of the server.  The
     server may also add new addresses to the IA.  The server can remove
     addresses from the IA by returning IA Address options for such
     addresses with preferred and valid lifetimes set to zero.

I think this is bad advice:

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

Can the client send a Renew or Rebind after zero seconds?   That would be a=
t its discretion, but obviously bad.   I think the right advice is to say t=
hat the client should choose a renew and rebind interval that is consistent=
 with the valid and preferred times of all the addresses and prefixes recei=
ved: if there are addresses and/or prefixes with preferred times, then the =
renewal and rebind times should result in those addresses and/or prefixes b=
eing renewed well before the preferred lifetime expires; if there are addre=
sses with preferred lifetimes of zero, but residual valid lifetimes, these =
should not be renewed.   That might be too complicated for this document, t=
hough--if you prefer, you could just say "at the client's discretion, but n=
o sooner than X," but then we'd have to argue about what X should be.

I think the following is unclear.   I've proposed a clearer version that I =
think says what was intended, but it was unclear, so I don't know if I corr=
ectly understood what was intended.   Also, I think this applies to Renew a=
nd Rebind messages, according to the preceding text, so the specific mentio=
n of Reply messages seems wrong, and I left it out of my proposed text:

OLD:
     The client includes an IA option with all addresses currently
     assigned to the IA in its Renew message.  The client also includes
     IA options for all other bindings for which the client desires to
     extend the lifetimes of addresses.  The client MUST only include
     addresses in the IA that the client obtained from the server and
     are still valid (have non-zero lifetime).
NEW:
     For IAs to which addresses have been assigned, the client includes
     a corresponding IA option containing an IA Address option for each
     address assigned to the IA.   For IAs to which prefixes have been
     assigned, the client includes a corresponding IA option containing
     an IA Prefix option for each prefix assigned to the IA.   The client
     MUST NOT include addresses or prefixes in any IA option that the
     client did not obtain from the server or that are no longer valid
     (that have have a zero valid lifetime).

You'll probably get a DISCUSS on this:

     If the client receives a Reply message with a Status Code
     containing UnspecFail, the server is indicating that it was unable
     to process the message due to an unspecified failure condition.  If
     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.

You really need to say something about how this rate limiting is done, or e=
lse it's too vague to really be meaningful.   For example, the client could=
 send no more frequently than every thirty seconds, and on a small network =
this would be no problem, but it would be absolutely nuts on a really big n=
etwork.

In the following text, I am left wondering on what basis the client should =
choose between the two alternatives:

     The client uses addresses and other information from any IAs that
     do not contain a Status Code option with the NoAddrsAvail code.
     For each IA for which the client receives NoAddrsAvail status code
     the client has the following choices:

     -  The client includes the IA with no addresses in subsequent Renew
        and Rebind messages sent to the server, to request creation of
        the binding for the IA.

     -  Tries another server (by restarting the DHCP server discovery
        process).

I think it's that if the client can't continue to operate without the resou=
rce it's trying to renew, it will choose to restart the process; if it can,=
 it doesn't restart the process.   Also, does this text apply just to addre=
sses, or also to prefixes?

What if the server has no record that it sent a unicast option, but is conf=
igured to support unicast?

     When the server receives a Renew message via unicast from a client
     to which the server has not sent a unicast option, the server
     discards the Renew message and responds with a Reply message

In 4.6, it might be worth adding that the client should treat the failure t=
o acquire an address as a result of a DaD conflict to be equivalent to not =
having received that address, insofar as it determined how it behaves when =
renewing/rebinding/confirming.

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


From nobody Thu Dec 18 04:26:20 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 F1EE51A883B for <dhcwg@ietfa.amsl.com>; Thu, 18 Dec 2014 04:26:18 -0800 (PST)
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 LVWM1QA-UYJ0 for <dhcwg@ietfa.amsl.com>; Thu, 18 Dec 2014 04:26:16 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id D9FA31A6FB9 for <dhcwg@ietf.org>; Thu, 18 Dec 2014 04:26:16 -0800 (PST)
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 A824F2380481; Thu, 18 Dec 2014 07:26:14 -0500 (EST)
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: <489D13FBFA9B3E41812EA89F188F018E1B783037@xmb-rcd-x04.cisco.com>
Date: Thu, 18 Dec 2014 07:25:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <562C38EF-88A7-44C7-A9EE-0FF6EA4808CA@fugue.com>
References: <3480FD7D-80E9-47B9-852B-0EDD2F887BF1@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B783037@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/KOd2E2WjUorR7WfavDPG1_YkDos
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC review 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, 18 Dec 2014 12:26:19 -0000

On Dec 17, 2014, at 10:48 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

Thanks for adding the 3315bis tickets.   I figured that was the right =
way to address the problem, but knew that if I didn't mention it during =
the review, I would forget.

> And, in another comment regarding text in 4.4.3, you  suggested =
revised text for RFC 3315. But that text specifically includes PD =
related text which RFC 3315 does not have. So, adding that text would be =
rather strange? Your proposed text would be more appropriate for RFC =
3315 bis work. Your text was, and the 2nd sentence is the issue related =
to PD.

I see your point, but the problem is that _this_ document is trying to =
fix the problem that occurs when you have IA_NAs and IA_PDs in the same =
message.   So if you never mention IA_PDs, it seems to me that you =
haven't really fixed it, because your new text doesn't apply to IA_PDs.  =
 Is your intention that the update for IA_NAs be sufficient, and that no =
changes are required for IA_PD?   I didn't look closely at 3633, so I =
would have missed that.


From nobody Thu Dec 18 10:12:10 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 39E2B1A1BC0 for <dhcwg@ietfa.amsl.com>; Thu, 18 Dec 2014 10:12:08 -0800 (PST)
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 ZEb9Q0fML9Nc for <dhcwg@ietfa.amsl.com>; Thu, 18 Dec 2014 10:12:01 -0800 (PST)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF4671A1B6D for <dhcwg@ietf.org>; Thu, 18 Dec 2014 10:12:00 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id x13so2358436wgg.19 for <dhcwg@ietf.org>; Thu, 18 Dec 2014 10:11:59 -0800 (PST)
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=GsvAFQcqfqSPIuOlyel3f7+Tkl6kdhIJaUE7lp4vlto=; b=JDCmjC3isgqAc1enKJC3rp1O5YPeUOd99LC2brnHIOXg6Po0t+Ch2Nud3pIcv6zT50 LqpGq2i7/3t7IV7ceszC7uft1P/jdwwZrOLo++E3xvgqryHT1mAKIfu8ulcrjqeOHPzr 19VgEM0f2ihd0vN9eBkJOmyOAwcx7dIuRkShQMyN2CnXjl2+T70EYtd7ahkAI7396kHU lBB/00wWbmClRZiRCnlxOqSmou3nC/DScinlp+g+xKklc0G9x0y+42B909bbtiQTAzmN 70Ypj9KHIGf3nX8IdKPFWrRh9Vo9ci/WtFqvCrclhNhP7D+uEMNHcYFrVltEdp6oiEAZ tAHw==
X-Received: by 10.180.96.97 with SMTP id dr1mr7356843wib.49.1418926319664; Thu, 18 Dec 2014 10:11:59 -0800 (PST)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id cs8sm25656226wib.1.2014.12.18.10.11.57 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Dec 2014 10:11:58 -0800 (PST)
Message-ID: <549318EA.3050400@gmail.com>
Date: Thu, 18 Dec 2014 19:11:54 +0100
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" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B744D04@xmb-rcd-x04.cisco.com>
X-TagToolbar-Keys: D20141218191154630
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/gD-Mpe5WKBrTJP2fAl2BONj081A
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 summary: Success!
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, 18 Dec 2014 18:12:08 -0000

On 26.11.2014 15:59, Bernie Volz (volz) wrote:
> This message starts the DHC working group last call to advance "Issues
> and Recommendations with Multiple Stateful DHCPv6 Options”,
> draft-ietf-dhc-dhcpv6-stateful-issues-09.txt, document as a Standards
> Track (Proposed Standard) RFC. The authors believe that this version is
> ready.
> 
> *Please send your comments by December 12th, 2014.
As Bernie is co-author of this draft, I did assess this WGLC on my own.
We did receive a substantial support and very good feedback for this
last call. I'm very happy to announce that this WGLC is a successful one.

Having said that, there were many comments received, so authors are
requested to address them and upload an updated version. In my opinion
none of the comments received was substantial enough to warrant another
WGLC. Therefore, once an updated version appears and the reviewers
confirm that their comments are addressed, we'll be sending this to the
IESG.

Thanks to everyone who contributed to this effort.

Tomek


From nobody Thu Dec 18 10:46:53 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 8C0891A1B8E for <dhcwg@ietfa.amsl.com>; Thu, 18 Dec 2014 10:46:49 -0800 (PST)
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 4CGnJLNq2pqO for <dhcwg@ietfa.amsl.com>; Thu, 18 Dec 2014 10:46:48 -0800 (PST)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01F6C1A1B80 for <dhcwg@ietf.org>; Thu, 18 Dec 2014 10:46:48 -0800 (PST)
Received: by mail-wi0-f177.google.com with SMTP id l15so2815355wiw.16 for <dhcwg@ietf.org>; Thu, 18 Dec 2014 10:46:46 -0800 (PST)
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=mcUDpwtMGN8Y9UnuMT4C7yjEEc7dvkR6/5ltIAJnQlk=; b=Ad+JYF1E1B2YZUOs/8l76HObEHygXSxJjnXMit/q9BHQIt/wVUMsQDHQvwzZs8R/GH tAjswaPl8bz+qnXOkmS1JBPPCBuia33fKfIY8ugsI+hP3ho8QEg/PFj3rigE0zbAV8G5 9ea/dTHO86KUTA4XpGY3fMuzZquTLC3iluTt+obmx2v9r+ONzuXzLyizQ4BTIazdkmvO nOadFrXw1zHVFiunerEr/3cgJRN9VznH3dgMJV3uspWFKeNd1v1mOiGi5BCdH+yn45Nm tPQl2QWDuZFk2RoR674tp3nTRdgCcFFmY2jb14ICPt/8lQjr11LFZ9FAxwNTjoxBk+xC 06VA==
X-Received: by 10.194.238.3 with SMTP id vg3mr6938612wjc.69.1418928406802; Thu, 18 Dec 2014 10:46:46 -0800 (PST)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id h8sm10944982wiy.17.2014.12.18.10.46.45 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Dec 2014 10:46:45 -0800 (PST)
Message-ID: <54932112.3080008@gmail.com>
Date: Thu, 18 Dec 2014 19:46:42 +0100
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 <dhcwg@ietf.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Ra20rSvFpfjW0rlO2rzNM__lCwA
Subject: [dhcwg] WGLC for draft-ietf-dhc-access-network-identifier-05 - Respond by Jan. 12th
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, 18 Dec 2014 18:46:49 -0000

Hello everyone,

Authors feels that this document is ready for WGLC, so here it is. This
message starts the DHC working group last call for "Access Network
Identifier Option in DHCP"
(draft-ietf-dhc-access-network-identifier-05), which is a standards
track document.

The draft is available at:
http://tools.ietf.org/html/draft-ietf-dhc-access-network-identifier-05

As there is a slower time approaching with many people expected to
finally go off-line for a while, this WGLC is longer than usual. Please
send your comments by Jan. 12th, 2015. If you do not feel this document
should advance, please state your reasons why.

There are no IPR claims reported at this time.

Sheng Jiang is the assigned shepherd for this document.

Bernie & Tomek


From nobody Mon Dec 22 13:04:58 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 E93F51A7D85 for <dhcwg@ietfa.amsl.com>; Mon, 22 Dec 2014 13:04:53 -0800 (PST)
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 ASNklQdmpOKX for <dhcwg@ietfa.amsl.com>; Mon, 22 Dec 2014 13:04:45 -0800 (PST)
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 95A6E1A6FFB for <dhcwg@ietf.org>; Mon, 22 Dec 2014 13:04:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=35577; q=dns/txt; s=iport; t=1419282282; x=1420491882; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=BVraeTSOBkYE/8mg/Em5sAmyA13m+ziuqvJ1oK6l+CY=; b=aDS9JLxWIDW54fUDTNaB84KVzjjVwJG2li12NwpEWA+btP7v2XyGZMm5 HE6QxGY0huPdbADHBdpett2PHYFwI9oh0fXW8G/Lo5QaB0Wi6VEn0Z0/3 ECHcqdJB6FF/96gICzrTTiFBZQeeJ8jW5hnSoBfGWtss/JbTevEDe49aC c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmoFAAmHmFStJV2U/2dsb2JhbABbgkNDUlgExF2BaYVwAoEbFgEBAQEBfYQMAQEBBC1cAgEIEQMBAQELFgEGBzIUCQgBAQQBEggBEogRDdAoAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4xEgn0gFwEGgxCBEwWMOoFXgz6GQTCCNIVphDiDOSKCMoE8b4FFfgEBAQ
X-IronPort-AV: E=Sophos;i="5.07,626,1413244800";  d="scan'208,217";a="382363402"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-2.cisco.com with ESMTP; 22 Dec 2014 21:04:40 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id sBML4dDC021220 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 22 Dec 2014 21:04:39 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.84]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0195.001; Mon, 22 Dec 2014 15:04:39 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "ian.farrer@telekom.de" <ian.farrer@telekom.de>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 2014
Thread-Index: AdAWJao3p4FUbQo5T+qdYaKm1ensDgIA+fzw
Date: Mon, 22 Dec 2014 21:04:38 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B78BEB0@xmb-rcd-x04.cisco.com>
References: <D0B0D0F6.E7352%ian.farrer@telekom.de>
In-Reply-To: <D0B0D0F6.E7352%ian.farrer@telekom.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.203]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B78BEB0xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/BA3rQsybw4PNqv3fwSDowKHaXZA
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respond by December 12th, 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, 22 Dec 2014 21:04:54 -0000

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

Ian:

Thanks for your review. Marcin and I working through all of the review comm=
ents and following up where we aren't sure what the issue is.

Regarding your issue:

Section 4 Para 4
The behaviour of creating separate DHCP state machines is also listed as th=
e first item in the issue with no reason given as to why it is a problem.
'multiple instances of the state machine in clients' could be replaced with=
 'additional host resources required to create/maintain multiple instances =
of the state machine in clients'.


Marcin and I are confused by this as there is in this paragraph:

   Creating a separate DHCP session (separate instances of the client
   state machine) per IA option type, while conceptually simple, has a
   number of issues: multiple instances of the state machine in clients,
   additional DHCP protocol traffic, 'collisions' between other
   configuration options, divergence in that each IA option type
   specification specifies its 'own' version of the DHCP protocol.


While we plan to not address it (since this document isn't to solve all of =
the RFC 3315 issues), we are also a bit confused as to what the following i=
ssue is:

One additional comment which I raised in Honolulu, is regarding RFC3633 and=
 the 'NoBinding'
error message, sent to the client when a renew message

RFC 3315, 18.1.8. Receipt of Reply Messages, has:

   When the client receives a Reply message in response to a Renew or
   Rebind message, the client examines each IA independently.  For each
   IA in the original Renew or Rebind message, the client:

   -  sends a Request message if the IA contained a Status Code option
      with the NoBinding status (and does not send any additional
      Renew/Rebind messages)

So, doesn't this cover the NoBinding status case?  This is the Renew/Rebind=
 with NoBinding, so it isn't clear what is missing?


Happy Holidays.


-          Bernie

From: ian.farrer@telekom.de [mailto:ian.farrer@telekom.de]
Sent: Friday, December 12, 2014 11:07 AM
To: Bernie Volz (volz); dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Re=
spond by December 12th, 2014

Hi,

A quick review of the document. Generally I think it's in good shape and su=
pport it moving forward.  A couple of small comments from my review:

Section 1
Suggested re-word;
Old:
DHCPv6 [RFC3315] was not written with the expectation that additional state=
ful DHCPv6 options would be developed.
New:
DHCPv6 [RFC3315] was written without the expectation that additional statef=
ul DHCPv6 options would be developed.

Section 4 Para 4
The behaviour of creating separate DHCP state machines is also listed as th=
e first item in the issue with no reason given as to why it is a problem.
'multiple instances of the state machine in clients' could be replaced with=
 'additional host resources required to create/maintain multiple instances =
of the state machine in clients'.

Section 4.4.1
The content first paragraph seems at odds with the second and third paragra=
ph.
Para 1 is about a limitation on how leases can be renewed, but then para 2 =
describes
extending the function of the renew message to also request bindings for ot=
her IAs
Para 3 then provides a solution for the problem in para 2, but nothing for =
the
problem described in para 1.
Suggest that Para 3 is updated to say that the Renew message would also be =
able to renew bindings that have been allocated via a Renew message.

One additional comment which I raised in Honolulu, is regarding RFC3633 and=
 the 'NoBinding'
error message, sent to the client when a renew message
However, client behaviour on receipt of this message is not specified. It w=
ould seem
logical that this was interpreted by the client as a reset of its DHCP stat=
e machine.
Should this be dealt with in this document (it is a DHCP state issue), or s=
hould it go into the RFC3315-bis?

Cheers,
Ian

From: "Bernie Volz (volz)" <volz@cisco.com<mailto:volz@cisco.com>>
Date: Thursday, 11 December 2014 22:50
To: "dhcwg@ietf.org<mailto:dhcwg@ietf.org>" <dhcwg@ietf.org<mailto:dhcwg@ie=
tf.org>>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Re=
spond by December 12th, 2014

Final reminder - PLEASE Review!


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Friday, December 05, 2014 11:59 PM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Re=
spond by December 12th, 2014

Reminder regarding this WGLC. Please review.

>From the IETF-91 minutes (http://www.ietf.org/proceedings/91/minutes/minute=
s-91-dhc):

Asking for additional reviewers: Suresh Krishnan, Ted Lemon, Tim Winters an=
d Tomek Mrugalski signed up.


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, November 26, 2014 9:59 AM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 - Respon=
d by December 12th, 2014


Hi all,



This message starts the DHC working group last call to advance "Issues and =
Recommendations with Multiple Stateful DHCPv6 Options", draft-ietf-dhc-dhcp=
v6-stateful-issues-09.txt, document as a Standards Track (Proposed Standard=
) RFC. The authors believe that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09



Please send your comments by December 12th, 2014. If you do not feel this d=
ocument 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_489D13FBFA9B3E41812EA89F188F018E1B78BEB0xmbrcdx04ciscoc_
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";}
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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{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:1378431861;
	mso-list-type:hybrid;
	mso-list-template-ids:-1214626008 738613330 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	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:1504052267;
	mso-list-type:hybrid;
	mso-list-template-ids:-477201226 -1527995754 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	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:2028868969;
	mso-list-type:hybrid;
	mso-list-template-ids:1022920178 252489098 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l2: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 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" style=3D"word-wrap: bre=
ak-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Ian:<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 for your review=
. Marcin and I working through all of the review comments and following up =
where we aren&#8217;t sure what the issue is.<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">Regarding your issue:<=
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"font-size:10.5pt;color:black">Section=
 4 Para 4<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">The beh=
aviour of creating separate DHCP state machines is also listed as the first=
 item in the issue with no reason given as to why it is a problem.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">'multip=
le instances of the state machine in clients' could be replaced with 'addit=
ional host resources required to create/maintain multiple instances of the =
state machine in clients'.<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"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Marcin and I are confu=
sed by this as there is in this paragraph:<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" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; Creating a separate DHCP session (separate instances of the client<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=
; state machine) per IA option type, while conceptually simple, has a<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=
; number of issues: multiple instances of the state machine in clients,<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=
; additional DHCP protocol traffic, 'collisions' between other<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=
; configuration options, divergence in that each IA option type<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=
; specification specifies its 'own' version of the DHCP protocol.<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"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">While we plan to not a=
ddress it (since this document isn&#8217;t to solve all of the RFC 3315 iss=
ues), we are also a bit confused as to what the following issue is:<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"font-size:10.5pt;color:black">One add=
itional comment which I raised in Honolulu, is regarding RFC3633 and the 'N=
oBinding'<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">error m=
essage, sent to the client when a renew message&nbsp;<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">RFC 3315, 18.1.8. Rece=
ipt of Reply Messages, has:<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" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; When the client receives a Reply message in response to a Renew or<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=
; Rebind message, the client examines each IA independently.&nbsp; For each=
<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=
; IA in the original Renew or Rebind message, the client:<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"><o:p>&nbsp;=
</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=
; -&nbsp; sends a Request message if the IA contained a Status Code option<=
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=
;&nbsp;&nbsp;&nbsp; with the NoBinding status (and does not send any additi=
onal<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=
;&nbsp;&nbsp;&nbsp; Renew/Rebind messages)<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">So, doesn&#8217;t this=
 cover the NoBinding status case? &nbsp;This is the Renew/Rebind with NoBin=
ding, so it isn&#8217;t clear what is missing?<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"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Happy Holidays.<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:l2 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;"> ian.farr=
er@telekom.de [mailto:ian.farrer@telekom.de]
<br>
<b>Sent:</b> Friday, December 12, 2014 11:07 AM<br>
<b>To:</b> Bernie Volz (volz); dhcwg@ietf.org<br>
<b>Subject:</b> Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-=
09 - Respond by December 12th, 2014<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi,<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">A quick=
 review of the document. Generally I think it&#8217;s in good shape and sup=
port it moving forward. &nbsp;A couple of small comments from my review:<o:=
p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Section=
 1<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Suggest=
ed re-word;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Old:<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">DHCPv6 =
[RFC3315] was not written with the expectation that additional stateful DHC=
Pv6 options would be developed.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">New:<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">DHCPv6 =
[RFC3315] was written without the expectation that additional stateful DHCP=
v6 options would be developed.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Section=
 4 Para 4<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">The beh=
aviour of creating separate DHCP state machines is also listed as the first=
 item in the issue with no reason given as to why it is a problem.<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">'multip=
le instances of the state machine in clients' could be replaced with 'addit=
ional host resources required to create/maintain multiple instances of the =
state machine in clients'.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Section=
 4.4.1<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">The con=
tent first paragraph seems at odds with the second and third paragraph.<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Para 1 =
is about a limitation on how leases can be renewed, but then para 2 describ=
es<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">extendi=
ng the function of the renew message to also request bindings for other IAs=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Para 3 =
then provides a solution for the problem in para 2, but nothing for the<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">problem=
 described in para 1.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Suggest=
 that Para 3 is updated to say that the Renew message would also be able to=
 renew bindings that have been allocated via a Renew message.<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">One add=
itional comment which I raised in Honolulu, is regarding RFC3633 and the 'N=
oBinding'<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">error m=
essage, sent to the client when a renew message&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">However=
, client behaviour on receipt of this message is not specified. It would se=
em<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">logical=
 that this was interpreted by the client as a reset of its DHCP state machi=
ne.<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Should =
this be dealt with in this document (it is a DHCP state issue), or should i=
t go into the RFC3315-bis?<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Cheers,=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Ian<o:p=
></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</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"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;Bernie Volz (volz)&quot; &lt;<a href=3D"mailt=
o:volz@cisco.com">volz@cisco.com</a>&gt;<br>
<b>Date: </b>Thursday, 11 December 2014 22:50<br>
<b>To: </b>&quot;<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-=
09 - Respond by December 12th, 2014<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Final reminder &#8211;=
 PLEASE Review!</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"color:black"><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"color:#1F497D">Bernie</span><=
span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"color:black"><o:p></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;;color:black">From:</span></b><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot=
;;color:black"> dhcwg [<a href=3D"mailto:dhcwg-bounces@ietf.org">mailto:dhc=
wg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Friday, December 05, 2014 11:59 PM<br>
<b>To:</b> <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<b>Subject:</b> Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-=
09 - Respond by December 12th, 2014</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Reminder regarding thi=
s WGLC. Please review.</span><span style=3D"color:black"><o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">From the IETF-91 minut=
es (<a href=3D"http://www.ietf.org/proceedings/91/minutes/minutes-91-dhc">h=
ttp://www.ietf.org/proceedings/91/minutes/minutes-91-dhc</a>):</span><span =
style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Asking for additional reviewers: Suresh Krishn=
an, Ted Lemon, Tim Winters and Tomek Mrugalski signed up.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo4"><![if !supportLists]><span style=3D"color:black"><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"color:#1F497D">Bernie</span><=
span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"color:black"><o:p></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;;color:black">From:</span></b><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot=
;;color:black"> dhcwg [<a href=3D"mailto:dhcwg-bounces@ietf.org">mailto:dhc=
wg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Wednesday, November 26, 2014 9:59 AM<br>
<b>To:</b> <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-stateful-issues-09 -=
 Respond by December 12th, 2014</span><span style=3D"color:black"><o:p></o:=
p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Hi all,<o:p></o:p></s=
pan></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">This message starts t=
he DHC working group last call to advance &quot;Issues and Recommendations =
with Multiple Stateful DHCPv6 Options&#8221;, draft-ietf-dhc-dhcpv6-statefu=
l-issues-09.txt, document as a Standards Track
 (Proposed Standard) RFC. The authors believe that this version is ready.<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">The draft is availabl=
e here:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black"><a href=3D"http://too=
ls.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09">http://tools.iet=
f.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-09</a><o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><b><span style=3D"color:black">Please send your c=
omments by December 12th, 2014. If you do not feel this document should adv=
ance, please state your reasons why.</span></b><span style=3D"color:black">=
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">There are no IPR clai=
ms reported at this time.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Tomek is the assigned=
 shepherd for this document.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">- Tomek &amp; Bernie<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
</div>
</div>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B78BEB0xmbrcdx04ciscoc_--

