
From nobody Fri May  2 05:34:00 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 9D1F01A6F74 for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 05:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WY3_hkPe500I for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 05:33:57 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id D3FA91A6F44 for <dhcwg@ietf.org>; Fri,  2 May 2014 05:33:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5403; q=dns/txt; s=iport; t=1399034034; x=1400243634; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=0fAT0wija25+ffPHj+gp8mTQBBdTnY3Andx47b6oTXQ=; b=a/Czptll4DmUwmVBFE3i8NCcUldyYMHFlOw+gEQj+X9Pql6UxbaeaSQJ 6qUdftZVSBs6c8EOd9VNrRHB+7yeyKFknQynx3836MiNzTRXUxqQLzHRf lCTaxyjhHCoVqUcGuVqi3HCcicf7ku01sArzyVRuYc0/psQbfz1ATM1Ze Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAJePY1OtJA2D/2dsb2JhbABagwZPV4JnuiiHPoEQFnSCJQEBAQMBAQEBHgFJAwsFBwQCAQgRBAEBAgMGHQIDAiEGCxQJCAIEAQ0FCIglAwkIDYkunBcBnSUNhkUTBIEnihx4gT8nMQcGgmY4gRUEhFkCkF+CBI8GhVuDNIFpQg
X-IronPort-AV: E=Sophos;i="4.97,972,1389744000"; d="scan'208";a="40520029"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-6.cisco.com with ESMTP; 02 May 2014 12:33:54 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s42CXsmx006710 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 May 2014 12:33:54 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Fri, 2 May 2014 07:33:53 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, "Tomek Mrugalski" <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPZJnNHMzNFfxEIk6wcBa/GM4ndJstOXMQ
Date: Fri, 2 May 2014 12:33:53 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com>
In-Reply-To: <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.245.71]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/FT_xe_VqMSiP98Z_3QltzUAsG2k
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 02 May 2014 12:33:58 -0000

Jinmei:

Thanks for your review and feedback.

Regarding your first point, there's probably nothing (except the option len=
gth limitations, though RFC 3396 handles that) that would prevent this from=
 being adopted for DHCPv4. But it is indeed a question of whether advancing=
 DHCPv4 is as important as advancing DHCPv6. Also, the DHC WG charter is fo=
cused on DHCPv6.

If this work does advance, and there's sufficient interest, I could well se=
e someone proposing the same for DHCPv4.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of ????
Sent: Wednesday, April 30, 2014 1:30 PM
To: Tomek Mrugalski
Cc: dhcwg
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 1=
8

At Tue, 29 Apr 2014 20:21:33 +0200,
Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:

> Since we have upcoming holiday on May 1st (which happens to be a=20
> reason for extended weekend in many parts of Europe) and the topic in=20
> question is not trivial, this WGLC is a bit longer than usual.
>
> Please send your comments by May 18th 2014. If you do not feel this=20
> document should advance, please state your reasons why.

I've read the document.  I don't have a particular opinion on whether it sh=
ould advance, mainly because I'm not a security expert.  I have some commen=
ts that may hopefully be useful, though:

Some higher level points
- (maybe already discussed before but) the concept of using public key
  authentication in DHCP makes some sense to me, but I wonder why we
  are discussing this specifically for DHCPv6.  As far as I know
  there's no such counterpart in DHCPv4 (the only related thing I can
  google is draft-gupta-dhcp-auth-02.txt, which expired long ago), am
  I correct?  If so, is that because *v4 is just too legacy and isn't
  worth improvements anymore?  Or does that reflect some DHCP specific
  points that make public key authentication not so viable?  If it's
  the latter, doesn't it also apply to this proposal?

- The description of the draft is a bit vague (which may have to be
  clarified anyway), but if I understand it correctly, it assumes that
  both clients (each of them) and servers maintain their pair of
  public-private keys, and a client offers and uses its own key to
  authenticate messages from the client to servers.  Is that correct?
  If so, does this make sense?  My general understanding is that
  authenticating DHCP messages from clients to server is not that
  critical, and it's quite unlikely that servers maintain public keys
  of all possible clients so the servers would have to rely on the
  leap-of-faith model.  They then may have to worry about the
  "resource exhaustion attacks" (although I'm not sure if this is a
  big issue, see below).

Other non editorial comments on the draft:
- Section 5.1:
   Public Key     A variable-length field containing public key. The
                  key MUST be represented as a lower-case hexadecimal
                  string with the most significant octet of the key
                  first. Typically, the length of a 2048-bit RSA

  Is there any specific reason it's represented as a string?  Not
  necessarily bad, but I thought more common practice here is to
  simply use the binary value of the key.  DHCP options in wire format
  are not expected to be human readable anyway, so I don't see the
  point for using a string here.

- In Section 6.2:

   On the recipient that supports the leap of faith model, the number of
   cached public keys or unverifiable certificates MUST be limited in
   order to protect against resource exhaustion attacks.  If the

  This is mainly concerned about servers, correct?  If so, I'm not
  sure how severe this "attacks" are; DHCP servers generally need to
  maintain some state for each client (unless that's stateless only
  server) and would naturally already have some limitation on that
  resource.  Shouldn't the general defense be enough for this
  particular resource, too?  (But I was also not sure if it makes
  sense to use (public key) authentication for messages from clients
  in the first place; see higher-level discussions above)

- Related, it seems some part of Section 6.2 is more specific for
  clients and some other part is more specific to servers.  So it may
  be helpful if we have separate subsections focusing on these
  particular cases.  Just a suggestion.

Editorial nits:
- Section 4.3
   they may fall back the unsecure model, if both client and server
  s/fall back the/fall back to the/
  (I found the missing 'to' of this kind in several other places in
  the draft)

- Section 4.3
   whether to accept the messages.  If the client accept the unsecure
   messages from the DHCPv6 server.  The subsequent exchanges will be in
   unsecure model.
  s/server.  The/server, the/

- Section 4.3
   on the server policy.  If the server mandidates the authentication,
  s/mandidates/mandates/

- Section 6.1
   messages, MUST contain either a the Public Key or Certificate option,
  s/a the/the/ (?)

- Section 6.2
   error status code, defined in Section 5.4, back to the client..
  s/.././

--
JINMEI, Tatuya

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


From nobody Fri May  2 06:18:53 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 244531A08F7 for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 06:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FpkN54iibjTH for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 06:18:50 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 12A331A0829 for <dhcwg@ietf.org>; Fri,  2 May 2014 06:18:49 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id lx4so5113586iec.37 for <dhcwg@ietf.org>; Fri, 02 May 2014 06:18:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jAuXTuvPv0xuedj907ka6ifBb3UzBOlOIePyIXnNAuM=; b=dpzevDdMIooqPbEJtwT2BOLeVspD9dLGYCL71eWN/q5UkLkiIyUlvOaG3apeRyWwSR 1Pk9aa0mX70s5eCm73y/PYShLP40+4hdV8Gr4i8Ih6D1sMpjO6UJOuK24LrCIEZAT88I jqv+v+8z0vlsOTvfKRXosnnk88D7I2NgOMhJarPdK1oB1xVFtY38RTHvHRyYDkXLRR0W /BuVJK5KFBtytgioibRSl9IFYRZSjD5pnTya/pAh+Tz3Ar6HWnX+2UGaOtm7Ha/2c1IC Rb6MZTn58CvFcPTYi72M/5CHQbKvWOA5kH+rF8xC9dwhAwUeshhoCZ1ywGONHRWTx8qF CTWQ==
X-Received: by 10.50.138.72 with SMTP id qo8mr4019794igb.26.1399036727562; Fri, 02 May 2014 06:18:47 -0700 (PDT)
Received: from [192.168.100.139] (mobile-166-186-171-219.mycingular.net. [166.186.171.219]) by mx.google.com with ESMTPSA id kr5sm7995294igb.9.2014.05.02.06.18.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 May 2014 06:18:46 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com>
Date: Fri, 2 May 2014 09:18:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/KLZvoveE5owDVJ-cQ_FuXYuGtCU
Cc: dhcwg <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 02 May 2014 13:18:52 -0000

On May 2, 2014, at 8:33 AM 5/2/14, Bernie Volz (volz) <volz@cisco.com> =
wrote:

> Jinmei:
>=20
> Thanks for your review and feedback.
>=20
> Regarding your first point, there's probably nothing (except the =
option length limitations, though RFC 3396 handles that) that would =
prevent this from being adopted for DHCPv4.

If I recall correctly, similar protocols have been considered in the =
past for DHCPv4.  Those protocols were not developed because of concerns =
about the length of individual options and the total length of all of =
the options (certs can get big) combined with concerns about whether =
deployed DHCPv4 infrastructure (relay agents) would correctly handle =
large DHCPv4 messages.

> But it is indeed a question of whether advancing DHCPv4 is as =
important as advancing DHCPv6. Also, the DHC WG charter is focused on =
DHCPv6.

Yup.

I would like to see some consideration of the total length of DHCPv6 =
messages that use this security protocol included in the document.

- Ralph

>=20
> If this work does advance, and there's sufficient interest, I could =
well see someone proposing the same for DHCPv4.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of ????
> Sent: Wednesday, April 30, 2014 1:30 PM
> To: Tomek Mrugalski
> Cc: dhcwg
> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by =
May 18
>=20
> At Tue, 29 Apr 2014 20:21:33 +0200,
> Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:
>=20
>> Since we have upcoming holiday on May 1st (which happens to be a=20
>> reason for extended weekend in many parts of Europe) and the topic in=20=

>> question is not trivial, this WGLC is a bit longer than usual.
>>=20
>> Please send your comments by May 18th 2014. If you do not feel this=20=

>> document should advance, please state your reasons why.
>=20
> I've read the document.  I don't have a particular opinion on whether =
it should advance, mainly because I'm not a security expert.  I have =
some comments that may hopefully be useful, though:
>=20
> Some higher level points
> - (maybe already discussed before but) the concept of using public key
>  authentication in DHCP makes some sense to me, but I wonder why we
>  are discussing this specifically for DHCPv6.  As far as I know
>  there's no such counterpart in DHCPv4 (the only related thing I can
>  google is draft-gupta-dhcp-auth-02.txt, which expired long ago), am
>  I correct?  If so, is that because *v4 is just too legacy and isn't
>  worth improvements anymore?  Or does that reflect some DHCP specific
>  points that make public key authentication not so viable?  If it's
>  the latter, doesn't it also apply to this proposal?
>=20
> - The description of the draft is a bit vague (which may have to be
>  clarified anyway), but if I understand it correctly, it assumes that
>  both clients (each of them) and servers maintain their pair of
>  public-private keys, and a client offers and uses its own key to
>  authenticate messages from the client to servers.  Is that correct?
>  If so, does this make sense?  My general understanding is that
>  authenticating DHCP messages from clients to server is not that
>  critical, and it's quite unlikely that servers maintain public keys
>  of all possible clients so the servers would have to rely on the
>  leap-of-faith model.  They then may have to worry about the
>  "resource exhaustion attacks" (although I'm not sure if this is a
>  big issue, see below).
>=20
> Other non editorial comments on the draft:
> - Section 5.1:
>   Public Key     A variable-length field containing public key. The
>                  key MUST be represented as a lower-case hexadecimal
>                  string with the most significant octet of the key
>                  first. Typically, the length of a 2048-bit RSA
>=20
>  Is there any specific reason it's represented as a string?  Not
>  necessarily bad, but I thought more common practice here is to
>  simply use the binary value of the key.  DHCP options in wire format
>  are not expected to be human readable anyway, so I don't see the
>  point for using a string here.
>=20
> - In Section 6.2:
>=20
>   On the recipient that supports the leap of faith model, the number =
of
>   cached public keys or unverifiable certificates MUST be limited in
>   order to protect against resource exhaustion attacks.  If the
>=20
>  This is mainly concerned about servers, correct?  If so, I'm not
>  sure how severe this "attacks" are; DHCP servers generally need to
>  maintain some state for each client (unless that's stateless only
>  server) and would naturally already have some limitation on that
>  resource.  Shouldn't the general defense be enough for this
>  particular resource, too?  (But I was also not sure if it makes
>  sense to use (public key) authentication for messages from clients
>  in the first place; see higher-level discussions above)
>=20
> - Related, it seems some part of Section 6.2 is more specific for
>  clients and some other part is more specific to servers.  So it may
>  be helpful if we have separate subsections focusing on these
>  particular cases.  Just a suggestion.
>=20
> Editorial nits:
> - Section 4.3
>   they may fall back the unsecure model, if both client and server
>  s/fall back the/fall back to the/
>  (I found the missing 'to' of this kind in several other places in
>  the draft)
>=20
> - Section 4.3
>   whether to accept the messages.  If the client accept the unsecure
>   messages from the DHCPv6 server.  The subsequent exchanges will be =
in
>   unsecure model.
>  s/server.  The/server, the/
>=20
> - Section 4.3
>   on the server policy.  If the server mandidates the authentication,
>  s/mandidates/mandates/
>=20
> - Section 6.1
>   messages, MUST contain either a the Public Key or Certificate =
option,
>  s/a the/the/ (?)
>=20
> - Section 6.2
>   error status code, defined in Section 5.4, back to the client..
>  s/.././
>=20
> --
> JINMEI, Tatuya
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Fri May  2 06:51:40 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 A38431A6FB4 for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 06:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HRLIPDNmRxE for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 06:51:34 -0700 (PDT)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 58C3B1A6F71 for <dhcwg@ietf.org>; Fri,  2 May 2014 06:51:34 -0700 (PDT)
Received: by mail-we0-f181.google.com with SMTP id q58so4434707wes.26 for <dhcwg@ietf.org>; Fri, 02 May 2014 06:51:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=pR4dIyvXoZbKo1DV7KF16pTBnMBjXy6NTC93bY36foA=; b=D5oon6IXu9X6un2QcYUsKheI0fabtX8kG/OnDnucQMHzIlMCnQfIFcvItMREgxSEWJ sCqAVcr907arVLWs62FOBWcc0I8M2ST7073mV4HbI8jag+tR1sJ2iwYvU1bPIxRwEoKY DxOItQeCJII76/zMNnmUhMJC0Z13LqaCCu96B8IcMhCR3+7bOg3i6g37veEeD1zVIRj1 ioKdoLZC73EzxYjeZ9mr/PUGFFjzNaIaY7q/qj/o+XRqP43TGRh8l4PpbRqyf1Ejwmyf 5Pa9Wy081qmzV8vZXNspBzgNHT3lOJ5F8gNnjLWQxe3miNDrC7d9PsEcnJbo8H0pEaM4 IBnQ==
X-Received: by 10.180.218.35 with SMTP id pd3mr3111453wic.26.1399038691541; Fri, 02 May 2014 06:51:31 -0700 (PDT)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id n5sm4019270wiz.1.2014.05.02.06.51.29 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 May 2014 06:51:30 -0700 (PDT)
Message-ID: <5363A2DD.2020603@gmail.com>
Date: Fri, 02 May 2014 15:51:25 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1AFDEE1D@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AFDEE1D@xmb-rcd-x04.cisco.com>
X-Enigmail-Version: 1.5.2
X-TagToolbar-Keys: D20140502155125586
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/-VPhNR8XQiV4Ct06vJiQGnbC5nY
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-access-network-identifier-02 - respond by April 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 May 2014 13:51:36 -0000

On 12.04.2014 16:04, Bernie Volz (volz) wrote:
> Folks, the authors of draft-ietf-dhc-access-network-identifier
> (http://tools.ietf.org/html/draft-ietf-dhc-access-network-identifier-02)
> 
> feel it's ready for work group last call. Please review this draft and
> indicate whether or not you feel it is ready to be published.
While I agree with the reasons behind the draft and I think the idea is
sound, I'm afraid that it is not ready in my opinion.

With my co-chair hat off, I must say that the text is confusing to read
and allows very bad things, like sending DHCPv6 options in DHCPv4
messages (and vice versa), inserting sub-options as regular options and
is very imprecise in many cases (it is not clear which options to insert
where, what to ignore: just a sub-option, whole option or the whole
message etc).

Sorry for sending another long list of comments. I tried to split them
into substantial and editorial.

Substantial comments:

Section 2 (motivation) the text in 3rd paragraph explains that APs
insert acess network identifiers in DHCP messages. It is unclear whether
this is:
a) AP acting as a DHCP client and configures itself
b) AP acting as a DHCP relay agent and relays messages from connected
clients.

I assume you meant b), but this is text is ambiguous and should be
clarified.

I'm uncomfortable with treating both protocols in the same way. That
notion is introduced in section 3 and then continued throughout the
document. That is reflected in many of my comments below.

Section 4 (DHCPv4 Access-Network-Identifier Option) actually redefines
Relay Agent Information option! You can't do that! Please define this
option just for the client (i.e. remove the text "code: if added by
relay agnet: Relay Agent Information Option (82)".

Please consider adding the following text at the end of section 4:
"Client inserts Access Network Identifier option that contains one or
more suboptions, as defined in Section 4.1. Relay agent that wants to
include Access Network Indentifer information includes one or more
sub-options (see Section 4.1) in Relay Agent Information option [RFC3046]."

Please move the paragraph starting with "ANI Sub-options" from section
4. to 4.1 where it belongs.

Please rearrange the text, so it follows this pattern:

4. DHCPv4 options
4.1 DHCPv4 option 1
4.2 DHCPv4 sub-option 1
4.3 DHCPv4 sub-option 2
...

5. DHCPv6 options
5.1 DHCPv6 option 1
5.2 DHCPv6 option 2
5.3 DHCPv6 option 3
...

This layout is better than what you have for several reasons:
1. People interested in only one protocol family can read only one
continuous chunk of the text.
2. It is easier to reference options (by giving their subsection numbers).
3. It is easier to read without constant context switching (in v4 most
defined things are sub-options while in v6 they are regular options).
4. You will need to add extra text in each section, something along the
lines of "DHCPv4 clients insert this sub-option into
Access-Network-Identifier Option. DHCPv4 Relay Agents insert this
sub-option into Relay Agent Information option.". This is actually very
important to NOT have v4 and v6 options mixed here. The current text
allows crazy things, like v4 relay agent inserting v6 options.

I understand that it will require a bit of text duplication, but is much
less of an issue than allowing mixing up v4 and v6 options. If you don't
want to repeat it, use something like "ATT field. For definition of ATT
field, see section X.Y".

Section 7 is completely broken. Please be explicit about protocol
family. In essence, you need to write everything twice.

"DHCPv4 clients MAY include DHCPv4 ANI Option (see Section X.Y)
including one or more sub-options, as defined in sections X.Y through
Z.W. DHCPv4 clients MAY include DHCPv6 ANI Option, as defined in Section
A.B."

Please pay special attention to the wording here. Your text must
distinguish between options and sub-options. Please do not use pronouns.

Let me give you and example how badly broken the current text is: "DHCP
Relay Agents MAY include these options". What does it mean "these" here?
All options? My DHCPv4 relay agent can insert DHCPv6 options or insert
DHCPv4 sub-options directly as options. Your text says that it's ok. It
clearly is not.

It is fine (and actually a good idea) to have separate
client/relay/server behavior sections for DHCPv4 and DHCPv6. It will be
especially useful for relay agents, as those work differently for v4 and v6.

I strongly suggest to take a look at draft-ietf-dhc-option-guidelines
(to be published as RFC7227), section 21. It gives examples on how to
write such client/server/relay agent behavior text.

Section 9 is also very confusing. "If DHCP Server is unable to
understand these options it MUST be ignored." What does the "it" means
in this context? The message or the option? Strictly adhering to English
grammar, "it" would mean "the DHCP server"... Anyway, the server ignores
options it doesn't understand. This is the standard behavior. No need to
use normative language here.

There is no text to explain what to do when both client and relay
include ANI options. If the relay sees that client included ANI options,
should it include them as well? I'm not an expert on mobility or access
networks, but as an operator, I would trust more the relay agent than
the values sent by client. Client can spoof its options in an attempt to
gain better service.

Since you define a new option with sub-options, please make sure to say
what's the server's behavior when receiving an option with some
sub-options not being recognized. Should the server ignore just that one
unrecognized sub-option or the whole option? If it's up to server
administrative policy, please say so in the text.

IANA considerations section uses wrong registry names.
"Bootp and DHCP options" =>
"BOOTP Vendor Extensions and DHCP Options"

"DHCPv6 and DHCPv6 options" =>
I think it should be "Option Codes registry for DHCPv6".

Security considerations section should mention that client can fake its
ANI option values to gain better service.

Many normative references should be informative.

Idnits reports several issues: missing and unused references, too long
lines, non-RFC2606 FQDNs and others. Please make sure that those are
resolved before you upload next version. Idnits is available here:
http://tools.ietf.org/tools/idnits/ you can check your unpublished version.

Editorial comments:

Section 1:
"range of application" => "range of applications".

"For e.g. The local mobility anchor..." => "For example the local
mobility anchor..."

The official protocol name is "Dynamic Host Configuration Protocol for
IPv6" or "DHCPv6", not "Dynamic Host Configuration Protocol v6". That
mistake is repeated in section 3.

Dot is missing at the last sentence in section 1.

Section 2
"various type of network deployments" =>
"various types of network deployments"

Section 3:
"DHCP refers to both DHCPv4 and DHCPv6 messages...". DHCP is a name of
the protocol, not the message. Did you want to say
"DHCP message refers to both DHCPv4 and DHCPv6 messages..." ?




From nobody Fri May  2 07:56:17 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 55F151A7015 for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 07:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level: 
X-Spam-Status: No, score=-10.151 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, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vDwTixcYFnil for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 07:56:14 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id EFD791A700A for <dhcwg@ietf.org>; Fri,  2 May 2014 07:56:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9633; q=dns/txt; s=iport; t=1399042572; x=1400252172; h=from:to:subject:date:message-id:mime-version; bh=ti0rT1kR8J4l4wUr4c0WZPkOt8RqWxbaXFNAH3535SA=; b=Zpr1swUDZrCeoWhHMvz3EtBXjDAmqfQEfMnvLADV/+oIw6+wLfrougmL tQieFaM9vdfCB5lpN2MgGW1n9bX5qlfEn4FvSzsFjAdGPxNLfNYD3JbF4 pLPBHETQzOojrV1xCpB1NzHlmTHxaIZiC1qU/WEbk8thwYl5NW7fejXUA c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AncFACexY1OtJV2a/2dsb2JhbABagkJET1i7Toh7gREWdIIlAQEBBC1eARkEAQELHTkUCQkBBBMIAYg4DZZAs0gXi0OCPgEBHjeDJYEVBJpskTOBdYE/bYEJOQ
X-IronPort-AV: E=Sophos; i="4.97,972,1389744000"; d="scan'208,217"; a="40554443"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-1.cisco.com with ESMTP; 02 May 2014 14:56:11 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s42EuBBU003206 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Fri, 2 May 2014 14:56:11 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Fri, 2 May 2014 09:56:11 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Results of WGLC for draft-ietf-dhc-access-network-identifier-02 - respond by April 27, 2014
Thread-Index: Ac9mA3HgVadDmLWmSoGHU5PHfl3S1A==
Date: Fri, 2 May 2014 14:56:09 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B008855@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.245.71]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B008855xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Zvj6VMKnM_TM5nHSftXcGjd7tUs
Subject: [dhcwg] Results of WGLC for draft-ietf-dhc-access-network-identifier-02 - respond by April 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 May 2014 14:56:16 -0000

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

Thanks to all those that provided comments during the WGLC.

The co-chairs have determined that there are significant issues in this dra=
ft that will need to be corrected - therefore, the document did NOT pass WG=
LC. Once the document is updated to address the issues raised, the chairs a=
nd shepherd will determine if the document is ready for another WGLC.

If the authors have questions or need assistance, please reach out to the c=
hairs and document shepherd (Sheng Jiang).


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Saturday, April 12, 2014 10:04 AM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-access-network-identifier-02 - res=
pond by April 27, 2014


Folks, the authors of draft-ietf-dhc-access-network-identifier (http://tool=
s.ietf.org/html/draft-ietf-dhc-access-network-identifier-02)

feel it's ready for work group last call. Please review this draft and indi=
cate whether or not you feel it is ready to be published.



At the time of this writing, there is no IPR reported against this draft. P=
lease see http://www.ietf.org/mail-archive/web/dhcwg/current/msg14143.html =
for a reminder regarding IPR disclosure requirements.



Tomek and I will evaluate consensus after April 27, 2014.



Thanks,

Bernie & Tomek


--_000_489D13FBFA9B3E41812EA89F188F018E1B008855xmbrcdx04ciscoc_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1556773647;
	mso-list-type:hybrid;
	mso-list-template-ids:955688234 1941975176 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks to all those th=
at provided comments during the WGLC.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The co-chairs have det=
ermined that there are significant issues in this draft that will need to b=
e corrected &#8211; therefore, the document did NOT pass WGLC. Once the doc=
ument is updated to address the issues raised,
 the chairs and shepherd will determine if the document is ready for anothe=
r WGLC.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If the authors have qu=
estions or need assistance, please reach out to the chairs and document she=
pherd (Sheng Jiang).<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> Saturday, April 12, 2014 10:04 AM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-access-network-identifier-0=
2 - respond by April 27, 2014<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Folks, the authors of draft-ietf-dhc-access-netwo=
rk-identifier (<a href=3D"http://tools.ietf.org/html/draft-ietf-dhc-access-=
network-identifier-02">http://tools.ietf.org/html/draft-ietf-dhc-access-net=
work-identifier-02</a>)<o:p></o:p></p>
<p class=3D"MsoPlainText">feel it's ready for work group last call. Please =
review this draft and indicate whether or not you feel it is ready to be pu=
blished.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">At the time of this writing, there is no IPR repo=
rted against this draft. Please see
<a href=3D"http://www.ietf.org/mail-archive/web/dhcwg/current/msg14143.html=
">http://www.ietf.org/mail-archive/web/dhcwg/current/msg14143.html</a> for =
a reminder regarding IPR disclosure requirements.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Tomek and I will evaluate consensus after April 2=
7, 2014.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks,<o:p></o:p></p>
<p class=3D"MsoPlainText">Bernie &amp; Tomek<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B008855xmbrcdx04ciscoc_--


From nobody Fri May  2 09:43:22 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76D621A08DE for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 09:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pE7wmhd4l1FP for <dhcwg@ietfa.amsl.com>; Fri,  2 May 2014 09:43:20 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 578C81A6F64 for <dhcwg@ietf.org>; Fri,  2 May 2014 09:43:20 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hm4so2654436wib.4 for <dhcwg@ietf.org>; Fri, 02 May 2014 09:43:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=O9auUreSc8E+6gHSZLfuZ8TkLt30tAoK+lVOQgAJA80=; b=Ms7RUNNG7NP85DfdZvL3RjrfM9YfTeDQVyQJ5xhBwRyDDzZpsAMQ2Z7dn7h5aPngD+ 6MnZUeAL7X19QpV7/P4U2HXoDd3/fUKx+HHBALvVn1yYvcM8QSFQbSXXyPlzZUOzZNR8 gjvkY6eZr2VbKwyBC1/6Kfbf+BK1+jyWZoY2fRFgrURTX925ZbMgoWqQb81fMOF4RxWC 7+8/+rBV6LJtLydjsR3bFUebxTqpkCE+NOj8P9UYeJPPRIlS3nU7gGCWN2kniH0vM/oE Ta6Z4YVtpQsriPZOL6Bqb69HlOIoSiISc5n+9t7BZgsb8Y4vWohgEp3onYIHuQFS4jue fdKw==
MIME-Version: 1.0
X-Received: by 10.180.187.111 with SMTP id fr15mr3699832wic.57.1399048997545;  Fri, 02 May 2014 09:43:17 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.3.14 with HTTP; Fri, 2 May 2014 09:43:17 -0700 (PDT)
In-Reply-To: <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com>
Date: Fri, 2 May 2014 09:43:17 -0700
X-Google-Sender-Auth: AyrcjYJslwBEqGrw0Oig_L2gUwg
Message-ID: <CAJE_bqcDS6FKRdt3BSDbATqkf+esyQXAFFnC00RYQ1GDBz2ZHA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/8IL6qSA_VQgoLx2aD1RXO59bTmI
Cc: dhcwg <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 02 May 2014 16:43:21 -0000

At Fri, 2 May 2014 09:18:11 -0400,
Ralph Droms <rdroms.ietf@gmail.com> wrote:

> If I recall correctly, similar protocols have been considered in the past=
 for DHCPv4.  Those protocols were not developed because of concerns about =
the length of individual options and the total length of all of the options=
 (certs can get big) combined with concerns about whether deployed DHCPv4 i=
nfrastructure (relay agents) would correctly handle large DHCPv4 messages.

Okay, thanks for the clarification, and I agree with the following point:

> I would like to see some consideration of the total length of DHCPv6 mess=
ages that use this security protocol included in the document.

--
JINMEI, Tatuya


From nobody Fri May  2 11:16:53 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B88E1A091C; Fri,  2 May 2014 11:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.852
X-Spam-Level: 
X-Spam-Status: No, score=-7.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MANGLED_NAIL=2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 voig9ljle7v6; Fri,  2 May 2014 11:16:50 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 218DC1A0911; Fri,  2 May 2014 11:16:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5293; q=dns/txt; s=iport; t=1399054608; x=1400264208; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=oIamQMhUsnQ70Uep9c4MX8YOyyWcrdC3qJn56s02H7E=; b=Ff52rQnMRqztnEDz7YKa0/fY7zAjlu8dkzCP65H7H+/VrszcWH8Qapxp 6ysHB5VqPB0YqcP0Y4fOYsr8cJzi+rydpzCGAyTR75EdQFG00doeLpiZr YAluYCeOEXeQfJqgs4u51Fuf90TIhaZ5vEc9mTIpcQFVuQHQMdSyfLwdJ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAA/gY1OtJA2K/2dsb2JhbABagwZPWL0ThmhRgREWdIIlAQEBBAEBARodNAsMBAIBCBEDAQEBCxQJBycLFAkIAgQBDQUIAYg4DcovF44hMQcGgx6BFQSabJEzgzRtgUI
X-IronPort-AV: E=Sophos;i="4.97,973,1389744000"; d="scan'208";a="40597418"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-3.cisco.com with ESMTP; 02 May 2014 18:16:47 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s42IGlAY010764 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 May 2014 18:16:47 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0123.003; Fri, 2 May 2014 13:16:46 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: dhcwg <dhcwg@ietf.org>, "draft-ietf-softwire-map-dhcp@tools.ietf.org" <draft-ietf-softwire-map-dhcp@tools.ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-softwire-map-dhcp-07 in Softwires WG
Thread-Index: AQHPXkllgPQyeQLf/0K92SBfVkmnIJstotTw
Date: Fri, 2 May 2014 18:16:45 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B008D40@xmb-rcd-x04.cisco.com>
References: <53422B8F.2020109@ericsson.com> <53569B1C.9030803@gmail.com>
In-Reply-To: <53569B1C.9030803@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.245.71]
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/g8V46PYXdltMuKP-UOU8Dg0wi6U
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-softwire-map-dhcp-07 in Softwires WG
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, 02 May 2014 18:16:51 -0000

Hi:

I'm reviewing this document from the DHC perspective and not evaluating it =
with respect to Softwires.

>From an options definition/formatting perspective, I think this draft follo=
ws the draft-ietf-dhc-option-guidelines-17 recommendations.

There are some minor nits that could improve the clarity of the draft:

For example:

   o  S46_RULE-options: a variable field that may contain zero or more
      options that specify additional parameters for this S46 rule, e.g.
      a Port Parameter Option.

Says "e.g. a Port Parameter Option". Are there others (today)? Be nice to b=
e explicit as to what can appear today (future documents can always add add=
itional options).

And, in other places when options are referenced the option name is given (=
so perhaps replace with OPTION_S46_PORTPARAMS)? There are similar issues in=
 other places in the draft.

Also:

   The OPTION_S46_PORTPARAMS option MUST be encapsulated in a
   OPTION_S46_RULE option or an OPTION_S46_V4V6BIND option.  It MUST NOT
   appear directly within a container option.

5.  Softwire 46 Container DHCPv6 Options

      +-----------------------+-------+-------+--------------------+
      | Option                | MAP-E | MAP-T | Lightweight 4over6 |
      +-----------------------+-------+-------+--------------------+
      | OPTION_S46_RULE       |   M   |   M   |        N/A         |
      | OPTION_S46_BR         |   M   |  N/A  |         M          |
      | OPTION_S46_PORTPARAMS |   O   |   O   |         O          |
      | OPTION_S46_DMR        |  N/A  |   M   |        N/A         |
      | OPTION_S46_V4V6BIND   |  N/A  |  N/A  |         O          |
      +-----------------------+-------+-------+--------------------+

             M - Mandatory, O - Optional, N/A - Not Applicable

                   Table 1: Option to Container Mappings

So, the last sentence before section 5 (It MUST NOT appear directly within =
a container Option). But section 5 calls the two options it is allowed in C=
ontainer options? Perhaps just drop that sentence? Also, the "MUST be encap=
sulated" seems wrong (it is optional)? Well, it all depends what is meant b=
y this sentence. I think it is trying to say "may only" or "can only"?

This table 1 should probably have an introduction / description? Perhaps it=
 should also be moved to the end of section 5?


It is wise to have the Security Considerations reference an expired and dea=
d document - [I-D.ietf-dhc-secure-dhcpv6]? It is Informative, but still ...=
 Perhaps worth adding whatever material makes sense? It looks like many of =
Informative references are to older (expired) draft documents?


- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tomek Mrugalski
Sent: Tuesday, April 22, 2014 12:39 PM
To: dhcwg
Cc: Softwires-wg
Subject: [dhcwg] WGLC for draft-ietf-softwire-map-dhcp-07 in Softwires WG

Oops, that slipped under the radar for while.

I'd like to bring up to DHC attention a document that goes through WGLC in =
Softwires. This is a document that specifies provisioning mechanism for MAP=
, lw4over6 and possibly other IPv4/IPv6 transition technologies.
It defines 8 DHCPv6 options. Some of them are containers and there are many=
 inter-option dependencies (including dependence on PD options), so it's no=
t a straightforward doc.

Please post your DHCP-related comments to Softwires list with cc: to dhc. I=
f you have MAP-, lw4over6- or other IPv4/IPv6 transition specific comments,=
 please post them to Softwires only and not to DHC.

With my DHC co-chair hat off: I used to be a primary author of that draft a=
round 1,5 years ago. Since then I gave up and didn't follow on the discussi=
ons (simply because of lack of time). While technically I'm still listed as=
 a co-author, I can't make any comments on the quality or correctness of th=
is draft.

Tomek

-------- Original Message --------
Subject: [Softwires] Working group last call for
draft-ietf-softwire-map-dhcp-07
Date: Mon, 7 Apr 2014 00:37:35 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Softwires WG <softwires@ietf.org>
CC: Yong Cui <cuiyong@tsinghua.edu.cn>

Hi all,
  This message starts a two week softwire working group last call on advanc=
ing the draft about the DHCPv6 Options for configuration of Softwire Addres=
s and Port Mapped Clients as a Standards Track RFC. The authors believe tha=
t this version has addressed all the issues raised on the document. The lat=
est version of the draft is available at

http://www.ietf.org/id/draft-ietf-softwire-map-dhcp-07.txt
http://tools.ietf.org/html/draft-ietf-softwire-map-dhcp-07

Substantive comments and statements of support/opposition for advancing thi=
s document should be directed to the mailing list. Editorial suggestions ca=
n be sent directly to the authors. This last call will conclude on April 21=
 2014.

Regards,
Suresh & Yong


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


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


From nobody Mon May  5 20:54:43 2014
Return-Path: <leo.liubing@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 B23F21A06DC for <dhcwg@ietfa.amsl.com>; Mon,  5 May 2014 20:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 W20eQHThP-jg for <dhcwg@ietfa.amsl.com>; Mon,  5 May 2014 20:54:40 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB861A06E1 for <dhcwg@ietf.org>; Mon,  5 May 2014 20:54:39 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGL03523; Tue, 06 May 2014 03:54:35 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 May 2014 04:53:20 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 May 2014 04:54:34 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.224]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Tue, 6 May 2014 11:54:32 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>, dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPY9fp2Mp60OTEb0+z8fgjzyjzkZsy9NNw
Date: Tue, 6 May 2014 03:54:31 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D887846@nkgeml506-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com>
In-Reply-To: <535FEDAD.5010103@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/s_Gx-JBY5OB2IZC31eUf0ocJfdo
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 03:54:41 -0000

Hi all,

I support advancing this draft.

Best regards,
Bing

> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tomek
> Mrugalski
> Sent: Wednesday, April 30, 2014 2:22 AM
> To: dhcwg
> Subject: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
>=20
> Hi all,
>=20
> This message starts DHC working group last call about advancing Secure
> DHCPv6 with Public Key document as a Standards Track RFC. The authors
> believe that this version addressed all the issues raised and is ready.
>=20
> The draft is available here:
> http://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-02
>=20
> Since we have upcoming holiday on May 1st (which happens to be a reason
> for extended weekend in many parts of Europe) and the topic in question i=
s
> not trivial, this WGLC is a bit longer than usual.
>=20
> Please send your comments by May 18th 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 Mrugalski is the document shepherd.
>=20
> Bernie & Tomek
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Mon May  5 23:05:12 2014
Return-Path: <madi@zdns.cn>
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 179F61A0255 for <dhcwg@ietfa.amsl.com>; Mon,  5 May 2014 23:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.449
X-Spam-Level: **
X-Spam-Status: No, score=2.449 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MIME_CHARSET_FARAWAY=2.45] 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 MJ1XZLFh2PNN for <dhcwg@ietfa.amsl.com>; Mon,  5 May 2014 23:05:09 -0700 (PDT)
Received: from mail.zdns.cn (smtp.knet.cn [202.173.10.15]) by ietfa.amsl.com (Postfix) with SMTP id A6EDE1A0724 for <dhcwg@ietf.org>; Mon,  5 May 2014 23:05:07 -0700 (PDT)
X-TM-DID: 468c72c829d579368969d789e43dfd0f
Content-Type: text/plain; charset=GB2312
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Declan Ma <madi@zdns.cn>
In-Reply-To: <535FEDAD.5010103@gmail.com>
Date: Tue, 6 May 2014 14:04:54 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA57132A-DE22-4C34-B5C0-DA2E6AE7B4F0@zdns.cn>
References: <535FEDAD.5010103@gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>, dhcwg <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/GSDnoyb-PY0Z4VBcV9CkYjQvtVQ
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 06:05:11 -0000

Over the years, rogue DHCP servers have been gripping the security of =
access network a lot.

By employing PKI, sedhcpv6 is going to offer a widely applicable method, =
with which DHCPv6 service can be provided securely.

I am in favor of advancing this document.


Declan Ma
Internet Domain Name System Beijing Engineering Research Centre (ZDNS)



=D4=DA 2014=C4=EA4=D4=C230=C8=D5=A3=AC=C9=CF=CE=E72:21=A3=ACTomek =
Mrugalski <tomasz.mrugalski@gmail.com> =D0=B4=B5=C0=A3=BA

> Hi all,
>=20
> This message starts DHC working group last call about advancing Secure
> DHCPv6 with Public Key document as a Standards Track RFC. The authors
> believe that this version addressed all the issues raised and is =
ready.
>=20
> The draft is available here:
> http://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-02
>=20
> Since we have upcoming holiday on May 1st (which happens to be a =
reason
> for extended weekend in many parts of Europe) and the topic in =
question
> is not trivial, this WGLC is a bit longer than usual.
>=20
> Please send your comments by May 18th 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 Mrugalski is the document shepherd.
>=20
> Bernie & Tomek
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Mon May  5 23:33:32 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 BB5991A071D for <dhcwg@ietfa.amsl.com>; Mon,  5 May 2014 23:33:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.552
X-Spam-Level: 
X-Spam-Status: No, score=-4.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 76_xDDAL7c0Y for <dhcwg@ietfa.amsl.com>; Mon,  5 May 2014 23:33:29 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE461A025A for <dhcwg@ietf.org>; Mon,  5 May 2014 23:33:28 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDW06233; Tue, 06 May 2014 06:33:22 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 May 2014 07:32:06 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 May 2014 07:33:20 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Tue, 6 May 2014 14:33:14 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPY9fqOkQX2Up+wk+VaPjsYGUK15sp5cSAgALR/YCABmmZkA==
Date: Tue, 6 May 2014 06:33:14 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE431E5@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B008430@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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/SRlWU_wTiV2N6sg00-19Rvp4cvw
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 06:33:31 -0000

SGksIEppbm1laSAmIEJlcm5pZSwNCg0KV2UgZG8gaGF2ZSBhIHBsYW4gdG8gZXh0ZW5kIHRoaXMg
dG8gREhDUHY0LiBXZSBhcmUgZ29pbmcgdG8gc3VibWl0IGFuIGluZGl2aWR1YWwgMDAgdmVyc2lv
biBiZWZvcmUgdGhlIG5leHQgSUVURiBtZWV0aW5nLiBIb3dldmVyLCB0aGUgc2VjdXJlIERIQ1B2
NiBpcyBpbiBvdXIgcHJpb3JpdHkgZm9yIG5vdy4gOikNCg0KQmVzdCByZWdhcmRzLA0KDQpTaGVu
ZyArIERhY2hlbmcNCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogZGhjd2cg
W21haWx0bzpkaGN3Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQmVybmllIFZvbHog
KHZvbHopDQo+U2VudDogRnJpZGF5LCBNYXkgMDIsIDIwMTQgODozNCBQTQ0KPlRvOiDnpZ7mmI7p
gZTlk4k7IFRvbWVrIE1ydWdhbHNraQ0KPkNjOiBkaGN3Zw0KPlN1YmplY3Q6IFJlOiBbZGhjd2dd
IFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhjLXNlZGhjcHY2LTAyIC0gUmVzcG9uZCBieSBNYXkNCj4x
OA0KPg0KPkppbm1laToNCj4NCj5UaGFua3MgZm9yIHlvdXIgcmV2aWV3IGFuZCBmZWVkYmFjay4N
Cj4NCj5SZWdhcmRpbmcgeW91ciBmaXJzdCBwb2ludCwgdGhlcmUncyBwcm9iYWJseSBub3RoaW5n
IChleGNlcHQgdGhlIG9wdGlvbiBsZW5ndGgNCj5saW1pdGF0aW9ucywgdGhvdWdoIFJGQyAzMzk2
IGhhbmRsZXMgdGhhdCkgdGhhdCB3b3VsZCBwcmV2ZW50IHRoaXMgZnJvbSBiZWluZw0KPmFkb3B0
ZWQgZm9yIERIQ1B2NC4gQnV0IGl0IGlzIGluZGVlZCBhIHF1ZXN0aW9uIG9mIHdoZXRoZXIgYWR2
YW5jaW5nDQo+REhDUHY0IGlzIGFzIGltcG9ydGFudCBhcyBhZHZhbmNpbmcgREhDUHY2LiBBbHNv
LCB0aGUgREhDIFdHIGNoYXJ0ZXIgaXMNCj5mb2N1c2VkIG9uIERIQ1B2Ni4NCj4NCj5JZiB0aGlz
IHdvcmsgZG9lcyBhZHZhbmNlLCBhbmQgdGhlcmUncyBzdWZmaWNpZW50IGludGVyZXN0LCBJIGNv
dWxkIHdlbGwgc2VlDQo+c29tZW9uZSBwcm9wb3NpbmcgdGhlIHNhbWUgZm9yIERIQ1B2NC4NCj4N
Cj4tIEJlcm5pZQ0KPg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogZGhjd2cg
W21haWx0bzpkaGN3Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgPz8/Pw0KPlNlbnQ6
IFdlZG5lc2RheSwgQXByaWwgMzAsIDIwMTQgMTozMCBQTQ0KPlRvOiBUb21layBNcnVnYWxza2kN
Cj5DYzogZGhjd2cNCj5TdWJqZWN0OiBSZTogW2RoY3dnXSBXR0xDIGZvciBkcmFmdC1pZXRmLWRo
Yy1zZWRoY3B2Ni0wMiAtIFJlc3BvbmQgYnkgTWF5DQo+MTgNCj4NCj5BdCBUdWUsIDI5IEFwciAy
MDE0IDIwOjIxOjMzICswMjAwLA0KPlRvbWVrIE1ydWdhbHNraSA8dG9tYXN6Lm1ydWdhbHNraUBn
bWFpbC5jb20+IHdyb3RlOg0KPg0KPj4gU2luY2Ugd2UgaGF2ZSB1cGNvbWluZyBob2xpZGF5IG9u
IE1heSAxc3QgKHdoaWNoIGhhcHBlbnMgdG8gYmUgYQ0KPj4gcmVhc29uIGZvciBleHRlbmRlZCB3
ZWVrZW5kIGluIG1hbnkgcGFydHMgb2YgRXVyb3BlKSBhbmQgdGhlIHRvcGljIGluDQo+PiBxdWVz
dGlvbiBpcyBub3QgdHJpdmlhbCwgdGhpcyBXR0xDIGlzIGEgYml0IGxvbmdlciB0aGFuIHVzdWFs
Lg0KPj4NCj4+IFBsZWFzZSBzZW5kIHlvdXIgY29tbWVudHMgYnkgTWF5IDE4dGggMjAxNC4gSWYg
eW91IGRvIG5vdCBmZWVsIHRoaXMNCj4+IGRvY3VtZW50IHNob3VsZCBhZHZhbmNlLCBwbGVhc2Ug
c3RhdGUgeW91ciByZWFzb25zIHdoeS4NCj4NCj5JJ3ZlIHJlYWQgdGhlIGRvY3VtZW50LiAgSSBk
b24ndCBoYXZlIGEgcGFydGljdWxhciBvcGluaW9uIG9uIHdoZXRoZXIgaXQNCj5zaG91bGQgYWR2
YW5jZSwgbWFpbmx5IGJlY2F1c2UgSSdtIG5vdCBhIHNlY3VyaXR5IGV4cGVydC4gIEkgaGF2ZSBz
b21lDQo+Y29tbWVudHMgdGhhdCBtYXkgaG9wZWZ1bGx5IGJlIHVzZWZ1bCwgdGhvdWdoOg0KPg0K
PlNvbWUgaGlnaGVyIGxldmVsIHBvaW50cw0KPi0gKG1heWJlIGFscmVhZHkgZGlzY3Vzc2VkIGJl
Zm9yZSBidXQpIHRoZSBjb25jZXB0IG9mIHVzaW5nIHB1YmxpYyBrZXkNCj4gIGF1dGhlbnRpY2F0
aW9uIGluIERIQ1AgbWFrZXMgc29tZSBzZW5zZSB0byBtZSwgYnV0IEkgd29uZGVyIHdoeSB3ZQ0K
PiAgYXJlIGRpc2N1c3NpbmcgdGhpcyBzcGVjaWZpY2FsbHkgZm9yIERIQ1B2Ni4gIEFzIGZhciBh
cyBJIGtub3cNCj4gIHRoZXJlJ3Mgbm8gc3VjaCBjb3VudGVycGFydCBpbiBESENQdjQgKHRoZSBv
bmx5IHJlbGF0ZWQgdGhpbmcgSSBjYW4NCj4gIGdvb2dsZSBpcyBkcmFmdC1ndXB0YS1kaGNwLWF1
dGgtMDIudHh0LCB3aGljaCBleHBpcmVkIGxvbmcgYWdvKSwgYW0NCj4gIEkgY29ycmVjdD8gIElm
IHNvLCBpcyB0aGF0IGJlY2F1c2UgKnY0IGlzIGp1c3QgdG9vIGxlZ2FjeSBhbmQgaXNuJ3QNCj4g
IHdvcnRoIGltcHJvdmVtZW50cyBhbnltb3JlPyAgT3IgZG9lcyB0aGF0IHJlZmxlY3Qgc29tZSBE
SENQIHNwZWNpZmljDQo+ICBwb2ludHMgdGhhdCBtYWtlIHB1YmxpYyBrZXkgYXV0aGVudGljYXRp
b24gbm90IHNvIHZpYWJsZT8gIElmIGl0J3MNCj4gIHRoZSBsYXR0ZXIsIGRvZXNuJ3QgaXQgYWxz
byBhcHBseSB0byB0aGlzIHByb3Bvc2FsPw0KPg0KPi0gVGhlIGRlc2NyaXB0aW9uIG9mIHRoZSBk
cmFmdCBpcyBhIGJpdCB2YWd1ZSAod2hpY2ggbWF5IGhhdmUgdG8gYmUNCj4gIGNsYXJpZmllZCBh
bnl3YXkpLCBidXQgaWYgSSB1bmRlcnN0YW5kIGl0IGNvcnJlY3RseSwgaXQgYXNzdW1lcyB0aGF0
DQo+ICBib3RoIGNsaWVudHMgKGVhY2ggb2YgdGhlbSkgYW5kIHNlcnZlcnMgbWFpbnRhaW4gdGhl
aXIgcGFpciBvZg0KPiAgcHVibGljLXByaXZhdGUga2V5cywgYW5kIGEgY2xpZW50IG9mZmVycyBh
bmQgdXNlcyBpdHMgb3duIGtleSB0bw0KPiAgYXV0aGVudGljYXRlIG1lc3NhZ2VzIGZyb20gdGhl
IGNsaWVudCB0byBzZXJ2ZXJzLiAgSXMgdGhhdCBjb3JyZWN0Pw0KPiAgSWYgc28sIGRvZXMgdGhp
cyBtYWtlIHNlbnNlPyAgTXkgZ2VuZXJhbCB1bmRlcnN0YW5kaW5nIGlzIHRoYXQNCj4gIGF1dGhl
bnRpY2F0aW5nIERIQ1AgbWVzc2FnZXMgZnJvbSBjbGllbnRzIHRvIHNlcnZlciBpcyBub3QgdGhh
dA0KPiAgY3JpdGljYWwsIGFuZCBpdCdzIHF1aXRlIHVubGlrZWx5IHRoYXQgc2VydmVycyBtYWlu
dGFpbiBwdWJsaWMga2V5cw0KPiAgb2YgYWxsIHBvc3NpYmxlIGNsaWVudHMgc28gdGhlIHNlcnZl
cnMgd291bGQgaGF2ZSB0byByZWx5IG9uIHRoZQ0KPiAgbGVhcC1vZi1mYWl0aCBtb2RlbC4gIFRo
ZXkgdGhlbiBtYXkgaGF2ZSB0byB3b3JyeSBhYm91dCB0aGUNCj4gICJyZXNvdXJjZSBleGhhdXN0
aW9uIGF0dGFja3MiIChhbHRob3VnaCBJJ20gbm90IHN1cmUgaWYgdGhpcyBpcyBhDQo+ICBiaWcg
aXNzdWUsIHNlZSBiZWxvdykuDQo+DQo+T3RoZXIgbm9uIGVkaXRvcmlhbCBjb21tZW50cyBvbiB0
aGUgZHJhZnQ6DQo+LSBTZWN0aW9uIDUuMToNCj4gICBQdWJsaWMgS2V5ICAgICBBIHZhcmlhYmxl
LWxlbmd0aCBmaWVsZCBjb250YWluaW5nIHB1YmxpYyBrZXkuIFRoZQ0KPiAgICAgICAgICAgICAg
ICAgIGtleSBNVVNUIGJlIHJlcHJlc2VudGVkIGFzIGEgbG93ZXItY2FzZSBoZXhhZGVjaW1hbA0K
PiAgICAgICAgICAgICAgICAgIHN0cmluZyB3aXRoIHRoZSBtb3N0IHNpZ25pZmljYW50IG9jdGV0
IG9mIHRoZSBrZXkNCj4gICAgICAgICAgICAgICAgICBmaXJzdC4gVHlwaWNhbGx5LCB0aGUgbGVu
Z3RoIG9mIGEgMjA0OC1iaXQgUlNBDQo+DQo+ICBJcyB0aGVyZSBhbnkgc3BlY2lmaWMgcmVhc29u
IGl0J3MgcmVwcmVzZW50ZWQgYXMgYSBzdHJpbmc/ICBOb3QNCj4gIG5lY2Vzc2FyaWx5IGJhZCwg
YnV0IEkgdGhvdWdodCBtb3JlIGNvbW1vbiBwcmFjdGljZSBoZXJlIGlzIHRvDQo+ICBzaW1wbHkg
dXNlIHRoZSBiaW5hcnkgdmFsdWUgb2YgdGhlIGtleS4gIERIQ1Agb3B0aW9ucyBpbiB3aXJlIGZv
cm1hdA0KPiAgYXJlIG5vdCBleHBlY3RlZCB0byBiZSBodW1hbiByZWFkYWJsZSBhbnl3YXksIHNv
IEkgZG9uJ3Qgc2VlIHRoZQ0KPiAgcG9pbnQgZm9yIHVzaW5nIGEgc3RyaW5nIGhlcmUuDQo+DQo+
LSBJbiBTZWN0aW9uIDYuMjoNCj4NCj4gICBPbiB0aGUgcmVjaXBpZW50IHRoYXQgc3VwcG9ydHMg
dGhlIGxlYXAgb2YgZmFpdGggbW9kZWwsIHRoZSBudW1iZXIgb2YNCj4gICBjYWNoZWQgcHVibGlj
IGtleXMgb3IgdW52ZXJpZmlhYmxlIGNlcnRpZmljYXRlcyBNVVNUIGJlIGxpbWl0ZWQgaW4NCj4g
ICBvcmRlciB0byBwcm90ZWN0IGFnYWluc3QgcmVzb3VyY2UgZXhoYXVzdGlvbiBhdHRhY2tzLiAg
SWYgdGhlDQo+DQo+ICBUaGlzIGlzIG1haW5seSBjb25jZXJuZWQgYWJvdXQgc2VydmVycywgY29y
cmVjdD8gIElmIHNvLCBJJ20gbm90DQo+ICBzdXJlIGhvdyBzZXZlcmUgdGhpcyAiYXR0YWNrcyIg
YXJlOyBESENQIHNlcnZlcnMgZ2VuZXJhbGx5IG5lZWQgdG8NCj4gIG1haW50YWluIHNvbWUgc3Rh
dGUgZm9yIGVhY2ggY2xpZW50ICh1bmxlc3MgdGhhdCdzIHN0YXRlbGVzcyBvbmx5DQo+ICBzZXJ2
ZXIpIGFuZCB3b3VsZCBuYXR1cmFsbHkgYWxyZWFkeSBoYXZlIHNvbWUgbGltaXRhdGlvbiBvbiB0
aGF0DQo+ICByZXNvdXJjZS4gIFNob3VsZG4ndCB0aGUgZ2VuZXJhbCBkZWZlbnNlIGJlIGVub3Vn
aCBmb3IgdGhpcw0KPiAgcGFydGljdWxhciByZXNvdXJjZSwgdG9vPyAgKEJ1dCBJIHdhcyBhbHNv
IG5vdCBzdXJlIGlmIGl0IG1ha2VzDQo+ICBzZW5zZSB0byB1c2UgKHB1YmxpYyBrZXkpIGF1dGhl
bnRpY2F0aW9uIGZvciBtZXNzYWdlcyBmcm9tIGNsaWVudHMNCj4gIGluIHRoZSBmaXJzdCBwbGFj
ZTsgc2VlIGhpZ2hlci1sZXZlbCBkaXNjdXNzaW9ucyBhYm92ZSkNCj4NCj4tIFJlbGF0ZWQsIGl0
IHNlZW1zIHNvbWUgcGFydCBvZiBTZWN0aW9uIDYuMiBpcyBtb3JlIHNwZWNpZmljIGZvcg0KPiAg
Y2xpZW50cyBhbmQgc29tZSBvdGhlciBwYXJ0IGlzIG1vcmUgc3BlY2lmaWMgdG8gc2VydmVycy4g
IFNvIGl0IG1heQ0KPiAgYmUgaGVscGZ1bCBpZiB3ZSBoYXZlIHNlcGFyYXRlIHN1YnNlY3Rpb25z
IGZvY3VzaW5nIG9uIHRoZXNlDQo+ICBwYXJ0aWN1bGFyIGNhc2VzLiAgSnVzdCBhIHN1Z2dlc3Rp
b24uDQo+DQo+RWRpdG9yaWFsIG5pdHM6DQo+LSBTZWN0aW9uIDQuMw0KPiAgIHRoZXkgbWF5IGZh
bGwgYmFjayB0aGUgdW5zZWN1cmUgbW9kZWwsIGlmIGJvdGggY2xpZW50IGFuZCBzZXJ2ZXINCj4g
IHMvZmFsbCBiYWNrIHRoZS9mYWxsIGJhY2sgdG8gdGhlLw0KPiAgKEkgZm91bmQgdGhlIG1pc3Np
bmcgJ3RvJyBvZiB0aGlzIGtpbmQgaW4gc2V2ZXJhbCBvdGhlciBwbGFjZXMgaW4NCj4gIHRoZSBk
cmFmdCkNCj4NCj4tIFNlY3Rpb24gNC4zDQo+ICAgd2hldGhlciB0byBhY2NlcHQgdGhlIG1lc3Nh
Z2VzLiAgSWYgdGhlIGNsaWVudCBhY2NlcHQgdGhlIHVuc2VjdXJlDQo+ICAgbWVzc2FnZXMgZnJv
bSB0aGUgREhDUHY2IHNlcnZlci4gIFRoZSBzdWJzZXF1ZW50IGV4Y2hhbmdlcyB3aWxsIGJlIGlu
DQo+ICAgdW5zZWN1cmUgbW9kZWwuDQo+ICBzL3NlcnZlci4gIFRoZS9zZXJ2ZXIsIHRoZS8NCj4N
Cj4tIFNlY3Rpb24gNC4zDQo+ICAgb24gdGhlIHNlcnZlciBwb2xpY3kuICBJZiB0aGUgc2VydmVy
IG1hbmRpZGF0ZXMgdGhlIGF1dGhlbnRpY2F0aW9uLA0KPiAgcy9tYW5kaWRhdGVzL21hbmRhdGVz
Lw0KPg0KPi0gU2VjdGlvbiA2LjENCj4gICBtZXNzYWdlcywgTVVTVCBjb250YWluIGVpdGhlciBh
IHRoZSBQdWJsaWMgS2V5IG9yIENlcnRpZmljYXRlIG9wdGlvbiwNCj4gIHMvYSB0aGUvdGhlLyAo
PykNCj4NCj4tIFNlY3Rpb24gNi4yDQo+ICAgZXJyb3Igc3RhdHVzIGNvZGUsIGRlZmluZWQgaW4g
U2VjdGlvbiA1LjQsIGJhY2sgdG8gdGhlIGNsaWVudC4uDQo+ICBzLy4uLy4vDQo+DQo+LS0NCj5K
SU5NRUksIFRhdHV5YQ0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+ZGhjd2cgbWFpbGluZyBsaXN0DQo+ZGhjd2dAaWV0Zi5vcmcNCj5odHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RoY3dnDQo+DQo+X19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5kaGN3ZyBtYWlsaW5nIGxpc3QNCj5k
aGN3Z0BpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhj
d2cNCg==


From nobody Tue May  6 00:00:33 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 269741A025F for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 00:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 KlSDJ9aXcYEI for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 00:00:30 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 678451A025E for <dhcwg@ietf.org>; Tue,  6 May 2014 00:00:29 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGL16274; Tue, 06 May 2014 07:00:25 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 May 2014 07:59:09 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 May 2014 08:00:23 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Tue, 6 May 2014 15:00:20 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ralph Droms <rdroms.ietf@gmail.com>, "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPY9fqOkQX2Up+wk+VaPjsYGUK15sp5cSAgALR/YCAAAxhgIAGX9Jg
Date: Tue, 6 May 2014 07:00:19 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com>
In-Reply-To: <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Qg1uAQm0YqNeXMhE4neLR5xdbfg
Cc: dhcwg <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 07:00:32 -0000

Pkkgd291bGQgbGlrZSB0byBzZWUgc29tZSBjb25zaWRlcmF0aW9uIG9mIHRoZSB0b3RhbCBsZW5n
dGggb2YgREhDUHY2DQo+bWVzc2FnZXMgdGhhdCB1c2UgdGhpcyBzZWN1cml0eSBwcm90b2NvbCBp
bmNsdWRlZCBpbiB0aGUgZG9jdW1lbnQuDQoNCkhpLCBSYWxwaCwNCg0KV2UgY291bGQgZ2l2ZSBj
b25zaWRlcmF0aW9uIG9mIHRoZSB0b3RhbCBsZW5ndGggb2YgREhDUHY2IG1lc3NhZ2VzIGluIHRo
ZSBjdXJyZW50IGRyYWZ0LiBUaGUgbWVzc2FnZSBsZW5ndGggYXJlIHZhcmlhYmxlIGJlY2F1c2Ug
dGhlcmUgYXJlIGZldyB2YXJpYWJsZSBmaWVsZCBpbiB0aGUgbWVzc2FnZSwgc3VjaCBhcyBwdWJs
aWMga2V5L2NlcnRpZmljYXRlICYgc2lnbmF0dXJlLCBldGMuIFdlIGV4cGVjdCB0aGUgbGVuZ3Ro
IG9mIHRoZSBtZXNzYWdlIHNob3VsZCBub3QgZXhjZWVkIHRoZSBtYXhpbXVtIGxlbmd0aCBvZiBV
RFAgcGFja2V0Lg0KDQpIb3dldmVyLCB3ZSBkbyBOT1Qgc2VlIHJlYXNvbnMgd2h5IHRoaXMgd291
bGQgYmUgYSBwcm9ibGVtLiBDb3VsZCBwbGVhc2UgeW91IHNoYXJlIHlvdXIgY29uY2VybnMgd2l0
aCB1cz8gU28gdGhhdCwgd2UgY2FuIGJldHRlciBhZGRyZXNzIHRoZSBjb25zaWRlcmF0aW9uLg0K
DQpSZWdhcmRzLA0KDQpTaGVuZyArIERhY2hlbmcNCg0KPi0gUmFscGgNCj4NCj4+DQo+PiBJZiB0
aGlzIHdvcmsgZG9lcyBhZHZhbmNlLCBhbmQgdGhlcmUncyBzdWZmaWNpZW50IGludGVyZXN0LCBJ
IGNvdWxkIHdlbGwgc2VlDQo+c29tZW9uZSBwcm9wb3NpbmcgdGhlIHNhbWUgZm9yIERIQ1B2NC4N
Cj4+DQo+PiAtIEJlcm5pZQ0KPj4NCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiBG
cm9tOiBkaGN3ZyBbbWFpbHRvOmRoY3dnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiA/
Pz8/DQo+PiBTZW50OiBXZWRuZXNkYXksIEFwcmlsIDMwLCAyMDE0IDE6MzAgUE0NCj4+IFRvOiBU
b21layBNcnVnYWxza2kNCj4+IENjOiBkaGN3Zw0KPj4gU3ViamVjdDogUmU6IFtkaGN3Z10gV0dM
QyBmb3IgZHJhZnQtaWV0Zi1kaGMtc2VkaGNwdjYtMDIgLSBSZXNwb25kIGJ5DQo+TWF5IDE4DQo+
Pg0KPj4gQXQgVHVlLCAyOSBBcHIgMjAxNCAyMDoyMTozMyArMDIwMCwNCj4+IFRvbWVrIE1ydWdh
bHNraSA8dG9tYXN6Lm1ydWdhbHNraUBnbWFpbC5jb20+IHdyb3RlOg0KPj4NCj4+PiBTaW5jZSB3
ZSBoYXZlIHVwY29taW5nIGhvbGlkYXkgb24gTWF5IDFzdCAod2hpY2ggaGFwcGVucyB0byBiZSBh
DQo+Pj4gcmVhc29uIGZvciBleHRlbmRlZCB3ZWVrZW5kIGluIG1hbnkgcGFydHMgb2YgRXVyb3Bl
KSBhbmQgdGhlIHRvcGljIGluDQo+Pj4gcXVlc3Rpb24gaXMgbm90IHRyaXZpYWwsIHRoaXMgV0dM
QyBpcyBhIGJpdCBsb25nZXIgdGhhbiB1c3VhbC4NCj4+Pg0KPj4+IFBsZWFzZSBzZW5kIHlvdXIg
Y29tbWVudHMgYnkgTWF5IDE4dGggMjAxNC4gSWYgeW91IGRvIG5vdCBmZWVsIHRoaXMNCj4+PiBk
b2N1bWVudCBzaG91bGQgYWR2YW5jZSwgcGxlYXNlIHN0YXRlIHlvdXIgcmVhc29ucyB3aHkuDQo+
Pg0KPj4gSSd2ZSByZWFkIHRoZSBkb2N1bWVudC4gIEkgZG9uJ3QgaGF2ZSBhIHBhcnRpY3VsYXIg
b3BpbmlvbiBvbiB3aGV0aGVyIGl0DQo+c2hvdWxkIGFkdmFuY2UsIG1haW5seSBiZWNhdXNlIEkn
bSBub3QgYSBzZWN1cml0eSBleHBlcnQuICBJIGhhdmUgc29tZQ0KPmNvbW1lbnRzIHRoYXQgbWF5
IGhvcGVmdWxseSBiZSB1c2VmdWwsIHRob3VnaDoNCj4+DQo+PiBTb21lIGhpZ2hlciBsZXZlbCBw
b2ludHMNCj4+IC0gKG1heWJlIGFscmVhZHkgZGlzY3Vzc2VkIGJlZm9yZSBidXQpIHRoZSBjb25j
ZXB0IG9mIHVzaW5nIHB1YmxpYyBrZXkNCj4+ICBhdXRoZW50aWNhdGlvbiBpbiBESENQIG1ha2Vz
IHNvbWUgc2Vuc2UgdG8gbWUsIGJ1dCBJIHdvbmRlciB3aHkgd2UNCj4+ICBhcmUgZGlzY3Vzc2lu
ZyB0aGlzIHNwZWNpZmljYWxseSBmb3IgREhDUHY2LiAgQXMgZmFyIGFzIEkga25vdw0KPj4gIHRo
ZXJlJ3Mgbm8gc3VjaCBjb3VudGVycGFydCBpbiBESENQdjQgKHRoZSBvbmx5IHJlbGF0ZWQgdGhp
bmcgSSBjYW4NCj4+ICBnb29nbGUgaXMgZHJhZnQtZ3VwdGEtZGhjcC1hdXRoLTAyLnR4dCwgd2hp
Y2ggZXhwaXJlZCBsb25nIGFnbyksIGFtDQo+PiAgSSBjb3JyZWN0PyAgSWYgc28sIGlzIHRoYXQg
YmVjYXVzZSAqdjQgaXMganVzdCB0b28gbGVnYWN5IGFuZCBpc24ndA0KPj4gIHdvcnRoIGltcHJv
dmVtZW50cyBhbnltb3JlPyAgT3IgZG9lcyB0aGF0IHJlZmxlY3Qgc29tZSBESENQIHNwZWNpZmlj
DQo+PiAgcG9pbnRzIHRoYXQgbWFrZSBwdWJsaWMga2V5IGF1dGhlbnRpY2F0aW9uIG5vdCBzbyB2
aWFibGU/ICBJZiBpdCdzDQo+PiAgdGhlIGxhdHRlciwgZG9lc24ndCBpdCBhbHNvIGFwcGx5IHRv
IHRoaXMgcHJvcG9zYWw/DQo+Pg0KPj4gLSBUaGUgZGVzY3JpcHRpb24gb2YgdGhlIGRyYWZ0IGlz
IGEgYml0IHZhZ3VlICh3aGljaCBtYXkgaGF2ZSB0byBiZQ0KPj4gIGNsYXJpZmllZCBhbnl3YXkp
LCBidXQgaWYgSSB1bmRlcnN0YW5kIGl0IGNvcnJlY3RseSwgaXQgYXNzdW1lcyB0aGF0DQo+PiAg
Ym90aCBjbGllbnRzIChlYWNoIG9mIHRoZW0pIGFuZCBzZXJ2ZXJzIG1haW50YWluIHRoZWlyIHBh
aXIgb2YNCj4+ICBwdWJsaWMtcHJpdmF0ZSBrZXlzLCBhbmQgYSBjbGllbnQgb2ZmZXJzIGFuZCB1
c2VzIGl0cyBvd24ga2V5IHRvDQo+PiAgYXV0aGVudGljYXRlIG1lc3NhZ2VzIGZyb20gdGhlIGNs
aWVudCB0byBzZXJ2ZXJzLiAgSXMgdGhhdCBjb3JyZWN0Pw0KPj4gIElmIHNvLCBkb2VzIHRoaXMg
bWFrZSBzZW5zZT8gIE15IGdlbmVyYWwgdW5kZXJzdGFuZGluZyBpcyB0aGF0DQo+PiAgYXV0aGVu
dGljYXRpbmcgREhDUCBtZXNzYWdlcyBmcm9tIGNsaWVudHMgdG8gc2VydmVyIGlzIG5vdCB0aGF0
DQo+PiAgY3JpdGljYWwsIGFuZCBpdCdzIHF1aXRlIHVubGlrZWx5IHRoYXQgc2VydmVycyBtYWlu
dGFpbiBwdWJsaWMga2V5cw0KPj4gIG9mIGFsbCBwb3NzaWJsZSBjbGllbnRzIHNvIHRoZSBzZXJ2
ZXJzIHdvdWxkIGhhdmUgdG8gcmVseSBvbiB0aGUNCj4+ICBsZWFwLW9mLWZhaXRoIG1vZGVsLiAg
VGhleSB0aGVuIG1heSBoYXZlIHRvIHdvcnJ5IGFib3V0IHRoZQ0KPj4gICJyZXNvdXJjZSBleGhh
dXN0aW9uIGF0dGFja3MiIChhbHRob3VnaCBJJ20gbm90IHN1cmUgaWYgdGhpcyBpcyBhDQo+PiAg
YmlnIGlzc3VlLCBzZWUgYmVsb3cpLg0KPj4NCj4+IE90aGVyIG5vbiBlZGl0b3JpYWwgY29tbWVu
dHMgb24gdGhlIGRyYWZ0Og0KPj4gLSBTZWN0aW9uIDUuMToNCj4+ICAgUHVibGljIEtleSAgICAg
QSB2YXJpYWJsZS1sZW5ndGggZmllbGQgY29udGFpbmluZyBwdWJsaWMga2V5LiBUaGUNCj4+ICAg
ICAgICAgICAgICAgICAga2V5IE1VU1QgYmUgcmVwcmVzZW50ZWQgYXMgYSBsb3dlci1jYXNlDQo+
aGV4YWRlY2ltYWwNCj4+ICAgICAgICAgICAgICAgICAgc3RyaW5nIHdpdGggdGhlIG1vc3Qgc2ln
bmlmaWNhbnQgb2N0ZXQgb2YgdGhlIGtleQ0KPj4gICAgICAgICAgICAgICAgICBmaXJzdC4gVHlw
aWNhbGx5LCB0aGUgbGVuZ3RoIG9mIGEgMjA0OC1iaXQgUlNBDQo+Pg0KPj4gIElzIHRoZXJlIGFu
eSBzcGVjaWZpYyByZWFzb24gaXQncyByZXByZXNlbnRlZCBhcyBhIHN0cmluZz8gIE5vdA0KPj4g
IG5lY2Vzc2FyaWx5IGJhZCwgYnV0IEkgdGhvdWdodCBtb3JlIGNvbW1vbiBwcmFjdGljZSBoZXJl
IGlzIHRvDQo+PiAgc2ltcGx5IHVzZSB0aGUgYmluYXJ5IHZhbHVlIG9mIHRoZSBrZXkuICBESENQ
IG9wdGlvbnMgaW4gd2lyZSBmb3JtYXQNCj4+ICBhcmUgbm90IGV4cGVjdGVkIHRvIGJlIGh1bWFu
IHJlYWRhYmxlIGFueXdheSwgc28gSSBkb24ndCBzZWUgdGhlDQo+PiAgcG9pbnQgZm9yIHVzaW5n
IGEgc3RyaW5nIGhlcmUuDQo+Pg0KPj4gLSBJbiBTZWN0aW9uIDYuMjoNCj4+DQo+PiAgIE9uIHRo
ZSByZWNpcGllbnQgdGhhdCBzdXBwb3J0cyB0aGUgbGVhcCBvZiBmYWl0aCBtb2RlbCwgdGhlIG51
bWJlciBvZg0KPj4gICBjYWNoZWQgcHVibGljIGtleXMgb3IgdW52ZXJpZmlhYmxlIGNlcnRpZmlj
YXRlcyBNVVNUIGJlIGxpbWl0ZWQgaW4NCj4+ICAgb3JkZXIgdG8gcHJvdGVjdCBhZ2FpbnN0IHJl
c291cmNlIGV4aGF1c3Rpb24gYXR0YWNrcy4gIElmIHRoZQ0KPj4NCj4+ICBUaGlzIGlzIG1haW5s
eSBjb25jZXJuZWQgYWJvdXQgc2VydmVycywgY29ycmVjdD8gIElmIHNvLCBJJ20gbm90DQo+PiAg
c3VyZSBob3cgc2V2ZXJlIHRoaXMgImF0dGFja3MiIGFyZTsgREhDUCBzZXJ2ZXJzIGdlbmVyYWxs
eSBuZWVkIHRvDQo+PiAgbWFpbnRhaW4gc29tZSBzdGF0ZSBmb3IgZWFjaCBjbGllbnQgKHVubGVz
cyB0aGF0J3Mgc3RhdGVsZXNzIG9ubHkNCj4+ICBzZXJ2ZXIpIGFuZCB3b3VsZCBuYXR1cmFsbHkg
YWxyZWFkeSBoYXZlIHNvbWUgbGltaXRhdGlvbiBvbiB0aGF0DQo+PiAgcmVzb3VyY2UuICBTaG91
bGRuJ3QgdGhlIGdlbmVyYWwgZGVmZW5zZSBiZSBlbm91Z2ggZm9yIHRoaXMNCj4+ICBwYXJ0aWN1
bGFyIHJlc291cmNlLCB0b28/ICAoQnV0IEkgd2FzIGFsc28gbm90IHN1cmUgaWYgaXQgbWFrZXMN
Cj4+ICBzZW5zZSB0byB1c2UgKHB1YmxpYyBrZXkpIGF1dGhlbnRpY2F0aW9uIGZvciBtZXNzYWdl
cyBmcm9tIGNsaWVudHMNCj4+ICBpbiB0aGUgZmlyc3QgcGxhY2U7IHNlZSBoaWdoZXItbGV2ZWwg
ZGlzY3Vzc2lvbnMgYWJvdmUpDQo+Pg0KPj4gLSBSZWxhdGVkLCBpdCBzZWVtcyBzb21lIHBhcnQg
b2YgU2VjdGlvbiA2LjIgaXMgbW9yZSBzcGVjaWZpYyBmb3INCj4+ICBjbGllbnRzIGFuZCBzb21l
IG90aGVyIHBhcnQgaXMgbW9yZSBzcGVjaWZpYyB0byBzZXJ2ZXJzLiAgU28gaXQgbWF5DQo+PiAg
YmUgaGVscGZ1bCBpZiB3ZSBoYXZlIHNlcGFyYXRlIHN1YnNlY3Rpb25zIGZvY3VzaW5nIG9uIHRo
ZXNlDQo+PiAgcGFydGljdWxhciBjYXNlcy4gIEp1c3QgYSBzdWdnZXN0aW9uLg0KPj4NCj4+IEVk
aXRvcmlhbCBuaXRzOg0KPj4gLSBTZWN0aW9uIDQuMw0KPj4gICB0aGV5IG1heSBmYWxsIGJhY2sg
dGhlIHVuc2VjdXJlIG1vZGVsLCBpZiBib3RoIGNsaWVudCBhbmQgc2VydmVyDQo+PiAgcy9mYWxs
IGJhY2sgdGhlL2ZhbGwgYmFjayB0byB0aGUvDQo+PiAgKEkgZm91bmQgdGhlIG1pc3NpbmcgJ3Rv
JyBvZiB0aGlzIGtpbmQgaW4gc2V2ZXJhbCBvdGhlciBwbGFjZXMgaW4NCj4+ICB0aGUgZHJhZnQp
DQo+Pg0KPj4gLSBTZWN0aW9uIDQuMw0KPj4gICB3aGV0aGVyIHRvIGFjY2VwdCB0aGUgbWVzc2Fn
ZXMuICBJZiB0aGUgY2xpZW50IGFjY2VwdCB0aGUgdW5zZWN1cmUNCj4+ICAgbWVzc2FnZXMgZnJv
bSB0aGUgREhDUHY2IHNlcnZlci4gIFRoZSBzdWJzZXF1ZW50IGV4Y2hhbmdlcyB3aWxsIGJlDQo+
aW4NCj4+ICAgdW5zZWN1cmUgbW9kZWwuDQo+PiAgcy9zZXJ2ZXIuICBUaGUvc2VydmVyLCB0aGUv
DQo+Pg0KPj4gLSBTZWN0aW9uIDQuMw0KPj4gICBvbiB0aGUgc2VydmVyIHBvbGljeS4gIElmIHRo
ZSBzZXJ2ZXIgbWFuZGlkYXRlcyB0aGUgYXV0aGVudGljYXRpb24sDQo+PiAgcy9tYW5kaWRhdGVz
L21hbmRhdGVzLw0KPj4NCj4+IC0gU2VjdGlvbiA2LjENCj4+ICAgbWVzc2FnZXMsIE1VU1QgY29u
dGFpbiBlaXRoZXIgYSB0aGUgUHVibGljIEtleSBvciBDZXJ0aWZpY2F0ZSBvcHRpb24sDQo+PiAg
cy9hIHRoZS90aGUvICg/KQ0KPj4NCj4+IC0gU2VjdGlvbiA2LjINCj4+ICAgZXJyb3Igc3RhdHVz
IGNvZGUsIGRlZmluZWQgaW4gU2VjdGlvbiA1LjQsIGJhY2sgdG8gdGhlIGNsaWVudC4uDQo+PiAg
cy8uLi8uLw0KPj4NCj4+IC0tDQo+PiBKSU5NRUksIFRhdHV5YQ0KPj4NCj4+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBkaGN3ZyBtYWlsaW5nIGxp
c3QNCj4+IGRoY3dnQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2RoY3dnDQo+Pg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4+IGRoY3dnIG1haWxpbmcgbGlzdA0KPj4gZGhjd2dAaWV0Zi5vcmcNCj4+
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhjd2cNCj4NCj5fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPmRoY3dnIG1haWxpbmcg
bGlzdA0KPmRoY3dnQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9kaGN3Zw0K


From nobody Tue May  6 00:36:49 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 A09DC1A0269 for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 00:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.552
X-Spam-Level: 
X-Spam-Status: No, score=-4.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 09IuCTT-hiB8 for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 00:36:46 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8511A0265 for <dhcwg@ietf.org>; Tue,  6 May 2014 00:36:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDW12092; Tue, 06 May 2014 07:36:40 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 May 2014 08:35:25 +0100
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 May 2014 08:36:39 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Tue, 6 May 2014 15:36:35 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPY9fqOkQX2Up+wk+VaPjsYGUK15sp5cSAgAlKLTA=
Date: Tue, 6 May 2014 07:36:34 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com>
In-Reply-To: <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/RhOMNwhcH976ystZKXgWI59L_A4
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 07:36:47 -0000

SGksIEppbm1laSwNCg0KVGhhbmtzIGZvciB5b3VyIGVtYWlsLiBSZXBsaWVzIGluIGxpbmVzLg0K
DQo+LSAobWF5YmUgYWxyZWFkeSBkaXNjdXNzZWQgYmVmb3JlIGJ1dCkgdGhlIGNvbmNlcHQgb2Yg
dXNpbmcgcHVibGljIGtleQ0KPiAgYXV0aGVudGljYXRpb24gaW4gREhDUCBtYWtlcyBzb21lIHNl
bnNlIHRvIG1lLCBidXQgSSB3b25kZXIgd2h5IHdlDQo+ICBhcmUgZGlzY3Vzc2luZyB0aGlzIHNw
ZWNpZmljYWxseSBmb3IgREhDUHY2LiAgQXMgZmFyIGFzIEkga25vdw0KPiAgdGhlcmUncyBubyBz
dWNoIGNvdW50ZXJwYXJ0IGluIERIQ1B2NCAodGhlIG9ubHkgcmVsYXRlZCB0aGluZyBJIGNhbg0K
PiAgZ29vZ2xlIGlzIGRyYWZ0LWd1cHRhLWRoY3AtYXV0aC0wMi50eHQsIHdoaWNoIGV4cGlyZWQg
bG9uZyBhZ28pLCBhbQ0KPiAgSSBjb3JyZWN0PyAgSWYgc28sIGlzIHRoYXQgYmVjYXVzZSAqdjQg
aXMganVzdCB0b28gbGVnYWN5IGFuZCBpc24ndA0KPiAgd29ydGggaW1wcm92ZW1lbnRzIGFueW1v
cmU/ICBPciBkb2VzIHRoYXQgcmVmbGVjdCBzb21lIERIQ1Agc3BlY2lmaWMNCj4gIHBvaW50cyB0
aGF0IG1ha2UgcHVibGljIGtleSBhdXRoZW50aWNhdGlvbiBub3Qgc28gdmlhYmxlPyAgSWYgaXQn
cw0KPiAgdGhlIGxhdHRlciwgZG9lc24ndCBpdCBhbHNvIGFwcGx5IHRvIHRoaXMgcHJvcG9zYWw/
DQoNClJlcGxpZWQgaW4gYW5vdGhlciBlbWFpbCwgdG9vLiBXZSBkbyBoYXZlIGEgcGxhbiB0byBl
eHRlbmQgaW4gREhDUHY0LiBIb3dldmVyLCBpdCB3b3VsZCBiZSBpbiBsb3dlciBwcmlvcml0eSBm
b3IgdXMgYW5kIGZvciBXRy4NCg0KPi0gVGhlIGRlc2NyaXB0aW9uIG9mIHRoZSBkcmFmdCBpcyBh
IGJpdCB2YWd1ZSAod2hpY2ggbWF5IGhhdmUgdG8gYmUNCj4gIGNsYXJpZmllZCBhbnl3YXkpLCBi
dXQgaWYgSSB1bmRlcnN0YW5kIGl0IGNvcnJlY3RseSwgaXQgYXNzdW1lcyB0aGF0DQo+ICBib3Ro
IGNsaWVudHMgKGVhY2ggb2YgdGhlbSkgYW5kIHNlcnZlcnMgbWFpbnRhaW4gdGhlaXIgcGFpciBv
Zg0KPiAgcHVibGljLXByaXZhdGUga2V5cywgYW5kIGEgY2xpZW50IG9mZmVycyBhbmQgdXNlcyBp
dHMgb3duIGtleSB0bw0KPiAgYXV0aGVudGljYXRlIG1lc3NhZ2VzIGZyb20gdGhlIGNsaWVudCB0
byBzZXJ2ZXJzLiAgSXMgdGhhdCBjb3JyZWN0Pw0KPiAgSWYgc28sIGRvZXMgdGhpcyBtYWtlIHNl
bnNlPyAgTXkgZ2VuZXJhbCB1bmRlcnN0YW5kaW5nIGlzIHRoYXQNCj4gIGF1dGhlbnRpY2F0aW5n
IERIQ1AgbWVzc2FnZXMgZnJvbSBjbGllbnRzIHRvIHNlcnZlciBpcyBub3QgdGhhdA0KPiAgY3Jp
dGljYWwsIGFuZCBpdCdzIHF1aXRlIHVubGlrZWx5IHRoYXQgc2VydmVycyBtYWludGFpbiBwdWJs
aWMga2V5cw0KPiAgb2YgYWxsIHBvc3NpYmxlIGNsaWVudHMgc28gdGhlIHNlcnZlcnMgd291bGQg
aGF2ZSB0byByZWx5IG9uIHRoZQ0KPiAgbGVhcC1vZi1mYWl0aCBtb2RlbC4gIFRoZXkgdGhlbiBt
YXkgaGF2ZSB0byB3b3JyeSBhYm91dCB0aGUNCj4gICJyZXNvdXJjZSBleGhhdXN0aW9uIGF0dGFj
a3MiIChhbHRob3VnaCBJJ20gbm90IHN1cmUgaWYgdGhpcyBpcyBhDQo+ICBiaWcgaXNzdWUsIHNl
ZSBiZWxvdykuDQo+DQo+T3RoZXIgbm9uIGVkaXRvcmlhbCBjb21tZW50cyBvbiB0aGUgZHJhZnQ6
DQo+LSBTZWN0aW9uIDUuMToNCj4gICBQdWJsaWMgS2V5ICAgICBBIHZhcmlhYmxlLWxlbmd0aCBm
aWVsZCBjb250YWluaW5nIHB1YmxpYyBrZXkuIFRoZQ0KPiAgICAgICAgICAgICAgICAgIGtleSBN
VVNUIGJlIHJlcHJlc2VudGVkIGFzIGEgbG93ZXItY2FzZSBoZXhhZGVjaW1hbA0KPiAgICAgICAg
ICAgICAgICAgIHN0cmluZyB3aXRoIHRoZSBtb3N0IHNpZ25pZmljYW50IG9jdGV0IG9mIHRoZSBr
ZXkNCj4gICAgICAgICAgICAgICAgICBmaXJzdC4gVHlwaWNhbGx5LCB0aGUgbGVuZ3RoIG9mIGEg
MjA0OC1iaXQgUlNBDQo+DQo+ICBJcyB0aGVyZSBhbnkgc3BlY2lmaWMgcmVhc29uIGl0J3MgcmVw
cmVzZW50ZWQgYXMgYSBzdHJpbmc/ICBOb3QNCj4gIG5lY2Vzc2FyaWx5IGJhZCwgYnV0IEkgdGhv
dWdodCBtb3JlIGNvbW1vbiBwcmFjdGljZSBoZXJlIGlzIHRvDQo+ICBzaW1wbHkgdXNlIHRoZSBi
aW5hcnkgdmFsdWUgb2YgdGhlIGtleS4gIERIQ1Agb3B0aW9ucyBpbiB3aXJlIGZvcm1hdA0KPiAg
YXJlIG5vdCBleHBlY3RlZCB0byBiZSBodW1hbiByZWFkYWJsZSBhbnl3YXksIHNvIEkgZG9uJ3Qg
c2VlIHRoZQ0KPiAgcG9pbnQgZm9yIHVzaW5nIGEgc3RyaW5nIGhlcmUuDQoNCldlIGJvcnJvdyB0
aGUgaWRlYXMgZnJvbSBtdWx0aXBsZSBvdGhlciBzZWN1cml0eSBtZWNoYW5pc21zIHN1Y2ggYXMg
cmZjIDcyMTAuIEJ1dCB5b3VyIGNvbmNlcm4gbWFrZXMgc2Vuc2UuIFdlIHdpbGwgY2hhbmdlIHRo
aXMgYWNjb3JkaW5nIHRvIHlvdXIgcG9pbnQuDQoNCj4tIEluIFNlY3Rpb24gNi4yOg0KPg0KPiAg
IE9uIHRoZSByZWNpcGllbnQgdGhhdCBzdXBwb3J0cyB0aGUgbGVhcCBvZiBmYWl0aCBtb2RlbCwg
dGhlIG51bWJlciBvZg0KPiAgIGNhY2hlZCBwdWJsaWMga2V5cyBvciB1bnZlcmlmaWFibGUgY2Vy
dGlmaWNhdGVzIE1VU1QgYmUgbGltaXRlZCBpbg0KPiAgIG9yZGVyIHRvIHByb3RlY3QgYWdhaW5z
dCByZXNvdXJjZSBleGhhdXN0aW9uIGF0dGFja3MuICBJZiB0aGUNCj4NCj4gIFRoaXMgaXMgbWFp
bmx5IGNvbmNlcm5lZCBhYm91dCBzZXJ2ZXJzLCBjb3JyZWN0PyAgSWYgc28sIEknbSBub3QNCj4g
IHN1cmUgaG93IHNldmVyZSB0aGlzICJhdHRhY2tzIiBhcmU7IERIQ1Agc2VydmVycyBnZW5lcmFs
bHkgbmVlZCB0bw0KPiAgbWFpbnRhaW4gc29tZSBzdGF0ZSBmb3IgZWFjaCBjbGllbnQgKHVubGVz
cyB0aGF0J3Mgc3RhdGVsZXNzIG9ubHkNCj4gIHNlcnZlcikgYW5kIHdvdWxkIG5hdHVyYWxseSBh
bHJlYWR5IGhhdmUgc29tZSBsaW1pdGF0aW9uIG9uIHRoYXQNCj4gIHJlc291cmNlLiAgU2hvdWxk
bid0IHRoZSBnZW5lcmFsIGRlZmVuc2UgYmUgZW5vdWdoIGZvciB0aGlzDQo+ICBwYXJ0aWN1bGFy
IHJlc291cmNlLCB0b28/ICANCg0KVGhlICJNVVNUIiBoZXJlIHNlZW1zIG5vdCBwcm9wZXIuIExl
dCB1cyByZXBsYWNlIGlzIHdpdGggIk1BWSIuIEl0IG1ha2VzIHRoaXMgcG9pbnQgb3B0aW9uYWwg
YW5kIHNob3VsZCBhZGRyZXNzIHlvdXIgY29uY2Vybi4NCg0KPkVkaXRvcmlhbCBuaXRzOg0KDQpF
ZGl0b3JpYWwgbml0cyB3aWxsIGJlIGZpeGVkLiA6KQ0KDQpCZXN0IHJlZ2FyZHMsDQoNClNoZW5n
ICsgRGFjaGVuZyANCg==


From nobody Tue May  6 04:24:28 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C351A02A7 for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 04:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5eZJdaqeoJ6L for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 04:24:24 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 00D311A01C7 for <dhcwg@ietf.org>; Tue,  6 May 2014 04:24:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8070; q=dns/txt; s=iport; t=1399375460; x=1400585060; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=bwWZGzVdqwaL1SQyWXmwXjdAMCRUfHeEev5gSVsu43I=; b=UnxMePUrREcD9+ECKEuzSK9heWJDdw9OhAXR7cFLn/CpJnFNrq9s/T1R bMe3AC9MWcyWPqt8Gm92t2L5LF09UgW+jz8i6igrNc12amMJIprGmQk1w HhJbN14ON3KNC8WMzETabwSiPwKYSrVXorAM37ZxU+uycWJXRjGHKeL7m E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjoFAGrFaFOtJA2M/2dsb2JhbABZgwZPWIJnujyHOYEcFnSCJQEBAQQBAQEeAUkDCwwEAgEIEQQBAQEBAwYFGAIDAiEGCxQJCAIEAQ0FCIglAxENi3GcGQGeWw2GRBMEgSeKHHiBPycxBwaCazmBFQSEWgKQZIIFjwyFYYM0gW1C
X-IronPort-AV: E=Sophos;i="4.97,996,1389744000"; d="scan'208";a="41390170"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-4.cisco.com with ESMTP; 06 May 2014 11:24:19 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s46BOJMY026928 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 6 May 2014 11:24:19 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Tue, 6 May 2014 06:24:19 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Sheng Jiang <jiangsheng@huawei.com>, Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPZJnNHMzNFfxEIk6wcBa/GM4ndJstOXMQgABjGYCABd/AgP//86lQ
Date: Tue, 6 May 2014 11:24:18 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.221.28]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Q2hH_cAyVUxORYUp5DyCeW90MaE
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 11:24:26 -0000

I suspect some of the issues here are:
1. Because socket interfaces are typically used, how large a buffer should =
clients, relays, and servers support? (Yes, it is possible to ask the socke=
t layer about how large a received packet is, but that requires two socket =
calls and I suspect is rarely done.)=20
2. If packets do exceed the MTU of the interface, fragmentation is required=
. As this is link-local (at least for first hop), probably not a big issue =
but does require fragmentation support (again, probably not a big issue exc=
ept if it was perhaps boot prom code - but why that would be using sedhcpv6=
 is unclear). Fragmentation for relay to server communication MIGHT be an i=
ssue if the traffic traverses firewalls?
3. As PMTU is harder with UDP traffic, it isn't clear how the fragmentation=
 MTU can easily be found. This may require clients, relays, and servers to =
support PMTU and be prepared for failures. Remember that with IPv6, fragmen=
tation is done by the end points - not the intermediate hops.

These issues aren't new, but they are more likely when sedhcpv6 is being us=
ed because we expect some of these options could be rather large (i.e., car=
rying certificates) and thus more likely require fragmentation.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Sheng Jiang
Sent: Tuesday, May 06, 2014 3:00 AM
To: Ralph Droms; Bernie Volz (volz)
Cc: dhcwg; =1B$B?@L@C#:H=1B(B
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 1=
8

>I would like to see some consideration of the total length of DHCPv6=20
>messages that use this security protocol included in the document.

Hi, Ralph,

We could give consideration of the total length of DHCPv6 messages in the c=
urrent draft. The message length are variable because there are few variabl=
e field in the message, such as public key/certificate & signature, etc. We=
 expect the length of the message should not exceed the maximum length of U=
DP packet.

However, we do NOT see reasons why this would be a problem. Could please yo=
u share your concerns with us? So that, we can better address the considera=
tion.

Regards,

Sheng + Dacheng

>- Ralph
>
>>
>> If this work does advance, and there's sufficient interest, I could=20
>> well see
>someone proposing the same for DHCPv4.
>>
>> - Bernie
>>
>> -----Original Message-----
>> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of ????
>> Sent: Wednesday, April 30, 2014 1:30 PM
>> To: Tomek Mrugalski
>> Cc: dhcwg
>> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by
>May 18
>>
>> At Tue, 29 Apr 2014 20:21:33 +0200,
>> Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:
>>
>>> Since we have upcoming holiday on May 1st (which happens to be a=20
>>> reason for extended weekend in many parts of Europe) and the topic=20
>>> in question is not trivial, this WGLC is a bit longer than usual.
>>>
>>> Please send your comments by May 18th 2014. If you do not feel this=20
>>> document should advance, please state your reasons why.
>>
>> I've read the document.  I don't have a particular opinion on whether=20
>> it
>should advance, mainly because I'm not a security expert.  I have some=20
>comments that may hopefully be useful, though:
>>
>> Some higher level points
>> - (maybe already discussed before but) the concept of using public=20
>> key  authentication in DHCP makes some sense to me, but I wonder why=20
>> we  are discussing this specifically for DHCPv6.  As far as I know =20
>> there's no such counterpart in DHCPv4 (the only related thing I can =20
>> google is draft-gupta-dhcp-auth-02.txt, which expired long ago), am =20
>> I correct?  If so, is that because *v4 is just too legacy and isn't =20
>> worth improvements anymore?  Or does that reflect some DHCP specific =20
>> points that make public key authentication not so viable?  If it's =20
>> the latter, doesn't it also apply to this proposal?
>>
>> - The description of the draft is a bit vague (which may have to be =20
>> clarified anyway), but if I understand it correctly, it assumes that =20
>> both clients (each of them) and servers maintain their pair of =20
>> public-private keys, and a client offers and uses its own key to =20
>> authenticate messages from the client to servers.  Is that correct?
>>  If so, does this make sense?  My general understanding is that =20
>> authenticating DHCP messages from clients to server is not that =20
>> critical, and it's quite unlikely that servers maintain public keys =20
>> of all possible clients so the servers would have to rely on the =20
>> leap-of-faith model.  They then may have to worry about the =20
>> "resource exhaustion attacks" (although I'm not sure if this is a =20
>> big issue, see below).
>>
>> Other non editorial comments on the draft:
>> - Section 5.1:
>>   Public Key     A variable-length field containing public key. The
>>                  key MUST be represented as a lower-case
>hexadecimal
>>                  string with the most significant octet of the key
>>                  first. Typically, the length of a 2048-bit RSA
>>
>>  Is there any specific reason it's represented as a string?  Not =20
>> necessarily bad, but I thought more common practice here is to =20
>> simply use the binary value of the key.  DHCP options in wire format =20
>> are not expected to be human readable anyway, so I don't see the =20
>> point for using a string here.
>>
>> - In Section 6.2:
>>
>>   On the recipient that supports the leap of faith model, the number of
>>   cached public keys or unverifiable certificates MUST be limited in
>>   order to protect against resource exhaustion attacks.  If the
>>
>>  This is mainly concerned about servers, correct?  If so, I'm not =20
>> sure how severe this "attacks" are; DHCP servers generally need to =20
>> maintain some state for each client (unless that's stateless only
>>  server) and would naturally already have some limitation on that =20
>> resource.  Shouldn't the general defense be enough for this =20
>> particular resource, too?  (But I was also not sure if it makes =20
>> sense to use (public key) authentication for messages from clients =20
>> in the first place; see higher-level discussions above)
>>
>> - Related, it seems some part of Section 6.2 is more specific for =20
>> clients and some other part is more specific to servers.  So it may =20
>> be helpful if we have separate subsections focusing on these =20
>> particular cases.  Just a suggestion.
>>
>> Editorial nits:
>> - Section 4.3
>>   they may fall back the unsecure model, if both client and server =20
>> s/fall back the/fall back to the/  (I found the missing 'to' of this=20
>> kind in several other places in  the draft)
>>
>> - Section 4.3
>>   whether to accept the messages.  If the client accept the unsecure
>>   messages from the DHCPv6 server.  The subsequent exchanges will be
>in
>>   unsecure model.
>>  s/server.  The/server, the/
>>
>> - Section 4.3
>>   on the server policy.  If the server mandidates the authentication, =20
>> s/mandidates/mandates/
>>
>> - Section 6.1
>>   messages, MUST contain either a the Public Key or Certificate=20
>> option,  s/a the/the/ (?)
>>
>> - Section 6.2
>>   error status code, defined in Section 5.4, back to the client..
>>  s/.././
>>
>> --
>> JINMEI, Tatuya
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Tue May  6 05:26:03 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA341A02E7 for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 05:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 EWtyzG5FM3vU for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 05:26:02 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id A650C1A02EA for <dhcwg@ietf.org>; Tue,  6 May 2014 05:26:00 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 208BC1B81BF for <dhcwg@ietf.org>; Tue,  6 May 2014 05:25:57 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id B427A19005C; Tue,  6 May 2014 05:25:56 -0700 (PDT)
Received: from [172.17.69.251] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 May 2014 05:25:56 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com>
Date: Tue, 6 May 2014 07:25:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <79996E6A-DF1D-41B9-878C-04F260E83DF6@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/JORPlrT3KTs8VbJTCpEAKTZVyVo
Cc: dhcwg <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 12:26:03 -0000

On May 6, 2014, at 2:36 AM, Sheng Jiang <jiangsheng@huawei.com> wrote:
> The "MUST" here seems not proper. Let us replace is with "MAY". It =
makes this point optional and should address your concern.

This is really implementation advice, so perhaps it doesn't need to be =
normative.


From nobody Tue May  6 06:14:15 2014
Return-Path: <iesg-secretary@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 3F0961A06A1; Tue,  6 May 2014 06:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IXtoUYHvJv-y; Tue,  6 May 2014 06:14:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0214D1A077D; Tue,  6 May 2014 06:14:09 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140506131409.12487.94606.idtracker@ietfa.amsl.com>
Date: Tue, 06 May 2014 06:14:09 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/fI6yXk1LB6j3SatpazgwwgdY2YI
Cc: dhc mailing list <dhcwg@ietf.org>, dhc chair <dhc-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [dhcwg] Protocol Action: 'Handling Unknown DHCPv6 Messages' to Proposed Standard (draft-ietf-dhc-dhcpv6-unknown-msg-08.txt)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 13:14:13 -0000

The IESG has approved the following document:
- 'Handling Unknown DHCPv6 Messages'
  (draft-ietf-dhc-dhcpv6-unknown-msg-08.txt) as Proposed Standard

This document is the product of the Dynamic Host Configuration Working
Group.

The IESG contact persons are Brian Haberman and Ted Lemon.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-unknown-msg/




Technical Summary:

  This document defines how a DHCPv6 server, client or relay agent should
  behave when receiving unknown DHCPv6 messages.

Working Group Summary:

  This document was called draft-csl-dhc-dhcpv6-unknown-msg-3315update prior to its
  adoption. There was unanimous support for it in favor of adoption and none 
  against), so this document was adopted in April 2013. There was quite interest in
  this work posts since its adoption. There was never any opposition for this work.

Document Quality:

Personnel:

Who is the Document Shepherd? Who is the Responsible Area Director?

  Sheng Jiang is the document shepherd. Brian Haberman is the responsible AD.


From nobody Tue May  6 07:15:57 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48F3E1A035D for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 07:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wQrGH9qEB_jP for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 07:15:49 -0700 (PDT)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id 811131A032F for <dhcwg@ietf.org>; Tue,  6 May 2014 07:15:49 -0700 (PDT)
Received: by mail-qg0-f48.google.com with SMTP id i50so7898868qgf.7 for <dhcwg@ietf.org>; Tue, 06 May 2014 07:15:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Tmw36TSqzflDJwtP+TGC8c+g50FbmWEKKhVebN3blic=; b=xAGCkHfilUdSAbq6bMT4cTVKjK0+sHbzQLCH5MVwv0J05xspiyDGrEKL0/o0w/ITMx ZlSj8JN5iJLCIobHh/xwpCz1kSm8BMvO07AgAVuV7Td8vWZptdQu0bgGZwQuIuSpq+kg 3ZbZ6Nxq5dvOsV4WT2VNDdIOP7lMqT2Bm5EDtBHajWRk0++DAeE8/cXY7Ek8DYlhIy80 6+8bPJsFd/B61U4l9mOOho+Nk2VMnJXLaO3GLiSt0q2sUagvzCHDB0STC2AXT0ywxvph WLtcVsikNPj+Ynx80Uo2z7IgMHnWSllHnyQcWlAmJ1BH+b0v1PP82YfFY4V+8uFMnBdp T2ew==
X-Received: by 10.229.28.2 with SMTP id k2mr54042853qcc.16.1399385745444; Tue, 06 May 2014 07:15:45 -0700 (PDT)
Received: from ?IPv6:2001:420:2c52:1316:c16a:9614:28c1:c450? ([2001:420:2c52:1316:c16a:9614:28c1:c450]) by mx.google.com with ESMTPSA id x5sm23728412qaj.9.2014.05.06.07.15.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 May 2014 07:15:42 -0700 (PDT)
Content-Type: text/plain; charset=iso-2022-jp
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com>
Date: Tue, 6 May 2014 10:15:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/lUw4c7eVYe9ntrTwkm55JayIKzw
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2014 14:15:56 -0000

Sheng, Dacheng - Sorry, I missed you earlier response.

There is no fundamental reason that fragmenting DHCPv6 traffic won't =
work, but, historically, DHCP fragmentation has been avoided and =
fragmentation is usually avoided in IPv6 traffic.

I think Bernie has the right set of issues.  There may be more.

- Ralph


On May 6, 2014, at 7:24 AM 5/6/14, Bernie Volz (volz) <volz@cisco.com> =
wrote:

> I suspect some of the issues here are:
> 1. Because socket interfaces are typically used, how large a buffer =
should clients, relays, and servers support? (Yes, it is possible to ask =
the socket layer about how large a received packet is, but that requires =
two socket calls and I suspect is rarely done.)=20
> 2. If packets do exceed the MTU of the interface, fragmentation is =
required. As this is link-local (at least for first hop), probably not a =
big issue but does require fragmentation support (again, probably not a =
big issue except if it was perhaps boot prom code - but why that would =
be using sedhcpv6 is unclear). Fragmentation for relay to server =
communication MIGHT be an issue if the traffic traverses firewalls?
> 3. As PMTU is harder with UDP traffic, it isn't clear how the =
fragmentation MTU can easily be found. This may require clients, relays, =
and servers to support PMTU and be prepared for failures. Remember that =
with IPv6, fragmentation is done by the end points - not the =
intermediate hops.
>=20
> These issues aren't new, but they are more likely when sedhcpv6 is =
being used because we expect some of these options could be rather large =
(i.e., carrying certificates) and thus more likely require =
fragmentation.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Sheng Jiang
> Sent: Tuesday, May 06, 2014 3:00 AM
> To: Ralph Droms; Bernie Volz (volz)
> Cc: dhcwg; =1B$B?@L@C#:H=1B(B
> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by =
May 18
>=20
>> I would like to see some consideration of the total length of DHCPv6=20=

>> messages that use this security protocol included in the document.
>=20
> Hi, Ralph,
>=20
> We could give consideration of the total length of DHCPv6 messages in =
the current draft. The message length are variable because there are few =
variable field in the message, such as public key/certificate & =
signature, etc. We expect the length of the message should not exceed =
the maximum length of UDP packet.
>=20
> However, we do NOT see reasons why this would be a problem. Could =
please you share your concerns with us? So that, we can better address =
the consideration.
>=20
> Regards,
>=20
> Sheng + Dacheng
>=20
>> - Ralph
>>=20
>>>=20
>>> If this work does advance, and there's sufficient interest, I could=20=

>>> well see
>> someone proposing the same for DHCPv4.
>>>=20
>>> - Bernie
>>>=20
>>> -----Original Message-----
>>> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of ????
>>> Sent: Wednesday, April 30, 2014 1:30 PM
>>> To: Tomek Mrugalski
>>> Cc: dhcwg
>>> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond =
by
>> May 18
>>>=20
>>> At Tue, 29 Apr 2014 20:21:33 +0200,
>>> Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:
>>>=20
>>>> Since we have upcoming holiday on May 1st (which happens to be a=20
>>>> reason for extended weekend in many parts of Europe) and the topic=20=

>>>> in question is not trivial, this WGLC is a bit longer than usual.
>>>>=20
>>>> Please send your comments by May 18th 2014. If you do not feel this=20=

>>>> document should advance, please state your reasons why.
>>>=20
>>> I've read the document.  I don't have a particular opinion on =
whether=20
>>> it
>> should advance, mainly because I'm not a security expert.  I have =
some=20
>> comments that may hopefully be useful, though:
>>>=20
>>> Some higher level points
>>> - (maybe already discussed before but) the concept of using public=20=

>>> key  authentication in DHCP makes some sense to me, but I wonder why=20=

>>> we  are discussing this specifically for DHCPv6.  As far as I know =20=

>>> there's no such counterpart in DHCPv4 (the only related thing I can =20=

>>> google is draft-gupta-dhcp-auth-02.txt, which expired long ago), am =20=

>>> I correct?  If so, is that because *v4 is just too legacy and isn't =20=

>>> worth improvements anymore?  Or does that reflect some DHCP specific =
=20
>>> points that make public key authentication not so viable?  If it's =20=

>>> the latter, doesn't it also apply to this proposal?
>>>=20
>>> - The description of the draft is a bit vague (which may have to be =20=

>>> clarified anyway), but if I understand it correctly, it assumes that =
=20
>>> both clients (each of them) and servers maintain their pair of =20
>>> public-private keys, and a client offers and uses its own key to =20
>>> authenticate messages from the client to servers.  Is that correct?
>>> If so, does this make sense?  My general understanding is that =20
>>> authenticating DHCP messages from clients to server is not that =20
>>> critical, and it's quite unlikely that servers maintain public keys =20=

>>> of all possible clients so the servers would have to rely on the =20
>>> leap-of-faith model.  They then may have to worry about the =20
>>> "resource exhaustion attacks" (although I'm not sure if this is a =20=

>>> big issue, see below).
>>>=20
>>> Other non editorial comments on the draft:
>>> - Section 5.1:
>>>  Public Key     A variable-length field containing public key. The
>>>                 key MUST be represented as a lower-case
>> hexadecimal
>>>                 string with the most significant octet of the key
>>>                 first. Typically, the length of a 2048-bit RSA
>>>=20
>>> Is there any specific reason it's represented as a string?  Not =20
>>> necessarily bad, but I thought more common practice here is to =20
>>> simply use the binary value of the key.  DHCP options in wire format =
=20
>>> are not expected to be human readable anyway, so I don't see the =20
>>> point for using a string here.
>>>=20
>>> - In Section 6.2:
>>>=20
>>>  On the recipient that supports the leap of faith model, the number =
of
>>>  cached public keys or unverifiable certificates MUST be limited in
>>>  order to protect against resource exhaustion attacks.  If the
>>>=20
>>> This is mainly concerned about servers, correct?  If so, I'm not =20
>>> sure how severe this "attacks" are; DHCP servers generally need to =20=

>>> maintain some state for each client (unless that's stateless only
>>> server) and would naturally already have some limitation on that =20
>>> resource.  Shouldn't the general defense be enough for this =20
>>> particular resource, too?  (But I was also not sure if it makes =20
>>> sense to use (public key) authentication for messages from clients =20=

>>> in the first place; see higher-level discussions above)
>>>=20
>>> - Related, it seems some part of Section 6.2 is more specific for =20=

>>> clients and some other part is more specific to servers.  So it may =20=

>>> be helpful if we have separate subsections focusing on these =20
>>> particular cases.  Just a suggestion.
>>>=20
>>> Editorial nits:
>>> - Section 4.3
>>>  they may fall back the unsecure model, if both client and server =20=

>>> s/fall back the/fall back to the/  (I found the missing 'to' of this=20=

>>> kind in several other places in  the draft)
>>>=20
>>> - Section 4.3
>>>  whether to accept the messages.  If the client accept the unsecure
>>>  messages from the DHCPv6 server.  The subsequent exchanges will be
>> in
>>>  unsecure model.
>>> s/server.  The/server, the/
>>>=20
>>> - Section 4.3
>>>  on the server policy.  If the server mandidates the authentication, =
=20
>>> s/mandidates/mandates/
>>>=20
>>> - Section 6.1
>>>  messages, MUST contain either a the Public Key or Certificate=20
>>> option,  s/a the/the/ (?)
>>>=20
>>> - Section 6.2
>>>  error status code, defined in Section 5.4, back to the client..
>>> s/.././
>>>=20
>>> --
>>> JINMEI, Tatuya
>>>=20
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>=20
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>=20
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Tue May  6 18:15:45 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 5F9531A01DF for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 18:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 VqlU9p2PwjtJ for <dhcwg@ietfa.amsl.com>; Tue,  6 May 2014 18:15:40 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id DFF781A0220 for <dhcwg@ietf.org>; Tue,  6 May 2014 18:15:39 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGL96704; Wed, 07 May 2014 01:15:35 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 May 2014 02:14:18 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 May 2014 02:15:34 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Wed, 7 May 2014 09:15:23 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ralph Droms <rdroms.ietf@gmail.com>, "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPY9fqOkQX2Up+wk+VaPjsYGUK15sp5cSAgALR/YCAAAxhgIAGX9Jg///JsACAAC/igIABNuCw
Date: Wed, 7 May 2014 01:15:23 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com>
In-Reply-To: <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/WxJptE-TA986hRrxL6zORQ5F028
Cc: dhcwg <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 01:15:43 -0000

SGksIEJlcm5pZSAmIFJhbHBoLA0KDQpXZSBkaWQgcmVhbGl6ZSB0aGUgaXNzdWVzIHlvdSBtZW50
aW9uZWQuIEhvd2V2ZXIsIHdlIHRob3VnaHQgdGhleSB3ZXJlIG5vdCByZWxldmFudC4gRm9yIHRo
cmVlIHJlYXNvbnMsIEEsIGFzIHByb3RvY29sIGRlc2lnbmluZywgdGhlcmUgaXMgbm8gbXVjaCB3
ZSBjYW4gZG8gdG8gc2hvcnRlbiB0aGUgREhDUCBtZXNzYWdlOyBCLCBtb3N0IG9mIGlzc3VlcyBh
cmUgcmVsZXZhbnQgd2l0aCBzcGVjaWZpYyB1bmRlci1sYXllciB0cmFuc21pdCBtZWNoYW5pc20s
IHdoaWNoIGlzIG5vdCBzcGVjaWZpYyBmb3IgREhDUHY2IHByb3RvY29sLiBJdCBzaG91bGQgYmUg
dGhlIGltcGxlbWVudGF0aW9uIG9mIHVuZGVyLWxheWVyIHRyYW5zbWl0IHRvIG1ha2UgaXQgd29y
ay4gQywgbW9zdCBvZiBpc3N1ZXMgZXhpc3QgaW4gc29tZSBzcGVjaWZpYyBkZXBsb3ltZW50IHNj
ZW5hcmlvcy4gVGhleSBtYXkgbm90IGJlIHRoZSBtYWpvcml0eS4gVGhleSBhcmUgZGVwbG95bWVu
dCBpc3N1ZXMsIHJhdGhlciB0aGFuIHByb3RvY29sIGRlc2lnbiBsZXZlbCBpc3N1ZXMuDQoNCkZv
ciB1cywgdGhlcmUgaXMgbm8gbXVjaCB3ZSBjb3VsZCBvciBzaG91bGQgZG8gaW4gdGhlIGRvY3Vt
ZW50LiBJdCBzZWVtcyByZWFzb25hYmxlIHRvIGdpdmUgc29tZSBkZXBsb3ltZW50IGNvbnNpZGVy
YXRpb24gaW4gdGhlIGRvY3VtZW50IGJ5IGp1c3Qgc2F5aW5nOiBTZURIQ1B2NiBtZXNzYWdlIGlz
IGNvbW1vbmx5IGxhcmdlLiBJUCBmcmFnbWVudHMgYXJlIGhpZ2hseSBwb3NzaWJsZS4gSGVuY2Us
IGRlcGxveW1lbnQgb2YgU2VESENQdjYgc2hvdWxkIGFsc28gY29uc2lkZXIgdGhlIGlzc3VlcyBv
ZiBJUCBmcmFnbWVudCwgUE1UVSwgZXRjLg0KDQpSZWdhcmRzLA0KDQpTaGVuZw0KDQo+LS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBSYWxwaCBEcm9tcyBbbWFpbHRvOnJkcm9tcy5p
ZXRmQGdtYWlsLmNvbV0NCj5TZW50OiBUdWVzZGF5LCBNYXkgMDYsIDIwMTQgMTA6MTYgUE0NCj5U
bzogU2hlbmcgSmlhbmc7IEJlcm5pZSBWb2x6ICh2b2x6KQ0KPkNjOiBkaGN3Zzsg56We5piO6YGU
5ZOJDQo+U3ViamVjdDogUmU6IFtkaGN3Z10gV0dMQyBmb3IgZHJhZnQtaWV0Zi1kaGMtc2VkaGNw
djYtMDIgLSBSZXNwb25kIGJ5IE1heQ0KPjE4DQo+DQo+U2hlbmcsIERhY2hlbmcgLSBTb3JyeSwg
SSBtaXNzZWQgeW91IGVhcmxpZXIgcmVzcG9uc2UuDQo+DQo+VGhlcmUgaXMgbm8gZnVuZGFtZW50
YWwgcmVhc29uIHRoYXQgZnJhZ21lbnRpbmcgREhDUHY2IHRyYWZmaWMgd29uJ3Qgd29yaywNCj5i
dXQsIGhpc3RvcmljYWxseSwgREhDUCBmcmFnbWVudGF0aW9uIGhhcyBiZWVuIGF2b2lkZWQgYW5k
IGZyYWdtZW50YXRpb24gaXMNCj51c3VhbGx5IGF2b2lkZWQgaW4gSVB2NiB0cmFmZmljLg0KPg0K
PkkgdGhpbmsgQmVybmllIGhhcyB0aGUgcmlnaHQgc2V0IG9mIGlzc3Vlcy4gIFRoZXJlIG1heSBi
ZSBtb3JlLg0KPg0KPi0gUmFscGgNCj4NCj4NCj5PbiBNYXkgNiwgMjAxNCwgYXQgNzoyNCBBTSA1
LzYvMTQsIEJlcm5pZSBWb2x6ICh2b2x6KSA8dm9sekBjaXNjby5jb20+DQo+d3JvdGU6DQo+DQo+
PiBJIHN1c3BlY3Qgc29tZSBvZiB0aGUgaXNzdWVzIGhlcmUgYXJlOg0KPj4gMS4gQmVjYXVzZSBz
b2NrZXQgaW50ZXJmYWNlcyBhcmUgdHlwaWNhbGx5IHVzZWQsIGhvdyBsYXJnZSBhIGJ1ZmZlciBz
aG91bGQNCj5jbGllbnRzLCByZWxheXMsIGFuZCBzZXJ2ZXJzIHN1cHBvcnQ/IChZZXMsIGl0IGlz
IHBvc3NpYmxlIHRvIGFzayB0aGUgc29ja2V0IGxheWVyDQo+YWJvdXQgaG93IGxhcmdlIGEgcmVj
ZWl2ZWQgcGFja2V0IGlzLCBidXQgdGhhdCByZXF1aXJlcyB0d28gc29ja2V0IGNhbGxzIGFuZCBJ
DQo+c3VzcGVjdCBpcyByYXJlbHkgZG9uZS4pDQo+PiAyLiBJZiBwYWNrZXRzIGRvIGV4Y2VlZCB0
aGUgTVRVIG9mIHRoZSBpbnRlcmZhY2UsIGZyYWdtZW50YXRpb24gaXMgcmVxdWlyZWQuDQo+QXMg
dGhpcyBpcyBsaW5rLWxvY2FsIChhdCBsZWFzdCBmb3IgZmlyc3QgaG9wKSwgcHJvYmFibHkgbm90
IGEgYmlnIGlzc3VlIGJ1dCBkb2VzDQo+cmVxdWlyZSBmcmFnbWVudGF0aW9uIHN1cHBvcnQgKGFn
YWluLCBwcm9iYWJseSBub3QgYSBiaWcgaXNzdWUgZXhjZXB0IGlmIGl0IHdhcw0KPnBlcmhhcHMg
Ym9vdCBwcm9tIGNvZGUgLSBidXQgd2h5IHRoYXQgd291bGQgYmUgdXNpbmcgc2VkaGNwdjYgaXMg
dW5jbGVhcikuDQo+RnJhZ21lbnRhdGlvbiBmb3IgcmVsYXkgdG8gc2VydmVyIGNvbW11bmljYXRp
b24gTUlHSFQgYmUgYW4gaXNzdWUgaWYgdGhlDQo+dHJhZmZpYyB0cmF2ZXJzZXMgZmlyZXdhbGxz
Pw0KPj4gMy4gQXMgUE1UVSBpcyBoYXJkZXIgd2l0aCBVRFAgdHJhZmZpYywgaXQgaXNuJ3QgY2xl
YXIgaG93IHRoZSBmcmFnbWVudGF0aW9uDQo+TVRVIGNhbiBlYXNpbHkgYmUgZm91bmQuIFRoaXMg
bWF5IHJlcXVpcmUgY2xpZW50cywgcmVsYXlzLCBhbmQgc2VydmVycyB0bw0KPnN1cHBvcnQgUE1U
VSBhbmQgYmUgcHJlcGFyZWQgZm9yIGZhaWx1cmVzLiBSZW1lbWJlciB0aGF0IHdpdGggSVB2NiwN
Cj5mcmFnbWVudGF0aW9uIGlzIGRvbmUgYnkgdGhlIGVuZCBwb2ludHMgLSBub3QgdGhlIGludGVy
bWVkaWF0ZSBob3BzLg0KPj4NCj4+IFRoZXNlIGlzc3VlcyBhcmVuJ3QgbmV3LCBidXQgdGhleSBh
cmUgbW9yZSBsaWtlbHkgd2hlbiBzZWRoY3B2NiBpcyBiZWluZw0KPnVzZWQgYmVjYXVzZSB3ZSBl
eHBlY3Qgc29tZSBvZiB0aGVzZSBvcHRpb25zIGNvdWxkIGJlIHJhdGhlciBsYXJnZSAoaS5lLiwN
Cj5jYXJyeWluZyBjZXJ0aWZpY2F0ZXMpIGFuZCB0aHVzIG1vcmUgbGlrZWx5IHJlcXVpcmUgZnJh
Z21lbnRhdGlvbi4NCj4+DQo+PiAtIEJlcm5pZQ0KPj4NCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+PiBGcm9tOiBkaGN3ZyBbbWFpbHRvOmRoY3dnLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBTaGVuZyBKaWFuZw0KPj4gU2VudDogVHVlc2RheSwgTWF5IDA2LCAyMDE0IDM6
MDAgQU0NCj4+IFRvOiBSYWxwaCBEcm9tczsgQmVybmllIFZvbHogKHZvbHopDQo+PiBDYzogZGhj
d2c7IOelnuaYjumBlOWTiQ0KPj4gU3ViamVjdDogUmU6IFtkaGN3Z10gV0dMQyBmb3IgZHJhZnQt
aWV0Zi1kaGMtc2VkaGNwdjYtMDIgLSBSZXNwb25kIGJ5DQo+TWF5IDE4DQo+Pg0KPj4+IEkgd291
bGQgbGlrZSB0byBzZWUgc29tZSBjb25zaWRlcmF0aW9uIG9mIHRoZSB0b3RhbCBsZW5ndGggb2Yg
REhDUHY2DQo+Pj4gbWVzc2FnZXMgdGhhdCB1c2UgdGhpcyBzZWN1cml0eSBwcm90b2NvbCBpbmNs
dWRlZCBpbiB0aGUgZG9jdW1lbnQuDQo+Pg0KPj4gSGksIFJhbHBoLA0KPj4NCj4+IFdlIGNvdWxk
IGdpdmUgY29uc2lkZXJhdGlvbiBvZiB0aGUgdG90YWwgbGVuZ3RoIG9mIERIQ1B2NiBtZXNzYWdl
cyBpbiB0aGUNCj5jdXJyZW50IGRyYWZ0LiBUaGUgbWVzc2FnZSBsZW5ndGggYXJlIHZhcmlhYmxl
IGJlY2F1c2UgdGhlcmUgYXJlIGZldyB2YXJpYWJsZQ0KPmZpZWxkIGluIHRoZSBtZXNzYWdlLCBz
dWNoIGFzIHB1YmxpYyBrZXkvY2VydGlmaWNhdGUgJiBzaWduYXR1cmUsIGV0Yy4gV2UNCj5leHBl
Y3QgdGhlIGxlbmd0aCBvZiB0aGUgbWVzc2FnZSBzaG91bGQgbm90IGV4Y2VlZCB0aGUgbWF4aW11
bSBsZW5ndGggb2YNCj5VRFAgcGFja2V0Lg0KPj4NCj4+IEhvd2V2ZXIsIHdlIGRvIE5PVCBzZWUg
cmVhc29ucyB3aHkgdGhpcyB3b3VsZCBiZSBhIHByb2JsZW0uIENvdWxkDQo+cGxlYXNlIHlvdSBz
aGFyZSB5b3VyIGNvbmNlcm5zIHdpdGggdXM/IFNvIHRoYXQsIHdlIGNhbiBiZXR0ZXIgYWRkcmVz
cyB0aGUNCj5jb25zaWRlcmF0aW9uLg0KPj4NCj4+IFJlZ2FyZHMsDQo+Pg0KPj4gU2hlbmcgKyBE
YWNoZW5nDQo+Pg0KPj4+IC0gUmFscGgNCj4+Pg0KPj4+Pg0KPj4+PiBJZiB0aGlzIHdvcmsgZG9l
cyBhZHZhbmNlLCBhbmQgdGhlcmUncyBzdWZmaWNpZW50IGludGVyZXN0LCBJIGNvdWxkDQo+Pj4+
IHdlbGwgc2VlDQo+Pj4gc29tZW9uZSBwcm9wb3NpbmcgdGhlIHNhbWUgZm9yIERIQ1B2NC4NCj4+
Pj4NCj4+Pj4gLSBCZXJuaWUNCj4+Pj4NCj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
Cj4+Pj4gRnJvbTogZGhjd2cgW21haWx0bzpkaGN3Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YgPz8/Pw0KPj4+PiBTZW50OiBXZWRuZXNkYXksIEFwcmlsIDMwLCAyMDE0IDE6MzAgUE0N
Cj4+Pj4gVG86IFRvbWVrIE1ydWdhbHNraQ0KPj4+PiBDYzogZGhjd2cNCj4+Pj4gU3ViamVjdDog
UmU6IFtkaGN3Z10gV0dMQyBmb3IgZHJhZnQtaWV0Zi1kaGMtc2VkaGNwdjYtMDIgLSBSZXNwb25k
IGJ5DQo+Pj4gTWF5IDE4DQo+Pj4+DQo+Pj4+IEF0IFR1ZSwgMjkgQXByIDIwMTQgMjA6MjE6MzMg
KzAyMDAsDQo+Pj4+IFRvbWVrIE1ydWdhbHNraSA8dG9tYXN6Lm1ydWdhbHNraUBnbWFpbC5jb20+
IHdyb3RlOg0KPj4+Pg0KPj4+Pj4gU2luY2Ugd2UgaGF2ZSB1cGNvbWluZyBob2xpZGF5IG9uIE1h
eSAxc3QgKHdoaWNoIGhhcHBlbnMgdG8gYmUgYQ0KPj4+Pj4gcmVhc29uIGZvciBleHRlbmRlZCB3
ZWVrZW5kIGluIG1hbnkgcGFydHMgb2YgRXVyb3BlKSBhbmQgdGhlIHRvcGljDQo+Pj4+PiBpbiBx
dWVzdGlvbiBpcyBub3QgdHJpdmlhbCwgdGhpcyBXR0xDIGlzIGEgYml0IGxvbmdlciB0aGFuIHVz
dWFsLg0KPj4+Pj4NCj4+Pj4+IFBsZWFzZSBzZW5kIHlvdXIgY29tbWVudHMgYnkgTWF5IDE4dGgg
MjAxNC4gSWYgeW91IGRvIG5vdCBmZWVsIHRoaXMNCj4+Pj4+IGRvY3VtZW50IHNob3VsZCBhZHZh
bmNlLCBwbGVhc2Ugc3RhdGUgeW91ciByZWFzb25zIHdoeS4NCj4+Pj4NCj4+Pj4gSSd2ZSByZWFk
IHRoZSBkb2N1bWVudC4gIEkgZG9uJ3QgaGF2ZSBhIHBhcnRpY3VsYXIgb3BpbmlvbiBvbiB3aGV0
aGVyDQo+Pj4+IGl0DQo+Pj4gc2hvdWxkIGFkdmFuY2UsIG1haW5seSBiZWNhdXNlIEknbSBub3Qg
YSBzZWN1cml0eSBleHBlcnQuICBJIGhhdmUgc29tZQ0KPj4+IGNvbW1lbnRzIHRoYXQgbWF5IGhv
cGVmdWxseSBiZSB1c2VmdWwsIHRob3VnaDoNCj4+Pj4NCj4+Pj4gU29tZSBoaWdoZXIgbGV2ZWwg
cG9pbnRzDQo+Pj4+IC0gKG1heWJlIGFscmVhZHkgZGlzY3Vzc2VkIGJlZm9yZSBidXQpIHRoZSBj
b25jZXB0IG9mIHVzaW5nIHB1YmxpYw0KPj4+PiBrZXkgIGF1dGhlbnRpY2F0aW9uIGluIERIQ1Ag
bWFrZXMgc29tZSBzZW5zZSB0byBtZSwgYnV0IEkgd29uZGVyIHdoeQ0KPj4+PiB3ZSAgYXJlIGRp
c2N1c3NpbmcgdGhpcyBzcGVjaWZpY2FsbHkgZm9yIERIQ1B2Ni4gIEFzIGZhciBhcyBJIGtub3cN
Cj4+Pj4gdGhlcmUncyBubyBzdWNoIGNvdW50ZXJwYXJ0IGluIERIQ1B2NCAodGhlIG9ubHkgcmVs
YXRlZCB0aGluZyBJIGNhbg0KPj4+PiBnb29nbGUgaXMgZHJhZnQtZ3VwdGEtZGhjcC1hdXRoLTAy
LnR4dCwgd2hpY2ggZXhwaXJlZCBsb25nIGFnbyksIGFtDQo+Pj4+IEkgY29ycmVjdD8gIElmIHNv
LCBpcyB0aGF0IGJlY2F1c2UgKnY0IGlzIGp1c3QgdG9vIGxlZ2FjeSBhbmQgaXNuJ3QNCj4+Pj4g
d29ydGggaW1wcm92ZW1lbnRzIGFueW1vcmU/ICBPciBkb2VzIHRoYXQgcmVmbGVjdCBzb21lIERI
Q1ANCj5zcGVjaWZpYw0KPj4+PiBwb2ludHMgdGhhdCBtYWtlIHB1YmxpYyBrZXkgYXV0aGVudGlj
YXRpb24gbm90IHNvIHZpYWJsZT8gIElmIGl0J3MNCj4+Pj4gdGhlIGxhdHRlciwgZG9lc24ndCBp
dCBhbHNvIGFwcGx5IHRvIHRoaXMgcHJvcG9zYWw/DQo+Pj4+DQo+Pj4+IC0gVGhlIGRlc2NyaXB0
aW9uIG9mIHRoZSBkcmFmdCBpcyBhIGJpdCB2YWd1ZSAod2hpY2ggbWF5IGhhdmUgdG8gYmUNCj4+
Pj4gY2xhcmlmaWVkIGFueXdheSksIGJ1dCBpZiBJIHVuZGVyc3RhbmQgaXQgY29ycmVjdGx5LCBp
dCBhc3N1bWVzIHRoYXQNCj4+Pj4gYm90aCBjbGllbnRzIChlYWNoIG9mIHRoZW0pIGFuZCBzZXJ2
ZXJzIG1haW50YWluIHRoZWlyIHBhaXIgb2YNCj4+Pj4gcHVibGljLXByaXZhdGUga2V5cywgYW5k
IGEgY2xpZW50IG9mZmVycyBhbmQgdXNlcyBpdHMgb3duIGtleSB0bw0KPj4+PiBhdXRoZW50aWNh
dGUgbWVzc2FnZXMgZnJvbSB0aGUgY2xpZW50IHRvIHNlcnZlcnMuICBJcyB0aGF0IGNvcnJlY3Q/
DQo+Pj4+IElmIHNvLCBkb2VzIHRoaXMgbWFrZSBzZW5zZT8gIE15IGdlbmVyYWwgdW5kZXJzdGFu
ZGluZyBpcyB0aGF0DQo+Pj4+IGF1dGhlbnRpY2F0aW5nIERIQ1AgbWVzc2FnZXMgZnJvbSBjbGll
bnRzIHRvIHNlcnZlciBpcyBub3QgdGhhdA0KPj4+PiBjcml0aWNhbCwgYW5kIGl0J3MgcXVpdGUg
dW5saWtlbHkgdGhhdCBzZXJ2ZXJzIG1haW50YWluIHB1YmxpYyBrZXlzDQo+Pj4+IG9mIGFsbCBw
b3NzaWJsZSBjbGllbnRzIHNvIHRoZSBzZXJ2ZXJzIHdvdWxkIGhhdmUgdG8gcmVseSBvbiB0aGUN
Cj4+Pj4gbGVhcC1vZi1mYWl0aCBtb2RlbC4gIFRoZXkgdGhlbiBtYXkgaGF2ZSB0byB3b3JyeSBh
Ym91dCB0aGUNCj4+Pj4gInJlc291cmNlIGV4aGF1c3Rpb24gYXR0YWNrcyIgKGFsdGhvdWdoIEkn
bSBub3Qgc3VyZSBpZiB0aGlzIGlzIGENCj4+Pj4gYmlnIGlzc3VlLCBzZWUgYmVsb3cpLg0KPj4+
Pg0KPj4+PiBPdGhlciBub24gZWRpdG9yaWFsIGNvbW1lbnRzIG9uIHRoZSBkcmFmdDoNCj4+Pj4g
LSBTZWN0aW9uIDUuMToNCj4+Pj4gIFB1YmxpYyBLZXkgICAgIEEgdmFyaWFibGUtbGVuZ3RoIGZp
ZWxkIGNvbnRhaW5pbmcgcHVibGljIGtleS4gVGhlDQo+Pj4+ICAgICAgICAgICAgICAgICBrZXkg
TVVTVCBiZSByZXByZXNlbnRlZCBhcyBhIGxvd2VyLWNhc2UNCj4+PiBoZXhhZGVjaW1hbA0KPj4+
PiAgICAgICAgICAgICAgICAgc3RyaW5nIHdpdGggdGhlIG1vc3Qgc2lnbmlmaWNhbnQgb2N0ZXQg
b2YgdGhlIGtleQ0KPj4+PiAgICAgICAgICAgICAgICAgZmlyc3QuIFR5cGljYWxseSwgdGhlIGxl
bmd0aCBvZiBhIDIwNDgtYml0IFJTQQ0KPj4+Pg0KPj4+PiBJcyB0aGVyZSBhbnkgc3BlY2lmaWMg
cmVhc29uIGl0J3MgcmVwcmVzZW50ZWQgYXMgYSBzdHJpbmc/ICBOb3QNCj4+Pj4gbmVjZXNzYXJp
bHkgYmFkLCBidXQgSSB0aG91Z2h0IG1vcmUgY29tbW9uIHByYWN0aWNlIGhlcmUgaXMgdG8NCj4+
Pj4gc2ltcGx5IHVzZSB0aGUgYmluYXJ5IHZhbHVlIG9mIHRoZSBrZXkuICBESENQIG9wdGlvbnMg
aW4gd2lyZSBmb3JtYXQNCj4+Pj4gYXJlIG5vdCBleHBlY3RlZCB0byBiZSBodW1hbiByZWFkYWJs
ZSBhbnl3YXksIHNvIEkgZG9uJ3Qgc2VlIHRoZQ0KPj4+PiBwb2ludCBmb3IgdXNpbmcgYSBzdHJp
bmcgaGVyZS4NCj4+Pj4NCj4+Pj4gLSBJbiBTZWN0aW9uIDYuMjoNCj4+Pj4NCj4+Pj4gIE9uIHRo
ZSByZWNpcGllbnQgdGhhdCBzdXBwb3J0cyB0aGUgbGVhcCBvZiBmYWl0aCBtb2RlbCwgdGhlIG51
bWJlciBvZg0KPj4+PiAgY2FjaGVkIHB1YmxpYyBrZXlzIG9yIHVudmVyaWZpYWJsZSBjZXJ0aWZp
Y2F0ZXMgTVVTVCBiZSBsaW1pdGVkIGluDQo+Pj4+ICBvcmRlciB0byBwcm90ZWN0IGFnYWluc3Qg
cmVzb3VyY2UgZXhoYXVzdGlvbiBhdHRhY2tzLiAgSWYgdGhlDQo+Pj4+DQo+Pj4+IFRoaXMgaXMg
bWFpbmx5IGNvbmNlcm5lZCBhYm91dCBzZXJ2ZXJzLCBjb3JyZWN0PyAgSWYgc28sIEknbSBub3QN
Cj4+Pj4gc3VyZSBob3cgc2V2ZXJlIHRoaXMgImF0dGFja3MiIGFyZTsgREhDUCBzZXJ2ZXJzIGdl
bmVyYWxseSBuZWVkIHRvDQo+Pj4+IG1haW50YWluIHNvbWUgc3RhdGUgZm9yIGVhY2ggY2xpZW50
ICh1bmxlc3MgdGhhdCdzIHN0YXRlbGVzcyBvbmx5DQo+Pj4+IHNlcnZlcikgYW5kIHdvdWxkIG5h
dHVyYWxseSBhbHJlYWR5IGhhdmUgc29tZSBsaW1pdGF0aW9uIG9uIHRoYXQNCj4+Pj4gcmVzb3Vy
Y2UuICBTaG91bGRuJ3QgdGhlIGdlbmVyYWwgZGVmZW5zZSBiZSBlbm91Z2ggZm9yIHRoaXMNCj4+
Pj4gcGFydGljdWxhciByZXNvdXJjZSwgdG9vPyAgKEJ1dCBJIHdhcyBhbHNvIG5vdCBzdXJlIGlm
IGl0IG1ha2VzDQo+Pj4+IHNlbnNlIHRvIHVzZSAocHVibGljIGtleSkgYXV0aGVudGljYXRpb24g
Zm9yIG1lc3NhZ2VzIGZyb20gY2xpZW50cw0KPj4+PiBpbiB0aGUgZmlyc3QgcGxhY2U7IHNlZSBo
aWdoZXItbGV2ZWwgZGlzY3Vzc2lvbnMgYWJvdmUpDQo+Pj4+DQo+Pj4+IC0gUmVsYXRlZCwgaXQg
c2VlbXMgc29tZSBwYXJ0IG9mIFNlY3Rpb24gNi4yIGlzIG1vcmUgc3BlY2lmaWMgZm9yDQo+Pj4+
IGNsaWVudHMgYW5kIHNvbWUgb3RoZXIgcGFydCBpcyBtb3JlIHNwZWNpZmljIHRvIHNlcnZlcnMu
ICBTbyBpdCBtYXkNCj4+Pj4gYmUgaGVscGZ1bCBpZiB3ZSBoYXZlIHNlcGFyYXRlIHN1YnNlY3Rp
b25zIGZvY3VzaW5nIG9uIHRoZXNlDQo+Pj4+IHBhcnRpY3VsYXIgY2FzZXMuICBKdXN0IGEgc3Vn
Z2VzdGlvbi4NCj4+Pj4NCj4+Pj4gRWRpdG9yaWFsIG5pdHM6DQo+Pj4+IC0gU2VjdGlvbiA0LjMN
Cj4+Pj4gIHRoZXkgbWF5IGZhbGwgYmFjayB0aGUgdW5zZWN1cmUgbW9kZWwsIGlmIGJvdGggY2xp
ZW50IGFuZCBzZXJ2ZXINCj4+Pj4gcy9mYWxsIGJhY2sgdGhlL2ZhbGwgYmFjayB0byB0aGUvICAo
SSBmb3VuZCB0aGUgbWlzc2luZyAndG8nIG9mIHRoaXMNCj4+Pj4ga2luZCBpbiBzZXZlcmFsIG90
aGVyIHBsYWNlcyBpbiAgdGhlIGRyYWZ0KQ0KPj4+Pg0KPj4+PiAtIFNlY3Rpb24gNC4zDQo+Pj4+
ICB3aGV0aGVyIHRvIGFjY2VwdCB0aGUgbWVzc2FnZXMuICBJZiB0aGUgY2xpZW50IGFjY2VwdCB0
aGUgdW5zZWN1cmUNCj4+Pj4gIG1lc3NhZ2VzIGZyb20gdGhlIERIQ1B2NiBzZXJ2ZXIuICBUaGUg
c3Vic2VxdWVudCBleGNoYW5nZXMgd2lsbCBiZQ0KPj4+IGluDQo+Pj4+ICB1bnNlY3VyZSBtb2Rl
bC4NCj4+Pj4gcy9zZXJ2ZXIuICBUaGUvc2VydmVyLCB0aGUvDQo+Pj4+DQo+Pj4+IC0gU2VjdGlv
biA0LjMNCj4+Pj4gIG9uIHRoZSBzZXJ2ZXIgcG9saWN5LiAgSWYgdGhlIHNlcnZlciBtYW5kaWRh
dGVzIHRoZSBhdXRoZW50aWNhdGlvbiwNCj4+Pj4gcy9tYW5kaWRhdGVzL21hbmRhdGVzLw0KPj4+
Pg0KPj4+PiAtIFNlY3Rpb24gNi4xDQo+Pj4+ICBtZXNzYWdlcywgTVVTVCBjb250YWluIGVpdGhl
ciBhIHRoZSBQdWJsaWMgS2V5IG9yIENlcnRpZmljYXRlDQo+Pj4+IG9wdGlvbiwgIHMvYSB0aGUv
dGhlLyAoPykNCj4+Pj4NCj4+Pj4gLSBTZWN0aW9uIDYuMg0KPj4+PiAgZXJyb3Igc3RhdHVzIGNv
ZGUsIGRlZmluZWQgaW4gU2VjdGlvbiA1LjQsIGJhY2sgdG8gdGhlIGNsaWVudC4uDQo+Pj4+IHMv
Li4vLi8NCj4+Pj4NCj4+Pj4gLS0NCj4+Pj4gSklOTUVJLCBUYXR1eWENCj4+Pj4NCj4+Pj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4gZGhjd2cg
bWFpbGluZyBsaXN0DQo+Pj4+IGRoY3dnQGlldGYub3JnDQo+Pj4+IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vZGhjd2cNCj4+Pj4NCj4+Pj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4gZGhjd2cgbWFpbGluZyBsaXN0DQo+
Pj4+IGRoY3dnQGlldGYub3JnDQo+Pj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vZGhjd2cNCj4+Pg0KPj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+Pj4gZGhjd2cgbWFpbGluZyBsaXN0DQo+Pj4gZGhjd2dAaWV0Zi5vcmcN
Cj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RoY3dnDQo+PiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gZGhjd2cgbWFp
bGluZyBsaXN0DQo+PiBkaGN3Z0BpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9kaGN3Zw0KDQo=


From nobody Wed May  7 04:23:30 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EACE11A06ED for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 04:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LYUi2HAVUT7Z for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 04:23:26 -0700 (PDT)
Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 13BE91A06D0 for <dhcwg@ietf.org>; Wed,  7 May 2014 04:23:25 -0700 (PDT)
Received: by mail-qa0-f52.google.com with SMTP id cm18so839309qab.39 for <dhcwg@ietf.org>; Wed, 07 May 2014 04:23:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DIMGeMJtsXplad9MDTF7nweO9WS89R0+dW3/GSYeGGg=; b=Ii//9JPzgMGHBru+VJwqMqkOfK3i4cxQVOztSZcPKg8NaHobJDak1s7ZBMJomzG/RS hbi8SakOdBDFEnbrhsgaMAoMXXU/P0bDb6YuyjTY1+8YdBVzTlMHd8Yg8URr3XRUt8q+ zq+PjuYrB5yZV3NLy2czr21eEJNWeS/ydfUA8Y2nAv5Yqu6kioo7/n9nFXbI5ePibdwK Qoz/3zU2rcpMtq9hPr/B95VDEYfZ9wajARlf1J1Jq2yl0OoTdgmzSJ1PDKZ6Xl1NJi5i KXjpD/V+wYVU69DcZVlotkiGgjOw11CSJ8upZK0GDip8WdbSvPA0jlrdd1dYfOJ3F219 nmHg==
X-Received: by 10.224.8.131 with SMTP id h3mr64638847qah.61.1399461801727; Wed, 07 May 2014 04:23:21 -0700 (PDT)
Received: from [10.116.164.54] (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPSA id w8sm28785480qag.30.2014.05.07.04.23.19 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 May 2014 04:23:20 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: iPad Mail (11D201)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com>
Date: Wed, 7 May 2014 07:23:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Rou-PJlj4-C0cmKype2UJSRghwQ
Cc: dhcwg <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 11:23:29 -0000

Zheng, Dacheng - I don't think any changes to the protocol are required.

However, this extension to DHCPv6 may result in DHCPv6 messages that are muc=
h larger than current messages (and are much larger than the original design=
ers of DHCP generally anticipated).  It may require the use of IPv6 fragment=
ation, which is not widely used and which introduces some potential problems=
 with UDP transport.  Therefore, I think it would be prudent to add some exp=
licit analysis and notice to implementors and deployers of this extension ab=
out the issues around large DHCPv6 messages.

- Ralph


> On May 6, 2014, at 9:15 PM, Sheng Jiang <jiangsheng@huawei.com> wrote:
>=20
> Hi, Bernie & Ralph,
>=20
> We did realize the issues you mentioned. However, we thought they were not=
 relevant. For three reasons, A, as protocol designing, there is no much we c=
an do to shorten the DHCP message; B, most of issues are relevant with speci=
fic under-layer transmit mechanism, which is not specific for DHCPv6 protoco=
l. It should be the implementation of under-layer transmit to make it work. C=
, most of issues exist in some specific deployment scenarios. They may not b=
e the majority. They are deployment issues, rather than protocol design leve=
l issues.
>=20
> For us, there is no much we could or should do in the document. It seems r=
easonable to give some deployment consideration in the document by just sayi=
ng: SeDHCPv6 message is commonly large. IP fragments are highly possible. He=
nce, deployment of SeDHCPv6 should also consider the issues of IP fragment, P=
MTU, etc.
>=20
> Regards,
>=20
> Sheng
>=20
>> -----Original Message-----
>> From: Ralph Droms [mailto:rdroms.ietf@gmail.com]
>> Sent: Tuesday, May 06, 2014 10:16 PM
>> To: Sheng Jiang; Bernie Volz (volz)
>> Cc: dhcwg; =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89
>> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May=

>> 18
>>=20
>> Sheng, Dacheng - Sorry, I missed you earlier response.
>>=20
>> There is no fundamental reason that fragmenting DHCPv6 traffic won't work=
,
>> but, historically, DHCP fragmentation has been avoided and fragmentation i=
s
>> usually avoided in IPv6 traffic.
>>=20
>> I think Bernie has the right set of issues.  There may be more.
>>=20
>> - Ralph
>>=20
>>=20
>> On May 6, 2014, at 7:24 AM 5/6/14, Bernie Volz (volz) <volz@cisco.com>
>> wrote:
>>=20
>>> I suspect some of the issues here are:
>>> 1. Because socket interfaces are typically used, how large a buffer shou=
ld
>> clients, relays, and servers support? (Yes, it is possible to ask the soc=
ket layer
>> about how large a received packet is, but that requires two socket calls a=
nd I
>> suspect is rarely done.)
>>> 2. If packets do exceed the MTU of the interface, fragmentation is requi=
red.
>> As this is link-local (at least for first hop), probably not a big issue b=
ut does
>> require fragmentation support (again, probably not a big issue except if i=
t was
>> perhaps boot prom code - but why that would be using sedhcpv6 is unclear)=
.
>> Fragmentation for relay to server communication MIGHT be an issue if the
>> traffic traverses firewalls?
>>> 3. As PMTU is harder with UDP traffic, it isn't clear how the fragmentat=
ion
>> MTU can easily be found. This may require clients, relays, and servers to=

>> support PMTU and be prepared for failures. Remember that with IPv6,
>> fragmentation is done by the end points - not the intermediate hops.
>>>=20
>>> These issues aren't new, but they are more likely when sedhcpv6 is being=

>> used because we expect some of these options could be rather large (i.e.,=

>> carrying certificates) and thus more likely require fragmentation.
>>>=20
>>> - Bernie
>>>=20
>>> -----Original Message-----
>>> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Sheng Jiang
>>> Sent: Tuesday, May 06, 2014 3:00 AM
>>> To: Ralph Droms; Bernie Volz (volz)
>>> Cc: dhcwg; =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89
>>> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by
>> May 18
>>>=20
>>>> I would like to see some consideration of the total length of DHCPv6
>>>> messages that use this security protocol included in the document.
>>>=20
>>> Hi, Ralph,
>>>=20
>>> We could give consideration of the total length of DHCPv6 messages in th=
e
>> current draft. The message length are variable because there are few vari=
able
>> field in the message, such as public key/certificate & signature, etc. We=

>> expect the length of the message should not exceed the maximum length of
>> UDP packet.
>>>=20
>>> However, we do NOT see reasons why this would be a problem. Could
>> please you share your concerns with us? So that, we can better address th=
e
>> consideration.
>>>=20
>>> Regards,
>>>=20
>>> Sheng + Dacheng
>>>=20
>>>> - Ralph
>>>>=20
>>>>>=20
>>>>> If this work does advance, and there's sufficient interest, I could
>>>>> well see
>>>> someone proposing the same for DHCPv4.
>>>>>=20
>>>>> - Bernie
>>>>>=20
>>>>> -----Original Message-----
>>>>> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of ????
>>>>> Sent: Wednesday, April 30, 2014 1:30 PM
>>>>> To: Tomek Mrugalski
>>>>> Cc: dhcwg
>>>>> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by
>>>> May 18
>>>>>=20
>>>>> At Tue, 29 Apr 2014 20:21:33 +0200,
>>>>> Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:
>>>>>=20
>>>>>> Since we have upcoming holiday on May 1st (which happens to be a
>>>>>> reason for extended weekend in many parts of Europe) and the topic
>>>>>> in question is not trivial, this WGLC is a bit longer than usual.
>>>>>>=20
>>>>>> Please send your comments by May 18th 2014. If you do not feel this
>>>>>> document should advance, please state your reasons why.
>>>>>=20
>>>>> I've read the document.  I don't have a particular opinion on whether
>>>>> it
>>>> should advance, mainly because I'm not a security expert.  I have some
>>>> comments that may hopefully be useful, though:
>>>>>=20
>>>>> Some higher level points
>>>>> - (maybe already discussed before but) the concept of using public
>>>>> key  authentication in DHCP makes some sense to me, but I wonder why
>>>>> we  are discussing this specifically for DHCPv6.  As far as I know
>>>>> there's no such counterpart in DHCPv4 (the only related thing I can
>>>>> google is draft-gupta-dhcp-auth-02.txt, which expired long ago), am
>>>>> I correct?  If so, is that because *v4 is just too legacy and isn't
>>>>> worth improvements anymore?  Or does that reflect some DHCP
>> specific
>>>>> points that make public key authentication not so viable?  If it's
>>>>> the latter, doesn't it also apply to this proposal?
>>>>>=20
>>>>> - The description of the draft is a bit vague (which may have to be
>>>>> clarified anyway), but if I understand it correctly, it assumes that
>>>>> both clients (each of them) and servers maintain their pair of
>>>>> public-private keys, and a client offers and uses its own key to
>>>>> authenticate messages from the client to servers.  Is that correct?
>>>>> If so, does this make sense?  My general understanding is that
>>>>> authenticating DHCP messages from clients to server is not that
>>>>> critical, and it's quite unlikely that servers maintain public keys
>>>>> of all possible clients so the servers would have to rely on the
>>>>> leap-of-faith model.  They then may have to worry about the
>>>>> "resource exhaustion attacks" (although I'm not sure if this is a
>>>>> big issue, see below).
>>>>>=20
>>>>> Other non editorial comments on the draft:
>>>>> - Section 5.1:
>>>>> Public Key     A variable-length field containing public key. The
>>>>>                key MUST be represented as a lower-case
>>>> hexadecimal
>>>>>                string with the most significant octet of the key
>>>>>                first. Typically, the length of a 2048-bit RSA
>>>>>=20
>>>>> Is there any specific reason it's represented as a string?  Not
>>>>> necessarily bad, but I thought more common practice here is to
>>>>> simply use the binary value of the key.  DHCP options in wire format
>>>>> are not expected to be human readable anyway, so I don't see the
>>>>> point for using a string here.
>>>>>=20
>>>>> - In Section 6.2:
>>>>>=20
>>>>> On the recipient that supports the leap of faith model, the number of
>>>>> cached public keys or unverifiable certificates MUST be limited in
>>>>> order to protect against resource exhaustion attacks.  If the
>>>>>=20
>>>>> This is mainly concerned about servers, correct?  If so, I'm not
>>>>> sure how severe this "attacks" are; DHCP servers generally need to
>>>>> maintain some state for each client (unless that's stateless only
>>>>> server) and would naturally already have some limitation on that
>>>>> resource.  Shouldn't the general defense be enough for this
>>>>> particular resource, too?  (But I was also not sure if it makes
>>>>> sense to use (public key) authentication for messages from clients
>>>>> in the first place; see higher-level discussions above)
>>>>>=20
>>>>> - Related, it seems some part of Section 6.2 is more specific for
>>>>> clients and some other part is more specific to servers.  So it may
>>>>> be helpful if we have separate subsections focusing on these
>>>>> particular cases.  Just a suggestion.
>>>>>=20
>>>>> Editorial nits:
>>>>> - Section 4.3
>>>>> they may fall back the unsecure model, if both client and server
>>>>> s/fall back the/fall back to the/  (I found the missing 'to' of this
>>>>> kind in several other places in  the draft)
>>>>>=20
>>>>> - Section 4.3
>>>>> whether to accept the messages.  If the client accept the unsecure
>>>>> messages from the DHCPv6 server.  The subsequent exchanges will be
>>>> in
>>>>> unsecure model.
>>>>> s/server.  The/server, the/
>>>>>=20
>>>>> - Section 4.3
>>>>> on the server policy.  If the server mandidates the authentication,
>>>>> s/mandidates/mandates/
>>>>>=20
>>>>> - Section 6.1
>>>>> messages, MUST contain either a the Public Key or Certificate
>>>>> option,  s/a the/the/ (?)
>>>>>=20
>>>>> - Section 6.2
>>>>> error status code, defined in Section 5.4, back to the client..
>>>>> s/.././
>>>>>=20
>>>>> --
>>>>> JINMEI, Tatuya
>>>>>=20
>>>>> _______________________________________________
>>>>> dhcwg mailing list
>>>>> dhcwg@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>=20
>>>>> _______________________________________________
>>>>> dhcwg mailing list
>>>>> dhcwg@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>=20
>>>> _______________________________________________
>>>> dhcwg mailing list
>>>> dhcwg@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>=20


From nobody Wed May  7 08:35:21 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 39D311A035C for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 08:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDkTiVZjKsd9 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 08:35:19 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id EE2F31A02EA for <dhcwg@ietf.org>; Wed,  7 May 2014 08:35:18 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id b13so1190165wgh.7 for <dhcwg@ietf.org>; Wed, 07 May 2014 08:35:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=yiP1OGQYbKAhxohJyK5SHTTvlWQlQiM/ZKOAnwImD90=; b=LW0Rk6nbJM++6/lNzmwKeL/8KFjWO7JnGyRHm0Lt5ILwisqa245Dj7JapIfKjXEsxA ALdZLNxFZSzt+zvJ5X5uy5sw8ef6rCRzwLvdOaIfL3tbYyD2rZoBq5h67eC/RA5dMZzd 2PF8s1jdkIP2rIS+1YBwSYQQToxZz/P3pxWK9dW5H+eohDrSsM4ezuC5fgxb7amG4dCS 8+TJUz550Yu4fv+sQQYMa3I8XvtiiW2cTKnN+4Tc8xtSE/xPt8wWN3LY/c4De/vVeN2I nmCsZUHJ3dGXfX7H4G+4airCFcRDPxX7ZNERyMAVVvk0csXNSTvY4lNcmP1S4YggV+Ia Yf+w==
MIME-Version: 1.0
X-Received: by 10.180.11.178 with SMTP id r18mr8463454wib.41.1399476914261; Wed, 07 May 2014 08:35:14 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.3.14 with HTTP; Wed, 7 May 2014 08:35:14 -0700 (PDT)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com>
Date: Wed, 7 May 2014 08:35:14 -0700
X-Google-Sender-Auth: odamYrwQCezgRHODcx1iFgomg3c
Message-ID: <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/V3-yswMSBBdJal-fgSZB2alDBlA
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 15:35:20 -0000

At Tue, 6 May 2014 07:36:34 +0000,
Sheng Jiang <jiangsheng@huawei.com> wrote:

> >- In Section 6.2:
> >
> >   On the recipient that supports the leap of faith model, the number of
> >   cached public keys or unverifiable certificates MUST be limited in
> >   order to protect against resource exhaustion attacks.  If the
> >
> >  This is mainly concerned about servers, correct?  If so, I'm not
> >  sure how severe this "attacks" are; DHCP servers generally need to
> >  maintain some state for each client (unless that's stateless only
> >  server) and would naturally already have some limitation on that
> >  resource.  Shouldn't the general defense be enough for this
> >  particular resource, too?
>
> The "MUST" here seems not proper. Let us replace is with "MAY". It makes this point optional and should address your concern.

I don't think my main point is MUST vs MAY.  It's about a more
general point of authenticating messages from clients to servers:

- whether we really need (public key) authentication in that
  direction, and if we do, why

- also if we do, what's the commonly expected model of "trust anchor":
  leap of faith or use of CA or something else, and if it's more
  likely to be a weaker model like leap of faith (I suspect so, for
  the direction of clients to servers), whether the motivation (1st
  bullet) is worth the weaker security

- and, if it's more likely to rely on leap of faith, what kind of
  consideration is needed

The discussion on caching the public keys is just a part of the third
bullet.  What I'm missing in the current draft is more comprehensive
and higher level discussions on all of these points.  It's far from
obvious to me compared to authenticating messages from servers to
clients.

--
JINMEI, Tatuya


From nobody Wed May  7 08:57:33 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 E0EF41A0367 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 08:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JfCUHQvqELa3 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 08:57:32 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id B29C61A035C for <dhcwg@ietf.org>; Wed,  7 May 2014 08:57:31 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id z12so1231131wgg.24 for <dhcwg@ietf.org>; Wed, 07 May 2014 08:57:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=QxYk2MKGGL+EWy/8is5vDYGHiw0r5fRCbyXWCB5lTOc=; b=NKyTPsXzrIu/5/2ZqVeSPBJC3MqplIP7v3n+1i2Ga1G0SCeUovDQPQ68plAQ3m3rhU N7c5T1/4EhQxmkpD8QDr4bNj/0C2sIC1QSiP1GyuXVgh6tnSKhkgfLCkB0rvwBLao9dw hDWgwnjbHqB2i9NM5QzWrdb7P8U+VxaTI9l5wt5WTDo7SFf/7KCWzc6EFohGbccWF0BY Is+jQp5OArF5UTJLyWcz0rsnplCy9YOwFMzeqP/T3OSeTo4Heg22tELKuXoiNDNH70Xz McwWSNT/3idR5lN/CpTU9dSY4/16BZP8El9IXLz2+DYpr6CJvJb6ayapjKZcmaps/EZG VDww==
MIME-Version: 1.0
X-Received: by 10.180.75.45 with SMTP id z13mr27300674wiv.41.1399478246911; Wed, 07 May 2014 08:57:26 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.3.14 with HTTP; Wed, 7 May 2014 08:57:26 -0700 (PDT)
In-Reply-To: <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com>
Date: Wed, 7 May 2014 08:57:26 -0700
X-Google-Sender-Auth: HLABasbyniXwy13UMx-r2RUte6w
Message-ID: <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Fk9NhtVn4eDtwg3W8vhCS4XEY4Y
Cc: dhcwg <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 15:57:33 -0000

At Wed, 7 May 2014 07:23:20 -0400,
Ralph Droms <rdroms.ietf@gmail.com> wrote:

> However, this extension to DHCPv6 may result in DHCPv6 messages that are =
much larger than current messages (and are much larger than the original de=
signers of DHCP generally anticipated).  It may require the use of IPv6 fra=
gmentation, which is not widely used and which introduces some potential pr=
oblems with UDP transport.  Therefore, I think it would be prudent to add s=
ome explicit analysis and notice to implementors and deployers of this exte=
nsion about the issues around large DHCPv6 messages.

I agree.

One specific point: newer DHCPv6 implementations that support this
protocol would have to use the IPV6_USE_MIN_MTU socket option (or
something equivalent to it), for exact the same kind of reason why all
modern DNS server implementations use it on UDP sockets.  I've quickly
checked a few open source implementations, and found none of them use
this option right now.  I'm not sure whether this draft should be as
specific as to mention that particular socket option, but at least
some higher level notes to implementors would be very helpful to avoid
surprise beforehand.

--
JINMEI, Tatuya


From nobody Wed May  7 09:06:03 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 001271A0791 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 09:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.852
X-Spam-Level: 
X-Spam-Status: No, score=-14.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCrFolU5WDvJ for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 09:06:00 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 3EB141A0392 for <dhcwg@ietf.org>; Wed,  7 May 2014 09:06:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2932; q=dns/txt; s=iport; t=1399478756; x=1400688356; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=aYFAbIiuKsedDIDEO/hZcUsm5F/+lEJ1Wy5JzGrh9z0=; b=OchBRcp1nHt3wyGphvVd/59uOdDprfKr8NLXmsovjef/rDpNnIRsaL+N vas+RmOA5m0wAmZMorxAlTomy/TdqMt/bpXRUNvv6lzL03066tciP8pfm 8EhIHy82z/FSFFcZcxjHk6GiA5XmI1/xSuMI/q4G5y6X3eUV8xIUzAVX7 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAMtYalOtJA2F/2dsb2JhbABagwaBJ4JnwjMBGYEAFnSCJQEBAQMBIxFFBQcEAgEIEQQBAQMCBh0DAgICHxEUAQgIAgQBDQUIiCUDCQiqO55vDYZIF4Eqihl4gWYWGwcGgm42gRUBA5dFjwyFYYM0gi8
X-IronPort-AV: E=Sophos;i="4.97,1004,1389744000"; d="scan'208";a="323092466"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-6.cisco.com with ESMTP; 07 May 2014 16:05:55 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s47G5tKr014366 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 May 2014 16:05:55 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Wed, 7 May 2014 11:05:55 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPag0KHMzNFfxEIk6wcBa/GM4ndJs1Rs+w
Date: Wed, 7 May 2014 16:05:55 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B00ECF9@xmb-rcd-x04.cisco.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com>
In-Reply-To: <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.121]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Vtw0_Rz1sQWoDpxPrQBXQX7uGw0
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 16:06:02 -0000

SSBhZ3JlZSB3aXRoIEppbm1laSBhbmQgUmFscGggdGhhdCB0aGlzIHBhY2tldCBzaXplIHNob3Vs
ZCBiZSBtZW50aW9uZWQgaW4gdGhlIGRvY3VtZW50Lg0KDQpJIHRoaW5rIGV4cGxpY2l0bHkgbWVu
dGlvbmluZyBJUFY2X1VTRV9NSU5fTVRVIHNvY2tldCBvcHRpb24gYXMgYW4gRVhBTVBMRSAoaS5l
LiwgZS5nLikgd291bGQgYmUgYSBnb29kIGlkZWEuIE1ha2VzIGl0IGVhc2llciBmb3IgYWxsIHRv
IGZpbmQgdGhpcyBwYXJ0aWN1bGFyIGZlYXR1cmUgKGFuZCBwb3NzaWJseSBtYXAgaXQgdG8gd2hh
dGV2ZXIgc3RhY2sgdGhleSBhcmUgdXNpbmcpLg0KDQpBdCBsZWFzdCBmcm9tIHRoZSBvbmUgZGVz
Y3JpcHRpb24gb2YgdGhpcyB0aGF0IEkgZm91bmQgaXQgbG9va3MgdG8gYmUgZXhhY3RseSB3aGF0
IHlvdSB3YW50Og0KDQoiQSB2YWx1ZSBvZiAxIGVuYWJsZXMgdGhpcyBvcHRpb24gZm9yIHVuaWNh
c3QgYW5kIG11bHRpY2FzdCBkZXN0aW5hdGlvbnMuIEFsbCBwYWNrZXRzIGFyZSBzZW50IHdpdGhv
dXQgdXNpbmcgcGF0aCBNVFUgZGlzY292ZXJ5IGluZm9ybWF0aW9uLCB1c2luZyB0aGUgbWluaW11
bSBNVFUgc2l6ZSwgdW5sZXNzIGEgZGlyZWN0IHJvdXRlIGlzIGF2YWlsYWJsZSB0byB0aGUgZGVz
dGluYXRpb24uIg0KDQotIEJlcm5pZQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv
bTogamlubWVpLnRhdHV5YUBnbWFpbC5jb20gW21haWx0bzpqaW5tZWkudGF0dXlhQGdtYWlsLmNv
bV0gT24gQmVoYWxmIE9mID8/Pz8NClNlbnQ6IFdlZG5lc2RheSwgTWF5IDA3LCAyMDE0IDExOjU3
IEFNDQpUbzogUmFscGggRHJvbXMNCkNjOiBTaGVuZyBKaWFuZzsgZGhjd2c7IEJlcm5pZSBWb2x6
ICh2b2x6KQ0KU3ViamVjdDogUmU6IFtkaGN3Z10gV0dMQyBmb3IgZHJhZnQtaWV0Zi1kaGMtc2Vk
aGNwdjYtMDIgLSBSZXNwb25kIGJ5IE1heSAxOA0KDQpBdCBXZWQsIDcgTWF5IDIwMTQgMDc6MjM6
MjAgLTA0MDAsDQpSYWxwaCBEcm9tcyA8cmRyb21zLmlldGZAZ21haWwuY29tPiB3cm90ZToNCg0K
PiBIb3dldmVyLCB0aGlzIGV4dGVuc2lvbiB0byBESENQdjYgbWF5IHJlc3VsdCBpbiBESENQdjYg
bWVzc2FnZXMgdGhhdCBhcmUgbXVjaCBsYXJnZXIgdGhhbiBjdXJyZW50IG1lc3NhZ2VzIChhbmQg
YXJlIG11Y2ggbGFyZ2VyIHRoYW4gdGhlIG9yaWdpbmFsIGRlc2lnbmVycyBvZiBESENQIGdlbmVy
YWxseSBhbnRpY2lwYXRlZCkuICBJdCBtYXkgcmVxdWlyZSB0aGUgdXNlIG9mIElQdjYgZnJhZ21l
bnRhdGlvbiwgd2hpY2ggaXMgbm90IHdpZGVseSB1c2VkIGFuZCB3aGljaCBpbnRyb2R1Y2VzIHNv
bWUgcG90ZW50aWFsIHByb2JsZW1zIHdpdGggVURQIHRyYW5zcG9ydC4gIFRoZXJlZm9yZSwgSSB0
aGluayBpdCB3b3VsZCBiZSBwcnVkZW50IHRvIGFkZCBzb21lIGV4cGxpY2l0IGFuYWx5c2lzIGFu
ZCBub3RpY2UgdG8gaW1wbGVtZW50b3JzIGFuZCBkZXBsb3llcnMgb2YgdGhpcyBleHRlbnNpb24g
YWJvdXQgdGhlIGlzc3VlcyBhcm91bmQgbGFyZ2UgREhDUHY2IG1lc3NhZ2VzLg0KDQpJIGFncmVl
Lg0KDQpPbmUgc3BlY2lmaWMgcG9pbnQ6IG5ld2VyIERIQ1B2NiBpbXBsZW1lbnRhdGlvbnMgdGhh
dCBzdXBwb3J0IHRoaXMgcHJvdG9jb2wgd291bGQgaGF2ZSB0byB1c2UgdGhlIElQVjZfVVNFX01J
Tl9NVFUgc29ja2V0IG9wdGlvbiAob3Igc29tZXRoaW5nIGVxdWl2YWxlbnQgdG8gaXQpLCBmb3Ig
ZXhhY3QgdGhlIHNhbWUga2luZCBvZiByZWFzb24gd2h5IGFsbCBtb2Rlcm4gRE5TIHNlcnZlciBp
bXBsZW1lbnRhdGlvbnMgdXNlIGl0IG9uIFVEUCBzb2NrZXRzLiAgSSd2ZSBxdWlja2x5IGNoZWNr
ZWQgYSBmZXcgb3BlbiBzb3VyY2UgaW1wbGVtZW50YXRpb25zLCBhbmQgZm91bmQgbm9uZSBvZiB0
aGVtIHVzZSB0aGlzIG9wdGlvbiByaWdodCBub3cuICBJJ20gbm90IHN1cmUgd2hldGhlciB0aGlz
IGRyYWZ0IHNob3VsZCBiZSBhcyBzcGVjaWZpYyBhcyB0byBtZW50aW9uIHRoYXQgcGFydGljdWxh
ciBzb2NrZXQgb3B0aW9uLCBidXQgYXQgbGVhc3Qgc29tZSBoaWdoZXIgbGV2ZWwgbm90ZXMgdG8g
aW1wbGVtZW50b3JzIHdvdWxkIGJlIHZlcnkgaGVscGZ1bCB0byBhdm9pZCBzdXJwcmlzZSBiZWZv
cmVoYW5kLg0KDQotLQ0KSklOTUVJLCBUYXR1eWENCg==


From nobody Wed May  7 09:25:23 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 E92221A0807 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 09:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level: 
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651] 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 n7z3Ik7UClhj for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 09:25:20 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 344871A07EE for <dhcwg@ietf.org>; Wed,  7 May 2014 09:25:20 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 200731B8282 for <dhcwg@ietf.org>; Wed,  7 May 2014 09:25:16 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 18CD119005C; Wed,  7 May 2014 09:25:16 -0700 (PDT)
Received: from [172.17.67.243] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 May 2014 09:25:15 -0700
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com>
Date: Wed, 7 May 2014 11:25:08 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/HVD-6CwmLqBKfSd6OhL1HAWh4w0
Cc: dhcwg <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 16:25:22 -0000

On May 7, 2014, at 10:57 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> One specific point: newer DHCPv6 implementations that support this
> protocol would have to use the IPV6_USE_MIN_MTU socket option (or
> something equivalent to it), for exact the same kind of reason why all
> modern DNS server implementations use it on UDP sockets.

What reason is that?



From nobody Wed May  7 09:49:21 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 E045D1A07B9 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 09:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id haucpt3yLwpp for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 09:49:18 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 975EF1A07D0 for <dhcwg@ietf.org>; Wed,  7 May 2014 09:49:18 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hm4so9470673wib.10 for <dhcwg@ietf.org>; Wed, 07 May 2014 09:49:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XbkBTkHKFtlS2+YaiSzdfD5G3EiO9dFrZ42Px0C7Ba8=; b=OqjlLH52ik/zDydJZi4FgLCL/DgllppWBook0pABEBQJvhjo9rPmg9Lunkg2FJosCh /ikbY+/A+fgzQthFd+UFLkDOKgypFc+49ZvIlYf/3eedkR52grV6Atk9e48i5+RXA4dF IHDWKe5UGm7RKUwuYRYAiWXVZVGSg3rjhIZKpD6WwN9SyaioEvhbLe0ttYftMbWSvy+5 eUafEZ67nY0XEmblhsUMNPemuq1u+jA7VnP4FToooFPqbbIjUFrXypoJgy0oh6o2u56l dJBppVyWLOG5a/5oVfagH4f33P0fuZS5vttjuBOLA7rTey0BnLN1336hjG9kzQM8vwYv E9Ww==
MIME-Version: 1.0
X-Received: by 10.180.81.40 with SMTP id w8mr27304652wix.45.1399481353849; Wed, 07 May 2014 09:49:13 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.3.14 with HTTP; Wed, 7 May 2014 09:49:13 -0700 (PDT)
In-Reply-To: <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com>
Date: Wed, 7 May 2014 09:49:13 -0700
X-Google-Sender-Auth: cNWJF1rRmaMmgN6RnTSrV5eB8hk
Message-ID: <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/dMn7qCFYbGWo6Ykmm6y-4wngq4c
Cc: dhcwg <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 16:49:20 -0000

At Wed, 7 May 2014 11:25:08 -0500,
Ted Lemon <ted.lemon@nominum.com> wrote:

> > One specific point: newer DHCPv6 implementations that support this
> > protocol would have to use the IPV6_USE_MIN_MTU socket option (or
> > something equivalent to it), for exact the same kind of reason why all
> > modern DNS server implementations use it on UDP sockets.
>
> What reason is that?

To avoid packet drop (+ ICMPv6 too big, which would normally be
ignored for UDP) at an intermediate router when you send a large DNS
(or DHCPv6) message.  In case of DNS, DNSSEC made it more critical.
In case of DHCPv6, sedhcpv6 would make it more critical.  But, on
thinking it in more detail, I realized I made the discussion too simplified
(maybe you were trying to point it out?).  For DHCPv6 we'll need to
discuss some more details:

- If the client only multicasts a message (to servers or relays), at
  least the client does not have this issue (but see the third bullet)
- So it's more about between servers and relays in practice.  In
  particular, since relays are not expected to be aware of sedhcpv6
  options, the implication will be less obvious for them and would be
  worth documenting explicitly.
- Even a client could unicast messages directly to a server after
  receiving the Server Unicast option, so it would still matter for
  clients in some rare cases.
- Regarding the similarity between DNS and DHCPv6, there's one
  important difference between them: in the case of DHCPv6 links (and
  MTUs) over which packets go would be less heterogeneous, so the risk
  of the drop due to this would be much smaller in practice (but that
  doesn't mean we can ignore it completely, so I think it's still
  worth discussing).

--
JINMEI, Tatuya


From nobody Wed May  7 10:11:41 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 DE3301A0834 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 10:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.852
X-Spam-Level: 
X-Spam-Status: No, score=-14.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEqXwuE6oJkk for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 10:11:32 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id C3C851A0821 for <dhcwg@ietf.org>; Wed,  7 May 2014 10:11:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3556; q=dns/txt; s=iport; t=1399482688; x=1400692288; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=BuuDljpv6MSWlYLyXGI+3XfdiTOK30ET6dQIu46boaE=; b=KUMPWsg1s3I9SzYCjW9vta2nDTxIr595JJJffzPvMX3VC23hreoqoBDs FwDRYgTyFhkO2LrB2hbetAqEjjRwKnCxZgWCvg22ruDCaPWykwl+ek6Xl 7cnYs3zuhBOsDVpe/Tdj2s8EKkGju7lsvl9vlDjToz7yj0Csi4i6TrOs0 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAExoalOtJV2b/2dsb2JhbABagwaBJ4JnwjQBGYEBFnSCJQEBAQMBIwQNRQwEAgEIEQQBAQMCBh0DAgICHxEUAQgIAgQBDQUIiCUDCQiqT55uDYY+F4Eqihl4gWYWGwcGgm42gRUBA5dFjwyFYYM0gi8
X-IronPort-AV: E=Sophos;i="4.97,1004,1389744000"; d="scan'208";a="323080575"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP; 07 May 2014 17:11:27 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s47HBRsD024382 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 May 2014 17:11:27 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.140]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Wed, 7 May 2014 12:11:27 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ted Lemon <ted.lemon@nominum.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPag0KHMzNFfxEIk6wcBa/GM4ndJs1oYkAgAAGu4D//7E7YA==
Date: Wed, 7 May 2014 17:11:26 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com>
In-Reply-To: <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.121]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/kNJ-Kh543kSR9QEnLIrS_BbraHg
Cc: dhcwg <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 17:11:40 -0000

QWxzbywgZG9uJ3QgZm9yZ2V0IHRoYXQgdW5pY2FzdCBpcyBwb3NzaWJsZSBmb3IgREhDUHY2IChh
dCB0aGUgc2VydmVyJ3MgZGlzY3JldGlvbikgOikuDQoNCkRvIHdlIHNlZSBhbnkgaGFybSBpbiB1
c2luZyBJUFY2X1VTRV9NSU5fTVRVPw0KDQpJZiB0aGVyZSBpcyBob3AtYnktaG9wIGNvbW11bmlj
YXRpb24gKGkuZS4sICJkaXJlY3Qgcm91dGUiKSwgYXQgbGVhc3QgcGVyIHRoZSBkb2N1bWVudGF0
aW9uIEkgZm91bmQgdGhlIE1UVSBvZiB0aGUgaW50ZXJmYWNlIGlzIHVzZWQgKGkuZS4sICJkaXJl
Y3Qgcm91dGUiKS4gSSBndWVzcyBpZiByZWxheSA8LT4gc2VydmVyIG9yIHJlbGF5IDwtPiByZWxh
eSBjb21tdW5pY2F0aW9uIHJlcXVpcmVzIGludGVybWVkaWF0ZSByb3V0ZXIgaG9wcywgUE1UVSBj
b3VsZCBhcHBseSBhcyB0aGVyZSBhcmUgbGlrZWx5IGZldyBlbmQtcG9pbnRzIGludm9sdmVkIGlu
IHRoZSBjb21tdW5pY2F0aW9uIChqdXN0IG5vdCBzdXJlIGhvdyB3ZWxsIFBNVFUgd29ya3MgZm9y
IFVEUCkuDQoNCi0gQmVybmllDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBq
aW5tZWkudGF0dXlhQGdtYWlsLmNvbSBbbWFpbHRvOmppbm1laS50YXR1eWFAZ21haWwuY29tXSBP
biBCZWhhbGYgT2YgPz8/Pw0KU2VudDogV2VkbmVzZGF5LCBNYXkgMDcsIDIwMTQgMTI6NDkgUE0N
ClRvOiBUZWQgTGVtb24NCkNjOiBkaGN3ZzsgUmFscGggRHJvbXM7IEJlcm5pZSBWb2x6ICh2b2x6
KQ0KU3ViamVjdDogUmU6IFtkaGN3Z10gV0dMQyBmb3IgZHJhZnQtaWV0Zi1kaGMtc2VkaGNwdjYt
MDIgLSBSZXNwb25kIGJ5IE1heSAxOA0KDQpBdCBXZWQsIDcgTWF5IDIwMTQgMTE6MjU6MDggLTA1
MDAsDQpUZWQgTGVtb24gPHRlZC5sZW1vbkBub21pbnVtLmNvbT4gd3JvdGU6DQoNCj4gPiBPbmUg
c3BlY2lmaWMgcG9pbnQ6IG5ld2VyIERIQ1B2NiBpbXBsZW1lbnRhdGlvbnMgdGhhdCBzdXBwb3J0
IHRoaXMgDQo+ID4gcHJvdG9jb2wgd291bGQgaGF2ZSB0byB1c2UgdGhlIElQVjZfVVNFX01JTl9N
VFUgc29ja2V0IG9wdGlvbiAob3IgDQo+ID4gc29tZXRoaW5nIGVxdWl2YWxlbnQgdG8gaXQpLCBm
b3IgZXhhY3QgdGhlIHNhbWUga2luZCBvZiByZWFzb24gd2h5IA0KPiA+IGFsbCBtb2Rlcm4gRE5T
IHNlcnZlciBpbXBsZW1lbnRhdGlvbnMgdXNlIGl0IG9uIFVEUCBzb2NrZXRzLg0KPg0KPiBXaGF0
IHJlYXNvbiBpcyB0aGF0Pw0KDQpUbyBhdm9pZCBwYWNrZXQgZHJvcCAoKyBJQ01QdjYgdG9vIGJp
Zywgd2hpY2ggd291bGQgbm9ybWFsbHkgYmUgaWdub3JlZCBmb3IgVURQKSBhdCBhbiBpbnRlcm1l
ZGlhdGUgcm91dGVyIHdoZW4geW91IHNlbmQgYSBsYXJnZSBETlMgKG9yIERIQ1B2NikgbWVzc2Fn
ZS4gIEluIGNhc2Ugb2YgRE5TLCBETlNTRUMgbWFkZSBpdCBtb3JlIGNyaXRpY2FsLg0KSW4gY2Fz
ZSBvZiBESENQdjYsIHNlZGhjcHY2IHdvdWxkIG1ha2UgaXQgbW9yZSBjcml0aWNhbC4gIEJ1dCwg
b24gdGhpbmtpbmcgaXQgaW4gbW9yZSBkZXRhaWwsIEkgcmVhbGl6ZWQgSSBtYWRlIHRoZSBkaXNj
dXNzaW9uIHRvbyBzaW1wbGlmaWVkIChtYXliZSB5b3Ugd2VyZSB0cnlpbmcgdG8gcG9pbnQgaXQg
b3V0PykuICBGb3IgREhDUHY2IHdlJ2xsIG5lZWQgdG8gZGlzY3VzcyBzb21lIG1vcmUgZGV0YWls
czoNCg0KLSBJZiB0aGUgY2xpZW50IG9ubHkgbXVsdGljYXN0cyBhIG1lc3NhZ2UgKHRvIHNlcnZl
cnMgb3IgcmVsYXlzKSwgYXQNCiAgbGVhc3QgdGhlIGNsaWVudCBkb2VzIG5vdCBoYXZlIHRoaXMg
aXNzdWUgKGJ1dCBzZWUgdGhlIHRoaXJkIGJ1bGxldCkNCi0gU28gaXQncyBtb3JlIGFib3V0IGJl
dHdlZW4gc2VydmVycyBhbmQgcmVsYXlzIGluIHByYWN0aWNlLiAgSW4NCiAgcGFydGljdWxhciwg
c2luY2UgcmVsYXlzIGFyZSBub3QgZXhwZWN0ZWQgdG8gYmUgYXdhcmUgb2Ygc2VkaGNwdjYNCiAg
b3B0aW9ucywgdGhlIGltcGxpY2F0aW9uIHdpbGwgYmUgbGVzcyBvYnZpb3VzIGZvciB0aGVtIGFu
ZCB3b3VsZCBiZQ0KICB3b3J0aCBkb2N1bWVudGluZyBleHBsaWNpdGx5Lg0KLSBFdmVuIGEgY2xp
ZW50IGNvdWxkIHVuaWNhc3QgbWVzc2FnZXMgZGlyZWN0bHkgdG8gYSBzZXJ2ZXIgYWZ0ZXINCiAg
cmVjZWl2aW5nIHRoZSBTZXJ2ZXIgVW5pY2FzdCBvcHRpb24sIHNvIGl0IHdvdWxkIHN0aWxsIG1h
dHRlciBmb3INCiAgY2xpZW50cyBpbiBzb21lIHJhcmUgY2FzZXMuDQotIFJlZ2FyZGluZyB0aGUg
c2ltaWxhcml0eSBiZXR3ZWVuIEROUyBhbmQgREhDUHY2LCB0aGVyZSdzIG9uZQ0KICBpbXBvcnRh
bnQgZGlmZmVyZW5jZSBiZXR3ZWVuIHRoZW06IGluIHRoZSBjYXNlIG9mIERIQ1B2NiBsaW5rcyAo
YW5kDQogIE1UVXMpIG92ZXIgd2hpY2ggcGFja2V0cyBnbyB3b3VsZCBiZSBsZXNzIGhldGVyb2dl
bmVvdXMsIHNvIHRoZSByaXNrDQogIG9mIHRoZSBkcm9wIGR1ZSB0byB0aGlzIHdvdWxkIGJlIG11
Y2ggc21hbGxlciBpbiBwcmFjdGljZSAoYnV0IHRoYXQNCiAgZG9lc24ndCBtZWFuIHdlIGNhbiBp
Z25vcmUgaXQgY29tcGxldGVseSwgc28gSSB0aGluayBpdCdzIHN0aWxsDQogIHdvcnRoIGRpc2N1
c3NpbmcpLg0KDQotLQ0KSklOTUVJLCBUYXR1eWENCg==


From nobody Wed May  7 11:45:30 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 A3C161A037D for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 11:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 t-QHmZxUfg3L for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 11:45:27 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id D108D1A0268 for <dhcwg@ietf.org>; Wed,  7 May 2014 11:45:27 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 13C161B82A8 for <dhcwg@ietf.org>; Wed,  7 May 2014 11:45:23 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id BC9BD19005C; Wed,  7 May 2014 11:45:22 -0700 (PDT)
Received: from [172.17.67.243] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 May 2014 11:45:22 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com>
Date: Wed, 7 May 2014 13:45:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/IzL2SBUXNV_3df2HB6TMpEUVrfM
Cc: dhcwg <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 18:45:28 -0000

On May 7, 2014, at 12:11 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> Do we see any harm in using IPV6_USE_MIN_MTU?

I would like to hear a description of the actual benefit it would =
confer.   I suspect there is none.   I can't find any documentation for =
the option using google, and the only discussion I find about it is in =
relation to BIND 10.


From nobody Wed May  7 11:51:25 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 D57651A07CA for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 11:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SyBZBDPO7pXr for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 11:51:22 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 75D1F1A0268 for <dhcwg@ietf.org>; Wed,  7 May 2014 11:51:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1098; q=dns/txt; s=iport; t=1399488678; x=1400698278; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=biYkj9SmCBhiuZd/8yaVBlsJD9/DwsSPsuiaiDB0SOY=; b=DKi9r9KOZtV4FvT4D5j52Ndqg1btWKMzypQCSUwmu9MfXRciDcG157j2 rBevief+eG+/voGiRXjVbrphIRpj0PISo0DdEAMBuQsqU+ziCD3rg61hd AJ5YDHwi4c2F9Uz1mJeSdfcfEcZnEdBauvuzOSrdu7cS1SA7m5f2p34C8 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAK9/alOtJV2Y/2dsb2JhbABagwZPWIJnunyHPAGBHBZ0giUBAQEEAQEBHgFMBAcMBAIBCBEEAQEBAQMGBRgCAwInCxQJCAIEDgUIiDkNjjKcGQGlPBeBJ4ocgl4xBwaCazmBFQSEWgKnVoM0bQEBAYE/
X-IronPort-AV: E=Sophos;i="4.97,1005,1389744000"; d="scan'208";a="322918463"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 07 May 2014 18:51:18 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s47IpI5T012065 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 May 2014 18:51:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.140]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0123.003; Wed, 7 May 2014 13:51:17 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <ted.lemon@nominum.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPag0KHMzNFfxEIk6wcBa/GM4ndJs1oYkAgAAGu4D//7E7YIAAby6A//+thtA=
Date: Wed, 7 May 2014 18:51:16 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com>
In-Reply-To: <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.121]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/MMQSaW-iT5QW48_E--fdLRdHhuU
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 18:51:24 -0000

Here's some documentation from IBM (google found this - 2nd in list when se=
arching for IPV6_USE_MIN_MTU):

http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=3D%2Fcom.ibm.zo=
s.r12.hale001%2Fipv6d0151000614.htm

There are plenty of other links -- About 10,100 results (0.25 seconds).

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Wednesday, May 07, 2014 2:45 PM
To: Bernie Volz (volz)
Cc: dhcwg; =1B$B?@L@C#:H=1B(B; Ralph Droms
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 1=
8

On May 7, 2014, at 12:11 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> Do we see any harm in using IPV6_USE_MIN_MTU?

I would like to hear a description of the actual benefit it would confer.  =
 I suspect there is none.   I can't find any documentation for the option u=
sing google, and the only discussion I find about it is in relation to BIND=
 10.

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


From nobody Wed May  7 12:08:13 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558D41A04A2 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 eNCOKz-LQHSI for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:08:07 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 689191A02A8 for <dhcwg@ietf.org>; Wed,  7 May 2014 12:08:07 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7D83C1B8290 for <dhcwg@ietf.org>; Wed,  7 May 2014 12:08:03 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 7587219005C; Wed,  7 May 2014 12:08:03 -0700 (PDT)
Received: from [172.17.67.243] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 May 2014 12:08:03 -0700
Content-Type: text/plain; charset="iso-2022-jp"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com>
Date: Wed, 7 May 2014 14:07:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/A8T4o03HNw1L2ZkuQIbPgrCObgo
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 19:08:09 -0000

On May 7, 2014, at 1:51 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> Here's some documentation from IBM (google found this - 2nd in list =
when searching for IPV6_USE_MIN_MTU):

Ah, thanks.   That took so long to load when I tried it that I gave up, =
but I waited this time and got the info.

I think this option is not only unnecessary, but harmful, when used with =
DHCP, because it sets the maximum DHCP message size to 1280 when in =
nearly every conceivable circumstance, the path MTU will be at least =
1500.

The reason why you might want to enable this option for DNS is that you =
really care about latency on DNS queries, and waiting for PMTU discovery =
increases latency.   No such problem exists for DHCP: the initial packet =
is _always_ multicast by the client, and that's the only one where we =
care about latency.   There's no latency for the client because it knows =
the path MTU--it's the link MTU.   There may be occasional latency on =
the relay agent, but it is amortized over many clients, and hence not =
really a problem.   It's unlikely that the same client will pay the =
latency tax twice.

Unicast queries only happen at renewal time.   At renewal time, latency =
is immaterial: you already have a configuration=1B$B!=3D=1B(Byou're just =
refreshing it, so nothing is blocked waiting on the response.

So I see no beneficial use case for this, and many harmful use cases.   =
We should be advising implementors _not_ to use this option, not =
advising them _to_ use it.


From nobody Wed May  7 12:14:45 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 C17391A0843 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.152
X-Spam-Level: 
X-Spam-Status: No, score=-8.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_BACKHAIR_55=1, J_BACKHAIR_56=1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 GmSUlVKIh7Xj for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:14:40 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id CE8391A0814 for <dhcwg@ietf.org>; Wed,  7 May 2014 12:14:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2827; q=dns/txt; s=iport; t=1399490076; x=1400699676; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=3mdAWIc9E8Q+DAIv8NmDwmltSIMyxd10RkrNARndNZc=; b=T2W4GgVDHnvK+xgWwfkxB1y+S7DAZrgZr9uH8CZNjRk6+/1uY03aswfm FoQqbACXt3yk1hwcZmqWp4rNGzFdx1I9tUK3bRXAMEcqrZMqVlWHyRZJJ 8/6dCSKk7r/YeUqlYZvz9sZEwRBorF0JfcItVvKKmr8f8au/g2CTUY/M2 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAMmFalOtJA2H/2dsb2JhbABagwaBJ4JnwjgBgRwWdIIlAQEBBCEBBVIMBAIBCBEEAQEBAQMGBRgCAwIyFAkIAgQOBQiIOY5HnBkBpTsXgSeKHIJeMQcGgms5gRUBA4RaAqdWgzSCLw
X-IronPort-AV: E=Sophos;i="4.97,1005,1389744000"; d="scan'208";a="41848699"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-5.cisco.com with ESMTP; 07 May 2014 19:14:36 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s47JEa2m018278 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 May 2014 19:14:36 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.140]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Wed, 7 May 2014 14:14:36 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <ted.lemon@nominum.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPag0KHMzNFfxEIk6wcBa/GM4ndJs1oYkAgAAGu4D//7E7YIAAby6A//+thtCAAFjVAP//rJ9Q
Date: Wed, 7 May 2014 19:14:35 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B00F31E@xmb-rcd-x04.cisco.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com> <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com>
In-Reply-To: <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.121]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/jwq-j_qQIpMlYXvZt5HNL3HxNiY
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 19:14:42 -0000

Ted:

1. There is client unicast. Though not sure how much it is used.
2. From my understanding (at least from the IBM documentation), if the dest=
ination is local to link (i.e. client multicast), the link's MTU is used (n=
ot the min MTU). So this still benefits client multicast and most of the co=
mmunication in DHCPv6 to use the FULL link's MTU.

So the only case is when the next hop (again, either relay<->relay or relay=
<->server or client/server unicast cases where the next-hop isn't local to =
the link), will the 1280 MTU be used and result in fragmentation.

I don't know who well PMTU works these days for UDP and how widely it is im=
plemented in the common stacks. If it works great, then maybe this option i=
s unnecessary (as the components must likely to need them are probably on '=
good' stacks - relays and servers that implement PMTU).

I am taking a sample of one (the IBM documentation) and perhaps there is ot=
her information that says this option doesn't work well.

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:ted.lemon@nominum.com]=20
Sent: Wednesday, May 07, 2014 3:08 PM
To: Bernie Volz (volz)
Cc: dhcwg; =1B$B?@L@C#:H=1B(B; Ralph Droms
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 1=
8

On May 7, 2014, at 1:51 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> Here's some documentation from IBM (google found this - 2nd in list when =
searching for IPV6_USE_MIN_MTU):

Ah, thanks.   That took so long to load when I tried it that I gave up, but=
 I waited this time and got the info.

I think this option is not only unnecessary, but harmful, when used with DH=
CP, because it sets the maximum DHCP message size to 1280 when in nearly ev=
ery conceivable circumstance, the path MTU will be at least 1500.

The reason why you might want to enable this option for DNS is that you rea=
lly care about latency on DNS queries, and waiting for PMTU discovery incre=
ases latency.   No such problem exists for DHCP: the initial packet is _alw=
ays_ multicast by the client, and that's the only one where we care about l=
atency.   There's no latency for the client because it knows the path MTU--=
it's the link MTU.   There may be occasional latency on the relay agent, bu=
t it is amortized over many clients, and hence not really a problem.   It's=
 unlikely that the same client will pay the latency tax twice.

Unicast queries only happen at renewal time.   At renewal time, latency is =
immaterial: you already have a configuration=1B$B!=3D=1B(Byou're just refre=
shing it, so nothing is blocked waiting on the response.

So I see no beneficial use case for this, and many harmful use cases.   We =
should be advising implementors _not_ to use this option, not advising them=
 _to_ use it.


From nobody Wed May  7 12:28:54 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2C11A08E2 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.551
X-Spam-Level: 
X-Spam-Status: No, score=-0.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_BACKHAIR_55=1, J_BACKHAIR_56=1, RP_MATCHES_RCVD=-0.651] 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 XuNXh0YQBmv2 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:28:52 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id D1B3F1A08E1 for <dhcwg@ietf.org>; Wed,  7 May 2014 12:28:52 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D8AF41B82AA for <dhcwg@ietf.org>; Wed,  7 May 2014 12:28:48 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id C02D019005C; Wed,  7 May 2014 12:28:48 -0700 (PDT)
Received: from [172.17.67.243] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 May 2014 12:28:48 -0700
Content-Type: text/plain; charset="iso-2022-jp"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B00F31E@xmb-rcd-x04.cisco.com>
Date: Wed, 7 May 2014 14:28:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <9C5EC552-A039-4EC5-B475-3A58A3C9BC70@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com> <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F31E@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/x6Q4ACp0BTktwJy1ybVexcBniJI
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 19:28:53 -0000

On May 7, 2014, at 2:14 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> 1. There is client unicast. Though not sure how much it is used.

You may have missed the point in my message where I addressed that.   =
Since unicast _only_ happens on renewal, there is no latency issue.

> 2. =46rom my understanding (at least from the IBM documentation), if =
the destination is local to link (i.e. client multicast), the link's MTU =
is used (not the min MTU). So this still benefits client multicast and =
most of the communication in DHCPv6 to use the FULL link's MTU.

Sure, but in that case it just doesn't matter.

> So the only case is when the next hop (again, either relay<->relay or =
relay<->server or client/server unicast cases where the next-hop isn't =
local to the link), will the 1280 MTU be used and result in =
fragmentation.
>=20
> I don't know who well PMTU works these days for UDP and how widely it =
is implemented in the common stacks. If it works great, then maybe this =
option is unnecessary (as the components must likely to need them are =
probably on 'good' stacks - relays and servers that implement PMTU).

PMTU discovery is necessary for IPv6.   If the host stack doesn't =
support it, it's broken and needs fixed.   I have not heard of any cases =
of this.   Middlebox brokenness is an issue when packets cross networks =
that are not controlled by the operator.   That's not the case for DHCP. =
  So I don't think we need to be concerned about this.   This is another =
difference between DHCP and DNS.


From nobody Wed May  7 12:37:01 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7305E1A02F1 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.152
X-Spam-Level: 
X-Spam-Status: No, score=-8.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_BACKHAIR_55=1, J_BACKHAIR_56=1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 aR1wsknSzuvQ for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:36:58 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 6458B1A00E8 for <dhcwg@ietf.org>; Wed,  7 May 2014 12:36:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2587; q=dns/txt; s=iport; t=1399491414; x=1400701014; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=WxwavMsfaEW26OxhVrOXhN8uwziZUK17kxmkV4RuhLE=; b=EOE9iW1RxfDnz3pwQGsHVpVH/xwTu4fzDcEJf2iVMGOqOC5GymxwXGy9 CvizOWqpGjVmV1auesq69dbrKPJkNnwx8M8xMZt4jlkrAJjRVb0ne/0UL nHXjKvj0US16HVxZG78/Xy35m2H7NozuWFsQ0yvyo+RemxQUdWHAZxQK4 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAOSKalOtJA2N/2dsb2JhbABagwZPWIJnunyHPAGBHBZ0giUBAQEDAQEBAR4BBUcLBQcEAgEIEQQBAQEBAwYFGAIDAicLFAkIAgQOBQiIMQgNjj+cGQGlOhMEgSeKHIJeMQcGgms5gRUErDKDNIIv
X-IronPort-AV: E=Sophos;i="4.97,1005,1389744000"; d="scan'208";a="41851709"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-2.cisco.com with ESMTP; 07 May 2014 19:36:54 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s47JarJA027547 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 May 2014 19:36:54 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.140]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Wed, 7 May 2014 14:36:53 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <ted.lemon@nominum.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPag0KHMzNFfxEIk6wcBa/GM4ndJs1oYkAgAAGu4D//7E7YIAAby6A//+thtCAAFjVAP//rJ9QAAsk+AAACmPbUA==
Date: Wed, 7 May 2014 19:36:53 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B00F37C@xmb-rcd-x04.cisco.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com> <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F31E@xmb-rcd-x04.cisco.com> <9C5EC552-A039-4EC5-B475-3A58A3C9BC70@nominum.com>
In-Reply-To: <9C5EC552-A039-4EC5-B475-3A58A3C9BC70@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.121]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/zsl1TSbBUjkZveede0bwU1rp2kk
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 19:36:59 -0000

I wasn't concerned with latency itself - except for the big one ... being a=
ble to get the packets through at all.

If PMTU for UDPv6 is always done and works great - then there is no issue a=
s PMTU should work it out.

> Middlebox brokenness is an issue when packets cross networks that are not=
 controlled by the operator.  =20

If that is the case, then PMTU or using MIN MTU does not help us. We must a=
ssume that this is not the case (if we are to use larger packets).

Or, perhaps we need a relay to relay <-> relay / server TCP (STCP, ...) pac=
ket delivery capability :).

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Wednesday, May 07, 2014 3:29 PM
To: Bernie Volz (volz)
Cc: dhcwg; =1B$B?@L@C#:H=1B(B; Ralph Droms
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 1=
8

On May 7, 2014, at 2:14 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> 1. There is client unicast. Though not sure how much it is used.

You may have missed the point in my message where I addressed that.   Since=
 unicast _only_ happens on renewal, there is no latency issue.

> 2. From my understanding (at least from the IBM documentation), if the de=
stination is local to link (i.e. client multicast), the link's MTU is used =
(not the min MTU). So this still benefits client multicast and most of the =
communication in DHCPv6 to use the FULL link's MTU.

Sure, but in that case it just doesn't matter.

> So the only case is when the next hop (again, either relay<->relay or rel=
ay<->server or client/server unicast cases where the next-hop isn't local t=
o the link), will the 1280 MTU be used and result in fragmentation.
>=20
> I don't know who well PMTU works these days for UDP and how widely it is =
implemented in the common stacks. If it works great, then maybe this option=
 is unnecessary (as the components must likely to need them are probably on=
 'good' stacks - relays and servers that implement PMTU).

PMTU discovery is necessary for IPv6.   If the host stack doesn't support i=
t, it's broken and needs fixed.   I have not heard of any cases of this.   =
Middlebox brokenness is an issue when packets cross networks that are not c=
ontrolled by the operator.   That's not the case for DHCP.   So I don't thi=
nk we need to be concerned about this.   This is another difference between=
 DHCP and DNS.

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


From nobody Wed May  7 12:42:05 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 A0F7D1A02F1 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 zE34_o1K8sPL for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:42:00 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 71C981A02AC for <dhcwg@ietf.org>; Wed,  7 May 2014 12:42:00 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 85DAD1B82A4 for <dhcwg@ietf.org>; Wed,  7 May 2014 12:41:56 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 771D819005C; Wed,  7 May 2014 12:41:56 -0700 (PDT)
Received: from [172.17.67.243] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 May 2014 12:41:56 -0700
Content-Type: text/plain; charset="iso-2022-jp"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B00F37C@xmb-rcd-x04.cisco.com>
Date: Wed, 7 May 2014 14:41:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <18E909A0-1955-4E5B-A003-304FE2B946FD@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com> <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F31E@xmb-rcd-x04.cisco.com> <9C5EC552-A039-4EC5-B475-3A58A3C9BC70@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F37C@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/IrtE4QcqoWh0gDLTjHKErP2Q89k
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 19:42:01 -0000

There are two ways to do PMTU discovery.   One is to just send the =
packet, and if we get an ICMP Packet Too Big packet back, we set the =
path MTU to the reported size and try again.   The other is to detect it =
in the application layer protocol.   In this case, that would be DHCP, =
probably the DHCP relay agent and server.   This would be necessary in =
the case of a firewall that drops ICMP Packet Too Big messages.

I think it would make sense to add a recommendation in 3315bis that =
operators configure their firewalls to pass ICMP Packet Too Big =
messages.   I don't think we should go any further than that.


From nobody Wed May  7 12:52:49 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 3968D1A02E8 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeMK0-WCkp7a for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:52:44 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id 733F81A0366 for <dhcwg@ietf.org>; Wed,  7 May 2014 12:52:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2032; q=dns/txt; s=iport; t=1399492358; x=1400701958; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=AIjrjDeH+xRce6Ypvx7jm9Ng2u3Ll5wggBRbEkRl1bU=; b=j+6u9WIUHgYrx4HD8uUVvhteKGKarw3Mu9tCgIeoYfTiaUYG0QcTOd99 oDRMk8EgfnCB3OKBnVzHcaB5vJ8cUu8m9FZFbx2ieYm1ur4/G75c0Qaui jaChht0sYIU4JTuRW5i96JaVHIQysq4f+sCtmr+8rtBOcShYE0eUEYJiV Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAAmOalOtJV2Z/2dsb2JhbABagwZPWIJnwjgBgRwWdIIlAQEBAgIhAQVSDAQCAQgRBAEBAgMGBRgCAwIyFAkIAgQOBQiIOQ2OOJwZAaU6F4EnihyCShQxBwaCazmBFQSac5E/gzRtAYFB
X-IronPort-AV: E=Sophos;i="4.97,1006,1389744000"; d="scan'208";a="41862095"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-7.cisco.com with ESMTP; 07 May 2014 19:52:38 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s47JqcOT009860 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 May 2014 19:52:38 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.140]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Wed, 7 May 2014 14:52:37 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <ted.lemon@nominum.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPag0KHMzNFfxEIk6wcBa/GM4ndJs1oYkAgAAGu4D//7E7YIAAby6A//+thtCAAFjVAP//rJ9QAAsk+AAACmPbUP//sJEAgABTnVA=
Date: Wed, 7 May 2014 19:52:37 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B00F3EF@xmb-rcd-x04.cisco.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com> <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F31E@xmb-rcd-x04.cisco.com> <9C5EC552-A039-4EC5-B475-3A58A3C9BC70@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F37C@xmb-rcd-x04.cisco.com> <18E909A0-1955-4E5B-A003-304FE2B946FD@nominum.com>
In-Reply-To: <18E909A0-1955-4E5B-A003-304FE2B946FD@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.70.121]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/evHoowFo9gk1ENHWfvz32WWn63k
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 19:52:46 -0000

It is interesting that Jinmei raised this issue given the following present=
ation he gave:

http://www.v6.wide.ad.jp/Presentations/ietf49-udpapp.pdf

"- But ... At least every BSD kernel always performs PMTU discovery.
 - not necessary if we can always rely on the kernel=1B$B!G=1B(Bs behavior.=
"

I do agree that the DNS problem is different because (a) there may not be m=
any attempts per 'transaction' so working out the PMTU can be difficult and=
 (b) there could be LOTS of end-points and that may exceed the kernel's cac=
he by the time a request comes around again.

So, I guess best to just rely on the Kernel PMTU support.

Getting back to this draft, I think pointing out that this can result in la=
rge packets and that for some communication (relay <-> relay/server, client=
/server unicast), PMTU support is critical. And, that where packets are lar=
ger than the v6 min mtu (1280), firewalls in the DHCPv6 communication path =
that drop fragments must not be used.

We can consider your request in 3315bis - I created http://trac.tools.ietf.=
org/group/dhcpv6bis/ticket/92.

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:ted.lemon@nominum.com]=20
Sent: Wednesday, May 07, 2014 3:42 PM
To: Bernie Volz (volz)
Cc: dhcwg; =1B$B?@L@C#:H=1B(B; Ralph Droms
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 1=
8

There are two ways to do PMTU discovery.   One is to just send the packet, =
and if we get an ICMP Packet Too Big packet back, we set the path MTU to th=
e reported size and try again.   The other is to detect it in the applicati=
on layer protocol.   In this case, that would be DHCP, probably the DHCP re=
lay agent and server.   This would be necessary in the case of a firewall t=
hat drops ICMP Packet Too Big messages.

I think it would make sense to add a recommendation in 3315bis that operato=
rs configure their firewalls to pass ICMP Packet Too Big messages.   I don'=
t think we should go any further than that.


From nobody Wed May  7 12:59:52 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE211A02F8 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 r0RwHBkDT5sG for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 12:59:38 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id CD34C1A0366 for <dhcwg@ietf.org>; Wed,  7 May 2014 12:59:38 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C47E91B82A4 for <dhcwg@ietf.org>; Wed,  7 May 2014 12:59:34 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A744619005C; Wed,  7 May 2014 12:59:34 -0700 (PDT)
Received: from [172.17.67.243] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 May 2014 12:59:34 -0700
Content-Type: text/plain; charset="iso-2022-jp"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B00F3EF@xmb-rcd-x04.cisco.com>
Date: Wed, 7 May 2014 14:59:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <94504235-1ADB-4C0A-9AEB-E46A1746453E@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com> <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F31E@xmb-rcd-x04.cisco.com> <9C5EC552-A039-4EC5-B475-3A58A3C9BC70@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F37C@xmb-rcd-x04.cisco.com> <18E909A0-1955-4E5B-A003-304FE2B946FD@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F3EF@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/caakW2TvC0A9F-tnfHQnsZuOQb4
Cc: dhcwg <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 19:59:41 -0000

On May 7, 2014, at 2:52 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> So, I guess best to just rely on the Kernel PMTU support.

Yup.

> Getting back to this draft, I think pointing out that this can result =
in large packets and that for some communication (relay <-> =
relay/server, client/server unicast), PMTU support is critical. And, =
that where packets are larger than the v6 min mtu (1280), firewalls in =
the DHCPv6 communication path that drop fragments must not be used.

Yup.

> We can consider your request in 3315bis - I created =
http://trac.tools.ietf.org/group/dhcpv6bis/ticket/92.

Thanks.

BTW, reading Jinmei's excellent presentation, he does say one thing that =
contradicts what I said, and I would assume that he is correct and I am =
wrong: if you send a UDP Packet and get an ICMP too big back, the kernel =
doesn't retransmit.   So this would result in a retransmission on the =
DHCP side.   DHCP does retransmit, so this is okay, but it's worth being =
clear about it.

We _could_ consider defining a PMTU discovery mechanism at the =
application layer for DHCPv6, but I think we should wait until someone =
comes to us and says "we are having a problem" before doing so.


From nobody Wed May  7 13:26:06 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 BB85D1A0381 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 13:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q8aWoio5OpNy for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 13:26:03 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF5E1A02F4 for <dhcwg@ietf.org>; Wed,  7 May 2014 13:26:03 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id y10so1517857wgg.1 for <dhcwg@ietf.org>; Wed, 07 May 2014 13:25:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=l/TJPVArURIX64JiArqZyu37605EeyTNINkdd7GJIlg=; b=IoX15mYlRdpi7eQKBJ7JBwOuDjHe9SXBsnb2fyVOLL9uQWuSwXmpesdJo5xmHWjc0c 1o5NxTE5nNwBoa62nY7pwoQKhUnNV+lRrYIi1zsy9mvXLd4Izc8/uulCxtKfFzY+zH2D qECNh5Il++BqGLAzkxA69rD8t3eLQT04EbLcNS8ZMQGbVnjNS+n/s6QaI5yram3PSBib JcS7nzj5iXbJZY6awBjz2r2d217dIKRAqRKltxA7Vv4w4xxVn+BQT6UE5PKdvt0SJmol kZb1JVFa4QiVKLQTlDjvdtyFKgTd/TJjhYPb4U1hjBZ8CxCQnznD8oXdFmFA9XZKvu4B bPtw==
MIME-Version: 1.0
X-Received: by 10.180.75.45 with SMTP id z13mr1824wiv.41.1399494358782; Wed, 07 May 2014 13:25:58 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.3.14 with HTTP; Wed, 7 May 2014 13:25:58 -0700 (PDT)
In-Reply-To: <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com> <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com>
Date: Wed, 7 May 2014 13:25:58 -0700
X-Google-Sender-Auth: 6eXgNOm7ldgkRv9jGqZrXpv4wGM
Message-ID: <CAJE_bqfCp31YnR1p+AaET=_MU6mBL1hytnp43gt+CHrr5Fw_0g@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/4ovyUg3qrYDjwqXTc7zCqwl4lbs
Cc: dhcwg <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 20:26:04 -0000

At Wed, 7 May 2014 14:07:58 -0500,
Ted Lemon <ted.lemon@nominum.com> wrote:

> I think this option is not only unnecessary, but harmful, when used with DHCP, because it sets the maximum DHCP message size to 1280

why?  This option just makes the message (however big it is) to be
fragmented at 1280 bytes.

> The reason why you might want to enable this option for DNS is that
> you really care about latency on DNS queries, and waiting for PMTU
> discovery increases latency.   No such problem exists for DHCP

Hmm, I thought many kernel implementations don't trust an incoming too
big message unless it has a corresponding connected socket to avoid
resource exhaustion DoS and PMTU discovery didn't work well for non
connected sockets (often the case for UDP applications).  But more
recent implementations seem to be smarter than that, allowing such
messages with some limitation.  So, in the end, it seems I was wrong:
as you said this option won't be necessary for DHCPv6 (still not sure
if it's "harmful" though as stated above, but that's not important at
this point).

--
JINMEI, Tatuya


From nobody Wed May  7 13:33:58 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 23A8F1A03A4 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 13:33:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level: 
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651] 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 LDzjsmI0u0a1 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 13:33:56 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 5D9681A01AC for <dhcwg@ietf.org>; Wed,  7 May 2014 13:33:56 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2F7411B82A4 for <dhcwg@ietf.org>; Wed,  7 May 2014 13:33:52 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 241D119005C; Wed,  7 May 2014 13:33:52 -0700 (PDT)
Received: from [172.17.67.243] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 7 May 2014 13:33:52 -0700
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAJE_bqfCp31YnR1p+AaET=_MU6mBL1hytnp43gt+CHrr5Fw_0g@mail.gmail.com>
Date: Wed, 7 May 2014 15:33:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <DE89DC07-ABAD-463F-884D-030A1C015AEC@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com> <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com> <CAJE_bqfCp31YnR1p+AaET=_MU6mBL1hytnp43gt+CHrr5Fw_0g@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/TYJRPekbCzmnZ-pZZlniLx942vU
Cc: dhcwg <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 07 May 2014 20:33:57 -0000

On May 7, 2014, at 3:25 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> So, in the end, it seems I was wrong:
> as you said this option won't be necessary for DHCPv6 (still not sure
> if it's "harmful" though as stated above, but that's not important at
> this point).

I may have overstated the point.   Fragmentation is messy and presents =
an attack surface, so I suspect it's considered even less safe to pass =
through firewalls than ICMP Packet Too Big messages.   But you're right =
that it's not quite at the level of "harmful" to rely on it.

In any case, thanks for raising this.   I think it's a useful =
discussion.=


From nobody Wed May  7 18:18:43 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 027F51A0450 for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 18:18:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 mpRSzA4ZMkDX for <dhcwg@ietfa.amsl.com>; Wed,  7 May 2014 18:18:28 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 213F11A044F for <dhcwg@ietf.org>; Wed,  7 May 2014 18:18:26 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGM95310; Thu, 08 May 2014 01:18:22 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 8 May 2014 02:14:53 +0100
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 8 May 2014 02:16:32 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Thu, 8 May 2014 09:16:24 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPY9fqOkQX2Up+wk+VaPjsYGUK15sp5cSAgALR/YCAAAxhgIAGX9Jg///JsACAAC/igIABNuCwgAArTQCAAEyVAIAAB74AgAAGuoCAAAY1AIAAGjSAgAABsQCAAASqAIAAAdqAgAAD7QCAAAJOgIAAAWIAgAADA4CAAAHlAIAA3RhQ
Date: Thu, 8 May 2014 01:16:24 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE44068@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B008430@xmb-rcd-x04.cisco.com> <4F2473AB-E8F7-4620-874C-3DCA59E70DE5@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE431FB@nkgeml512-mbx.china.huawei.com> <489D13FBFA9B3E41812EA89F188F018E1B00BAC1@xmb-rcd-x04.cisco.com> <9A6A9452-AF57-4EE1-9401-E0CE26922E6B@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE438BE@nkgeml512-mbx.china.huawei.com> <4891B713-5C8E-414A-99D7-64869C2E6F3A@gmail.com> <CAJE_bqc+qofsHEHZyuG7UotHmZ170OuFoUzz13hz7Rj_8V5FsA@mail.gmail.com> <87A01A92-7517-40A4-8DD0-EE29AADA4AF6@nominum.com> <CAJE_bqeKYoRzVxSgJHg2Ud6H2qEZGaEdFyD=4Ps84NTFyOdELA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B00EF3B@xmb-rcd-x04.cisco.com> <074EF8DF-6404-4D90-B56C-6955A3939A6D@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F1F6@xmb-rcd-x04.cisco.com> <9EDC6F15-62FA-42B4-A145-94CEFAAE2918@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F31E@xmb-rcd-x04.cisco.com> <9C5EC552-A039-4EC5-B475-3A58A3C9BC70@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F37C@xmb-rcd-x04.cisco.com> <18E909A0-1955-4E5B-A003-304FE2B946FD@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1B00F3EF@xmb-rcd-x04.cisco.com> <94504235-1ADB-4C0A-9AEB-E46A1746453E@nominum.com>
In-Reply-To: <94504235-1ADB-4C0A-9AEB-E46A1746453E@nominum.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/EDAL495SfS1Q6-z8pWQeTFNv32c
Cc: dhcwg <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 08 May 2014 01:18:30 -0000

Pj4gR2V0dGluZyBiYWNrIHRvIHRoaXMgZHJhZnQsIEkgdGhpbmsgcG9pbnRpbmcgb3V0IHRoYXQg
dGhpcyBjYW4gcmVzdWx0IGluIGxhcmdlDQo+cGFja2V0cyBhbmQgdGhhdCBmb3Igc29tZSBjb21t
dW5pY2F0aW9uIChyZWxheSA8LT4gcmVsYXkvc2VydmVyLA0KPmNsaWVudC9zZXJ2ZXIgdW5pY2Fz
dCksIFBNVFUgc3VwcG9ydCBpcyBjcml0aWNhbC4gQW5kLCB0aGF0IHdoZXJlIHBhY2tldHMgYXJl
DQo+bGFyZ2VyIHRoYW4gdGhlIHY2IG1pbiBtdHUgKDEyODApLCBmaXJld2FsbHMgaW4gdGhlIERI
Q1B2NiBjb21tdW5pY2F0aW9uDQo+cGF0aCB0aGF0IGRyb3AgZnJhZ21lbnRzIG11c3Qgbm90IGJl
IHVzZWQuDQo+DQo+WXVwLg0KDQpNaXNzZWQgdGhlIGRpc2N1c3Npb24gcHJvY2VzcyBkdWUgdG8g
dGhlIGRpZmZlcmVudCBvZiB0aW1lIHpvbmVzLiBJIGFncmVlIHRoZSBjb25jbHVzaW9uIHRoYXQg
Z290IGJ5IHRoZSBkaXNjdXNzaW9uLiBGb3IgdXMsIHRoZXJlIGlzIG5vIG11Y2ggd2UgY291bGQg
ZG8gaW4gcHJvdG9jb2wgZGVzaWduIGFzcGVjdC4gQnV0LCBjbGVhcmx5IHBvaW50aW5nIG91dCB0
aGUgc2VkaGNwdjYgcGFja2V0cyBhcmUgbGFyZ2Ugd291bGQgYmUgdmVyeSBoZWxwZnVsIGZvciBp
bXBsZW1lbnRlcnMgYW5kIGRlcGxveW1lbnQuIFdlIHdpbGwgYWRkIHNvbWUgdGV4dCBhbW9uZyB3
aXRoIG90aGVyIGNvbW1lbnRzIHdlIHJlY2VpdmVkIGR1cmluZyBXR0xDLg0KDQpSZWdhcmRzLA0K
DQpTaGVuZyArIERhY2hlbmcNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+ZGhjd2cgbWFpbGluZyBsaXN0DQo+ZGhjd2dAaWV0Zi5vcmcNCj5odHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RoY3dnDQo=


From nobody Thu May  8 01:57:26 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 241BE1A04A7 for <dhcwg@ietfa.amsl.com>; Thu,  8 May 2014 01:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.552
X-Spam-Level: 
X-Spam-Status: No, score=-4.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 mIbQ0ByBSsOb for <dhcwg@ietfa.amsl.com>; Thu,  8 May 2014 01:57:22 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2121A1A04A3 for <dhcwg@ietf.org>; Thu,  8 May 2014 01:57:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGN28561; Thu, 08 May 2014 08:57:16 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 8 May 2014 09:55:33 +0100
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 8 May 2014 09:57:12 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Thu, 8 May 2014 16:57:01 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPY9fqOkQX2Up+wk+VaPjsYGUK15sp5cSAgAlKLTCAAZYjAIABm4uA
Date: Thu, 8 May 2014 08:56:59 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE442FD@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com> <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com>
In-Reply-To: <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/L0keuQYsEtTnUeQK3WpWMr7ldeQ
Cc: dhcwg <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 08 May 2014 08:57:24 -0000

SGksIEppbm1laSwNCg0KSW4gdGhlIGNvbW1vbiBzY2VuYXJpbyB0aGF0IHdlIGV4cGVjdCwgdGhl
IGxlYXAgb2YgZmFpdGggbW9kZWwgaXMgbm90IGRlcGxveWVkIGluZGVwZW5kZW50LiBJbiB0aGUg
ZGVwbG95bWVudCBvZiBzZWN1cmUgREhDUHY2IHNlcnZlciwgdGhlIHNlcnZlciBzZXJ2ZXMgdGhy
ZWUgdHlwZXMgb2YgY2xpZW50czogMSkgZnVsbCBhdXRoZW50aWNhdGVkIGNsaWVudHMsIDIpIGNs
aWVudHMgdHJ1c3RlZCBieSBsZWFwIG9mIGZhaXRoIG1vZGVsLCAzKSB1bi1hdXRoZW50aWNhdGVk
IGNsaWVudHMuIEhlbmNlLCB0aGUgY2xpZW50cyBhcmUgaW4gZGlmZmVyZW50IGNsYXNzIGZvciBs
aW1pdGVkIHJlc291cmNlIGFzc2lnbm1lbnQgYW5kIGFjY2VzcyBwcmlvcml0eS4gSXQgcHJvdmlk
ZXMgZmluZS1ncmFpbmVkIGNsaWVudCBtYW5hZ2VtZW50Lg0KDQpSZWdhcmRzLA0KDQpTaGVuZyAr
IERhY2hlbmcNCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogamlubWVpLnRh
dHV5YUBnbWFpbC5jb20gW21haWx0bzpqaW5tZWkudGF0dXlhQGdtYWlsLmNvbV0gT24gQmVoYWxm
DQo+T2Yg56We5piO6YGU5ZOJDQo+U2VudDogV2VkbmVzZGF5LCBNYXkgMDcsIDIwMTQgMTE6MzUg
UE0NCj5UbzogU2hlbmcgSmlhbmcNCj5DYzogVG9tZWsgTXJ1Z2Fsc2tpOyBkaGN3Zw0KPlN1Ympl
Y3Q6IFJlOiBbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhjLXNlZGhjcHY2LTAyIC0gUmVz
cG9uZCBieSBNYXkNCj4xOA0KPg0KPkF0IFR1ZSwgNiBNYXkgMjAxNCAwNzozNjozNCArMDAwMCwN
Cj5TaGVuZyBKaWFuZyA8amlhbmdzaGVuZ0BodWF3ZWkuY29tPiB3cm90ZToNCj4NCj4+ID4tIElu
IFNlY3Rpb24gNi4yOg0KPj4gPg0KPj4gPiAgIE9uIHRoZSByZWNpcGllbnQgdGhhdCBzdXBwb3J0
cyB0aGUgbGVhcCBvZiBmYWl0aCBtb2RlbCwgdGhlIG51bWJlciBvZg0KPj4gPiAgIGNhY2hlZCBw
dWJsaWMga2V5cyBvciB1bnZlcmlmaWFibGUgY2VydGlmaWNhdGVzIE1VU1QgYmUgbGltaXRlZCBp
bg0KPj4gPiAgIG9yZGVyIHRvIHByb3RlY3QgYWdhaW5zdCByZXNvdXJjZSBleGhhdXN0aW9uIGF0
dGFja3MuICBJZiB0aGUNCj4+ID4NCj4+ID4gIFRoaXMgaXMgbWFpbmx5IGNvbmNlcm5lZCBhYm91
dCBzZXJ2ZXJzLCBjb3JyZWN0PyAgSWYgc28sIEknbSBub3QNCj4+ID4gIHN1cmUgaG93IHNldmVy
ZSB0aGlzICJhdHRhY2tzIiBhcmU7IERIQ1Agc2VydmVycyBnZW5lcmFsbHkgbmVlZCB0bw0KPj4g
PiAgbWFpbnRhaW4gc29tZSBzdGF0ZSBmb3IgZWFjaCBjbGllbnQgKHVubGVzcyB0aGF0J3Mgc3Rh
dGVsZXNzIG9ubHkNCj4+ID4gIHNlcnZlcikgYW5kIHdvdWxkIG5hdHVyYWxseSBhbHJlYWR5IGhh
dmUgc29tZSBsaW1pdGF0aW9uIG9uIHRoYXQNCj4+ID4gIHJlc291cmNlLiAgU2hvdWxkbid0IHRo
ZSBnZW5lcmFsIGRlZmVuc2UgYmUgZW5vdWdoIGZvciB0aGlzDQo+PiA+ICBwYXJ0aWN1bGFyIHJl
c291cmNlLCB0b28/DQo+Pg0KPj4gVGhlICJNVVNUIiBoZXJlIHNlZW1zIG5vdCBwcm9wZXIuIExl
dCB1cyByZXBsYWNlIGlzIHdpdGggIk1BWSIuIEl0IG1ha2VzDQo+dGhpcyBwb2ludCBvcHRpb25h
bCBhbmQgc2hvdWxkIGFkZHJlc3MgeW91ciBjb25jZXJuLg0KPg0KPkkgZG9uJ3QgdGhpbmsgbXkg
bWFpbiBwb2ludCBpcyBNVVNUIHZzIE1BWS4gIEl0J3MgYWJvdXQgYSBtb3JlDQo+Z2VuZXJhbCBw
b2ludCBvZiBhdXRoZW50aWNhdGluZyBtZXNzYWdlcyBmcm9tIGNsaWVudHMgdG8gc2VydmVyczoN
Cj4NCj4tIHdoZXRoZXIgd2UgcmVhbGx5IG5lZWQgKHB1YmxpYyBrZXkpIGF1dGhlbnRpY2F0aW9u
IGluIHRoYXQNCj4gIGRpcmVjdGlvbiwgYW5kIGlmIHdlIGRvLCB3aHkNCj4NCj4tIGFsc28gaWYg
d2UgZG8sIHdoYXQncyB0aGUgY29tbW9ubHkgZXhwZWN0ZWQgbW9kZWwgb2YgInRydXN0IGFuY2hv
ciI6DQo+ICBsZWFwIG9mIGZhaXRoIG9yIHVzZSBvZiBDQSBvciBzb21ldGhpbmcgZWxzZSwgYW5k
IGlmIGl0J3MgbW9yZQ0KPiAgbGlrZWx5IHRvIGJlIGEgd2Vha2VyIG1vZGVsIGxpa2UgbGVhcCBv
ZiBmYWl0aCAoSSBzdXNwZWN0IHNvLCBmb3INCj4gIHRoZSBkaXJlY3Rpb24gb2YgY2xpZW50cyB0
byBzZXJ2ZXJzKSwgd2hldGhlciB0aGUgbW90aXZhdGlvbiAoMXN0DQo+ICBidWxsZXQpIGlzIHdv
cnRoIHRoZSB3ZWFrZXIgc2VjdXJpdHkNCj4NCj4tIGFuZCwgaWYgaXQncyBtb3JlIGxpa2VseSB0
byByZWx5IG9uIGxlYXAgb2YgZmFpdGgsIHdoYXQga2luZCBvZg0KPiAgY29uc2lkZXJhdGlvbiBp
cyBuZWVkZWQNCj4NCj5UaGUgZGlzY3Vzc2lvbiBvbiBjYWNoaW5nIHRoZSBwdWJsaWMga2V5cyBp
cyBqdXN0IGEgcGFydCBvZiB0aGUgdGhpcmQNCj5idWxsZXQuICBXaGF0IEknbSBtaXNzaW5nIGlu
IHRoZSBjdXJyZW50IGRyYWZ0IGlzIG1vcmUgY29tcHJlaGVuc2l2ZQ0KPmFuZCBoaWdoZXIgbGV2
ZWwgZGlzY3Vzc2lvbnMgb24gYWxsIG9mIHRoZXNlIHBvaW50cy4gIEl0J3MgZmFyIGZyb20NCj5v
YnZpb3VzIHRvIG1lIGNvbXBhcmVkIHRvIGF1dGhlbnRpY2F0aW5nIG1lc3NhZ2VzIGZyb20gc2Vy
dmVycyB0bw0KPmNsaWVudHMuDQo+DQo+LS0NCj5KSU5NRUksIFRhdHV5YQ0K


From nobody Thu May  8 09:24:35 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 267F31A0066 for <dhcwg@ietfa.amsl.com>; Thu,  8 May 2014 09:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0d1MKR09FGdp for <dhcwg@ietfa.amsl.com>; Thu,  8 May 2014 09:24:29 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by ietfa.amsl.com (Postfix) with ESMTP id 112691A0052 for <dhcwg@ietf.org>; Thu,  8 May 2014 09:24:28 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id f8so3387117wiw.16 for <dhcwg@ietf.org>; Thu, 08 May 2014 09:24:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=BDdhA8fnQcaECzr1g29cRkGWDrvsuWlV6Ke6fPn/eIs=; b=ewSNsgnGvDkmOKWC86W3co/chz0klUghELoiv5SGu4WZ0X9Pd9ztCXXB5aTbmKoFmP F2dP5GFfPWjI6CwhiiB9keTzqJb+4qmSkquN110PSnGSaDY4grov+hy54sWbJULYHBba Y6YViR4lwii/DxCo9BFLjckUCIdDyGGVDAMF3GIw2KZW69sYn7e0sukL7xgFzTGzKjL8 hYiePToHeoElmc57e/3lAFLZQLLCRFjk6Epj5Oa+3vx+3+9ApBBUdsYbopdAjCzGlvKq kSA/iIG0Rh1VfRAJH5/B+2Tpu9rHZPcGg+1CL7UFEf7v7QIGQCi6Ic1aAEifqe9kS8G5 60kg==
MIME-Version: 1.0
X-Received: by 10.180.11.178 with SMTP id r18mr13865979wib.41.1399566264091; Thu, 08 May 2014 09:24:24 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.3.14 with HTTP; Thu, 8 May 2014 09:24:23 -0700 (PDT)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE442FD@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com> <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE442FD@nkgeml512-mbx.china.huawei.com>
Date: Thu, 8 May 2014 09:24:23 -0700
X-Google-Sender-Auth: x4ks-EN6rMC0SDu9BG6AMxN5YeY
Message-ID: <CAJE_bqc+Z8awb5773OLs8QtXuCRxYCWFRAKuQ9YP8anFwEQqsQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/SdTM91coKlcr1FAJlUrWaU_6K4E
Cc: dhcwg <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 08 May 2014 16:24:33 -0000

At Thu, 8 May 2014 08:56:59 +0000,
Sheng Jiang <jiangsheng@huawei.com> wrote:

> In the common scenario that we expect, the leap of faith model is
> not deployed independent. In the deployment of secure DHCPv6 server,
> the server serves three types of clients: 1) full authenticated
> clients, 2) clients trusted by leap of faith model, 3)
> un-authenticated clients. Hence, the clients are in different class
> for limited resource assignment and access priority. It provides
> fine-grained client management.

I'm afraid we're on different pages...the above explanation doesn't
answer my questions:

> >I don't think my main point is MUST vs MAY.  It's about a more
> >general point of authenticating messages from clients to servers:
> >
> >- whether we really need (public key) authentication in that
> >  direction, and if we do, why
> >
> >- also if we do, what's the commonly expected model of "trust anchor":
> >  leap of faith or use of CA or something else, and if it's more
> >  likely to be a weaker model like leap of faith (I suspect so, for
> >  the direction of clients to servers), whether the motivation (1st
> >  bullet) is worth the weaker security
> >
> >- and, if it's more likely to rely on leap of faith, what kind of
> >  consideration is needed

If this is because I was not clear enough, I have no idea how I can
clarify my questions further.  As I said in my very first comment on
the draft, I don't have a strong position on whether to advance the
draft, so I guess I should simply drop these points, especially if
others in the wg don't see these an issue.

--
JINMEI, Tatuya


From nobody Thu May  8 11:30:12 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 4B54A1A00BA for <dhcwg@ietfa.amsl.com>; Thu,  8 May 2014 11:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level: 
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651] 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 jjRivlVfD1C5 for <dhcwg@ietfa.amsl.com>; Thu,  8 May 2014 11:30:11 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id E4EAD1A00B2 for <dhcwg@ietf.org>; Thu,  8 May 2014 11:30:10 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A546D1B8219 for <dhcwg@ietf.org>; Thu,  8 May 2014 11:30:06 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 78E45190043; Thu,  8 May 2014 11:30:06 -0700 (PDT)
Received: from [172.19.131.142] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 8 May 2014 11:30:06 -0700
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAJE_bqc+Z8awb5773OLs8QtXuCRxYCWFRAKuQ9YP8anFwEQqsQ@mail.gmail.com>
Date: Thu, 8 May 2014 13:30:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <5D53E8BB-F692-4752-A1B2-9BB09747C58B@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com> <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE442FD@nkgeml512-mbx.china.huawei.com> <CAJE_bqc+Z8awb5773OLs8QtXuCRxYCWFRAKuQ9YP8anFwEQqsQ@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/4qcJhhaXfkFIfpaTwKjjNX0H92A
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 08 May 2014 18:30:12 -0000

On May 8, 2014, at 11:24 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
>>> - whether we really need (public key) authentication in that
>>> direction, and if we do, why

Public key authentication makes sense in both directions.   Servers may =
be configured to grant different access to clients that authenticate =
than to clients that don't.  Clients may have lists of servers that =
either are known to be legitimate, or that are known to have worked in =
the past (leap of faith).   Being able to discriminate between a good =
server and a rogue server using this mechanism is desirable.

>>> - also if we do, what's the commonly expected model of "trust =
anchor":
>>> leap of faith or use of CA or something else, and if it's more
>>> likely to be a weaker model like leap of faith (I suspect so, for
>>> the direction of clients to servers), whether the motivation (1st
>>> bullet) is worth the weaker security

This seems to be out of scope for the current document, which just =
specifies a mechanism for authenticating transactions given that a key =
is known.   It's possible that this needs to be stated more clearly.   =
The reason (IMHO) why it's out of scope is that there are a variety of =
mechanisms that might make sense and that could be implemented.   For =
instance, a DHCP server might give an unknown client an address in a =
walled garden where it could arrange to pay for service, and then its =
key would be known to the DHCP server and could be used to authenticate =
service in the future without requiring registration.

>>> - and, if it's more likely to rely on leap of faith, what kind of
>>> consideration is needed

You mean in terms of risk assessments?


From nobody Thu May  8 17:08:56 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 687331A01D6; Thu,  8 May 2014 17:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level: 
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-NQxvzSdef1; Thu,  8 May 2014 17:08:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9571A01CF; Thu,  8 May 2014 17:08:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D93871801A4; Thu,  8 May 2014 17:08:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140509000809.D93871801A4@rfc-editor.org>
Date: Thu,  8 May 2014 17:08:09 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/K092Vrfsn9u9_kAmCCVpAQ6ZLTc
Cc: drafts-update-ref@iana.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [dhcwg] BCP 187, RFC 7227 on Guidelines for Creating New DHCPv6 Options
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, 09 May 2014 00:08:54 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 187        
        RFC 7227

        Title:      Guidelines for Creating New DHCPv6 
                    Options 
        Author:     D. Hankins, T. Mrugalski,
                    M. Siodelski, S. Jiang,
                    S. Krishnan
        Status:     Best Current Practice
        Stream:     IETF
        Date:       May 2014
        Mailbox:    dhankins@google.com, 
                    tomasz.mrugalski@gmail.com, 
                    msiodelski@gmail.com,
                    jiangsheng@huawei.com, 
                    suresh.krishnan@ericsson.com
        Pages:      35
        Characters: 83694
        Updates:    RFC 3315
        See Also:   BCP 187

        I-D Tag:    draft-ietf-dhc-option-guidelines-17.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7227.txt

This document provides guidance to prospective DHCPv6 option
developers to help them create option formats that are easily
adoptable by existing DHCPv6 software.  It also provides guidelines
for expert reviewers to evaluate new registrations.  This document
updates RFC 3315.

This document is a product of the Dynamic Host Configuration Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Thu May  8 19:54:14 2014
Return-Path: <liuzilong8266@163.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7621A0135 for <dhcwg@ietfa.amsl.com>; Thu,  8 May 2014 19:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.347
X-Spam-Level: **
X-Spam-Status: No, score=2.347 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RELAY_IS_220=2.118, RP_MATCHES_RCVD=-0.651, 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 7JoD8eRsitpB for <dhcwg@ietfa.amsl.com>; Thu,  8 May 2014 19:54:11 -0700 (PDT)
Received: from m13-240.163.com (m13-240.163.com [220.181.13.240]) by ietfa.amsl.com (Postfix) with ESMTP id 81A0F1A0149 for <dhcwg@ietf.org>; Thu,  8 May 2014 19:54:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Message-ID:Subject:MIME-Version; bh=Vcjd6 0N+33Jq48rJqiQmcbVVMulYRD1f67qXfwQDKpQ=; b=cJLjL8bFOTYa01oiTxOho HSD/v1vNm2FEpWExCXQFoqW06RhqnJBYtNKwkbsyIO3uglmBYSB/xH0X1ECNc0F1 Do4TdTHt97PKyZlA+VAUqimaW1Q8RiUi1eoK4dH+iYln06TABM2WfdcRcp1eeXnH L7e13pSQQCNpssnLf+C768=
Received: from liuzilong8266$163.com ( [166.111.68.231] ) by ajax-webmail-sdy6 (Coremail) ; Fri, 9 May 2014 10:53:57 +0800 (GMT+08:00)
Date: Fri, 9 May 2014 10:53:57 +0800
From: "liuzilong8266"<liuzilong8266@163.com>
To: "Tomek Mrugalski"<tomasz.mrugalski@gmail.com>
Message-ID: <689237c3.1d8e.145dee6c759.Coremail.liuzilong8266@163.com>
In-Reply-To: <535FEDAD.5010103@gmail.com>
References: <535FEDAD.5010103@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="__=_Part_Boundary_001_012945.022105"
X-Mailer: NetEase Flash Mail 2.4.0.11
X-Priority: 3 (Normal)
X-Originating-IP: [166.111.68.231]
X-CM-TRANSID: 58KowGA5K0JGQ2xTWAIbAA--.6918W
X-CM-SenderInfo: xolx6xporqwmqswwqiywtou0bp/1tbiVA+GmFEAISYYtQABs-
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Vw7rXItc1Yck_nsu71wVqjMmw4o
Cc: dhcwg <dhcwg@ietf.org>, sunqibupt <sunqibupt@gmail.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 09 May 2014 02:54:13 -0000

--__=_Part_Boundary_001_012945.022105
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

SGksYWxsDQogICBJIHN1cHBvcnQgYWR2YW5jaW5nIHRoaXMgZG9jdW1lbnQuIEFuZCBJIGFsc28g
aGF2ZSBzb21lIGNvbW1lbnRzIHRoYXQgbWF5IGhvcGVmdWxseSBiZSB1c2VmdWwsIHRob3VnaDoN
Cg0KLXNlY3Rpb24gNA0KIkluIG9yZGVyIHRvIGVuYWJsZSBhIERIQ1AgY2xpZW50IGFuZCBhIHNl
cnZlciBtdXR1YWxseSBhdXRoZW50aWNhdGUgZWFjaCBvdGhlciB3aXRob3V0IHByZXZpb3VzIGtl
eSBkZXBsb3ltZW50Ig0KICAgd2hhdCBkb2VzIGl0IG1lYW4gYnkgc2F5aW5nICJ3aXRob3V0IHBy
ZXZpb3VzIGtleSBkZXBsb3ltZW50Ij8gQXMgaXMgZGVzY3JpYmVkIGluIHRoZSBkcmFmdCwgcHVi
bGljL3ByaXZhdGUga2V5IGlzIHByZS1jb25maWd1cmVkLiBUaGlzIHN0YXRlbWVudCBzZWVtcyBj
b25mbGljdCBhZ2FpbnN0IHRoZSBwcmUtY29uZmlndXJhdGlvbiBvZiBwdWJsaWMvcHJpdmF0ZSBr
ZXk/IA0KDQoiSXQgaXMgcG9zc2libGUgZm9yIHRoZSBzYW1lIHB1YmxpYyBrZXkgdG8gYmUgdXNl
ZCB3aXRoIGRpZmZlcmVudCByZWNpcGllbnRzIGluIGJvdGggbW9kZXMuIg0KIHdoeSBkaWZmZXJl
bnQgcmVjaXBpZW50cyBjYW4gdXNlIHNhbWUgcHVibGljIGtleT8gSXMgaXQgc2VjdXJlPw0KDQpU
aGFua3MhDQoNCg0KMjAxNC0wNS0wOSANCg0KbGl1emlsb25nODI2NiANCg0KDQoNCuWPkeS7tuS6
uu+8mlRvbWVrIE1ydWdhbHNraSA8dG9tYXN6Lm1ydWdhbHNraUBnbWFpbC5jb20+DQrlj5HpgIHm
l7bpl7TvvJoyMDE0LTA0LTMwIDAyOjIxDQrkuLvpopjvvJpbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0
LWlldGYtZGhjLXNlZGhjcHY2LTAyIC0gUmVzcG9uZCBieSBNYXkgMTgNCuaUtuS7tuS6uu+8miJk
aGN3ZyI8ZGhjd2dAaWV0Zi5vcmc+DQrmioTpgIHvvJoNCg0KSGkgYWxsLCANCg0KVGhpcyBtZXNz
YWdlIHN0YXJ0cyBESEMgd29ya2luZyBncm91cCBsYXN0IGNhbGwgYWJvdXQgYWR2YW5jaW5nIFNl
Y3VyZSANCkRIQ1B2NiB3aXRoIFB1YmxpYyBLZXkgZG9jdW1lbnQgYXMgYSBTdGFuZGFyZHMgVHJh
Y2sgUkZDLiBUaGUgYXV0aG9ycyANCmJlbGlldmUgdGhhdCB0aGlzIHZlcnNpb24gYWRkcmVzc2Vk
IGFsbCB0aGUgaXNzdWVzIHJhaXNlZCBhbmQgaXMgcmVhZHkuIA0KDQpUaGUgZHJhZnQgaXMgYXZh
aWxhYmxlIGhlcmU6IA0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kaGMt
c2VkaGNwdjYtMDIgDQoNClNpbmNlIHdlIGhhdmUgdXBjb21pbmcgaG9saWRheSBvbiBNYXkgMXN0
ICh3aGljaCBoYXBwZW5zIHRvIGJlIGEgcmVhc29uIA0KZm9yIGV4dGVuZGVkIHdlZWtlbmQgaW4g
bWFueSBwYXJ0cyBvZiBFdXJvcGUpIGFuZCB0aGUgdG9waWMgaW4gcXVlc3Rpb24gDQppcyBub3Qg
dHJpdmlhbCwgdGhpcyBXR0xDIGlzIGEgYml0IGxvbmdlciB0aGFuIHVzdWFsLiANCg0KUGxlYXNl
IHNlbmQgeW91ciBjb21tZW50cyBieSBNYXkgMTh0aCAyMDE0LiBJZiB5b3UgZG8gbm90IGZlZWwg
dGhpcyANCmRvY3VtZW50IHNob3VsZCBhZHZhbmNlLCBwbGVhc2Ugc3RhdGUgeW91ciByZWFzb25z
IHdoeS4gDQoNClRoZXJlIGFyZSBubyBJUFIgY2xhaW1zIHJlcG9ydGVkIGF0IHRoaXMgdGltZS4g
DQoNClRvbWVrIE1ydWdhbHNraSBpcyB0aGUgZG9jdW1lbnQgc2hlcGhlcmQuIA0KDQpCZXJuaWUg
JiBUb21layANCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18gDQpkaGN3ZyBtYWlsaW5nIGxpc3QgDQpkaGN3Z0BpZXRmLm9yZyANCmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhjd2cg
--__=_Part_Boundary_001_012945.022105
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0
Zi04IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT48IS0tIGZsYXNobWFpbCBzdHlsZSBiZWdpbiAt
LT4NCjxTVFlMRSB0eXBlPXRleHQvY3NzPgpib2R5IHtib3JkZXItd2lkdGg6MDttYXJnaW46MH0K
aW1nIHtib3JkZXI6MDttYXJnaW46MDtwYWRkaW5nOjB9CjwvU1RZTEU+DQo8QkFTRSB0YXJnZXQ9
X2JsYW5rPjwhLS0gZmxhc2htYWlsIHN0eWxlIGVuZCAtLT4NCjxNRVRBIG5hbWU9R0VORVJBVE9S
IGNvbnRlbnQ9Ik1TSFRNTCAxMS4wMC45NjAwLjE3MTA1Ij48L0hFQUQ+DQo8Qk9EWSANCnN0eWxl
PSJCT1JERVItTEVGVC1XSURUSDogMHB4OyBGT05ULVNJWkU6IDEwLjVwdDsgRk9OVC1GQU1JTFk6
IOW+rui9r+mbhem7kTsgQk9SREVSLVJJR0hULVdJRFRIOiAwcHg7IEJPUkRFUi1CT1RUT00tV0lE
VEg6IDBweDsgQ09MT1I6ICMwMDAwMDA7IE1BUkdJTjogMTJweDsgTElORS1IRUlHSFQ6IDEuNTsg
Qk9SREVSLVRPUC1XSURUSDogMHB4IiANCm1hcmdpbmhlaWdodD0iMCIgbWFyZ2lud2lkdGg9IjAi
Pg0KPERJViANCnN0eWxlPSJXSElURS1TUEFDRTogbm9ybWFsOyBXT1JELVNQQUNJTkc6IDBweDsg
VEVYVC1UUkFOU0ZPUk06IG5vbmU7IENPTE9SOiByZ2IoMCwwLDE3KTsgRk9OVDogMTIuMXB0LzEu
MyDlrovkvZMsIHNlcmlmOyBMRVRURVItU1BBQ0lORzogbm9ybWFsOyAtd2Via2l0LXRleHQtc3Ry
b2tlLXdpZHRoOiAwcHgiPjxGT05UIA0Kc2l6ZT0zIGZhY2U95a6L5L2TPkhpLGFsbDwvRk9OVD48
L0RJVj4NCjxESVYgDQpzdHlsZT0iV0hJVEUtU1BBQ0U6IG5vcm1hbDsgV09SRC1TUEFDSU5HOiAw
cHg7IFRFWFQtVFJBTlNGT1JNOiBub25lOyBDT0xPUjogcmdiKDAsMCwxNyk7IEZPTlQ6IDEyLjFw
dC8xLjMg5a6L5L2TLCBzZXJpZjsgTEVUVEVSLVNQQUNJTkc6IG5vcm1hbDsgLXdlYmtpdC10ZXh0
LXN0cm9rZS13aWR0aDogMHB4Ij48Rk9OVCANCnNpemU9Mz4mbmJzcDsmbmJzcDsgSSBzdXBwb3J0
IGFkdmFuY2luZyB0aGlzIGRvY3VtZW50LiBBbmQgSSBhbHNvIGhhdmUgc29tZSANCmNvbW1lbnRz
IHRoYXQgbWF5IGhvcGVmdWxseSBiZSB1c2VmdWwsIHRob3VnaDo8L0ZPTlQ+PC9ESVY+DQo8RElW
IA0Kc3R5bGU9IldISVRFLVNQQUNFOiBub3JtYWw7IFdPUkQtU1BBQ0lORzogMHB4OyBURVhULVRS
QU5TRk9STTogbm9uZTsgQ09MT1I6IHJnYigwLDAsMTcpOyBGT05UOiAxMi4xcHQvMS4zIOWui+S9
kywgc2VyaWY7IExFVFRFUi1TUEFDSU5HOiBub3JtYWw7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lk
dGg6IDBweCI+PEZPTlQgDQpzaXplPTM+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJViANCnN0eWxl
PSJXSElURS1TUEFDRTogbm9ybWFsOyBXT1JELVNQQUNJTkc6IDBweDsgVEVYVC1UUkFOU0ZPUk06
IG5vbmU7IENPTE9SOiByZ2IoMCwwLDE3KTsgRk9OVDogMTIuMXB0LzEuMyDlrovkvZMsIHNlcmlm
OyBMRVRURVItU1BBQ0lORzogbm9ybWFsOyAtd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHgi
PjxGT05UIA0Kc2l6ZT0zPi1zZWN0aW9uIDQ8L0ZPTlQ+PC9ESVY+DQo8RElWIA0Kc3R5bGU9IldI
SVRFLVNQQUNFOiBub3JtYWw7IFdPUkQtU1BBQ0lORzogMHB4OyBURVhULVRSQU5TRk9STTogbm9u
ZTsgQ09MT1I6IHJnYigwLDAsMTcpOyBGT05UOiAxMi4xcHQvMS4zIOWui+S9kywgc2VyaWY7IExF
VFRFUi1TUEFDSU5HOiBub3JtYWw7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweCI+PEZP
TlQgDQpzaXplPTM+IkluIG9yZGVyIHRvIGVuYWJsZSBhIERIQ1AgY2xpZW50IGFuZCBhIHNlcnZl
ciBtdXR1YWxseSBhdXRoZW50aWNhdGUgZWFjaCANCm90aGVyIHdpdGhvdXQgcHJldmlvdXMga2V5
IGRlcGxveW1lbnQiPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCANCnN0eWxlPSJXSElURS1TUEFD
RTogbm9ybWFsOyBXT1JELVNQQUNJTkc6IDBweDsgVEVYVC1UUkFOU0ZPUk06IG5vbmU7IENPTE9S
OiByZ2IoMCwwLDE3KTsgRk9OVDogMTIuMXB0LzEuMyDlrovkvZMsIHNlcmlmOyBMRVRURVItU1BB
Q0lORzogbm9ybWFsOyAtd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHgiIA0Kc2l6ZT0zPiZu
YnNwOyZuYnNwOyB3aGF0IGRvZXMgaXQgbWVhbiBieSBzYXlpbmcgIndpdGhvdXQgcHJldmlvdXMg
a2V5IA0KZGVwbG95bWVudCI/IEFzIGlzIGRlc2NyaWJlZCBpbiB0aGUgZHJhZnQsIHB1YmxpYy9w
cml2YXRlIGtleSBpcyBwcmUtY29uZmlndXJlZC4gDQpUaGlzIHN0YXRlbWVudCBzZWVtcyZuYnNw
OzwvRk9OVD48Rk9OVCBjb2xvcj0jMDAwMDExIHNpemU9MyANCmZhY2U9IuWui+S9kywgc2VyaWYi
PjxTUEFOIHN0eWxlPSJMSU5FLUhFSUdIVDogMjBweCI+Y29uZmxpY3QgYWdhaW5zdCB0aGUgDQpw
cmUtY29uZmlndXJhdGlvbiBvZiZuYnNwO3B1YmxpYy9wcml2YXRlIA0Ka2V5PyZuYnNwOzwvU1BB
Tj48L0ZPTlQ+PC9ESVY+PC9TVEFUSU9ORVJZPg0KPEJMT0NLUVVPVEUgdHlwZT0iY2l0ZSI+PFNU
QVRJT05FUlk+PC9CTE9DS1FVT1RFPg0KPERJViANCnN0eWxlPSJCT1JERVItTEVGVC1XSURUSDog
MHB4OyBCT1JERVItUklHSFQtV0lEVEg6IDBweDsgV0hJVEUtU1BBQ0U6IG5vcm1hbDsgQk9SREVS
LUJPVFRPTS1XSURUSDogMHB4OyBXT1JELVNQQUNJTkc6IDBweDsgVEVYVC1UUkFOU0ZPUk06IG5v
bmU7IENPTE9SOiByZ2IoMCwwLDE3KTsgRk9OVDogMTIuMXB0LzEuMyDlrovkvZMsIHNlcmlmOyBN
QVJHSU46IDEycHg7IExFVFRFUi1TUEFDSU5HOiBub3JtYWw7IEJPUkRFUi1UT1AtV0lEVEg6IDBw
eDsgVEVYVC1JTkRFTlQ6IDBweDsgLXdlYmtpdC10ZXh0LXN0cm9rZS13aWR0aDogMHB4IiANCm1h
cmdpbmhlaWdodD0iMCIgbWFyZ2lud2lkdGg9IjAiPjxGT05UIHNpemU9Mz48L0ZPTlQ+PEZPTlQg
c2l6ZT0zPiJJdCBpcyANCnBvc3NpYmxlIGZvciB0aGUgc2FtZSBwdWJsaWMga2V5IHRvIGJlIHVz
ZWQgd2l0aCBkaWZmZXJlbnQgcmVjaXBpZW50cyBpbiBib3RoIA0KbW9kZXMuIjwvRk9OVD48L0RJ
Vj4NCjxESVYgDQpzdHlsZT0iQk9SREVSLUxFRlQtV0lEVEg6IDBweDsgQk9SREVSLVJJR0hULVdJ
RFRIOiAwcHg7IFdISVRFLVNQQUNFOiBub3JtYWw7IEJPUkRFUi1CT1RUT00tV0lEVEg6IDBweDsg
V09SRC1TUEFDSU5HOiAwcHg7IFRFWFQtVFJBTlNGT1JNOiBub25lOyBDT0xPUjogcmdiKDAsMCwx
Nyk7IEZPTlQ6IDEyLjFwdC8xLjMg5a6L5L2TLCBzZXJpZjsgTUFSR0lOOiAxMnB4OyBMRVRURVIt
U1BBQ0lORzogbm9ybWFsOyBCT1JERVItVE9QLVdJRFRIOiAwcHg7IFRFWFQtSU5ERU5UOiAwcHg7
IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweCIgDQptYXJnaW5oZWlnaHQ9IjAiIG1hcmdp
bndpZHRoPSIwIj48Rk9OVCBzaXplPTM+Jm5ic3A7d2h5IGRpZmZlcmVudCByZWNpcGllbnRzIGNh
biANCnVzZSBzYW1lIHB1YmxpYyBrZXk/IElzIGl0IHNlY3VyZT88L0ZPTlQ+PC9ESVY+DQo8RElW
IA0Kc3R5bGU9IkJPUkRFUi1MRUZULVdJRFRIOiAwcHg7IEJPUkRFUi1SSUdIVC1XSURUSDogMHB4
OyBXSElURS1TUEFDRTogbm9ybWFsOyBCT1JERVItQk9UVE9NLVdJRFRIOiAwcHg7IFdPUkQtU1BB
Q0lORzogMHB4OyBURVhULVRSQU5TRk9STTogbm9uZTsgQ09MT1I6IHJnYigwLDAsMTcpOyBGT05U
OiAxMi4xcHQvMS4zIOWui+S9kywgc2VyaWY7IE1BUkdJTjogMTJweDsgTEVUVEVSLVNQQUNJTkc6
IG5vcm1hbDsgQk9SREVSLVRPUC1XSURUSDogMHB4OyBURVhULUlOREVOVDogMHB4OyAtd2Via2l0
LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHgiIA0KbWFyZ2luaGVpZ2h0PSIwIiBtYXJnaW53aWR0aD0i
MCI+PEZPTlQgc2l6ZT0zPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVYgDQpzdHlsZT0iQk9SREVS
LUxFRlQtV0lEVEg6IDBweDsgQk9SREVSLVJJR0hULVdJRFRIOiAwcHg7IFdISVRFLVNQQUNFOiBu
b3JtYWw7IEJPUkRFUi1CT1RUT00tV0lEVEg6IDBweDsgV09SRC1TUEFDSU5HOiAwcHg7IFRFWFQt
VFJBTlNGT1JNOiBub25lOyBDT0xPUjogcmdiKDAsMCwxNyk7IEZPTlQ6IDEyLjFwdC8xLjMg5a6L
5L2TLCBzZXJpZjsgTUFSR0lOOiAxMnB4OyBMRVRURVItU1BBQ0lORzogbm9ybWFsOyBCT1JERVIt
VE9QLVdJRFRIOiAwcHg7IFRFWFQtSU5ERU5UOiAwcHg7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lk
dGg6IDBweCIgDQptYXJnaW5oZWlnaHQ9IjAiIG1hcmdpbndpZHRoPSIwIj48Rk9OVCBzaXplPTM+
VGhhbmtzITwvRk9OVD48L0RJVj4NCjxESVYgDQpzdHlsZT0iQk9SREVSLUxFRlQtV0lEVEg6IDBw
eDsgQk9SREVSLVJJR0hULVdJRFRIOiAwcHg7IFdISVRFLVNQQUNFOiBub3JtYWw7IEJPUkRFUi1C
T1RUT00tV0lEVEg6IDBweDsgV09SRC1TUEFDSU5HOiAwcHg7IFRFWFQtVFJBTlNGT1JNOiBub25l
OyBDT0xPUjogcmdiKDAsMCwxNyk7IEZPTlQ6IDEyLjFwdC8xLjMg5a6L5L2TLCBzZXJpZjsgTUFS
R0lOOiAxMnB4OyBMRVRURVItU1BBQ0lORzogbm9ybWFsOyBCT1JERVItVE9QLVdJRFRIOiAwcHg7
IFRFWFQtSU5ERU5UOiAwcHg7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweCIgDQptYXJn
aW5oZWlnaHQ9IjAiIG1hcmdpbndpZHRoPSIwIj4mbmJzcDs8L0RJVj48L1NUQVRJT05FUlk+DQo8
RElWPiZuYnNwOzwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlM
WTogVmVyZGFuYTsgQ09MT1I6ICNjMGMwYzAiIA0KYWxpZ249bGVmdD4yMDE0LTA1LTA5IA0KPEhS
IGlkPVNpZ25OYW1lSFIgDQpzdHlsZT0iQk9SREVSLVRPUDogI2MwYzBjMCAxcHggc29saWQ7IEhF
SUdIVDogMXB4OyBCT1JERVItUklHSFQ6IDBweDsgV0lEVEg6IDEyMnB4OyBCT1JERVItQk9UVE9N
OiAwcHg7IEJPUkRFUi1MRUZUOiAwcHgiIA0KYWxpZ249bGVmdD4NCjxTUEFOIGlkPV9GbGFzaFNp
Z25OYW1lPmxpdXppbG9uZzgyNjY8L1NQQU4+IDwvRElWPg0KPEhSIA0Kc3R5bGU9IkJPUkRFUi1U
T1A6ICNjMGMwYzAgMXB4IHNvbGlkOyBIRUlHSFQ6IDFweDsgQk9SREVSLVJJR0hUOiAwcHg7IEJP
UkRFUi1CT1RUT006IDBweDsgQk9SREVSLUxFRlQ6IDBweCI+DQoNCjxESVYgc3R5bGU9IkZPTlQt
U0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IFZlcmRhbmEiPg0KPERJVj48U1RST05HPuWPkeS7tuS6
uu+8mjwvU1RST05HPlRvbWVrIE1ydWdhbHNraSANCiZsdDt0b21hc3oubXJ1Z2Fsc2tpQGdtYWls
LmNvbSZndDs8L0RJVj4NCjxESVY+PFNUUk9ORz7lj5HpgIHml7bpl7TvvJo8L1NUUk9ORz4yMDE0
LTA0LTMwJm5ic3A7MDI6MjE8L0RJVj4NCjxESVY+PFNUUk9ORz7kuLvpopjvvJo8L1NUUk9ORz5b
ZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhjLXNlZGhjcHY2LTAyIC0gUmVzcG9uZCANCmJ5
IE1heSAxODwvRElWPg0KPERJVj48U1RST05HPuaUtuS7tuS6uu+8mjwvU1RST05HPiJkaGN3ZyIm
bHQ7ZGhjd2dAaWV0Zi5vcmcmZ3Q7PC9ESVY+DQo8RElWPjxTVFJPTkc+5oqE6YCB77yaPC9TVFJP
Tkc+PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj4NCjxESVY+SGkmbmJzcDthbGwsJm5i
c3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5UaGlzJm5ic3A7bWVzc2FnZSZuYnNw
O3N0YXJ0cyZuYnNwO0RIQyZuYnNwO3dvcmtpbmcmbmJzcDtncm91cCZuYnNwO2xhc3QmbmJzcDtj
YWxsJm5ic3A7YWJvdXQmbmJzcDthZHZhbmNpbmcmbmJzcDtTZWN1cmUmbmJzcDs8L0RJVj4NCjxE
SVY+REhDUHY2Jm5ic3A7d2l0aCZuYnNwO1B1YmxpYyZuYnNwO0tleSZuYnNwO2RvY3VtZW50Jm5i
c3A7YXMmbmJzcDthJm5ic3A7U3RhbmRhcmRzJm5ic3A7VHJhY2smbmJzcDtSRkMuJm5ic3A7VGhl
Jm5ic3A7YXV0aG9ycyZuYnNwOzwvRElWPg0KPERJVj5iZWxpZXZlJm5ic3A7dGhhdCZuYnNwO3Ro
aXMmbmJzcDt2ZXJzaW9uJm5ic3A7YWRkcmVzc2VkJm5ic3A7YWxsJm5ic3A7dGhlJm5ic3A7aXNz
dWVzJm5ic3A7cmFpc2VkJm5ic3A7YW5kJm5ic3A7aXMmbmJzcDtyZWFkeS4mbmJzcDs8L0RJVj4N
CjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPlRoZSZuYnNwO2RyYWZ0Jm5ic3A7aXMmbmJzcDthdmFp
bGFibGUmbmJzcDtoZXJlOiZuYnNwOzwvRElWPg0KPERJVj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9kcmFmdC1pZXRmLWRoYy1zZWRoY3B2Ni0wMiZuYnNwOzwvRElWPg0KPERJVj4mbmJzcDs8
L0RJVj4NCjxESVY+U2luY2UmbmJzcDt3ZSZuYnNwO2hhdmUmbmJzcDt1cGNvbWluZyZuYnNwO2hv
bGlkYXkmbmJzcDtvbiZuYnNwO01heSZuYnNwOzFzdCZuYnNwOyh3aGljaCZuYnNwO2hhcHBlbnMm
bmJzcDt0byZuYnNwO2JlJm5ic3A7YSZuYnNwO3JlYXNvbiZuYnNwOzwvRElWPg0KPERJVj5mb3Im
bmJzcDtleHRlbmRlZCZuYnNwO3dlZWtlbmQmbmJzcDtpbiZuYnNwO21hbnkmbmJzcDtwYXJ0cyZu
YnNwO29mJm5ic3A7RXVyb3BlKSZuYnNwO2FuZCZuYnNwO3RoZSZuYnNwO3RvcGljJm5ic3A7aW4m
bmJzcDtxdWVzdGlvbiZuYnNwOzwvRElWPg0KPERJVj5pcyZuYnNwO25vdCZuYnNwO3RyaXZpYWws
Jm5ic3A7dGhpcyZuYnNwO1dHTEMmbmJzcDtpcyZuYnNwO2EmbmJzcDtiaXQmbmJzcDtsb25nZXIm
bmJzcDt0aGFuJm5ic3A7dXN1YWwuJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJ
Vj5QbGVhc2UmbmJzcDtzZW5kJm5ic3A7eW91ciZuYnNwO2NvbW1lbnRzJm5ic3A7YnkmbmJzcDtN
YXkmbmJzcDsxOHRoJm5ic3A7MjAxNC4mbmJzcDtJZiZuYnNwO3lvdSZuYnNwO2RvJm5ic3A7bm90
Jm5ic3A7ZmVlbCZuYnNwO3RoaXMmbmJzcDs8L0RJVj4NCjxESVY+ZG9jdW1lbnQmbmJzcDtzaG91
bGQmbmJzcDthZHZhbmNlLCZuYnNwO3BsZWFzZSZuYnNwO3N0YXRlJm5ic3A7eW91ciZuYnNwO3Jl
YXNvbnMmbmJzcDt3aHkuJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5UaGVy
ZSZuYnNwO2FyZSZuYnNwO25vJm5ic3A7SVBSJm5ic3A7Y2xhaW1zJm5ic3A7cmVwb3J0ZWQmbmJz
cDthdCZuYnNwO3RoaXMmbmJzcDt0aW1lLiZuYnNwOzwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4N
CjxESVY+VG9tZWsmbmJzcDtNcnVnYWxza2kmbmJzcDtpcyZuYnNwO3RoZSZuYnNwO2RvY3VtZW50
Jm5ic3A7c2hlcGhlcmQuJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5CZXJu
aWUmbmJzcDsmYW1wOyZuYnNwO1RvbWVrJm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0K
PERJVj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXyZuYnNw
OzwvRElWPg0KPERJVj5kaGN3ZyZuYnNwO21haWxpbmcmbmJzcDtsaXN0Jm5ic3A7PC9ESVY+DQo8
RElWPmRoY3dnQGlldGYub3JnJm5ic3A7PC9ESVY+DQo8RElWPmh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vZGhjd2cmbmJzcDs8L0RJVj48L0RJVj48L0RJVj48L0JPRFk+PC9I
VE1MPg==
--__=_Part_Boundary_001_012945.022105--


From nobody Fri May  9 11:39:39 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 64D5F1A0099 for <dhcwg@ietfa.amsl.com>; Fri,  9 May 2014 11:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqBPMOm2XQaW for <dhcwg@ietfa.amsl.com>; Fri,  9 May 2014 11:39:35 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA541A00B0 for <dhcwg@ietf.org>; Fri,  9 May 2014 11:39:34 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id r20so1787289wiv.3 for <dhcwg@ietf.org>; Fri, 09 May 2014 11:39:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=XtA6z8W6tOZxjDlSskkFZ6krq13SXo5UobxBagpWUTc=; b=aLc74oQCtJSeJTnr7IhNcoC9CTaqKVzxn6MhNsTihct5x7blrbxgo0ZIzMzZlb98Mj LXFGj+fmLr6mHdONz8LN1vIYF41KkJZs7qtTucPiAykL58zdGpSCsi0HcM/606XXJF/x nTn31o8pYiMZKFPjhRSXWAsDDZjLQlHPJAR2pj/74ph58YSQccFCXGfPXKaPyYOFYHmf AFq/c5PQkMgkvcjaN8Q70it6EhntuNDrqoayFMCcnSOOJShwfRw3NeYKzVMZ71EAuEhc xXKKlc2AaMFbobfZvudFGTlgo3CM/4SVzP+FSUnAOoitpUePrexKYL3VTN0ZKCQQk2au j1yg==
MIME-Version: 1.0
X-Received: by 10.194.242.66 with SMTP id wo2mr4509730wjc.37.1399660769615; Fri, 09 May 2014 11:39:29 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.95.5 with HTTP; Fri, 9 May 2014 11:39:29 -0700 (PDT)
In-Reply-To: <5D53E8BB-F692-4752-A1B2-9BB09747C58B@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com> <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE442FD@nkgeml512-mbx.china.huawei.com> <CAJE_bqc+Z8awb5773OLs8QtXuCRxYCWFRAKuQ9YP8anFwEQqsQ@mail.gmail.com> <5D53E8BB-F692-4752-A1B2-9BB09747C58B@nominum.com>
Date: Fri, 9 May 2014 11:39:29 -0700
X-Google-Sender-Auth: YYKB-IegiNyXF57h-kGpZIbTKlE
Message-ID: <CAJE_bqeNNW1=dSnj4f=t7Fx9waG81cDeHdcikqk0ECUoLvgVzQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/oOkimr5FqmtS1dHVnRxw5pYO4GA
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 09 May 2014 18:39:36 -0000

At Thu, 8 May 2014 13:30:01 -0500,
Ted Lemon <ted.lemon@nominum.com> wrote:

> >>> - whether we really need (public key) authentication in that
> >>> direction, and if we do, why
>
> Public key authentication makes sense in both directions.   Servers
> may be configured to grant different access to clients that
> authenticate than to clients that don't.  Clients may have lists of

Okay, I can see that usage.

> servers that either are known to be legitimate, or that are known to
> have worked in the past (leap of faith).   Being able to
> discriminate between a good server and a rogue server using this
> mechanism is desirable.

I have no problem with this either.

My main concern is the combination of authenticating clients with the
leap of faith model.  This model isn't suitable for the "grant
different access" usage, since anyone can pretend to be an
authenticated client with that model.

> >>> - also if we do, what's the commonly expected model of "trust anchor"=
:
> >>> leap of faith or use of CA or something else, and if it's more
> >>> likely to be a weaker model like leap of faith (I suspect so, for
> >>> the direction of clients to servers), whether the motivation (1st
> >>> bullet) is worth the weaker security
>
> This seems to be out of scope for the current document, which just specif=
ies a mechanism for authenticating transactions given that a key is known. =
  It's possible that this needs to be stated more clearly.   The reason (IM=
HO) why it's out of scope is that there are a variety of mechanisms that mi=
ght make sense and that could be implemented.

I'm okay with separating such discussions outside of this document.
But then I'd personally like to see a "threat analysis" document
first (covering these points), not the other way around.  As a
believer of the YAGNI principle, I personally cannot be so
enthusiastic about defining/implementing something that just *might*
make sense somewhere.  Especially so, if we need to worry about a
security impact as mentioned in the security considerations section of
the draft.

> For instance, a DHCP server might give an unknown client an address in a =
walled garden where it could arrange to pay for service, and then its key w=
ould be known to the DHCP server and could be used to authenticate service =
in the future without requiring registration.

I'm impressed with your imagination:-) Although I'm not sure if this
example is persuasive enough, I see we can come up with some
*possible* usage of client authentication with leap of faith.

> >>> - and, if it's more likely to rely on leap of faith, what kind of
> >>> consideration is needed
>
> You mean in terms of risk assessments?

Considerations like the possibility of resource exhaustion attacks as
mentioned in Section 7 of the draft.

--
JINMEI, Tatuya


From nobody Fri May  9 15:45:26 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 3AD761A010C for <dhcwg@ietfa.amsl.com>; Fri,  9 May 2014 15:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level: 
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651] 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 dU3ySukHyAx6 for <dhcwg@ietfa.amsl.com>; Fri,  9 May 2014 15:45:22 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 7F5791A00F6 for <dhcwg@ietf.org>; Fri,  9 May 2014 15:45:22 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 727FB1B81C7 for <dhcwg@ietf.org>; Fri,  9 May 2014 15:45:09 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 4EBE6190043; Fri,  9 May 2014 15:45:09 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 9 May 2014 15:45:02 -0700
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAJE_bqeNNW1=dSnj4f=t7Fx9waG81cDeHdcikqk0ECUoLvgVzQ@mail.gmail.com>
Date: Fri, 9 May 2014 18:44:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <86DAC0E6-BC1A-4247-9AD1-C13DA01F170D@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com> <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE442FD@nkgeml512-mbx.china.huawei.com> <CAJE_bqc+Z8awb5773OLs8QtXuCRxYCWFRAKuQ9YP8anFwEQqsQ@mail.gmail.com> <5D53E8BB-F692-4752-A1B2-9BB09747C58B@nominum.com> <CAJE_bqeNNW1=dSnj4f=t7Fx9waG81cDeHdcikqk0ECUoLvgVzQ@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/4sqkSrhinnl-oskLv_kuVE9EXF4
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 09 May 2014 22:45:24 -0000

On May 9, 2014, at 2:39 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> My main concern is the combination of authenticating clients with the
> leap of faith model.  This model isn't suitable for the "grant
> different access" usage, since anyone can pretend to be an
> authenticated client with that model.

You are right--I don't think there is a use case for leap-of-faith with =
clients.

> I'm okay with separating such discussions outside of this document.
> But then I'd personally like to see a "threat analysis" document
> first (covering these points), not the other way around.  As a
> believer of the YAGNI principle, I personally cannot be so
> enthusiastic about defining/implementing something that just *might*
> make sense somewhere.  Especially so, if we need to worry about a
> security impact as mentioned in the security considerations section of
> the draft.

We are in the awkward situation that lots of DHCP people already know =
what the threat models are, although I think you are correct that they =
have not been clearly articulated in a threat analysis document.   I =
think such a document would be a good idea.   However, I'm reluctant to =
delay this document on that basis.   It might make sense to do so, but I =
will leave that up to the working group to debate.

> I'm impressed with your imagination:-) Although I'm not sure if this
> example is persuasive enough, I see we can come up with some
> *possible* usage of client authentication with leap of faith.

This is a pretty common use model, actually.   But nowadays we do it =
without authentication, using just the client identifier, or by forcing =
a captive portal login every session, which is really inconvenient.   I =
wouldn't describe this as leap-of-faith, however, since it relies on =
some out-of-band authentication mechanism to validate the client key =
before choosing to trust it.

>>>>> - and, if it's more likely to rely on leap of faith, what kind of
>>>>> consideration is needed
>>=20
>> You mean in terms of risk assessments?
>=20
> Considerations like the possibility of resource exhaustion attacks as
> mentioned in Section 7 of the draft.

Leap-of-faith typically involves some kind of act of faith before =
trusting a key.   E.g., with ssh, that's the user saying "yes, go =
ahead."   I don't think you could do a resource exhaustion attack in =
this situation.


From nobody Sat May 10 07:14:21 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 306F61A0255 for <dhcwg@ietfa.amsl.com>; Sat, 10 May 2014 07:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] 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 3qxUNte-MRdP for <dhcwg@ietfa.amsl.com>; Sat, 10 May 2014 07:14:18 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id EEE351A024A for <dhcwg@ietf.org>; Sat, 10 May 2014 07:14:17 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C2D1A1B81C7 for <dhcwg@ietf.org>; Sat, 10 May 2014 07:14:12 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A46D8190043 for <dhcwg@ietf.org>; Sat, 10 May 2014 07:14:12 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 10 May 2014 07:14:05 -0700
From: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CA7438CA-D64A-40CB-9B5B-A49E6E4C7202"
Date: Sat, 10 May 2014 10:14:03 -0400
References: <20140510061841.GA23600@laperouse.bortzmeyer.org>
To: dhcwg <dhcwg@ietf.org>
Message-ID: <76AD81FE-11BE-4583-BCE3-D439886AA729@nominum.com>
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/m5D1YWDf0ENbNRgWnTENYJ3rTZg
Subject: [dhcwg] Fwd: [DNSOP] [rfc-editor@rfc-editor.org: BCP 187, RFC 7227 on Guidelines for Creating New DHCPv6 Options]
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, 10 May 2014 14:14:20 -0000

--Apple-Mail=_CA7438CA-D64A-40CB-9B5B-A49E6E4C7202
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

For those who don't read dnsop, here is a nice thumbs-up for the work on =
the DHCP Options draft!

Begin forwarded message:

> From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
> Subject: [DNSOP] [rfc-editor@rfc-editor.org: BCP 187, RFC 7227 on =
Guidelines for Creating New DHCPv6 Options]
> Date: May 10, 2014 at 2:18:41 AM EDT
> To: <dnsop@ietf.org>
>=20
> The issues described in this RFC seem very close from the issues of
> new DNS RR types (reusing elements of previous formats, to avoid
> creating a parser from scratch, thinking in advance of implementation
> considerations, to increase the chances of atcual deployment,
> considering the end systems - provisioning and consumption - not only
> what goes on the wire, etc).
>=20
> A very good reading, IMHO.
>=20
>=20
> Resent-From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
> From: <rfc-editor@rfc-editor.org>
> Subject: BCP 187, RFC 7227 on Guidelines for Creating New DHCPv6 =
Options
> Date: May 8, 2014 at 8:08:09 PM EDT
> Resent-To: <stephane@laperouse.bortzmeyer.org>
> To: <ietf-announce@ietf.org>, <rfc-dist@rfc-editor.org>
> Cc: <drafts-update-ref@iana.org>, <dhcwg@ietf.org>, =
<rfc-editor@rfc-editor.org>
> Reply-To: <ietf@ietf.org>
>=20
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>        BCP 187       =20
>        RFC 7227
>=20
>        Title:      Guidelines for Creating New DHCPv6=20
>                    Options=20
>        Author:     D. Hankins, T. Mrugalski,
>                    M. Siodelski, S. Jiang,
>                    S. Krishnan
>        Status:     Best Current Practice
>        Stream:     IETF
>        Date:       May 2014
>        Mailbox:    dhankins@google.com,=20
>                    tomasz.mrugalski@gmail.com,=20
>                    msiodelski@gmail.com,
>                    jiangsheng@huawei.com,=20
>                    suresh.krishnan@ericsson.com
>        Pages:      35
>        Characters: 83694
>        Updates:    RFC 3315
>        See Also:   BCP 187
>=20
>        I-D Tag:    draft-ietf-dhc-option-guidelines-17.txt
>=20
>        URL:        http://www.rfc-editor.org/rfc/rfc7227.txt
>=20
> This document provides guidance to prospective DHCPv6 option
> developers to help them create option formats that are easily
> adoptable by existing DHCPv6 software.  It also provides guidelines
> for expert reviewers to evaluate new registrations.  This document
> updates RFC 3315.
>=20
> This document is a product of the Dynamic Host Configuration Working =
Group of the IETF.
>=20
>=20
> BCP: This document specifies an Internet Best Current Practices for =
the
> Internet Community, and requests discussion and suggestions for=20
> improvements. Distribution of this memo is unlimited.
>=20
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>=20
> For searching the RFC series, see http://www.rfc-editor.org/search
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>=20
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  =
Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>=20
>=20
> The RFC Editor Team
> Association Management Solutions, LLC
>=20
>=20
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


--Apple-Mail=_CA7438CA-D64A-40CB-9B5B-A49E6E4C7202
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">For =
those who don't read dnsop, here is a nice thumbs-up for the work on the =
DHCP Options draft!<br><div><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; color:rgba(0, =
0, 0, 1.0);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica';">Stephane Bortzmeyer &lt;<a =
href=3D"mailto:bortzmeyer@nic.fr">bortzmeyer@nic.fr</a>&gt;<br></span></di=
v><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; color:rgba(0, =
0, 0, 1.0);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica';"><b>[DNSOP] [<a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>: =
BCP 187, RFC 7227 on Guidelines for Creating New DHCPv6 =
Options]</b><br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>Date: =
</b></span><span style=3D"font-family:'Helvetica';">May 10, 2014 at =
2:18:41 AM EDT<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(0, 0, 0, 1.0);"><b>To: =
</b></span><span style=3D"font-family:'Helvetica';">&lt;<a =
href=3D"mailto:dnsop@ietf.org">dnsop@ietf.org</a>&gt;<br></span></div><br>=
<div>The issues described in this RFC seem very close from the issues =
of<br>new DNS RR types (reusing elements of previous formats, to =
avoid<br>creating a parser from scratch, thinking in advance of =
implementation<br>considerations, to increase the chances of atcual =
deployment,<br>considering the end systems - provisioning and =
consumption - not only<br>what goes on the wire, etc).<br><br>A very =
good reading, IMHO.<br><br><br><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(127, 127, 127, =
1.0);"><b>Resent-From: </b></span><span =
style=3D"font-family:'Helvetica';">Stephane Bortzmeyer &lt;<a =
href=3D"mailto:bortzmeyer@nic.fr">bortzmeyer@nic.fr</a>&gt;<br></span></di=
v><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
color:rgba(127, 127, 127, 1.0);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica';">&lt;<a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>&gt=
;<br></span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(127, 127, 127, =
1.0);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica';"><b>BCP 187, RFC 7227 on Guidelines =
for Creating New DHCPv6 Options</b><br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
color:rgba(127, 127, 127, 1.0);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica';">May 8, 2014 at 8:08:09 PM =
EDT<br></span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(127, 127, 127, =
1.0);"><b>Resent-To: </b></span><span =
style=3D"font-family:'Helvetica';">&lt;<a =
href=3D"mailto:stephane@laperouse.bortzmeyer.org">stephane@laperouse.bortz=
meyer.org</a>&gt;<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(127, 127, 127, =
1.0);"><b>To: </b></span><span style=3D"font-family:'Helvetica';">&lt;<a =
href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>&gt;, =
&lt;<a =
href=3D"mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a>&gt;<br=
></span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(127, 127, 127, =
1.0);"><b>Cc: </b></span><span style=3D"font-family:'Helvetica';">&lt;<a =
href=3D"mailto:drafts-update-ref@iana.org">drafts-update-ref@iana.org</a>&=
gt;, &lt;<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>&gt;, =
&lt;<a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>&gt=
;<br></span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; color:rgba(127, 127, 127, =
1.0);"><b>Reply-To: </b></span><span =
style=3D"font-family:'Helvetica';">&lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br></span></div><br><b=
r>A new Request for Comments is now available in online RFC =
libraries.<br><br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BCP 187 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RFC 7227<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Guidelines for Creating New DHCPv6 <br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Options <br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Author: =
&nbsp;&nbsp;&nbsp;&nbsp;D. Hankins, T. Mrugalski,<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;M. Siodelski, S. Jiang,<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;S. Krishnan<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Status: =
&nbsp;&nbsp;&nbsp;&nbsp;Best Current Practice<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Stream: =
&nbsp;&nbsp;&nbsp;&nbsp;IETF<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Date: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;May 2014<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Mailbox: &nbsp;&nbsp;&nbsp;<a =
href=3D"mailto:dhankins@google.com">dhankins@google.com</a>, <br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"mailto:tomasz.mrugalski@gmail.com">tomasz.mrugalski@gmail.com</a>,=
 <br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"mailto:msiodelski@gmail.com">msiodelski@gmail.com</a>,<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"mailto:jiangsheng@huawei.com">jiangsheng@huawei.com</a>, <br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"mailto:suresh.krishnan@ericsson.com">suresh.krishnan@ericsson.com<=
/a><br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Pages: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;35<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Characters: 83694<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Updates: &nbsp;&nbsp;&nbsp;RFC =
3315<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;See Also: =
&nbsp;&nbsp;BCP 187<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I-D Tag: =
&nbsp;&nbsp;&nbsp;draft-ietf-dhc-option-guidelines-17.txt<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.rfc-editor.org/rfc/rfc7227.txt">http://www.rfc-editor.o=
rg/rfc/rfc7227.txt</a><br><br>This document provides guidance to =
prospective DHCPv6 option<br>developers to help them create option =
formats that are easily<br>adoptable by existing DHCPv6 software. =
&nbsp;It also provides guidelines<br>for expert reviewers to evaluate =
new registrations. &nbsp;This document<br>updates RFC 3315.<br><br>This =
document is a product of the Dynamic Host Configuration Working Group of =
the IETF.<br><br><br>BCP: This document specifies an Internet Best =
Current Practices for the<br>Internet Community, and requests discussion =
and suggestions for <br>improvements. Distribution of this memo is =
unlimited.<br><br>This announcement is sent to the IETF-Announce and =
rfc-dist lists.<br>To subscribe or unsubscribe, see<br> &nbsp;<a =
href=3D"http://www.ietf.org/mailman/listinfo/ietf-announce">http://www.iet=
f.org/mailman/listinfo/ietf-announce</a><br> &nbsp;<a =
href=3D"http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist">http://ma=
ilman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br><br>For searching =
the RFC series, see <a =
href=3D"http://www.rfc-editor.org/search">http://www.rfc-editor.org/search=
</a><br>For downloading RFCs, see <a =
href=3D"http://www.rfc-editor.org/rfc.html">http://www.rfc-editor.org/rfc.=
html</a><br><br>Requests for special distribution should be addressed to =
either the<br>author of the RFC in question, or to <a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>. =
&nbsp;Unless<br>specifically noted otherwise on the RFC itself, all RFCs =
are for<br>unlimited distribution.<br><br><br>The RFC Editor =
Team<br>Association Management Solutions, =
LLC<br><br><br>_______________________________________________<br>DNSOP =
mailing list<br><a =
href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/dnsop<br></div></blockquote></div><br></body></html>=

--Apple-Mail=_CA7438CA-D64A-40CB-9B5B-A49E6E4C7202--


From nobody Mon May 12 01:32:16 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 5ABAC1A0309 for <dhcwg@ietfa.amsl.com>; Mon, 12 May 2014 01:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4pxk2h3e8fMU for <dhcwg@ietfa.amsl.com>; Mon, 12 May 2014 01:32:11 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 42ECB1A00C5 for <dhcwg@ietf.org>; Mon, 12 May 2014 01:32:11 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id m15so6563168wgh.20 for <dhcwg@ietf.org>; Mon, 12 May 2014 01:32:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=zoN/X8SDJKB7eD+wIfE8fOXBQ8oKmwsqG7py/ElHRvU=; b=k+rvn/BQ6//aRytXfFR8/o6Y8MP812zHzT74B2IpdkRtsinRMG0Om9ahh4xFbhbkD8 pA2rrKuLAu+zOrDHJWetJVxBjjDmG/QGNFPISLGf6HDLJO5dYdfKXvSDcqr7NRHadhN4 WAZqZYTiSFTgHTZKNCfJT0CWDDCASUjXUji4k+rkfpLbxB9g2zPSlSQ6VMs6Dn4zuDCG dQ72VdAlVzCZdUklwTdbEgJUqpwq44ff9cm0Dn+rc/2DkLJzwPvQVTIlp/TXs0wu9lW3 muhNcbcTNKtfqumoMMbd6Unvvo52IQdv7a9KnVYZFZAtyIa/fV0ns4MC7cY5wv4DQZjR gSsQ==
X-Received: by 10.180.81.36 with SMTP id w4mr14181215wix.36.1399883524841; Mon, 12 May 2014 01:32:04 -0700 (PDT)
Received: from dhcp-25-210.ripemtg.ripe.net ([2001:67c:64:42:20d1:fb2c:f6a5:711e]) by mx.google.com with ESMTPSA id k19sm14787047wic.10.2014.05.12.01.32.03 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 12 May 2014 01:32:04 -0700 (PDT)
Message-ID: <53708702.8060806@gmail.com>
Date: Mon, 12 May 2014 10:32:02 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <20140509000809.D93871801A4@rfc-editor.org>
In-Reply-To: <20140509000809.D93871801A4@rfc-editor.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/ZSJxpSgBzKm49YxKKDJETXDmHBk
Subject: Re: [dhcwg] BCP 187, RFC 7227 on Guidelines for Creating New DHCPv6 Options
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, 12 May 2014 08:32:13 -0000

Thanks to everyone who was involved in this effort. I'd like to
especially thank David Hankins, who initiated and then single-handedly
kept this effort running for many years. (This work has started in 2007).

Hopefully this BCP will make our lives easier. Instead of lengthy
reviews, we can now point to specific sections of this document and just
say "read and follow this, please".

Tomek

On 09/05/14 02:08, rfc-editor@rfc-editor.org wrote:
> A new Request for Comments is now available in online RFC libraries.
> 
>         BCP 187        
>         RFC 7227
> 
>         Title:      Guidelines for Creating New DHCPv6 
>                     Options 
>         Author:     D. Hankins, T. Mrugalski,
>                     M. Siodelski, S. Jiang,
>                     S. Krishnan
>         Status:     Best Current Practice
>         Stream:     IETF
>         Date:       May 2014
>         Mailbox:    dhankins@google.com, 
>                     tomasz.mrugalski@gmail.com, 
>                     msiodelski@gmail.com,
>                     jiangsheng@huawei.com, 
>                     suresh.krishnan@ericsson.com
>         Pages:      35
>         Characters: 83694
>         Updates:    RFC 3315
>         See Also:   BCP 187
> 
>         I-D Tag:    draft-ietf-dhc-option-guidelines-17.txt
> 
>         URL:        http://www.rfc-editor.org/rfc/rfc7227.txt
> 
> This document provides guidance to prospective DHCPv6 option
> developers to help them create option formats that are easily
> adoptable by existing DHCPv6 software.  It also provides guidelines
> for expert reviewers to evaluate new registrations.  This document
> updates RFC 3315.
> 
> This document is a product of the Dynamic Host Configuration Working Group of the IETF.
> 
> 
> BCP: This document specifies an Internet Best Current Practices for the
> Internet Community, and requests discussion and suggestions for 
> improvements. Distribution of this memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   http://www.ietf.org/mailman/listinfo/ietf-announce
>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see http://www.rfc-editor.org/search
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 


From nobody Mon May 12 10:12:15 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 47EC41A0733 for <dhcwg@ietfa.amsl.com>; Mon, 12 May 2014 10:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lBvvK7ENSegX for <dhcwg@ietfa.amsl.com>; Mon, 12 May 2014 10:11:55 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5FBE71A0741 for <dhcwg@ietf.org>; Mon, 12 May 2014 10:11:54 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id k48so7063174wev.5 for <dhcwg@ietf.org>; Mon, 12 May 2014 10:11:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=rHCmto7TQG0K9lPTB1JS2w9gY+NECUdjiO1QufqU5Kc=; b=HT3g634dh0eP1IVFj3zLZ28Py5LgqV9wmgO655IPBHlSrsr6SLbDDgy3xos4B7Ez8w nEuQAqWbEgwkVcbKMitUrpNMwhspXs3aD7nAx0H5eUdTzI0nN1U3l+pODo/UiqzfJEYH 36XCKxUE1O+QT22J01ihJsbwHmRYF0obg+nF+6YsiOztmzORy30pB6k9VrPT7tdfO2Rp XwekSHwAXySj/FBnn+lJK8a2SuVWPhuN9CNSvE5ByTOgjRb6wSv+whc84ibtCofItpx7 oS07x/GAziO6R0S4Ti8+u+znsg6beaZj8nbmmT2SNOpTB7jZwxwwpjC5BPeLIgBlNJ44 MioA==
MIME-Version: 1.0
X-Received: by 10.195.17.169 with SMTP id gf9mr993860wjd.10.1399914707782; Mon, 12 May 2014 10:11:47 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.222.9 with HTTP; Mon, 12 May 2014 10:11:47 -0700 (PDT)
In-Reply-To: <86DAC0E6-BC1A-4247-9AD1-C13DA01F170D@nominum.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com> <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE442FD@nkgeml512-mbx.china.huawei.com> <CAJE_bqc+Z8awb5773OLs8QtXuCRxYCWFRAKuQ9YP8anFwEQqsQ@mail.gmail.com> <5D53E8BB-F692-4752-A1B2-9BB09747C58B@nominum.com> <CAJE_bqeNNW1=dSnj4f=t7Fx9waG81cDeHdcikqk0ECUoLvgVzQ@mail.gmail.com> <86DAC0E6-BC1A-4247-9AD1-C13DA01F170D@nominum.com>
Date: Mon, 12 May 2014 10:11:47 -0700
X-Google-Sender-Auth: rUGWd1W7xDwr0XNyqxp4TUOLAzw
Message-ID: <CAJE_bqfnOhziaiOzf89gFK3vy_bC+SSWqUFwtLqusNtRRiyFkg@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/pz698qvju6I6XEx0WpD46rWyQGE
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 12 May 2014 17:12:00 -0000

At Fri, 9 May 2014 18:44:57 -0400,
Ted Lemon <ted.lemon@nominum.com> wrote:

> > My main concern is the combination of authenticating clients with the
> > leap of faith model. [...]
>
> You are right--I don't think there is a use case for leap-of-faith with c=
lients.

Okay.

> > I'm okay with separating such discussions outside of this document.
> > But then I'd personally like to see a "threat analysis" document
> > first (covering these points), not the other way around. [...]
>
> We are in the awkward situation that lots of DHCP people already know wha=
t the threat models are, although I think you are correct that they have no=
t been clearly articulated in a threat analysis document.   I think such a =
document would be a good idea.   However, I'm reluctant to delay this docum=
ent on that basis.   It might make sense to do so, but I will leave that up=
 to the working group to debate.

I don't want to be a blocker for this document because of this,
either.  If the rest of the wg thinks this is sufficiently
substantial, that's fine; if not, but it's actually to be considered,
hopefully a security AD will raise a concern at the time the IESG
review; and if that's not even the case, presumably my point is not
really that important.  I'm okay with any of these possibilities.

With noting this, if I may make a specific suggestion for the draft:

- provide some specific common use cases of server authentication and
  client authentication
- provide considerations on the applicability of the leap of faith
  model for these cases.  in particular, note that there is no known
  use case for client authentication with leap of faith

These can go to the introduction or a small separate section.  And, I
believe these can be sufficiently concise to fit in the protocol
document without breaking its scope too much (and I think it's a
reasonable compromise if we don't want to delay this document for a
more formal threat analysis).

On top of these, I'd even say: client authentication with leap of
faith SHOULD NOT be used until a clear use case is identified.

And, for the security considerations section on the resource
exhaustion attacks I'd revise it so it will:

- note that as long as the above 'SHOULD NOT' is honored this should
  be less concerned because this "attack" is much less
  likely/realistic on clients.  (in other words, this is another
  reason why we should discourage the use of client authentication
  with leap of faith)

> > Considerations like the possibility of resource exhaustion attacks as
> > mentioned in Section 7 of the draft.
>
> Leap-of-faith typically involves some kind of act of faith before trustin=
g a key.   E.g., with ssh, that's the user saying "yes, go ahead."   I don'=
t think you could do a resource exhaustion attack in this situation.

True, but this type of "act of faith" is not very feasible for servers
since it requires human intervention (ssh itself is a proof of this).
In the case of DHCP servers, I'm actually still not sure if this is a
real threat (because they should already manage other types of
possibly stale client related resources), but if we still consider
this as a security matter, we need something else than the ssh kind of
"act of faith".  My suggestion above is one such thing.

--
JINMEI, Tatuya


From nobody Tue May 13 01:58:45 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 200501A0447 for <dhcwg@ietfa.amsl.com>; Tue, 13 May 2014 01:58:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.552
X-Spam-Level: 
X-Spam-Status: No, score=-4.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 Rkfj-J_1-NFw for <dhcwg@ietfa.amsl.com>; Tue, 13 May 2014 01:58:41 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id EB98A1A018F for <dhcwg@ietf.org>; Tue, 13 May 2014 01:58:40 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BEC16684; Tue, 13 May 2014 08:58:33 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 13 May 2014 09:56:47 +0100
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 13 May 2014 09:58:21 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.206]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Tue, 13 May 2014 16:58:08 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <ted.lemon@nominum.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
Thread-Index: AQHPY9fqOkQX2Up+wk+VaPjsYGUK15sp5cSAgAlKLTCAAZYjAIABm4uAgAAEhoCAACMagIABlPqAgABElYCABc/wYA==
Date: Tue, 13 May 2014 08:58:07 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE47C5A@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com> <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE442FD@nkgeml512-mbx.china.huawei.com> <CAJE_bqc+Z8awb5773OLs8QtXuCRxYCWFRAKuQ9YP8anFwEQqsQ@mail.gmail.com> <5D53E8BB-F692-4752-A1B2-9BB09747C58B@nominum.com> <CAJE_bqeNNW1=dSnj4f=t7Fx9waG81cDeHdcikqk0ECUoLvgVzQ@mail.gmail.com> <86DAC0E6-BC1A-4247-9AD1-C13DA01F170D@nominum.com>
In-Reply-To: <86DAC0E6-BC1A-4247-9AD1-C13DA01F170D@nominum.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/wwrgsysz-OiTQQPTXgFCXUAaX_4
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 May 2014 08:58:43 -0000

Pk9uIE1heSA5LCAyMDE0LCBhdCAyOjM5IFBNLCDnpZ7mmI7pgZTlk4kgPGppbm1laUB3aWRlLmFk
LmpwPiB3cm90ZToNCj4+IE15IG1haW4gY29uY2VybiBpcyB0aGUgY29tYmluYXRpb24gb2YgYXV0
aGVudGljYXRpbmcgY2xpZW50cyB3aXRoIHRoZQ0KPj4gbGVhcCBvZiBmYWl0aCBtb2RlbC4gIFRo
aXMgbW9kZWwgaXNuJ3Qgc3VpdGFibGUgZm9yIHRoZSAiZ3JhbnQNCj4+IGRpZmZlcmVudCBhY2Nl
c3MiIHVzYWdlLCBzaW5jZSBhbnlvbmUgY2FuIHByZXRlbmQgdG8gYmUgYW4NCj4+IGF1dGhlbnRp
Y2F0ZWQgY2xpZW50IHdpdGggdGhhdCBtb2RlbC4NCj4NClRlZCBMZW1vbj5Zb3UgYXJlIHJpZ2h0
LS1JIGRvbid0IHRoaW5rIHRoZXJlIGlzIGEgdXNlIGNhc2UgZm9yIGxlYXAtb2YtZmFpdGggd2l0
aCBjbGllbnRzLg0KDQpUaGUgcHVycG9zZSBvZiBhdXRoZW50aWNhdGluZyBjbGllbnRzIHdpdGgg
dGhlIGxlYXAgb2YgZmFpdGggbW9kZWwgaXMgdG8gcHJvdGVjdCB0aGUgZm9sbG93LXVwIGNsaWVu
dC10by1zZXJ2ZXIgbWVzc2FnZXMsIHN1Y2ggYXMgQ29uZmlybSwgUmVuZXcsIFJlYmluZCwgRGVj
bGluZSwgUmVsZWFzZSwgSW5mb3JtYXRpb24tcmVxdWVzdCBtZXNzYWdlcywgaGVuY2UsIG1vcmUg
cHJvdGVjdGlvbiBmb3IgY2xpZW50cy4NCg0KV2hlbiB0aGVyZSBpcyBubyBzZWN1cml0eSBwcm90
ZWN0aW9uLCBhbiBhdHRhY2tlciBjYW4gdHJ5IHRvIHRhbXBlciB0aGUgbWVzc2FnZXMgb3IgZ2Vu
ZXJhdGUgYm9ndXMgbWVzc2FnZXMgYXQgdGhlIGFsbCB0aGUgc3RhZ2VzIG9mIHRoZSBjb21tdW5p
Y2F0aW9uIGJldHdlZW4gYSBESENQIGNsaWVudCBhbmQgYSBzZXJ2ZXIuIEZvciBleGFtcGxlLCBh
biBhdHRhY2tlciBtYXkgc2VuZCBhIGJvZ3VzIFJlbGVhc2UgbWVzc2FnZSwgbWFzcXVlcmFkaW5n
IGFzIGEgY2xpZW50LCB0byB0aGUgc2VydmVyLiBUaGUgbmV0d29yayB0aGVuIGRlbnkgdGhlIGFj
Y2VzcyBmcm9tIHRoYXQgSVAgYWRkcmVzcy4gSXQgd291bGQgYWN0dWFsbHkgYWZmZWN0IHRoZSBj
bGllbnQuDQoNCkFmdGVyIGludHJvZHVjaW5nIGxlYXAgb2YgZmFpdGgsIHRoZSBhdHRhY2sgc3Vy
ZmFjZSBpcyBuYXJyb3dlZC4gQW4gYXR0YWNrZXIgY2FuIG9ubHkgaGF2ZSBjaGFuZ2VzIHRvIHBl
cmZvcm0gYWJvdmUgbWVudGlvbmVkIGF0dGFja3Mgd2hlbiB0aGUgbGVnYWwgY2xpZW50IG9yIHRo
ZSBsZWdhbCBESENQIHNlcnZlciBleGNoYW5nZSB0aGVpciBmaXJzdCBwYWlyIG9mIG1lc3NhZ2Vz
LiBBZnRlciB0aGF0LCBhbnkgYm9ndXMgcGFja2V0cyBjb3VsZCBiZSBkZXRlY3RlZC4gU28sIHRo
ZSBjbGllbnRzIHRoYXQgdXNlIFBLIG9yIHVudmVyaWZpYWJsZSBjZXJ0aWZpY2F0ZSB3b3VsZCBo
YXZlIG1vcmUgcHJvdGVjdGlvbiBvdmVyIGxlZ2FjeSBjbGllbnRzLg0KDQpJdCBoYXMgYmVlbiBy
ZWFsaXplZCB0aGF0IHRoZSBsZWFwIG9mIGZhaXRoIGNhbm5vdCBwcmV2ZW50IGFuIGF0dGFja2Vy
IGZyb20gaW1wZXJzb25hdGluZyBsZWdhbCBjbGllbnRzIHRvIHBlcmZvcm0gcmVzb3VyY2UgZXho
YXVzdGluZyBhdHRhY2tzIGFnYWluc3QgdGhlIERIQ1Agc2VydmVyLiBJbiBvcmRlciB0byBkZWFs
IHdpdGggdGhpcyB0eXBlIG9mIGF0dGFjaywgY2VydGlmaWNhdGUgYmFzZWQgbWVjaGFuaXNtIG5l
ZWRzIHRvIGJlIHByb3ZpZGVkLiBXZSBhbHNvIG5vdGUgdGhhdCB0aGUgbGVhcCBvZiBmYWl0aCB3
aWxsIGNvbnN1bWUgYWRkaXRpb25hbCBtZW1vcnkgcmVzb3VyY2VzIG9mIHNlcnZlcnMgdG8gcmVt
ZW1iZXIgdGhlIGhhc2ggdmFsdWVzIG9mIHRoZSBwdWJsaWMga2V5cyB1c2VkIGJ5IHRoZSBjbGll
bnRzLiBIb3dldmVyLCB3aGVuIHVzaW5nIFNIQS0xIHRoZSBsZW5ndGggb2YgdGhlIGhhc2ggb2Yg
YSBwdWJsaWMga2V5IGlzIG5vIGxvbmdlciB0aGFuIGFuIElQdjYgYWRkcmVzcy4gU28sIHdlIGRv
buKAmXQgdGhpbmsgdGhpcyB3aWxsIHNlcmlvdXNseSBhZmZlY3QgdGhlIHBlcmZvcm1hbmNlIG9m
IHRoZSBESENQIHNlcnZlci4NCg0KQmVzdCByZWdhcmRzLA0KDQpTaGVuZyArIERhY2hlbmcNCg==


From nobody Thu May 15 10:37:00 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 CA9BD1A02CB for <dhcwg@ietfa.amsl.com>; Thu, 15 May 2014 10:36:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L3m3vb3H09ey for <dhcwg@ietfa.amsl.com>; Thu, 15 May 2014 10:36:56 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F05A51A02B9 for <dhcwg@ietf.org>; Thu, 15 May 2014 10:36:55 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id u57so1434560wes.32 for <dhcwg@ietf.org>; Thu, 15 May 2014 10:36:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=AQF0vXj3lR6QIrBe91JWFzWG+TkrpjbWqmNzjebrydc=; b=wJbRGNgV1+eLfntJX3cb8nUl1oZO6aQzC0mAos8sNKxxMVKhTFXSenmpRwj4F8G73q VWzSO+20666Vb+JXsHVNU5LeCTBCBloc/hF9HY+JYWgVHjvNENFps/az7Z4T30ijdWqM iR6bjAWaoEZC+i3kCCiMwA248D7zAlwHvD4fXvhclIQIJ1S/s2OnGEvUgocQj86bxxgj U57nuAMyN/TYBJO0xkzvPYGnUORhmj+vxksQ6DjI9VLUxJUdVJfOCCa+3kQbgPBAigK1 wPmM3neI00pUyMT5ySVGx8T7MXqh6PvwE5AmKyN0XWWjOk2kE2KzGXtBA89W+APVFvQk 759w==
MIME-Version: 1.0
X-Received: by 10.180.13.239 with SMTP id k15mr6291536wic.4.1400175407676; Thu, 15 May 2014 10:36:47 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.222.9 with HTTP; Thu, 15 May 2014 10:36:47 -0700 (PDT)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE47C5A@nkgeml512-mbx.china.huawei.com>
References: <535FEDAD.5010103@gmail.com> <CAJE_bqen37j5UCsKZj6syVyvk2Xed4V_xGp-t4xY8shjmS+H5g@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE43272@nkgeml512-mbx.china.huawei.com> <CAJE_bqe75D7oRJq=XmjPR9Dfvu3-AcL8kF9Pkm3JEOVsyxhr5A@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AE442FD@nkgeml512-mbx.china.huawei.com> <CAJE_bqc+Z8awb5773OLs8QtXuCRxYCWFRAKuQ9YP8anFwEQqsQ@mail.gmail.com> <5D53E8BB-F692-4752-A1B2-9BB09747C58B@nominum.com> <CAJE_bqeNNW1=dSnj4f=t7Fx9waG81cDeHdcikqk0ECUoLvgVzQ@mail.gmail.com> <86DAC0E6-BC1A-4247-9AD1-C13DA01F170D@nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923AE47C5A@nkgeml512-mbx.china.huawei.com>
Date: Thu, 15 May 2014 10:36:47 -0700
X-Google-Sender-Auth: v4vsA8gu6hM1pdS6SZ9PilVw13I
Message-ID: <CAJE_bqeSH+qELChVq=_bjRQ_8eWzsRV379wWKPNQjHTqAuMbFg@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Qnuf68r5oV2NDxmdK76iKPOZZsE
Cc: dhcwg <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 15 May 2014 17:36:58 -0000

At Tue, 13 May 2014 08:58:07 +0000,
Sheng Jiang <jiangsheng@huawei.com> wrote:

> >> My main concern is the combination of authenticating clients with the
> >> leap of faith model.  This model isn't suitable for the "grant
> >> different access" usage, since anyone can pretend to be an
> >> authenticated client with that model.
> >
> Ted Lemon>You are right--I don't think there is a use case for leap-of-fa=
ith with clients.
>
> The purpose of authenticating clients with the leap of faith model
> is to protect the follow-up client-to-server messages, such as
> Confirm, Renew, Rebind, Decline, Release, Information-request
> messages, hence, more protection for clients.
>
> When there is no security protection, an attacker can try to tamper
> the messages or generate bogus messages at the all the stages of the
> communication between a DHCP client and a server. For example, an
> attacker may send a bogus Release message, masquerading as a client,
> to the server. The network then deny the access from that IP
> address. It would actually affect the client.

I see what you're trying to say, and it makes some sense, but I'd like
to see more precise discussion, rather than just listing random
message types and obscuring details with a word like "such as".  For
example, I don't see (at least not immediately) what kind of
protection can be provided for Information-request in this context.
It's stateless by definition, so a forged Information-request from an
attacker doesn't break anything on other clients.

Also, I don't see the need for leap-of-faith in the case of forged
Release.  The server doesn't have to "leap" when it first sees a
client's public key since it's not for authenticating the client for
that particular request but for authenticating a possible subsequent
Release to confirm that is certainly from the client the server
originally responded to.  Also, for this purpose, the server only has
to remember the client's public key during that DHCPv6 session; it can
immediately forget the public key after that, so it doesn't have to
worry about "resource exhaustion attacks" at all.

I can see one possibility of client authentication + leap-of-faith
from the discussion so far, though: it may help prevent an attacker
from pretending to be a disconnected past client by sending a forged
Solicit (maybe with a forged public key).  If it was granted, there
might be confusion when the legitimate client comes back and tries to
establish another DHCPv6 session (I'm not sure if this inevitably
causes a security threat or could be just some confusion).  If the
server stores the original public key of the legitimate client, it can
reject the forged Solicit.  (Interesting, Solicit is not listed in the
message types you listed above).

> It has been realized that the leap of faith cannot prevent an
> attacker from impersonating legal clients to perform resource
> exhausting attacks against the DHCP server. In order to deal with
> this type of attack, certificate based mechanism needs to be
> provided. We also note that the leap of faith will consume
> additional memory resources of servers to remember the hash values
> of the public keys used by the clients. However, when using SHA-1
> the length of the hash of a public key is no longer than an IPv6
> address. So, we don=E2=80=99t think this will seriously affect the
> performance of the DHCP server.

Any trick to "mitigate" such a threat may be useful, but my main point
was at a more higher level: whether we should worry about this issue
in the first place: for clients this shouldn't be much concern in
practice; for sever, if we don't see the need for client authentication +
leap-of-faith, we don't have to worry about it (note that avoiding
forged Release doesn't require leap-of-faith as I noted above).  So,
only with an example like avoiding a forged Solicit explained above do
we need to worry about it.  But, right now, such a precise discussion
is totally missing in the draft and only some vague fear of a threat
is documented, which made me think whether this is really an issue or
not.  Discussions like specific "mitigation" such as the use of
fingerprint does not address this fundamental point.  I hope I'm clear
about my concern this time...

Now, with this latest understanding, I'd revise my previous specific
suggestion I described in
http://www.ietf.org/mail-archive/web/dhcwg/current/msg15524.html:

- provide a short "applicability considerations" section.  It includes
  some specific common use cases of server authentication and
  client authentication with key management:
  1. authenticating a server, mainly for clients to authenticate the
     information the server provides
  2. authenticating a client, so the server can selectively serve a
     specific client (or deny specific clients)
  3. authenticating a client, so the server can prevent an attacker
     from breaking an existing DHCPv6 session of a legitimate client.
  4. authenticating a client, so the server can prevent an attacker
     from establishing a new DHCPv6 session pretending to be a past
     legitimate client.

  For 1, both CA/preshared or leap-of-faith can be used.  The latter
  is weak in pure security point of view, but probably better than
  no protection by narrowing the attack scope.

  For 2, leap-of-faith cannot be used, since anyone can pretend to be
  a new legitimate client.

  For 3, leap-of-faith is not necessary, since the server uses the
  public key only to confirm that a subsequent message is sent from
  that client (rather than "trusting" the client in the initial
  solicit).

  For 4, both CA/preshared or leap-of-faith can be used, just like
  case 1.

And, for the security consideration on the "resource exhaustion
attacks", we'd note it matters only for cases like 4 in the
applicability categorization.  (With that clarification, we might or
might now want to mention possible mitigation, like the use of
footprint instead of full key information).

If this document is organized like this, I'll feel much more
comfortable.

--
JINMEI, Tatuya


From nobody Fri May 16 09:39:28 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA7861A00B5 for <dhcwg@ietfa.amsl.com>; Fri, 16 May 2014 09:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yoe9J8LejIng for <dhcwg@ietfa.amsl.com>; Fri, 16 May 2014 09:39:25 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 058691A0281 for <dhcwg@ietf.org>; Fri, 16 May 2014 09:39:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4357; q=dns/txt; s=iport; t=1400258358; x=1401467958; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=/gMAaBsP3y9MRsjTU+aomhLRSpFNlYceai/gSh/tVRE=; b=LjT2X+0tiOaSTHyKKTKao9Esfn35UHEhX26WxPjuoNgvk7hdjYKmiuiX IBDxZ8Og653wjzfhl8r1KqnVjOpqV0oKMwx7abaVrYyvzxygWruI1PPeQ R86HsL7Hi/7VNyNApV4fS+cVAqFPlOvg+tGxkFawjm19SIyJ1DA+WP/NT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAAc+dlOtJV2Y/2dsb2JhbABZgwZPWMNxAYEWFnSCJQEBAQQdHS4hAgEIEQMBAgsUEDIUBwEBBQMCBBMIDAiIJQ3NBYRzEwSJMIIRAYIrDgMBHzgCgymBFQSscYM3gXc5
X-IronPort-AV: E=Sophos;i="4.97,1068,1389744000"; d="scan'208";a="325519724"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-3.cisco.com with ESMTP; 16 May 2014 16:39:16 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s4GGdGuh026621 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Fri, 16 May 2014 16:39:16 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.63]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Fri, 16 May 2014 11:39:15 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: NomCom 2014-2015 Call for Volunteers
Thread-Index: AQHPcRLQ1IdZ+WY2EEmlAMPuvcKmPZtDsqIA//+1sEA=
Date: Fri, 16 May 2014 16:39:14 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B02E2D1@xmb-rcd-x04.cisco.com>
References: <9913.1400250296@sandelman.ca> <8936E630-7FDA-40F2-B6B6-F7477017F692@cisco.com>
In-Reply-To: <8936E630-7FDA-40F2-B6B6-F7477017F692@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.246.25]
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/Qr8bnfqAPfrcPJrvbsxSoSDvkRc
Subject: [dhcwg] FW: NomCom 2014-2015 Call for Volunteers
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, 16 May 2014 16:39:27 -0000

FYI ...

From: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: NomCom 2014-2015 Call for Volunteers
Date: May 16, 2014 at 7:24:56 AM PDT
To: <ietf@ietf.org>
Reply-To: <nomcom-chair-2014@ietf.org>

{I have to post using my subscribed address. Appologies for duplicates}

The IETF nominating committee (nomcom) process for 2014-15 has begun. The I=
ETF nomcom appoints folks to fill the open slots on the IAOC, the IAB, and =
the IESG (including IETF Chair).

Ten voting members for the nomcom are selected in a verifiably random way f=
rom a pool of volunteers. The more volunteers, the better chance we have of=
 choosing a random yet representative cross section of the IETF population.

Let's break the 200 volunteer mark again this year!

The details of the operation of the nomcom can be found in RFC 3777, and BC=
P10/RFC3797 details the selection algorithm.

Volunteers must have attended 3 of the past 5 IETF meetings.  As specified =
in RFC 3777, that means three out of the five past meetings up to the time =
this email announcement goes out to start the solicitation of volunteers.
The five meetings out of which you must have attended *three*
are IETF 85(Atlanta),      \
        86(Orlando),       \
        87(Berlin),         *** ANY THREE!
        88(Vancouver),     /
        89(London)        /

If you qualify, please volunteer.   However, much as we want this, before y=
ou
decide to volunteer, please be sure you are willing to forgo appointment to=
 any of the positions for which this nomcom is responsible.

The list of people and posts whose terms end with the March 2015 IETF meeti=
ng, and thus the positions for which this nomcom is responsible, are

IAOC:
To be confirmed

IAB:
Joel Halpern
Russ Housley
Eliot Lear
Xing Li
Andrew Sullivan
Dave Thaler

IESG:
Pete Resnick (Applications)
Ted Lemon (Internet)
Joel Jaeggli (Operations and Management) Richard Barnes (RAI) Adrian Farrel=
* (Routing) Stephen Farrell (Security) Spencer Dawkins (Transport) Jari Ark=
ko (Gen)

(names with * have publically indicated they will not serve another term)

The primary activity for this nomcom will begin in July 2014 and should be
completed in January 2015.   The nomcom will have regularly scheduled
conference calls to ensure progress. (We might dogfood WebRTC) There will b=
e activities to collect requirements from the community, review candidate q=
uestionnaires, review feedback from community members about candidates, and=
 talk to candidates.

Thus, being a nomcom member does require some time commitment; but it is al=
so a very rewarding experience.

It is very important that you be able to attend IETF91 to conduct interview=
s.
Being at IETF90 is useful for training.  Being at IETF92 is not essential.

Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours) =
June 22, 2013, as follows:

To: nomcom-chair-2014@ietf.org
Subject: Nomcom 2014-15 Volunteer

Please include the following information in the email body:

<Your Full Name>
   // First/Given Name followed by Last/Family Name
   // matching how you enter it in the IETF Registration Form)

<Current Primary Affiliation>
   // Typically what goes in the Company field
   // in the IETF Registration Form
[<All email addresses used to register for the past 5 IETF meetings>] <Pref=
erred email address> <Telephone number>
   // For confirmation if selected

You should expect an email response from me within 3 business days stating =
whether or not you are qualified.  If you don't receive this response, plea=
se re-send your email with the tag "RESEND"" added to the subject line.

If you are not yet sure if you would like to volunteer, please consider tha=
t nomcom members play a very important role in shaping the leadership of th=
e IETF.  Questions by email or voice are welcome.
Volunteering for the nomcom is a great way to contribute to the IETF!

You can find a detailed timeline on the nomcom web site at:
   https://datatracker.ietf.org/nomcom/2014/

I will be publishing a more detailed target timetable, as well as details o=
f the randomness seeds to be used for the RFC 3797 selection process, withi=
n the next couple weeks.

Thank you!
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org




From nobody Sat May 17 15:21:42 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1B551A021A for <dhcwg@ietfa.amsl.com>; Sat, 17 May 2014 15:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HR9v-kcF4hR for <dhcwg@ietfa.amsl.com>; Sat, 17 May 2014 15:21:38 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 474FA1A0119 for <dhcwg@ietf.org>; Sat, 17 May 2014 15:21:38 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id fa1so4066625pad.25 for <dhcwg@ietf.org>; Sat, 17 May 2014 15:21:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=foyvmKTDOz29SpYrrGF/ETIb/qBi8/lsMJZdWH+ecRk=; b=KzKxvlhdkll3QGeZIy9SwSrmNZdvfU11HXth/E1HHHRvCUehbCz4fBPBeUorWDFjV/ 37Sz/qkD48k4kJbuYcxznPie/Dpu3zA9WvjE2dS3ddWt+81Sv6xp1DQ4/ouY7drX9CD/ xzBvSH4zmFtx3r6r1A+Bg4if0GqfQwelCUpvVvhZM+0ZrUzUZWfb7mjl5CVDRiS6r6UX uS18N/QanxOx4fsj0do1+9e2MxpPVlPfACTsVR5yfSv5ZP3wIcc7IhngmZt/VUfkdGnY uceF9QOp45ACMcDEGV8q5VA+qdOP7zPggUsFqgKPaW+a+7jZHuof9FwmJIgYv4rG91cB 9M7Q==
X-Received: by 10.66.142.233 with SMTP id rz9mr31692863pab.71.1400365297930; Sat, 17 May 2014 15:21:37 -0700 (PDT)
Received: from sjc-vpn6-1565.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPSA id au4sm21738798pbc.10.2014.05.17.15.21.35 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 17 May 2014 15:21:36 -0700 (PDT)
From: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <1C435EB5-6982-4A07-A89D-769A954821A2@gmail.com>
Date: Sat, 17 May 2014 15:21:41 -0700
To: dhcwg <dhcwg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/zcLT-cd0gftd64MTZK5oMixQ5vA
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 17 May 2014 22:21:40 -0000

After reading the document, I don't fully understand where this
mechanism would be useful and where it wouldn't.  The meta-question
here is "what security problem does this mechanism solve?".

draft-ietf-dhc-sedhcpv6-02 defines a PKI/cert mechanism and talks a
little about leap-of-faith mechanisms/TOFU.  But the document doesn't
talk about various attack scenarios and which of those scenarios are
mitigated by the mechanism described in the draft.

TOFU prevents subsequent attacks by other servers once the client has
decided to TOFU some server, right?  How does that mechanism work:

1. in a home network?
2. in a Starbucks?
3. in a university/school?
4. in an enterprise?
5. when attaching to an ISP?

Put simply, do I have it right that the "leap of faith" prevents
future attacks spoofed as coming from that server?  The client has no
knowledge about whether the server might mount an attack itself.

Trusting a cert requires some way to evaluate that cert's
trustworthiness. Seems applicable in some scenarios (maybe #4 above)
but not in others ... unless we implement some huge infrastructure for
handing out "approved DHCP certs".

Specific questions:

Can a server send a secure DHCPv6 message in response to an insecure
message from a client?

What is the definition of "secure model" in section 4.3?  I assume you
mean the client should "start by sending secure DHCPv6 messages".

In section 4.3, suppose a DHCPv6 legacy DHCPv6 server decides to
discard a secure DHCPv6 message (which may not be compliant with RFC
3315).  I suggest the document recommend that a client fall back to
non-secure DHCPv6 messages if it receives no response to secure DHCPv6
messages.

Section 6.2 mentions the requirement for a "local trust public key
list".  In my opinion, this requirement is a very important
characteristic of the security mechanism described in this document,
and should be explained much earlier in the document.


From nobody Mon May 19 08:16:21 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 1F2081A010F for <dhcwg@ietfa.amsl.com>; Mon, 19 May 2014 08:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZuK8qBbJp56 for <dhcwg@ietfa.amsl.com>; Mon, 19 May 2014 08:16:14 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B56B31A008D for <dhcwg@ietf.org>; Mon, 19 May 2014 08:16:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4250; q=dns/txt; s=iport; t=1400512574; x=1401722174; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=uCA/97FPwstL69pIN9WrSb3FkSIFK3Ih5lfykBDOceA=; b=TnMrxHrIrzZbvbBwnvT/o7IbsldbT3j4pZdgM+kZ4Nfq06YWBmmGmDV+ Lh8JaMqkSkDTjy5oKvBAN+EeXs5q87eP5NJ5+muDT9kw3zuSr2Fc1qJdt 57uR6yCGKfKm5KbWKB7FfrY9rgfBDdUaoJ6GjZgeX5S/l8UAoKOtbjDVJ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AswIAO0felOtJA2I/2dsb2JhbABZgwZRUQeCacEeARl8FnSCJQEBAQQjEUMOBAIBGQQBAQMCBh0DAgICMBQBCAgCBBMIAYg4CAWtTKQ/F4EqjEQQAgEKFBYiBoJvNoEVBJsXkV2DN22BQw
X-IronPort-AV: E=Sophos;i="4.98,868,1392163200"; d="scan'208";a="326082238"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-8.cisco.com with ESMTP; 19 May 2014 15:16:14 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s4JFGE9b023653 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Mon, 19 May 2014 15:16:14 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.63]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0123.003; Mon, 19 May 2014 10:16:13 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: New Version Notification for draft-dhcwg-dhc-rfc3315bis-01.txt
Thread-Index: AQHPc3OAslCvfUG1wk2wTmj/EaZE/JtIACNQ
Date: Mon, 19 May 2014 15:16:13 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B03125B@xmb-rcd-x04.cisco.com>
References: <20140519150302.3625.29866.idtracker@ietfa.amsl.com>
In-Reply-To: <20140519150302.3625.29866.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.243.64]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/KRBLkBA1yWNs-ngSbdFeqa_x254
Subject: [dhcwg] New Version Notification for draft-dhcwg-dhc-rfc3315bis-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 May 2014 15:16:19 -0000

VGhlIGRoY3B2NmJpcyB0ZWFtIGlzIHBsZWFzZWQgdG8gaGF2ZSBwdWJsaXNoZWQgYSByZXZpc2lv
biBvZiBSRkMzMzE1YmlzIHdvcmsuDQoNClRoaXMgdmVyc2lvbiBvZiB0aGUgZHJhZnQ6DQoxLiBJ
bmNvcnBvcmF0ZXMgdGhlIFJGQzMzMTUgRXJyYXRhLg0KMi4gSW5jb3Jwb3JhdGVzIHRoZSBjaGFu
Z2VzIG1hZGUgdG8gUkZDMzMxNSBieSBvdGhlciBSRkNzLg0KMy4gQWRkcmVzc2VzIG90aGVyIGlz
c3VlcyByYWlzZWQgdmlhIGVtYWlsIHRvIHRoZSBvcmlnaW5hbCBhdXRob3JzIG9yIHRoZSBkaGNw
djZiaXMgdGVhbSBvciBpbiBvdGhlciBkb2N1bWVudHMgKHN1Y2ggYXMg4oCLaHR0cDovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LWNsYXJpZnktYXV0aC0wMSkuDQoN
ClRoaXMgbW9zdGx5IGNvdmVycyB0aGUgTWlsZXN0b25lIEEgKGFwcGx5IGJlZm9yZSBtZXJnZSkg
dGlja2V0cyAtIHNlZSBodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy9ncm91cC9kaGNwdjZiaXMv
cmVwb3J0LzYgKG1vc3Qgb2YgdGhlIHRpY2tldHMgcmVzb2x2ZWQgYXJlIGF0IHRoZSBib3R0b20g
aW4gdGhlICJBIGVhc3ksIGFwcGx5IGJlZm9yZSBtZXJnZSIgY2F0ZWdvcnkpLg0KDQpUaGlzIHZl
cnNpb24gb2YgdGhlIGRyYWZ0IGRvZXMgTk9UIHlldCBjb3ZlciB0aGUgbWVyZ2UgZnJvbSBSRkMg
MzYzMyAoYW5kIFJGQyAzNzM2KSwgdGhvdWdoIHlvdSBmaW5kIGEgZmV3IGluc3RhbmNlcyB3aGVy
ZSB0aGF0IHdvcmsgd2FzIHN0YXJ0ZWQuIEFkZGluZyB0aGlzIG1hdGVyaWFsIGlzIHRoZSBuZXh0
IG1ham9yIGdvYWwuDQoNCldlIHdvdWxkIGFwcHJlY2lhdGUgYW55IHJldmlld3MgcGVvcGxlIGNh
biBkbyBvbiB0aGlzIGRyYWZ0IC0gcGxlYXNlIHByb3ZpZGUgY29tbWVudHMgb24gd2hhdCBuZWVk
cyB0byBiZSBmaXhlZCBvciB5b3UgZmVlbCBpcyBub3QgYW4gYXBwcm9wcmlhdGUgY2hhbmdlISAo
U2VuZCBtYWlsIHRvIGRoY3B2NmJpc0BpZXRmLm9yZykuDQoNCkh0bWxpemVkOiAgICAgICBodHRw
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1kaGN3Zy1kaGMtcmZjMzMxNWJpcy0wMQ0KRGlm
ZjogICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWRoY3dn
LWRoYy1yZmMzMzE1YmlzLTAxDQoNCi0gQmVybmllIChmb3IgdGhlIGRoY3B2NmJpcyB0ZWFtKQ0K
DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYu
b3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6IE1vbmRheSwgTWF5
IDE5LCAyMDE0IDExOjAzIEFNDQpUbzogQW5kcmV3IFlvdXJ0Y2hlbmtvIChheW91cnRjaCk7IEJl
cm5pZSBWb2x6ICh2b2x6KTsgVG9tZWsgTXJ1Z2Fsc2tpOyBCZXJuaWUgVm9seiAodm9seik7IE1h
cmNpbiBTaW9kZWxza2k7IE1pY2hhZWwgQy4gUmljaGFyZHNvbjsgU2hlbmcgSmlhbmc7IFRlZCBM
ZW1vbjsgQW5kcmV3IFlvdXJ0Y2hlbmtvIChheW91cnRjaCk7IFRvbWVrIE1ydWdhbHNraTsgU2hl
bmcgSmlhbmc7IE1hcmNpbiBTaW9kZWxza2k7IE1pY2hhZWwgUmljaGFyZHNvbjsgVGVkIExlbW9u
DQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWRoY3dnLWRoYy1y
ZmMzMzE1YmlzLTAxLnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1kaGN3Zy1k
aGMtcmZjMzMxNWJpcy0wMS50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkg
QmVybmllIFZvbHogYW5kIHBvc3RlZCB0byB0aGUNCklFVEYgcmVwb3NpdG9yeS4NCg0KTmFtZToJ
CWRyYWZ0LWRoY3dnLWRoYy1yZmMzMzE1YmlzDQpSZXZpc2lvbjoJMDENClRpdGxlOgkJRHluYW1p
YyBIb3N0IENvbmZpZ3VyYXRpb24gUHJvdG9jb2wgZm9yIElQdjYgKERIQ1B2NikgYmlzDQpEb2N1
bWVudCBkYXRlOgkyMDE0LTA1LTE5DQpHcm91cDoJCUluZGl2aWR1YWwgU3VibWlzc2lvbg0KUGFn
ZXM6CQkxMDgNClVSTDogICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRy
YWZ0cy9kcmFmdC1kaGN3Zy1kaGMtcmZjMzMxNWJpcy0wMS50eHQNClN0YXR1czogICAgICAgICBo
dHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1kaGN3Zy1kaGMtcmZjMzMxNWJp
cy8NCkh0bWxpemVkOiAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1kaGN3
Zy1kaGMtcmZjMzMxNWJpcy0wMQ0KRGlmZjogICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcv
cmZjZGlmZj91cmwyPWRyYWZ0LWRoY3dnLWRoYy1yZmMzMzE1YmlzLTAxDQoNCkFic3RyYWN0Og0K
ICAgVGhlIER5bmFtaWMgSG9zdCBDb25maWd1cmF0aW9uIFByb3RvY29sIGZvciBJUHY2IChESENQ
KSBlbmFibGVzIERIQ1ANCiAgIHNlcnZlcnMgdG8gcGFzcyBjb25maWd1cmF0aW9uIHBhcmFtZXRl
cnMgc3VjaCBhcyBJUHY2IG5ldHdvcmsNCiAgIGFkZHJlc3NlcyB0byBJUHY2IG5vZGVzLiAgSXQg
b2ZmZXJzIHRoZSBjYXBhYmlsaXR5IG9mIGF1dG9tYXRpYw0KICAgYWxsb2NhdGlvbiBvZiByZXVz
YWJsZSBuZXR3b3JrIGFkZHJlc3NlcyBhbmQgYWRkaXRpb25hbCBjb25maWd1cmF0aW9uDQogICBm
bGV4aWJpbGl0eS4gIFRoaXMgcHJvdG9jb2wgaXMgYSBzdGF0ZWZ1bCBjb3VudGVycGFydCB0byAi
SVB2Ng0KICAgU3RhdGVsZXNzIEFkZHJlc3MgQXV0b2NvbmZpZ3VyYXRpb24iIChSRkMgNDg2Miks
IGFuZCBjYW4gYmUgdXNlZA0KICAgc2VwYXJhdGVseSBvciBjb25jdXJyZW50bHkgd2l0aCB0aGUg
bGF0dGVyIHRvIG9idGFpbiBjb25maWd1cmF0aW9uDQogICBwYXJhbWV0ZXJzLg0KDQogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNv
dXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KdW50aWwgdGhlIGh0
bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4N
Cg0KVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0K


From nobody Wed May 21 11:41:49 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 CF3C41A036F for <dhcwg@ietfa.amsl.com>; Wed, 21 May 2014 11:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dfbahrPs9hBt for <dhcwg@ietfa.amsl.com>; Wed, 21 May 2014 11:41:45 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A7551A0280 for <dhcwg@ietf.org>; Wed, 21 May 2014 11:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8341; q=dns/txt; s=iport; t=1400697704; x=1401907304; h=from:to:subject:date:message-id:mime-version; bh=6bLcMcqm43VjI2SRyWzorDLIGXmQbLkBTlPDMHNszp8=; b=bafTpc/XTtLBCWTi/837I99cIDfsz3Hyw+0FtrBoE58ExcLJgYFsP2Oj pFRf8c7x3NOwOD2iHNkg1SXZexfNinXRar0b35j83E5X71L9jJVxBr59U O0ENtZnOpHBE2c5tPRw+kXLG36hQ23dV4XCHVcoZnef/R5Lktlb3VmE94 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8FAAnzfFOtJA2I/2dsb2JhbABZgkJHUljEGwGBDBZ0gicBBC1eASodORQSAQQTCAGIOA2hYrRnF4tAgl2DY4EVBK0SgzhtgUM
X-IronPort-AV: E=Sophos; i="4.98,881,1392163200"; d="scan'208,217"; a="45947912"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-3.cisco.com with ESMTP; 21 May 2014 18:41:44 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s4LIfhik017717 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Wed, 21 May 2014 18:41:44 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.63]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0123.003; Wed, 21 May 2014 13:41:43 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Agenda Items for Toronto (IETF-90, July 20-25)
Thread-Index: Ac91I2gIYqx1usMOTr2pSVooCnjj5A==
Date: Wed, 21 May 2014 18:41:42 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B033BD3@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.244.75]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B033BD3xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/7heL3ANyiDRdDR7eeVxfutqX6sA
Subject: [dhcwg] Agenda Items for Toronto (IETF-90, July 20-25)
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, 21 May 2014 18:41:47 -0000

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

Hi:

While still 2 months out, I did want to get folks to start thinking about p=
resenting at the DHC WG meeting in Toronto.

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

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

More details about the Toronto IETF can be found at http://www.ietf.org/mee=
ting/90/index.html.


-          Tomek & Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1B033BD3xmbrcdx04ciscoc_
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:1747876996;
	mso-list-type:hybrid;
	mso-list-template-ids:-53208082 427484132 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1805079178;
	mso-list-type:hybrid;
	mso-list-template-ids:-286487600 427484132 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While still 2 months out, I did want to get folks to=
 start thinking about presenting at the DHC WG meeting in Toronto.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please send us (<a href=3D"mailto:dhc-chairs@tools.i=
etf.org">dhc-chairs@tools.ietf.org</a>) requests for sessions and include:<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Name of session:<o:p></o:p></p>
<p class=3D"MsoNormal">Name of draft(s):<o:p></o:p></p>
<p class=3D"MsoNormal">Time requested:<o:p></o:p></p>
<p class=3D"MsoNormal">Presenter name(s):<o:p></o:p></p>
<p class=3D"MsoNormal">Brief description of what issues need discussing and=
 what you hope to accomplish by presenting:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">More details about the Toronto IETF can be found at =
<a href=3D"http://www.ietf.org/meeting/90/index.html">
http://www.ietf.org/meeting/90/index.html</a>.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Tomek &amp; Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B033BD3xmbrcdx04ciscoc_--


From nobody Wed May 21 11:56:02 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 AFBB31A0691 for <dhcwg@ietfa.amsl.com>; Wed, 21 May 2014 11:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cbV1rhWbQK4Q for <dhcwg@ietfa.amsl.com>; Wed, 21 May 2014 11:55:57 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C5A71A0280 for <dhcwg@ietf.org>; Wed, 21 May 2014 11:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7036; q=dns/txt; s=iport; t=1400698556; x=1401908156; h=from:to:cc:subject:date:message-id:mime-version; bh=FlAzo/HU7nIqO/UEPKp57OLUphcAjnshsQfOLawmilg=; b=A8HQdap/iGGePcbHKHS/dMY8nreQF9xLiYUhIwqUee1l6pWahnyronNK 7n6hcGis+WmdKdk+m142GHRWCLpvVjlX3C5K9/igHop29AWAFwtSSj9dW pnITJEKqeZyHsFA/Zp18lLJW8kCsZWIgzww6akH6p+zVtuq6hmpkBzSQt o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFABP2fFOtJA2H/2dsb2JhbABZgkJHUli7Hoh9AYEMFnSCJwEELUwSASpWJgEEAQ0NiDkN1lIXjh0xgzKBFQSbK5FngziCMA
X-IronPort-AV: E=Sophos; i="4.98,881,1392163200"; d="scan'208,217"; a="45955320"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-5.cisco.com with ESMTP; 21 May 2014 18:55:55 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s4LIttkn030848 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 21 May 2014 18:55:55 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.63]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Wed, 21 May 2014 13:55:55 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Sheng Jiang (jiangsheng@huawei.com)" <jiangsheng@huawei.com>
Thread-Topic: DHC WG Secretary
Thread-Index: Ac91JGqrZFN80vgIThOsWfMt1b6PzQ==
Date: Wed, 21 May 2014 18:55:54 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B033C72@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.244.75]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B033C72xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/bwl_V2dukLr17RXH2tQEa6m8fio
Cc: "Ted Lemon \(Ted.Lemon@nominum.com\)" <Ted.Lemon@nominum.com>
Subject: [dhcwg] DHC WG Secretary
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, 21 May 2014 18:55:58 -0000

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

An update regarding the DHC WG ...

Thanks to Sheng for volunteering to help out the DHC WG co-chairs as the DH=
C WG Secretary!!

Tomek and I look forward to working with him.

While this is a new roll to the DHC WG, it has been in use by other working=
 groups. And there is a draft being developed to define expanded responsibi=
lities over what was in RFC 2418 - see http://tools.ietf.org/html/draft-sec=
retaries-good-practices-03.

Tomek and I will work with Sheng to determine what responsibilities to pass=
 to him and when, and we will update the WG as appropriate.

Sheng will also continue to shepherd some WG documents as well.

Again, Tomek and I thank Sheng for stepping forward and volunteering for th=
is roll.


-          Tomek and Bernie




--_000_489D13FBFA9B3E41812EA89F188F018E1B033C72xmbrcdx04ciscoc_
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:864901883;
	mso-list-type:hybrid;
	mso-list-template-ids:-1516896036 427484132 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.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">An update regarding the DHC WG &#8230;<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks to Sheng for volunteering to help out the DHC=
 WG co-chairs as the DHC WG Secretary!!<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Tomek and I look forward to working with him.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While this is a new roll to the DHC WG, it has been =
in use by other working groups. And there is a draft being developed to def=
ine expanded responsibilities over what was in RFC 2418 &#8211; see
<a href=3D"http://tools.ietf.org/html/draft-secretaries-good-practices-03">=
http://tools.ietf.org/html/draft-secretaries-good-practices-03</a>.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Tomek and I will work with Sheng to determine what r=
esponsibilities to pass to him and when, and we will update the WG as appro=
priate.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Sheng will also continue to shepherd some WG documen=
ts as well.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Again, Tomek and I thank Sheng for stepping forward =
and volunteering for this roll.<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 and Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B033C72xmbrcdx04ciscoc_--


From nobody Wed May 21 18:14:48 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 80F501A0018 for <dhcwg@ietfa.amsl.com>; Wed, 21 May 2014 18:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level: 
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 2FvOofe-MusL for <dhcwg@ietfa.amsl.com>; Wed, 21 May 2014 18:14:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69B1C1A0011 for <dhcwg@ietf.org>; Wed, 21 May 2014 18:14:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHB15576; Thu, 22 May 2014 01:14:25 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 22 May 2014 02:14:12 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 22 May 2014 02:14:23 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.68]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Thu, 22 May 2014 09:14:16 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHC WG Secretary
Thread-Index: Ac91JGqrZFN80vgIThOsWfMt1b6PzQANa97w
Date: Thu, 22 May 2014 01:14:15 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AE7E503@nkgeml512-mbx.china.huawei.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B033C72@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B033C72@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_5D36713D8A4E7348A7E10DF7437A4B923AE7E503nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/QjQyckAMnIBY51sclTRXk4b4z7E
Cc: "Ted Lemon \(Ted.Lemon@nominum.com\)" <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] DHC WG Secretary
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, 22 May 2014 01:14:45 -0000

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

SXQgaXMgbXkgcGxlYXN1cmUgdG8gc2VydmUgYW5kIGNvbnRyaWJ1dGUgbW9yZS4gRm9yIGxhc3Qg
c2V2ZXJhbCB5ZWFycywgREhDIGlzIGEgYnVzeSBhbmQgZnJ1aXRmdWwgd29ya2luZyBncm91cC4g
Q2hhaXJzIGFuZCBBRHMgaGF2ZSBkb25lIGEgbG90IHdvcmtzLiBIb3BlIG15IGpvaW5pbmcgY291
bGQgc2hhcmUgdGhlaXIgaGVhdnkgd29ya3MuDQoNCkJlc3QgcmVnYXJkcywNCg0KU2hlbmcNCg0K
RnJvbTogQmVybmllIFZvbHogKHZvbHopIFttYWlsdG86dm9sekBjaXNjby5jb21dDQpTZW50OiBU
aHVyc2RheSwgTWF5IDIyLCAyMDE0IDI6NTYgQU0NClRvOiBkaGN3Z0BpZXRmLm9yZzsgU2hlbmcg
SmlhbmcNCkNjOiBUZWQgTGVtb24gKFRlZC5MZW1vbkBub21pbnVtLmNvbSkNClN1YmplY3Q6IERI
QyBXRyBTZWNyZXRhcnkNCg0KQW4gdXBkYXRlIHJlZ2FyZGluZyB0aGUgREhDIFdHIOKApg0KDQpU
aGFua3MgdG8gU2hlbmcgZm9yIHZvbHVudGVlcmluZyB0byBoZWxwIG91dCB0aGUgREhDIFdHIGNv
LWNoYWlycyBhcyB0aGUgREhDIFdHIFNlY3JldGFyeSEhDQoNClRvbWVrIGFuZCBJIGxvb2sgZm9y
d2FyZCB0byB3b3JraW5nIHdpdGggaGltLg0KDQpXaGlsZSB0aGlzIGlzIGEgbmV3IHJvbGwgdG8g
dGhlIERIQyBXRywgaXQgaGFzIGJlZW4gaW4gdXNlIGJ5IG90aGVyIHdvcmtpbmcgZ3JvdXBzLiBB
bmQgdGhlcmUgaXMgYSBkcmFmdCBiZWluZyBkZXZlbG9wZWQgdG8gZGVmaW5lIGV4cGFuZGVkIHJl
c3BvbnNpYmlsaXRpZXMgb3ZlciB3aGF0IHdhcyBpbiBSRkMgMjQxOCDigJMgc2VlIGh0dHA6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXNlY3JldGFyaWVzLWdvb2QtcHJhY3RpY2VzLTAzLg0K
DQpUb21layBhbmQgSSB3aWxsIHdvcmsgd2l0aCBTaGVuZyB0byBkZXRlcm1pbmUgd2hhdCByZXNw
b25zaWJpbGl0aWVzIHRvIHBhc3MgdG8gaGltIGFuZCB3aGVuLCBhbmQgd2Ugd2lsbCB1cGRhdGUg
dGhlIFdHIGFzIGFwcHJvcHJpYXRlLg0KDQpTaGVuZyB3aWxsIGFsc28gY29udGludWUgdG8gc2hl
cGhlcmQgc29tZSBXRyBkb2N1bWVudHMgYXMgd2VsbC4NCg0KQWdhaW4sIFRvbWVrIGFuZCBJIHRo
YW5rIFNoZW5nIGZvciBzdGVwcGluZyBmb3J3YXJkIGFuZCB2b2x1bnRlZXJpbmcgZm9yIHRoaXMg
cm9sbC4NCg0KDQotICAgICAgICBUb21layBhbmQgQmVybmllDQoNCg0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTrlrovkvZM7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1
IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBh
bm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
VGFob21hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6IlxA5a6L5L2TIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30N
Ci8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYu
TXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpi
bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5
cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7
DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1z
b0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdyYXBoDQoJe21zby1zdHlsZS1wcmlvcml0
eTozNDsNCgltYXJnaW4tdG9wOjBjbTsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1hcmdpbi1ib3R0
b206MGNtOw0KCW1hcmdpbi1sZWZ0OjM2LjBwdDsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30N
CnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6d2luZG93dGV4dDt9DQpzcGFuLkVt
YWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1
bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpA
cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBw
dCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNl
Y3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlk
Ojg2NDkwMTg4MzsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10ZW1wbGF0ZS1p
ZHM6LTE1MTY4OTYwMzYgNDI3NDg0MTMyIDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4
NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwwOmxldmVs
MQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6LTsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt
c2VyaWYiOw0KCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJbXNvLWJpZGktZm9u
dC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJe21zby1sZXZl
bC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10
YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWlu
ZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2
ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrv
gqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30N
CkBsaXN0IGwwOmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNv
LWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1u
dW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5
OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVs
bGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNv
LWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9u
dC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51
bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFi
LXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRl
bnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJ
bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0
Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGww
OmxldmVsOA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRl
eHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0
aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBO
ZXciO30NCkBsaXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7
DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQt
ZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQp1bA0KCXttYXJn
aW4tYm90dG9tOjBjbTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86
c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2Vu
ZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVk
aXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+
PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJaSC1DTiIgbGluaz0iYmx1
ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Nv
bG9yOiMxRjQ5N0QiPkl0IGlzIG15IHBsZWFzdXJlIHRvIHNlcnZlIGFuZCBjb250cmlidXRlIG1v
cmUuIEZvciBsYXN0IHNldmVyYWwgeWVhcnMsIERIQyBpcyBhIGJ1c3kgYW5kIGZydWl0ZnVsIHdv
cmtpbmcgZ3JvdXAuIENoYWlycyBhbmQgQURzIGhhdmUgZG9uZSBhIGxvdCB3b3Jrcy4gSG9wZSBt
eSBqb2luaW5nIGNvdWxkIHNoYXJlDQogdGhlaXIgaGVhdnkgd29ya3MuPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtjb2xvcjojMUY0OTdEIj5CZXN0IHJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjVwdDtjb2xvcjojMUY0OTdEIj5TaGVuZzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBj
bSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6
c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
IEJlcm5pZSBWb2x6ICh2b2x6KSBbbWFpbHRvOnZvbHpAY2lzY28uY29tXQ0KPGJyPg0KPGI+U2Vu
dDo8L2I+IFRodXJzZGF5LCBNYXkgMjIsIDIwMTQgMjo1NiBBTTxicj4NCjxiPlRvOjwvYj4gZGhj
d2dAaWV0Zi5vcmc7IFNoZW5nIEppYW5nPGJyPg0KPGI+Q2M6PC9iPiBUZWQgTGVtb24gKFRlZC5M
ZW1vbkBub21pbnVtLmNvbSk8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gREhDIFdHIFNlY3JldGFyeTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkFuIHVwZGF0ZSByZWdhcmRpbmcgdGhl
IERIQyBXRyDigKY8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRoYW5rcyB0byBTaGVuZyBmb3Igdm9sdW50
ZWVyaW5nIHRvIGhlbHAgb3V0IHRoZSBESEMgV0cgY28tY2hhaXJzIGFzIHRoZSBESEMgV0cgU2Vj
cmV0YXJ5ISE8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRvbWVrIGFuZCBJIGxvb2sgZm9yd2FyZCB0byB3
b3JraW5nIHdpdGggaGltLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+V2hpbGUgdGhpcyBpcyBhIG5ldyBy
b2xsIHRvIHRoZSBESEMgV0csIGl0IGhhcyBiZWVuIGluIHVzZSBieSBvdGhlciB3b3JraW5nIGdy
b3Vwcy4gQW5kIHRoZXJlIGlzIGEgZHJhZnQgYmVpbmcgZGV2ZWxvcGVkIHRvIGRlZmluZSBleHBh
bmRlZCByZXNwb25zaWJpbGl0aWVzIG92ZXIgd2hhdCB3YXMgaW4gUkZDIDI0MTgg4oCTIHNlZQ0K
PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtc2VjcmV0YXJpZXMtZ29v
ZC1wcmFjdGljZXMtMDMiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXNlY3JldGFy
aWVzLWdvb2QtcHJhY3RpY2VzLTAzPC9hPi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRvbWVrIGFuZCBJ
IHdpbGwgd29yayB3aXRoIFNoZW5nIHRvIGRldGVybWluZSB3aGF0IHJlc3BvbnNpYmlsaXRpZXMg
dG8gcGFzcyB0byBoaW0gYW5kIHdoZW4sIGFuZCB3ZSB3aWxsIHVwZGF0ZSB0aGUgV0cgYXMgYXBw
cm9wcmlhdGUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5TaGVuZyB3aWxsIGFsc28gY29udGludWUgdG8g
c2hlcGhlcmQgc29tZSBXRyBkb2N1bWVudHMgYXMgd2VsbC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkFn
YWluLCBUb21layBhbmQgSSB0aGFuayBTaGVuZyBmb3Igc3RlcHBpbmcgZm9yd2FyZCBhbmQgdm9s
dW50ZWVyaW5nIGZvciB0aGlzIHJvbGwuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBw
dDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMiI+PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gbGFu
Zz0iRU4tVVMiPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPi08c3BhbiBzdHlsZT0iZm9u
dDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxz
cGFuIGxhbmc9IkVOLVVTIj5Ub21layBhbmQgQmVybmllPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
Ym9keT4NCjwvaHRtbD4NCg==

--_000_5D36713D8A4E7348A7E10DF7437A4B923AE7E503nkgeml512mbxchi_--


From nobody Wed May 21 19:14:15 2014
Return-Path: <leaf.yeh.sdo@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 338071A004D for <dhcwg@ietfa.amsl.com>; Wed, 21 May 2014 19:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5J_FQmWotNp3 for <dhcwg@ietfa.amsl.com>; Wed, 21 May 2014 19:14:09 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED03D1A0051 for <dhcwg@ietf.org>; Wed, 21 May 2014 19:14:08 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id jt11so2003077pbb.27 for <dhcwg@ietf.org>; Wed, 21 May 2014 19:14:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:thread-index:content-language; bh=hy35irDI7yketlqZJSjMc0WGAHB39jOXLbbKXrk7DY8=; b=t/YYfOFYPaVyLYloSDd6XQJtBEGlfqpBii+Sign2lPG127fXvw+teiRTKU5tXgdnCq IgNfnJlxok+uFEkijxrfkqUI7Ntek4UW7CBhr67w+SDsORLmCBHFZTQ/cPTcu5H3K4U6 xwcNW9EElH59uSpvPoekesNrZWBFw7fGF4p+zIh/Oo3HKapKC7euxGO9QeyjuMksj0co Qc6FwJzKzc40nspRtGfYTTllHDzwd2W99opXKiWVP+gG7Xn1mpZoIskwr0p/SXNko5BI A1mFP7UR6mxrYLfZGoIVqAsXU4EzSiFTI8VrKYb1lRM8mfW4HnSM2xPoEcKwz3KI5lkf mEpQ==
X-Received: by 10.66.139.201 with SMTP id ra9mr60057060pab.84.1400724847841; Wed, 21 May 2014 19:14:07 -0700 (PDT)
Received: from PC ([118.244.255.8]) by mx.google.com with ESMTPSA id ec2sm10236506pbc.63.2014.05.21.19.13.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 21 May 2014 19:14:07 -0700 (PDT)
X-Google-Original-Message-ID: <009301cf7563$7eceae00$7c6c0a00$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Sheng Jiang'" <jiangsheng@huawei.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B033C72@xmb-rcd-x04.cisco.com> <5D36713D8A4E7348A7E10DF7437A4B923AE7E503@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE7E503@nkgeml512-mbx.china.huawei.com>
Date: Thu, 22 May 2014 10:13:47 +0800
Message-ID: <537d5d6f.42b6440a.0424.ffffc338@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0094_01CF75A6.8CF1EE00"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac91JGqrZFN80vgIThOsWfMt1b6PzQANa97wAAIUiJA=
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/fPX5IjODUadNE7xCWbS_hmkhvtw
Cc: dhcwg@ietf.org, 'Ted Lemon' <Ted.Lemon@nominum.com>, "'Bernie Volz \(volz\)'" <volz@cisco.com>
Subject: Re: [dhcwg] DHC WG Secretary
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, 22 May 2014 02:14:11 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0094_01CF75A6.8CF1EE00
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Congrats!

=20

=20

Best Regards,

Leaf

=20

=20

=20

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Sheng Jiang
Sent: Thursday, May 22, 2014 9:14 AM
To: Bernie Volz (volz); dhcwg@ietf.org
Cc: Ted Lemon (Ted.Lemon@nominum.com)
Subject: Re: [dhcwg] DHC WG Secretary

=20

It is my pleasure to serve and contribute more. For last several years, =
DHC is a busy and fruitful working group. Chairs and ADs have done a lot =
works. Hope my joining could share their heavy works.

=20

Best regards,

=20

Sheng

=20

From: Bernie Volz (volz) [mailto:volz@cisco.com]=20
Sent: Thursday, May 22, 2014 2:56 AM
To: dhcwg@ietf.org; Sheng Jiang
Cc: Ted Lemon (Ted.Lemon@nominum.com)
Subject: DHC WG Secretary

=20

An update regarding the DHC WG =E2=80=A6

=20

Thanks to Sheng for volunteering to help out the DHC WG co-chairs as the =
DHC WG Secretary!!

=20

Tomek and I look forward to working with him.

=20

While this is a new roll to the DHC WG, it has been in use by other =
working groups. And there is a draft being developed to define expanded =
responsibilities over what was in RFC 2418 =E2=80=93 see =
http://tools.ietf.org/html/draft-secretaries-good-practices-03.

=20

Tomek and I will work with Sheng to determine what responsibilities to =
pass to him and when, and we will update the WG as appropriate.

=20

Sheng will also continue to shepherd some WG documents as well.

=20

Again, Tomek and I thank Sheng for stepping forward and volunteering for =
this roll.

=20

-          Tomek and Bernie

=20

=20

=20


------=_NextPart_000_0094_01CF75A6.8CF1EE00
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-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.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Char
	{mso-style-name:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC;
	font-family:"Calibri","sans-serif";}
span.EmailStyle22
	{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:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:864901883;
	mso-list-type:hybrid;
	mso-list-template-ids:-1516896036 427484132 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Congrats!<o:p></o:p></span></p><=
p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Best =
Regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Leaf<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><div=
><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> dhcwg =
[mailto:dhcwg-bounces@ietf.org] <b>On Behalf Of </b>Sheng =
Jiang<br><b>Sent:</b> Thursday, May 22, 2014 9:14 AM<br><b>To:</b> =
Bernie Volz (volz); dhcwg@ietf.org<br><b>Cc:</b> Ted Lemon =
(Ted.Lemon@nominum.com)<br><b>Subject:</b> Re: [dhcwg] DHC WG =
Secretary<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:#1F497D'>It is my pleasure =
to serve and contribute more. For last several years, DHC is a busy and =
fruitful working group. Chairs and ADs have done a lot works. Hope my =
joining could share their heavy works.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Sheng<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><div=
 style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bernie =
Volz (volz) [<a =
href=3D"mailto:volz@cisco.com">mailto:volz@cisco.com</a>] =
<br><b>Sent:</b> Thursday, May 22, 2014 2:56 AM<br><b>To:</b> <a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; Sheng =
Jiang<br><b>Cc:</b> Ted Lemon (<a =
href=3D"mailto:Ted.Lemon@nominum.com">Ted.Lemon@nominum.com</a>)<br><b>Su=
bject:</b> DHC WG Secretary<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>An update regarding the DHC WG =
=E2=80=A6<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Thanks to Sheng for volunteering to help out the DHC WG =
co-chairs as the DHC WG Secretary!!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Tomek and I look forward to working =
with him.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>While this is a new roll to the DHC WG, it has been in use =
by other working groups. And there is a draft being developed to define =
expanded responsibilities over what was in RFC 2418 =E2=80=93 see <a =
href=3D"http://tools.ietf.org/html/draft-secretaries-good-practices-03">h=
ttp://tools.ietf.org/html/draft-secretaries-good-practices-03</a>.<o:p></=
o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Tomek and I will work with Sheng to determine what =
responsibilities to pass to him and when, and we will update the WG as =
appropriate.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Sheng will also continue to shepherd some WG documents as =
well.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Again, Tomek and I thank Sheng for stepping forward and =
volunteering for this roll.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-US><span =
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US>Tomek and =
Bernie<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_0094_01CF75A6.8CF1EE00--


From nobody Thu May 22 20:16:33 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 22A951A0063; Thu, 22 May 2014 20:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0YqSlz1A_5x8; Thu, 22 May 2014 20:16:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 31F531A0064; Thu, 22 May 2014 20:16:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140523031630.26461.20781.idtracker@ietfa.amsl.com>
Date: Thu, 22 May 2014 20:16:30 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/AxtlVjvGp5THsyO7OzczgMaCeHY
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-dhcpv6-08.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2014 03:16:31 -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           : DHCPv4 over DHCPv6 Transport
        Authors         : Qi Sun
                          Yong Cui
                          Marcin Siodelski
                          Suresh Krishnan
                          Ian Farrer
	Filename        : draft-ietf-dhc-dhcpv4-over-dhcpv6-08.txt
	Pages           : 15
	Date            : 2014-05-22

Abstract:
   IPv4 connectivity is still needed as networks migrate towards IPv6.
   Users require IPv4 configuration even if the uplink to their service
   provider supports IPv6 only.  This document describes a mechanism for
   obtaining IPv4 configuration information dynamically in IPv6 networks
   by carrying DHCPv4 messages over DHCPv6 transport.  Two new DHCPv6
   messages and two new DHCPv6 options are defined for this purpose.


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

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

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


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

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


From nobody Sun May 25 06:43:39 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED6861A03B1 for <dhcwg@ietfa.amsl.com>; Sun, 25 May 2014 06:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QtBNBpJAk3iT for <dhcwg@ietfa.amsl.com>; Sun, 25 May 2014 06:43:33 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0A761A03AF for <dhcwg@ietf.org>; Sun, 25 May 2014 06:43:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19609; q=dns/txt; s=iport; t=1401025411; x=1402235011; h=from:to:cc:subject:date:message-id:mime-version; bh=mokPSOYOOYQtXyS9aeQgfa+o41MHSyBn2UJ6ZZTUnRQ=; b=B9bFMzVdmk7RNlb79NDp+eSeBPx1MUtQJQxzTkxNnNCDsYuNWObuTcWx QOtp0cYTLp4VTolFCBdge5RDAS+zY+lTBwMM0l6Iyg8repN8BkdqJcjKx 7GSpHs89YjMDwzjLnO0pd6htO+ZL83G89awLJ8QNMUM1EGgrtlaOvS/XP A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAPHygVOtJV2Z/2dsb2JhbABZgkJFUljCBAGBAxZ0gicBBC1BCxIBKlYmAQQODROIJ9dfF41wEQEfMYMygRUErRqDOIF2OQ
X-IronPort-AV: E=Sophos;i="4.98,906,1392163200";  d="scan'208,217";a="327794574"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 25 May 2014 13:43:28 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s4PDhShg004129 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 25 May 2014 13:43:28 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.136]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Sun, 25 May 2014 08:43:27 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: draft-ietf-dhc-dhcpv6-stateful-issues - Section 4.2. Placement of Status Codes
Thread-Index: Ac94GrJ1L1t9tvwxRrO4/K8YE7v9yA==
Date: Sun, 25 May 2014 13:43:26 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B04792A@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.245.27]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B04792Axmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/IQdtn7tuxvfZVuNevzrDCjKr-zo
Cc: "rob.shakir@bt.com" <rob.shakir@bt.com>
Subject: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues - Section 4.2. Placement of Status Codes
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, 25 May 2014 13:43:37 -0000

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

Rob Shakir from BT recently raised (to the authors) the issue of the placem=
ent of status codes for Advertise messages based on some operational experi=
ence. A few of us (Ole Troan, Marcin Siodelski, and Tomek Mrugalski) discus=
sed this via email. After our discussion, we are taking the conclusion to t=
he mailing list for feedback - please read and provide your feedback (conce=
rns/objections or support for the change).

Some Background:

The original reason for keeping the RFC 3315 Advertise behavior with respec=
t to IA_NA/IA_TA requests and NoAddrsAvail status code option  was to avoid=
 backwards compatibility issues (i.e., with existing clients). However, dur=
ing this discussion it turns out that there are already servers in the fiel=
d that, strictly speaking, weren't following RFC 3315 Advertise behavior an=
d only returning the NoAddrsAvail Status Code option encapsulated in the IA=
_* option (not at the global scope). Because at least some of these servers=
 are freely and widely available, we assume that if there had been issues, =
someone would have reported the problem.

Proposed Change:

Thus, we are planning to update the next revision of draft-ietf-dhc-dhcpv6-=
stateful-issues to change section 4.2, Placement of Status Codes, which wil=
l change RFC 3315 behavior and have the NoAddrsAvail status in Advertise me=
ssages move into the IA_* options rather than being a global scope option (=
i.e., follow how a Reply is formatted with respect to Status Code options).

More Detailed Information:

The possible Advertise responses when IA_NA and IA_PD are requested and one=
 or the other or both are not available are (ignoring other errors or issue=
s):


1. IA_NA - no addresses available, IA_PD - no prefix available

                A. Global scope status code with NoAddrsAvail, no IA_NA opt=
ion, IA_PD with status code of NoPrefixAvail

                B. IA_NA with status code of NoAddrsAvail, IA_PD with statu=
s code of NoPrefixAvail

                C. (b) but also with global scope status code with NoAddrsA=
vail



2. IA_NA - no addresses available, IA_PD - assigned

                A. Global scope status code with NoAddrsAvail, no IA_NA opt=
ion, IA_PD with prefix

                B. IA_NA with status code of NoAddrsAvail, IA_PD with prefi=
x

                C. (b) but also with global scope status code with NoAddrsA=
vail



3. IA_NA - assigned, IA_PD - no prefix available

                A. IA_NA with address, IA_PD with status code of NoPrefixAv=
ail



Note that if an IA_PD is not included, there are still 3 possible responses=
 for just IA_NA:

                A. Global scope status code with NoAddrsAvail, no IA_NA opt=
ion

                B. IA_NA with status code of NoAddrsAvail

                C. (b) but also with global scope status code with NoAddrsA=
vail



In all cases, if multiple IA_NA, multiple IA_PD, and multiple IA_TA options=
 are present, just extend appropriately.



And, we are, in all cases, recommending that form B. in the above is used.

Proposed Revised Section 4.2 Text:

The revised 4.2 text might thus end up being (the first 2 paragraphs are ex=
actly what is currently in the document, the rest of the section will be re=
placed):

++ START OF REVISED SECTION 4.2:



4.2. Placement of Status Code



In Reply messages IA specific status codes (i.e., NoAddrsAvail, NotOnlink, =
NoBinding, NoPrefixAvail) are encapsulated in the IA option.  In Advertisem=
ent messages the Status Code option with the NoAddrsAvail code is in the "g=
lobal" scope.  That makes sense when the failure case is fatal.  With the i=
ntroduction of multiple IA option types, there might be a case where a serv=
er is not willing to offer addresses, but might be willing to offer other s=
tateful option types.



While a Status Code option is implicitly bound to a specific type of IA, e.=
g. NoPrefixAvail is only applicable to IA_PD and NoAddrsAvail is only appli=
cable to IA_NA/IA_TA, it may be problematic to make this assumption for all=
 status codes.  Ideally the Status Code option should be encapsulated in th=
e IA option for all DHCP messages.  This makes Advertisement messages equal=
 to Reply messages.



However, how a server formats the Advertise message when addresses are not =
available has been a point of some confusion and implementations seem to va=
ry.



Therefore, the Proposed solution is:



Clients MUST be prepared to handle each of the following Advertise messages=
 formats when there are no addresses available (even when no IA_PD was in t=
he Solicit):

1. Advertise containing just a global scope status code option (of NoAddrsA=
vail) and no IA_NAs/IA_TAs.

2. Advertise containing the IA_NAs and/or IA_TAs with encapsulated status c=
ode option (of NoAddrsAvail) and no global scope status code option.

3. Advertise containing a global scope status code option (of NoAddrsAvail)=
 and IA_NAs and/or IA_TAs with a status code option (of NoAddrsAvail).



Servers MUST use the encapsulated status code option (of NoAddrsAvail) in a=
n IA_NA/IA_TA and not a global scope status code option (of NoAddrsAvail) w=
hen no addresses will be assigned (2 in the above list). This means that th=
e Advertise response matches the Reply response with respect to the handlin=
g of the NoAddrsAvail status.



Replace the following paragraph in RFC 3315, section 17.2.2:



   If the server will not assign any addresses to any IAs in a

   subsequent Request from the client, the server MUST send an Advertise

   message to the client that includes only a Status Code option with

   code NoAddrsAvail and a status message for the user, a Server

   Identifier option with the server's DUID, and a Client Identifier

   option with the client's DUID.



With:



   If the server will not assign any addresses to an IA in a

   subsequent Request from the client, the server MUST include

   the IA in the Advertise message with no addresses in the IA

   and a Status Code option in the IA containing status code

   NoAddrsAvail.



END OF SECTION 4.2 --



** ACTION NEEDED FROM YOU:



Does anyone have any concerns or objections regarding this change?



- Bernie


--_000_489D13FBFA9B3E41812EA89F188F018E1B04792Axmbrcdx04ciscoc_
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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Rob Shakir from BT recently raised (to the authors) =
the issue of the placement of status codes for Advertise messages based on =
some operational experience. A few of us (Ole Troan, Marcin Siodelski, and =
Tomek Mrugalski) discussed this via
 email. After our discussion, we are taking the conclusion to the mailing l=
ist for feedback &#8211; please read and provide your feedback (concerns/ob=
jections or support for the change).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Some Background:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The original reason for keeping the RFC 3315 Adverti=
se behavior with respect to IA_NA/IA_TA requests and NoAddrsAvail status co=
de option &nbsp;was to avoid backwards compatibility issues (i.e., with exi=
sting clients). However, during this discussion
 it turns out that there are already servers in the field that, strictly sp=
eaking, weren&#8217;t following RFC 3315 Advertise behavior and only return=
ing the NoAddrsAvail Status Code option encapsulated in the IA_* option (no=
t at the global scope). Because at least
 some of these servers are freely and widely available, we assume that if t=
here had been issues, someone would have reported the problem.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Proposed Change:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thus, we are planning to update the next revision of=
 draft-ietf-dhc-dhcpv6-stateful-issues to change section 4.2, Placement of =
Status Codes, which will change RFC 3315 behavior and have the NoAddrsAvail=
 status in Advertise messages move
 into the IA_* options rather than being a global scope option (i.e., follo=
w how a Reply is formatted with respect to Status Code options).<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">More Detailed Information:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The possible Advertise responses when IA_NA and IA_P=
D are requested and one or the other or both are not available are (ignorin=
g other errors or issues):<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">1. IA_NA - no addresses available, IA_PD - no pre=
fix available<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. Global scope status code with =
NoAddrsAvail, no IA_NA option, IA_PD with status code of NoPrefixAvail<o:p>=
</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. IA_NA with status code of NoAd=
drsAvail, IA_PD with status code of NoPrefixAvail<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. (b) but also with global scope=
 status code with NoAddrsAvail<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">2. IA_NA - no addresses available, IA_PD - assign=
ed<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. Global scope status code with =
NoAddrsAvail, no IA_NA option, IA_PD with prefix<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. IA_NA with status code of NoAd=
drsAvail, IA_PD with prefix<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. (b) but also with global scope=
 status code with NoAddrsAvail<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">3. IA_NA - assigned, IA_PD - no prefix available<=
o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. IA_NA with address, IA_PD with=
 status code of NoPrefixAvail<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Note that if an IA_PD is not included, there are =
still 3 possible responses for just IA_NA:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. Global scope status code with =
NoAddrsAvail, no IA_NA option<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. IA_NA with status code of NoAd=
drsAvail<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. (b) but also with global scope=
 status code with NoAddrsAvail<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">In all cases, if multiple IA_NA, multiple IA_PD, =
and multiple IA_TA options are present, just extend appropriately.<o:p></o:=
p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">And, we are, in all cases, recommending that form=
 B. in the above is used.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Proposed Revised Section 4.2 Text:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The revised 4.2 text might thus end up being (the fi=
rst 2 paragraphs are exactly what is currently in the document, the rest of=
 the section will be replaced):<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#43;&#43; START OF REVISED SECTION 4.2:<o:p></o:p><=
/p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">4.2. Placement of Status Code<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">In Reply messages IA specific status codes (i.e.,=
 NoAddrsAvail, NotOnlink, NoBinding, NoPrefixAvail) are encapsulated in the=
 IA option.&nbsp; In Advertisement messages the Status Code option with the=
 NoAddrsAvail code is in the &quot;global&quot; scope.&nbsp;
 That makes sense when the failure case is fatal.&nbsp; With the introducti=
on of multiple IA option types, there might be a case where a server is not=
 willing to offer addresses, but might be willing to offer other stateful o=
ption types.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">While a Status Code option is implicitly bound to=
 a specific type of IA, e.g. NoPrefixAvail is only applicable to IA_PD and =
NoAddrsAvail is only applicable to IA_NA/IA_TA, it may be problematic to ma=
ke this assumption for all status
 codes.&nbsp; Ideally the Status Code option should be encapsulated in the =
IA option for all DHCP messages.&nbsp; This makes Advertisement messages eq=
ual to Reply messages.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">However, how a server formats the Advertise messa=
ge when addresses are not available has been a point of some confusion and =
implementations seem to vary.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Therefore, the Proposed solution is:<o:p></o:p></=
p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Clients MUST be prepared to handle each of the fo=
llowing Advertise messages formats when there are no addresses available (e=
ven when no IA_PD was in the Solicit):<o:p></o:p></p>
<p class=3D"MsoPlainText">1. Advertise containing just a global scope statu=
s code option (of NoAddrsAvail) and no IA_NAs/IA_TAs.<o:p></o:p></p>
<p class=3D"MsoPlainText">2. Advertise containing the IA_NAs and/or IA_TAs =
with encapsulated status code option (of NoAddrsAvail) and no global scope =
status code option.<o:p></o:p></p>
<p class=3D"MsoPlainText">3. Advertise containing a global scope status cod=
e option (of NoAddrsAvail) and IA_NAs and/or IA_TAs with a status code opti=
on (of NoAddrsAvail).<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Servers MUST use the encapsulated status code opt=
ion (of NoAddrsAvail) in an IA_NA/IA_TA and not a global scope status code =
option (of NoAddrsAvail) when no addresses will be assigned (2 in the above=
 list). This means that the Advertise
 response matches the Reply response with respect to the handling of the No=
AddrsAvail status.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Replace the following paragraph in RFC 3315, sect=
ion 17.2.2:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; If the server will not assign any ad=
dresses to any IAs in a<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; subsequent Request from the client, =
the server MUST send an Advertise<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; message to the client that includes =
only a Status Code option with<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; code NoAddrsAvail and a status messa=
ge for the user, a Server<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; Identifier option with the server's =
DUID, and a Client Identifier<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; option with the client's DUID.<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">With:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; If the server will not assign any ad=
dresses to an IA in a<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; subsequent Request from the client, =
the server MUST include<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; the IA in the Advertise message with=
 no addresses in the IA<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; and a Status Code option in the IA c=
ontaining status code<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; NoAddrsAvail.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">END OF SECTION 4.2 --<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">** ACTION NEEDED FROM YOU:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Does anyone have any concerns or objections regar=
ding this change?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1B04792Axmbrcdx04ciscoc_--


From nobody Sun May 25 19:54:01 2014
Return-Path: <leaf.yeh.sdo@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 2D7491A0430; Sun, 25 May 2014 19:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AhbbHOv9cKXm; Sun, 25 May 2014 19:53:57 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 590581A0431; Sun, 25 May 2014 19:53:57 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id lf10so6847259pab.6 for <multiple recipients>; Sun, 25 May 2014 19:53:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:subject:date:mime-version:content-type :thread-index:content-language; bh=e6l2DGxMuV/RZClYIipD6AAyQflNStbstXAo3GXEmHM=; b=JrZAxToDYrVL/u7LCASxFJCjf+Gq0g8kF1BFTFpa5eL54QgkfZGjrKkP1CJpABkakR GJ6eQdJlXeA5MfN8fRs6sNgdKINQUcvaV93bCm/YCjful4VhIuFt0s/+1yoWcLi+Ax61 M+Dr3utp9WtnZF1SKU+gKE4Pt6H2F2Z7p9JkvgazgQ+KTwV8wHDqtn0yua0TcBQ3/BFR kBPhcZ25c9kBp5+4fWgdFDGnG76tlyOZghXdmUYmWALYR9hfyp8x3ETD4+fuKZD8p8zU NinD18gUbOHSc9TCFumzXZX8FIvFzhuP508GoikzjQLyDaKno8YQ1f4O/L6bgj30dvNC sG8Q==
X-Received: by 10.68.237.133 with SMTP id vc5mr24438923pbc.92.1401072834500; Sun, 25 May 2014 19:53:54 -0700 (PDT)
Received: from PC ([218.241.103.194]) by mx.google.com with ESMTPSA id ec2sm15523056pbc.63.2014.05.25.19.53.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 25 May 2014 19:53:53 -0700 (PDT)
Message-ID: <5382acc1.42b6440a.5361.ffff8363@mx.google.com>
X-Google-Original-Message-ID: <00c501cf788d$ba8c4330$2fa4c990$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>, "'Tomasz Mrugalski'" <tomasz.mrugalski@gmail.com>
Date: Mon, 26 May 2014 10:53:49 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C6_01CF78D0.C8AF8330"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac94ja1zHl9NfJkXSMiqk9XERg5MCw==
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/CFa9FG6UNiYNpD5BTQljccJDDzU
Cc: dhcwg@ietf.org, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: [dhcwg] Reply to Confirm in RFC3315
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, 26 May 2014 02:53:59 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00C6_01CF78D0.C8AF8330
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Got 2 questions on the text in Section 18.1.8-'Receipt of Reply Messages' of
RFC3315:

 

<quote>

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
<http://tools.ietf.org/html/rfc3315#section-17> section 17, and
client-initiated

   configuration as described in
<http://tools.ietf.org/html/rfc3315#section-18> section 18.  If the client
receives any

   Reply messages that do not indicate a NotOnLink status, the client

   can use the addresses in the IA and ignore any messages that indicate

   a NotOnLink status.

</quote>

 

1.       If the client receive an Reply message indicating 'NoBinding' (or
even ' NoAddrsAvail'), the above sounds the client can still use the address
in the IA. Why?

2.       Why does the client could ignore 'any message' indicating
'NotOnLink' (in the 2nd half of the above paragraph)? It sounds conflict
with the 1st half of the above paragraph, not?

 

 

Best Regards,

Leaf

 


------=_NextPart_000_00C6_01CF78D0.C8AF8330
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-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
h4
	{mso-style-priority:9;
	mso-style-link:"\6807\9898 4 Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:21.0pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.4Char
	{mso-style-name:"\6807\9898 4 Char";
	mso-style-priority:9;
	mso-style-link:"\6807\9898 4";
	font-family:"Courier New";
	font-weight:bold;}
span.HTMLChar
	{mso-style-name:"HTML \9884\8BBE\683C\5F0F Char";
	mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F";
	font-family:SimSun;}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:4793751;
	mso-list-type:hybrid;
	mso-list-template-ids:1871052910 425776660 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US>Got 2 =
questions on the text in Section 18.1.8-&#8216;Receipt of Reply =
Messages&#8217; of RFC3315:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US>&lt;quote&gt;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-indent:15.75pt'><span lang=3DEN-US>When the client =
receives a NotOnLink status from the server in<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;&nbsp; response to a Confirm =
message, the client performs DHCP server<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;&nbsp; solicitation, as =
described in <a =
href=3D"http://tools.ietf.org/html/rfc3315#section-17"><span =
style=3D'color:windowtext;text-decoration:none'>section 17</span></a>, =
and client-initiated<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;&nbsp; configuration as described in <a =
href=3D"http://tools.ietf.org/html/rfc3315#section-18"><span =
style=3D'color:windowtext;text-decoration:none'>section =
18</span></a>.&nbsp; If the client receives any<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;&nbsp; Reply messages that do =
<span style=3D'color:red'>not indicate a NotOnLink status, the =
client<o:p></o:p></span></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:red'>&nbsp;&nbsp; can use</span><span =
lang=3DEN-US> the addresses in the IA and<span style=3D'color:red'> =
ignore any messages</span> that indicate<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;&nbsp; a NotOnLink =
status.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>&lt;/quote&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:18.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-US><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US>If the client receive =
an Reply message indicating &#8216;NoBinding&#8217; (or even &#8216; =
NoAddrsAvail&#8217;), the above sounds the client can still use the =
address in the IA. Why?<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:18.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-US><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US>Why does the client =
could ignore &#8216;any message&#8217; indicating =
&#8216;NotOnLink&#8217; (in the 2<sup>nd</sup> half of the above =
paragraph)? It sounds conflict with the 1<sup>st</sup> half of the above =
paragraph, not?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Best Regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Leaf<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_00C6_01CF78D0.C8AF8330--


From nobody Mon May 26 03:54:15 2014
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C1DD1A00DE; Mon, 26 May 2014 03:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJY7qxyjJ3gH; Mon, 26 May 2014 03:54:07 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E4811A00C9; Mon, 26 May 2014 03:54:07 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id x12so7675979wgg.6 for <multiple recipients>; Mon, 26 May 2014 03:54:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=1O6nu2USqJhMyYcwQ6cqgS9X6MSj9bupSQLDQxk1qQM=; b=jXyiVw+C0TLHAYtJJhP3MCYuxisixEFcG33rzb0MRj8TH2GLbGgEJD1YUlG5qHllhx ivs6BPIq7hwx5WodDLron4yKMx0Kjn88UcV/bbwoz8XMCYAbSneSFefw6MkGCNEqXeav Z3QHEG8+imCP3Z2S7hYhaOH/dktLm0KbuO62Gsi37KkRlYUkZb5dH/IJsomDmA5SaaGB sk1hACPbJucOZ06WgdeFCc8cFEaeqrRzoQUq3FA/V2BMv8jbFu19nteq0xlr250qpLA9 YY/f9EmYHhWbXLeMZFH7x4cGvbxEB7CYtc0Hx6lAKmdPH7BiJ14mAgITqBEFKkYOkwxe 3KkA==
X-Received: by 10.180.11.9 with SMTP id m9mr26802796wib.51.1401101643293; Mon, 26 May 2014 03:54:03 -0700 (PDT)
Received: from ?IPv6:2001:470:71:10d:120b:a9ff:fe7b:e3f0? ([2001:470:71:10d:120b:a9ff:fe7b:e3f0]) by mx.google.com with ESMTPSA id fu10sm25941137wib.11.2014.05.26.03.54.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 May 2014 03:54:02 -0700 (PDT)
Message-ID: <53831D49.8020800@gmail.com>
Date: Mon, 26 May 2014 12:54:01 +0200
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>,  "'Bernie Volz (volz)'" <volz@cisco.com>, 'Tomasz Mrugalski' <tomasz.mrugalski@gmail.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com>
In-Reply-To: <5382acc1.42b6440a.5361.ffff8363@mx.google.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/89WSLSs6HaGr2VKmzGjJjwMzcRI
Cc: dhcwg@ietf.org, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
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, 26 May 2014 10:54:12 -0000

On 26/05/14 04:53, Leaf Yeh wrote:
> Got 2 questions on the text in Section 18.1.8-‘Receipt of Reply
> Messages’ of RFC3315:
> 
>  
> 
> <quote>
> 
> 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
> <http://tools.ietf.org/html/rfc3315#section-17>, and client-initiated
> 
>    configuration as described in section 18
> <http://tools.ietf.org/html/rfc3315#section-18>.  If the client receives any
> 
>    Reply messages that do not indicate a NotOnLink status, the client
> 
>    can usethe addresses in the IA andignore any messages that indicate
> 
>    a NotOnLink status.
> 
> </quote>
> 
>  
> 
> 1.       If the client receive an Reply message indicating ‘NoBinding’
> (or even ‘ NoAddrsAvail’), the above sounds the client can still use the
> address in the IA. Why?

I think the context of the paragraph is important. The client sends
Confirm to any available server and client may receive multiple Replies.
Typically, one of these Replies will not contain NotOnLink status (or
contain Success) to indicate that client can use the address. Other
servers will send NotOnLink because they are not configured for the
particular subnet or so. So, the purpose of this paragraph is just to
describe this scenario.

Of course, client may receive Replies with other status codes too, and
there are relevant sections that talk about client behavior in this
case". So a couple of lines down:

"
   The client examines the status code in each IA individually.  If the
   status code is NoAddrsAvail, the client has received no usable
   addresses in the IA and may choose to try obtaining addresses for the
   IA from another server.  The client uses addresses and other
   information from any IAs that do not contain a Status Code option
   with the NoAddrsAvail code.  If the client receives no addresses in
   any of the IAs, it may either try another server (perhaps restarting
   the DHCP server discovery process) or use the Information-request
   message to obtain other configuration information only.
"

So, I don't really think there is any conflict here.

Also, you indicate that the client could use the address even though
there is a NoAddrsAvail or NoBinding. But, the returned IA will not have
an address to be used, because server places just status code NoBinding
or NoAddrsAvail in the IA and nothing else.



> 
> 2.       Why does the client could ignore ‘any message’ indicating
> ‘NotOnLink’ (in the 2^nd half of the above paragraph)? It sounds
> conflict with the 1^st half of the above paragraph, not?
> 
>  

The way I read it is that when the client receives at least one Reply
that has no NotOnLink status code, it may use the address it desires to
use. Otherwise it performs solicitation.

Perhaps, it could be more precise and say something along the lines: if
none of the Reply messages received in response to a Confirm message
indicates success, the client performs solicitation. Otherwise, it may
use the address.

Marcin


From nobody Mon May 26 04:41:38 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA5051A0109; Mon, 26 May 2014 04:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2_tpvZU53Sr; Mon, 26 May 2014 04:41:34 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 180811A00F4; Mon, 26 May 2014 04:41:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4210; q=dns/txt; s=iport; t=1401104491; x=1402314091; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=pJwbxAfAtvmm+602wG6Dquy6QGwGZlu1YrgxiQyRPyk=; b=XlR/5iSc65PUk4R7Xh+o/jf1slgO1KnYekTVaZELnwsJn9dJPtE8vrGO If/B7FprXfJOkcKq+ckWvXN0ASjoQUbRfwCa3K9AFCTQ0AMZsKnTynAY/ P/v+QcVUl9aDNyNnuZAM2GY2oKT+z5flBaDNt7B6DXosYkczZMYZqmnkM Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFAN4ng1OtJV2P/2dsb2JhbABZgwdSWMIQAYEPFnSCJQEBAQMBOj8MBAIBCA4DBAEBAQoUCQchERQJCAEBBAENBQiIJgMJCA3SEA2GGheLQ3mBZTEHBoMlgRUEl32DM4t4hXKDOIFvJBw
X-IronPort-AV: E=Sophos;i="4.98,912,1392163200"; d="scan'208";a="328030924"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-4.cisco.com with ESMTP; 26 May 2014 11:41:30 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s4QBfU2b004580 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 May 2014 11:41:30 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.136]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Mon, 26 May 2014 06:41:30 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Marcin Siodelski <msiodelski@gmail.com>, Leaf Yeh <leaf.yeh.sdo@gmail.com>, "'Tomasz Mrugalski'" <tomasz.mrugalski@gmail.com>
Thread-Topic: [Dhcpv6bis] Reply to Confirm in RFC3315
Thread-Index: Ac94ja1zHl9NfJkXSMiqk9XERg5MCwAbQiyAAAkBxtA=
Date: Mon, 26 May 2014 11:41:30 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com>
In-Reply-To: <53831D49.8020800@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.245.27]
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/bpYJOHLm_xpQQi9ZFJAYnGgrcGo
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
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, 26 May 2014 11:41:36 -0000

I think we're talking about Reply to Confirm. If so, why would these contai=
n NoAddrsAvail/NoBinding? They don't. Confirm does not validate a particula=
r client's addresses/PDs or bindings. It only validates whether the address=
es/PDs are on link or not.

Other than global errors like UnspecFail, a Confirm will either contain Not=
OnLink or Success. Nothing else.

And, yes the idea was there could be multiple servers some of which may sen=
d NotOnLink (as they may be lacking the configuration) but others that send=
 Success. The Success on can be taken.

In general servers that aren't authoritative for a particular set of links =
should not respond.

- Bernie

-----Original Message-----
From: Marcin Siodelski [mailto:msiodelski@gmail.com]=20
Sent: Monday, May 26, 2014 6:54 AM
To: Leaf Yeh; Bernie Volz (volz); 'Tomasz Mrugalski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'
Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315



On 26/05/14 04:53, Leaf Yeh wrote:
> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply=20
> Messages' of RFC3315:
>=20
> =20
>=20
> <quote>
>=20
> When the client receives a NotOnLink status from the server in
>=20
>    response to a Confirm message, the client performs DHCP server
>=20
>    solicitation, as described in section 17=20
> <http://tools.ietf.org/html/rfc3315#section-17>, and client-initiated
>=20
>    configuration as described in section 18=20
> <http://tools.ietf.org/html/rfc3315#section-18>.  If the client=20
> receives any
>=20
>    Reply messages that do not indicate a NotOnLink status, the client
>=20
>    can usethe addresses in the IA andignore any messages that indicate
>=20
>    a NotOnLink status.
>=20
> </quote>
>=20
> =20
>=20
> 1.       If the client receive an Reply message indicating 'NoBinding'
> (or even ' NoAddrsAvail'), the above sounds the client can still use=20
> the address in the IA. Why?

I think the context of the paragraph is important. The client sends Confirm=
 to any available server and client may receive multiple Replies.
Typically, one of these Replies will not contain NotOnLink status (or conta=
in Success) to indicate that client can use the address. Other servers will=
 send NotOnLink because they are not configured for the particular subnet o=
r so. So, the purpose of this paragraph is just to describe this scenario.

Of course, client may receive Replies with other status codes too, and ther=
e are relevant sections that talk about client behavior in this case". So a=
 couple of lines down:

"
   The client examines the status code in each IA individually.  If the
   status code is NoAddrsAvail, the client has received no usable
   addresses in the IA and may choose to try obtaining addresses for the
   IA from another server.  The client uses addresses and other
   information from any IAs that do not contain a Status Code option
   with the NoAddrsAvail code.  If the client receives no addresses in
   any of the IAs, it may either try another server (perhaps restarting
   the DHCP server discovery process) or use the Information-request
   message to obtain other configuration information only.
"

So, I don't really think there is any conflict here.

Also, you indicate that the client could use the address even though there =
is a NoAddrsAvail or NoBinding. But, the returned IA will not have an addre=
ss to be used, because server places just status code NoBinding or NoAddrsA=
vail in the IA and nothing else.



>=20
> 2.       Why does the client could ignore 'any message' indicating
> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds=20
> conflict with the 1^st half of the above paragraph, not?
>=20
> =20

The way I read it is that when the client receives at least one Reply that =
has no NotOnLink status code, it may use the address it desires to use. Oth=
erwise it performs solicitation.

Perhaps, it could be more precise and say something along the lines: if non=
e of the Reply messages received in response to a Confirm message indicates=
 success, the client performs solicitation. Otherwise, it may use the addre=
ss.

Marcin


From nobody Mon May 26 04:55:42 2014
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 758071A011D; Mon, 26 May 2014 04:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xTxKKgQkmlb; Mon, 26 May 2014 04:55:38 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9C111A0111; Mon, 26 May 2014 04:55:37 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id q59so7839326wes.38 for <multiple recipients>; Mon, 26 May 2014 04:55:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=21BIYiXn2BFcxchX9Jk5yT16QIipX3mhYxkd16fshzM=; b=Vzpysxf9EEvmqtVtU5mod7bLkzUqhGrOSLbjcmoTQ0eNF43Ub9G9GMtDxGaWjKChBG g/K8hwbuEkPaFP52LKqJ9g+/IQpYmQzDdRNfLLmBD+nhc+QCPDqSI76FoP3i0p98pBbB BvG3Jte7pq6Ammskx8LsgMhBn9Zo6EDvUZq725D5/UTXkq7IoE52FntqjqVPNNCKO/tb aGaBBcifk1LVL7edUc+ok3bMgUTXLRRkCjpnLHXrwBuJV46jEG3MXSo8V+BaGjcXWC+N czF3Qp7CR06uaKsdPJSoQM0DQxZ9Dt6+dznyQNkU87ooi7hwCHGmWb9hfkQUm4OWTLU+ CKiQ==
X-Received: by 10.180.228.100 with SMTP id sh4mr27528949wic.40.1401105332867;  Mon, 26 May 2014 04:55:32 -0700 (PDT)
Received: from ?IPv6:2001:470:71:10d:120b:a9ff:fe7b:e3f0? ([2001:470:71:10d:120b:a9ff:fe7b:e3f0]) by mx.google.com with ESMTPSA id qq5sm26351849wic.10.2014.05.26.04.55.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 May 2014 04:55:32 -0700 (PDT)
Message-ID: <53832BB3.6000902@gmail.com>
Date: Mon, 26 May 2014 13:55:31 +0200
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/4A8i8XsaBIKGy0EYwVHvyDnAnfQ
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
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, 26 May 2014 11:55:39 -0000

Yes, NoAddrsAvail/NoBinding are not sent in response to Confirm. May 
point rather was that *even in a more general case* the server will not 
send addresses in the IA in which there is NoAddrsAvail or NoBinding. 
This comment was beyond the context of Confirm/Reply message exchange.

Marcin

On Mon 26 May 2014 13:41:30 CEST, Bernie Volz (volz) wrote:
> I think we're talking about Reply to Confirm. If so, why would these contain NoAddrsAvail/NoBinding? They don't. Confirm does not validate a particular client's addresses/PDs or bindings. It only validates whether the addresses/PDs are on link or not.
>
> Other than global errors like UnspecFail, a Confirm will either contain NotOnLink or Success. Nothing else.
>
> And, yes the idea was there could be multiple servers some of which may send NotOnLink (as they may be lacking the configuration) but others that send Success. The Success on can be taken.
>
> In general servers that aren't authoritative for a particular set of links should not respond.
>
> - Bernie
>
> -----Original Message-----
> From: Marcin Siodelski [mailto:msiodelski@gmail.com]
> Sent: Monday, May 26, 2014 6:54 AM
> To: Leaf Yeh; Bernie Volz (volz); 'Tomasz Mrugalski'
> Cc: dhcwg@ietf.org; 'dhcpv6bis'
> Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315
>
>
>
> On 26/05/14 04:53, Leaf Yeh wrote:
>> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply
>> Messages' of RFC3315:
>>
>>
>>
>> <quote>
>>
>> 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
>> <http://tools.ietf.org/html/rfc3315#section-17>, and client-initiated
>>
>>    configuration as described in section 18
>> <http://tools.ietf.org/html/rfc3315#section-18>.  If the client
>> receives any
>>
>>    Reply messages that do not indicate a NotOnLink status, the client
>>
>>    can usethe addresses in the IA andignore any messages that indicate
>>
>>    a NotOnLink status.
>>
>> </quote>
>>
>>
>>
>> 1.       If the client receive an Reply message indicating 'NoBinding'
>> (or even ' NoAddrsAvail'), the above sounds the client can still use
>> the address in the IA. Why?
>
> I think the context of the paragraph is important. The client sends Confirm to any available server and client may receive multiple Replies.
> Typically, one of these Replies will not contain NotOnLink status (or contain Success) to indicate that client can use the address. Other servers will send NotOnLink because they are not configured for the particular subnet or so. So, the purpose of this paragraph is just to describe this scenario.
>
> Of course, client may receive Replies with other status codes too, and there are relevant sections that talk about client behavior in this case". So a couple of lines down:
>
> "
>    The client examines the status code in each IA individually.  If the
>    status code is NoAddrsAvail, the client has received no usable
>    addresses in the IA and may choose to try obtaining addresses for the
>    IA from another server.  The client uses addresses and other
>    information from any IAs that do not contain a Status Code option
>    with the NoAddrsAvail code.  If the client receives no addresses in
>    any of the IAs, it may either try another server (perhaps restarting
>    the DHCP server discovery process) or use the Information-request
>    message to obtain other configuration information only.
> "
>
> So, I don't really think there is any conflict here.
>
> Also, you indicate that the client could use the address even though there is a NoAddrsAvail or NoBinding. But, the returned IA will not have an address to be used, because server places just status code NoBinding or NoAddrsAvail in the IA and nothing else.
>
>
>
>>
>> 2.       Why does the client could ignore 'any message' indicating
>> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds
>> conflict with the 1^st half of the above paragraph, not?
>>
>>
>
> The way I read it is that when the client receives at least one Reply that has no NotOnLink status code, it may use the address it desires to use. Otherwise it performs solicitation.
>
> Perhaps, it could be more precise and say something along the lines: if none of the Reply messages received in response to a Confirm message indicates success, the client performs solicitation. Otherwise, it may use the address.
>
> Marcin


From nobody Mon May 26 05:07:20 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 14A811A0126; Mon, 26 May 2014 05:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5a4YmIX_Yjq; Mon, 26 May 2014 05:07:13 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 997DD1A00F6; Mon, 26 May 2014 05:07:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8200; q=dns/txt; s=iport; t=1401106031; x=1402315631; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Kt3K9+FbjO6zQ9huPXUTHKtxkMTZIoePODH0rtrqFLc=; b=UoGa71zMSTV9RjB7MvNOn4P0gTO2UYMc67Lz/PjybYFvG2X0sl5o/B8f obNbCpkVYJRXvwxSdxEKRiz90d1w/86EPTeeP9vb+pNFzFdjeRMFbYAdD TCBAhP7FcQhuOFil9Nnhvh+hI/PgBqC+ENjiOk1ObAQK7IJ+mqW+guk5e A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFALYtg1OtJA2B/2dsb2JhbABZgwdSWIJqvycBGXYWdIIlAQEBAwEjEUUFBwQCAQgOAwQBAQECAgYdAwICAh8RFAEICAEBBA4FCIgmAwkIDbJunykNhhoXgSqKGXmBZRYbBwaCbzaBFQSXfYMzi3iFcoM4gW8kHA
X-IronPort-AV: E=Sophos;i="4.98,912,1392163200"; d="scan'208";a="47275375"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-3.cisco.com with ESMTP; 26 May 2014 12:07:10 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s4QC7Aqc028512 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 May 2014 12:07:10 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.136]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Mon, 26 May 2014 07:07:09 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Marcin Siodelski <msiodelski@gmail.com>
Thread-Topic: [Dhcpv6bis] Reply to Confirm in RFC3315
Thread-Index: Ac94ja1zHl9NfJkXSMiqk9XERg5MCwAbQiyAAAkBxtD//8kggIAAUv7Q
Date: Mon, 26 May 2014 12:07:09 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B049CB0@xmb-rcd-x04.cisco.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com>
In-Reply-To: <53832BB3.6000902@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.245.27]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/NV1XLMFYRHfJIwmb0ybh-hK91Dg
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
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, 26 May 2014 12:07:16 -0000

VGhlIG9ubHkgdHdvIGNhc2VzIHdoZXJlIE5vdE9uTGluayBzdGF0dXMgaXMgdXNlZCBpcyBpbiB0
aGUgcmVzcG9uc2UgdG8gUmVxdWVzdCBhbmQgQ29uZmlybS4NCg0KSW4gQ29uZmlybSBjYXNlIGl0
IGlzIGdsb2JhbCBsZXZlbCBzdGF0dXMuDQoNCkluIFJlcXVlc3QgY2FzZSBpdCBpcyB3aXRoaW4g
dGhlIElBIGFuZCBtZWFucyB0aGF0IHRoZSBjbGllbnQncyByZXF1ZXN0ZWQgYWRkcmVzc2VzIChv
ciBQRCkgaXMgbm90IG9uIHRoZSBsaW5rLiBObyBhZGRyZXNzZXMvUEQgc2hvdWxkIGJlIHJldHVy
bmVkIHRvIGNsaWVudCBmb3IgdGhhdCBJQS4gVGhlIFJlcXVlc3QgY2FzZSBpcyBhIGJpdCB3ZWly
ZCBpbiBvbmUgcmVzcGVjdCBhcyAxOC4xLjggc2F5czoNCg0KICAgV2hlbiB0aGUgY2xpZW50IHJl
Y2VpdmVzIGEgTm90T25MaW5rIHN0YXR1cyBmcm9tIHRoZSBzZXJ2ZXIgaW4NCiAgIHJlc3BvbnNl
IHRvIGEgUmVxdWVzdCwgdGhlIGNsaWVudCBjYW4gZWl0aGVyIHJlLWlzc3VlIHRoZSBSZXF1ZXN0
DQogICB3aXRob3V0IHNwZWNpZnlpbmcgYW55IGFkZHJlc3NlcyBvciByZXN0YXJ0IHRoZSBESENQ
IHNlcnZlciBkaXNjb3ZlcnkNCiAgIHByb2Nlc3MgKHNlZSBzZWN0aW9uIDE3KS4NCg0KVGhpcyBr
aW5kIG9mIGltcGxpZXMgdGhhdCBpdCBpcyAiZ2xvYmFsIi4NCg0KSSB0aGluayB0aGlzIGNhc2Ug
d2FzIHRvIGhhbmRsZSB0aGUgY2xpZW50IG1vdmluZyBiZXR3ZWVuIFNvbGljaXQgYW5kIFJlcXVl
c3QgKGJ1dCB3aXRoIHRoZSBzYW1lIHNlcnZlciBzdGlsbCByZXNwb25kaW5nIHNpbmNlIHRoZSBT
ZXJ2ZXIgRFVJRCBtYXRjaGVzKS4NCg0KSXQgaXMgYSBnb29kIHF1ZXN0aW9uIGFzIHRvIHdoZXRo
ZXIgd2Ugc2hvdWxkIG1ha2UgdGhpcyBzdGF0dXMgZ2xvYmFsIHJhdGhlciB0aGFuIElBIHNwZWNp
ZmljLiBJbiBpbiB0aGUgZW5kIHRoZXJlJ3MgcHJvYmFibHkgbm90IG11Y2ggaGFybSBpbiBsZWF2
aW5nIGl0IGFzIGlzIGJlY2F1c2UgaWYgdGhlIGNsaWVudCByZXN0YXJ0cyB0aGUgcHJvY2Vzcywg
aXQgd2lsbCBqdXN0IGdldCBiYWNrIHRoZSBvdGhlciBhZGRyZXNzZXMvUEQgdGhhdCBtaWdodCBo
YXZlIGJlZW4gYXNzaWduZWQgdG8gb3RoZXIgSUEgb3B0aW9ucyB0aGF0IGRpZCBub3QgcmVzdWx0
IGluIE5vdE9uTGluay4NCg0KLSBCZXJuaWUNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
CkZyb206IE1hcmNpbiBTaW9kZWxza2kgW21haWx0bzptc2lvZGVsc2tpQGdtYWlsLmNvbV0gDQpT
ZW50OiBNb25kYXksIE1heSAyNiwgMjAxNCA3OjU2IEFNDQpUbzogQmVybmllIFZvbHogKHZvbHop
DQpDYzogZGhjd2dAaWV0Zi5vcmc7ICdkaGNwdjZiaXMnOyBMZWFmIFllaDsgJ1RvbWFzeiBNcnVn
YWxza2knDQpTdWJqZWN0OiBSZTogW0RoY3B2NmJpc10gUmVwbHkgdG8gQ29uZmlybSBpbiBSRkMz
MzE1DQoNClllcywgTm9BZGRyc0F2YWlsL05vQmluZGluZyBhcmUgbm90IHNlbnQgaW4gcmVzcG9u
c2UgdG8gQ29uZmlybS4gTWF5IHBvaW50IHJhdGhlciB3YXMgdGhhdCAqZXZlbiBpbiBhIG1vcmUg
Z2VuZXJhbCBjYXNlKiB0aGUgc2VydmVyIHdpbGwgbm90IHNlbmQgYWRkcmVzc2VzIGluIHRoZSBJ
QSBpbiB3aGljaCB0aGVyZSBpcyBOb0FkZHJzQXZhaWwgb3IgTm9CaW5kaW5nLiANClRoaXMgY29t
bWVudCB3YXMgYmV5b25kIHRoZSBjb250ZXh0IG9mIENvbmZpcm0vUmVwbHkgbWVzc2FnZSBleGNo
YW5nZS4NCg0KTWFyY2luDQoNCk9uIE1vbiAyNiBNYXkgMjAxNCAxMzo0MTozMCBDRVNULCBCZXJu
aWUgVm9seiAodm9seikgd3JvdGU6DQo+IEkgdGhpbmsgd2UncmUgdGFsa2luZyBhYm91dCBSZXBs
eSB0byBDb25maXJtLiBJZiBzbywgd2h5IHdvdWxkIHRoZXNlIGNvbnRhaW4gTm9BZGRyc0F2YWls
L05vQmluZGluZz8gVGhleSBkb24ndC4gQ29uZmlybSBkb2VzIG5vdCB2YWxpZGF0ZSBhIHBhcnRp
Y3VsYXIgY2xpZW50J3MgYWRkcmVzc2VzL1BEcyBvciBiaW5kaW5ncy4gSXQgb25seSB2YWxpZGF0
ZXMgd2hldGhlciB0aGUgYWRkcmVzc2VzL1BEcyBhcmUgb24gbGluayBvciBub3QuDQo+DQo+IE90
aGVyIHRoYW4gZ2xvYmFsIGVycm9ycyBsaWtlIFVuc3BlY0ZhaWwsIGEgQ29uZmlybSB3aWxsIGVp
dGhlciBjb250YWluIE5vdE9uTGluayBvciBTdWNjZXNzLiBOb3RoaW5nIGVsc2UuDQo+DQo+IEFu
ZCwgeWVzIHRoZSBpZGVhIHdhcyB0aGVyZSBjb3VsZCBiZSBtdWx0aXBsZSBzZXJ2ZXJzIHNvbWUg
b2Ygd2hpY2ggbWF5IHNlbmQgTm90T25MaW5rIChhcyB0aGV5IG1heSBiZSBsYWNraW5nIHRoZSBj
b25maWd1cmF0aW9uKSBidXQgb3RoZXJzIHRoYXQgc2VuZCBTdWNjZXNzLiBUaGUgU3VjY2VzcyBv
biBjYW4gYmUgdGFrZW4uDQo+DQo+IEluIGdlbmVyYWwgc2VydmVycyB0aGF0IGFyZW4ndCBhdXRo
b3JpdGF0aXZlIGZvciBhIHBhcnRpY3VsYXIgc2V0IG9mIGxpbmtzIHNob3VsZCBub3QgcmVzcG9u
ZC4NCj4NCj4gLSBCZXJuaWUNCj4NCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJv
bTogTWFyY2luIFNpb2RlbHNraSBbbWFpbHRvOm1zaW9kZWxza2lAZ21haWwuY29tXQ0KPiBTZW50
OiBNb25kYXksIE1heSAyNiwgMjAxNCA2OjU0IEFNDQo+IFRvOiBMZWFmIFllaDsgQmVybmllIFZv
bHogKHZvbHopOyAnVG9tYXN6IE1ydWdhbHNraScNCj4gQ2M6IGRoY3dnQGlldGYub3JnOyAnZGhj
cHY2YmlzJw0KPiBTdWJqZWN0OiBSZTogW0RoY3B2NmJpc10gUmVwbHkgdG8gQ29uZmlybSBpbiBS
RkMzMzE1DQo+DQo+DQo+DQo+IE9uIDI2LzA1LzE0IDA0OjUzLCBMZWFmIFllaCB3cm90ZToNCj4+
IEdvdCAyIHF1ZXN0aW9ucyBvbiB0aGUgdGV4dCBpbiBTZWN0aW9uIDE4LjEuOC0nUmVjZWlwdCBv
ZiBSZXBseSANCj4+IE1lc3NhZ2VzJyBvZiBSRkMzMzE1Og0KPj4NCj4+DQo+Pg0KPj4gPHF1b3Rl
Pg0KPj4NCj4+IFdoZW4gdGhlIGNsaWVudCByZWNlaXZlcyBhIE5vdE9uTGluayBzdGF0dXMgZnJv
bSB0aGUgc2VydmVyIGluDQo+Pg0KPj4gICAgcmVzcG9uc2UgdG8gYSBDb25maXJtIG1lc3NhZ2Us
IHRoZSBjbGllbnQgcGVyZm9ybXMgREhDUCBzZXJ2ZXINCj4+DQo+PiAgICBzb2xpY2l0YXRpb24s
IGFzIGRlc2NyaWJlZCBpbiBzZWN0aW9uIDE3IA0KPj4gPGh0dHA6Ly90b29scy5pZXRmLm9yZy9o
dG1sL3JmYzMzMTUjc2VjdGlvbi0xNz4sIGFuZCBjbGllbnQtaW5pdGlhdGVkDQo+Pg0KPj4gICAg
Y29uZmlndXJhdGlvbiBhcyBkZXNjcmliZWQgaW4gc2VjdGlvbiAxOCANCj4+IDxodHRwOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9yZmMzMzE1I3NlY3Rpb24tMTg+LiAgSWYgdGhlIGNsaWVudCANCj4+
IHJlY2VpdmVzIGFueQ0KPj4NCj4+ICAgIFJlcGx5IG1lc3NhZ2VzIHRoYXQgZG8gbm90IGluZGlj
YXRlIGEgTm90T25MaW5rIHN0YXR1cywgdGhlIGNsaWVudA0KPj4NCj4+ICAgIGNhbiB1c2V0aGUg
YWRkcmVzc2VzIGluIHRoZSBJQSBhbmRpZ25vcmUgYW55IG1lc3NhZ2VzIHRoYXQgDQo+PiBpbmRp
Y2F0ZQ0KPj4NCj4+ICAgIGEgTm90T25MaW5rIHN0YXR1cy4NCj4+DQo+PiA8L3F1b3RlPg0KPj4N
Cj4+DQo+Pg0KPj4gMS4gICAgICAgSWYgdGhlIGNsaWVudCByZWNlaXZlIGFuIFJlcGx5IG1lc3Nh
Z2UgaW5kaWNhdGluZyAnTm9CaW5kaW5nJw0KPj4gKG9yIGV2ZW4gJyBOb0FkZHJzQXZhaWwnKSwg
dGhlIGFib3ZlIHNvdW5kcyB0aGUgY2xpZW50IGNhbiBzdGlsbCB1c2UgDQo+PiB0aGUgYWRkcmVz
cyBpbiB0aGUgSUEuIFdoeT8NCj4NCj4gSSB0aGluayB0aGUgY29udGV4dCBvZiB0aGUgcGFyYWdy
YXBoIGlzIGltcG9ydGFudC4gVGhlIGNsaWVudCBzZW5kcyBDb25maXJtIHRvIGFueSBhdmFpbGFi
bGUgc2VydmVyIGFuZCBjbGllbnQgbWF5IHJlY2VpdmUgbXVsdGlwbGUgUmVwbGllcy4NCj4gVHlw
aWNhbGx5LCBvbmUgb2YgdGhlc2UgUmVwbGllcyB3aWxsIG5vdCBjb250YWluIE5vdE9uTGluayBz
dGF0dXMgKG9yIGNvbnRhaW4gU3VjY2VzcykgdG8gaW5kaWNhdGUgdGhhdCBjbGllbnQgY2FuIHVz
ZSB0aGUgYWRkcmVzcy4gT3RoZXIgc2VydmVycyB3aWxsIHNlbmQgTm90T25MaW5rIGJlY2F1c2Ug
dGhleSBhcmUgbm90IGNvbmZpZ3VyZWQgZm9yIHRoZSBwYXJ0aWN1bGFyIHN1Ym5ldCBvciBzby4g
U28sIHRoZSBwdXJwb3NlIG9mIHRoaXMgcGFyYWdyYXBoIGlzIGp1c3QgdG8gZGVzY3JpYmUgdGhp
cyBzY2VuYXJpby4NCj4NCj4gT2YgY291cnNlLCBjbGllbnQgbWF5IHJlY2VpdmUgUmVwbGllcyB3
aXRoIG90aGVyIHN0YXR1cyBjb2RlcyB0b28sIGFuZCB0aGVyZSBhcmUgcmVsZXZhbnQgc2VjdGlv
bnMgdGhhdCB0YWxrIGFib3V0IGNsaWVudCBiZWhhdmlvciBpbiB0aGlzIGNhc2UiLiBTbyBhIGNv
dXBsZSBvZiBsaW5lcyBkb3duOg0KPg0KPiAiDQo+ICAgIFRoZSBjbGllbnQgZXhhbWluZXMgdGhl
IHN0YXR1cyBjb2RlIGluIGVhY2ggSUEgaW5kaXZpZHVhbGx5LiAgSWYgdGhlDQo+ICAgIHN0YXR1
cyBjb2RlIGlzIE5vQWRkcnNBdmFpbCwgdGhlIGNsaWVudCBoYXMgcmVjZWl2ZWQgbm8gdXNhYmxl
DQo+ICAgIGFkZHJlc3NlcyBpbiB0aGUgSUEgYW5kIG1heSBjaG9vc2UgdG8gdHJ5IG9idGFpbmlu
ZyBhZGRyZXNzZXMgZm9yIHRoZQ0KPiAgICBJQSBmcm9tIGFub3RoZXIgc2VydmVyLiAgVGhlIGNs
aWVudCB1c2VzIGFkZHJlc3NlcyBhbmQgb3RoZXINCj4gICAgaW5mb3JtYXRpb24gZnJvbSBhbnkg
SUFzIHRoYXQgZG8gbm90IGNvbnRhaW4gYSBTdGF0dXMgQ29kZSBvcHRpb24NCj4gICAgd2l0aCB0
aGUgTm9BZGRyc0F2YWlsIGNvZGUuICBJZiB0aGUgY2xpZW50IHJlY2VpdmVzIG5vIGFkZHJlc3Nl
cyBpbg0KPiAgICBhbnkgb2YgdGhlIElBcywgaXQgbWF5IGVpdGhlciB0cnkgYW5vdGhlciBzZXJ2
ZXIgKHBlcmhhcHMgcmVzdGFydGluZw0KPiAgICB0aGUgREhDUCBzZXJ2ZXIgZGlzY292ZXJ5IHBy
b2Nlc3MpIG9yIHVzZSB0aGUgSW5mb3JtYXRpb24tcmVxdWVzdA0KPiAgICBtZXNzYWdlIHRvIG9i
dGFpbiBvdGhlciBjb25maWd1cmF0aW9uIGluZm9ybWF0aW9uIG9ubHkuDQo+ICINCj4NCj4gU28s
IEkgZG9uJ3QgcmVhbGx5IHRoaW5rIHRoZXJlIGlzIGFueSBjb25mbGljdCBoZXJlLg0KPg0KPiBB
bHNvLCB5b3UgaW5kaWNhdGUgdGhhdCB0aGUgY2xpZW50IGNvdWxkIHVzZSB0aGUgYWRkcmVzcyBl
dmVuIHRob3VnaCB0aGVyZSBpcyBhIE5vQWRkcnNBdmFpbCBvciBOb0JpbmRpbmcuIEJ1dCwgdGhl
IHJldHVybmVkIElBIHdpbGwgbm90IGhhdmUgYW4gYWRkcmVzcyB0byBiZSB1c2VkLCBiZWNhdXNl
IHNlcnZlciBwbGFjZXMganVzdCBzdGF0dXMgY29kZSBOb0JpbmRpbmcgb3IgTm9BZGRyc0F2YWls
IGluIHRoZSBJQSBhbmQgbm90aGluZyBlbHNlLg0KPg0KPg0KPg0KPj4NCj4+IDIuICAgICAgIFdo
eSBkb2VzIHRoZSBjbGllbnQgY291bGQgaWdub3JlICdhbnkgbWVzc2FnZScgaW5kaWNhdGluZw0K
Pj4gJ05vdE9uTGluaycgKGluIHRoZSAyXm5kIGhhbGYgb2YgdGhlIGFib3ZlIHBhcmFncmFwaCk/
IEl0IHNvdW5kcyANCj4+IGNvbmZsaWN0IHdpdGggdGhlIDFec3QgaGFsZiBvZiB0aGUgYWJvdmUg
cGFyYWdyYXBoLCBub3Q/DQo+Pg0KPj4NCj4NCj4gVGhlIHdheSBJIHJlYWQgaXQgaXMgdGhhdCB3
aGVuIHRoZSBjbGllbnQgcmVjZWl2ZXMgYXQgbGVhc3Qgb25lIFJlcGx5IHRoYXQgaGFzIG5vIE5v
dE9uTGluayBzdGF0dXMgY29kZSwgaXQgbWF5IHVzZSB0aGUgYWRkcmVzcyBpdCBkZXNpcmVzIHRv
IHVzZS4gT3RoZXJ3aXNlIGl0IHBlcmZvcm1zIHNvbGljaXRhdGlvbi4NCj4NCj4gUGVyaGFwcywg
aXQgY291bGQgYmUgbW9yZSBwcmVjaXNlIGFuZCBzYXkgc29tZXRoaW5nIGFsb25nIHRoZSBsaW5l
czogaWYgbm9uZSBvZiB0aGUgUmVwbHkgbWVzc2FnZXMgcmVjZWl2ZWQgaW4gcmVzcG9uc2UgdG8g
YSBDb25maXJtIG1lc3NhZ2UgaW5kaWNhdGVzIHN1Y2Nlc3MsIHRoZSBjbGllbnQgcGVyZm9ybXMg
c29saWNpdGF0aW9uLiBPdGhlcndpc2UsIGl0IG1heSB1c2UgdGhlIGFkZHJlc3MuDQo+DQo+IE1h
cmNpbg0K


From nobody Mon May 26 05:14:03 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CF7F1A00F6; Mon, 26 May 2014 05:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 3peK_Ik76lJB; Mon, 26 May 2014 05:14:00 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07E101A011F; Mon, 26 May 2014 05:14:00 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3C2081B81BC; Mon, 26 May 2014 05:13:57 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 1A2D519005C; Mon, 26 May 2014 05:13:57 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 26 May 2014 05:13:51 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5382acc1.42b6440a.5361.ffff8363@mx.google.com>
Date: Mon, 26 May 2014 08:13:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <0A1AEB66-C223-4E58-9574-FAF8A5FFFC72@nominum.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/-upAbd0YilyQk9WUxGJ7ndwqVfI
Cc: dhcwg@ietf.org, Bernie Volz <volz@cisco.com>, dhcpv6bis <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
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, 26 May 2014 12:14:02 -0000

On May 25, 2014, at 10:53 PM, Leaf Yeh <leaf.yeh.sdo@gmail.com> wrote:
> 1.       If the client receive an Reply message indicating =91NoBinding=92=
 (or even =91 NoAddrsAvail=92), the above sounds the client can still =
use the address in the IA. Why?
> 2.       Why does the client could ignore =91any message=92 indicating =
=91NotOnLink=92 (in the 2nd half of the above paragraph)? It sounds =
conflict with the 1st half of the above paragraph, not?

NoBinding and NoAddrsAvail are indications about the status of a single =
DHCP server, but there may be more than one DHCP server on the wire.   =
So if a server replies with such a message rather than a NotOnLink =
message, this means that that server believes the client is correctly =
configured, but isn't the server that configured it.   So if another =
server replies NotOnLink, there's a misconfiguration=97DHCP servers =
should never disagree about that.   Ignoring the NotOnLink in this case =
may be incorrect, but accepting it may also be incorrect.   And since =
NotOnLink is a great way to do a DoS attack, it's better to ignore an =
erroneous NotOnLink than honor it.

I think this is explained somewhere in the document--if so, it might be =
good to say so explicitly here.   If not, more explanation wouldn't =
hurt.


From nobody Mon May 26 05:17:29 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 16E8C1A0146; Mon, 26 May 2014 05:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 BWdTR4yYjpMh; Mon, 26 May 2014 05:17:24 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2DAC1A0137; Mon, 26 May 2014 05:17:24 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 24A621B81BC; Mon, 26 May 2014 05:17:22 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 14B3D19005C; Mon, 26 May 2014 05:17:22 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 26 May 2014 05:17:22 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <53831D49.8020800@gmail.com>
Date: Mon, 26 May 2014 08:17:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <9A715AE9-3BC6-486C-8CCB-DD4CCC632823@nominum.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com>
To: Marcin Siodelski <msiodelski@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/heoV9zesftwB9zPD1VA-Ig3cOEw
Cc: dhcwg@ietf.org, Bernie Volz <volz@cisco.com>, dhcpv6bis <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
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, 26 May 2014 12:17:26 -0000

On May 26, 2014, at 6:54 AM, Marcin Siodelski <msiodelski@gmail.com> =
wrote:
> Other
> servers will send NotOnLink because they are not configured for the
> particular subnet or so.

That should never happen.   If the server is not configured with =
information about a link, it should not respond.   Does the document say =
it should?   If one server responds with NotOnLink and another with =
NoAddrsAvail, I think that's always a configuration error.


From nobody Mon May 26 05:29:36 2014
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 933231A0148; Mon, 26 May 2014 05:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSKb8noVvJrn; Mon, 26 May 2014 05:29:33 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 335931A0129; Mon, 26 May 2014 05:29:33 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id f8so4188704wiw.8 for <multiple recipients>; Mon, 26 May 2014 05:29:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=4Z3LlgfmmK9gph/Czd5Es2XdTHPQEMD0a1YMjmMvy+o=; b=YXpBHpSOcywb9rzlX7CxnRCrsh9W33FSPadg6As3ozg/x3n0/40WkIIBhF596Ogq8j E3zTmm5VAlDkavE+cCGoNkVW2pKG9yJZS7vnfQBsKKrpyprRbOD51w1Zdx7bDFJ/b2l/ cEZMImfzpNujNYut82XPr4dxZHi9CybjEkfKfjHxb+GJQO+e6otaRSsxUfWmmY21Sv1I jUyfoerW0IMi8kEoBwuyNHGJfUWIfV5eOBxuCMIahY5qsYOwzyDUyrXdFWVeq2Bb6BV8 XgOxLXxSzrm6X11Xo2tCrn3NcqPW23h04qtwWTB85jve6/9IoyLzOqjVDDGnRuRgGk60 YhHg==
X-Received: by 10.180.37.198 with SMTP id a6mr11850954wik.58.1401107368182; Mon, 26 May 2014 05:29:28 -0700 (PDT)
Received: from ?IPv6:2001:470:71:10d:120b:a9ff:fe7b:e3f0? ([2001:470:71:10d:120b:a9ff:fe7b:e3f0]) by mx.google.com with ESMTPSA id f6sm26547935wiy.19.2014.05.26.05.29.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 May 2014 05:29:27 -0700 (PDT)
Message-ID: <538333A6.5040100@gmail.com>
Date: Mon, 26 May 2014 14:29:26 +0200
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <9A715AE9-3BC6-486C-8CCB-DD4CCC632823@nominum.com>
In-Reply-To: <9A715AE9-3BC6-486C-8CCB-DD4CCC632823@nominum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/oP9GMHpY4yC7FTjAOz9KREXjL4c
Cc: dhcwg@ietf.org, Bernie Volz <volz@cisco.com>, dhcpv6bis <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
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, 26 May 2014 12:29:34 -0000

On Mon 26 May 2014 14:17:14 CEST, Ted Lemon wrote:
> On May 26, 2014, at 6:54 AM, Marcin Siodelski <msiodelski@gmail.com> wrote:
>> Other
>> servers will send NotOnLink because they are not configured for the
>> particular subnet or so.
>
> That should never happen.   If the server is not configured with information about a link, it should not respond.   Does the document say it should?   If one server responds with NotOnLink and another with NoAddrsAvail, I think that's always a configuration error.
>

You're right. In 18.2.2 it is said that it should not respond when it 
doesn't have a knowledge of the prefixes on the link to which the 
client is connected. So, it really sounds that when there are two 
responses (one with NotOnLink, another one with Success) it either 
means misconfiguration or a rogue server sending Replies.

Marcin



From nobody Mon May 26 19:05:33 2014
Return-Path: <leaf.yeh.sdo@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 BCD0C1A02F4; Mon, 26 May 2014 19:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yx6W1AttPa4H; Mon, 26 May 2014 19:05:27 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D16EE1A02E5; Mon, 26 May 2014 19:05:27 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id fa1so8352731pad.11 for <multiple recipients>; Mon, 26 May 2014 19:05:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=wbIlGhPvGW7Pip6XMrCDi/du+gmFIx/3b8XyE/9Ja4s=; b=tMdhqdyUUPfFynHCB77RYdP8yT32mf45hvRLcr8OkhmZizQIhkRyezbFf//iHk/BQE 28D5Ksq3DRTwXX9mPiTsgWI3HYOheVc6UBFLTg460n6wUi+xMXxXGWtCS8pEfZOaPWf+ vDp7q708CDCMUbi3HTRqMGHVy3qAESrQn0omC7Y80PWWKwEjD/cZuBLVxPsd40gqdb8B UKw8Q6M20JgFJSYFq84vId1QMO0twHFsAjIZoU83oU6zKVaxQe78kLTzEodVmR8VTfm/ Bb0i4NDMxEH/3CWVtYJh95gpXJGINMZTX+x2/c02ECxXCySGBPzGM+lsgL1HKtiq7/CK wfbA==
X-Received: by 10.66.66.108 with SMTP id e12mr32190848pat.35.1401156324825; Mon, 26 May 2014 19:05:24 -0700 (PDT)
Received: from PC ([218.241.103.104]) by mx.google.com with ESMTPSA id qj3sm20368785pbc.91.2014.05.26.19.05.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 26 May 2014 19:05:24 -0700 (PDT)
Message-ID: <5383f2e4.23de440a.5bc9.5d0d@mx.google.com>
X-Google-Original-Message-ID: <007501cf7950$1d795830$586c0890$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>, "'Marcin Siodelski'" <msiodelski@gmail.com>, "'Tomasz Mrugalski'" <tomasz.mrugalski@gmail.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com>
Date: Tue, 27 May 2014 10:05:15 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac94ja1zHl9NfJkXSMiqk9XERg5MCwAbQiyAAAkBxtAACjfckA==
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/m3yHjiXNjVOqw1J6Zr-nIrO1vJk
Cc: dhcwg@ietf.org, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 02:05:29 -0000

BV > Other than global errors like UnspecFail, a Confirm will either contain
NotOnLink or Success. Nothing else.

If the client receive a reply with global error 'UnspecFail' , can the
client still 'use the addresses in the IA' indicating in the Confirm?


Best Regards,
Leaf



-----Original Message-----
From: Bernie Volz (volz) [mailto:volz@cisco.com] 
Sent: Monday, May 26, 2014 7:42 PM
To: Marcin Siodelski; Leaf Yeh; 'Tomasz Mrugalski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'
Subject: RE: [Dhcpv6bis] Reply to Confirm in RFC3315

I think we're talking about Reply to Confirm. If so, why would these contain
NoAddrsAvail/NoBinding? They don't. Confirm does not validate a particular
client's addresses/PDs or bindings. It only validates whether the
addresses/PDs are on link or not.

Other than global errors like UnspecFail, a Confirm will either contain
NotOnLink or Success. Nothing else.

And, yes the idea was there could be multiple servers some of which may send
NotOnLink (as they may be lacking the configuration) but others that send
Success. The Success on can be taken.

In general servers that aren't authoritative for a particular set of links
should not respond.

- Bernie

-----Original Message-----
From: Marcin Siodelski [mailto:msiodelski@gmail.com] 
Sent: Monday, May 26, 2014 6:54 AM
To: Leaf Yeh; Bernie Volz (volz); 'Tomasz Mrugalski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'
Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315



On 26/05/14 04:53, Leaf Yeh wrote:
> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply 
> Messages' of RFC3315:
> 
>  
> 
> <quote>
> 
> 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 
> <http://tools.ietf.org/html/rfc3315#section-17>, and client-initiated
> 
>    configuration as described in section 18 
> <http://tools.ietf.org/html/rfc3315#section-18>.  If the client 
> receives any
> 
>    Reply messages that do not indicate a NotOnLink status, the client
> 
>    can usethe addresses in the IA andignore any messages that indicate
> 
>    a NotOnLink status.
> 
> </quote>
> 
>  
> 
> 1.       If the client receive an Reply message indicating 'NoBinding'
> (or even ' NoAddrsAvail'), the above sounds the client can still use 
> the address in the IA. Why?

I think the context of the paragraph is important. The client sends Confirm
to any available server and client may receive multiple Replies.
Typically, one of these Replies will not contain NotOnLink status (or
contain Success) to indicate that client can use the address. Other servers
will send NotOnLink because they are not configured for the particular
subnet or so. So, the purpose of this paragraph is just to describe this
scenario.

Of course, client may receive Replies with other status codes too, and there
are relevant sections that talk about client behavior in this case". So a
couple of lines down:

"
   The client examines the status code in each IA individually.  If the
   status code is NoAddrsAvail, the client has received no usable
   addresses in the IA and may choose to try obtaining addresses for the
   IA from another server.  The client uses addresses and other
   information from any IAs that do not contain a Status Code option
   with the NoAddrsAvail code.  If the client receives no addresses in
   any of the IAs, it may either try another server (perhaps restarting
   the DHCP server discovery process) or use the Information-request
   message to obtain other configuration information only.
"

So, I don't really think there is any conflict here.

Also, you indicate that the client could use the address even though there
is a NoAddrsAvail or NoBinding. But, the returned IA will not have an
address to be used, because server places just status code NoBinding or
NoAddrsAvail in the IA and nothing else.



> 
> 2.       Why does the client could ignore 'any message' indicating
> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds 
> conflict with the 1^st half of the above paragraph, not?
> 
>  

The way I read it is that when the client receives at least one Reply that
has no NotOnLink status code, it may use the address it desires to use.
Otherwise it performs solicitation.

Perhaps, it could be more precise and say something along the lines: if none
of the Reply messages received in response to a Confirm message indicates
success, the client performs solicitation. Otherwise, it may use the
address.

Marcin


From nobody Mon May 26 19:06:03 2014
Return-Path: <leaf.yeh.sdo@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 856621A02E5; Mon, 26 May 2014 19:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozc0iv3RNpz2; Mon, 26 May 2014 19:05:30 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98EDD1A02F4; Mon, 26 May 2014 19:05:30 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fb1so8316292pad.37 for <multiple recipients>; Mon, 26 May 2014 19:05:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=SmumGFunGk1eVtdL6wZ2F9DBgYAR85ICagBpGRKrzl4=; b=LK5g/2dZu/+uj9yRwmm+WFEVLQ6mhyXVGPvnmO77Kfat/hg57IjNuyzQIqyPBWu/+0 p8BP+T3rL5aRFBqinEO0ersnrQ3OiEiDT0b+DWUcmiaeZ0ndbPo1vq/zXhBJ1Cuuqvki UKpQOBLitigDn4wAwPv3MTOUhU0vQsTmIQeuLTlvtgathHTZ4YtMf1kqvrRiHrxPm7tM 4Bt5W+laWbGZGA2hQgfBgWwPQYCjlgyCKb89PtWQnW81E3ukHPpMI6K2YCuBV2/nuSCd lziEw5MTLot5IOFCfz2M3anZUwBav3R4ct2AGJN1DidurCCBIC1tFKCLErZze5Coaspn VqvA==
X-Received: by 10.68.137.33 with SMTP id qf1mr31988429pbb.99.1401156327719; Mon, 26 May 2014 19:05:27 -0700 (PDT)
Received: from PC ([218.241.103.104]) by mx.google.com with ESMTPSA id qj3sm20368785pbc.91.2014.05.26.19.05.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 26 May 2014 19:05:27 -0700 (PDT)
Message-ID: <5383f2e7.23de440a.5bc9.5d0e@mx.google.com>
X-Google-Original-Message-ID: <007c01cf7950$1f5a4d30$5e0ee790$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Marcin Siodelski'" <msiodelski@gmail.com>, "'Bernie Volz \(volz\)'" <volz@cisco.com>, "'Tomasz Mrugalski'" <tomasz.mrugalski@gmail.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com>
In-Reply-To: <53831D49.8020800@gmail.com>
Date: Tue, 27 May 2014 10:05:15 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac940M8XiH4UJdPkSNKQp6RF4n4HlgAe5Bpg
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/P3DRt_BsOsHMnag2yIcxij4qT1w
Cc: dhcwg@ietf.org, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 02:05:32 -0000

Marcin - ... The client sends Confirm to any available server and client may
receive multiple Replies.
Typically, one of these Replies will not contain NotOnLink status (or
contain Success) to indicate that client can use the address. Other servers
will send NotOnLink because they are not configured for the particular
subnet or so. So, the purpose of this paragraph is just to describe this
scenario.

Yes, Confirm is a multicast message. Thanks for your explanation. But the
text here in the RFC3315 sounds to 'ignore any messages that indicate a
NotOnLink status.', which is under question. If no Success received, then
client performs 'DHCP server solicitation, and client-initiated
configuration'. That sounds not ignore 'any message.'


Marcin -Also, you indicate that the client could use the address even though
there is a NoAddrsAvail or NoBinding. But, the returned IA will not have an
address to be used, because server places just status code NoBinding or
NoAddrsAvail in the IA and nothing else.

I am not quite sure this Reply to Confirm will return IAs. But the text here
in RFC3315 sounds 'the addresses in the IA', which are from Confirm.


Marcin - Perhaps, it could be more precise and say something along the
lines: if none of the Reply messages received in response to a Confirm
message indicates success, the client performs solicitation. Otherwise, it
may use the address.

That sounds fine with me.


Best Regards,
Leaf



-----Original Message-----
From: Marcin Siodelski [mailto:msiodelski@gmail.com] 
Sent: Monday, May 26, 2014 6:54 PM
To: Leaf Yeh; 'Bernie Volz (volz)'; 'Tomasz Mrugalski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'
Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315



On 26/05/14 04:53, Leaf Yeh wrote:
> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply 
> Messages' of RFC3315:
> 
>  
> 
> <quote>
> 
> 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 
> <http://tools.ietf.org/html/rfc3315#section-17>, and client-initiated
> 
>    configuration as described in section 18 
> <http://tools.ietf.org/html/rfc3315#section-18>.  If the client 
> receives any
> 
>    Reply messages that do not indicate a NotOnLink status, the client
> 
>    can usethe addresses in the IA andignore any messages that indicate
> 
>    a NotOnLink status.
> 
> </quote>
> 
>  
> 
> 1.       If the client receive an Reply message indicating 'NoBinding'
> (or even ' NoAddrsAvail'), the above sounds the client can still use 
> the address in the IA. Why?

I think the context of the paragraph is important. The client sends Confirm
to any available server and client may receive multiple Replies.
Typically, one of these Replies will not contain NotOnLink status (or
contain Success) to indicate that client can use the address. Other servers
will send NotOnLink because they are not configured for the particular
subnet or so. So, the purpose of this paragraph is just to describe this
scenario.

Of course, client may receive Replies with other status codes too, and there
are relevant sections that talk about client behavior in this case". So a
couple of lines down:

"
   The client examines the status code in each IA individually.  If the
   status code is NoAddrsAvail, the client has received no usable
   addresses in the IA and may choose to try obtaining addresses for the
   IA from another server.  The client uses addresses and other
   information from any IAs that do not contain a Status Code option
   with the NoAddrsAvail code.  If the client receives no addresses in
   any of the IAs, it may either try another server (perhaps restarting
   the DHCP server discovery process) or use the Information-request
   message to obtain other configuration information only.
"

So, I don't really think there is any conflict here.

Also, you indicate that the client could use the address even though there
is a NoAddrsAvail or NoBinding. But, the returned IA will not have an
address to be used, because server places just status code NoBinding or
NoAddrsAvail in the IA and nothing else.



> 
> 2.       Why does the client could ignore 'any message' indicating
> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds 
> conflict with the 1^st half of the above paragraph, not?
> 
>  

The way I read it is that when the client receives at least one Reply that
has no NotOnLink status code, it may use the address it desires to use.
Otherwise it performs solicitation.

Perhaps, it could be more precise and say something along the lines: if none
of the Reply messages received in response to a Confirm message indicates
success, the client performs solicitation. Otherwise, it may use the
address.

Marcin


From nobody Mon May 26 22:42:20 2014
Return-Path: <leaf.yeh.sdo@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 69C651A01A7; Mon, 26 May 2014 22:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EO4VzBrIZ0St; Mon, 26 May 2014 22:42:14 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A37D01A011B; Mon, 26 May 2014 22:42:14 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rp16so8673534pbb.34 for <multiple recipients>; Mon, 26 May 2014 22:42:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:thread-index:content-language; bh=dW4d1Uq9lGL933Y1KdwD6Vf3Cv5jhignUoE7KiVZWZY=; b=zKsetXsxxn3iKLJHjhkZNJmvhavBwJ5acv4ocWntfz9rRLWTT3j5AHJiTy35dciRlW W9UCPrEjvGajzmKMAghAPI/WKYBcPenItkuSYxYn72mYQ+Qg3g+kKMHXN4yLKaVCNjM0 nVljadjlOAFPcXjBIT/eUQjSlfwPOirY00ONsjwM/hCYzxCLAgeIA1KHC5Cp0ComNRHu 6dt0Mf3504oKNpMniv5wdfk26gzltg8k0TVJLgPD9KiRvr2pR2T0WQGVnAP6AzIzxsnq M0hv+vXt6FgN+gemuVb9LRC6zF4aNKnq4OPpqVe7O1/SQxd/49skMv0PFHgJoH1ehkMk 21mQ==
X-Received: by 10.66.146.199 with SMTP id te7mr33687453pab.106.1401169331554;  Mon, 26 May 2014 22:42:11 -0700 (PDT)
Received: from PC ([218.241.103.104]) by mx.google.com with ESMTPSA id su8sm21157270pbc.72.2014.05.26.22.42.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 26 May 2014 22:42:11 -0700 (PDT)
Message-ID: <538425b3.08e6440a.08fb.7da2@mx.google.com>
X-Google-Original-Message-ID: <00aa01cf796e$658c9830$30a5c890$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com>
In-Reply-To: <53832BB3.6000902@gmail.com>
Date: Tue, 27 May 2014 13:42:02 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AB_01CF79B1.73AFD830"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac942WaAqfzeIl/7So+WMHZxqku17wAd2kKA
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/KnKoU3yX-2t9LJuOyzBtSsmVd0k
Cc: dhcwg@ietf.org, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: [dhcwg] More Discussion - RE: [Dhcpv6bis] Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 05:42:18 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00AB_01CF79B1.73AFD830
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

When I read the text on 'Reply to Confirm' in RFC3315, the following =
statements sounds me a little misunderstanding:

=20

<quote> @ 18.1.2 - Creation and Transmission of Confirm Messages

   The client MUST include a Client Identifier option to identify itself

   to the server.  The client includes IA options for all of the IAs

   assigned to the interface for which the Confirm message is being

   sent.  The IA options include all of the addresses the client

   currently has associated with those IAs.  The client SHOULD set the

   T1 and T2 fields in any IA_NA options, and the preferred-lifetime and

   valid-lifetime fields in the IA Address options to 0, as the server

   will ignore these fields.

</quote>

=20

It sounds the client ask the server to confirm the address (& IA) for =
his interface, but why not ask the server to confirm the values of lease =
timers (T1/T2 for IA, preferred/valid-LT for address) he has.

=20

=20

<quote> @ 18.2.2 -Receipt of Confirm Messages

   The server ignores the T1 and T2 fields in the IA options and the

   preferred-lifetime and valid-lifetime fields in the IA Address

   options.

   ...

   The server MUST include a Server Identifier option containing the

   server's DUID and the Client Identifier option from the Confirm

   message in the Reply message.  The server includes a Status Code

   option indicating the status of the Confirm message.

</quote>

=20

=20

Certainly, the server confirmed the address (& the associated IAID) of =
client based on its this own database. If the server returned the global =
=E2=80=98Success=E2=80=99 in the Status Code option, it sounds all the =
information the client provided in Confirm has been confirmed, and =
assumed the client has the same lease as that recoded in the database of =
server.

=20

But I think it sounds much better the server could confirm (or update) =
all the information about the lease (including address and the value of =
timers) for the client in the Reply message. It looks much clearer, and =
cost little in the Reply.

=20

The global Status Code looks unspecified to each address (and its =
lease), which in fact needs to be confirmed.

=20

=20

Best Regards,

Leaf

=20

=20

=20

-----Original Message-----
From: Marcin Siodelski [mailto:msiodelski@gmail.com]=20
Sent: Monday, May 26, 2014 7:56 PM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org; 'dhcpv6bis'; Leaf Yeh; 'Tomasz Mrugalski'
Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315

=20

Yes, NoAddrsAvail/NoBinding are not sent in response to Confirm. May =
point rather was that *even in a more general case* the server will not =
send addresses in the IA in which there is NoAddrsAvail or NoBinding.=20

This comment was beyond the context of Confirm/Reply message exchange.

=20

Marcin

=20

On Mon 26 May 2014 13:41:30 CEST, Bernie Volz (volz) wrote:

> I think we're talking about Reply to Confirm. If so, why would these =
contain NoAddrsAvail/NoBinding? They don't. Confirm does not validate a =
particular client's addresses/PDs or bindings. It only validates whether =
the addresses/PDs are on link or not.

>=20

> Other than global errors like UnspecFail, a Confirm will either =
contain NotOnLink or Success. Nothing else.

>=20

> And, yes the idea was there could be multiple servers some of which =
may send NotOnLink (as they may be lacking the configuration) but others =
that send Success. The Success on can be taken.

>=20

> In general servers that aren't authoritative for a particular set of =
links should not respond.

>=20

> - Bernie

>=20

> -----Original Message-----

> From: Marcin Siodelski [ <mailto:msiodelski@gmail.com> =
mailto:msiodelski@gmail.com]

> Sent: Monday, May 26, 2014 6:54 AM

> To: Leaf Yeh; Bernie Volz (volz); 'Tomasz Mrugalski'

> Cc:  <mailto:dhcwg@ietf.org> dhcwg@ietf.org; 'dhcpv6bis'

> Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315

>=20

>=20

>=20

> On 26/05/14 04:53, Leaf Yeh wrote:

>> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply=20

>> Messages' of RFC3315:

>>=20

>>=20

>>=20

>> <quote>

>>=20

>> When the client receives a NotOnLink status from the server in

>>=20

>>    response to a Confirm message, the client performs DHCP server

>>=20

>>    solicitation, as described in section 17=20

>> < <http://tools.ietf.org/html/rfc3315#section-17> =
http://tools.ietf.org/html/rfc3315#section-17>, and client-initiated

>>=20

>>    configuration as described in section 18=20

>> < <http://tools.ietf.org/html/rfc3315#section-18> =
http://tools.ietf.org/html/rfc3315#section-18>.  If the client=20

>> receives any

>>=20

>>    Reply messages that do not indicate a NotOnLink status, the client

>>=20

>>    can usethe addresses in the IA andignore any messages that=20

>> indicate

>>=20

>>    a NotOnLink status.

>>=20

>> </quote>

>>=20

>>=20

>>=20

>> 1.       If the client receive an Reply message indicating =
'NoBinding'

>> (or even ' NoAddrsAvail'), the above sounds the client can still use=20

>> the address in the IA. Why?

>=20

> I think the context of the paragraph is important. The client sends =
Confirm to any available server and client may receive multiple Replies.

> Typically, one of these Replies will not contain NotOnLink status (or =
contain Success) to indicate that client can use the address. Other =
servers will send NotOnLink because they are not configured for the =
particular subnet or so. So, the purpose of this paragraph is just to =
describe this scenario.

>=20

> Of course, client may receive Replies with other status codes too, and =
there are relevant sections that talk about client behavior in this =
case". So a couple of lines down:

>=20

> "

>    The client examines the status code in each IA individually.  If =
the

>    status code is NoAddrsAvail, the client has received no usable

>    addresses in the IA and may choose to try obtaining addresses for =
the

>    IA from another server.  The client uses addresses and other

>    information from any IAs that do not contain a Status Code option

>    with the NoAddrsAvail code.  If the client receives no addresses in

>    any of the IAs, it may either try another server (perhaps =
restarting

>    the DHCP server discovery process) or use the Information-request

>    message to obtain other configuration information only.

> "

>=20

> So, I don't really think there is any conflict here.

>=20

> Also, you indicate that the client could use the address even though =
there is a NoAddrsAvail or NoBinding. But, the returned IA will not have =
an address to be used, because server places just status code NoBinding =
or NoAddrsAvail in the IA and nothing else.

>=20

>=20

>=20

>>=20

>> 2.       Why does the client could ignore 'any message' indicating

>> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds=20

>> conflict with the 1^st half of the above paragraph, not?

>>=20

>>=20

>=20

> The way I read it is that when the client receives at least one Reply =
that has no NotOnLink status code, it may use the address it desires to =
use. Otherwise it performs solicitation.

>=20

> Perhaps, it could be more precise and say something along the lines: =
if none of the Reply messages received in response to a Confirm message =
indicates success, the client performs solicitation. Otherwise, it may =
use the address.

>=20

> Marcin


------=_NextPart_000_00AB_01CF79B1.73AFD830
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-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.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:9.0pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E7=BA=AF=E6=96=87=E6=9C=AC;
	font-family:"Calibri","sans-serif";}
span.Char0
	{mso-style-name:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoPlainText><span lang=3DEN-US>When I =
read the text on 'Reply to Confirm' in RFC3315, the following statements =
sounds me a little misunderstanding:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&lt;quote&gt; @ 18.1.2 - =
Creation and Transmission of Confirm Messages<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 The client MUST =
include a Client Identifier option to identify =
itself<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 to the server.=C2=A0 The client includes IA =
options for <span style=3D'color:red'>all of the =
IAs<o:p></o:p></span></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:red'>=C2=A0=C2=A0 assigned to the =
interface</span><span lang=3DEN-US> for which the Confirm message is =
being<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 sent.=C2=A0 The IA options include all of the =
addresses the client<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 currently has associated with those IAs.=C2=A0 =
The client SHOULD set the<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 <span =
style=3D'color:red'>T1 and T2 fields in any IA_NA options, and the =
preferred-lifetime and<o:p></o:p></span></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:red'>=C2=A0=C2=A0 =
valid-lifetime fields in the IA Address options to 0</span><span =
lang=3DEN-US>, as the server<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 will ignore these =
fields.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&lt;/quote&gt;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>It sounds the client ask the =
server to confirm the address (&amp; IA) for his interface, but <b>why =
not</b> ask the server to confirm the values of lease timers (T1/T2 for =
IA, preferred/valid-LT for address) he has.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&lt;quote&gt; @ 18.2.2 -Receipt =
of Confirm Messages<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 The server <span =
style=3D'color:red'>ignores</span> the T1 and T2 fields in the IA =
options and the<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 preferred-lifetime and valid-lifetime fields =
in the IA Address<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 options.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 =
...<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 The server MUST include a Server Identifier =
option containing the<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 server's DUID and the Client Identifier option =
from the Confirm<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 message in the Reply message.=C2=A0 <span =
style=3D'color:red'>The server includes a Status =
Code<o:p></o:p></span></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:red'>=C2=A0=C2=A0 option indicating the =
status of the Confirm message.</span><span =
lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&lt;/quote&gt;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Certainly, the server confirmed =
the address (&amp; the associated IAID) of client based on its this own =
database. If the server returned the global </span><span lang=3DEN-US =
style=3D'font-family:"Courier New"'>=E2=80=98</span><span =
lang=3DEN-US>Success</span><span lang=3DEN-US =
style=3D'font-family:"Courier New"'>=E2=80=99</span><span lang=3DEN-US> =
in the Status Code option, it sounds all the information the client =
provided in Confirm has been confirmed, and <b>assumed the client has =
the same lease as that recoded in the database of =
server.</b><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>But I think it sounds much better the server could confirm =
(or update) all the information about the lease (including address and =
the value of timers) for the client in the Reply message. It looks much =
clearer, and cost little in the Reply.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>The global Status Code looks =
unspecified to each address (and its lease), which in fact needs to be =
confirmed.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Best Regards,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Leaf<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>-----Original =
Message-----<br>From: Marcin Siodelski [mailto:msiodelski@gmail.com] =
<br>Sent: Monday, May 26, 2014 7:56 PM<br>To: Bernie Volz (volz)<br>Cc: =
dhcwg@ietf.org; 'dhcpv6bis'; Leaf Yeh; 'Tomasz Mrugalski'<br>Subject: =
Re: [Dhcpv6bis] Reply to Confirm in RFC3315<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Yes, NoAddrsAvail/NoBinding are =
not sent in response to Confirm. May point rather was that *even in a =
more general case* the server will not send addresses in the IA in which =
there is NoAddrsAvail or NoBinding. <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>This comment was beyond the =
context of Confirm/Reply message exchange.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Marcin<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>On Mon 26 May 2014 13:41:30 =
CEST, Bernie Volz (volz) wrote:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; I think we're talking about =
Reply to Confirm. If so, why would these contain NoAddrsAvail/NoBinding? =
They don't. Confirm does not validate a particular client's =
addresses/PDs or bindings. It only validates whether the addresses/PDs =
are on link or not.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Other than global errors =
like UnspecFail, a Confirm will either contain NotOnLink or Success. =
Nothing else.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; And, yes the idea was there =
could be multiple servers some of which may send NotOnLink (as they may =
be lacking the configuration) but others that send Success. The Success =
on can be taken.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; In general servers that =
aren't authoritative for a particular set of links should not =
respond.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; - =
Bernie<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; -----Original =
Message-----<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; From: Marcin Siodelski [<a =
href=3D"mailto:msiodelski@gmail.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:msiodelski@gmail.c=
om</span></a>]<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; Sent: Monday, May 26, 2014 6:54 =
AM<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>&gt; =
To: Leaf Yeh; Bernie Volz (volz); 'Tomasz =
Mrugalski'<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; Cc: <a href=3D"mailto:dhcwg@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>dhcwg@ietf.org</span></a>=
; 'dhcpv6bis'<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; Subject: Re: [Dhcpv6bis] Reply to Confirm in =
RFC3315<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; On 26/05/14 04:53, Leaf Yeh =
wrote:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; Got 2 questions on the text in Section =
18.1.8-'Receipt of Reply <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; Messages' of =
RFC3315:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
&lt;quote&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; When the client =
receives a NotOnLink status from the server in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 =
response to a Confirm message, the client performs DHCP =
server<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 =
solicitation, as described in section 17 <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; &lt;<a =
href=3D"http://tools.ietf.org/html/rfc3315#section-17"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/rfc3315#section-17</span></a>&gt;, and =
client-initiated<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 =
configuration as described in section 18 <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; &lt;<a =
href=3D"http://tools.ietf.org/html/rfc3315#section-18"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/rfc3315#section-18</span></a>&gt;.=C2=A0 If the client =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; receives any<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 Reply =
messages that do not indicate a NotOnLink status, the =
client<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 can =
usethe addresses in the IA andignore any messages that =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; indicate<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 a =
NotOnLink status.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
&lt;/quote&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
1.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 If the client receive an Reply =
message indicating 'NoBinding'<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; (or even ' =
NoAddrsAvail'), the above sounds the client can still use =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; the address in the IA. =
Why?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; I think the context of the =
paragraph is important. The client sends Confirm to any available server =
and client may receive multiple Replies.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Typically, one of these =
Replies will not contain NotOnLink status (or contain Success) to =
indicate that client can use the address. Other servers will send =
NotOnLink because they are not configured for the particular subnet or =
so. So, the purpose of this paragraph is just to describe this =
scenario.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Of course, client may =
receive Replies with other status codes too, and there are relevant =
sections that talk about client behavior in this case&quot;. So a couple =
of lines down:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; =
&quot;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 The client examines the status code =
in each IA individually.=C2=A0 If the<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 status =
code is NoAddrsAvail, the client has received no =
usable<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 addresses in the IA and may choose =
to try obtaining addresses for the<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 IA from =
another server.=C2=A0 The client uses addresses and =
other<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 information from any IAs that do not =
contain a Status Code option<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 with the =
NoAddrsAvail code.=C2=A0 If the client receives no addresses =
in<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 any of the IAs, it may either try =
another server (perhaps restarting<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 the DHCP =
server discovery process) or use the =
Information-request<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 message to obtain other =
configuration information only.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; =
&quot;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; So, I don't really think =
there is any conflict here.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Also, you indicate that the =
client could use the address even though there is a NoAddrsAvail or =
NoBinding. But, the returned IA will not have an address to be used, =
because server places just status code NoBinding or NoAddrsAvail in the =
IA and nothing else.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
2.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Why does the client could ignore =
'any message' indicating<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; 'NotOnLink' (in the =
2^nd half of the above paragraph)? It sounds <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; conflict with the 1^st =
half of the above paragraph, not?<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; The way I read it is that =
when the client receives at least one Reply that has no NotOnLink status =
code, it may use the address it desires to use. Otherwise it performs =
solicitation.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Perhaps, it could be more =
precise and say something along the lines: if none of the Reply messages =
received in response to a Confirm message indicates success, the client =
performs solicitation. Otherwise, it may use the =
address.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; =
Marcin<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_00AB_01CF79B1.73AFD830--


From nobody Tue May 27 01:55:02 2014
Return-Path: <leaf.yeh.sdo@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 DE8B21A03DB; Tue, 27 May 2014 01:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPUcY21w1z-S; Tue, 27 May 2014 01:54:57 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6779E1A0035; Tue, 27 May 2014 01:54:57 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id md12so9002842pbc.1 for <multiple recipients>; Tue, 27 May 2014 01:54:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:thread-index:content-language; bh=us6PFggDcR6PY9GkI5wqeppA5jUOclGAY0zJnHm4LGo=; b=NDWf/B1WBedjTDRxNrCsJ/v9g2ImxEsq8IpPuSwIB5B3oyO4Xl9Z5QWyAIk0QgvmtE QOx4JV83nte57rW9nmBrG569fo5Pur32lrOy97YAI4iuX1Rpw78LGxTyZH4r1KjVpnYt ir6lUaj+JwKIpdA81Q+fwdRbOc+J1wuSfQpoK8cd34JzRu6zrER/tTTY0NDO58GLY2Yh s/bfghWr9ViXOt+ZXalQvBg87JdD94/pFWlEpP1+N07ePwgSUHq06IraMlxdvy02cZuD 35g9ZLino1mf4zIVO15Zrkl1OgX1rxpWkhD45mugcA6X4MOv27boOJrtglyXz4d3tOjT J+hA==
X-Received: by 10.67.23.135 with SMTP id ia7mr33953107pad.5.1401180894305; Tue, 27 May 2014 01:54:54 -0700 (PDT)
Received: from PC ([218.241.103.104]) by mx.google.com with ESMTPSA id zq5sm22147147pbb.37.2014.05.27.01.54.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 27 May 2014 01:54:53 -0700 (PDT)
Message-ID: <538452dd.c5a7440a.37fc.ffffa93f@mx.google.com>
X-Google-Original-Message-ID: <00e401cf7989$51454b90$f3cfe2b0$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>, "'Marcin Siodelski'" <msiodelski@gmail.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049CB0@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B049CB0@xmb-rcd-x04.cisco.com>
Date: Tue, 27 May 2014 16:54:46 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E5_01CF79CC.5F688B90"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac94ja1zHl9NfJkXSMiqk9XERg5MCwAbQiyAAAkBxtD//8kggIAAUv7Q//9aoQA=
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/V7W4OqccixLLDZuTMIw9AHxcx9I
Cc: dhcwg@ietf.org, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: [dhcwg] Reply to Request in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 08:55:01 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00E5_01CF79CC.5F688B90
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

BV> In Request case it is within the IA and means that the client's =
requested addresses (or PD) is not on the link...The Request case is a =
bit weird in one respect as 18.1.8 says:

   When the client receives a NotOnLink status from the server in

   response to a Request, the client can either re-issue the Request

   without specifying any addresses or restart the DHCP server discovery

   process (see section 17).

This kind of implies that it is "global". I think this case was to =
handle the client moving between Solicit and Request (but with the same =
server still responding since the Server DUID matches).

=20

The above quoted paragraph is associated with one paragraph in section =
18.2.1,=20

   If the server finds that the prefix on one or more IP addresses in

   any IA in the message from the client is not appropriate for the link

   to which the client is connected, the server MUST return the IA to

   the client with a Status Code option with the value NotOnLink.

=20

My question is why the server can't ignore 'the addresses in any IA in =
the message from the client', and send back a new address for the IA =
requested by the client per its (configuration) policy.

=20

=20

Best Regards,

Leaf

=20

=20

=20

-----Original Message-----
From: Bernie Volz (volz) [mailto:volz@cisco.com]=20
Sent: Monday, May 26, 2014 8:07 PM
To: Marcin Siodelski
Cc: dhcwg@ietf.org; 'dhcpv6bis'; Leaf Yeh; 'Tomasz Mrugalski'
Subject: RE: [Dhcpv6bis] Reply to Confirm in RFC3315

=20

The only two cases where NotOnLink status is used is in the response to =
Request and Confirm.

=20

In Confirm case it is global level status.

=20

In Request case it is within the IA and means that the client's =
requested addresses (or PD) is not on the link. No addresses/PD should =
be returned to client for that IA. The Request case is a bit weird in =
one respect as 18.1.8 says:

=20

   When the client receives a NotOnLink status from the server in

   response to a Request, the client can either re-issue the Request

   without specifying any addresses or restart the DHCP server discovery

   process (see section 17).

=20

This kind of implies that it is "global".

=20

I think this case was to handle the client moving between Solicit and =
Request (but with the same server still responding since the Server DUID =
matches).

=20

It is a good question as to whether we should make this status global =
rather than IA specific. In in the end there's probably not much harm in =
leaving it as is because if the client restarts the process, it will =
just get back the other addresses/PD that might have been assigned to =
other IA options that did not result in NotOnLink.

=20

- Bernie

=20

-----Original Message-----

From: Marcin Siodelski [ <mailto:msiodelski@gmail.com> =
mailto:msiodelski@gmail.com]

Sent: Monday, May 26, 2014 7:56 AM

To: Bernie Volz (volz)

Cc:  <mailto:dhcwg@ietf.org> dhcwg@ietf.org; 'dhcpv6bis'; Leaf Yeh; =
'Tomasz Mrugalski'

Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315

=20

Yes, NoAddrsAvail/NoBinding are not sent in response to Confirm. May =
point rather was that *even in a more general case* the server will not =
send addresses in the IA in which there is NoAddrsAvail or NoBinding.=20

This comment was beyond the context of Confirm/Reply message exchange.

=20

Marcin

=20

On Mon 26 May 2014 13:41:30 CEST, Bernie Volz (volz) wrote:

> I think we're talking about Reply to Confirm. If so, why would these =
contain NoAddrsAvail/NoBinding? They don't. Confirm does not validate a =
particular client's addresses/PDs or bindings. It only validates whether =
the addresses/PDs are on link or not.

>=20

> Other than global errors like UnspecFail, a Confirm will either =
contain NotOnLink or Success. Nothing else.

>=20

> And, yes the idea was there could be multiple servers some of which =
may send NotOnLink (as they may be lacking the configuration) but others =
that send Success. The Success on can be taken.

>=20

> In general servers that aren't authoritative for a particular set of =
links should not respond.

>=20

> - Bernie

>=20

> -----Original Message-----

> From: Marcin Siodelski [ <mailto:msiodelski@gmail.com> =
mailto:msiodelski@gmail.com]

> Sent: Monday, May 26, 2014 6:54 AM

> To: Leaf Yeh; Bernie Volz (volz); 'Tomasz Mrugalski'

> Cc:  <mailto:dhcwg@ietf.org> dhcwg@ietf.org; 'dhcpv6bis'

> Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315

>=20

>=20

>=20

> On 26/05/14 04:53, Leaf Yeh wrote:

>> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply=20

>> Messages' of RFC3315:

>>=20

>>=20

>>=20

>> <quote>

>>=20

>> When the client receives a NotOnLink status from the server in

>>=20

>>    response to a Confirm message, the client performs DHCP server

>>=20

>>    solicitation, as described in section 17=20

>> < <http://tools.ietf.org/html/rfc3315#section-17> =
http://tools.ietf.org/html/rfc3315#section-17>, and client-initiated

>>=20

>>    configuration as described in section 18=20

>> < <http://tools.ietf.org/html/rfc3315#section-18> =
http://tools.ietf.org/html/rfc3315#section-18>.  If the client=20

>> receives any

>>=20

>>    Reply messages that do not indicate a NotOnLink status, the client

>>=20

>>    can usethe addresses in the IA andignore any messages that=20

>> indicate

>>=20

>>    a NotOnLink status.

>>=20

>> </quote>

>>=20

>>=20

>>=20

>> 1.       If the client receive an Reply message indicating =
'NoBinding'

>> (or even ' NoAddrsAvail'), the above sounds the client can still use=20

>> the address in the IA. Why?

>=20

> I think the context of the paragraph is important. The client sends =
Confirm to any available server and client may receive multiple Replies.

> Typically, one of these Replies will not contain NotOnLink status (or =
contain Success) to indicate that client can use the address. Other =
servers will send NotOnLink because they are not configured for the =
particular subnet or so. So, the purpose of this paragraph is just to =
describe this scenario.

>=20

> Of course, client may receive Replies with other status codes too, and =
there are relevant sections that talk about client behavior in this =
case". So a couple of lines down:

>=20

> "

>    The client examines the status code in each IA individually.  If =
the

>    status code is NoAddrsAvail, the client has received no usable

>    addresses in the IA and may choose to try obtaining addresses for =
the

>    IA from another server.  The client uses addresses and other

>    information from any IAs that do not contain a Status Code option

>    with the NoAddrsAvail code.  If the client receives no addresses in

>    any of the IAs, it may either try another server (perhaps =
restarting

>    the DHCP server discovery process) or use the Information-request

>    message to obtain other configuration information only.

> "

>=20

> So, I don't really think there is any conflict here.

>=20

> Also, you indicate that the client could use the address even though =
there is a NoAddrsAvail or NoBinding. But, the returned IA will not have =
an address to be used, because server places just status code NoBinding =
or NoAddrsAvail in the IA and nothing else.

>=20

>=20

>=20

>>=20

>> 2.       Why does the client could ignore 'any message' indicating

>> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds=20

>> conflict with the 1^st half of the above paragraph, not?

>>=20

>>=20

>=20

> The way I read it is that when the client receives at least one Reply =
that has no NotOnLink status code, it may use the address it desires to =
use. Otherwise it performs solicitation.

>=20

> Perhaps, it could be more precise and say something along the lines: =
if none of the Reply messages received in response to a Confirm message =
indicates success, the client performs solicitation. Otherwise, it may =
use the address.

>=20

> Marcin


------=_NextPart_000_00E5_01CF79CC.5F688B90
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-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.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:9.0pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E7=BA=AF=E6=96=87=E6=9C=AC;
	font-family:"Calibri","sans-serif";}
span.Char0
	{mso-style-name:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoPlainText><span lang=3DEN-US>BV&gt; =
In Request case it is within the IA and means that the client's =
requested addresses (or PD) is not on the link...The Request case is a =
bit weird in one respect as 18.1.8 says:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 When the client =
receives a NotOnLink status from the server in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 response to a =
Request, the client can either re-issue the =
Request<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 without specifying any addresses or restart =
the DHCP server discovery<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 process (see =
section 17).<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>This kind of implies that it is &quot;global&quot;. I think =
this case was to handle the client moving between Solicit and Request =
(but with the same server still responding since the Server DUID =
matches).<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>The above quoted paragraph is associated with one paragraph =
in section 18.2.1, <o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0If the server finds that the prefix on =
one or more IP addresses in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 any IA in the =
message from the client is not appropriate for the =
link<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 to which the client is connected, the server =
<span style=3D'color:red'>MUST return the IA =
to<o:p></o:p></span></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:red'>=C2=A0=C2=A0 the client with a Status =
Code option with the value NotOnLink</span><span =
lang=3DEN-US>.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>My question is why the server can't ignore 'the addresses =
in any IA in the message from the client', and send back a new address =
for the IA requested by the client per its (configuration) =
policy.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Best Regards,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Leaf<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>-----Original =
Message-----<br>From: Bernie Volz (volz) [mailto:volz@cisco.com] =
<br>Sent: Monday, May 26, 2014 8:07 PM<br>To: Marcin Siodelski<br>Cc: =
dhcwg@ietf.org; 'dhcpv6bis'; Leaf Yeh; 'Tomasz Mrugalski'<br>Subject: =
RE: [Dhcpv6bis] Reply to Confirm in RFC3315<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>The only two cases where =
NotOnLink status is used is in the response to Request and =
Confirm.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>In Confirm case it is global level =
status.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>In Request case it is within the IA and means that the =
client's requested addresses (or PD) is not on the link. No addresses/PD =
should be returned to client for that IA. The Request case is a bit =
weird in one respect as 18.1.8 says:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 When the client =
receives a NotOnLink status from the server in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 response to a =
Request, the client can either re-issue the =
Request<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0 without specifying any addresses or restart =
the DHCP server discovery<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 process (see =
section 17).<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>This kind of implies that it is =
&quot;global&quot;.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>I think this case was to handle the client moving between =
Solicit and Request (but with the same server still responding since the =
Server DUID matches).<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>It is a good question as to whether we should make this =
status global rather than IA specific. In in the end there's probably =
not much harm in leaving it as is because if the client restarts the =
process, it will just get back the other addresses/PD that might have =
been assigned to other IA options that did not result in =
NotOnLink.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>- Bernie<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>-----Original Message-----<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>From: Marcin Siodelski [<a =
href=3D"mailto:msiodelski@gmail.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:msiodelski@gmail.c=
om</span></a>]<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Sent: Monday, May 26, 2014 7:56 AM<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>To: Bernie Volz =
(volz)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Cc: <a href=3D"mailto:dhcwg@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>dhcwg@ietf.org</span></a>=
; 'dhcpv6bis'; Leaf Yeh; 'Tomasz Mrugalski'<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Subject: Re: [Dhcpv6bis] Reply =
to Confirm in RFC3315<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Yes, NoAddrsAvail/NoBinding are not sent in response to =
Confirm. May point rather was that *even in a more general case* the =
server will not send addresses in the IA in which there is NoAddrsAvail =
or NoBinding. <o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>This comment was beyond the context of Confirm/Reply =
message exchange.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Marcin<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>On Mon 26 May 2014 13:41:30 CEST, Bernie Volz (volz) =
wrote:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; I think we're talking about Reply to Confirm. If so, =
why would these contain NoAddrsAvail/NoBinding? They don't. Confirm does =
not validate a particular client's addresses/PDs or bindings. It only =
validates whether the addresses/PDs are on link or =
not.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Other than global errors =
like UnspecFail, a Confirm will either contain NotOnLink or Success. =
Nothing else.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; And, yes the idea was there =
could be multiple servers some of which may send NotOnLink (as they may =
be lacking the configuration) but others that send Success. The Success =
on can be taken.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; In general servers that =
aren't authoritative for a particular set of links should not =
respond.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; - =
Bernie<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; -----Original =
Message-----<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; From: Marcin Siodelski [<a =
href=3D"mailto:msiodelski@gmail.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:msiodelski@gmail.c=
om</span></a>]<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; Sent: Monday, May 26, 2014 6:54 =
AM<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>&gt; =
To: Leaf Yeh; Bernie Volz (volz); 'Tomasz =
Mrugalski'<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; Cc: <a href=3D"mailto:dhcwg@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>dhcwg@ietf.org</span></a>=
; 'dhcpv6bis'<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; Subject: Re: [Dhcpv6bis] Reply to Confirm in =
RFC3315<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; On 26/05/14 04:53, Leaf Yeh =
wrote:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; Got 2 questions on the text in Section =
18.1.8-'Receipt of Reply <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; Messages' of =
RFC3315:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
&lt;quote&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; When the client =
receives a NotOnLink status from the server in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 =
response to a Confirm message, the client performs DHCP =
server<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 =
solicitation, as described in section 17 <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; &lt;<a =
href=3D"http://tools.ietf.org/html/rfc3315#section-17"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/rfc3315#section-17</span></a>&gt;, and =
client-initiated<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 =
configuration as described in section 18 <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; &lt;<a =
href=3D"http://tools.ietf.org/html/rfc3315#section-18"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/rfc3315#section-18</span></a>&gt;.=C2=A0 If the client =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; receives any<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 Reply =
messages that do not indicate a NotOnLink status, the =
client<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 can =
usethe addresses in the IA andignore any messages that =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; indicate<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;=C2=A0=C2=A0=C2=A0 a =
NotOnLink status.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
&lt;/quote&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
1.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 If the client receive an Reply =
message indicating 'NoBinding'<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; (or even ' =
NoAddrsAvail'), the above sounds the client can still use =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; the address in the IA. =
Why?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; I think the context of the =
paragraph is important. The client sends Confirm to any available server =
and client may receive multiple Replies.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Typically, one of these =
Replies will not contain NotOnLink status (or contain Success) to =
indicate that client can use the address. Other servers will send =
NotOnLink because they are not configured for the particular subnet or =
so. So, the purpose of this paragraph is just to describe this =
scenario.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Of course, client may =
receive Replies with other status codes too, and there are relevant =
sections that talk about client behavior in this case&quot;. So a couple =
of lines down:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; =
&quot;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 The client examines the status code =
in each IA individually.=C2=A0 If the<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 status =
code is NoAddrsAvail, the client has received no =
usable<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 addresses in the IA and may choose =
to try obtaining addresses for the<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 IA from =
another server.=C2=A0 The client uses addresses and =
other<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 information from any IAs that do not =
contain a Status Code option<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 with the =
NoAddrsAvail code.=C2=A0 If the client receives no addresses =
in<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 any of the IAs, it may either try =
another server (perhaps restarting<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 the DHCP =
server discovery process) or use the =
Information-request<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;=C2=A0=C2=A0=C2=A0 message to obtain other =
configuration information only.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; =
&quot;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; So, I don't really think =
there is any conflict here.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Also, you indicate that the =
client could use the address even though there is a NoAddrsAvail or =
NoBinding. But, the returned IA will not have an address to be used, =
because server places just status code NoBinding or NoAddrsAvail in the =
IA and nothing else.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
2.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Why does the client could ignore =
'any message' indicating<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; 'NotOnLink' (in the =
2^nd half of the above paragraph)? It sounds <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; conflict with the 1^st =
half of the above paragraph, not?<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; The way I read it is that =
when the client receives at least one Reply that has no NotOnLink status =
code, it may use the address it desires to use. Otherwise it performs =
solicitation.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Perhaps, it could be more =
precise and say something along the lines: if none of the Reply messages =
received in response to a Confirm message indicates success, the client =
performs solicitation. Otherwise, it may use the =
address.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; =
Marcin<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_00E5_01CF79CC.5F688B90--


From nobody Tue May 27 02:24:02 2014
Return-Path: <leaf.yeh.sdo@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 581DE1A0049; Tue, 27 May 2014 02:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vUTqLgNCXspw; Tue, 27 May 2014 02:23:58 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B04C1A002F; Tue, 27 May 2014 02:23:58 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz1so8831008pad.2 for <multiple recipients>; Tue, 27 May 2014 02:23:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=2xQr8tphLrA5H7V2XEDGxjV/vDe90DagW9hi/aZCgbU=; b=HuodAC54HunhNilnunYR3GaoSsoUGNI5yBJO45u0AuyjowaKXzxIoFenxs0vbOAgXM t0mTOxqGXCVR3lqCVO0FqZldg0VEERMMn8V9zYyb2je2BCtmyw55SV81z/kO8f0BKDEm dsOMOkXQiN+wVnTddnoTLY7Oatdxlh9mUd/KLr7XvrNSlSHWvqFEoNf75CNrNqmdy7VC fHddgg2w8hHjXNk/DLwVXRJ6HltFgL4mpfhlJZ4y1HO/qdlvlc2Q+Xw1PZB1BAUz/NwE feA83qI9YJPSmjglY+bitdw+wibLg4zmZV1c7nB2ZdKb/zGWFz4IHmG75ETtePtyN7Gc PkKQ==
X-Received: by 10.66.163.164 with SMTP id yj4mr34735779pab.91.1401182634828; Tue, 27 May 2014 02:23:54 -0700 (PDT)
Received: from PC ([218.241.103.104]) by mx.google.com with ESMTPSA id xk1sm70758893pac.21.2014.05.27.02.23.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 27 May 2014 02:23:53 -0700 (PDT)
Message-ID: <538459a9.01f5420a.7d2f.5089@mx.google.com>
X-Google-Original-Message-ID: <00ef01cf798d$5ec48200$1c4d8600$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Marcin Siodelski'" <msiodelski@gmail.com>, "'Ted Lemon'" <ted.lemon@nominum.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <9A715AE9-3BC6-486C-8CCB-DD4CCC632823@nominum.com> <538333A6.5040100@gmail.com>
In-Reply-To: <538333A6.5040100@gmail.com>
Date: Tue, 27 May 2014 17:23:45 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac943iN1DZKkuKn/Rmq3VgJE1F7GmwArICmQ
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/bx9d4_NU9OUqEoYv5JHN0pCDrqY
Cc: dhcwg@ietf.org, 'Bernie Volz' <volz@cisco.com>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 09:23:59 -0000

Ted - If the server is not configured with information about a link, it =
should not respond.

Agreed. Then I might be confused on the other sentence says in section =
18.2.2- Receipt of Confirm Messages:
   When the server receives a Confirm message, the server determines
   whether the addresses in the Confirm message are appropriate for the
   link to which the client is attached. ...
   If any of the addresses do not pass this test, the server
   returns a status of NotOnLink.
Or the server does not necessarily to return the global 'NotOnLink'....

Marcin  - ...NotOnLink...) it either means misconfiguration or a rogue =
server sending Replies.

That sounds horrible ...:-) Anyway, may we need more clarification on =
the sentence under discussion...


Best Regards,
Leaf



-----Original Message-----
From: Marcin Siodelski [mailto:msiodelski@gmail.com]=20
Sent: Monday, May 26, 2014 8:29 PM
To: Ted Lemon
Cc: Leaf Yeh; Bernie Volz; Tomek Mrugalski; dhcwg@ietf.org; dhcpv6bis
Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315



On Mon 26 May 2014 14:17:14 CEST, Ted Lemon wrote:
> On May 26, 2014, at 6:54 AM, Marcin Siodelski <msiodelski@gmail.com> =
wrote:
>> Other
>> servers will send NotOnLink because they are not configured for the=20
>> particular subnet or so.
>
> That should never happen.   If the server is not configured with =
information about a link, it should not respond.   Does the document say =
it should?   If one server responds with NotOnLink and another with =
NoAddrsAvail, I think that's always a configuration error.
>

You're right. In 18.2.2 it is said that it should not respond when it =
doesn't have a knowledge of the prefixes on the link to which the client =
is connected. So, it really sounds that when there are two responses =
(one with NotOnLink, another one with Success) it either means =
misconfiguration or a rogue server sending Replies.

Marcin



From nobody Tue May 27 02:43:44 2014
Return-Path: <leaf.yeh.sdo@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 77F201A0073; Tue, 27 May 2014 02:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e0-7Fv57vStV; Tue, 27 May 2014 02:43:41 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5716F1A0049; Tue, 27 May 2014 02:43:41 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id ma3so9055887pbc.10 for <multiple recipients>; Tue, 27 May 2014 02:43:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=KO4DAAGK8dza3lm+wQVvwV3t098tKMnwYIC6nESe4Lg=; b=ZfiRlZb84Sca7WqD7eMnAA48hDjHhwq0YDtuvQVNGY/RILfF52hqLBZOhI1g5aQr2U 4UHXJxgqjnjACxxDdv3AnaGiALAZahC3oAhsaUZtDuZBR8NwYaNqPn/M5OoH4vjt1FJY 0CUfuBvbqAETpmpCcQOfLJx+BUlM/R2xr1qa6FekeUsHm8Xby+dSj1d1fRi2kcXWz6uD crBsDumlzJ0JDPel/Tz1ASsRubni0ynDHkUkz+FX7oE+VSjNgY0CBoYaQ6MEjsYIBZBF hhi19YJUSp2vdAvgQ7vNddgocAoAGWi9X+3Qxj2rMQ1By/OQsnrQ4ImtEOel0P/LfwXJ uVSw==
X-Received: by 10.68.97.129 with SMTP id ea1mr1996595pbb.73.1401183818311; Tue, 27 May 2014 02:43:38 -0700 (PDT)
Received: from PC ([218.241.103.104]) by mx.google.com with ESMTPSA id hb10sm22356869pbd.75.2014.05.27.02.43.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 27 May 2014 02:43:37 -0700 (PDT)
Message-ID: <53845e49.6a14450a.520e.ffffa3bc@mx.google.com>
X-Google-Original-Message-ID: <00f001cf7990$203c54b0$60b4fe10$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Ted Lemon'" <ted.lemon@nominum.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <0A1AEB66-C223-4E58-9574-FAF8A5FFFC72@nominum.com>
In-Reply-To: <0A1AEB66-C223-4E58-9574-FAF8A5FFFC72@nominum.com>
Date: Tue, 27 May 2014 17:43:29 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac942/iKAdY5RYOGSJuXPvw345mukAAsbxDw
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/WqrXat_FYnDaS8ZbRG7p2foakqk
Cc: dhcwg@ietf.org, 'Bernie Volz' <volz@cisco.com>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 09:43:42 -0000

Ted - I think this is explained somewhere in the document--if so, it might
be good to say so explicitly here.   If not, more explanation wouldn't hurt.

FYI, the RFC has 7 places mentioned 'NotOnLink', but it seems no place to
explain that ' NotOnLink is a great way to do a DoS attack'...


Best Regards,
Leaf



-----Original Message-----
From: Ted Lemon [mailto:ted.lemon@nominum.com] 
Sent: Monday, May 26, 2014 8:14 PM
To: Leaf Yeh
Cc: Bernie Volz; Tomek Mrugalski; dhcwg@ietf.org; dhcpv6bis
Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315

On May 25, 2014, at 10:53 PM, Leaf Yeh <leaf.yeh.sdo@gmail.com> wrote:
> 1.       If the client receive an Reply message indicating 'NoBinding' (or
even ' NoAddrsAvail'), the above sounds the client can still use the address
in the IA. Why?
> 2.       Why does the client could ignore 'any message' indicating
'NotOnLink' (in the 2nd half of the above paragraph)? It sounds conflict
with the 1st half of the above paragraph, not?

NoBinding and NoAddrsAvail are indications about the status of a single DHCP
server, but there may be more than one DHCP server on the wire.   So if a
server replies with such a message rather than a NotOnLink message, this
means that that server believes the client is correctly configured, but
isn't the server that configured it.   So if another server replies
NotOnLink, there's a misconfiguration-DHCP servers should never disagree
about that.   Ignoring the NotOnLink in this case may be incorrect, but
accepting it may also be incorrect.   And since NotOnLink is a great way to
do a DoS attack, it's better to ignore an erroneous NotOnLink than honor it.

I think this is explained somewhere in the document--if so, it might be good
to say so explicitly here.   If not, more explanation wouldn't hurt.


From nobody Tue May 27 04:10:25 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 4E2571A0099; Tue, 27 May 2014 04:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H5r3YuyDkeuH; Tue, 27 May 2014 04:10:00 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAA3E1A00A9; Tue, 27 May 2014 04:09:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5109; q=dns/txt; s=iport; t=1401188997; x=1402398597; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=RZwGSeZcwZtsB6NcS02Q71mPOjUkB6NVzSp8q8vg8lk=; b=LLImxONym0GYWs9I6RpJQcj/s2HowNpXUzJ8Pu1vzMch/F12R1Cv2u72 o4LlvRzlhxVqPrD7WPNTkt9UBKTFBza+rCexZjPmQPFg9sOnm1cQxyLZO xev+9uopSp4ybiVBD49KhqdCEkdLxXoANP5GjwY5G1lHosq1CSvwmenrg 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFADRxhFOtJV2Y/2dsb2JhbABZgwdSWMIVAYENFnSCJQEBAQMBOj8MBAIBCBEEAQEBChQJByERFAkIAQEEAQ0FCIgmAwkIDc4iDYYaF4tDeYFlMQcGgyWBFQSXfYMzi3iFcoM4bIEDJBw
X-IronPort-AV: E=Sophos;i="4.98,918,1392163200"; d="scan'208";a="47525445"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-5.cisco.com with ESMTP; 27 May 2014 11:09:55 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s4RB9tU6028229 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 May 2014 11:09:55 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.136]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Tue, 27 May 2014 06:09:55 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>, "'Marcin Siodelski'" <msiodelski@gmail.com>, "'Tomasz Mrugalski'" <tomasz.mrugalski@gmail.com>
Thread-Topic: [Dhcpv6bis] Reply to Confirm in RFC3315
Thread-Index: Ac94ja1zHl9NfJkXSMiqk9XERg5MCwAbQiyAAAkBxtAACjfckAAVHRdA
Date: Tue, 27 May 2014 11:09:53 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B04C26A@xmb-rcd-x04.cisco.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <5383f2e4.23de440a.5bc9.5d0d@mx.google.com>
In-Reply-To: <5383f2e4.23de440a.5bc9.5d0d@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.245.27]
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/FktgwOivw2s1xZ1VNuiaH5Ay-kc
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 11:10:04 -0000

It is not Success not NotOnLInk, so I would say the client would ignore thi=
s message.

- Bernie

-----Original Message-----
From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com]=20
Sent: Monday, May 26, 2014 10:05 PM
To: Bernie Volz (volz); 'Marcin Siodelski'; 'Tomasz Mrugalski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'
Subject: RE: [Dhcpv6bis] Reply to Confirm in RFC3315

BV > Other than global errors like UnspecFail, a Confirm will either contai=
n NotOnLink or Success. Nothing else.

If the client receive a reply with global error 'UnspecFail' , can the clie=
nt still 'use the addresses in the IA' indicating in the Confirm?


Best Regards,
Leaf



-----Original Message-----
From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Monday, May 26, 2014 7:42 PM
To: Marcin Siodelski; Leaf Yeh; 'Tomasz Mrugalski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'
Subject: RE: [Dhcpv6bis] Reply to Confirm in RFC3315

I think we're talking about Reply to Confirm. If so, why would these contai=
n NoAddrsAvail/NoBinding? They don't. Confirm does not validate a particula=
r client's addresses/PDs or bindings. It only validates whether the address=
es/PDs are on link or not.

Other than global errors like UnspecFail, a Confirm will either contain Not=
OnLink or Success. Nothing else.

And, yes the idea was there could be multiple servers some of which may sen=
d NotOnLink (as they may be lacking the configuration) but others that send=
 Success. The Success on can be taken.

In general servers that aren't authoritative for a particular set of links =
should not respond.

- Bernie

-----Original Message-----
From: Marcin Siodelski [mailto:msiodelski@gmail.com]
Sent: Monday, May 26, 2014 6:54 AM
To: Leaf Yeh; Bernie Volz (volz); 'Tomasz Mrugalski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'
Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315



On 26/05/14 04:53, Leaf Yeh wrote:
> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply=20
> Messages' of RFC3315:
>=20
> =20
>=20
> <quote>
>=20
> When the client receives a NotOnLink status from the server in
>=20
>    response to a Confirm message, the client performs DHCP server
>=20
>    solicitation, as described in section 17=20
> <http://tools.ietf.org/html/rfc3315#section-17>, and client-initiated
>=20
>    configuration as described in section 18=20
> <http://tools.ietf.org/html/rfc3315#section-18>.  If the client=20
> receives any
>=20
>    Reply messages that do not indicate a NotOnLink status, the client
>=20
>    can usethe addresses in the IA andignore any messages that indicate
>=20
>    a NotOnLink status.
>=20
> </quote>
>=20
> =20
>=20
> 1.       If the client receive an Reply message indicating 'NoBinding'
> (or even ' NoAddrsAvail'), the above sounds the client can still use=20
> the address in the IA. Why?

I think the context of the paragraph is important. The client sends Confirm
to any available server and client may receive multiple Replies.
Typically, one of these Replies will not contain NotOnLink status (or
contain Success) to indicate that client can use the address. Other servers
will send NotOnLink because they are not configured for the particular
subnet or so. So, the purpose of this paragraph is just to describe this
scenario.

Of course, client may receive Replies with other status codes too, and ther=
e
are relevant sections that talk about client behavior in this case". So a
couple of lines down:

"
   The client examines the status code in each IA individually.  If the
   status code is NoAddrsAvail, the client has received no usable
   addresses in the IA and may choose to try obtaining addresses for the
   IA from another server.  The client uses addresses and other
   information from any IAs that do not contain a Status Code option
   with the NoAddrsAvail code.  If the client receives no addresses in
   any of the IAs, it may either try another server (perhaps restarting
   the DHCP server discovery process) or use the Information-request
   message to obtain other configuration information only.
"

So, I don't really think there is any conflict here.

Also, you indicate that the client could use the address even though there
is a NoAddrsAvail or NoBinding. But, the returned IA will not have an
address to be used, because server places just status code NoBinding or
NoAddrsAvail in the IA and nothing else.



>=20
> 2.       Why does the client could ignore 'any message' indicating
> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds=20
> conflict with the 1^st half of the above paragraph, not?
>=20
> =20

The way I read it is that when the client receives at least one Reply that
has no NotOnLink status code, it may use the address it desires to use.
Otherwise it performs solicitation.

Perhaps, it could be more precise and say something along the lines: if non=
e
of the Reply messages received in response to a Confirm message indicates
success, the client performs solicitation. Otherwise, it may use the
address.

Marcin


From nobody Tue May 27 04:16:00 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 2DA751A00A8; Tue, 27 May 2014 04:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id THHtLwicOUNZ; Tue, 27 May 2014 04:15:54 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 433DB1A0099; Tue, 27 May 2014 04:15:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17530; q=dns/txt; s=iport; t=1401189351; x=1402398951; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=cXAMAaePLKf/ao3vPbcGoW/i51COeN3AW1FTGQ6Lquo=; b=dVcLVov04qu4aGvuV+u+mrSSJOb+XngwtMGkFiatRMPQvZH80hV8xqaN docJqxf9E8LawyqOGrjmts9nxCIuckmMoM3aSLRy/1Gm37CFRenP96T9p 6hWNc0XPfW86wlaROC61p3CqlYQvm8Ea131TckwUMtYjBKztotGpeOSiW U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAI9zhFOtJV2Z/2dsb2JhbABZgkJFUliCar8rARl0FnSCJQEBAQQjCkwQAgEIEQQBAQsdAwICAh8RFAkIAgQBDQUIiCYDEa9nnk8NhhoXiTOCEHmBZTEGAQaCbzaBFQSXfY8rhXKDOGyBQw
X-IronPort-AV: E=Sophos;i="4.98,918,1392163200";  d="scan'208,217";a="328135906"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 27 May 2014 11:15:50 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s4RBFo5H006789 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 May 2014 11:15:50 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.136]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Tue, 27 May 2014 06:15:50 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>, "'Marcin Siodelski'" <msiodelski@gmail.com>
Thread-Topic: Reply to Request in RFC3315
Thread-Index: AQHPeYlVgi+RrpQNj0CHqAOH+KEJm5tURn3Q
Date: Tue, 27 May 2014 11:15:49 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B04C349@xmb-rcd-x04.cisco.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049CB0@xmb-rcd-x04.cisco.com> <538452dd.c5a7440a.37fc.ffffa93f@mx.google.com>
In-Reply-To: <538452dd.c5a7440a.37fc.ffffa93f@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.245.27]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B04C349xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/bDU146ZWzsQtEaM5FneFNLHHS2M
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] Reply to Request in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 11:15:56 -0000

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

Pk15IHF1ZXN0aW9uIGlzIHdoeSB0aGUgc2VydmVyIGNhbid0IGlnbm9yZSAndGhlIGFkZHJlc3Nl
cyBpbiBhbnkgSUEgaW4gdGhlIG1lc3NhZ2UgZnJvbSB0aGUgY2xpZW50JywgYW5kIHNlbmQgYmFj
ayBhIG5ldyBhZGRyZXNzIGZvciB0aGUgSUEgcmVxdWVzdGVkIGJ5IHRoZSBjbGllbnQgcGVyIGl0
cyAoY29uZmlndXJhdGlvbikgcG9saWN5Lg0KDQpCZWNhdXNlIHRoZSBjbGllbnQgaGFzIG1vdmVk
IGFuZCBzbyB3ZSB3YW50IGl0IHRvIHN0YXJ0IG92ZXIg4oCTIGl0IG1heSBiZSB0aGF0IGxvdHMg
b2Ygb3RoZXIgaXRlbXMgaGF2ZSBjaGFuZ2VkIGFzIHdlbGwgKHBlcmhhcHMgZXZlbiBhIOKAnGJl
dHRlcuKAnSBzZXJ2ZXIgaXMgYXZhaWxhYmxlKS4NCg0KDQotICAgICAgICAgIEJlcm5pZQ0KDQpG
cm9tOiBMZWFmIFllaCBbbWFpbHRvOmxlYWYueWVoLnNkb0BnbWFpbC5jb21dDQpTZW50OiBUdWVz
ZGF5LCBNYXkgMjcsIDIwMTQgNDo1NSBBTQ0KVG86IEJlcm5pZSBWb2x6ICh2b2x6KTsgJ01hcmNp
biBTaW9kZWxza2knDQpDYzogZGhjd2dAaWV0Zi5vcmc7ICdkaGNwdjZiaXMnOyAnVG9tYXN6IE1y
dWdhbHNraScNClN1YmplY3Q6IFJlcGx5IHRvIFJlcXVlc3QgaW4gUkZDMzMxNQ0KDQoNCkJWPiBJ
biBSZXF1ZXN0IGNhc2UgaXQgaXMgd2l0aGluIHRoZSBJQSBhbmQgbWVhbnMgdGhhdCB0aGUgY2xp
ZW50J3MgcmVxdWVzdGVkIGFkZHJlc3NlcyAob3IgUEQpIGlzIG5vdCBvbiB0aGUgbGluay4uLlRo
ZSBSZXF1ZXN0IGNhc2UgaXMgYSBiaXQgd2VpcmQgaW4gb25lIHJlc3BlY3QgYXMgMTguMS44IHNh
eXM6DQoNCiAgIFdoZW4gdGhlIGNsaWVudCByZWNlaXZlcyBhIE5vdE9uTGluayBzdGF0dXMgZnJv
bSB0aGUgc2VydmVyIGluDQoNCiAgIHJlc3BvbnNlIHRvIGEgUmVxdWVzdCwgdGhlIGNsaWVudCBj
YW4gZWl0aGVyIHJlLWlzc3VlIHRoZSBSZXF1ZXN0DQoNCiAgIHdpdGhvdXQgc3BlY2lmeWluZyBh
bnkgYWRkcmVzc2VzIG9yIHJlc3RhcnQgdGhlIERIQ1Agc2VydmVyIGRpc2NvdmVyeQ0KDQogICBw
cm9jZXNzIChzZWUgc2VjdGlvbiAxNykuDQoNClRoaXMga2luZCBvZiBpbXBsaWVzIHRoYXQgaXQg
aXMgImdsb2JhbCIuIEkgdGhpbmsgdGhpcyBjYXNlIHdhcyB0byBoYW5kbGUgdGhlIGNsaWVudCBt
b3ZpbmcgYmV0d2VlbiBTb2xpY2l0IGFuZCBSZXF1ZXN0IChidXQgd2l0aCB0aGUgc2FtZSBzZXJ2
ZXIgc3RpbGwgcmVzcG9uZGluZyBzaW5jZSB0aGUgU2VydmVyIERVSUQgbWF0Y2hlcykuDQoNCg0K
DQpUaGUgYWJvdmUgcXVvdGVkIHBhcmFncmFwaCBpcyBhc3NvY2lhdGVkIHdpdGggb25lIHBhcmFn
cmFwaCBpbiBzZWN0aW9uIDE4LjIuMSwNCg0KICAgSWYgdGhlIHNlcnZlciBmaW5kcyB0aGF0IHRo
ZSBwcmVmaXggb24gb25lIG9yIG1vcmUgSVAgYWRkcmVzc2VzIGluDQoNCiAgIGFueSBJQSBpbiB0
aGUgbWVzc2FnZSBmcm9tIHRoZSBjbGllbnQgaXMgbm90IGFwcHJvcHJpYXRlIGZvciB0aGUgbGlu
aw0KDQogICB0byB3aGljaCB0aGUgY2xpZW50IGlzIGNvbm5lY3RlZCwgdGhlIHNlcnZlciBNVVNU
IHJldHVybiB0aGUgSUEgdG8NCg0KICAgdGhlIGNsaWVudCB3aXRoIGEgU3RhdHVzIENvZGUgb3B0
aW9uIHdpdGggdGhlIHZhbHVlIE5vdE9uTGluay4NCg0KDQoNCk15IHF1ZXN0aW9uIGlzIHdoeSB0
aGUgc2VydmVyIGNhbid0IGlnbm9yZSAndGhlIGFkZHJlc3NlcyBpbiBhbnkgSUEgaW4gdGhlIG1l
c3NhZ2UgZnJvbSB0aGUgY2xpZW50JywgYW5kIHNlbmQgYmFjayBhIG5ldyBhZGRyZXNzIGZvciB0
aGUgSUEgcmVxdWVzdGVkIGJ5IHRoZSBjbGllbnQgcGVyIGl0cyAoY29uZmlndXJhdGlvbikgcG9s
aWN5Lg0KDQoNCg0KDQoNCkJlc3QgUmVnYXJkcywNCg0KTGVhZg0KDQoNCg0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIg
MiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3Nl
LTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25z
b2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0
aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJn
aW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCgl0ZXh0LWFsaWduOmp1c3RpZnk7DQoJ
Zm9udC1zaXplOjEwLjVwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30N
CmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNv
bG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4u
TXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1
cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5N
c29QbGFpblRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2lu
LWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC41cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjt9DQpwLk1zb0FjZXRhdGUsIGxpLk1zb0FjZXRhdGUsIGRpdi5Nc29B
Y2V0YXRlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9v
biBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCXRl
eHQtYWxpZ246anVzdGlmeTsNCglmb250LXNpemU6OS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjt9DQpwLk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3Jh
cGgsIGRpdi5Nc29MaXN0UGFyYWdyYXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJn
aW4tdG9wOjBpbjsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1h
cmdpbi1sZWZ0Oi41aW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCXRleHQtYWxpZ246anVz
dGlmeTsNCglmb250LXNpemU6MTAuNXB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z
ZXJpZiI7fQ0Kc3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQbGFpbiBUZXh0
IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4g
VGV4dCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5CYWxsb29uVGV4dENoYXINCgl7
bXNvLXN0eWxlLW5hbWU6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCI7DQoJZm9udC1mYW1pbHk6IlRhaG9t
YSIsInNhbnMtc2VyaWYiO30NCnAuYSwgbGkuYSwgZGl2LmENCgl7bXNvLXN0eWxlLW5hbWU657qv
5paH5pysOw0KCW1zby1zdHlsZS1saW5rOiLnuq/mlofmnKwgQ2hhciI7DQoJbWFyZ2luOjBpbjsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJdGV4dC1hbGlnbjpqdXN0aWZ5Ow0KCWZvbnQtc2l6
ZToxMC41cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkNo
YXINCgl7bXNvLXN0eWxlLW5hbWU6Iue6r+aWh+acrCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJbXNvLXN0eWxlLWxpbms657qv5paH5pysOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
Iiwic2Fucy1zZXJpZiI7fQ0KcC5hMCwgbGkuYTAsIGRpdi5hMA0KCXttc28tc3R5bGUtbmFtZTrm
ibnms6jmoYbmlofmnKw7DQoJbXNvLXN0eWxlLWxpbms6IuaJueazqOahhuaWh+acrCBDaGFyIjsN
CgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCgl0ZXh0LWFsaWduOmp1c3Rp
Znk7DQoJZm9udC1zaXplOjEwLjVwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiO30NCnNwYW4uQ2hhcjANCgl7bXNvLXN0eWxlLW5hbWU6IuaJueazqOahhuaWh+acrCBDaGFy
IjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms65om55rOo5qGG5paH
5pysO30NCnNwYW4uRW1haWxTdHlsZTI1DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9
DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNp
emU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCglt
YXJnaW46MS4waW4gMS4yNWluIDEuMGluIDEuMjVpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21z
by1saXN0LWlkOjUwMTg5MjgxMjsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10
ZW1wbGF0ZS1pZHM6LTQyNzc4NTc4NCAyMTIxOTU0ODkyIDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4
Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0
IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtc3RhcnQtYXQ6MDsNCgltc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6LTsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtZm9u
dC1mYW1pbHk6Q2FsaWJyaTsNCgltc28tYmlkaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFu
Ijt9DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWls
eToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNA0KCXttc28tbGV2
ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZl
bC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0
LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsNQ0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCglt
c28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7
DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxp
c3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2
ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJl
ci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5n
ZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNv
LWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250
LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9y
bWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25l
Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47
DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4
dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4t
Ym90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSIgc3R5bGU9InRleHQtanVz
dGlmeS10cmltOnB1bmN0dWF0aW9uIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6Wkgt
Q04iPiZndDtNeSBxdWVzdGlvbiBpcyB3aHkgdGhlIHNlcnZlciBjYW4ndCBpZ25vcmUgJ3RoZSBh
ZGRyZXNzZXMgaW4gYW55IElBIGluIHRoZSBtZXNzYWdlIGZyb20gdGhlIGNsaWVudCcsIGFuZCBz
ZW5kIGJhY2sgYSBuZXcgYWRkcmVzcyBmb3IgdGhlIElBIHJlcXVlc3RlZCBieSB0aGUgY2xpZW50
IHBlciBpdHMgKGNvbmZpZ3VyYXRpb24pIHBvbGljeS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjojMUY0OTdEIj5CZWNhdXNlIHRo
ZSBjbGllbnQgaGFzIG1vdmVkIGFuZCBzbyB3ZSB3YW50IGl0IHRvIHN0YXJ0IG92ZXIg4oCTIGl0
IG1heSBiZSB0aGF0IGxvdHMgb2Ygb3RoZXIgaXRlbXMgaGF2ZSBjaGFuZ2VkIGFzIHdlbGwgKHBl
cmhhcHMgZXZlbiBhIOKAnGJldHRlcuKAnSBzZXJ2ZXIgaXMgYXZhaWxhYmxlKS48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9InRleHQtaW5kZW50Oi0uMjVpbjttc28tbGlz
dDpsMCBsZXZlbDEgbGZvMSI+PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Y29sb3I6IzFGNDk3RCI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+
LTxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3Nw
YW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Y29sb3I6IzFGNDk3RCI+QmVybmllPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Y29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGlu
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIGFsaWduPSJsZWZ0IiBzdHlsZT0idGV4dC1hbGlnbjps
ZWZ0Ij48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gTGVhZiBZZWggW21haWx0bzpsZWFmLnllaC5zZG9AZ21h
aWwuY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIE1heSAyNywgMjAxNCA0OjU1IEFN
PGJyPg0KPGI+VG86PC9iPiBCZXJuaWUgVm9seiAodm9seik7ICdNYXJjaW4gU2lvZGVsc2tpJzxi
cj4NCjxiPkNjOjwvYj4gZGhjd2dAaWV0Zi5vcmc7ICdkaGNwdjZiaXMnOyAnVG9tYXN6IE1ydWdh
bHNraSc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmVwbHkgdG8gUmVxdWVzdCBpbiBSRkMzMzE1PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IGFsaWduPSJsZWZ0IiBzdHlsZT0idGV4dC1hbGlnbjpsZWZ0Ij48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5n
dWFnZTpaSC1DTiI+QlYmZ3Q7IEluIFJlcXVlc3QgY2FzZSBpdCBpcyB3aXRoaW4gdGhlIElBIGFu
ZCBtZWFucyB0aGF0IHRoZSBjbGllbnQncyByZXF1ZXN0ZWQgYWRkcmVzc2VzIChvciBQRCkgaXMg
bm90IG9uIHRoZSBsaW5rLi4uVGhlIFJlcXVlc3QgY2FzZSBpcyBhIGJpdCB3ZWlyZCBpbiBvbmUg
cmVzcGVjdCBhcyAxOC4xLjggc2F5czo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZu
YnNwOyZuYnNwOyBXaGVuIHRoZSBjbGllbnQgcmVjZWl2ZXMgYSBOb3RPbkxpbmsgc3RhdHVzIGZy
b20gdGhlIHNlcnZlciBpbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jm5ic3A7Jm5i
c3A7IHJlc3BvbnNlIHRvIGEgUmVxdWVzdCwgdGhlIGNsaWVudCBjYW4gZWl0aGVyIHJlLWlzc3Vl
IHRoZSBSZXF1ZXN0PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mbmJzcDsmbmJzcDsg
d2l0aG91dCBzcGVjaWZ5aW5nIGFueSBhZGRyZXNzZXMgb3IgcmVzdGFydCB0aGUgREhDUCBzZXJ2
ZXIgZGlzY292ZXJ5PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mbmJzcDsmbmJzcDsg
cHJvY2VzcyAoc2VlIHNlY3Rpb24gMTcpLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+
VGhpcyBraW5kIG9mIGltcGxpZXMgdGhhdCBpdCBpcyAmcXVvdDtnbG9iYWwmcXVvdDsuIEkgdGhp
bmsgdGhpcyBjYXNlIHdhcyB0byBoYW5kbGUgdGhlIGNsaWVudCBtb3ZpbmcgYmV0d2VlbiBTb2xp
Y2l0IGFuZCBSZXF1ZXN0IChidXQgd2l0aCB0aGUgc2FtZSBzZXJ2ZXIgc3RpbGwgcmVzcG9uZGlu
ZyBzaW5jZSB0aGUgU2VydmVyIERVSUQgbWF0Y2hlcykuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdl
OlpILUNOIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPlRoZSBhYm92ZSBx
dW90ZWQgcGFyYWdyYXBoIGlzIGFzc29jaWF0ZWQgd2l0aCBvbmUgcGFyYWdyYXBoIGluIHNlY3Rp
b24gMTguMi4xLA0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mbmJzcDsmbmJzcDsm
bmJzcDtJZiB0aGUgc2VydmVyIGZpbmRzIHRoYXQgdGhlIHByZWZpeCBvbiBvbmUgb3IgbW9yZSBJ
UCBhZGRyZXNzZXMgaW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZuYnNwOyZuYnNw
OyBhbnkgSUEgaW4gdGhlIG1lc3NhZ2UgZnJvbSB0aGUgY2xpZW50IGlzIG5vdCBhcHByb3ByaWF0
ZSBmb3IgdGhlIGxpbms8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZuYnNwOyZuYnNw
OyB0byB3aGljaCB0aGUgY2xpZW50IGlzIGNvbm5lY3RlZCwgdGhlIHNlcnZlcg0KPHNwYW4gc3R5
bGU9ImNvbG9yOnJlZCI+TVVTVCByZXR1cm4gdGhlIElBIHRvPG86cD48L286cD48L3NwYW4+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJjb2xvcjpyZWQ7
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZuYnNwOyZuYnNwOyB0aGUgY2xpZW50IHdpdGgg
YSBTdGF0dXMgQ29kZSBvcHRpb24gd2l0aCB0aGUgdmFsdWUgTm90T25MaW5rPC9zcGFuPjxzcGFu
IHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5n
dWFnZTpaSC1DTiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj5NeSBxdWVz
dGlvbiBpcyB3aHkgdGhlIHNlcnZlciBjYW4ndCBpZ25vcmUgJ3RoZSBhZGRyZXNzZXMgaW4gYW55
IElBIGluIHRoZSBtZXNzYWdlIGZyb20gdGhlIGNsaWVudCcsIGFuZCBzZW5kIGJhY2sgYSBuZXcg
YWRkcmVzcyBmb3IgdGhlIElBIHJlcXVlc3RlZCBieSB0aGUgY2xpZW50IHBlciBpdHMgKGNvbmZp
Z3VyYXRpb24pIHBvbGljeS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxl
PSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1
YWdlOlpILUNOIj5CZXN0IFJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj5M
ZWFmPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4g
c3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3Qt
bGFuZ3VhZ2U6WkgtQ04iPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9i
b2R5Pg0KPC9odG1sPg0K

--_000_489D13FBFA9B3E41812EA89F188F018E1B04C349xmbrcdx04ciscoc_--


From nobody Tue May 27 04:16:40 2014
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1FF01A00A9; Tue, 27 May 2014 04:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cK9UqSisNMEX; Tue, 27 May 2014 04:13:49 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B312A1A00A8; Tue, 27 May 2014 04:13:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=50828; q=dns/txt; s=iport; t=1401189225; x=1402398825; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Hq/O2Tg5YgYd425Nbn4lgf/xwyun1Hod45meLLGZi40=; b=bk4ezwSYMQJqJn7erVbrsnPX/xTqPzlyaRZInzI5Y7Wgzcfkefz2PPUP 5lOzOsf93+FKPu0Kziylt4RJ9ZH5JjrG1Fjb+rardk5DVuPN44sknidu1 5qHAsHLR6LoG3xf2fcXFde/16BeO7topxgaE4aGND0q2ogNJ/Lk1Y6wT+ Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiQFAM5yhFOtJV2Z/2dsb2JhbABPCoJCRVJYgmq2L4h8ARl0FnSCJQEBAQMBIwpMBQcEAgEIEQQBAQsWAQYDAgICHxEUCQgBAQQOBQiIJgMJCA2vWp5PDYYaF4kzghB5gTorFhALBgEGgm82gRUEl32DM4t4hXKDOGyBAyQc
X-IronPort-AV: E=Sophos; i="4.98,918,1392163200"; d="scan'208,217"; a="47521252"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-3.cisco.com with ESMTP; 27 May 2014 11:13:44 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s4RBDi3a006072 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 May 2014 11:13:44 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.136]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0123.003; Tue, 27 May 2014 06:13:44 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
Thread-Topic: More Discussion - RE: [Dhcpv6bis] Reply to Confirm in RFC3315
Thread-Index: Ac94ja1zHl9NfJkXSMiqk9XERg5MCwAd2kKAACXQ9zA=
Date: Tue, 27 May 2014 11:13:43 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B04C315@xmb-rcd-x04.cisco.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <538425b3.08e6440a.08fb.7da2@mx.google.com>
In-Reply-To: <538425b3.08e6440a.08fb.7da2@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.245.27]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1B04C315xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/9bWqEG0TzcSTB3V82fGqN_9KzkE
X-Mailman-Approved-At: Tue, 27 May 2014 04:16:38 -0700
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] More Discussion - RE: [Dhcpv6bis] Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 11:13:52 -0000

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

V2hhdCBpcyB0aGUgcG9pbnQgb2YgYWxsIHRoaXM/DQoNCkNvbmZpcm0gZG9lcyBub3QgY29uZmly
bSBhbnkgbGVhc2VzIG9yIGxlYXNlIHRpbWVzLiBJdCBqdXN0IGNvbmZpcm1zIHRoYXQgdGhlIGFk
ZHJlc3NlcyBhcmUgT04gTElOSy4NCg0KQ29uZmlybSBpcyBzdXBwb3NlZCB0byBiZSBxdWljayBh
bmQgZWFzeSBmb3Igc2VydmVycyAobm8gZGF0YWJhc2UgbG9va3Mgb3Igd3JpdGVzIGFib3V0IGEg
c3BlY2lmaWMgbGVhc2UpIOKAkyBqdXN0IHRvIHZlcmlmeSB0aGF0IGFkZHJlc3NlcyBhcmUgb24g
bGluayAod2hpY2ggaXMgYW55IGVhc3kgdGVzdCB0byBsb2NhdGUgdGhlIHByZWZpeCBjb250YWlu
aW5nIHRoZSBhZGRyZXNzZXMpLiBJdCBpcyBOT1QgYSBSZW5ldy4NCg0KDQotICAgICAgICAgIEJl
cm5pZQ0KDQpGcm9tOiBMZWFmIFllaCBbbWFpbHRvOmxlYWYueWVoLnNkb0BnbWFpbC5jb21dDQpT
ZW50OiBUdWVzZGF5LCBNYXkgMjcsIDIwMTQgMTo0MiBBTQ0KVG86IEJlcm5pZSBWb2x6ICh2b2x6
KQ0KQ2M6IGRoY3dnQGlldGYub3JnOyAnZGhjcHY2YmlzJzsgJ1RvbWFzeiBNcnVnYWxza2knOyAn
TWFyY2luIFNpb2RlbHNraScNClN1YmplY3Q6IE1vcmUgRGlzY3Vzc2lvbiAtIFJFOiBbRGhjcHY2
YmlzXSBSZXBseSB0byBDb25maXJtIGluIFJGQzMzMTUNCg0KDQpXaGVuIEkgcmVhZCB0aGUgdGV4
dCBvbiAnUmVwbHkgdG8gQ29uZmlybScgaW4gUkZDMzMxNSwgdGhlIGZvbGxvd2luZyBzdGF0ZW1l
bnRzIHNvdW5kcyBtZSBhIGxpdHRsZSBtaXN1bmRlcnN0YW5kaW5nOg0KDQoNCg0KPHF1b3RlPiBA
IDE4LjEuMiAtIENyZWF0aW9uIGFuZCBUcmFuc21pc3Npb24gb2YgQ29uZmlybSBNZXNzYWdlcw0K
DQogICBUaGUgY2xpZW50IE1VU1QgaW5jbHVkZSBhIENsaWVudCBJZGVudGlmaWVyIG9wdGlvbiB0
byBpZGVudGlmeSBpdHNlbGYNCg0KICAgdG8gdGhlIHNlcnZlci4gIFRoZSBjbGllbnQgaW5jbHVk
ZXMgSUEgb3B0aW9ucyBmb3IgYWxsIG9mIHRoZSBJQXMNCg0KICAgYXNzaWduZWQgdG8gdGhlIGlu
dGVyZmFjZSBmb3Igd2hpY2ggdGhlIENvbmZpcm0gbWVzc2FnZSBpcyBiZWluZw0KDQogICBzZW50
LiAgVGhlIElBIG9wdGlvbnMgaW5jbHVkZSBhbGwgb2YgdGhlIGFkZHJlc3NlcyB0aGUgY2xpZW50
DQoNCiAgIGN1cnJlbnRseSBoYXMgYXNzb2NpYXRlZCB3aXRoIHRob3NlIElBcy4gIFRoZSBjbGll
bnQgU0hPVUxEIHNldCB0aGUNCg0KICAgVDEgYW5kIFQyIGZpZWxkcyBpbiBhbnkgSUFfTkEgb3B0
aW9ucywgYW5kIHRoZSBwcmVmZXJyZWQtbGlmZXRpbWUgYW5kDQoNCiAgIHZhbGlkLWxpZmV0aW1l
IGZpZWxkcyBpbiB0aGUgSUEgQWRkcmVzcyBvcHRpb25zIHRvIDAsIGFzIHRoZSBzZXJ2ZXINCg0K
ICAgd2lsbCBpZ25vcmUgdGhlc2UgZmllbGRzLg0KDQo8L3F1b3RlPg0KDQoNCg0KSXQgc291bmRz
IHRoZSBjbGllbnQgYXNrIHRoZSBzZXJ2ZXIgdG8gY29uZmlybSB0aGUgYWRkcmVzcyAoJiBJQSkg
Zm9yIGhpcyBpbnRlcmZhY2UsIGJ1dCB3aHkgbm90IGFzayB0aGUgc2VydmVyIHRvIGNvbmZpcm0g
dGhlIHZhbHVlcyBvZiBsZWFzZSB0aW1lcnMgKFQxL1QyIGZvciBJQSwgcHJlZmVycmVkL3ZhbGlk
LUxUIGZvciBhZGRyZXNzKSBoZSBoYXMuDQoNCg0KDQoNCg0KPHF1b3RlPiBAIDE4LjIuMiAtUmVj
ZWlwdCBvZiBDb25maXJtIE1lc3NhZ2VzDQoNCiAgIFRoZSBzZXJ2ZXIgaWdub3JlcyB0aGUgVDEg
YW5kIFQyIGZpZWxkcyBpbiB0aGUgSUEgb3B0aW9ucyBhbmQgdGhlDQoNCiAgIHByZWZlcnJlZC1s
aWZldGltZSBhbmQgdmFsaWQtbGlmZXRpbWUgZmllbGRzIGluIHRoZSBJQSBBZGRyZXNzDQoNCiAg
IG9wdGlvbnMuDQoNCiAgIC4uLg0KDQogICBUaGUgc2VydmVyIE1VU1QgaW5jbHVkZSBhIFNlcnZl
ciBJZGVudGlmaWVyIG9wdGlvbiBjb250YWluaW5nIHRoZQ0KDQogICBzZXJ2ZXIncyBEVUlEIGFu
ZCB0aGUgQ2xpZW50IElkZW50aWZpZXIgb3B0aW9uIGZyb20gdGhlIENvbmZpcm0NCg0KICAgbWVz
c2FnZSBpbiB0aGUgUmVwbHkgbWVzc2FnZS4gIFRoZSBzZXJ2ZXIgaW5jbHVkZXMgYSBTdGF0dXMg
Q29kZQ0KDQogICBvcHRpb24gaW5kaWNhdGluZyB0aGUgc3RhdHVzIG9mIHRoZSBDb25maXJtIG1l
c3NhZ2UuDQoNCjwvcXVvdGU+DQoNCg0KDQoNCg0KQ2VydGFpbmx5LCB0aGUgc2VydmVyIGNvbmZp
cm1lZCB0aGUgYWRkcmVzcyAoJiB0aGUgYXNzb2NpYXRlZCBJQUlEKSBvZiBjbGllbnQgYmFzZWQg
b24gaXRzIHRoaXMgb3duIGRhdGFiYXNlLiBJZiB0aGUgc2VydmVyIHJldHVybmVkIHRoZSBnbG9i
YWwg4oCYU3VjY2Vzc+KAmSBpbiB0aGUgU3RhdHVzIENvZGUgb3B0aW9uLCBpdCBzb3VuZHMgYWxs
IHRoZSBpbmZvcm1hdGlvbiB0aGUgY2xpZW50IHByb3ZpZGVkIGluIENvbmZpcm0gaGFzIGJlZW4g
Y29uZmlybWVkLCBhbmQgYXNzdW1lZCB0aGUgY2xpZW50IGhhcyB0aGUgc2FtZSBsZWFzZSBhcyB0
aGF0IHJlY29kZWQgaW4gdGhlIGRhdGFiYXNlIG9mIHNlcnZlci4NCg0KDQoNCkJ1dCBJIHRoaW5r
IGl0IHNvdW5kcyBtdWNoIGJldHRlciB0aGUgc2VydmVyIGNvdWxkIGNvbmZpcm0gKG9yIHVwZGF0
ZSkgYWxsIHRoZSBpbmZvcm1hdGlvbiBhYm91dCB0aGUgbGVhc2UgKGluY2x1ZGluZyBhZGRyZXNz
IGFuZCB0aGUgdmFsdWUgb2YgdGltZXJzKSBmb3IgdGhlIGNsaWVudCBpbiB0aGUgUmVwbHkgbWVz
c2FnZS4gSXQgbG9va3MgbXVjaCBjbGVhcmVyLCBhbmQgY29zdCBsaXR0bGUgaW4gdGhlIFJlcGx5
Lg0KDQoNCg0KVGhlIGdsb2JhbCBTdGF0dXMgQ29kZSBsb29rcyB1bnNwZWNpZmllZCB0byBlYWNo
IGFkZHJlc3MgKGFuZCBpdHMgbGVhc2UpLCB3aGljaCBpbiBmYWN0IG5lZWRzIHRvIGJlIGNvbmZp
cm1lZC4NCg0KDQoNCg0KDQpCZXN0IFJlZ2FyZHMsDQoNCkxlYWYNCg0KDQoNCg0KDQoNCg0KLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IE1hcmNpbiBTaW9kZWxza2kgW21haWx0bzpt
c2lvZGVsc2tpQGdtYWlsLmNvbV0NClNlbnQ6IE1vbmRheSwgTWF5IDI2LCAyMDE0IDc6NTYgUE0N
ClRvOiBCZXJuaWUgVm9seiAodm9seikNCkNjOiBkaGN3Z0BpZXRmLm9yZzxtYWlsdG86ZGhjd2dA
aWV0Zi5vcmc+OyAnZGhjcHY2YmlzJzsgTGVhZiBZZWg7ICdUb21hc3ogTXJ1Z2Fsc2tpJw0KU3Vi
amVjdDogUmU6IFtEaGNwdjZiaXNdIFJlcGx5IHRvIENvbmZpcm0gaW4gUkZDMzMxNQ0KDQoNCg0K
WWVzLCBOb0FkZHJzQXZhaWwvTm9CaW5kaW5nIGFyZSBub3Qgc2VudCBpbiByZXNwb25zZSB0byBD
b25maXJtLiBNYXkgcG9pbnQgcmF0aGVyIHdhcyB0aGF0ICpldmVuIGluIGEgbW9yZSBnZW5lcmFs
IGNhc2UqIHRoZSBzZXJ2ZXIgd2lsbCBub3Qgc2VuZCBhZGRyZXNzZXMgaW4gdGhlIElBIGluIHdo
aWNoIHRoZXJlIGlzIE5vQWRkcnNBdmFpbCBvciBOb0JpbmRpbmcuDQoNClRoaXMgY29tbWVudCB3
YXMgYmV5b25kIHRoZSBjb250ZXh0IG9mIENvbmZpcm0vUmVwbHkgbWVzc2FnZSBleGNoYW5nZS4N
Cg0KDQoNCk1hcmNpbg0KDQoNCg0KT24gTW9uIDI2IE1heSAyMDE0IDEzOjQxOjMwIENFU1QsIEJl
cm5pZSBWb2x6ICh2b2x6KSB3cm90ZToNCg0KPiBJIHRoaW5rIHdlJ3JlIHRhbGtpbmcgYWJvdXQg
UmVwbHkgdG8gQ29uZmlybS4gSWYgc28sIHdoeSB3b3VsZCB0aGVzZSBjb250YWluIE5vQWRkcnNB
dmFpbC9Ob0JpbmRpbmc/IFRoZXkgZG9uJ3QuIENvbmZpcm0gZG9lcyBub3QgdmFsaWRhdGUgYSBw
YXJ0aWN1bGFyIGNsaWVudCdzIGFkZHJlc3Nlcy9QRHMgb3IgYmluZGluZ3MuIEl0IG9ubHkgdmFs
aWRhdGVzIHdoZXRoZXIgdGhlIGFkZHJlc3Nlcy9QRHMgYXJlIG9uIGxpbmsgb3Igbm90Lg0KDQo+
DQoNCj4gT3RoZXIgdGhhbiBnbG9iYWwgZXJyb3JzIGxpa2UgVW5zcGVjRmFpbCwgYSBDb25maXJt
IHdpbGwgZWl0aGVyIGNvbnRhaW4gTm90T25MaW5rIG9yIFN1Y2Nlc3MuIE5vdGhpbmcgZWxzZS4N
Cg0KPg0KDQo+IEFuZCwgeWVzIHRoZSBpZGVhIHdhcyB0aGVyZSBjb3VsZCBiZSBtdWx0aXBsZSBz
ZXJ2ZXJzIHNvbWUgb2Ygd2hpY2ggbWF5IHNlbmQgTm90T25MaW5rIChhcyB0aGV5IG1heSBiZSBs
YWNraW5nIHRoZSBjb25maWd1cmF0aW9uKSBidXQgb3RoZXJzIHRoYXQgc2VuZCBTdWNjZXNzLiBU
aGUgU3VjY2VzcyBvbiBjYW4gYmUgdGFrZW4uDQoNCj4NCg0KPiBJbiBnZW5lcmFsIHNlcnZlcnMg
dGhhdCBhcmVuJ3QgYXV0aG9yaXRhdGl2ZSBmb3IgYSBwYXJ0aWN1bGFyIHNldCBvZiBsaW5rcyBz
aG91bGQgbm90IHJlc3BvbmQuDQoNCj4NCg0KPiAtIEJlcm5pZQ0KDQo+DQoNCj4gLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCg0KPiBGcm9tOiBNYXJjaW4gU2lvZGVsc2tpIFttYWlsdG86bXNp
b2RlbHNraUBnbWFpbC5jb21dDQoNCj4gU2VudDogTW9uZGF5LCBNYXkgMjYsIDIwMTQgNjo1NCBB
TQ0KDQo+IFRvOiBMZWFmIFllaDsgQmVybmllIFZvbHogKHZvbHopOyAnVG9tYXN6IE1ydWdhbHNr
aScNCg0KPiBDYzogZGhjd2dAaWV0Zi5vcmc8bWFpbHRvOmRoY3dnQGlldGYub3JnPjsgJ2RoY3B2
NmJpcycNCg0KPiBTdWJqZWN0OiBSZTogW0RoY3B2NmJpc10gUmVwbHkgdG8gQ29uZmlybSBpbiBS
RkMzMzE1DQoNCj4NCg0KPg0KDQo+DQoNCj4gT24gMjYvMDUvMTQgMDQ6NTMsIExlYWYgWWVoIHdy
b3RlOg0KDQo+PiBHb3QgMiBxdWVzdGlvbnMgb24gdGhlIHRleHQgaW4gU2VjdGlvbiAxOC4xLjgt
J1JlY2VpcHQgb2YgUmVwbHkNCg0KPj4gTWVzc2FnZXMnIG9mIFJGQzMzMTU6DQoNCj4+DQoNCj4+
DQoNCj4+DQoNCj4+IDxxdW90ZT4NCg0KPj4NCg0KPj4gV2hlbiB0aGUgY2xpZW50IHJlY2VpdmVz
IGEgTm90T25MaW5rIHN0YXR1cyBmcm9tIHRoZSBzZXJ2ZXIgaW4NCg0KPj4NCg0KPj4gICAgcmVz
cG9uc2UgdG8gYSBDb25maXJtIG1lc3NhZ2UsIHRoZSBjbGllbnQgcGVyZm9ybXMgREhDUCBzZXJ2
ZXINCg0KPj4NCg0KPj4gICAgc29saWNpdGF0aW9uLCBhcyBkZXNjcmliZWQgaW4gc2VjdGlvbiAx
Nw0KDQo+PiA8aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjMzMxNSNzZWN0aW9uLTE3Piwg
YW5kIGNsaWVudC1pbml0aWF0ZWQNCg0KPj4NCg0KPj4gICAgY29uZmlndXJhdGlvbiBhcyBkZXNj
cmliZWQgaW4gc2VjdGlvbiAxOA0KDQo+PiA8aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZj
MzMxNSNzZWN0aW9uLTE4Pi4gIElmIHRoZSBjbGllbnQNCg0KPj4gcmVjZWl2ZXMgYW55DQoNCj4+
DQoNCj4+ICAgIFJlcGx5IG1lc3NhZ2VzIHRoYXQgZG8gbm90IGluZGljYXRlIGEgTm90T25MaW5r
IHN0YXR1cywgdGhlIGNsaWVudA0KDQo+Pg0KDQo+PiAgICBjYW4gdXNldGhlIGFkZHJlc3NlcyBp
biB0aGUgSUEgYW5kaWdub3JlIGFueSBtZXNzYWdlcyB0aGF0DQoNCj4+IGluZGljYXRlDQoNCj4+
DQoNCj4+ICAgIGEgTm90T25MaW5rIHN0YXR1cy4NCg0KPj4NCg0KPj4gPC9xdW90ZT4NCg0KPj4N
Cg0KPj4NCg0KPj4NCg0KPj4gMS4gICAgICAgSWYgdGhlIGNsaWVudCByZWNlaXZlIGFuIFJlcGx5
IG1lc3NhZ2UgaW5kaWNhdGluZyAnTm9CaW5kaW5nJw0KDQo+PiAob3IgZXZlbiAnIE5vQWRkcnNB
dmFpbCcpLCB0aGUgYWJvdmUgc291bmRzIHRoZSBjbGllbnQgY2FuIHN0aWxsIHVzZQ0KDQo+PiB0
aGUgYWRkcmVzcyBpbiB0aGUgSUEuIFdoeT8NCg0KPg0KDQo+IEkgdGhpbmsgdGhlIGNvbnRleHQg
b2YgdGhlIHBhcmFncmFwaCBpcyBpbXBvcnRhbnQuIFRoZSBjbGllbnQgc2VuZHMgQ29uZmlybSB0
byBhbnkgYXZhaWxhYmxlIHNlcnZlciBhbmQgY2xpZW50IG1heSByZWNlaXZlIG11bHRpcGxlIFJl
cGxpZXMuDQoNCj4gVHlwaWNhbGx5LCBvbmUgb2YgdGhlc2UgUmVwbGllcyB3aWxsIG5vdCBjb250
YWluIE5vdE9uTGluayBzdGF0dXMgKG9yIGNvbnRhaW4gU3VjY2VzcykgdG8gaW5kaWNhdGUgdGhh
dCBjbGllbnQgY2FuIHVzZSB0aGUgYWRkcmVzcy4gT3RoZXIgc2VydmVycyB3aWxsIHNlbmQgTm90
T25MaW5rIGJlY2F1c2UgdGhleSBhcmUgbm90IGNvbmZpZ3VyZWQgZm9yIHRoZSBwYXJ0aWN1bGFy
IHN1Ym5ldCBvciBzby4gU28sIHRoZSBwdXJwb3NlIG9mIHRoaXMgcGFyYWdyYXBoIGlzIGp1c3Qg
dG8gZGVzY3JpYmUgdGhpcyBzY2VuYXJpby4NCg0KPg0KDQo+IE9mIGNvdXJzZSwgY2xpZW50IG1h
eSByZWNlaXZlIFJlcGxpZXMgd2l0aCBvdGhlciBzdGF0dXMgY29kZXMgdG9vLCBhbmQgdGhlcmUg
YXJlIHJlbGV2YW50IHNlY3Rpb25zIHRoYXQgdGFsayBhYm91dCBjbGllbnQgYmVoYXZpb3IgaW4g
dGhpcyBjYXNlIi4gU28gYSBjb3VwbGUgb2YgbGluZXMgZG93bjoNCg0KPg0KDQo+ICINCg0KPiAg
ICBUaGUgY2xpZW50IGV4YW1pbmVzIHRoZSBzdGF0dXMgY29kZSBpbiBlYWNoIElBIGluZGl2aWR1
YWxseS4gIElmIHRoZQ0KDQo+ICAgIHN0YXR1cyBjb2RlIGlzIE5vQWRkcnNBdmFpbCwgdGhlIGNs
aWVudCBoYXMgcmVjZWl2ZWQgbm8gdXNhYmxlDQoNCj4gICAgYWRkcmVzc2VzIGluIHRoZSBJQSBh
bmQgbWF5IGNob29zZSB0byB0cnkgb2J0YWluaW5nIGFkZHJlc3NlcyBmb3IgdGhlDQoNCj4gICAg
SUEgZnJvbSBhbm90aGVyIHNlcnZlci4gIFRoZSBjbGllbnQgdXNlcyBhZGRyZXNzZXMgYW5kIG90
aGVyDQoNCj4gICAgaW5mb3JtYXRpb24gZnJvbSBhbnkgSUFzIHRoYXQgZG8gbm90IGNvbnRhaW4g
YSBTdGF0dXMgQ29kZSBvcHRpb24NCg0KPiAgICB3aXRoIHRoZSBOb0FkZHJzQXZhaWwgY29kZS4g
IElmIHRoZSBjbGllbnQgcmVjZWl2ZXMgbm8gYWRkcmVzc2VzIGluDQoNCj4gICAgYW55IG9mIHRo
ZSBJQXMsIGl0IG1heSBlaXRoZXIgdHJ5IGFub3RoZXIgc2VydmVyIChwZXJoYXBzIHJlc3RhcnRp
bmcNCg0KPiAgICB0aGUgREhDUCBzZXJ2ZXIgZGlzY292ZXJ5IHByb2Nlc3MpIG9yIHVzZSB0aGUg
SW5mb3JtYXRpb24tcmVxdWVzdA0KDQo+ICAgIG1lc3NhZ2UgdG8gb2J0YWluIG90aGVyIGNvbmZp
Z3VyYXRpb24gaW5mb3JtYXRpb24gb25seS4NCg0KPiAiDQoNCj4NCg0KPiBTbywgSSBkb24ndCBy
ZWFsbHkgdGhpbmsgdGhlcmUgaXMgYW55IGNvbmZsaWN0IGhlcmUuDQoNCj4NCg0KPiBBbHNvLCB5
b3UgaW5kaWNhdGUgdGhhdCB0aGUgY2xpZW50IGNvdWxkIHVzZSB0aGUgYWRkcmVzcyBldmVuIHRo
b3VnaCB0aGVyZSBpcyBhIE5vQWRkcnNBdmFpbCBvciBOb0JpbmRpbmcuIEJ1dCwgdGhlIHJldHVy
bmVkIElBIHdpbGwgbm90IGhhdmUgYW4gYWRkcmVzcyB0byBiZSB1c2VkLCBiZWNhdXNlIHNlcnZl
ciBwbGFjZXMganVzdCBzdGF0dXMgY29kZSBOb0JpbmRpbmcgb3IgTm9BZGRyc0F2YWlsIGluIHRo
ZSBJQSBhbmQgbm90aGluZyBlbHNlLg0KDQo+DQoNCj4NCg0KPg0KDQo+Pg0KDQo+PiAyLiAgICAg
ICBXaHkgZG9lcyB0aGUgY2xpZW50IGNvdWxkIGlnbm9yZSAnYW55IG1lc3NhZ2UnIGluZGljYXRp
bmcNCg0KPj4gJ05vdE9uTGluaycgKGluIHRoZSAyXm5kIGhhbGYgb2YgdGhlIGFib3ZlIHBhcmFn
cmFwaCk/IEl0IHNvdW5kcw0KDQo+PiBjb25mbGljdCB3aXRoIHRoZSAxXnN0IGhhbGYgb2YgdGhl
IGFib3ZlIHBhcmFncmFwaCwgbm90Pw0KDQo+Pg0KDQo+Pg0KDQo+DQoNCj4gVGhlIHdheSBJIHJl
YWQgaXQgaXMgdGhhdCB3aGVuIHRoZSBjbGllbnQgcmVjZWl2ZXMgYXQgbGVhc3Qgb25lIFJlcGx5
IHRoYXQgaGFzIG5vIE5vdE9uTGluayBzdGF0dXMgY29kZSwgaXQgbWF5IHVzZSB0aGUgYWRkcmVz
cyBpdCBkZXNpcmVzIHRvIHVzZS4gT3RoZXJ3aXNlIGl0IHBlcmZvcm1zIHNvbGljaXRhdGlvbi4N
Cg0KPg0KDQo+IFBlcmhhcHMsIGl0IGNvdWxkIGJlIG1vcmUgcHJlY2lzZSBhbmQgc2F5IHNvbWV0
aGluZyBhbG9uZyB0aGUgbGluZXM6IGlmIG5vbmUgb2YgdGhlIFJlcGx5IG1lc3NhZ2VzIHJlY2Vp
dmVkIGluIHJlc3BvbnNlIHRvIGEgQ29uZmlybSBtZXNzYWdlIGluZGljYXRlcyBzdWNjZXNzLCB0
aGUgY2xpZW50IHBlcmZvcm1zIHNvbGljaXRhdGlvbi4gT3RoZXJ3aXNlLCBpdCBtYXkgdXNlIHRo
ZSBhZGRyZXNzLg0KDQo+DQoNCj4gTWFyY2luDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIg
MiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3Nl
LTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25z
b2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0
aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJn
aW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCgl0ZXh0LWFsaWduOmp1c3RpZnk7DQoJ
Zm9udC1zaXplOjEwLjVwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30N
CmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNv
bG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4u
TXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1
cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5N
c29QbGFpblRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2lu
LWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC41cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjt9DQpwLk1zb0FjZXRhdGUsIGxpLk1zb0FjZXRhdGUsIGRpdi5Nc29B
Y2V0YXRlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9v
biBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCXRl
eHQtYWxpZ246anVzdGlmeTsNCglmb250LXNpemU6OS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjt9DQpwLk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3Jh
cGgsIGRpdi5Nc29MaXN0UGFyYWdyYXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJn
aW4tdG9wOjBpbjsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1h
cmdpbi1sZWZ0Oi41aW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCXRleHQtYWxpZ246anVz
dGlmeTsNCglmb250LXNpemU6MTAuNXB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z
ZXJpZiI7fQ0Kc3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQbGFpbiBUZXh0
IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4g
VGV4dCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5CYWxsb29uVGV4dENoYXINCgl7
bXNvLXN0eWxlLW5hbWU6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCI7DQoJZm9udC1mYW1pbHk6IlRhaG9t
YSIsInNhbnMtc2VyaWYiO30NCnAuYSwgbGkuYSwgZGl2LmENCgl7bXNvLXN0eWxlLW5hbWU657qv
5paH5pysOw0KCW1zby1zdHlsZS1saW5rOiLnuq/mlofmnKwgQ2hhciI7DQoJbWFyZ2luOjBpbjsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJdGV4dC1hbGlnbjpqdXN0aWZ5Ow0KCWZvbnQtc2l6
ZToxMC41cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkNo
YXINCgl7bXNvLXN0eWxlLW5hbWU6Iue6r+aWh+acrCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJbXNvLXN0eWxlLWxpbms657qv5paH5pysOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
Iiwic2Fucy1zZXJpZiI7fQ0KcC5hMCwgbGkuYTAsIGRpdi5hMA0KCXttc28tc3R5bGUtbmFtZTrm
ibnms6jmoYbmlofmnKw7DQoJbXNvLXN0eWxlLWxpbms6IuaJueazqOahhuaWh+acrCBDaGFyIjsN
CgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCgl0ZXh0LWFsaWduOmp1c3Rp
Znk7DQoJZm9udC1zaXplOjEwLjVwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiO30NCnNwYW4uQ2hhcjANCgl7bXNvLXN0eWxlLW5hbWU6IuaJueazqOahhuaWh+acrCBDaGFy
IjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms65om55rOo5qGG5paH
5pysO30NCnNwYW4uRW1haWxTdHlsZTI1DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9
DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNp
emU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCglt
YXJnaW46MS4waW4gMS4yNWluIDEuMGluIDEuMjVpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21z
by1saXN0LWlkOjE2NjExNTA3NDY7DQoJbXNvLWxpc3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3Qt
dGVtcGxhdGUtaWRzOi0xODMzMjgxNDEyIC0xMDk1MzE5NTEwIDY3Njk4NjkxIDY3Njk4NjkzIDY3
Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBs
aXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtc3RhcnQtYXQ6MDsNCgltc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6LTsNCgltc28tbGV2ZWwtdGFiLXN0b3A6
bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4y
NWluOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3Qt
Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCgltc28tYmlkaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJv
bWFuIjt9DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZh
bWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3Rv
cDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
LjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNA0KCXttc28t
bGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1s
ZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0
ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVs
NQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0K
QGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28t
bGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpX
aW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglm
b250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNv
LWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28t
bGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJ
dGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJn
aW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQotLT48L3N0eWxlPjwh
LS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3Bp
ZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1s
Pg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRh
dGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8
Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSIgc3R5bGU9InRleHQt
anVzdGlmeS10cmltOnB1bmN0dWF0aW9uIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjoj
MUY0OTdEIj5XaGF0IGlzIHRoZSBwb2ludCBvZiBhbGwgdGhpcz88bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjojMUY0OTdEIj5Db25m
aXJtIGRvZXMgbm90IGNvbmZpcm0gYW55IGxlYXNlcyBvciBsZWFzZSB0aW1lcy4gSXQganVzdCBj
b25maXJtcyB0aGF0IHRoZSBhZGRyZXNzZXMgYXJlIE9OIExJTksuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Y29sb3I6IzFGNDk3RCI+Q29u
ZmlybSBpcyBzdXBwb3NlZCB0byBiZSBxdWljayBhbmQgZWFzeSBmb3Igc2VydmVycyAobm8gZGF0
YWJhc2UgbG9va3Mgb3Igd3JpdGVzIGFib3V0IGEgc3BlY2lmaWMgbGVhc2UpIOKAkyBqdXN0IHRv
IHZlcmlmeSB0aGF0IGFkZHJlc3NlcyBhcmUgb24gbGluayAod2hpY2ggaXMgYW55IGVhc3kgdGVz
dCB0byBsb2NhdGUgdGhlIHByZWZpeA0KIGNvbnRhaW5pbmcgdGhlIGFkZHJlc3NlcykuIEl0IGlz
IE5PVCBhIFJlbmV3LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0idGV4
dC1pbmRlbnQ6LS4yNWluO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj48IVtpZiAhc3VwcG9ydExp
c3RzXT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjojMUY0OTdEIj48c3BhbiBz
dHlsZT0ibXNvLWxpc3Q6SWdub3JlIj4tPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGlt
ZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjojMUY0OTdEIj5CZXJuaWU8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0K
PGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3Bh
ZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249Imxl
ZnQiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBMZWFmIFllaCBb
bWFpbHRvOmxlYWYueWVoLnNkb0BnbWFpbC5jb21dDQo8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2Rh
eSwgTWF5IDI3LCAyMDE0IDE6NDIgQU08YnI+DQo8Yj5Ubzo8L2I+IEJlcm5pZSBWb2x6ICh2b2x6
KTxicj4NCjxiPkNjOjwvYj4gZGhjd2dAaWV0Zi5vcmc7ICdkaGNwdjZiaXMnOyAnVG9tYXN6IE1y
dWdhbHNraSc7ICdNYXJjaW4gU2lvZGVsc2tpJzxicj4NCjxiPlN1YmplY3Q6PC9iPiBNb3JlIERp
c2N1c3Npb24gLSBSRTogW0RoY3B2NmJpc10gUmVwbHkgdG8gQ29uZmlybSBpbiBSRkMzMzE1PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IGFsaWduPSJsZWZ0IiBzdHlsZT0idGV4dC1hbGlnbjpsZWZ0Ij48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5n
dWFnZTpaSC1DTiI+V2hlbiBJIHJlYWQgdGhlIHRleHQgb24gJ1JlcGx5IHRvIENvbmZpcm0nIGlu
IFJGQzMzMTUsIHRoZSBmb2xsb3dpbmcgc3RhdGVtZW50cyBzb3VuZHMgbWUgYSBsaXR0bGUgbWlz
dW5kZXJzdGFuZGluZzo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJt
c28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmx0O3F1b3RlJmd0OyBAIDE4LjEuMiAtIENyZWF0
aW9uIGFuZCBUcmFuc21pc3Npb24gb2YgQ29uZmlybSBNZXNzYWdlczxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1s
YW5ndWFnZTpaSC1DTiI+Jm5ic3A7Jm5ic3A7IFRoZSBjbGllbnQgTVVTVCBpbmNsdWRlIGEgQ2xp
ZW50IElkZW50aWZpZXIgb3B0aW9uIHRvIGlkZW50aWZ5IGl0c2VsZjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1s
YW5ndWFnZTpaSC1DTiI+Jm5ic3A7Jm5ic3A7IHRvIHRoZSBzZXJ2ZXIuJm5ic3A7IFRoZSBjbGll
bnQgaW5jbHVkZXMgSUEgb3B0aW9ucyBmb3INCjxzcGFuIHN0eWxlPSJjb2xvcjpyZWQiPmFsbCBv
ZiB0aGUgSUFzPG86cD48L286cD48L3NwYW4+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIHN0eWxlPSJjb2xvcjpyZWQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04i
PiZuYnNwOyZuYnNwOyBhc3NpZ25lZCB0byB0aGUgaW50ZXJmYWNlPC9zcGFuPjxzcGFuIHN0eWxl
PSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+IGZvciB3aGljaCB0aGUgQ29uZmlybSBtZXNz
YWdlIGlzIGJlaW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mbmJzcDsmbmJzcDsg
c2VudC4mbmJzcDsgVGhlIElBIG9wdGlvbnMgaW5jbHVkZSBhbGwgb2YgdGhlIGFkZHJlc3NlcyB0
aGUgY2xpZW50PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mbmJzcDsmbmJzcDsgY3Vy
cmVudGx5IGhhcyBhc3NvY2lhdGVkIHdpdGggdGhvc2UgSUFzLiZuYnNwOyBUaGUgY2xpZW50IFNI
T1VMRCBzZXQgdGhlPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mbmJzcDsmbmJzcDsg
PHNwYW4gc3R5bGU9ImNvbG9yOnJlZCI+DQpUMSBhbmQgVDIgZmllbGRzIGluIGFueSBJQV9OQSBv
cHRpb25zLCBhbmQgdGhlIHByZWZlcnJlZC1saWZldGltZSBhbmQ8bzpwPjwvbzpwPjwvc3Bhbj48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOnJl
ZDttc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jm5ic3A7Jm5ic3A7IHZhbGlkLWxpZmV0aW1l
IGZpZWxkcyBpbiB0aGUgSUEgQWRkcmVzcyBvcHRpb25zIHRvIDA8L3NwYW4+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4sIGFzIHRoZSBzZXJ2ZXI8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6WkgtQ04iPiZuYnNwOyZuYnNwOyB3aWxsIGlnbm9yZSB0aGVzZSBmaWVsZHMu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5
bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mbHQ7L3F1b3RlJmd0OzxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFy
ZWFzdC1sYW5ndWFnZTpaSC1DTiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNO
Ij5JdCBzb3VuZHMgdGhlIGNsaWVudCBhc2sgdGhlIHNlcnZlciB0byBjb25maXJtIHRoZSBhZGRy
ZXNzICgmYW1wOyBJQSkgZm9yIGhpcyBpbnRlcmZhY2UsIGJ1dA0KPGI+d2h5IG5vdDwvYj4gYXNr
IHRoZSBzZXJ2ZXIgdG8gY29uZmlybSB0aGUgdmFsdWVzIG9mIGxlYXNlIHRpbWVycyAoVDEvVDIg
Zm9yIElBLCBwcmVmZXJyZWQvdmFsaWQtTFQgZm9yIGFkZHJlc3MpIGhlIGhhcy48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1D
TiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mbHQ7cXVvdGUmZ3Q7IEAg
MTguMi4yIC1SZWNlaXB0IG9mIENvbmZpcm0gTWVzc2FnZXM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6WkgtQ04iPiZuYnNwOyZuYnNwOyBUaGUgc2VydmVyIDxzcGFuIHN0eWxlPSJjb2xvcjpyZWQi
Pg0KaWdub3Jlczwvc3Bhbj4gdGhlIFQxIGFuZCBUMiBmaWVsZHMgaW4gdGhlIElBIG9wdGlvbnMg
YW5kIHRoZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxz
cGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jm5ic3A7Jm5ic3A7IHByZWZl
cnJlZC1saWZldGltZSBhbmQgdmFsaWQtbGlmZXRpbWUgZmllbGRzIGluIHRoZSBJQSBBZGRyZXNz
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5
bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mbmJzcDsmbmJzcDsgb3B0aW9ucy48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0i
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZuYnNwOyZuYnNwOyAuLi48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6WkgtQ04iPiZuYnNwOyZuYnNwOyBUaGUgc2VydmVyIE1VU1QgaW5jbHVkZSBh
IFNlcnZlciBJZGVudGlmaWVyIG9wdGlvbiBjb250YWluaW5nIHRoZTxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1s
YW5ndWFnZTpaSC1DTiI+Jm5ic3A7Jm5ic3A7IHNlcnZlcidzIERVSUQgYW5kIHRoZSBDbGllbnQg
SWRlbnRpZmllciBvcHRpb24gZnJvbSB0aGUgQ29uZmlybTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFn
ZTpaSC1DTiI+Jm5ic3A7Jm5ic3A7IG1lc3NhZ2UgaW4gdGhlIFJlcGx5IG1lc3NhZ2UuJm5ic3A7
DQo8c3BhbiBzdHlsZT0iY29sb3I6cmVkIj5UaGUgc2VydmVyIGluY2x1ZGVzIGEgU3RhdHVzIENv
ZGU8bzpwPjwvbzpwPjwvc3Bhbj48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gc3R5bGU9ImNvbG9yOnJlZDttc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jm5ic3A7
Jm5ic3A7IG9wdGlvbiBpbmRpY2F0aW5nIHRoZSBzdGF0dXMgb2YgdGhlIENvbmZpcm0gbWVzc2Fn
ZS48L3NwYW4+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZsdDsvcXVvdGUmZ3Q7PG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxh
bmd1YWdlOlpILUNOIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0
eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Q2VydGFpbmx5LCB0aGUgc2VydmVyIGNv
bmZpcm1lZCB0aGUgYWRkcmVzcyAoJmFtcDsgdGhlIGFzc29jaWF0ZWQgSUFJRCkgb2YgY2xpZW50
IGJhc2VkIG9uIGl0cyB0aGlzIG93biBkYXRhYmFzZS4gSWYgdGhlIHNlcnZlciByZXR1cm5lZCB0
aGUgZ2xvYmFsDQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O21zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj7igJg8L3NwYW4+PHNwYW4gc3R5
bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj5TdWNjZXNzPC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Ozttc28tZmFyZWFzdC1sYW5ndWFn
ZTpaSC1DTiI+4oCZPC9zcGFuPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1D
TiI+IGluDQogdGhlIFN0YXR1cyBDb2RlIG9wdGlvbiwgaXQgc291bmRzIGFsbCB0aGUgaW5mb3Jt
YXRpb24gdGhlIGNsaWVudCBwcm92aWRlZCBpbiBDb25maXJtIGhhcyBiZWVuIGNvbmZpcm1lZCwg
YW5kDQo8Yj5hc3N1bWVkIHRoZSBjbGllbnQgaGFzIHRoZSBzYW1lIGxlYXNlIGFzIHRoYXQgcmVj
b2RlZCBpbiB0aGUgZGF0YWJhc2Ugb2Ygc2VydmVyLjwvYj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6WkgtQ04iPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+QnV0IEkgdGhp
bmsgaXQgc291bmRzIG11Y2ggYmV0dGVyIHRoZSBzZXJ2ZXIgY291bGQgY29uZmlybSAob3IgdXBk
YXRlKSBhbGwgdGhlIGluZm9ybWF0aW9uIGFib3V0IHRoZSBsZWFzZSAoaW5jbHVkaW5nIGFkZHJl
c3MgYW5kIHRoZSB2YWx1ZSBvZiB0aW1lcnMpIGZvciB0aGUgY2xpZW50IGluIHRoZSBSZXBseSBt
ZXNzYWdlLiBJdCBsb29rcw0KIG11Y2ggY2xlYXJlciwgYW5kIGNvc3QgbGl0dGxlIGluIHRoZSBS
ZXBseS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3Bh
biBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFz
dC1sYW5ndWFnZTpaSC1DTiI+VGhlIGdsb2JhbCBTdGF0dXMgQ29kZSBsb29rcyB1bnNwZWNpZmll
ZCB0byBlYWNoIGFkZHJlc3MgKGFuZCBpdHMgbGVhc2UpLCB3aGljaCBpbiBmYWN0IG5lZWRzIHRv
IGJlIGNvbmZpcm1lZC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJt
c28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdl
OlpILUNOIj5CZXN0IFJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj5MZWFm
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5
bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6WkgtQ04iPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5
bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t
LTxicj4NCkZyb206IE1hcmNpbiBTaW9kZWxza2kgWzxhIGhyZWY9Im1haWx0bzptc2lvZGVsc2tp
QGdtYWlsLmNvbSI+bWFpbHRvOm1zaW9kZWxza2lAZ21haWwuY29tPC9hPl0NCjxicj4NClNlbnQ6
IE1vbmRheSwgTWF5IDI2LCAyMDE0IDc6NTYgUE08YnI+DQpUbzogQmVybmllIFZvbHogKHZvbHop
PGJyPg0KQ2M6IDxhIGhyZWY9Im1haWx0bzpkaGN3Z0BpZXRmLm9yZyI+ZGhjd2dAaWV0Zi5vcmc8
L2E+OyAnZGhjcHY2YmlzJzsgTGVhZiBZZWg7ICdUb21hc3ogTXJ1Z2Fsc2tpJzxicj4NClN1Ympl
Y3Q6IFJlOiBbRGhjcHY2YmlzXSBSZXBseSB0byBDb25maXJtIGluIFJGQzMzMTU8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1D
TiI+WWVzLCBOb0FkZHJzQXZhaWwvTm9CaW5kaW5nIGFyZSBub3Qgc2VudCBpbiByZXNwb25zZSB0
byBDb25maXJtLiBNYXkgcG9pbnQgcmF0aGVyIHdhcyB0aGF0ICpldmVuIGluIGEgbW9yZSBnZW5l
cmFsIGNhc2UqIHRoZSBzZXJ2ZXIgd2lsbCBub3Qgc2VuZCBhZGRyZXNzZXMgaW4gdGhlIElBIGlu
IHdoaWNoIHRoZXJlIGlzIE5vQWRkcnNBdmFpbA0KIG9yIE5vQmluZGluZy4gPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJl
YXN0LWxhbmd1YWdlOlpILUNOIj5UaGlzIGNvbW1lbnQgd2FzIGJleW9uZCB0aGUgY29udGV4dCBv
ZiBDb25maXJtL1JlcGx5IG1lc3NhZ2UgZXhjaGFuZ2UuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdl
OlpILUNOIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPk1hcmNpbjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJt
c28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdl
OlpILUNOIj5PbiBNb24gMjYgTWF5IDIwMTQgMTM6NDE6MzAgQ0VTVCwgQmVybmllIFZvbHogKHZv
bHopIHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyBJIHRoaW5rIHdl
J3JlIHRhbGtpbmcgYWJvdXQgUmVwbHkgdG8gQ29uZmlybS4gSWYgc28sIHdoeSB3b3VsZCB0aGVz
ZSBjb250YWluIE5vQWRkcnNBdmFpbC9Ob0JpbmRpbmc/IFRoZXkgZG9uJ3QuIENvbmZpcm0gZG9l
cyBub3QgdmFsaWRhdGUgYSBwYXJ0aWN1bGFyIGNsaWVudCdzIGFkZHJlc3Nlcy9QRHMgb3IgYmlu
ZGluZ3MuIEl0DQogb25seSB2YWxpZGF0ZXMgd2hldGhlciB0aGUgYWRkcmVzc2VzL1BEcyBhcmUg
b24gbGluayBvciBub3QuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5
bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7IE90aGVyIHRoYW4gZ2xvYmFsIGVy
cm9ycyBsaWtlIFVuc3BlY0ZhaWwsIGEgQ29uZmlybSB3aWxsIGVpdGhlciBjb250YWluIE5vdE9u
TGluayBvciBTdWNjZXNzLiBOb3RoaW5nIGVsc2UuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpI
LUNOIj4mZ3Q7PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7IEFuZCwg
eWVzIHRoZSBpZGVhIHdhcyB0aGVyZSBjb3VsZCBiZSBtdWx0aXBsZSBzZXJ2ZXJzIHNvbWUgb2Yg
d2hpY2ggbWF5IHNlbmQgTm90T25MaW5rIChhcyB0aGV5IG1heSBiZSBsYWNraW5nIHRoZSBjb25m
aWd1cmF0aW9uKSBidXQgb3RoZXJzIHRoYXQgc2VuZCBTdWNjZXNzLiBUaGUgU3VjY2VzcyBvbiBj
YW4gYmUgdGFrZW4uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7IEluIGdlbmVyYWwgc2VydmVycyB0aGF0
IGFyZW4ndCBhdXRob3JpdGF0aXZlIGZvciBhIHBhcnRpY3VsYXIgc2V0IG9mIGxpbmtzIHNob3Vs
ZCBub3QgcmVzcG9uZC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDs8bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHls
ZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsgLSBCZXJuaWU8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDs8bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6Wkgt
Q04iPiZndDsgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6WkgtQ04iPiZndDsgRnJvbTogTWFyY2luIFNpb2RlbHNraSBbPGEgaHJlZj0ibWFpbHRvOm1z
aW9kZWxza2lAZ21haWwuY29tIj48c3BhbiBzdHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRl
Y29yYXRpb246bm9uZSI+bWFpbHRvOm1zaW9kZWxza2lAZ21haWwuY29tPC9zcGFuPjwvYT5dPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7IFNlbnQ6IE1vbmRheSwgTWF5IDI2LCAy
MDE0IDY6NTQgQU08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsgVG86IExlYWYg
WWVoOyBCZXJuaWUgVm9seiAodm9seik7ICdUb21hc3ogTXJ1Z2Fsc2tpJzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFz
dC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyBDYzogPGEgaHJlZj0ibWFpbHRvOmRoY3dnQGlldGYub3Jn
Ij4NCjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3JhdGlvbjpub25lIj5k
aGN3Z0BpZXRmLm9yZzwvc3Bhbj48L2E+OyAnZGhjcHY2YmlzJzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5n
dWFnZTpaSC1DTiI+Jmd0OyBTdWJqZWN0OiBSZTogW0RoY3B2NmJpc10gUmVwbHkgdG8gQ29uZmly
bSBpbiBSRkMzMzE1PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxh
bmd1YWdlOlpILUNOIj4mZ3Q7PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4m
Z3Q7IE9uIDI2LzA1LzE0IDA0OjUzLCBMZWFmIFllaCB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6WkgtQ04iPiZndDsmZ3Q7IEdvdCAyIHF1ZXN0aW9ucyBvbiB0aGUgdGV4dCBpbiBTZWN0
aW9uIDE4LjEuOC0nUmVjZWlwdCBvZiBSZXBseQ0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpI
LUNOIj4mZ3Q7Jmd0OyBNZXNzYWdlcycgb2YgUkZDMzMxNTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6WkgtQ04iPiZndDsmZ3Q7PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4m
Z3Q7Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyZndDs8bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBz
dHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsmZ3Q7ICZsdDtxdW90ZSZndDs8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHls
ZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsmZ3Q7PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJl
YXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7Jmd0OyBXaGVuIHRoZSBjbGllbnQgcmVjZWl2ZXMgYSBO
b3RPbkxpbmsgc3RhdHVzIGZyb20gdGhlIHNlcnZlciBpbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFn
ZTpaSC1DTiI+Jmd0OyZndDs8bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZn
dDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHJlc3BvbnNlIHRvIGEgQ29uZmlybSBtZXNzYWdlLCB0
aGUgY2xpZW50IHBlcmZvcm1zIERIQ1Agc2VydmVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpI
LUNOIj4mZ3Q7Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyZn
dDsmbmJzcDsmbmJzcDsmbmJzcDsgc29saWNpdGF0aW9uLCBhcyBkZXNjcmliZWQgaW4gc2VjdGlv
biAxNw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNw
YW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7Jmd0OyAmbHQ7PGEgaHJl
Zj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjMzMxNSNzZWN0aW9uLTE3Ij48c3BhbiBz
dHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246bm9uZSI+aHR0cDovL3Rvb2xz
LmlldGYub3JnL2h0bWwvcmZjMzMxNSNzZWN0aW9uLTE3PC9zcGFuPjwvYT4mZ3Q7LCBhbmQgY2xp
ZW50LWluaXRpYXRlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyZndDs8bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBz
dHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IGNvbmZpZ3VyYXRpb24gYXMgZGVzY3JpYmVkIGluIHNlY3Rpb24gMTgNCjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFy
ZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyZndDsgJmx0OzxhIGhyZWY9Imh0dHA6Ly90b29scy5p
ZXRmLm9yZy9odG1sL3JmYzMzMTUjc2VjdGlvbi0xOCI+PHNwYW4gc3R5bGU9ImNvbG9yOndpbmRv
d3RleHQ7dGV4dC1kZWNvcmF0aW9uOm5vbmUiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL3Jm
YzMzMTUjc2VjdGlvbi0xODwvc3Bhbj48L2E+Jmd0Oy4mbmJzcDsgSWYgdGhlIGNsaWVudA0KPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7Jmd0OyByZWNlaXZlcyBhbnk8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsmZ3Q7PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxh
bmd1YWdlOlpILUNOIj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyBSZXBseSBtZXNzYWdlcyB0
aGF0IGRvIG5vdCBpbmRpY2F0ZSBhIE5vdE9uTGluayBzdGF0dXMsIHRoZSBjbGllbnQ8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsmZ3Q7PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxh
bmd1YWdlOlpILUNOIj4mZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyBjYW4gdXNldGhlIGFkZHJl
c3NlcyBpbiB0aGUgSUEgYW5kaWdub3JlIGFueSBtZXNzYWdlcyB0aGF0DQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsmZ3Q7IGluZGljYXRlPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1
YWdlOlpILUNOIj4mZ3Q7Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+
Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsgYSBOb3RPbkxpbmsgc3RhdHVzLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFy
ZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyZndDs8bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6WkgtQ04iPiZndDsmZ3Q7ICZsdDsvcXVvdGUmZ3Q7PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdl
OlpILUNOIj4mZ3Q7Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0
OyZndDs8bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsmZ3Q7PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5
bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7Jmd0OyAxLiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBJZiB0aGUgY2xpZW50IHJlY2VpdmUgYW4gUmVwbHkgbWVz
c2FnZSBpbmRpY2F0aW5nICdOb0JpbmRpbmcnPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNO
Ij4mZ3Q7Jmd0OyAob3IgZXZlbiAnIE5vQWRkcnNBdmFpbCcpLCB0aGUgYWJvdmUgc291bmRzIHRo
ZSBjbGllbnQgY2FuIHN0aWxsIHVzZQ0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4m
Z3Q7Jmd0OyB0aGUgYWRkcmVzcyBpbiB0aGUgSUEuIFdoeT88bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6WkgtQ04iPiZndDs8bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsg
SSB0aGluayB0aGUgY29udGV4dCBvZiB0aGUgcGFyYWdyYXBoIGlzIGltcG9ydGFudC4gVGhlIGNs
aWVudCBzZW5kcyBDb25maXJtIHRvIGFueSBhdmFpbGFibGUgc2VydmVyIGFuZCBjbGllbnQgbWF5
IHJlY2VpdmUgbXVsdGlwbGUgUmVwbGllcy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04i
PiZndDsgVHlwaWNhbGx5LCBvbmUgb2YgdGhlc2UgUmVwbGllcyB3aWxsIG5vdCBjb250YWluIE5v
dE9uTGluayBzdGF0dXMgKG9yIGNvbnRhaW4gU3VjY2VzcykgdG8gaW5kaWNhdGUgdGhhdCBjbGll
bnQgY2FuIHVzZSB0aGUgYWRkcmVzcy4gT3RoZXIgc2VydmVycyB3aWxsIHNlbmQgTm90T25MaW5r
IGJlY2F1c2UgdGhleSBhcmUgbm90IGNvbmZpZ3VyZWQNCiBmb3IgdGhlIHBhcnRpY3VsYXIgc3Vi
bmV0IG9yIHNvLiBTbywgdGhlIHB1cnBvc2Ugb2YgdGhpcyBwYXJhZ3JhcGggaXMganVzdCB0byBk
ZXNjcmliZSB0aGlzIHNjZW5hcmlvLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0
OzxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxz
cGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyBPZiBjb3Vyc2UsIGNs
aWVudCBtYXkgcmVjZWl2ZSBSZXBsaWVzIHdpdGggb3RoZXIgc3RhdHVzIGNvZGVzIHRvbywgYW5k
IHRoZXJlIGFyZSByZWxldmFudCBzZWN0aW9ucyB0aGF0IHRhbGsgYWJvdXQgY2xpZW50IGJlaGF2
aW9yIGluIHRoaXMgY2FzZSZxdW90Oy4gU28gYSBjb3VwbGUgb2YgbGluZXMgZG93bjo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDs8bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6WkgtQ04iPiZndDsgJnF1b3Q7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7
Jm5ic3A7Jm5ic3A7Jm5ic3A7IFRoZSBjbGllbnQgZXhhbWluZXMgdGhlIHN0YXR1cyBjb2RlIGlu
IGVhY2ggSUEgaW5kaXZpZHVhbGx5LiZuYnNwOyBJZiB0aGU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6WkgtQ04iPiZndDsmbmJzcDsmbmJzcDsmbmJzcDsgc3RhdHVzIGNvZGUgaXMgTm9BZGRyc0F2
YWlsLCB0aGUgY2xpZW50IGhhcyByZWNlaXZlZCBubyB1c2FibGU8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6WkgtQ04iPiZndDsmbmJzcDsmbmJzcDsmbmJzcDsgYWRkcmVzc2VzIGluIHRoZSBJQSBh
bmQgbWF5IGNob29zZSB0byB0cnkgb2J0YWluaW5nIGFkZHJlc3NlcyBmb3IgdGhlPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1m
YXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7IElBIGZyb20gYW5v
dGhlciBzZXJ2ZXIuJm5ic3A7IFRoZSBjbGllbnQgdXNlcyBhZGRyZXNzZXMgYW5kIG90aGVyPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGluZm9y
bWF0aW9uIGZyb20gYW55IElBcyB0aGF0IGRvIG5vdCBjb250YWluIGEgU3RhdHVzIENvZGUgb3B0
aW9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4g
c3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IHdpdGggdGhlIE5vQWRkcnNBdmFpbCBjb2RlLiZuYnNwOyBJZiB0aGUgY2xpZW50IHJlY2VpdmVz
IG5vIGFkZHJlc3NlcyBpbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyZuYnNw
OyZuYnNwOyZuYnNwOyBhbnkgb2YgdGhlIElBcywgaXQgbWF5IGVpdGhlciB0cnkgYW5vdGhlciBz
ZXJ2ZXIgKHBlcmhhcHMgcmVzdGFydGluZzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+
Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyB0aGUgREhDUCBzZXJ2ZXIgZGlzY292ZXJ5IHByb2Nlc3Mp
IG9yIHVzZSB0aGUgSW5mb3JtYXRpb24tcmVxdWVzdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpa
SC1DTiI+Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyBtZXNzYWdlIHRvIG9idGFpbiBvdGhlciBjb25m
aWd1cmF0aW9uIGluZm9ybWF0aW9uIG9ubHkuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNO
Ij4mZ3Q7ICZxdW90OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OzxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxl
PSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyBTbywgSSBkb24ndCByZWFsbHkgdGhp
bmsgdGhlcmUgaXMgYW55IGNvbmZsaWN0IGhlcmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpI
LUNOIj4mZ3Q7PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7IEFsc28s
IHlvdSBpbmRpY2F0ZSB0aGF0IHRoZSBjbGllbnQgY291bGQgdXNlIHRoZSBhZGRyZXNzIGV2ZW4g
dGhvdWdoIHRoZXJlIGlzIGEgTm9BZGRyc0F2YWlsIG9yIE5vQmluZGluZy4gQnV0LCB0aGUgcmV0
dXJuZWQgSUEgd2lsbCBub3QgaGF2ZSBhbiBhZGRyZXNzIHRvIGJlIHVzZWQsIGJlY2F1c2Ugc2Vy
dmVyIHBsYWNlcyBqdXN0DQogc3RhdHVzIGNvZGUgTm9CaW5kaW5nIG9yIE5vQWRkcnNBdmFpbCBp
biB0aGUgSUEgYW5kIG5vdGhpbmcgZWxzZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04i
PiZndDs8bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDs8bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0i
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDs8bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6WkgtQ04iPiZndDsmZ3Q7PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNO
Ij4mZ3Q7Jmd0OyAyLiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBXaHkgZG9l
cyB0aGUgY2xpZW50IGNvdWxkIGlnbm9yZSAnYW55IG1lc3NhZ2UnIGluZGljYXRpbmc8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04iPiZndDsmZ3Q7ICdOb3RPbkxpbmsnIChpbiB0aGUgMl5u
ZCBoYWxmIG9mIHRoZSBhYm92ZSBwYXJhZ3JhcGgpPyBJdCBzb3VuZHMNCjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFz
dC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyZndDsgY29uZmxpY3Qgd2l0aCB0aGUgMV5zdCBoYWxmIG9m
IHRoZSBhYm92ZSBwYXJhZ3JhcGgsIG5vdD88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6WkgtQ04i
PiZndDsmZ3Q7PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4mZ3Q7Jmd0Ozxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFu
IHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFy
ZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyBUaGUgd2F5IEkgcmVhZCBpdCBpcyB0aGF0IHdoZW4g
dGhlIGNsaWVudCByZWNlaXZlcyBhdCBsZWFzdCBvbmUgUmVwbHkgdGhhdCBoYXMgbm8gTm90T25M
aW5rIHN0YXR1cyBjb2RlLCBpdCBtYXkgdXNlIHRoZSBhZGRyZXNzIGl0IGRlc2lyZXMgdG8gdXNl
LiBPdGhlcndpc2UgaXQgcGVyZm9ybXMgc29saWNpdGF0aW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5n
dWFnZTpaSC1DTiI+Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0
OyBQZXJoYXBzLCBpdCBjb3VsZCBiZSBtb3JlIHByZWNpc2UgYW5kIHNheSBzb21ldGhpbmcgYWxv
bmcgdGhlIGxpbmVzOiBpZiBub25lIG9mIHRoZSBSZXBseSBtZXNzYWdlcyByZWNlaXZlZCBpbiBy
ZXNwb25zZSB0byBhIENvbmZpcm0gbWVzc2FnZSBpbmRpY2F0ZXMgc3VjY2VzcywgdGhlIGNsaWVu
dCBwZXJmb3JtcyBzb2xpY2l0YXRpb24uDQogT3RoZXJ3aXNlLCBpdCBtYXkgdXNlIHRoZSBhZGRy
ZXNzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFu
IHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJtc28tZmFy
ZWFzdC1sYW5ndWFnZTpaSC1DTiI+Jmd0OyBNYXJjaW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_489D13FBFA9B3E41812EA89F188F018E1B04C315xmbrcdx04ciscoc_--


From nobody Tue May 27 05:39:55 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 775FB1A011D; Tue, 27 May 2014 05:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 N9vXqS8DXJPv; Tue, 27 May 2014 05:39:49 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 553D01A011A; Tue, 27 May 2014 05:39:49 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4C17D1B8078; Tue, 27 May 2014 05:39:46 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 2B19019005C; Tue, 27 May 2014 05:39:46 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 27 May 2014 05:39:46 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <538425b3.08e6440a.08fb.7da2@mx.google.com>
Date: Tue, 27 May 2014 08:39:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <CB7501C1-7FB1-440B-9209-60D310D85832@nominum.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <538425b3.08e6440a.08fb.7da2@mx.google.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/JK7VIDQ-qsxreWzytha91bq7oNU
Cc: dhcwg@ietf.org, Bernie Volz <volz@cisco.com>, dhcpv6bis <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] More Discussion - RE: Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 12:39:50 -0000

On May 27, 2014, at 1:42 AM, Leaf Yeh <leaf.yeh.sdo@gmail.com> wrote:
> It sounds the client ask the server to confirm the address (& IA) for =
his interface, but why not ask the server to confirm the values of lease =
timers (T1/T2 for IA, preferred/valid-LT for address) he has.

That would be a change to the protocol, and would serve no purpose, =
since the client already knows its lease times.   The point of this =
exercise is not to make gratuitous changes to the protocol.


From nobody Tue May 27 07:57:15 2014
Return-Path: <leaf.yeh.sdo@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 0F8861A0157; Tue, 27 May 2014 07:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id llA6BPmRqEW0; Tue, 27 May 2014 07:57:05 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AB851A0166; Tue, 27 May 2014 07:57:05 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id rd3so9324401pab.29 for <multiple recipients>; Tue, 27 May 2014 07:57:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:thread-index:content-language; bh=KDWmI4V3Eke5M+87aGsfD4VfwsElJ7F2y6dvAtcc57U=; b=jbApPaKLubvwhtmAP0vxS2U5oAFKkkzkvGtFVrTAsH9JzyzFxda841c9FggET75A1d SkziZ0Voh6hFMP5lri3Sg2hEIhich0UDnJT9nkDTSgLI63q1ee3y/YLIGTK5Q4J3oPlk dStp5ydEkpqeRjzOTxyd1vi8T/toX79nCXq2pjxoq1fnYpxmqp+DvwSIapjn60Wvm1gd 1G9PCGnx0Ln0tR6tyjlFLpFG39u4jPiz3RGfUIYWllHSJ0ke/F4iLnSWME4WsQtpkXAb tZal+Y3ZXISzzCpHT7mS6hFnMsK4g8gdR0CP15t1xTcPZX39pxtL/+jMlr+gJ18kSWuz 8sAA==
X-Received: by 10.66.246.138 with SMTP id xw10mr36429868pac.142.1401202622280;  Tue, 27 May 2014 07:57:02 -0700 (PDT)
Received: from PC ([111.199.99.113]) by mx.google.com with ESMTPSA id ix7sm23757409pbd.36.2014.05.27.07.56.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 27 May 2014 07:57:01 -0700 (PDT)
Message-ID: <5384a7bd.671a450a.7fd5.ffffddd4@mx.google.com>
X-Google-Original-Message-ID: <015201cf79bb$e7589060$b609b120$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>, "'Marcin Siodelski'" <msiodelski@gmail.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049CB0@xmb-rcd-x04.cisco.com> <538452dd.c5a7440a.37fc.ffffa93f@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E1B04C349@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B04C349@xmb-rcd-x04.cisco.com>
Date: Tue, 27 May 2014 22:56:52 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0153_01CF79FE.F57BD060"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHPeYlVgi+RrpQNj0CHqAOH+KEJm5tURn3QgAAx1dA=
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/7UVjLFzSDBVUkQQjkYeU3u4pxwE
Cc: dhcwg@ietf.org, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] Reply to Request in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 14:57:09 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0153_01CF79FE.F57BD060
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

BV> Because the client has moved=E2=80=A6

=20

I guess Reply to Request is not assumed the client has moved.

=20

=20

Best Regards,

Leaf

=20

=20

=20

From: Bernie Volz (volz) [mailto:volz@cisco.com]=20
Sent: Tuesday, May 27, 2014 7:16 PM
To: Leaf Yeh; 'Marcin Siodelski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'
Subject: RE: Reply to Request in RFC3315

=20

>My question is why the server can't ignore 'the addresses in any IA in =
the message from the client', and send back a new address for the IA =
requested by the client per its (configuration) policy.

=20

Because the client has moved and so we want it to start over =E2=80=93 =
it may be that lots of other items have changed as well (perhaps even a =
=E2=80=9Cbetter=E2=80=9D server is available).

=20

-          Bernie

=20

From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com]=20
Sent: Tuesday, May 27, 2014 4:55 AM
To: Bernie Volz (volz); 'Marcin Siodelski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'
Subject: Reply to Request in RFC3315

=20

BV> In Request case it is within the IA and means that the client's =
requested addresses (or PD) is not on the link...The Request case is a =
bit weird in one respect as 18.1.8 says:

   When the client receives a NotOnLink status from the server in

   response to a Request, the client can either re-issue the Request

   without specifying any addresses or restart the DHCP server discovery

   process (see section 17).

This kind of implies that it is "global". I think this case was to =
handle the client moving between Solicit and Request (but with the same =
server still responding since the Server DUID matches).

=20

The above quoted paragraph is associated with one paragraph in section =
18.2.1,=20

   If the server finds that the prefix on one or more IP addresses in

   any IA in the message from the client is not appropriate for the link

   to which the client is connected, the server MUST return the IA to

   the client with a Status Code option with the value NotOnLink.

=20

My question is why the server can't ignore 'the addresses in any IA in =
the message from the client', and send back a new address for the IA =
requested by the client per its (configuration) policy.

=20

=20

Best Regards,

Leaf

=20

=20


------=_NextPart_000_0153_01CF79FE.F57BD060
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-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.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E7=BA=AF=E6=96=87=E6=9C=AC;
	font-family:"Calibri","sans-serif";}
span.Char0
	{mso-style-name:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle27
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:501892812;
	mso-list-type:hybrid;
	mso-list-template-ids:-427785784 2121954892 67698691 67698693 67698689 =
67698691 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:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>BV&gt;</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'> Because the client has =
moved=E2=80=A6<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>I guess Reply to Request is not =
assumed the client has moved.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Best =
Regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Leaf<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bernie =
Volz (volz) [mailto:volz@cisco.com] <br><b>Sent:</b> Tuesday, May 27, =
2014 7:16 PM<br><b>To:</b> Leaf Yeh; 'Marcin Siodelski'<br><b>Cc:</b> =
dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'<br><b>Subject:</b> RE: =
Reply to Request in RFC3315<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;My question is why the server can't ignore 'the =
addresses in any IA in the message from the client', and send back a new =
address for the IA requested by the client per its (configuration) =
policy.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>Because the client has moved =
and so we want it to start over =E2=80=93 it may be that lots of other =
items have changed as well (perhaps even a =E2=80=9Cbetter=E2=80=9D =
server is available).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><span =
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>Bernie<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><div=
><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Leaf Yeh =
[<a =
href=3D"mailto:leaf.yeh.sdo@gmail.com">mailto:leaf.yeh.sdo@gmail.com</a>]=
 <br><b>Sent:</b> Tuesday, May 27, 2014 4:55 AM<br><b>To:</b> Bernie =
Volz (volz); 'Marcin Siodelski'<br><b>Cc:</b> <a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; 'dhcpv6bis'; 'Tomasz =
Mrugalski'<br><b>Subject:</b> Reply to Request in =
RFC3315<o:p></o:p></span></p></div></div><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>BV&gt; In Request case it is within the IA and means that =
the client's requested addresses (or PD) is not on the link...The =
Request case is a bit weird in one respect as 18.1.8 =
says:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; When the client receives a NotOnLink status =
from the server in<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; response to a Request, the client can either =
re-issue the Request<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; without specifying any addresses or restart =
the DHCP server discovery<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; process (see =
section 17).<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>This kind of implies that it is &quot;global&quot;. I think =
this case was to handle the client moving between Solicit and Request =
(but with the same server still responding since the Server DUID =
matches).<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>The above quoted paragraph is associated with one paragraph =
in section 18.2.1, <o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;If the server finds that the prefix on =
one or more IP addresses in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; any IA in the =
message from the client is not appropriate for the =
link<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; to which the client is connected, the server =
<span style=3D'color:red'>MUST return the IA =
to<o:p></o:p></span></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:red'>&nbsp;&nbsp; the client with a Status =
Code option with the value NotOnLink</span><span =
lang=3DEN-US>.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>My question is why the server can't ignore 'the addresses =
in any IA in the message from the client', and send back a new address =
for the IA requested by the client per its (configuration) =
policy.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Best Regards,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Leaf<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0153_01CF79FE.F57BD060--


From nobody Tue May 27 08:05:11 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 629541A0452; Tue, 27 May 2014 08:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dSvz4z45Zdlt; Tue, 27 May 2014 08:05:05 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A17111A013B; Tue, 27 May 2014 08:05:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19673; q=dns/txt; s=iport; t=1401203101; x=1402412701; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=MBpxhr6b0wa2/Zi/jmyrZkEU31Gju/3NfPcrPr+oExg=; b=m3wSGpz32eMrLau6slLgKlsY1rylkF7Y84eF7CO5HZB8vzYhEW4g9xWi yq08KC2IRJxzDWy2Gufi3ah9HDHCEcfomeiOOQj0AAyJ/czluvaZZMjeZ lCtOSknG+c3YoRjNOgZGLwNOcEaL9KW9xBiiq38is/FF38MGxy+YlT/G6 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFADuohFOtJA2H/2dsb2JhbABZgkJFUljCGgGBDhZ0giUBAQEELUwQAgEIEQMBAQEhBwchERQJCAIEAQ0FiC4DEc8hDYVHF4kzghB5ggURBgEGhDoEl32Bdo01hXKDOGyBQw
X-IronPort-AV: E=Sophos; i="4.98,919,1392163200"; d="scan'208,217"; a="47592794"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-8.cisco.com with ESMTP; 27 May 2014 15:04:55 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s4RF4tdh016175 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 May 2014 15:04:55 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.136]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Tue, 27 May 2014 10:04:55 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>, "'Marcin Siodelski'" <msiodelski@gmail.com>
Thread-Topic: Reply to Request in RFC3315
Thread-Index: AQHPeYlVgi+RrpQNj0CHqAOH+KEJm5tURn3QgAAx1dCAAB9egA==
Date: Tue, 27 May 2014 15:04:54 +0000
Message-ID: <CFAA217A.1DBB6%volz@cisco.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049CB0@xmb-rcd-x04.cisco.com> <538452dd.c5a7440a.37fc.ffffa93f@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E1B04C349@xmb-rcd-x04.cisco.com> <5384a7bd.671a450a.7fd5.ffffddd4@mx.google.com>
In-Reply-To: <5384a7bd.671a450a.7fd5.ffffddd4@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [161.44.70.110]
Content-Type: multipart/alternative; boundary="_000_CFAA217A1DBB6volzciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/HwvFbfBvC-Zfz6EFZ-BXGO4ax1Q
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] Reply to Request in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 15:05:10 -0000

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

Request case allows for client to do either (re-issues Request or start ove=
r):


   When the client receives a NotOnLink status from the server in

   response to a Request, the client can either re-issue the Request

   without specifying any addresses or restart the DHCP server discovery

   process (see section 17).

For Confirm, as client is using the leases it is best it start over.

- Bernie

From: Leaf Yeh <leaf.yeh.sdo@gmail.com<mailto:leaf.yeh.sdo@gmail.com>>
Date: Tuesday, May 27, 2014 at 10:56 AM
To: Cisco Employee <volz@cisco.com<mailto:volz@cisco.com>>, Marcin Siodelsk=
i <msiodelski@gmail.com<mailto:msiodelski@gmail.com>>
Cc: "dhcwg@ietf.org<mailto:dhcwg@ietf.org>" <dhcwg@ietf.org<mailto:dhcwg@ie=
tf.org>>, "dhcpv6bis@ietf.org<mailto:dhcpv6bis@ietf.org>" <dhcpv6bis@ietf.o=
rg<mailto:dhcpv6bis@ietf.org>>, Tomek Mrugalski <tomasz.mrugalski@gmail.com=
<mailto:tomasz.mrugalski@gmail.com>>
Subject: RE: Reply to Request in RFC3315

BV> Because the client has moved=85

I guess Reply to Request is not assumed the client has moved.


Best Regards,
Leaf



From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Tuesday, May 27, 2014 7:16 PM
To: Leaf Yeh; 'Marcin Siodelski'
Cc: dhcwg@ietf.org<mailto:dhcwg@ietf.org>; 'dhcpv6bis'; 'Tomasz Mrugalski'
Subject: RE: Reply to Request in RFC3315


>My question is why the server can't ignore 'the addresses in any IA in the=
 message from the client', and send back a new address for the IA requested=
 by the client per its (configuration) policy.

Because the client has moved and so we want it to start over =96 it may be =
that lots of other items have changed as well (perhaps even a =93better=94 =
server is available).


-          Bernie

From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com]
Sent: Tuesday, May 27, 2014 4:55 AM
To: Bernie Volz (volz); 'Marcin Siodelski'
Cc: dhcwg@ietf.org<mailto:dhcwg@ietf.org>; 'dhcpv6bis'; 'Tomasz Mrugalski'
Subject: Reply to Request in RFC3315


BV> In Request case it is within the IA and means that the client's request=
ed addresses (or PD) is not on the link...The Request case is a bit weird i=
n one respect as 18.1.8 says:

   When the client receives a NotOnLink status from the server in

   response to a Request, the client can either re-issue the Request

   without specifying any addresses or restart the DHCP server discovery

   process (see section 17).

This kind of implies that it is "global". I think this case was to handle t=
he client moving between Solicit and Request (but with the same server stil=
l responding since the Server DUID matches).



The above quoted paragraph is associated with one paragraph in section 18.2=
.1,

   If the server finds that the prefix on one or more IP addresses in

   any IA in the message from the client is not appropriate for the link

   to which the client is connected, the server MUST return the IA to

   the client with a Status Code option with the value NotOnLink.



My question is why the server can't ignore 'the addresses in any IA in the =
message from the client', and send back a new address for the IA requested =
by the client per its (configuration) policy.





Best Regards,

Leaf





--_000_CFAA217A1DBB6volzciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <4918CFF4D2FD234CB38CC06EC74D6A73@emea.cisco.com>
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-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Request case allows for client to do either (re-issues Request or star=
t over):</div>
<div><br>
</div>
<div>
<p class=3D"MsoPlainText" style=3D"font-size: medium; font-family: Calibri,=
 sans-serif;">
<span lang=3D"EN-US">&nbsp; &nbsp;When the client receives a NotOnLink stat=
us from the server in<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"font-size: medium; font-family: Calibri,=
 sans-serif;">
<span lang=3D"EN-US">&nbsp;&nbsp; response to a Request, the client can eit=
her re-issue the Request<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"font-size: medium; font-family: Calibri,=
 sans-serif;">
<span lang=3D"EN-US">&nbsp;&nbsp; without specifying any addresses or resta=
rt the DHCP server discovery<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"font-size: medium; font-family: Calibri,=
 sans-serif;">
<span lang=3D"EN-US">&nbsp;&nbsp; process (see section 17).</span></p>
</div>
<div><br>
</div>
<div>For Confirm, as client is using the leases it is best it start over.</=
div>
<div><br>
</div>
<div>- Bernie</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Leaf Yeh &lt;<a href=3D"mailt=
o:leaf.yeh.sdo@gmail.com">leaf.yeh.sdo@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, May 27, 2014 at 10:5=
6 AM<br>
<span style=3D"font-weight:bold">To: </span>Cisco Employee &lt;<a href=3D"m=
ailto:volz@cisco.com">volz@cisco.com</a>&gt;, Marcin Siodelski &lt;<a href=
=3D"mailto:msiodelski@gmail.com">msiodelski@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </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;, &quot;<a href=3D"mailto:dhcpv6bis@ietf.org">dhcpv6bis@=
ietf.org</a>&quot; &lt;<a href=3D"mailto:dhcpv6bis@ietf.org">dhcpv6bis@ietf=
.org</a>&gt;,
 Tomek Mrugalski &lt;<a href=3D"mailto:tomasz.mrugalski@gmail.com">tomasz.m=
rugalski@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: Reply to Request in RF=
C3315<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:??;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@??";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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:"??? Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"????? Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"??? Char";
	mso-style-priority:99;
	mso-style-link:???;
	font-family:"Calibri","sans-serif";}
span.Char0
	{mso-style-name:"????? Char";
	mso-style-priority:99;
	mso-style-link:?????;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle27
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:501892812;
	mso-list-type:hybrid;
	mso-list-template-ids:-427785784 2121954892 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:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-tr=
im:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">BV&gt;<=
/span><span lang=3D"EN-US" style=3D"font-size:11.0pt;color:#1F497D"> Becaus=
e the client has moved=85<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D">I guess Reply to Request is not assumed the client has moved.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Best Re=
gards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Leaf<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><b><span la=
ng=3D"EN-US" style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;">Fr=
om:</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: T=
ahoma, sans-serif;"> Bernie Volz (volz) [<a href=3D"mailto:volz@cisco.com">=
mailto:volz@cisco.com</a>]
<br>
<b>Sent:</b> Tuesday, May 27, 2014 7:16 PM<br>
<b>To:</b> Leaf Yeh; 'Marcin Siodelski'<br>
<b>Cc:</b> <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; 'dhcpv6bis=
'; 'Tomasz Mrugalski'<br>
<b>Subject:</b> RE: Reply to Request in RFC3315<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt;My question is why the s=
erver can't ignore 'the addresses in any IA in the message from the client'=
, and send back a new address for the IA requested by the client per its (c=
onfiguration) policy.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D">Because the client has moved and so we want it to start over =96 =
it may be that lots of other items have changed as well (perhaps even a =93=
better=94 server is available).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo2"><!--[if !supportLists]--><span lang=3D"EN-US" style=3D"font-size:1=
1.0pt;color:#1F497D"><span style=3D"mso-list:Ignore">-<span style=3D"font-s=
tyle: normal; font-variant: normal; font-weight: normal; font-size: 7pt; li=
ne-height: normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><!--[endif]--><span lang=3D"EN-US" style=3D"font-size:=
11.0pt;color:#1F497D">Bernie<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><b><span la=
ng=3D"EN-US" style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;">Fr=
om:</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: T=
ahoma, sans-serif;"> Leaf Yeh [<a href=3D"mailto:leaf.yeh.sdo@gmail.com">ma=
ilto:leaf.yeh.sdo@gmail.com</a>]
<br>
<b>Sent:</b> Tuesday, May 27, 2014 4:55 AM<br>
<b>To:</b> Bernie Volz (volz); 'Marcin Siodelski'<br>
<b>Cc:</b> <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; 'dhcpv6bis=
'; 'Tomasz Mrugalski'<br>
<b>Subject:</b> Reply to Request in RFC3315<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">BV&gt; In Request case it is=
 within the IA and means that the client's requested addresses (or PD) is n=
ot on the link...The Request case is a bit weird in one respect as 18.1.8 s=
ays:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; When the client=
 receives a NotOnLink status from the server in<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; response to a R=
equest, the client can either re-issue the Request<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; without specify=
ing any addresses or restart the DHCP server discovery<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; process (see se=
ction 17).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">This kind of implies that it=
 is &quot;global&quot;. I think this case was to handle the client moving b=
etween Solicit and Request (but with the same server still responding since=
 the Server DUID matches).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">The above quoted paragraph i=
s associated with one paragraph in section 18.2.1,
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;If the ser=
ver finds that the prefix on one or more IP addresses in<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; any IA in the m=
essage from the client is not appropriate for the link<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; to which the cl=
ient is connected, the server
<span style=3D"color:red">MUST return the IA to<o:p></o:p></span></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:red">&nbsp;&n=
bsp; the client with a Status Code option with the value NotOnLink</span><s=
pan lang=3D"EN-US">.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">My question is why the serve=
r can't ignore 'the addresses in any IA in the message from the client', an=
d send back a new address for the IA requested by the client per its (confi=
guration) policy.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Best Regards,<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Leaf<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_CFAA217A1DBB6volzciscocom_--


From nobody Tue May 27 08:10:39 2014
Return-Path: <leaf.yeh.sdo@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 D75821A0157; Tue, 27 May 2014 08:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MdLYe0jX87h7; Tue, 27 May 2014 08:10:32 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B19E1A013B; Tue, 27 May 2014 08:10:31 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id lf10so9312002pab.20 for <multiple recipients>; Tue, 27 May 2014 08:10:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:thread-index:content-language; bh=SjJpFKlIi3Ls52yxstFrjQTGKRHStoVBmezii8UZJQU=; b=k6cmFlGiYBe+BLiQ7T8y9DIBsyqJGFbzNbkJkBf8EzDntHVCxYNzhsa9uJW0yFEPc2 Xmsuduy6+yjYCWLG2xFO17xxOcKmja/Kl6BEZczTeUuIA7+0LenO/hpsziij19FeTB9P Djp9mBBjVuYgFnwhjqyWcnfJrALDkDPjSMN1/2eAvKhjUD/hj6ulLh+oI+yuvXb1AmkU 2oB9uIBMmnU9pfaphTLKECARtNfhVhbsx59e/Dxtg4RHJXGUjK3n5x53HvRCEmx3kk81 cr/HOWNzxyMzk8rko/LqHTcrfKALh6kY/QolbHGOWnb3LA1FJZTzUaGwwUHD6EXFeCUS tunA==
X-Received: by 10.66.182.69 with SMTP id ec5mr36794666pac.125.1401203428478; Tue, 27 May 2014 08:10:28 -0700 (PDT)
Received: from PC ([111.199.99.113]) by mx.google.com with ESMTPSA id sv10sm23780878pbc.74.2014.05.27.08.10.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 27 May 2014 08:10:27 -0700 (PDT)
Message-ID: <5384aae3.2ae6440a.7b97.ffffdf4e@mx.google.com>
X-Google-Original-Message-ID: <016601cf79bd$c6765f60$53631e20$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <538425b3.08e6440a.08fb.7da2@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E1B04C315@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B04C315@xmb-rcd-x04.cisco.com>
Date: Tue, 27 May 2014 23:10:12 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0167_01CF7A00.D4999F60"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac94ja1zHl9NfJkXSMiqk9XERg5MCwAd2kKAACXQ9zAAB6h/wA==
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/AQMoB-KASSGH65p6rSBuZ8Y1LGA
Cc: dhcwg@ietf.org, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] More Discussion - RE: [Dhcpv6bis] Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 15:10:35 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0167_01CF7A00.D4999F60
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

BV> Confirm is supposed to be quick and easy for servers (no database =
looks =E2=80=A6 about a specific lease) =E2=80=93 just to verify that =
addresses are on link (which is any easy test to locate the prefix =
containing the addresses).

=20

Even though Confirm in RFC3315 sounds only verify the addresses in IAs =
and assume the client knows the correct lease for each address, it still =
looks much clearer that the server does verify each IA, and could send =
back the Status Code for each IA.

=20

I do personally like Confirm could works as Renew. J

=20

=20

Best Regards,

Leaf

=20

=20

=20

From: Bernie Volz (volz) [mailto:volz@cisco.com]=20
Sent: Tuesday, May 27, 2014 7:14 PM
To: Leaf Yeh
Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'; 'Marcin Siodelski'
Subject: RE: More Discussion - RE: [Dhcpv6bis] Reply to Confirm in =
RFC3315

=20

What is the point of all this?

=20

Confirm does not confirm any leases or lease times. It just confirms =
that the addresses are ON LINK.

=20

Confirm is supposed to be quick and easy for servers (no database looks =
or writes about a specific lease) =E2=80=93 just to verify that =
addresses are on link (which is any easy test to locate the prefix =
containing the addresses). It is NOT a Renew.

=20

-          Bernie

=20

From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com]=20
Sent: Tuesday, May 27, 2014 1:42 AM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'; 'Marcin Siodelski'
Subject: More Discussion - RE: [Dhcpv6bis] Reply to Confirm in RFC3315

=20

When I read the text on 'Reply to Confirm' in RFC3315, the following =
statements sounds me a little misunderstanding:

=20

<quote> @ 18.1.2 - Creation and Transmission of Confirm Messages

   The client MUST include a Client Identifier option to identify itself

   to the server.  The client includes IA options for all of the IAs

   assigned to the interface for which the Confirm message is being

   sent.  The IA options include all of the addresses the client

   currently has associated with those IAs.  The client SHOULD set the

   T1 and T2 fields in any IA_NA options, and the preferred-lifetime and

   valid-lifetime fields in the IA Address options to 0, as the server

   will ignore these fields.

</quote>

=20

It sounds the client ask the server to confirm the address (& IA) for =
his interface, but why not ask the server to confirm the values of lease =
timers (T1/T2 for IA, preferred/valid-LT for address) he has.

=20

=20

<quote> @ 18.2.2 -Receipt of Confirm Messages

   The server ignores the T1 and T2 fields in the IA options and the

   preferred-lifetime and valid-lifetime fields in the IA Address

   options.

   ...

   The server MUST include a Server Identifier option containing the

   server's DUID and the Client Identifier option from the Confirm

   message in the Reply message.  The server includes a Status Code

   option indicating the status of the Confirm message.

</quote>

=20

=20

Certainly, the server confirmed the address (& the associated IAID) of =
client based on its this own database. If the server returned the global =
=E2=80=98Success=E2=80=99 in the Status Code option, it sounds all the =
information the client provided in Confirm has been confirmed, and =
assumed the client has the same lease as that recoded in the database of =
server.

=20

But I think it sounds much better the server could confirm (or update) =
all the information about the lease (including address and the value of =
timers) for the client in the Reply message. It looks much clearer, and =
cost little in the Reply.

=20

The global Status Code looks unspecified to each address (and its =
lease), which in fact needs to be confirmed.

=20

=20

Best Regards,

Leaf

=20

=20

=20

-----Original Message-----
From: Marcin Siodelski [mailto:msiodelski@gmail.com]=20
Sent: Monday, May 26, 2014 7:56 PM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org; 'dhcpv6bis'; Leaf Yeh; 'Tomasz Mrugalski'
Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315

=20

Yes, NoAddrsAvail/NoBinding are not sent in response to Confirm. May =
point rather was that *even in a more general case* the server will not =
send addresses in the IA in which there is NoAddrsAvail or NoBinding.=20

This comment was beyond the context of Confirm/Reply message exchange.

=20

Marcin

=20

On Mon 26 May 2014 13:41:30 CEST, Bernie Volz (volz) wrote:

> I think we're talking about Reply to Confirm. If so, why would these =
contain NoAddrsAvail/NoBinding? They don't. Confirm does not validate a =
particular client's addresses/PDs or bindings. It only validates whether =
the addresses/PDs are on link or not.

>=20

> Other than global errors like UnspecFail, a Confirm will either =
contain NotOnLink or Success. Nothing else.

>=20

> And, yes the idea was there could be multiple servers some of which =
may send NotOnLink (as they may be lacking the configuration) but others =
that send Success. The Success on can be taken.

>=20

> In general servers that aren't authoritative for a particular set of =
links should not respond.

>=20

> - Bernie

>=20

> -----Original Message-----

> From: Marcin Siodelski [ <mailto:msiodelski@gmail.com> =
mailto:msiodelski@gmail.com]

> Sent: Monday, May 26, 2014 6:54 AM

> To: Leaf Yeh; Bernie Volz (volz); 'Tomasz Mrugalski'

> Cc:  <mailto:dhcwg@ietf.org> dhcwg@ietf.org; 'dhcpv6bis'

> Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315

>=20

>=20

>=20

> On 26/05/14 04:53, Leaf Yeh wrote:

>> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply=20

>> Messages' of RFC3315:

>>=20

>>=20

>>=20

>> <quote>

>>=20

>> When the client receives a NotOnLink status from the server in

>>=20

>>    response to a Confirm message, the client performs DHCP server

>>=20

>>    solicitation, as described in section 17=20

>> < <http://tools.ietf.org/html/rfc3315#section-17> =
http://tools.ietf.org/html/rfc3315#section-17>, and client-initiated

>>=20

>>    configuration as described in section 18=20

>> < <http://tools.ietf.org/html/rfc3315#section-18> =
http://tools.ietf.org/html/rfc3315#section-18>.  If the client=20

>> receives any

>>=20

>>    Reply messages that do not indicate a NotOnLink status, the client

>>=20

>>    can usethe addresses in the IA andignore any messages that=20

>> indicate

>>=20

>>    a NotOnLink status.

>>=20

>> </quote>

>>=20

>>=20

>>=20

>> 1.       If the client receive an Reply message indicating =
'NoBinding'

>> (or even ' NoAddrsAvail'), the above sounds the client can still use=20

>> the address in the IA. Why?

>=20

> I think the context of the paragraph is important. The client sends =
Confirm to any available server and client may receive multiple Replies.

> Typically, one of these Replies will not contain NotOnLink status (or =
contain Success) to indicate that client can use the address. Other =
servers will send NotOnLink because they are not configured for the =
particular subnet or so. So, the purpose of this paragraph is just to =
describe this scenario.

>=20

> Of course, client may receive Replies with other status codes too, and =
there are relevant sections that talk about client behavior in this =
case". So a couple of lines down:

>=20

> "

>    The client examines the status code in each IA individually.  If =
the

>    status code is NoAddrsAvail, the client has received no usable

>    addresses in the IA and may choose to try obtaining addresses for =
the

>    IA from another server.  The client uses addresses and other

>    information from any IAs that do not contain a Status Code option

>    with the NoAddrsAvail code.  If the client receives no addresses in

>    any of the IAs, it may either try another server (perhaps =
restarting

>    the DHCP server discovery process) or use the Information-request

>    message to obtain other configuration information only.

> "

>=20

> So, I don't really think there is any conflict here.

>=20

> Also, you indicate that the client could use the address even though =
there is a NoAddrsAvail or NoBinding. But, the returned IA will not have =
an address to be used, because server places just status code NoBinding =
or NoAddrsAvail in the IA and nothing else.

>=20

>=20

>=20

>>=20

>> 2.       Why does the client could ignore 'any message' indicating

>> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds=20

>> conflict with the 1^st half of the above paragraph, not?

>>=20

>>=20

>=20

> The way I read it is that when the client receives at least one Reply =
that has no NotOnLink status code, it may use the address it desires to =
use. Otherwise it performs solicitation.

>=20

> Perhaps, it could be more precise and say something along the lines: =
if none of the Reply messages received in response to a Confirm message =
indicates success, the client performs solicitation. Otherwise, it may =
use the address.

>=20

> Marcin


------=_NextPart_000_0167_01CF7A00.D4999F60
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-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.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E7=BA=AF=E6=96=87=E6=9C=AC;
	font-family:"Calibri","sans-serif";}
span.Char0
	{mso-style-name:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle27
	{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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1661150746;
	mso-list-type:hybrid;
	mso-list-template-ids:-1833281412 -1095319510 67698691 67698693 =
67698689 67698691 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:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>BV&gt; Confirm is supposed to =
be quick and easy for servers (no database looks =E2=80=A6 about a =
specific lease) =E2=80=93 just to verify that addresses are on link =
(which is any easy test to locate the prefix containing the =
addresses).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>Even though Confirm in RFC3315 =
sounds only verify the addresses in IAs and assume the client knows the =
correct lease for each address, it still looks much clearer that the =
server does verify each IA, and could send back the Status Code for each =
IA.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>I do personally like Confirm =
could works as Renew. </span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><s=
pan lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>Best =
Regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>Leaf<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bernie =
Volz (volz) [mailto:volz@cisco.com] <br><b>Sent:</b> Tuesday, May 27, =
2014 7:14 PM<br><b>To:</b> Leaf Yeh<br><b>Cc:</b> dhcwg@ietf.org; =
'dhcpv6bis'; 'Tomasz Mrugalski'; 'Marcin Siodelski'<br><b>Subject:</b> =
RE: More Discussion - RE: [Dhcpv6bis] Reply to Confirm in =
RFC3315<o:p></o:p></span></p></div></div><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>What is the point =
of all this?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>Confirm does not confirm any =
leases or lease times. It just confirms that the addresses are ON =
LINK.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>Confirm is supposed to be quick =
and easy for servers (no database looks or writes about a specific =
lease) =E2=80=93 just to verify that addresses are on link (which is any =
easy test to locate the prefix containing the addresses). It is NOT a =
Renew.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><span =
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>Bernie<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><div=
><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Leaf Yeh =
[<a =
href=3D"mailto:leaf.yeh.sdo@gmail.com">mailto:leaf.yeh.sdo@gmail.com</a>]=
 <br><b>Sent:</b> Tuesday, May 27, 2014 1:42 AM<br><b>To:</b> Bernie =
Volz (volz)<br><b>Cc:</b> <a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; 'dhcpv6bis'; 'Tomasz =
Mrugalski'; 'Marcin Siodelski'<br><b>Subject:</b> More Discussion - RE: =
[Dhcpv6bis] Reply to Confirm in =
RFC3315<o:p></o:p></span></p></div></div><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>When I read the text on 'Reply to Confirm' in RFC3315, the =
following statements sounds me a little =
misunderstanding:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&lt;quote&gt; @ 18.1.2 - Creation and Transmission of =
Confirm Messages<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; The client MUST include a Client Identifier =
option to identify itself<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; to the =
server.&nbsp; The client includes IA options for <span =
style=3D'color:red'>all of the IAs<o:p></o:p></span></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:red'>&nbsp;&nbsp; =
assigned to the interface</span><span lang=3DEN-US> for which the =
Confirm message is being<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; sent.&nbsp; The IA =
options include all of the addresses the client<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; currently has =
associated with those IAs.&nbsp; The client SHOULD set =
the<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; <span style=3D'color:red'>T1 and T2 fields in =
any IA_NA options, and the preferred-lifetime =
and<o:p></o:p></span></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:red'>&nbsp;&nbsp; valid-lifetime fields in =
the IA Address options to 0</span><span lang=3DEN-US>, as the =
server<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; will ignore these =
fields.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&lt;/quote&gt;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>It sounds the client ask the =
server to confirm the address (&amp; IA) for his interface, but <b>why =
not</b> ask the server to confirm the values of lease timers (T1/T2 for =
IA, preferred/valid-LT for address) he has.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&lt;quote&gt; @ 18.2.2 -Receipt =
of Confirm Messages<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; The server <span =
style=3D'color:red'>ignores</span> the T1 and T2 fields in the IA =
options and the<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; preferred-lifetime and valid-lifetime fields =
in the IA Address<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; options.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; =
...<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; The server MUST include a Server Identifier =
option containing the<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; server's DUID and the Client Identifier option =
from the Confirm<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; message in the Reply message.&nbsp; <span =
style=3D'color:red'>The server includes a Status =
Code<o:p></o:p></span></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:red'>&nbsp;&nbsp; option indicating the =
status of the Confirm message.</span><span =
lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&lt;/quote&gt;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Certainly, the server confirmed =
the address (&amp; the associated IAID) of client based on its this own =
database. If the server returned the global </span><span lang=3DEN-US =
style=3D'font-family:"Courier New"'>=E2=80=98</span><span =
lang=3DEN-US>Success</span><span lang=3DEN-US =
style=3D'font-family:"Courier New"'>=E2=80=99</span><span lang=3DEN-US> =
in the Status Code option, it sounds all the information the client =
provided in Confirm has been confirmed, and <b>assumed the client has =
the same lease as that recoded in the database of =
server.</b><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>But I think it sounds much better the server could confirm =
(or update) all the information about the lease (including address and =
the value of timers) for the client in the Reply message. It looks much =
clearer, and cost little in the Reply.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>The global Status Code looks =
unspecified to each address (and its lease), which in fact needs to be =
confirmed.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Best Regards,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Leaf<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>-----Original =
Message-----<br>From: Marcin Siodelski [<a =
href=3D"mailto:msiodelski@gmail.com">mailto:msiodelski@gmail.com</a>] =
<br>Sent: Monday, May 26, 2014 7:56 PM<br>To: Bernie Volz (volz)<br>Cc: =
<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; 'dhcpv6bis'; Leaf =
Yeh; 'Tomasz Mrugalski'<br>Subject: Re: [Dhcpv6bis] Reply to Confirm in =
RFC3315<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Yes, NoAddrsAvail/NoBinding are not sent in response to =
Confirm. May point rather was that *even in a more general case* the =
server will not send addresses in the IA in which there is NoAddrsAvail =
or NoBinding. <o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>This comment was beyond the context of Confirm/Reply =
message exchange.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Marcin<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>On Mon 26 May 2014 13:41:30 CEST, Bernie Volz (volz) =
wrote:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; I think we're talking about Reply to Confirm. If so, =
why would these contain NoAddrsAvail/NoBinding? They don't. Confirm does =
not validate a particular client's addresses/PDs or bindings. It only =
validates whether the addresses/PDs are on link or =
not.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Other than global errors =
like UnspecFail, a Confirm will either contain NotOnLink or Success. =
Nothing else.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; And, yes the idea was there =
could be multiple servers some of which may send NotOnLink (as they may =
be lacking the configuration) but others that send Success. The Success =
on can be taken.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; In general servers that =
aren't authoritative for a particular set of links should not =
respond.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; - =
Bernie<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; -----Original =
Message-----<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; From: Marcin Siodelski [<a =
href=3D"mailto:msiodelski@gmail.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:msiodelski@gmail.c=
om</span></a>]<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; Sent: Monday, May 26, 2014 6:54 =
AM<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>&gt; =
To: Leaf Yeh; Bernie Volz (volz); 'Tomasz =
Mrugalski'<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; Cc: <a href=3D"mailto:dhcwg@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>dhcwg@ietf.org</span></a>=
; 'dhcpv6bis'<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt; Subject: Re: [Dhcpv6bis] Reply to Confirm in =
RFC3315<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; On 26/05/14 04:53, Leaf Yeh =
wrote:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; Got 2 questions on the text in Section =
18.1.8-'Receipt of Reply <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; Messages' of =
RFC3315:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
&lt;quote&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; When the client =
receives a NotOnLink status from the server in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;&nbsp;&nbsp;&nbsp; =
response to a Confirm message, the client performs DHCP =
server<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;&nbsp;&nbsp;&nbsp; =
solicitation, as described in section 17 <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; &lt;<a =
href=3D"http://tools.ietf.org/html/rfc3315#section-17"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/rfc3315#section-17</span></a>&gt;, and =
client-initiated<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;&nbsp;&nbsp;&nbsp; =
configuration as described in section 18 <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; &lt;<a =
href=3D"http://tools.ietf.org/html/rfc3315#section-18"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/rfc3315#section-18</span></a>&gt;.&nbsp; If the client =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; receives any<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;&nbsp;&nbsp;&nbsp; Reply =
messages that do not indicate a NotOnLink status, the =
client<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;&nbsp;&nbsp;&nbsp; can =
usethe addresses in the IA andignore any messages that =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; indicate<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt;&nbsp;&nbsp;&nbsp; a =
NotOnLink status.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
&lt;/quote&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If the client receive an Reply =
message indicating 'NoBinding'<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; (or even ' =
NoAddrsAvail'), the above sounds the client can still use =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt; the address in the IA. =
Why?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; I think the context of the =
paragraph is important. The client sends Confirm to any available server =
and client may receive multiple Replies.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Typically, one of these =
Replies will not contain NotOnLink status (or contain Success) to =
indicate that client can use the address. Other servers will send =
NotOnLink because they are not configured for the particular subnet or =
so. So, the purpose of this paragraph is just to describe this =
scenario.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Of course, client may =
receive Replies with other status codes too, and there are relevant =
sections that talk about client behavior in this case&quot;. So a couple =
of lines down:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; =
&quot;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&nbsp;&nbsp;&nbsp; The client examines the status code =
in each IA individually.&nbsp; If the<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&nbsp;&nbsp;&nbsp; status =
code is NoAddrsAvail, the client has received no =
usable<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&nbsp;&nbsp;&nbsp; addresses in the IA and may choose =
to try obtaining addresses for the<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&nbsp;&nbsp;&nbsp; IA from =
another server.&nbsp; The client uses addresses and =
other<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&nbsp;&nbsp;&nbsp; information from any IAs that do not =
contain a Status Code option<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&nbsp;&nbsp;&nbsp; with the =
NoAddrsAvail code.&nbsp; If the client receives no addresses =
in<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&nbsp;&nbsp;&nbsp; any of the IAs, it may either try =
another server (perhaps restarting<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&nbsp;&nbsp;&nbsp; the DHCP =
server discovery process) or use the =
Information-request<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&nbsp;&nbsp;&nbsp; message to obtain other =
configuration information only.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; =
&quot;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; So, I don't really think =
there is any conflict here.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Also, you indicate that the =
client could use the address even though there is a NoAddrsAvail or =
NoBinding. But, the returned IA will not have an address to be used, =
because server places just status code NoBinding or NoAddrsAvail in the =
IA and nothing else.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; =
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Why does the client could ignore =
'any message' indicating<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; 'NotOnLink' (in the =
2^nd half of the above paragraph)? It sounds <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt;&gt; conflict with the 1^st =
half of the above paragraph, not?<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; The way I read it is that =
when the client receives at least one Reply that has no NotOnLink status =
code, it may use the address it desires to use. Otherwise it performs =
solicitation.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; Perhaps, it could be more =
precise and say something along the lines: if none of the Reply messages =
received in response to a Confirm message indicates success, the client =
performs solicitation. Otherwise, it may use the =
address.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&gt; =
Marcin<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0167_01CF7A00.D4999F60--



From nobody Tue May 27 08:11:35 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 AFB021A0171; Tue, 27 May 2014 08:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 GCuevBJ81cGZ; Tue, 27 May 2014 08:11:31 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D32181A0157; Tue, 27 May 2014 08:11:31 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B35241B81C6; Tue, 27 May 2014 08:11:28 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 8AF5619005C; Tue, 27 May 2014 08:11:28 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 27 May 2014 08:11:28 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5384aae3.2ae6440a.7b97.ffffdf4e@mx.google.com>
Date: Tue, 27 May 2014 11:11:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <20C83C0A-B602-41DF-A3E9-00748CC92E07@nominum.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <538425b3.08e6440a.08fb.7da2@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E1B04C315@xmb-rcd-x04.cisco.com> <5384aae3.2ae6440a.7b97.ffffdf4e@mx.google.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/axMrTfgq4FilpGUpmMd6yKMWMcA
Cc: dhcwg@ietf.org, Bernie Volz <volz@cisco.com>, dhcpv6bis <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] More Discussion - RE: Reply to Confirm in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 15:11:34 -0000

On May 27, 2014, at 11:10 AM, Leaf Yeh <leaf.yeh.sdo@gmail.com> wrote:
> I do personally like Confirm could works as Renew. J

We are not changing the protocol.   Also, what you are proposing makes =
Confirm more expensive.



From nobody Tue May 27 08:26:41 2014
Return-Path: <leaf.yeh.sdo@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 4462A1A042D; Tue, 27 May 2014 08:26:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4OSAXljROte5; Tue, 27 May 2014 08:26:33 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45BA21A0428; Tue, 27 May 2014 08:26:04 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kq14so9388882pab.10 for <multiple recipients>; Tue, 27 May 2014 08:26:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:thread-index:content-language; bh=KLSH4nk/TeV4spi5Ww4BqhJukLI+CsAaCuQ1sluxgQY=; b=K8qNWyA5o8u/nWM2bEZp9OIZqoW4F0jkTDd0CcB93wBbG+oTwkMj5E1v4qzlFXa1rb hNJZAIqyhEp/Ia5OpF8Y4KK0KU5CZPvNS7acM+RPAfNpVwOUL+JhbhSMyOqkCUA564E5 ohbK+yIilNJUmO8TDwhtiga6Fh7xrxwe3oCHWMsu87RduNjyUtbFWQGyZjL0YsdAyv6b 4zDJLNx20Ihp6EZLUEof12RSeJi+L+7GPj+ZIYvZD0BumtSC+ovRQ8KZ5xTPG2hkz2kz OyqTnfPNm3LjgceRrAKJgEtJRScjaLL+KpUrlHIW8WFwqs68EmdKSzNpIlRvB1+TEQiF QtCA==
X-Received: by 10.66.192.104 with SMTP id hf8mr20879867pac.13.1401204361114; Tue, 27 May 2014 08:26:01 -0700 (PDT)
Received: from PC ([111.199.99.113]) by mx.google.com with ESMTPSA id qb6sm74876364pac.12.2014.05.27.08.25.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 27 May 2014 08:26:00 -0700 (PDT)
Message-ID: <5384ae88.26dd420a.1f6f.ffff870b@mx.google.com>
X-Google-Original-Message-ID: <017101cf79bf$f3138190$d93a84b0$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>, "'Marcin Siodelski'" <msiodelski@gmail.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049CB0@xmb-rcd-x04.cisco.com> <538452dd.c5a7440a.37fc.ffffa93f@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E1B04C349@xmb-rcd-x04.cisco.com> <5384a7bd.671a450a.7fd5.ffffddd4@mx.google.com> <CFAA217A.1DBB6%volz@cisco.com>
In-Reply-To: <CFAA217A.1DBB6%volz@cisco.com>
Date: Tue, 27 May 2014 23:25:46 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0172_01CF7A03.0136C190"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHPeYlVgi+RrpQNj0CHqAOH+KEJm5tURn3QgAAx1dCAAB9egP//8RFA
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/BoEL_OxuBfYkhqHC-XAia_thWn4
Cc: dhcwg@ietf.org, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] Reply to Request in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 15:26:39 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0172_01CF7A03.0136C190
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

My point in the mail before my last mail was against: 

 

 If the server finds that the prefix on one or more IP addresses in

   any IA in the message from the client is not appropriate for the link

   to which the client is connected, the server MUST return the IA to

   the client with a Status Code option with the value NotOnLink.

 

in section  <http://tools.ietf.org/html/rfc3315#section-18.2.1> 18.2.1-
Receipt of Request Messages.

 

I guess the server could choose to ignore the IP addresses in any IA from
Request, and don't return back the IA-specific 'NotOnLink'.

Why not? Pls. help to exercise my brain. J

 

 

Best Regards,

Leaf

 

 

 

From: Bernie Volz (volz) [mailto:volz@cisco.com] 
Sent: Tuesday, May 27, 2014 11:05 PM
To: Leaf Yeh; 'Marcin Siodelski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'
Subject: Re: Reply to Request in RFC3315

 

Request case allows for client to do either (re-issues Request or start
over):

 

   When the client receives a NotOnLink status from the server in

   response to a Request, the client can either re-issue the Request

   without specifying any addresses or restart the DHCP server discovery

   process (see section 17).

 

For Confirm, as client is using the leases it is best it start over.

 

- Bernie

 

From: Leaf Yeh <leaf.yeh.sdo@gmail.com>
Date: Tuesday, May 27, 2014 at 10:56 AM
To: Cisco Employee <volz@cisco.com>, Marcin Siodelski <msiodelski@gmail.com>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "dhcpv6bis@ietf.org"
<dhcpv6bis@ietf.org>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Subject: RE: Reply to Request in RFC3315

 

BV> Because the client has moved.

 

I guess Reply to Request is not assumed the client has moved.

 

 

Best Regards,

Leaf

 

 

 

From: Bernie Volz (volz) [mailto:volz@cisco.com] 
Sent: Tuesday, May 27, 2014 7:16 PM
To: Leaf Yeh; 'Marcin Siodelski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'
Subject: RE: Reply to Request in RFC3315

 

>My question is why the server can't ignore 'the addresses in any IA in the
message from the client', and send back a new address for the IA requested
by the client per its (configuration) policy.

 

Because the client has moved and so we want it to start over - it may be
that lots of other items have changed as well (perhaps even a "better"
server is available).

 

-          Bernie

 

From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com] 
Sent: Tuesday, May 27, 2014 4:55 AM
To: Bernie Volz (volz); 'Marcin Siodelski'
Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'
Subject: Reply to Request in RFC3315

 

BV> In Request case it is within the IA and means that the client's
requested addresses (or PD) is not on the link...The Request case is a bit
weird in one respect as 18.1.8 says:

   When the client receives a NotOnLink status from the server in

   response to a Request, the client can either re-issue the Request

   without specifying any addresses or restart the DHCP server discovery

   process (see section 17).

This kind of implies that it is "global". I think this case was to handle
the client moving between Solicit and Request (but with the same server
still responding since the Server DUID matches).

 

The above quoted paragraph is associated with one paragraph in section
18.2.1, 

   If the server finds that the prefix on one or more IP addresses in

   any IA in the message from the client is not appropriate for the link

   to which the client is connected, the server MUST return the IA to

   the client with a Status Code option with the value NotOnLink.

 

My question is why the server can't ignore 'the addresses in any IA in the
message from the client', and send back a new address for the IA requested
by the client per its (configuration) policy.

 

 

Best Regards,

Leaf

 

 


------=_NextPart_000_0172_01CF7A03.0136C190
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-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
h4
	{mso-style-priority:9;
	mso-style-link:"\6807\9898 4 Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
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:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"\6279\6CE8\6846\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:SimSun;}
span.Char0
	{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.a, li.a, div.a
	{mso-style-name:???;
	mso-style-link:"??? Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char1
	{mso-style-name:"??? Char";
	mso-style-priority:99;
	mso-style-link:???;
	font-family:"Calibri","sans-serif";}
p.a0, li.a0, div.a0
	{mso-style-name:?????;
	mso-style-link:"????? Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char2
	{mso-style-name:"????? Char";
	mso-style-priority:99;
	mso-style-link:?????;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.4Char
	{mso-style-name:"\6807\9898 4 Char";
	mso-style-priority:9;
	mso-style-link:"\6807\9898 4";
	font-family:"Courier New";
	font-weight:bold;}
span.HTMLChar
	{mso-style-name:"HTML \9884\8BBE\683C\5F0F Char";
	mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F";
	font-family:SimSun;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:501892812;
	mso-list-type:hybrid;
	mso-list-template-ids:-427785784 2121954892 67698691 67698693 67698689 =
67698691 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:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:?;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>My point in the mail before my last mail was =
against: <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'text-indent:5.25pt'><span lang=3DEN-US =
style=3D'color:black'>&nbsp;If the server finds that the prefix on one =
or more IP addresses in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp; any IA in the message from the client =
is not appropriate for the link<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp; to which the client is connected, the =
server </span><span lang=3DEN-US style=3D'color:red'>MUST return the IA =
to</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:red'>&nbsp;&nbsp; =
the client with a Status Code option with the value =
NotOnLink</span><span lang=3DEN-US =
style=3D'color:black'>.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>in section =
<a name=3Dsection-18.2.1></a><a =
href=3D"http://tools.ietf.org/html/rfc3315#section-18.2.1"><span =
style=3D'color:#1F497D;text-decoration:none'>18.2.1</span></a>- Receipt =
of Request Messages.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>I guess the =
server could choose to ignore the IP addresses in any IA from Request, =
and don&#8217;t return back the IA-specific =
&#8216;NotOnLink&#8217;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Why not? Pls. help to exercise my =
brain. </span><span lang=3DEN-US =
style=3D'font-family:Wingdings;color:#1F497D'>J</span><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Best =
Regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Leaf<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bernie =
Volz (volz) [mailto:volz@cisco.com] <br><b>Sent:</b> Tuesday, May 27, =
2014 11:05 PM<br><b>To:</b> Leaf Yeh; 'Marcin Siodelski'<br><b>Cc:</b> =
dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'<br><b>Subject:</b> Re: =
Reply to Request in RFC3315<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>Request case allows for client to do =
either (re-issues Request or start =
over):<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:13.5pt;color:black'>&nbsp; &nbsp;When the client =
receives a NotOnLink status from the server in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:13.5pt;color:black'>&nbsp;&nbsp; response to a =
Request, the client can either re-issue the =
Request<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:13.5pt;color:black'>&nbsp;&nbsp; without specifying =
any addresses or restart the DHCP server =
discovery<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-size:13.5pt;color:black'>&nbsp;&nbsp; process =
(see section 17).<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>For Confirm, =
as client is using the leases it is best it start =
over.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>- =
Bernie<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p></div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:black'>From: </span></b><span =
lang=3DEN-US style=3D'font-size:11.0pt;color:black'>Leaf Yeh &lt;<a =
href=3D"mailto:leaf.yeh.sdo@gmail.com">leaf.yeh.sdo@gmail.com</a>&gt;<br>=
<b>Date: </b>Tuesday, May 27, 2014 at 10:56 AM<br><b>To: </b>Cisco =
Employee &lt;<a href=3D"mailto:volz@cisco.com">volz@cisco.com</a>&gt;, =
Marcin Siodelski &lt;<a =
href=3D"mailto:msiodelski@gmail.com">msiodelski@gmail.com</a>&gt;<br><b>C=
c: </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;, &quot;<a =
href=3D"mailto:dhcpv6bis@ietf.org">dhcpv6bis@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:dhcpv6bis@ietf.org">dhcpv6bis@ietf.org</a>&gt;, Tomek =
Mrugalski &lt;<a =
href=3D"mailto:tomasz.mrugalski@gmail.com">tomasz.mrugalski@gmail.com</a>=
&gt;<br><b>Subject: </b>RE: Reply to Request in =
RFC3315<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>BV&gt;</span><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'> Because the client has =
moved&#8230;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>I guess Reply to Request is not =
assumed the client has moved.</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Best Regards,</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Leaf</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
 Bernie Volz (volz) [<a =
href=3D"mailto:volz@cisco.com">mailto:volz@cisco.com</a>] =
<br><b>Sent:</b> Tuesday, May 27, 2014 7:16 PM<br><b>To:</b> Leaf Yeh; =
'Marcin Siodelski'<br><b>Cc:</b> <a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; 'dhcpv6bis'; 'Tomasz =
Mrugalski'<br><b>Subject:</b> RE: Reply to Request in =
RFC3315</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>&gt;My =
question is why the server can't ignore 'the addresses in any IA in the =
message from the client', and send back a new address for the IA =
requested by the client per its (configuration) =
policy.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>Because the client =
has moved and so we want it to start over &#8211; it may be that lots of =
other items have changed as well (perhaps even a &#8220;better&#8221; =
server is available).</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:black'><span style=3D'mso-list:Ignore'>-<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'font-size:11.0pt;color:#1F497D'>Bernie</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
 Leaf Yeh [<a =
href=3D"mailto:leaf.yeh.sdo@gmail.com">mailto:leaf.yeh.sdo@gmail.com</a>]=
 <br><b>Sent:</b> Tuesday, May 27, 2014 4:55 AM<br><b>To:</b> Bernie =
Volz (volz); 'Marcin Siodelski'<br><b>Cc:</b> <a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; 'dhcpv6bis'; 'Tomasz =
Mrugalski'<br><b>Subject:</b> Reply to Request in RFC3315</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>BV&gt; In =
Request case it is within the IA and means that the client's requested =
addresses (or PD) is not on the link...The Request case is a bit weird =
in one respect as 18.1.8 says:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp; When the client receives a NotOnLink =
status from the server in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp; response to a Request, the client can =
either re-issue the Request<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp; without specifying any addresses or =
restart the DHCP server discovery<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp; process (see section =
17).<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>This kind of implies that it is =
&quot;global&quot;. I think this case was to handle the client moving =
between Solicit and Request (but with the same server still responding =
since the Server DUID matches).<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>The above =
quoted paragraph is associated with one paragraph in section 18.2.1, =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp;&nbsp;If the server finds that the =
prefix on one or more IP addresses in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp; any IA in the message from the client =
is not appropriate for the link<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp; to which the client is connected, the =
server </span><span lang=3DEN-US style=3D'color:red'>MUST return the IA =
to</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:red'>&nbsp;&nbsp; =
the client with a Status Code option with the value =
NotOnLink</span><span lang=3DEN-US =
style=3D'color:black'>.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>My =
question is why the server can't ignore 'the addresses in any IA in the =
message from the client', and send back a new address for the IA =
requested by the client per its (configuration) =
policy.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>Best =
Regards,<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>Leaf<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p></div></div></div></bod=
y></html>
------=_NextPart_000_0172_01CF7A03.0136C190--


From nobody Wed May 28 03:56:30 2014
Return-Path: <otroan@employees.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 6179E1A0929; Wed, 28 May 2014 03:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, 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 xrOSQvN07o2f; Wed, 28 May 2014 03:56:26 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BF571A0084; Wed, 28 May 2014 03:56:26 -0700 (PDT)
Received: from dhcp-10-61-109-245.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 701EB6190; Wed, 28 May 2014 03:56:14 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <5384aae3.2ae6440a.7b97.ffffdf4e@mx.google.com>
Date: Wed, 28 May 2014 12:56:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <18B851EE-1047-40F4-8D72-CFCF78E07A82@employees.org>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <538425b3.08e6440a.08fb.7da2@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E1B04C315@xmb-rcd-x04.cisco.com> <5384aae3.2ae6440a.7b97.ffffdf4e@mx.google.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/KqtaQeEJ70soxgnZpGllQseN6AU
Cc: dhcwg@ietf.org, "Bernie Volz \(volz\)" <volz@cisco.com>, dhcpv6bis <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] More Discussion - RE: [Dhcpv6bis] Reply to Confirm in RFC3315
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, 28 May 2014 10:56:28 -0000

> BV> Confirm is supposed to be quick and easy for servers (no database =
looks =85 about a specific lease) =96 just to verify that addresses are =
on link (which is any easy test to locate the prefix containing the =
addresses).
>=20
> Even though Confirm in RFC3315 sounds only verify the addresses in IAs =
and assume the client knows the correct lease for each address, it still =
looks much clearer that the server does verify each IA, and could send =
back the Status Code for each IA.
>=20
> I do personally like Confirm could works as Renew. J

we did exactly that in RFC3633.
although servers without the binding is unlikely to be able to give any =
confirmation, in the stateful-issues draft I believe we specify a more =
generic form of confirm, that can also be used by other IA types than =
addresses.

cheers,
Ole

> From: Bernie Volz (volz) [mailto:volz@cisco.com]=20
> Sent: Tuesday, May 27, 2014 7:14 PM
> To: Leaf Yeh
> Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'; 'Marcin =
Siodelski'
> Subject: RE: More Discussion - RE: [Dhcpv6bis] Reply to Confirm in =
RFC3315
>=20
> What is the point of all this?
>=20
> Confirm does not confirm any leases or lease times. It just confirms =
that the addresses are ON LINK.
>=20
> Confirm is supposed to be quick and easy for servers (no database =
looks or writes about a specific lease) =96 just to verify that =
addresses are on link (which is any easy test to locate the prefix =
containing the addresses). It is NOT a Renew.
>=20
> -          Bernie
>=20
> From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com]=20
> Sent: Tuesday, May 27, 2014 1:42 AM
> To: Bernie Volz (volz)
> Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'; 'Marcin =
Siodelski'
> Subject: More Discussion - RE: [Dhcpv6bis] Reply to Confirm in RFC3315
>=20
> When I read the text on 'Reply to Confirm' in RFC3315, the following =
statements sounds me a little misunderstanding:
>=20
> <quote> @ 18.1.2 - Creation and Transmission of Confirm Messages
>   The client MUST include a Client Identifier option to identify =
itself
>   to the server.  The client includes IA options for all of the IAs
>   assigned to the interface for which the Confirm message is being
>   sent.  The IA options include all of the addresses the client
>   currently has associated with those IAs.  The client SHOULD set the
>   T1 and T2 fields in any IA_NA options, and the preferred-lifetime =
and
>   valid-lifetime fields in the IA Address options to 0, as the server
>   will ignore these fields.
> </quote>
>=20
> It sounds the client ask the server to confirm the address (& IA) for =
his interface, but why not ask the server to confirm the values of lease =
timers (T1/T2 for IA, preferred/valid-LT for address) he has.
>=20
>=20
> <quote> @ 18.2.2 -Receipt of Confirm Messages
>   The server ignores the T1 and T2 fields in the IA options and the
>   preferred-lifetime and valid-lifetime fields in the IA Address
>   options.
>   ...
>   The server MUST include a Server Identifier option containing the
>   server's DUID and the Client Identifier option from the Confirm
>   message in the Reply message.  The server includes a Status Code
>   option indicating the status of the Confirm message.
> </quote>
>=20
>=20
> Certainly, the server confirmed the address (& the associated IAID) of =
client based on its this own database. If the server returned the global =
=91Success=92in the Status Code option, it sounds all the information =
the client provided in Confirm has been confirmed, and assumed the =
client has the same lease as that recoded in the database of server.
>=20
> But I think it sounds much better the server could confirm (or update) =
all the information about the lease (including address and the value of =
timers) for the client in the Reply message. It looks much clearer, and =
cost little in the Reply.
>=20
> The global Status Code looks unspecified to each address (and its =
lease), which in fact needs to be confirmed.
>=20
>=20
> Best Regards,
> Leaf
>=20
>=20
>=20
> -----Original Message-----
> From: Marcin Siodelski [mailto:msiodelski@gmail.com]=20
> Sent: Monday, May 26, 2014 7:56 PM
> To: Bernie Volz (volz)
> Cc: dhcwg@ietf.org; 'dhcpv6bis'; Leaf Yeh; 'Tomasz Mrugalski'
> Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315
>=20
> Yes, NoAddrsAvail/NoBinding are not sent in response to Confirm. May =
point rather was that *even in a more general case* the server will not =
send addresses in the IA in which there is NoAddrsAvail or NoBinding.
> This comment was beyond the context of Confirm/Reply message exchange.
>=20
> Marcin
>=20
> On Mon 26 May 2014 13:41:30 CEST, Bernie Volz (volz) wrote:
>> I think we're talking about Reply to Confirm. If so, why would these =
contain NoAddrsAvail/NoBinding? They don't. Confirm does not validate a =
particular client's addresses/PDs or bindings. It only validates whether =
the addresses/PDs are on link or not.
>>=20
>> Other than global errors like UnspecFail, a Confirm will either =
contain NotOnLink or Success. Nothing else.
>>=20
>> And, yes the idea was there could be multiple servers some of which =
may send NotOnLink (as they may be lacking the configuration) but others =
that send Success. The Success on can be taken.
>>=20
>> In general servers that aren't authoritative for a particular set of =
links should not respond.
>>=20
>> - Bernie
>>=20
>> -----Original Message-----
>> From: Marcin Siodelski [mailto:msiodelski@gmail.com]
>> Sent: Monday, May 26, 2014 6:54 AM
>> To: Leaf Yeh; Bernie Volz (volz); 'Tomasz Mrugalski'
>> Cc: dhcwg@ietf.org; 'dhcpv6bis'
>> Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315
>>=20
>>=20
>>=20
>> On 26/05/14 04:53, Leaf Yeh wrote:
>>> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply
>>> Messages' of RFC3315:
>>>=20
>>>=20
>>>=20
>>> <quote>
>>>=20
>>> When the client receives a NotOnLink status from the server in
>>>=20
>>>   response to a Confirm message, the client performs DHCP server
>>>=20
>>>   solicitation, as described in section 17
>>> <http://tools.ietf.org/html/rfc3315#section-17>, and =
client-initiated
>>>=20
>>>   configuration as described in section 18
>>> <http://tools.ietf.org/html/rfc3315#section-18>.  If the client
>>> receives any
>>>=20
>>>   Reply messages that do not indicate a NotOnLink status, the client
>>>=20
>>>   can usethe addresses in the IA andignore any messages that
>>> indicate
>>>=20
>>>   a NotOnLink status.
>>>=20
>>> </quote>
>>>=20
>>>=20
>>>=20
>>> 1.       If the client receive an Reply message indicating =
'NoBinding'
>>> (or even ' NoAddrsAvail'), the above sounds the client can still use
>>> the address in the IA. Why?
>>=20
>> I think the context of the paragraph is important. The client sends =
Confirm to any available server and client may receive multiple Replies.
>> Typically, one of these Replies will not contain NotOnLink status (or =
contain Success) to indicate that client can use the address. Other =
servers will send NotOnLink because they are not configured for the =
particular subnet or so. So, the purpose of this paragraph is just to =
describe this scenario.
>>=20
>> Of course, client may receive Replies with other status codes too, =
and there are relevant sections that talk about client behavior in this =
case". So a couple of lines down:
>>=20
>> "
>>   The client examines the status code in each IA individually.  If =
the
>>   status code is NoAddrsAvail, the client has received no usable
>>   addresses in the IA and may choose to try obtaining addresses for =
the
>>   IA from another server.  The client uses addresses and other
>>   information from any IAs that do not contain a Status Code option
>>   with the NoAddrsAvail code.  If the client receives no addresses in
>>   any of the IAs, it may either try another server (perhaps =
restarting
>>   the DHCP server discovery process) or use the Information-request
>>   message to obtain other configuration information only.
>> "
>>=20
>> So, I don't really think there is any conflict here.
>>=20
>> Also, you indicate that the client could use the address even though =
there is a NoAddrsAvail or NoBinding. But, the returned IA will not have =
an address to be used, because server places just status code NoBinding =
or NoAddrsAvail in the IA and nothing else.
>>=20
>>=20
>>=20
>>>=20
>>> 2.       Why does the client could ignore 'any message' indicating
>>> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds
>>> conflict with the 1^st half of the above paragraph, not?
>>>=20
>>>=20
>>=20
>> The way I read it is that when the client receives at least one Reply =
that has no NotOnLink status code, it may use the address it desires to =
use. Otherwise it performs solicitation.
>>=20
>> Perhaps, it could be more precise and say something along the lines: =
if none of the Reply messages received in response to a Confirm message =
indicates success, the client performs solicitation. Otherwise, it may =
use the address.
>>=20
>> Marcin
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Wed May 28 08:35:31 2014
Return-Path: <leaf.yeh.sdo@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 D6F291A0427; Wed, 28 May 2014 08:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_62=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2z_EUgdVoQ23; Wed, 28 May 2014 08:35:20 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3D261A040C; Wed, 28 May 2014 08:35:20 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kp14so11196511pab.40 for <multiple recipients>; Wed, 28 May 2014 08:35:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=8K+Jo2USUbg1n1cOqq3Uh+jJUj7+UoO95rvPPQ7jW38=; b=Vre4kY/jTbXBImnglwXiorJOBpIw+C0chu0OaJCyJEmTLxpbZd26h9qw7hB5KHfNpV SOXISJFR2W6XbMpYo/JM+6YtX8kl1sw19GQ/NEBIx1sKUqmaXUm4rgOjNrWxPW3fHqRU BwmIxJ5DQ7lbn+/DUzXNdOgMeoZ5eGZYrDXf8ZrsTKXmRJADN/OOMyGv6J9MgiNgZyCy /dwYRgV5XLDuMiz4EhPASruHsGIaSQPt8ijZ5Z2pQKs87rxL3DsaqNzH1xZ5bHUuT1hS 8q9Jeu3gPG01HGXkd94h0Dk4QRGFjzVWjgXWDQOgOhwvu9ThQROflR0BBnzEp8ZEx/IH 54Yw==
X-Received: by 10.68.160.163 with SMTP id xl3mr357370pbb.39.1401291317106; Wed, 28 May 2014 08:35:17 -0700 (PDT)
Received: from PC ([221.219.109.1]) by mx.google.com with ESMTPSA id xk1sm90358241pac.21.2014.05.28.08.35.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 28 May 2014 08:35:16 -0700 (PDT)
Message-ID: <53860234.01f5420a.7d2f.4d1b@mx.google.com>
X-Google-Original-Message-ID: <00dc01cf7a8a$6ab5f960$4021ec20$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Ted Lemon'" <ted.lemon@nominum.com>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <538425b3.08e6440a.08fb.7da2@mx.google.com> <CB7501C1-7FB1-440B-9209-60D310D85832@nominum.com>
In-Reply-To: <CB7501C1-7FB1-440B-9209-60D310D85832@nominum.com>
Date: Wed, 28 May 2014 23:35:03 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac95qL7Tcpq9UWzjRWqWGFPfy1vTRAA3T1+w
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/FMqhDKnoiaUJkV097f0ZyaedGjc
Cc: dhcwg@ietf.org, 'Bernie Volz' <volz@cisco.com>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] More Discussion - RE: Reply to Confirm in RFC3315
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, 28 May 2014 15:35:22 -0000

Ted - That would be a change to the protocol, 

A very small change(no new message), just ask to return IAs (+ the
appropriate lease for its associated addresses) in the Reply to client.


Ted - and would serve no purpose, 

It can be used by SAVI-switch to create a new (and informational) binding
entry, when one client moved to a new SAVI-switch in the same broadcasting
domain.


Ted - since the client already knows its lease times.

Yes, the client knows but the SAVI-switch does not.


Best Regards,
Leaf

PS. https://datatracker.ietf.org/doc/draft-ietf-savi-dhcp/?include_text=1



-----Original Message-----
From: Ted Lemon [mailto:ted.lemon@nominum.com] 
Sent: Tuesday, May 27, 2014 8:40 PM
To: Leaf Yeh
Cc: Bernie Volz; Tomek Mrugalski; dhcwg@ietf.org; dhcpv6bis; Marcin
Siodelski
Subject: Re: [Dhcpv6bis] More Discussion - RE: Reply to Confirm in RFC3315

On May 27, 2014, at 1:42 AM, Leaf Yeh <leaf.yeh.sdo@gmail.com> wrote:
> It sounds the client ask the server to confirm the address (& IA) for his
interface, but why not ask the server to confirm the values of lease timers
(T1/T2 for IA, preferred/valid-LT for address) he has.

That would be a change to the protocol, and would serve no purpose, since
the client already knows its lease times.   The point of this exercise is
not to make gratuitous changes to the protocol.


From nobody Wed May 28 09:53:34 2014
Return-Path: <leaf.yeh.sdo@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 987191A09DB; Wed, 28 May 2014 09:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CHFGR_QYrERi; Wed, 28 May 2014 09:53:29 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E5D11A01A0; Wed, 28 May 2014 09:53:29 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kq14so11355369pab.38 for <multiple recipients>; Wed, 28 May 2014 09:53:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=x4hsOZN2jx/CCUd+RTuqJCBsqVKGOs5ojsaiSKlFeRo=; b=p0ALfhB1xM/0FrEgw1GFStjpjmJUwjZoUEBSpFNn5zBYiDeIX8qQdRZzZPHKuA/A1h qBF/NY1Jdz898Y8XxmSSevH93xDsgjw0fcgk4FFl1gp/ambjz8uWf/DKx6NOqRT11WaQ 7H+7hfEw0T1MrbfzW6qlrjVaZXvl8fXJtmRSJgL9NmOAPUXlVQv62qsYcIEcVhNjVOXi L3TJYjCLMoPbOJzY2b6EoT/NA83UoKPmlpZ5w08BjTWDCTEkzIWSXclHE8tuXHHpvE6H 2+QPA8/NoUPeRkaV4YrYEdHlCjED99N8YBhREK+9EBQNZcOJJ1zOaF814hHn2GvsM8jk KDiA==
X-Received: by 10.68.102.34 with SMTP id fl2mr1272822pbb.2.1401296005713; Wed, 28 May 2014 09:53:25 -0700 (PDT)
Received: from PC ([221.219.109.1]) by mx.google.com with ESMTPSA id vn13sm15285902pab.8.2014.05.28.09.53.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 28 May 2014 09:53:25 -0700 (PDT)
Message-ID: <53861485.6d9a420a.3681.ffffd0a2@mx.google.com>
X-Google-Original-Message-ID: <010501cf7a95$55229800$ff67c800$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Ole Troan'" <otroan@employees.org>
References: <5382acc1.42b6440a.5361.ffff8363@mx.google.com> <53831D49.8020800@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B049C7E@xmb-rcd-x04.cisco.com> <53832BB3.6000902@gmail.com> <538425b3.08e6440a.08fb.7da2@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E1B04C315@xmb-rcd-x04.cisco.com> <5384aae3.2ae6440a.7b97.ffffdf4e@mx.google.com> <18B851EE-1047-40F4-8D72-CFCF78E07A82@employees.org>
In-Reply-To: <18B851EE-1047-40F4-8D72-CFCF78E07A82@employees.org>
Date: Thu, 29 May 2014 00:53:13 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac96Y+6TdC7nrhSEQcOwBlYa5rf8pwAIs8NA
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/RXbiDYdIw1S23vNvwzNNKqkudi8
Cc: dhcwg@ietf.org, "'Bernie Volz \(volz\)'" <volz@cisco.com>, 'dhcpv6bis' <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] [Dhcpv6bis] More Discussion - RE: Reply to Confirm in RFC3315
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, 28 May 2014 16:53:31 -0000

Ole - we did exactly that in RFC3633.

Per Section 12.1- Requesting router behavior in RFC3633, "The Confirm and
Decline message types are not used with Prefix Delegation. " I suppose
RFC3633 employs Rebind instead of Confirm.


Ole - in the stateful-issues draft I believe we specify a more generic form
of confirm, 

I propose a smallest change to employ back Confirm, surely we need IA_PD to
be included in Confirm to support PD. 
But the Reply to Confirm could also include IA_NA and/or IA_PD (+
IA-specified status code). 
I might need to find some time to read draft-stateful-issues again.


Ole - that can also be used by other IA types than addresses.

DHCPv6 Confirm -> Reply process needs support both IA_NA and IA_PD, and
shall respond them respectively, not only return the global and vague
'NotOnLink'. And it is better to return their lease in IA_NA and/or IA_PD.
Then we got flexibility and precision in the same time.


Best Regards,
Leaf



-----Original Message-----
From: Dhcpv6bis [mailto:dhcpv6bis-bounces@ietf.org] On Behalf Of Ole Troan
Sent: Wednesday, May 28, 2014 6:56 PM
To: Leaf Yeh
Cc: dhcwg@ietf.org; Bernie Volz (volz); dhcpv6bis
Subject: Re: [Dhcpv6bis] [dhcwg] More Discussion - RE: Reply to Confirm in
RFC3315

> BV> Confirm is supposed to be quick and easy for servers (no database
looks . about a specific lease) - just to verify that addresses are on link
(which is any easy test to locate the prefix containing the addresses).
> 
> Even though Confirm in RFC3315 sounds only verify the addresses in IAs and
assume the client knows the correct lease for each address, it still looks
much clearer that the server does verify each IA, and could send back the
Status Code for each IA.
> 
> I do personally like Confirm could works as Renew. J

we did exactly that in RFC3633.
although servers without the binding is unlikely to be able to give any
confirmation, in the stateful-issues draft I believe we specify a more
generic form of confirm, that can also be used by other IA types than
addresses.

cheers,
Ole

> From: Bernie Volz (volz) [mailto:volz@cisco.com]
> Sent: Tuesday, May 27, 2014 7:14 PM
> To: Leaf Yeh
> Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'; 'Marcin Siodelski'
> Subject: RE: More Discussion - RE: [Dhcpv6bis] Reply to Confirm in 
> RFC3315
> 
> What is the point of all this?
> 
> Confirm does not confirm any leases or lease times. It just confirms that
the addresses are ON LINK.
> 
> Confirm is supposed to be quick and easy for servers (no database looks or
writes about a specific lease) - just to verify that addresses are on link
(which is any easy test to locate the prefix containing the addresses). It
is NOT a Renew.
> 
> -          Bernie
> 
> From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com]
> Sent: Tuesday, May 27, 2014 1:42 AM
> To: Bernie Volz (volz)
> Cc: dhcwg@ietf.org; 'dhcpv6bis'; 'Tomasz Mrugalski'; 'Marcin Siodelski'
> Subject: More Discussion - RE: [Dhcpv6bis] Reply to Confirm in RFC3315
> 
> When I read the text on 'Reply to Confirm' in RFC3315, the following
statements sounds me a little misunderstanding:
> 
> <quote> @ 18.1.2 - Creation and Transmission of Confirm Messages
>   The client MUST include a Client Identifier option to identify itself
>   to the server.  The client includes IA options for all of the IAs
>   assigned to the interface for which the Confirm message is being
>   sent.  The IA options include all of the addresses the client
>   currently has associated with those IAs.  The client SHOULD set the
>   T1 and T2 fields in any IA_NA options, and the preferred-lifetime and
>   valid-lifetime fields in the IA Address options to 0, as the server
>   will ignore these fields.
> </quote>
> 
> It sounds the client ask the server to confirm the address (& IA) for his
interface, but why not ask the server to confirm the values of lease timers
(T1/T2 for IA, preferred/valid-LT for address) he has.
> 
> 
> <quote> @ 18.2.2 -Receipt of Confirm Messages
>   The server ignores the T1 and T2 fields in the IA options and the
>   preferred-lifetime and valid-lifetime fields in the IA Address
>   options.
>   ...
>   The server MUST include a Server Identifier option containing the
>   server's DUID and the Client Identifier option from the Confirm
>   message in the Reply message.  The server includes a Status Code
>   option indicating the status of the Confirm message.
> </quote>
> 
> 
> Certainly, the server confirmed the address (& the associated IAID) of
client based on its this own database. If the server returned the global
'Success'in the Status Code option, it sounds all the information the client
provided in Confirm has been confirmed, and assumed the client has the same
lease as that recoded in the database of server.
> 
> But I think it sounds much better the server could confirm (or update) all
the information about the lease (including address and the value of timers)
for the client in the Reply message. It looks much clearer, and cost little
in the Reply.
> 
> The global Status Code looks unspecified to each address (and its lease),
which in fact needs to be confirmed.
> 
> 
> Best Regards,
> Leaf
> 
> 
> 
> -----Original Message-----
> From: Marcin Siodelski [mailto:msiodelski@gmail.com]
> Sent: Monday, May 26, 2014 7:56 PM
> To: Bernie Volz (volz)
> Cc: dhcwg@ietf.org; 'dhcpv6bis'; Leaf Yeh; 'Tomasz Mrugalski'
> Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315
> 
> Yes, NoAddrsAvail/NoBinding are not sent in response to Confirm. May point
rather was that *even in a more general case* the server will not send
addresses in the IA in which there is NoAddrsAvail or NoBinding.
> This comment was beyond the context of Confirm/Reply message exchange.
> 
> Marcin
> 
> On Mon 26 May 2014 13:41:30 CEST, Bernie Volz (volz) wrote:
>> I think we're talking about Reply to Confirm. If so, why would these
contain NoAddrsAvail/NoBinding? They don't. Confirm does not validate a
particular client's addresses/PDs or bindings. It only validates whether the
addresses/PDs are on link or not.
>> 
>> Other than global errors like UnspecFail, a Confirm will either contain
NotOnLink or Success. Nothing else.
>> 
>> And, yes the idea was there could be multiple servers some of which may
send NotOnLink (as they may be lacking the configuration) but others that
send Success. The Success on can be taken.
>> 
>> In general servers that aren't authoritative for a particular set of
links should not respond.
>> 
>> - Bernie
>> 
>> -----Original Message-----
>> From: Marcin Siodelski [mailto:msiodelski@gmail.com]
>> Sent: Monday, May 26, 2014 6:54 AM
>> To: Leaf Yeh; Bernie Volz (volz); 'Tomasz Mrugalski'
>> Cc: dhcwg@ietf.org; 'dhcpv6bis'
>> Subject: Re: [Dhcpv6bis] Reply to Confirm in RFC3315
>> 
>> 
>> 
>> On 26/05/14 04:53, Leaf Yeh wrote:
>>> Got 2 questions on the text in Section 18.1.8-'Receipt of Reply 
>>> Messages' of RFC3315:
>>> 
>>> 
>>> 
>>> <quote>
>>> 
>>> 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 
>>> <http://tools.ietf.org/html/rfc3315#section-17>, and 
>>> client-initiated
>>> 
>>>   configuration as described in section 18 
>>> <http://tools.ietf.org/html/rfc3315#section-18>.  If the client 
>>> receives any
>>> 
>>>   Reply messages that do not indicate a NotOnLink status, the client
>>> 
>>>   can usethe addresses in the IA andignore any messages that 
>>> indicate
>>> 
>>>   a NotOnLink status.
>>> 
>>> </quote>
>>> 
>>> 
>>> 
>>> 1.       If the client receive an Reply message indicating 'NoBinding'
>>> (or even ' NoAddrsAvail'), the above sounds the client can still use 
>>> the address in the IA. Why?
>> 
>> I think the context of the paragraph is important. The client sends
Confirm to any available server and client may receive multiple Replies.
>> Typically, one of these Replies will not contain NotOnLink status (or
contain Success) to indicate that client can use the address. Other servers
will send NotOnLink because they are not configured for the particular
subnet or so. So, the purpose of this paragraph is just to describe this
scenario.
>> 
>> Of course, client may receive Replies with other status codes too, and
there are relevant sections that talk about client behavior in this case".
So a couple of lines down:
>> 
>> "
>>   The client examines the status code in each IA individually.  If the
>>   status code is NoAddrsAvail, the client has received no usable
>>   addresses in the IA and may choose to try obtaining addresses for the
>>   IA from another server.  The client uses addresses and other
>>   information from any IAs that do not contain a Status Code option
>>   with the NoAddrsAvail code.  If the client receives no addresses in
>>   any of the IAs, it may either try another server (perhaps restarting
>>   the DHCP server discovery process) or use the Information-request
>>   message to obtain other configuration information only.
>> "
>> 
>> So, I don't really think there is any conflict here.
>> 
>> Also, you indicate that the client could use the address even though
there is a NoAddrsAvail or NoBinding. But, the returned IA will not have an
address to be used, because server places just status code NoBinding or
NoAddrsAvail in the IA and nothing else.
>> 
>> 
>> 
>>> 
>>> 2.       Why does the client could ignore 'any message' indicating
>>> 'NotOnLink' (in the 2^nd half of the above paragraph)? It sounds 
>>> conflict with the 1^st half of the above paragraph, not?
>>> 
>>> 
>> 
>> The way I read it is that when the client receives at least one Reply
that has no NotOnLink status code, it may use the address it desires to use.
Otherwise it performs solicitation.
>> 
>> Perhaps, it could be more precise and say something along the lines: if
none of the Reply messages received in response to a Confirm message
indicates success, the client performs solicitation. Otherwise, it may use
the address.
>> 
>> Marcin
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

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


From nobody Fri May 30 14:33:07 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 81D521A883F for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 14:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYexLjink8ru for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 14:33:04 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF791A6FFA for <dhcwg@ietf.org>; Fri, 30 May 2014 14:33:03 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id q59so2560905wes.24 for <dhcwg@ietf.org>; Fri, 30 May 2014 14:32:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=6ea30Gi0d6+N6TIHI2pkOdcrq+WOyal+eDlzjatlw8Y=; b=IExCWSmstEkHj06sBfA0nem84sO78ZzJd9+Fc3pEmH1XH/qBWFKxldNZbuEDjK+hbD VL0NpGObItoBa3PoBOfLeFj4IdKaM2/kDB8ZQFU7AIBwDjIeZGSXUJNoKGf7JrRQXv3v ohLHPW36P34azaAWmQ5BT/eSLeopicQySTo41WOGkILHTsbcmHAK2TYMtyHmTHyOgKfn igPAbfSvQiRBLFDx4cCJc5a+2LrrOR/qIQZbB7fA0dGtbDRcIc1C+QIJh/lSc1uBfMjv LOVN0dYpq/Dh6juisOFUUvSGz3VswQALRMbS44VNj3eTkFPyXhuALj6JUd+W4oTF15TD EuDQ==
X-Received: by 10.195.12.34 with SMTP id en2mr26429440wjd.13.1401485577727; Fri, 30 May 2014 14:32:57 -0700 (PDT)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id nb8sm9084669wic.18.2014.05.30.14.32.55 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 May 2014 14:32:56 -0700 (PDT)
Message-ID: <5388F901.1000709@gmail.com>
Date: Fri, 30 May 2014 23:32:49 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
References: <535FEDAD.5010103@gmail.com>
In-Reply-To: <535FEDAD.5010103@gmail.com>
X-Enigmail-Version: 1.5.2
X-TagToolbar-Keys: D20140530233249716
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/902fYSuhXLkoGWleYxbRI6F9_Rw
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 30 May 2014 21:33:06 -0000

On 29.04.2014 20:21, Tomek Mrugalski wrote:
> Hi all,
> 
> This message starts DHC working group last call about advancing Secure
> DHCPv6 with Public Key document as a Standards Track RFC. The authors
> believe that this version addressed all the issues raised and is ready.
Apologies that I didn't participate in the discussion and didn't
review this draft earlier.

<dhc co-chair hat off>
I read draft-ietf-dhc-sedhcpv6-02 and support this work. I think there's
significant value in this work. I agree with previous commenters that
the specific use cases could be described somewhere, perhaps in the
introduction section. One use case where it could be useful is a high
security network, like a military base or a R&D department that wants to
protect its secrets. This authentication could be mutual - legitimate
employers are provided with devices that have preconfigured keys and
this mechanism is an additional step in access control. On the other
hand, the employees want to make sure that they indeed connect to the
legitimate network, not a spoofed one. Another use case could be a paid
hotspot. Unknown clients are assigned a different set of
addresses/options that get them to the site where they can pay for the
service. Once the service is paid, the client becomes known and future
configuration will get him direct connection, thus bypassing annoying
login/pay portal. Having to go through the captive portal only one could
be a big advantage of this mechanism.

The server authentication could also be useful. Mobile clients can
store list of previously visited networks that are known to work.

I think it is important to add a section that enumerates those and
similar use cases. Otherwise you risk that this work will be stalled
and you'd be asked to write a separate problem statement document.

Section 1 claims that messages exchanged between relay agents and
servers are less vulnerable. That is usually true, but it is possible
for client to spoof a relay. Instead of sending plain messages,
it could send Relay-forward messages with spoofed options and
Solicit or Request inside it. I don't see any obvious attack vector
here, though.

Nitpick: I'm confused what the fourth paragraph is Section 3 is about.
It starts discussion about manual key distribution, but then explains
flaws of reconfigure key authentication. These are not really related
topics, so I think it would read better if the text was split into 2
paragraphs.

Section 4:
soltuion => solution
certificates are can be used => certificates can be used

Nitpick: The text mentions clients and DHCPv6 servers. It reads a bit
awkwardly. It should be either "DHCPv6 clients and DHCPv6 servers" or
"clients and servers". You may mention in Terminology section what
clients and servers mean and then use that shorter version throught
the text. It will just read easier.

Section 4.3 says "the DHCPv6 server (for most of known DHCPv6
implementations) would just omit or disregard unknown options and still
process the known options." Are you aware of any implementations that
do not follow this principle?

"If the client accept the unsecure messages from the DHCPv6 server.
The subsequent exchanges will be in unsecure model." Those two
sentences should be combined into one.

"If the server mandidates the authentication..." =>
"If the server's policy requires the authentication..."

Section 5.1: The Public key format is confusing. Should it be binary
data or hex? Second sentence suggests that it's hex string. 2048bit key
requires 256 bytes if sent as a binary. However, if you send it as
hex string, it requires 512 bytes. Obviously, better way is to send
it as binary, as it is size optimal.

+1 for having packet size discussion in the document. Here's my take
on it:

Section 5.2 says that the maxium certificate length is 65535 bytes.
There are other limits that would practically never allow you to put
that large option. The first soft limit is MTU of the interface, which
is typically 1500 bytes - IPv6 header size - UDP header - DHCPv6
header - size of mandatory options - size of certificate option
header. (Some may point out that the min. MTU for IPv6-capable links
is 1280, so the limit may be even lower than that). This is a "soft"
limit. If you cross it, DHCPv6 messages will get fragmented. There's
nothing in RFC3315 that forbid that, but I never saw fragmented DHCPv6
packets out in the wild and I expect that it may cause problems
(firewalls dropping fragments, simple clients not supporting
fragmentation etc.). You can get above that limit, but you'd be
walking on an increasingly exotic territory. The next limit is imposed
by Payload length in IPv6 header. Its max. value is 65535, so you need
to decrease it by mentioned UDP/DHCPv6/options headers. So even
max. UDP packet is not enough for storing the max size of the option
you propose. I'd be very interested in seeing how existing
implementations behave when they receive 64k packets. If you really
want to go above that, there are jumbograms (see RFC2675). Although I
haven't checked that, my gut feeling is that current implementations
will be puzzled when they get a jumbogram-wrapped DHCPv6 packet. Note
that the current text of section 5.2 implies that jumbograms are
required to deliver the biggest OPTION_CERT_PARAMETER option. I do not
know how big X.509 certificates can be. If they are approaching 1500
bytes, you should have a section discussing the issues I mentioned.

This document defines two mandatory algorithms: SHA-256 for hash and
RSASSA-PKCS1-v1_5 for signature. I'm not a security expert by any
means, so I'm not questioning those choices, but it would be useful if
you could include some background information why you chose those two.

Time stamp in section 3. You chose the timestamp to follow RFC5905
format (64 bit, starting 1 Jan 1900). DHCPv6 already defines a time
format (see section 9.2 in RFC3315), which unfortunately is only
32bits. NTP format has the advantage of being 64 bits, but
unnecessarily covers dates from 20th century. RFC3315 style on the
other hand begins 1 Jan 2000, but is only 32 bits. Perhaps it would
make sense to define a new format: 64 bit, starting in 2000? This is
just somthing to consider. I'm ok if you want to keep current format.

They last paragraph in 5.3 says that authentication option is not
covered. So it's unclear for me how should I calculate the digests
if both authentication and signature options are present.

Section 5.4 defines new value of status code called
NotSupportAlgorithm. The name sounds a bit awkward.
AlgorithmNotSupported sound better in my opinion. Also, its definition
says that the server does not support algorithms that the sender
(presumably the client) used. What is the opposite is true: client does
not support an algorithm that the server used? Up until now, client
never did send status codes. Is the case where client needs to
communicate this failure to the server described in the text? Also, I
think the status descriptions should be reworded to use either
server/client or sender/receiver.

Further in the same section: SignitureFail => SignatureFail. That
misspelling appears in multiple sections.

Section 6.1: which MUST contructed => which MUST be contructed

Section 6.1 "Upon receiving an AuthFailNotSupportLoF error status
code [...] the client MAY switch to other certificate or public
key if it has.  But it SHOULD NOT retry with the same certificate/
public-key." Why SHOULD NOT and not MUST NOT?

"Upon receiving a SignitureFail error status code, the client MAY
resend the message.". I have 2 issues with that. First, if the
receiver was unable to verify the signature first time, why would
retransmission fix anything? It is likely that the repeated
transmissions will also fail signature verification. Second, there
should be some clarification regarding retransmission not being
immiediate. Otherwise, you risk clients flooding the server. I think
some clarification like "upon receiving non-success status code, the
client follows normal retransmission routines defined in RFC3315"
would do the trick here.

Section 6.2: "In the failure cases, both DHCPv6 server and client
SHOULD NOT process received message, and the server SHOULD reply a
correspondent error status could, while the client does nothing."
Isn't this a configuration policy? I can imagine a case where clients
that failed authentication are still served, but they get a different
threatment (like a separate subnet with captive portal that explains
what they are supposed to do).

The paragraph that discusses leap of faith should say that specific
behavior depends on configured policy.

Section 6.4 rough synchronized clocks => roughly synchronized clocks

Section 7 "The clients may decline..." => "The clients may discard..."
('decline' has special meaning in DHCPv6 context).

Section 8: Why do you need reserved (0000) value in Hash algorithm
table?

I'd like to see a section describing key rollover. It doesn't have to
be long. Just a paragraph or two would suffice.

<co-chair hat on>
I'll chat with Bernie early next week and we'll wrap up this WGLC
shortly afterwards.

Tomek


From nobody Fri May 30 17:47:27 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 254DB1A030D for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 17:47:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 XGp5UPXTghvk for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 17:47:25 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B9521A0685 for <dhcwg@ietf.org>; Fri, 30 May 2014 17:47:25 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id DB6601B81EB for <dhcwg@ietf.org>; Fri, 30 May 2014 17:47:20 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id AE58619005C; Fri, 30 May 2014 17:47:20 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 30 May 2014 17:47:20 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5388F901.1000709@gmail.com>
Date: Fri, 30 May 2014 20:47:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <78B235AF-D94C-40F1-9C76-4159B3A0A043@nominum.com>
References: <535FEDAD.5010103@gmail.com> <5388F901.1000709@gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/p9nX54BB03dZiaYyTXPMU2EF9pU
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 31 May 2014 00:47:26 -0000

On May 30, 2014, at 5:32 PM, Tomek Mrugalski =
<tomasz.mrugalski@gmail.com> wrote:
> I think it is important to add a section that enumerates those and
> similar use cases. Otherwise you risk that this work will be stalled
> and you'd be asked to write a separate problem statement document.

A use case can't be theoretical.   You should have an actual use for it. =
  So I think documenting use cases like a "high security network" is =
pointless.   The point of this mechanism is to authenticate DHCP =
transactions in both directions using public keys.   Why do we need a =
list of use cases for this?   This is something we've been asked for for =
over a decade.   Does someone seriously think there's a different way to =
do this that's more appropriate?   If so, please explain!   Does someone =
think that the actual uses documented in the draft won't work?   If so, =
please say why.

I certainly think that if people want to suggest ways of clarifying the =
document, that would be beneficial, but let's not get carried away =
throwing the kitchen sink into the document for no good reason.   That =
makes it slower to review and is as likely to generate controversy as =
quell it.


From nobody Fri May 30 17:57:25 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D0911A043C for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 17:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zOD-R5OMhjMi for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 17:57:21 -0700 (PDT)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F2AC1A030D for <dhcwg@ietf.org>; Fri, 30 May 2014 17:57:21 -0700 (PDT)
Received: by mail-qg0-f50.google.com with SMTP id z60so7562837qgd.9 for <dhcwg@ietf.org>; Fri, 30 May 2014 17:57:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ag/TpYVTaEDJ5ky/+9WwaHI4Al7+TWXnJZ/5rmmkFek=; b=WT4UOxrfD4Vq1hpSY2kUN0Yb7jblEuVKaOZk3w0HSOM85NF3OCGX2GA0zJdIpdp+xf ucpjJH8c5NscfOuB29QtkLOepCvWbI0O4nt2pCsDKxI4lB5WPRsvE/+6DEwjhPreoLpo JS9L0ip+KA1Ssf5hmI7ZMZZb2/rssWM44S3bvEnAvuW/o5hd0caakGqArOKJBJRyB8X+ 2I1yrg+sD9Fc9HQ6uAbIvAyznz1H3OPsXik+tG/b8oWkrX2Djlp2g7t6eKyRBcVGQL2C T+jx0n8y+W6mqWKHAXKqoxZHGJVqcLRqlYKWhWtayE2zQNC/E6tt3dEPz7LYjSUVC1xu t/EQ==
X-Received: by 10.224.37.10 with SMTP id v10mr26243307qad.98.1401497836598; Fri, 30 May 2014 17:57:16 -0700 (PDT)
Received: from che-vpn-cluster-2-271.cisco.com (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id b10sm8784698qag.31.2014.05.30.17.57.13 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 May 2014 17:57:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <78B235AF-D94C-40F1-9C76-4159B3A0A043@nominum.com>
Date: Fri, 30 May 2014 20:57:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F079574B-FF8A-4C8B-B562-0E0F8D4DC47F@gmail.com>
References: <535FEDAD.5010103@gmail.com> <5388F901.1000709@gmail.com> <78B235AF-D94C-40F1-9C76-4159B3A0A043@nominum.com>
To: Lemon Ted <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/u1Ne8jQlMH4dZh4RXv8bLSNm1XA
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 31 May 2014 00:57:24 -0000

On May 30, 2014, at 8:47 PM 5/30/14, Ted Lemon <ted.lemon@nominum.com> =
wrote:

> On May 30, 2014, at 5:32 PM, Tomek Mrugalski =
<tomasz.mrugalski@gmail.com> wrote:
>> I think it is important to add a section that enumerates those and
>> similar use cases. Otherwise you risk that this work will be stalled
>> and you'd be asked to write a separate problem statement document.
>=20
> A use case can't be theoretical.   You should have an actual use for =
it.   So I think documenting use cases like a "high security network" is =
pointless.   The point of this mechanism is to authenticate DHCP =
transactions in both directions using public keys.   Why do we need a =
list of use cases for this?   This is something we've been asked for for =
over a decade.   Does someone seriously think there's a different way to =
do this that's more appropriate?   If so, please explain!   Does someone =
think that the actual uses documented in the draft won't work?   If so, =
please say why.

In my opinion, there is a need in the document for an applicability =
statement that gives guidance about what this mechanism provides and in =
what situations it is useful.  I have come to this opinion because a =
precise understanding of exactly what the protocol will provide will be =
important to those considering its deployment.

- Ralph

>=20
> I certainly think that if people want to suggest ways of clarifying =
the document, that would be beneficial, but let's not get carried away =
throwing the kitchen sink into the document for no good reason.   That =
makes it slower to review and is as likely to generate controversy as =
quell it.
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Fri May 30 17:59:04 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 EB1541A06C5 for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 17:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 8-ALCveGVVRG for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 17:58:59 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1387E1A06C3 for <dhcwg@ietf.org>; Fri, 30 May 2014 17:58:59 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A3FA41B81C6 for <dhcwg@ietf.org>; Fri, 30 May 2014 17:58:54 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 9DCC719005C; Fri, 30 May 2014 17:58:54 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 30 May 2014 17:58:54 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <F079574B-FF8A-4C8B-B562-0E0F8D4DC47F@gmail.com>
Date: Fri, 30 May 2014 20:58:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <9EC3E851-483F-49CA-8C76-8D3149E4A230@nominum.com>
References: <535FEDAD.5010103@gmail.com> <5388F901.1000709@gmail.com> <78B235AF-D94C-40F1-9C76-4159B3A0A043@nominum.com> <F079574B-FF8A-4C8B-B562-0E0F8D4DC47F@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/3K3D_s1Lo2qf5tcucnCk1N5kqNY
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 31 May 2014 00:59:02 -0000

On May 30, 2014, at 8:57 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
> In my opinion, there is a need in the document for an applicability =
statement that gives guidance about what this mechanism provides and in =
what situations it is useful.  I have come to this opinion because a =
precise understanding of exactly what the protocol will provide will be =
important to those considering its deployment.

Isn't it applicable in any case where you want to authenticate the other =
endpoint that you are communicating with?   Are there use cases where =
you want that but this mechanism wouldn't be the right mechanism?



From nobody Fri May 30 18:10:33 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 920D21A06CB for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 18:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Syu2He4_uihH for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 18:10:23 -0700 (PDT)
Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A85741A06D1 for <dhcwg@ietf.org>; Fri, 30 May 2014 18:10:05 -0700 (PDT)
Received: by mail-qg0-f54.google.com with SMTP id q108so7563927qgd.27 for <dhcwg@ietf.org>; Fri, 30 May 2014 18:10:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ja+q8BGigTi0ESB/7uKbZpSeZ9Wxgfbqdl8Y/ayComM=; b=b2x49gPNVbaPhs+azqBgZkMx14blt/iabzTaAo8k3aal5W4ZWlTOixrIqdo0IRDmWs 1x/4vXN2D5Uon3jznMTadbt8KmYgi0LcG8aB3hcTaiLSuABsgT4WR74xR5X1G/vC9VNb LrWQBTmrPL4T398pPclCk2YkgnoV3R4LIv95cbrzsvtre5nvVk+EhxvlycIm5QB0pwpu LLTrb8coRqfsJXNIF5X8lYBTy/5D2DGokyXLE1O6HQDNJPBvm/HxNN3h32Z/XYzRDAm2 ZBXrUmVmrWYzSlRsdhKBGeEeYP8iq09oCmas8l0JwBNPyBUURS/MrnVxi9Yx7gf+cMoB 0ARg==
X-Received: by 10.229.234.67 with SMTP id kb3mr26720120qcb.6.1401498600875; Fri, 30 May 2014 18:10:00 -0700 (PDT)
Received: from che-vpn-cluster-2-271.cisco.com (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id s60sm3508740qga.30.2014.05.30.18.09.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 May 2014 18:09:57 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <9EC3E851-483F-49CA-8C76-8D3149E4A230@nominum.com>
Date: Fri, 30 May 2014 21:09:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1A3F542-E891-4B5D-961A-ED86E9234B03@gmail.com>
References: <535FEDAD.5010103@gmail.com> <5388F901.1000709@gmail.com> <78B235AF-D94C-40F1-9C76-4159B3A0A043@nominum.com> <F079574B-FF8A-4C8B-B562-0E0F8D4DC47F@gmail.com> <9EC3E851-483F-49CA-8C76-8D3149E4A230@nominum.com>
To: Lemon Ted <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/DK7aKZ8boeuuporBvRkZ255zvjM
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 31 May 2014 01:10:25 -0000

On May 30, 2014, at 8:58 PM 5/30/14, Ted Lemon <ted.lemon@nominum.com> =
wrote:

> On May 30, 2014, at 8:57 PM, Ralph Droms <rdroms.ietf@gmail.com> =
wrote:
>> In my opinion, there is a need in the document for an applicability =
statement that gives guidance about what this mechanism provides and in =
what situations it is useful.  I have come to this opinion because a =
precise understanding of exactly what the protocol will provide will be =
important to those considering its deployment.
>=20
> Isn't it applicable in any case where you want to authenticate the =
other endpoint that you are communicating with?   Are there use cases =
where you want that but this mechanism wouldn't be the right mechanism?
>=20
>=20
My concern is that the RFC should be clear that authenticating the other =
endpoint isn't always enough, or can't be used in some situations.  =
Authenticating messages from a malicious server doesn't do much good.  I =
don't see how this mechanism could be used in an open network situation =
like at your local coffee chain shop.

- Ralph


From nobody Fri May 30 18:23:02 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 72EB21A043C for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 18:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 1nOqtqv-pZia for <dhcwg@ietfa.amsl.com>; Fri, 30 May 2014 18:22:56 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1104A1A0354 for <dhcwg@ietf.org>; Fri, 30 May 2014 18:22:56 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A11171B81D5 for <dhcwg@ietf.org>; Fri, 30 May 2014 18:22:51 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 8930119005C; Fri, 30 May 2014 18:22:51 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 30 May 2014 18:22:51 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <D1A3F542-E891-4B5D-961A-ED86E9234B03@gmail.com>
Date: Fri, 30 May 2014 21:22:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <D0FBDF9E-172E-4BA8-AB89-8AB7E9DA7309@nominum.com>
References: <535FEDAD.5010103@gmail.com> <5388F901.1000709@gmail.com> <78B235AF-D94C-40F1-9C76-4159B3A0A043@nominum.com> <F079574B-FF8A-4C8B-B562-0E0F8D4DC47F@gmail.com> <9EC3E851-483F-49CA-8C76-8D3149E4A230@nominum.com> <D1A3F542-E891-4B5D-961A-ED86E9234B03@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/wlNy7uDW6l96gtr0-tg80e4fwaU
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-02 - Respond by May 18
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, 31 May 2014 01:22:57 -0000

On May 30, 2014, at 9:09 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
> My concern is that the RFC should be clear that authenticating the =
other endpoint isn't always enough, or can't be used in some situations. =
 Authenticating messages from a malicious server doesn't do much good.  =
I don't see how this mechanism could be used in an open network =
situation like at your local coffee chain shop.

I don't think the working group is qualified to say under what =
circumstances this mechanism is useful.   I can think of scenarios where =
it makes perfect sense to use it in the local coffee shop, and also =
scenarios where it doesn't.   It's applicable when you have keys, or =
when you are willing to make a leap of faith, or when you want to verify =
that the thing you're talking to now is the same thing you talked to =
previously.   Going through "it makes sense in the enterprise but not =
the coffee shop" seems wrong-headed to me.

