
From mohamed.boucadair@orange.com  Fri Mar  1 02:24:09 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7B821F886A for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 02:24:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.083
X-Spam-Level: 
X-Spam-Status: No, score=-2.083 tagged_above=-999 required=5 tests=[AWL=0.165,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LddEfwoC5XEv for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 02:24:08 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id C0BDF21F87E0 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 02:24:07 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 1695B22C7BF; Fri,  1 Mar 2013 11:24:06 +0100 (CET)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id D482F27C076; Fri,  1 Mar 2013 11:24:05 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Fri, 1 Mar 2013 11:24:04 +0100
From: <mohamed.boucadair@orange.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Date: Fri, 1 Mar 2013 11:24:03 +0100
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: Ac4To7U7cr4L60i/Ykinr5uevMfmMQATmaFQABQKCgAAfc7GkAAK4lGQ
Message-ID: <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.1.94517
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 10:24:09 -0000

Hi Bernie, all,

I updated the text as follows:

OLD:

   o  If the request is successfully handled by the server, the server
      MUST include a Status Code Option indicating "Success".

   o  If the request includes several Client Identifier options but the
      server will issue reconfigure requests only for a subset of them,
      the server MUST include a Status Code Option indicating "Success"
      but in the meantime it MUST copy back the list of Client
      Identifier Options pointing to clients for which the server won't
      issue a Reconfigure message.

   o  If the server failed to process the request for all clients, the
      server MUST set the Status Code Option to the appropriate status
      code (e.g., UnspecFail, NotAllowed, etc.).

NEW:

   o  If the request is successfully handled by the server, the server
      MUST include a Status Code Option indicating "Success".

   o  If the request includes several Client Identifier options but the
      server won't issue reconfigure requests to all of them, the server
      MUST include in Reconfigure-Ack a Status Code Option
      indicating "Success" but in the meantime it MUST copy back the
      list of Client Identifier Options pointing to clients for which
      the server won't issue a Reconfigure message.

   o  If the server fails to process the request for all clients, the
      server MUST set the Status Code Option to the appropriate status
      code (e.g., UnspecFail, NotAllowed, etc.).  In particular,

      *  UnspecFail MUST be returned if Reconfigure-Request message is
         malformed.

      *  NotAllowed MUST be returned if the server is not configured to
         allow Reconfigure-Request.

      *  NotConfigured MUST be returned if the server has no record of
         the link.=20


Please check if the new wording is better.
If there are no other comments, this text will be incorporated in the next =
iteration of the draft.

Cheers,
Med

>-----Message d'origine-----
>De : Bernie Volz (volz) [mailto:volz@cisco.com]=20
>Envoy=E9 : vendredi 1 mars 2013 06:21
>=C0 : Tomek Mrugalski; BOUCADAIR Mohamed OLNC/OLN
>Cc : dhcwg@ietf.org
>Objet : RE: [dhcwg] Reminder - WGLC:=20
>draft-ietf-dhc-triggered-reconfigure-03
>
>(WG hat off)
>
>The issue regarding section 4.4 and error-codes should be=20
>addressed and clarified.
>
>Personally, I don't see a need for the server to return=20
>specific status (error) information for each client, as the=20
>likely reasons it would not be able to send a Reconfigure is=20
>because the client didn't negotiate for reconfigure support or=20
>the client doesn't exist in the server. There are other=20
>reasons (lack of resources) ...
>
>We have to ask what benefit (other than potentially logging)=20
>would the Relay gain by having more specific information? I=20
>don't really believe there is.
>
>Perhaps the three possible returns are:
>- Full Success (first bullet in existing section).
>- Partial Success (second bullet) - includes list of clients=20
>NOT processed (for whatever reason) which might be ALL clients.
>- Full failure (third bullet) where clients were not even=20
>attempted - this handles the case where:
>A) the packet is malformed (for example has no=20
>client-identifier option) - UnspecFail
>B) the server has been configured not to allow this request -=20
>NotAllowed
>C) the server has no record of the link - NotConfigured
>
>- Bernie
>
>-----Original Message-----
>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20
>On Behalf Of Tomek Mrugalski
>Sent: Tuesday, February 26, 2013 5:57 AM
>To: mohamed.boucadair@orange.com
>Cc: dhcwg@ietf.org
>Subject: Re: [dhcwg] Reminder - WGLC:=20
>draft-ietf-dhc-triggered-reconfigure-03
>
>On 26.02.2013 10:34, mohamed.boucadair@orange.com wrote:
>>> Figure 1 mentions NAS, without explaining what it means. I presume=20
>>> that it is Network Access Server, but it is not a common=20
>term in DHCP=20
>>> world, so it would be good to explain it.
>>=20
>> Med: I added this sentence:=20
>> "Figure 1 shows a broadband network scenario in which the=20
>Network Access Server (NAS) embeds a DHCPv6 relay agent."
>> Do you think the document needs to say more?
>No. That addition is sufficient.
>
>
>>> Section 2: "Reconfigure message is then sent to the DHCPv6 relay,=20
>>> which in turn will forward the message to the appropriate DHCPv6=20
>>> client." This reconfigure message will be sent encapsulated in=20
>>> Relay-Reply, so it will look like every other message=20
>received from a=20
>>> server and to be processed by the relay, right? There's no=20
>text that=20
>>> clarifies that.
>>=20
>> Med: I added this sentence just after the one you quoted:=20
>>=20
>> "Note, the server encapsulates the Reconfigure message in a=20
>Relay-reply message."
>> Better?
>Yes.
>
>>> Last paragraph is section 2 talks about retransmissions, but do not=20
>>> explain how to conduct them if there is no server response.=20
>It should=20
>>> point out that the details are explained in section 4.3.
>> Med: The text is now updated to call out Section 4.3.=20
>Thanks.
>
>>> Section 4.2.1: "Clients MUST silently discard any received=20
>>> RECONFIGURE-REQUEST messages.". I would add that logging such an=20
>>> event is allowed, though.
>> Med: Is there any value to log such events in the client side?
>Sometimes yes. Some clients (e.g. dibbler) will print out a=20
>warning message, when receiving unknown message (basically=20
>anything besides advertise or reply). Reception of such a=20
>message by a client may mean that your network is seriously=20
>broken or there is an attack in progress.
>This is really a grey area that nobody cares about. Many=20
>clients and servers log various things when configured with=20
>sufficient log levels.
>If we want to be strict, this is a violation of RFC3315, but I=20
>have serious doubts anyone care about that. So I'm ok if you=20
>don't want to do anything here.
>
>>> "The server MUST be configurable to accept or reject RECONFIGURE-=20
>>> REQUEST messages." This should probably be moved to "Server=20
>behavior"
>>> section.=20
>> Med: Ok for me. Done.
>Thanks.
>
>> Also, you should specify what is the server default if not
>>> explicitly configured. It should be reject in my opinion.
>>=20
>> Med: I added this sentence:=20
>> "If no indication is explicitly configured to the server,=20
>the default behaviour is to reject RECONFIGURE-REQUEST messages."
>Ok, great.
>
>>> "The relay agent MUST be configurable to accept or reject=20
>>> RECONFIGURE- REQUEST messages received from other relay agents.".
>>> Reconfigure-Request
>>> is not addressed at relay and it merely helps deliver it to server,=20
>>> so instead of "accept or reject" I would use "forward or drop" here.
>>=20
>> Med: I do think both wording would work. "accept" is more=20
>generic as forwarding the message will be the result of other=20
>steps than just accept handling the message. I will maintain=20
>the initial wording.=20
>Ok.
>
>>> There should be a separate "Relay behavior" section and second to=20
>>> last paragraph in 4.2.1 should be moved to it.
>>=20
>> Med: I added a new section called "Intermediate Relay Agents=20
>Behaviour" and moved that text to the new section.
>Thanks.
>
>>  There are very good reasons
>>> for having separate behavior sections for server, relays and client=20
>>> There should be one for client as well, even if it contains=20
>only one=20
>>> sentence about dropping those messages. It makes life of=20
>implementors=20
>>> much easier and increases chances of wider adoption of that=20
>proposal.
>>>
>>> The last paragraph in 4.2.1 belongs more in the Server behavior=20
>>> section.
>>=20
>> Med: Agree.
>Ok, thanks.
>
>
>>> Section 4.3 "The relay may receive (Relay-Reply)=20
>Reconfigure before..."
>>> is awkward. It should be "The relay may receive Reconfigure=20
>>> encapsulated in Relay-Reply before..."
>>=20
>> Med: Fixed. Thanks.
>Thanks.
>
>>> "The relay agent MUST include a Client Identifier=20
>Option..." =3D> "The=20
>>> relay agent MUST include one or more Client Identifier Options..."
>> Med: Fixed.=20
>Thanks a lot. This was confusing without this clarification.
>
>>> Section 4.4 "Upon receipt of a valid Reconfigure-Request=20
>message from=20
>>> a
>>> DHCPv6 relay agent (see Section 4.2), the server determines the
>>> client(s) for which a Reconfigure message is to be sent.".
>>>
>>> Section 4.4, bullet 2 and 3 contradict each other. When relay=20
>>> requested reconfigure for 2 clients and one succeeds and the other=20
>>> fails, what should be the return status: success or failure code?
>>=20
>> Med: bullet 2 is about partial failure (i.e., there is at least a=20
>> success for one client); bullet 3 is when there is failure for all=20
>> clients. In
>the
>> partial failure case, the list of failed cio are returned=20
>also in the=20
>> Reconfigure-Ack.
>>=20
>>  What if the
>>> failure reasons are different for each client? It seems that the=20
>>> status code returning is not very useful for more than one client.
>>>
>>> Section 4.4, bullet 2 says that server must keep list of client-ids=20
>>> that it couldn't configure, but does not explain what to do=20
>with that=20
>>> list.
>>> Did you mean "include in reconfigure-ack"? If that is so, please=20
>>> rephrase that sentence. If you meant something else, please clarify=20
>>> as well.
>>=20
>> Med: The text is about Reconfigure-Ack. I fixed the text.
>Thanks.
>
>>> Section 7. You should change the text to say that servers MUST=20
>>> discard configure-request unless explicitly configured to=20
>accept them=20
>>> (or perhaps this should go into server behavior section).=20
>It's better=20
>>> to be safe than sorry.
>>=20
>> Med: discarding RECONFIGURE-REQUEST messages + configuration options=20
>> are already covered in the server behaviour. I prefer
>Good point. THere's no need to repeat them here. One place is enough.
>
>>> Although DUIDs are typically 14 bytes long, the maximum allowed=20
>>> length is 128, so we can hit fragementation limit with only 10=20
>>> clients. There should be a short clarification that relay=20
>should send=20
>>> separate reconfigure-requests if there are more clients (or some=20
>>> other suggestion what to do if the MTU limit is hit).
>>=20
>> Med: Isn't this covered in the text of Section 4.3:=20
>>=20
>>  If including Client
>>    Identifier Options of all impacted clients exceeds the maximum
>>    message size (see Section 5), the relay MUST generate several
>>    RECONFIGURE-REQUEST messages required to carry all Client=20
>Identifier
>>    Options.  Rate-limit considerations are discussed in Section 5.
>Oh, I missed that. Sorry. Yes, the existing text is clear then.
>
>>> Reconfigure mechanism is optional. What should the server do if=20
>>> client does not support Reconfigure?  There's currently no way for=20
>>> server to signal that to back to relay. UnspecFail doesn't look=20
>>> right. Perhaps NotConfigured would be the right code for it?
>>=20
>> Med: If we need to specific, a new error code need to be defined for=20
>> this case. If you think there is a value in specifying that=20
>behaviour,=20
>> I suggest we define a new error code for it.
>I don't know. Does the relay can use the information why the=20
>reconfigure failed? I suppose there could be some value in=20
>making different permanent failures (e.g. the client do not=20
>support reconfigure) with some temporary failure that may=20
>disappear when repeated reconfigure request is made. But I do=20
>not have any strong opinion on that. Can someone else comment=20
>on this as well?
>
>>> Excuse my poor understanding of how NAS works, but does it=20
>keep DUIDs=20
>>> of all clients connected through it? So from the pure DHCP=20
>>> perspective, this is a stateful relay, right? If that is so, it=20
>>> should be pointed somewhere that the way relay keeps the=20
>information=20
>>> about clients is outside of scope for this document.
>>=20
>> Med: Section 2 says:=20
>>=20
>>    This setup assumes the relay has a record of the client,=20
>so that it
>>    has enough information to send the Reconfigure-Request=20
>message to the
>>    server.  Means to recover state in failure events must be=20
>supported,
>>    but are not discussed in this document.
>>=20
>> I propose to change it to
>>=20
>>    This setup assumes the relay has a record of the client,=20
>so that it
>>    has enough information to send the Reconfigure-Request=20
>message to the
>>    server. How the state is recorded in the relay is out of=20
>scope. Furthermore, means to recover state in failure events=20
>must be supported,
>>    but are not discussed in this document.
>Ok.
>
>Ok, great. That deals with all my comments. Let's see if=20
>anyone else has additional comments on the status code. I'm ok=20
>with leaving it as it is, reusing some of the codes from=20
>leasequery or defining a new one.
>
>After that I think the draft is good to move forward.
>
>Cheers,
>Tomek
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg
>=

From volz@cisco.com  Fri Mar  1 05:35:09 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DDE221F90CE for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 05:35:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.513
X-Spam-Level: 
X-Spam-Status: No, score=-10.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id et5JDPE7oxke for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 05:35:08 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF6521F90C1 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 05:34:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14768; q=dns/txt; s=iport; t=1362144898; x=1363354498; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Stn7yEd+TKNtZhNlA5hD5klDj7V3CrywITGehv8NTwc=; b=OhyXqwuAkMEcQZO3I3jX/1azLZb45n7uFhZGVnIBD1gOIdTjVwnfW1rY lwac8FlpZOe/yzMKxFJEJzrG+GiO/q1bJyKBTPyeVEKDcQVdgoaH7VNOG Kxj3GR3tmD2SvJKwaw0alpOOIh5NTfH66VCyheHnXoL2aPiQIbQSYzK8D M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAHStMFGtJV2c/2dsb2JhbABFwjN7FnOCHwEBAQMBAQEBRCUCCAMFBwQCAQgRBAEBAScHJwsUCQgBAQQOBRmHdAYMslKOMASNToETKAsHBoJZYQOINY4OkGuDCIFpAQYZBA
X-IronPort-AV: E=Sophos;i="4.84,761,1355097600"; d="scan'208";a="182644046"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 01 Mar 2013 13:34:57 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r21DYv0X029738 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Mar 2013 13:34:57 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 07:34:57 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: Ac4To7U7cr4L60i/Ykinr5uevMfmMQATmaFQABQKCgAAfc7GkAAK4lGQAAch57M=
Date: Fri, 1 Mar 2013 13:34:56 +0000
Message-ID: <82B68ADB-4FD0-475B-86C5-0CD9EAA6A6E5@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com>, <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 13:35:09 -0000

I still think this means if there is 1 client in request but it cannot be R=
econfigured as client didn't negotiate for that support, the third case wou=
ld apply but I don't think that is what you want as what status code would =
you use?

In my mind third case means that request itself is invalid - not that clien=
ts are.

Use of "won't" is also not recommended.

Perhaps reorder the items:
1. Server is unable to process request. Missing data, not allowed, unknown =
link.
2. Server processes request but one or more clients cannot be sent a reconf=
igure (might be all clients).
3. Full success. This is same as #2, just no clients included.

- Bernie

On Mar 1, 2013, at 5:24 AM, "mohamed.boucadair@orange.com" <mohamed.boucada=
ir@orange.com> wrote:

> Hi Bernie, all,
>=20
> I updated the text as follows:
>=20
> OLD:
>=20
>   o  If the request is successfully handled by the server, the server
>      MUST include a Status Code Option indicating "Success".
>=20
>   o  If the request includes several Client Identifier options but the
>      server will issue reconfigure requests only for a subset of them,
>      the server MUST include a Status Code Option indicating "Success"
>      but in the meantime it MUST copy back the list of Client
>      Identifier Options pointing to clients for which the server won't
>      issue a Reconfigure message.
>=20
>   o  If the server failed to process the request for all clients, the
>      server MUST set the Status Code Option to the appropriate status
>      code (e.g., UnspecFail, NotAllowed, etc.).
>=20
> NEW:
>=20
>   o  If the request is successfully handled by the server, the server
>      MUST include a Status Code Option indicating "Success".
>=20
>   o  If the request includes several Client Identifier options but the
>      server won't issue reconfigure requests to all of them, the server
>      MUST include in Reconfigure-Ack a Status Code Option
>      indicating "Success" but in the meantime it MUST copy back the
>      list of Client Identifier Options pointing to clients for which
>      the server won't issue a Reconfigure message.
>=20
>   o  If the server fails to process the request for all clients, the
>      server MUST set the Status Code Option to the appropriate status
>      code (e.g., UnspecFail, NotAllowed, etc.).  In particular,
>=20
>      *  UnspecFail MUST be returned if Reconfigure-Request message is
>         malformed.
>=20
>      *  NotAllowed MUST be returned if the server is not configured to
>         allow Reconfigure-Request.
>=20
>      *  NotConfigured MUST be returned if the server has no record of
>         the link.=20
>=20
>=20
> Please check if the new wording is better.
> If there are no other comments, this text will be incorporated in the nex=
t iteration of the draft.
>=20
> Cheers,
> Med
>=20
>> -----Message d'origine-----
>> De : Bernie Volz (volz) [mailto:volz@cisco.com]=20
>> Envoy=E9 : vendredi 1 mars 2013 06:21
>> =C0 : Tomek Mrugalski; BOUCADAIR Mohamed OLNC/OLN
>> Cc : dhcwg@ietf.org
>> Objet : RE: [dhcwg] Reminder - WGLC:=20
>> draft-ietf-dhc-triggered-reconfigure-03
>>=20
>> (WG hat off)
>>=20
>> The issue regarding section 4.4 and error-codes should be=20
>> addressed and clarified.
>>=20
>> Personally, I don't see a need for the server to return=20
>> specific status (error) information for each client, as the=20
>> likely reasons it would not be able to send a Reconfigure is=20
>> because the client didn't negotiate for reconfigure support or=20
>> the client doesn't exist in the server. There are other=20
>> reasons (lack of resources) ...
>>=20
>> We have to ask what benefit (other than potentially logging)=20
>> would the Relay gain by having more specific information? I=20
>> don't really believe there is.
>>=20
>> Perhaps the three possible returns are:
>> - Full Success (first bullet in existing section).
>> - Partial Success (second bullet) - includes list of clients=20
>> NOT processed (for whatever reason) which might be ALL clients.
>> - Full failure (third bullet) where clients were not even=20
>> attempted - this handles the case where:
>> A) the packet is malformed (for example has no=20
>> client-identifier option) - UnspecFail
>> B) the server has been configured not to allow this request -=20
>> NotAllowed
>> C) the server has no record of the link - NotConfigured
>>=20
>> - Bernie
>>=20
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20
>> On Behalf Of Tomek Mrugalski
>> Sent: Tuesday, February 26, 2013 5:57 AM
>> To: mohamed.boucadair@orange.com
>> Cc: dhcwg@ietf.org
>> Subject: Re: [dhcwg] Reminder - WGLC:=20
>> draft-ietf-dhc-triggered-reconfigure-03
>>=20
>> On 26.02.2013 10:34, mohamed.boucadair@orange.com wrote:
>>>> Figure 1 mentions NAS, without explaining what it means. I presume=20
>>>> that it is Network Access Server, but it is not a common
>> term in DHCP=20
>>>> world, so it would be good to explain it.
>>>=20
>>> Med: I added this sentence:=20
>>> "Figure 1 shows a broadband network scenario in which the
>> Network Access Server (NAS) embeds a DHCPv6 relay agent."
>>> Do you think the document needs to say more?
>> No. That addition is sufficient.
>>=20
>>=20
>>>> Section 2: "Reconfigure message is then sent to the DHCPv6 relay,=20
>>>> which in turn will forward the message to the appropriate DHCPv6=20
>>>> client." This reconfigure message will be sent encapsulated in=20
>>>> Relay-Reply, so it will look like every other message
>> received from a=20
>>>> server and to be processed by the relay, right? There's no
>> text that=20
>>>> clarifies that.
>>>=20
>>> Med: I added this sentence just after the one you quoted:=20
>>>=20
>>> "Note, the server encapsulates the Reconfigure message in a
>> Relay-reply message."
>>> Better?
>> Yes.
>>=20
>>>> Last paragraph is section 2 talks about retransmissions, but do not=20
>>>> explain how to conduct them if there is no server response.
>> It should=20
>>>> point out that the details are explained in section 4.3.
>>> Med: The text is now updated to call out Section 4.3.
>> Thanks.
>>=20
>>>> Section 4.2.1: "Clients MUST silently discard any received=20
>>>> RECONFIGURE-REQUEST messages.". I would add that logging such an=20
>>>> event is allowed, though.
>>> Med: Is there any value to log such events in the client side?
>> Sometimes yes. Some clients (e.g. dibbler) will print out a=20
>> warning message, when receiving unknown message (basically=20
>> anything besides advertise or reply). Reception of such a=20
>> message by a client may mean that your network is seriously=20
>> broken or there is an attack in progress.
>> This is really a grey area that nobody cares about. Many=20
>> clients and servers log various things when configured with=20
>> sufficient log levels.
>> If we want to be strict, this is a violation of RFC3315, but I=20
>> have serious doubts anyone care about that. So I'm ok if you=20
>> don't want to do anything here.
>>=20
>>>> "The server MUST be configurable to accept or reject RECONFIGURE-=20
>>>> REQUEST messages." This should probably be moved to "Server
>> behavior"
>>>> section.
>>> Med: Ok for me. Done.
>> Thanks.
>>=20
>>> Also, you should specify what is the server default if not
>>>> explicitly configured. It should be reject in my opinion.
>>>=20
>>> Med: I added this sentence:=20
>>> "If no indication is explicitly configured to the server,
>> the default behaviour is to reject RECONFIGURE-REQUEST messages."
>> Ok, great.
>>=20
>>>> "The relay agent MUST be configurable to accept or reject=20
>>>> RECONFIGURE- REQUEST messages received from other relay agents.".
>>>> Reconfigure-Request
>>>> is not addressed at relay and it merely helps deliver it to server,=20
>>>> so instead of "accept or reject" I would use "forward or drop" here.
>>>=20
>>> Med: I do think both wording would work. "accept" is more
>> generic as forwarding the message will be the result of other=20
>> steps than just accept handling the message. I will maintain=20
>> the initial wording.=20
>> Ok.
>>=20
>>>> There should be a separate "Relay behavior" section and second to=20
>>>> last paragraph in 4.2.1 should be moved to it.
>>>=20
>>> Med: I added a new section called "Intermediate Relay Agents
>> Behaviour" and moved that text to the new section.
>> Thanks.
>>=20
>>> There are very good reasons
>>>> for having separate behavior sections for server, relays and client=20
>>>> There should be one for client as well, even if it contains
>> only one=20
>>>> sentence about dropping those messages. It makes life of
>> implementors=20
>>>> much easier and increases chances of wider adoption of that
>> proposal.
>>>>=20
>>>> The last paragraph in 4.2.1 belongs more in the Server behavior=20
>>>> section.
>>>=20
>>> Med: Agree.
>> Ok, thanks.
>>=20
>>=20
>>>> Section 4.3 "The relay may receive (Relay-Reply)
>> Reconfigure before..."
>>>> is awkward. It should be "The relay may receive Reconfigure=20
>>>> encapsulated in Relay-Reply before..."
>>>=20
>>> Med: Fixed. Thanks.
>> Thanks.
>>=20
>>>> "The relay agent MUST include a Client Identifier
>> Option..." =3D> "The=20
>>>> relay agent MUST include one or more Client Identifier Options..."
>>> Med: Fixed.
>> Thanks a lot. This was confusing without this clarification.
>>=20
>>>> Section 4.4 "Upon receipt of a valid Reconfigure-Request
>> message from=20
>>>> a
>>>> DHCPv6 relay agent (see Section 4.2), the server determines the
>>>> client(s) for which a Reconfigure message is to be sent.".
>>>>=20
>>>> Section 4.4, bullet 2 and 3 contradict each other. When relay=20
>>>> requested reconfigure for 2 clients and one succeeds and the other=20
>>>> fails, what should be the return status: success or failure code?
>>>=20
>>> Med: bullet 2 is about partial failure (i.e., there is at least a=20
>>> success for one client); bullet 3 is when there is failure for all=20
>>> clients. In
>> the
>>> partial failure case, the list of failed cio are returned
>> also in the=20
>>> Reconfigure-Ack.
>>>=20
>>> What if the
>>>> failure reasons are different for each client? It seems that the=20
>>>> status code returning is not very useful for more than one client.
>>>>=20
>>>> Section 4.4, bullet 2 says that server must keep list of client-ids=20
>>>> that it couldn't configure, but does not explain what to do
>> with that=20
>>>> list.
>>>> Did you mean "include in reconfigure-ack"? If that is so, please=20
>>>> rephrase that sentence. If you meant something else, please clarify=20
>>>> as well.
>>>=20
>>> Med: The text is about Reconfigure-Ack. I fixed the text.
>> Thanks.
>>=20
>>>> Section 7. You should change the text to say that servers MUST=20
>>>> discard configure-request unless explicitly configured to
>> accept them=20
>>>> (or perhaps this should go into server behavior section).
>> It's better=20
>>>> to be safe than sorry.
>>>=20
>>> Med: discarding RECONFIGURE-REQUEST messages + configuration options=20
>>> are already covered in the server behaviour. I prefer
>> Good point. THere's no need to repeat them here. One place is enough.
>>=20
>>>> Although DUIDs are typically 14 bytes long, the maximum allowed=20
>>>> length is 128, so we can hit fragementation limit with only 10=20
>>>> clients. There should be a short clarification that relay
>> should send=20
>>>> separate reconfigure-requests if there are more clients (or some=20
>>>> other suggestion what to do if the MTU limit is hit).
>>>=20
>>> Med: Isn't this covered in the text of Section 4.3:=20
>>>=20
>>> If including Client
>>>   Identifier Options of all impacted clients exceeds the maximum
>>>   message size (see Section 5), the relay MUST generate several
>>>   RECONFIGURE-REQUEST messages required to carry all Client
>> Identifier
>>>   Options.  Rate-limit considerations are discussed in Section 5.
>> Oh, I missed that. Sorry. Yes, the existing text is clear then.
>>=20
>>>> Reconfigure mechanism is optional. What should the server do if=20
>>>> client does not support Reconfigure?  There's currently no way for=20
>>>> server to signal that to back to relay. UnspecFail doesn't look=20
>>>> right. Perhaps NotConfigured would be the right code for it?
>>>=20
>>> Med: If we need to specific, a new error code need to be defined for=20
>>> this case. If you think there is a value in specifying that
>> behaviour,=20
>>> I suggest we define a new error code for it.
>> I don't know. Does the relay can use the information why the=20
>> reconfigure failed? I suppose there could be some value in=20
>> making different permanent failures (e.g. the client do not=20
>> support reconfigure) with some temporary failure that may=20
>> disappear when repeated reconfigure request is made. But I do=20
>> not have any strong opinion on that. Can someone else comment=20
>> on this as well?
>>=20
>>>> Excuse my poor understanding of how NAS works, but does it
>> keep DUIDs=20
>>>> of all clients connected through it? So from the pure DHCP=20
>>>> perspective, this is a stateful relay, right? If that is so, it=20
>>>> should be pointed somewhere that the way relay keeps the
>> information=20
>>>> about clients is outside of scope for this document.
>>>=20
>>> Med: Section 2 says:=20
>>>=20
>>>   This setup assumes the relay has a record of the client,
>> so that it
>>>   has enough information to send the Reconfigure-Request
>> message to the
>>>   server.  Means to recover state in failure events must be
>> supported,
>>>   but are not discussed in this document.
>>>=20
>>> I propose to change it to
>>>=20
>>>   This setup assumes the relay has a record of the client,
>> so that it
>>>   has enough information to send the Reconfigure-Request
>> message to the
>>>   server. How the state is recorded in the relay is out of
>> scope. Furthermore, means to recover state in failure events=20
>> must be supported,
>>>   but are not discussed in this document.
>> Ok.
>>=20
>> Ok, great. That deals with all my comments. Let's see if=20
>> anyone else has additional comments on the status code. I'm ok=20
>> with leaving it as it is, reusing some of the codes from=20
>> leasequery or defining a new one.
>>=20
>> After that I think the draft is good to move forward.
>>=20
>> Cheers,
>> Tomek
>>=20
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg

From Ted.Lemon@nominum.com  Fri Mar  1 05:50:43 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A1521F8BA2 for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 05:50:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.58
X-Spam-Level: 
X-Spam-Status: No, score=-106.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pmtuET8AuFJb for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 05:50:43 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id D4D9C21F95A8 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 05:50:37 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUTCyJDTdZnLr044hQg7V7ehyS94sxrMB@postini.com; Fri, 01 Mar 2013 05:50:38 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2D69910804D for <dhcwg@ietf.org>; Fri,  1 Mar 2013 05:50:28 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 205F4190043; Fri,  1 Mar 2013 05:50:28 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 05:50:28 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: AQHOE6O0r+FJTNnUlkKnhUGkzSCfKJiMZ76AgAAXCQCABFkeAIAAVLqAgAA5qgA=
Date: Fri, 1 Mar 2013 13:50:27 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <0E8392074592CD46BB2DE0C751707F73@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 13:50:43 -0000

On Mar 1, 2013, at 5:24 AM, mohamed.boucadair@orange.com wrote:
>   o  If the request includes several Client Identifier options but the
>      server won't issue reconfigure requests to all of them, the server
>      MUST include in Reconfigure-Ack a Status Code Option
>      indicating "Success" but in the meantime it MUST copy back the
>      list of Client Identifier Options pointing to clients for which
>      the server won't issue a Reconfigure message.

I'm uncomfortable with the number of conditionals in this that seem unneces=
sary.   How about this:

If the server is able to issue one or more Reconfigure messages to the clie=
nts identified in the Reconfigure-Request, the server MUST return a Status =
Code option indicating "success."   In addition, the server MUST include a =
list of all the Client-Identifier options of the clients to which Reconfigu=
re messages were successfully sent.

This points out two issues that I think you should consider:

1. What result code does the server return if zero of the listed clients co=
uld receive a Reconfigure?
2. Is this really even a good idea?   Now the DHCP server is holding off on=
 sending the acknowledgement until all the reconfigures have been sent; is =
that in fact what you want?   It's fine if it is, but I thought I'd ask the=
 question.   You probably already answered it elsewhere in the draft, but I=
 haven't read it in a while. :(


From mohamed.boucadair@orange.com  Fri Mar  1 05:52:15 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3F221E80E2 for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 05:52:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level: 
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[AWL=0.162,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VhjbRlqlSShh for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 05:52:14 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id AA0F221E80DA for <dhcwg@ietf.org>; Fri,  1 Mar 2013 05:52:13 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id CE93322C6A2; Fri,  1 Mar 2013 14:52:12 +0100 (CET)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id AA846238061; Fri,  1 Mar 2013 14:52:12 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Fri, 1 Mar 2013 14:52:12 +0100
From: <mohamed.boucadair@orange.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Date: Fri, 1 Mar 2013 14:52:11 +0100
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: Ac4To7U7cr4L60i/Ykinr5uevMfmMQATmaFQABQKCgAAfc7GkAAK4lGQAAch57MAAAwcsA==
Message-ID: <94C682931C08B048B7A8645303FDC9F36EB47D7ACD@PUEXCB1B.nanterre.francetelecom.fr>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com>, <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <82B68ADB-4FD0-475B-86C5-0CD9EAA6A6E5@cisco.com>
In-Reply-To: <82B68ADB-4FD0-475B-86C5-0CD9EAA6A6E5@cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.19.124517
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 13:52:15 -0000

Re-,

Please see inline.

Cheers,
Med


>-----Message d'origine-----
>De : Bernie Volz (volz) [mailto:volz@cisco.com]
>Envoy=E9 : vendredi 1 mars 2013 14:35
>=C0 : BOUCADAIR Mohamed OLNC/OLN
>Cc : Tomek Mrugalski; dhcwg@ietf.org
>Objet : Re: [dhcwg] Reminder - WGLC:
>draft-ietf-dhc-triggered-reconfigure-03
>
>I still think this means if there is 1 client in request but
>it cannot be Reconfigured as client didn't negotiate for that
>support, the third case would apply but I don't think that is
>what you want as what status code would you use?

Med: For me this is covered in the second bullet:

   o  If the request includes several Client Identifier options but the
      server won't issue reconfigure requests to all of them, the server
      MUST include in Reconfigure-Ack a Status Code Option
      indicating "Success" but in the meantime it MUST copy back the
      list of Client Identifier Options pointing to clients for which
      the server won't issue a Reconfigure message.

Should the text be tweaked further?

>
>In my mind third case means that request itself is invalid -
>not that clients are.

Med: The third bullet covers the case where the server fails to process the=
 request itself or can't process it for administrative reasons.

>
>Use of "won't" is also not recommended.

Med: s/won't/is unable to?

>
>Perhaps reorder the items:
>1. Server is unable to process request. Missing data, not
>allowed, unknown link.
>2. Server processes request but one or more clients cannot be
>sent a reconfigure (might be all clients).
>3. Full success. This is same as #2, just no clients included.
>
>- Bernie
>
>On Mar 1, 2013, at 5:24 AM, "mohamed.boucadair@orange.com"
><mohamed.boucadair@orange.com> wrote:
>
>> Hi Bernie, all,
>>
>> I updated the text as follows:
>>
>> OLD:
>>
>>   o  If the request is successfully handled by the server, the server
>>      MUST include a Status Code Option indicating "Success".
>>
>>   o  If the request includes several Client Identifier
>options but the
>>      server will issue reconfigure requests only for a
>subset of them,
>>      the server MUST include a Status Code Option indicating
>"Success"
>>      but in the meantime it MUST copy back the list of Client
>>      Identifier Options pointing to clients for which the
>server won't
>>      issue a Reconfigure message.
>>
>>   o  If the server failed to process the request for all clients, the
>>      server MUST set the Status Code Option to the appropriate status
>>      code (e.g., UnspecFail, NotAllowed, etc.).
>>
>> NEW:
>>
>>   o  If the request is successfully handled by the server, the server
>>      MUST include a Status Code Option indicating "Success".
>>
>>   o  If the request includes several Client Identifier
>options but the
>>      server won't issue reconfigure requests to all of them,
>the server
>>      MUST include in Reconfigure-Ack a Status Code Option
>>      indicating "Success" but in the meantime it MUST copy back the
>>      list of Client Identifier Options pointing to clients for which
>>      the server won't issue a Reconfigure message.
>>
>>   o  If the server fails to process the request for all clients, the
>>      server MUST set the Status Code Option to the appropriate status
>>      code (e.g., UnspecFail, NotAllowed, etc.).  In particular,
>>
>>      *  UnspecFail MUST be returned if Reconfigure-Request message is
>>         malformed.
>>
>>      *  NotAllowed MUST be returned if the server is not
>configured to
>>         allow Reconfigure-Request.
>>
>>      *  NotConfigured MUST be returned if the server has no record of
>>         the link.
>>
>>
>> Please check if the new wording is better.
>> If there are no other comments, this text will be
>incorporated in the next iteration of the draft.
>>
>> Cheers,
>> Med
>>
>>> -----Message d'origine-----
>>> De : Bernie Volz (volz) [mailto:volz@cisco.com]
>>> Envoy=E9 : vendredi 1 mars 2013 06:21
>>> =C0 : Tomek Mrugalski; BOUCADAIR Mohamed OLNC/OLN
>>> Cc : dhcwg@ietf.org
>>> Objet : RE: [dhcwg] Reminder - WGLC:
>>> draft-ietf-dhc-triggered-reconfigure-03
>>>
>>> (WG hat off)
>>>
>>> The issue regarding section 4.4 and error-codes should be
>>> addressed and clarified.
>>>
>>> Personally, I don't see a need for the server to return
>>> specific status (error) information for each client, as the
>>> likely reasons it would not be able to send a Reconfigure is
>>> because the client didn't negotiate for reconfigure support or
>>> the client doesn't exist in the server. There are other
>>> reasons (lack of resources) ...
>>>
>>> We have to ask what benefit (other than potentially logging)
>>> would the Relay gain by having more specific information? I
>>> don't really believe there is.
>>>
>>> Perhaps the three possible returns are:
>>> - Full Success (first bullet in existing section).
>>> - Partial Success (second bullet) - includes list of clients
>>> NOT processed (for whatever reason) which might be ALL clients.
>>> - Full failure (third bullet) where clients were not even
>>> attempted - this handles the case where:
>>> A) the packet is malformed (for example has no
>>> client-identifier option) - UnspecFail
>>> B) the server has been configured not to allow this request -
>>> NotAllowed
>>> C) the server has no record of the link - NotConfigured
>>>
>>> - Bernie
>>>
>>> -----Original Message-----
>>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]
>>> On Behalf Of Tomek Mrugalski
>>> Sent: Tuesday, February 26, 2013 5:57 AM
>>> To: mohamed.boucadair@orange.com
>>> Cc: dhcwg@ietf.org
>>> Subject: Re: [dhcwg] Reminder - WGLC:
>>> draft-ietf-dhc-triggered-reconfigure-03
>>>
>>> On 26.02.2013 10:34, mohamed.boucadair@orange.com wrote:
>>>>> Figure 1 mentions NAS, without explaining what it means.
>I presume
>>>>> that it is Network Access Server, but it is not a common
>>> term in DHCP
>>>>> world, so it would be good to explain it.
>>>>
>>>> Med: I added this sentence:
>>>> "Figure 1 shows a broadband network scenario in which the
>>> Network Access Server (NAS) embeds a DHCPv6 relay agent."
>>>> Do you think the document needs to say more?
>>> No. That addition is sufficient.
>>>
>>>
>>>>> Section 2: "Reconfigure message is then sent to the DHCPv6 relay,
>>>>> which in turn will forward the message to the appropriate DHCPv6
>>>>> client." This reconfigure message will be sent encapsulated in
>>>>> Relay-Reply, so it will look like every other message
>>> received from a
>>>>> server and to be processed by the relay, right? There's no
>>> text that
>>>>> clarifies that.
>>>>
>>>> Med: I added this sentence just after the one you quoted:
>>>>
>>>> "Note, the server encapsulates the Reconfigure message in a
>>> Relay-reply message."
>>>> Better?
>>> Yes.
>>>
>>>>> Last paragraph is section 2 talks about retransmissions,
>but do not
>>>>> explain how to conduct them if there is no server response.
>>> It should
>>>>> point out that the details are explained in section 4.3.
>>>> Med: The text is now updated to call out Section 4.3.
>>> Thanks.
>>>
>>>>> Section 4.2.1: "Clients MUST silently discard any received
>>>>> RECONFIGURE-REQUEST messages.". I would add that logging such an
>>>>> event is allowed, though.
>>>> Med: Is there any value to log such events in the client side?
>>> Sometimes yes. Some clients (e.g. dibbler) will print out a
>>> warning message, when receiving unknown message (basically
>>> anything besides advertise or reply). Reception of such a
>>> message by a client may mean that your network is seriously
>>> broken or there is an attack in progress.
>>> This is really a grey area that nobody cares about. Many
>>> clients and servers log various things when configured with
>>> sufficient log levels.
>>> If we want to be strict, this is a violation of RFC3315, but I
>>> have serious doubts anyone care about that. So I'm ok if you
>>> don't want to do anything here.
>>>
>>>>> "The server MUST be configurable to accept or reject RECONFIGURE-
>>>>> REQUEST messages." This should probably be moved to "Server
>>> behavior"
>>>>> section.
>>>> Med: Ok for me. Done.
>>> Thanks.
>>>
>>>> Also, you should specify what is the server default if not
>>>>> explicitly configured. It should be reject in my opinion.
>>>>
>>>> Med: I added this sentence:
>>>> "If no indication is explicitly configured to the server,
>>> the default behaviour is to reject RECONFIGURE-REQUEST messages."
>>> Ok, great.
>>>
>>>>> "The relay agent MUST be configurable to accept or reject
>>>>> RECONFIGURE- REQUEST messages received from other relay agents.".
>>>>> Reconfigure-Request
>>>>> is not addressed at relay and it merely helps deliver it
>to server,
>>>>> so instead of "accept or reject" I would use "forward or
>drop" here.
>>>>
>>>> Med: I do think both wording would work. "accept" is more
>>> generic as forwarding the message will be the result of other
>>> steps than just accept handling the message. I will maintain
>>> the initial wording.
>>> Ok.
>>>
>>>>> There should be a separate "Relay behavior" section and second to
>>>>> last paragraph in 4.2.1 should be moved to it.
>>>>
>>>> Med: I added a new section called "Intermediate Relay Agents
>>> Behaviour" and moved that text to the new section.
>>> Thanks.
>>>
>>>> There are very good reasons
>>>>> for having separate behavior sections for server, relays
>and client
>>>>> There should be one for client as well, even if it contains
>>> only one
>>>>> sentence about dropping those messages. It makes life of
>>> implementors
>>>>> much easier and increases chances of wider adoption of that
>>> proposal.
>>>>>
>>>>> The last paragraph in 4.2.1 belongs more in the Server behavior
>>>>> section.
>>>>
>>>> Med: Agree.
>>> Ok, thanks.
>>>
>>>
>>>>> Section 4.3 "The relay may receive (Relay-Reply)
>>> Reconfigure before..."
>>>>> is awkward. It should be "The relay may receive Reconfigure
>>>>> encapsulated in Relay-Reply before..."
>>>>
>>>> Med: Fixed. Thanks.
>>> Thanks.
>>>
>>>>> "The relay agent MUST include a Client Identifier
>>> Option..." =3D> "The
>>>>> relay agent MUST include one or more Client Identifier Options..."
>>>> Med: Fixed.
>>> Thanks a lot. This was confusing without this clarification.
>>>
>>>>> Section 4.4 "Upon receipt of a valid Reconfigure-Request
>>> message from
>>>>> a
>>>>> DHCPv6 relay agent (see Section 4.2), the server determines the
>>>>> client(s) for which a Reconfigure message is to be sent.".
>>>>>
>>>>> Section 4.4, bullet 2 and 3 contradict each other. When relay
>>>>> requested reconfigure for 2 clients and one succeeds and
>the other
>>>>> fails, what should be the return status: success or failure code?
>>>>
>>>> Med: bullet 2 is about partial failure (i.e., there is at least a
>>>> success for one client); bullet 3 is when there is failure for all
>>>> clients. In
>>> the
>>>> partial failure case, the list of failed cio are returned
>>> also in the
>>>> Reconfigure-Ack.
>>>>
>>>> What if the
>>>>> failure reasons are different for each client? It seems that the
>>>>> status code returning is not very useful for more than one client.
>>>>>
>>>>> Section 4.4, bullet 2 says that server must keep list of
>client-ids
>>>>> that it couldn't configure, but does not explain what to do
>>> with that
>>>>> list.
>>>>> Did you mean "include in reconfigure-ack"? If that is so, please
>>>>> rephrase that sentence. If you meant something else,
>please clarify
>>>>> as well.
>>>>
>>>> Med: The text is about Reconfigure-Ack. I fixed the text.
>>> Thanks.
>>>
>>>>> Section 7. You should change the text to say that servers MUST
>>>>> discard configure-request unless explicitly configured to
>>> accept them
>>>>> (or perhaps this should go into server behavior section).
>>> It's better
>>>>> to be safe than sorry.
>>>>
>>>> Med: discarding RECONFIGURE-REQUEST messages +
>configuration options
>>>> are already covered in the server behaviour. I prefer
>>> Good point. THere's no need to repeat them here. One place
>is enough.
>>>
>>>>> Although DUIDs are typically 14 bytes long, the maximum allowed
>>>>> length is 128, so we can hit fragementation limit with only 10
>>>>> clients. There should be a short clarification that relay
>>> should send
>>>>> separate reconfigure-requests if there are more clients (or some
>>>>> other suggestion what to do if the MTU limit is hit).
>>>>
>>>> Med: Isn't this covered in the text of Section 4.3:
>>>>
>>>> If including Client
>>>>   Identifier Options of all impacted clients exceeds the maximum
>>>>   message size (see Section 5), the relay MUST generate several
>>>>   RECONFIGURE-REQUEST messages required to carry all Client
>>> Identifier
>>>>   Options.  Rate-limit considerations are discussed in Section 5.
>>> Oh, I missed that. Sorry. Yes, the existing text is clear then.
>>>
>>>>> Reconfigure mechanism is optional. What should the server do if
>>>>> client does not support Reconfigure?  There's currently
>no way for
>>>>> server to signal that to back to relay. UnspecFail doesn't look
>>>>> right. Perhaps NotConfigured would be the right code for it?
>>>>
>>>> Med: If we need to specific, a new error code need to be
>defined for
>>>> this case. If you think there is a value in specifying that
>>> behaviour,
>>>> I suggest we define a new error code for it.
>>> I don't know. Does the relay can use the information why the
>>> reconfigure failed? I suppose there could be some value in
>>> making different permanent failures (e.g. the client do not
>>> support reconfigure) with some temporary failure that may
>>> disappear when repeated reconfigure request is made. But I do
>>> not have any strong opinion on that. Can someone else comment
>>> on this as well?
>>>
>>>>> Excuse my poor understanding of how NAS works, but does it
>>> keep DUIDs
>>>>> of all clients connected through it? So from the pure DHCP
>>>>> perspective, this is a stateful relay, right? If that is so, it
>>>>> should be pointed somewhere that the way relay keeps the
>>> information
>>>>> about clients is outside of scope for this document.
>>>>
>>>> Med: Section 2 says:
>>>>
>>>>   This setup assumes the relay has a record of the client,
>>> so that it
>>>>   has enough information to send the Reconfigure-Request
>>> message to the
>>>>   server.  Means to recover state in failure events must be
>>> supported,
>>>>   but are not discussed in this document.
>>>>
>>>> I propose to change it to
>>>>
>>>>   This setup assumes the relay has a record of the client,
>>> so that it
>>>>   has enough information to send the Reconfigure-Request
>>> message to the
>>>>   server. How the state is recorded in the relay is out of
>>> scope. Furthermore, means to recover state in failure events
>>> must be supported,
>>>>   but are not discussed in this document.
>>> Ok.
>>>
>>> Ok, great. That deals with all my comments. Let's see if
>>> anyone else has additional comments on the status code. I'm ok
>>> with leaving it as it is, reusing some of the codes from
>>> leasequery or defining a new one.
>>>
>>> After that I think the draft is good to move forward.
>>>
>>> Cheers,
>>> Tomek
>>>
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>

From mohamed.boucadair@orange.com  Fri Mar  1 06:08:51 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B974421F8CAA for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:08:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level: 
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qe+x0tw4ec2v for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:08:51 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id E100321F8EA6 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 06:08:50 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id C3D55264103; Fri,  1 Mar 2013 15:08:49 +0100 (CET)
Received: from PUEXCH21.nanterre.francetelecom.fr (unknown [10.101.44.28]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 919DD35C06C; Fri,  1 Mar 2013 15:08:49 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH21.nanterre.francetelecom.fr ([10.101.44.28]) with mapi; Fri, 1 Mar 2013 15:08:49 +0100
From: <mohamed.boucadair@orange.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Date: Fri, 1 Mar 2013 15:08:48 +0100
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: AQHOE6O0r+FJTNnUlkKnhUGkzSCfKJiMZ76AgAAXCQCABFkeAIAAVLqAgAA5qgD//3qyIA==
Message-ID: <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.1.111515
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 14:08:51 -0000

Hi Ted,

Please see inline.

Cheers,
Med=20

>-----Message d'origine-----
>De : Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
>Envoy=E9 : vendredi 1 mars 2013 14:50
>=C0 : BOUCADAIR Mohamed OLNC/OLN
>Cc : Bernie Volz (volz); Tomek Mrugalski; dhcwg@ietf.org
>Objet : Re: [dhcwg] Reminder - WGLC:=20
>draft-ietf-dhc-triggered-reconfigure-03
>
>On Mar 1, 2013, at 5:24 AM, mohamed.boucadair@orange.com wrote:
>>   o  If the request includes several Client Identifier=20
>options but the
>>      server won't issue reconfigure requests to all of them,=20
>the server
>>      MUST include in Reconfigure-Ack a Status Code Option
>>      indicating "Success" but in the meantime it MUST copy back the
>>      list of Client Identifier Options pointing to clients for which
>>      the server won't issue a Reconfigure message.
>
>I'm uncomfortable with the number of conditionals in this that=20
>seem unnecessary.   How about this:
>
>If the server is able to issue one or more Reconfigure=20
>messages to the clients identified in the Reconfigure-Request,=20
>the server MUST return a Status Code option indicating=20
>"success."   In addition, the server MUST include a list of=20
>all the Client-Identifier options of the clients to which=20
>Reconfigure messages were successfully sent.

Med: Only clients for which reconfigure won't be sent are returned in the r=
esponse and also I would change "Reconfigure messages were successfully sen=
t" to "Reconfigure messages will be sent". Apart from that, I'm fine with t=
he proposed wording.

>
>This points out two issues that I think you should consider:
>
>1. What result code does the server return if zero of the=20
>listed clients could receive a Reconfigure?

Med: If there is no error to handle the request (e.g., malformed request) o=
r there is no administrative policy which disallow reconfigure-request, the=
n a "success" is returned with the list of ALL clients. Else, an error code=
 is sent back. The order proposed by Bernie will make this more clear IMHO.

>2. Is this really even a good idea?   Now the DHCP server is=20
>holding off on sending the acknowledgement until all the=20
>reconfigures have been sent; is that in fact what you want?

Med: No, the server should not hold reconfigure-ack. The reconfigure-ack is=
 sent back once the server validates the requests and concludes it can gene=
rate a reconfigure or not. For rate-limit considerations, the actual sendin=
g of the corresponding reconfigure messages will be delayed, but not the re=
configure-ack.
  =20
>It's fine if it is, but I thought I'd ask the question.   You=20
>probably already answered it elsewhere in the draft, but I=20
>haven't read it in a while. :(

Med: This text is in the draft to explain the rationale:=20

   The support of Reconfigure-Ack simplifies the retransmission
   procedure of the relay as it provides an explicit indication from the
   server.  An alternative approach is the relay monitors Reconfigure
   messages received from the server to conclude whether Reconfigure-
   Request was successfully handled or not.  Nevertheless, this implicit
   approach may fail to achieve its goals in some cases: e.g., the
   server accepts the request but it delays to generate the
   corresponding Reconfigure messages due to its rate-limiting policies,
   the request was partially failed for some clients, etc.=20

>
>=

From volz@cisco.com  Fri Mar  1 06:13:28 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC4E221E80C3 for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:13:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.54
X-Spam-Level: 
X-Spam-Status: No, score=-10.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bTxt+n2Dz1p2 for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:13:28 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 2A66821E80AA for <dhcwg@ietf.org>; Fri,  1 Mar 2013 06:13:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3768; q=dns/txt; s=iport; t=1362147208; x=1363356808; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=984XJdhXVOsjBEmZSw+pS+6ra3skOx0SJCEsnEWdLwU=; b=aCBMsVzrwKfJM8rUCMOq3oX48qaG7nWo/H/jkyaQhBhFNNlYPo40WP1g 6QEI473EgH5yepXpuhVvMnPHr52bn8CGRwuGjlmFtlSRdISp6mcqZxl+R CMfFLn+H5a49i3lUP+CnL2lxtAookBtsRuGGbTt+RkkPNCzaeTp76msfZ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAGW2MFGtJXG8/2dsb2JhbABEwjN7FnOCHwEBAQMBeQULAgEIGCcHMhQRAgQOBYgNBsEXjU6BEzMHgl9hA4g1ik2DQZBrgwiBagEeBg
X-IronPort-AV: E=Sophos;i="4.84,761,1355097600"; d="scan'208";a="182686172"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-3.cisco.com with ESMTP; 01 Mar 2013 14:13:27 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r21EDRxq015347 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Mar 2013 14:13:27 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 08:13:27 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: Ac4To7U7cr4L60i/Ykinr5uevMfmMQATmaFQABQKCgAAfc7GkAAK4lGQABQ/RYAAAKQQAP//nLbT
Date: Fri, 1 Mar 2013 14:13:26 +0000
Message-ID: <12342447-2880-4A53-AADB-5086FF5C2950@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com>, <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 14:13:29 -0000

I would prefer the failed clients be listed.

Sent from my iPad

On Mar 1, 2013, at 9:08 AM, "mohamed.boucadair@orange.com" <mohamed.boucada=
ir@orange.com> wrote:

> Hi Ted,
>=20
> Please see inline.
>=20
> Cheers,
> Med=20
>=20
>> -----Message d'origine-----
>> De : Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
>> Envoy=E9 : vendredi 1 mars 2013 14:50
>> =C0 : BOUCADAIR Mohamed OLNC/OLN
>> Cc : Bernie Volz (volz); Tomek Mrugalski; dhcwg@ietf.org
>> Objet : Re: [dhcwg] Reminder - WGLC:=20
>> draft-ietf-dhc-triggered-reconfigure-03
>>=20
>> On Mar 1, 2013, at 5:24 AM, mohamed.boucadair@orange.com wrote:
>>>  o  If the request includes several Client Identifier
>> options but the
>>>     server won't issue reconfigure requests to all of them,
>> the server
>>>     MUST include in Reconfigure-Ack a Status Code Option
>>>     indicating "Success" but in the meantime it MUST copy back the
>>>     list of Client Identifier Options pointing to clients for which
>>>     the server won't issue a Reconfigure message.
>>=20
>> I'm uncomfortable with the number of conditionals in this that=20
>> seem unnecessary.   How about this:
>>=20
>> If the server is able to issue one or more Reconfigure=20
>> messages to the clients identified in the Reconfigure-Request,=20
>> the server MUST return a Status Code option indicating=20
>> "success."   In addition, the server MUST include a list of=20
>> all the Client-Identifier options of the clients to which=20
>> Reconfigure messages were successfully sent.
>=20
> Med: Only clients for which reconfigure won't be sent are returned in the=
 response and also I would change "Reconfigure messages were successfully s=
ent" to "Reconfigure messages will be sent". Apart from that, I'm fine with=
 the proposed wording.
>=20
>>=20
>> This points out two issues that I think you should consider:
>>=20
>> 1. What result code does the server return if zero of the=20
>> listed clients could receive a Reconfigure?
>=20
> Med: If there is no error to handle the request (e.g., malformed request)=
 or there is no administrative policy which disallow reconfigure-request, t=
hen a "success" is returned with the list of ALL clients. Else, an error co=
de is sent back. The order proposed by Bernie will make this more clear IMH=
O.
>=20
>> 2. Is this really even a good idea?   Now the DHCP server is=20
>> holding off on sending the acknowledgement until all the=20
>> reconfigures have been sent; is that in fact what you want?
>=20
> Med: No, the server should not hold reconfigure-ack. The reconfigure-ack =
is sent back once the server validates the requests and concludes it can ge=
nerate a reconfigure or not. For rate-limit considerations, the actual send=
ing of the corresponding reconfigure messages will be delayed, but not the =
reconfigure-ack.
>=20
>> It's fine if it is, but I thought I'd ask the question.   You=20
>> probably already answered it elsewhere in the draft, but I=20
>> haven't read it in a while. :(
>=20
> Med: This text is in the draft to explain the rationale:=20
>=20
>   The support of Reconfigure-Ack simplifies the retransmission
>   procedure of the relay as it provides an explicit indication from the
>   server.  An alternative approach is the relay monitors Reconfigure
>   messages received from the server to conclude whether Reconfigure-
>   Request was successfully handled or not.  Nevertheless, this implicit
>   approach may fail to achieve its goals in some cases: e.g., the
>   server accepts the request but it delays to generate the
>   corresponding Reconfigure messages due to its rate-limiting policies,
>   the request was partially failed for some clients, etc.=20
>=20
>>=20

From mohamed.boucadair@orange.com  Fri Mar  1 06:17:35 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8469D21E80D3 for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level: 
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sazy3INgxGyK for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:17:35 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id B157B21E809F for <dhcwg@ietf.org>; Fri,  1 Mar 2013 06:17:34 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 03A483B4530; Fri,  1 Mar 2013 15:17:34 +0100 (CET)
Received: from PUEXCH21.nanterre.francetelecom.fr (unknown [10.101.44.28]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id CE6CA4C06E; Fri,  1 Mar 2013 15:17:33 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH21.nanterre.francetelecom.fr ([10.101.44.28]) with mapi; Fri, 1 Mar 2013 15:17:33 +0100
From: <mohamed.boucadair@orange.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Date: Fri, 1 Mar 2013 15:17:33 +0100
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: AQHOE6O0r+FJTNnUlkKnhUGkzSCfKJiMZ76AgAAXCQCABFkeAIAAVLqAgAA5qgD//3qyIIAABilg
Message-ID: <94C682931C08B048B7A8645303FDC9F36EB47D7AF6@PUEXCB1B.nanterre.francetelecom.fr>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com> 
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.19.124517
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 14:17:35 -0000

=20
One correction inline.

Cheers,
Med

>-----Message d'origine-----
>De : BOUCADAIR Mohamed OLNC/OLN=20
>Envoy=E9 : vendredi 1 mars 2013 15:09
>=C0 : 'Ted Lemon'
>Cc : Bernie Volz (volz); Tomek Mrugalski; dhcwg@ietf.org
>Objet : RE: [dhcwg] Reminder - WGLC:=20
>draft-ietf-dhc-triggered-reconfigure-03
>
>Hi Ted,
>
>Please see inline.
>
>Cheers,
>Med=20
>
>>-----Message d'origine-----
>>De : Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
>>Envoy=E9 : vendredi 1 mars 2013 14:50
>>=C0 : BOUCADAIR Mohamed OLNC/OLN
>>Cc : Bernie Volz (volz); Tomek Mrugalski; dhcwg@ietf.org
>>Objet : Re: [dhcwg] Reminder - WGLC:=20
>>draft-ietf-dhc-triggered-reconfigure-03
>>
>>On Mar 1, 2013, at 5:24 AM, mohamed.boucadair@orange.com wrote:
>>>   o  If the request includes several Client Identifier=20
>>options but the
>>>      server won't issue reconfigure requests to all of them,=20
>>the server
>>>      MUST include in Reconfigure-Ack a Status Code Option
>>>      indicating "Success" but in the meantime it MUST copy back the
>>>      list of Client Identifier Options pointing to clients for which
>>>      the server won't issue a Reconfigure message.
>>
>>I'm uncomfortable with the number of conditionals in this that=20
>>seem unnecessary.   How about this:
>>
>>If the server is able to issue one or more Reconfigure=20
>>messages to the clients identified in the Reconfigure-Request,=20
>>the server MUST return a Status Code option indicating=20
>>"success."   In addition, the server MUST include a list of=20
>>all the Client-Identifier options of the clients to which=20
>>Reconfigure messages were successfully sent.
>
>Med: Only clients for which reconfigure won't be sent are=20
>returned in the response and also I would change "Reconfigure=20
>messages were successfully sent" to "Reconfigure messages will=20
>be sent". Apart from that, I'm fine with the proposed wording.
>

Med: I wanted to say: "Reconfigure messages were successfully sent" to be c=
hanged to "Reconfigure messages won't be sent"=

From Ted.Lemon@nominum.com  Fri Mar  1 06:20:26 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 395DD21F8E7A for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:20:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.58
X-Spam-Level: 
X-Spam-Status: No, score=-106.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSClXadhvUlr for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:20:25 -0800 (PST)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id D077221F900E for <dhcwg@ietf.org>; Fri,  1 Mar 2013 06:20:06 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUTC5FpM96kUQfeWVrmey4YP+A/yFH4bb@postini.com; Fri, 01 Mar 2013 06:20:06 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3C87D1B8310 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 06:20:06 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 35E68190043; Fri,  1 Mar 2013 06:20:06 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 06:20:00 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: AQHOE6O0r+FJTNnUlkKnhUGkzSCfKJiMZ76AgAAXCQCABFkeAIAAVLqAgAA5qgD//3qyIIAAjY+A
Date: Fri, 1 Mar 2013 14:20:00 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474A88F1@mbx-01.win.nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com> <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E7DD531B5F3C0C428B61BE7B0EDEAE39@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 14:20:26 -0000

On Mar 1, 2013, at 9:08 AM, mohamed.boucadair@orange.com wrote:
>> If the server is able to issue one or more Reconfigure=20
>> messages to the clients identified in the Reconfigure-Request,=20
>> the server MUST return a Status Code option indicating=20
>> "success."   In addition, the server MUST include a list of=20
>> all the Client-Identifier options of the clients to which=20
>> Reconfigure messages were successfully sent.
>=20
> Med: Only clients for which reconfigure won't be sent are returned in the=
 response and also I would change "Reconfigure messages were successfully s=
ent" to "Reconfigure messages will be sent". Apart from that, I'm fine with=
 the proposed wording.

Okay, so the language ought to look like this?

If the reconfigure request is successfully validated, the server MUST retur=
n a Status Code option indicating "success."   In addition, the server MUST=
 include a list of=20
all the Client-Identifier options of the clients to which=20
Reconfigure messages will not be sent.   Note that this means that "success=
" will be returned even if none of the clients are able to receive Reconfig=
ure messages.


From volz@cisco.com  Fri Mar  1 06:38:56 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E03E221E80D3 for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.544
X-Spam-Level: 
X-Spam-Status: No, score=-10.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9l-sjZ0A4Czd for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:38:56 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 63A1D21E8091 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 06:38:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1455; q=dns/txt; s=iport; t=1362148736; x=1363358336; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=MMAkjkZxmVFBjubaLKUylSFUQBi5KdGO/Qp7F9Gi+HY=; b=LGKu4deOj7ZOueVMyJ0sHn1YrUztmAGqbjxiaCNLgbB+7L7/JZOFd3Sj dw/881gSnK/gqYgJIjrfxjEYUbXHmLj9x10WBOdGNRDEGoQgktuQ3y5et jC2lbzkmq8PvYEXStf6u2QaepZVc0v3h45pxrThS7Ds16uu46MUfvYYEg A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAP+7MFGtJXHA/2dsb2JhbABEwjN7FnOCHwEBAQMBOj8FCwIBCBgeEDIlAgQOBYgNBsEjjmEzB4JfYQOWQ5BrgwiBayQ
X-IronPort-AV: E=Sophos;i="4.84,761,1355097600"; d="scan'208";a="182448696"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 01 Mar 2013 14:38:53 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r21Ecruf027464 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Mar 2013 14:38:53 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 08:38:53 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: Ac4To7U7cr4L60i/Ykinr5uevMfmMQATmaFQABQKCgAAfc7GkAAK4lGQABQ/RYAAAKQQAAAAZCMA//+gsGM=
Date: Fri, 1 Mar 2013 14:38:52 +0000
Message-ID: <E9CAEEB7-4C9C-4BE5-B74B-CA3341E1364F@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com> <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>, <8D23D4052ABE7A4490E77B1A012B6307474A88F1@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307474A88F1@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 14:38:57 -0000

Yes that looks good with one minor edit:

> none of the clients are able to [be sent] Reconfigure messages.

The server has no idea whether clients are able to receive them.

On Mar 1, 2013, at 9:20 AM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:

> On Mar 1, 2013, at 9:08 AM, mohamed.boucadair@orange.com wrote:
>>> If the server is able to issue one or more Reconfigure=20
>>> messages to the clients identified in the Reconfigure-Request,=20
>>> the server MUST return a Status Code option indicating=20
>>> "success."   In addition, the server MUST include a list of=20
>>> all the Client-Identifier options of the clients to which=20
>>> Reconfigure messages were successfully sent.
>>=20
>> Med: Only clients for which reconfigure won't be sent are returned in th=
e response and also I would change "Reconfigure messages were successfully =
sent" to "Reconfigure messages will be sent". Apart from that, I'm fine wit=
h the proposed wording.
>=20
> Okay, so the language ought to look like this?
>=20
> If the reconfigure request is successfully validated, the server MUST ret=
urn a Status Code option indicating "success."   In addition, the server MU=
ST include a list of=20
> all the Client-Identifier options of the clients to which=20
> Reconfigure messages will not be sent.   Note that this means that "succe=
ss" will be returned even if none of the clients are able to receive Reconf=
igure messages.
>=20

From Ted.Lemon@nominum.com  Fri Mar  1 06:46:49 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6CCC21E8091 for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:46:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.581
X-Spam-Level: 
X-Spam-Status: No, score=-106.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ivXoBZnzlF9D for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 06:46:49 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 27A1C21E8064 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 06:46:49 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUTC/Wf5yDv5aLFqBDzvIeS/1CFS6t7Um@postini.com; Fri, 01 Mar 2013 06:46:49 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BE4C21B8394 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 06:46:48 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B4726190043; Fri,  1 Mar 2013 06:46:48 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 06:46:48 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: AQHOE6O0r+FJTNnUlkKnhUGkzSCfKJiMZ76AgAAXCQCABFkeAIAAVLqAgAA5qgD//3qyIIAAjY+AgAAFRwCAAAI3AA==
Date: Fri, 1 Mar 2013 14:46:48 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474A8ACE@mbx-01.win.nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com> <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>, <8D23D4052ABE7A4490E77B1A012B6307474A88F1@mbx-01.win.nominum.com> <E9CAEEB7-4C9C-4BE5-B74B-CA3341E1364F@cisco.com>
In-Reply-To: <E9CAEEB7-4C9C-4BE5-B74B-CA3341E1364F@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <9FA236C47B75854ABA779952F29EEB7D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 14:46:49 -0000

On Mar 1, 2013, at 9:38 AM, "Bernie Volz (volz)" <volz@cisco.com>
 wrote:
> The server has no idea whether clients are able to receive them.

Not true=97clients indicate if they are willing to be reconfigured.   That'=
s what I meant with this bit; maybe the language could be clearer.


From volz@cisco.com  Fri Mar  1 07:31:42 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D94121E8064 for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 07:31:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.524
X-Spam-Level: 
X-Spam-Status: No, score=-10.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNA-QVFJMHWT for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 07:31:41 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 9917921E8051 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 07:31:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2290; q=dns/txt; s=iport; t=1362151901; x=1363361501; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=3o12KRQLRVsotK/H+Publ4g5phdLDw2FVZPX24oYXvg=; b=JibzeO3ZDYo/Nzlb404xc7QlT8UzDgY1WUDpHw2/iKYRUBLnDoDOwWly k4IJ8+W/DotNiZTSfaMtQLqZjaQfH3v2NaZoDUg6JKgoxedBqm73LqMCW AQxsUcu4Rl1jge+sCQASYlH/BLNAsbDOO6fM61fHfjMEFNNEYjoTSRC4v I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFANbIMFGtJV2Z/2dsb2JhbABEwjN9FnOCHwEBAQQ6PwwEAgEIEQQBAQEKFAkHMhQJCAIEDgUIiAvBG45jJgsHBoJZYQOnLoMIgWkHNw
X-IronPort-AV: E=Sophos;i="4.84,761,1355097600"; d="scan'208";a="182726349"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP; 01 Mar 2013 15:31:40 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r21FVeUv031629 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Mar 2013 15:31:40 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 09:31:40 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: Ac4To7U7cr4L60i/Ykinr5uevMfmMQATmaFQABQKCgAAfc7GkAAK4lGQABQ/RYAAAKQQAAAAZCMA//+gsGOAAGbMAIAAXOtA
Date: Fri, 1 Mar 2013 15:31:39 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1848815B@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com> <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>, <8D23D4052ABE7A4490E77B1A012B6307474A88F1@mbx-01.win.nominum.com> <E9CAEEB7-4C9C-4BE5-B74B-CA3341E1364F@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307474A8ACE@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307474A8ACE@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.246.27]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 15:31:42 -0000

That is my point about sending. That is the clearer language. Note that yes=
 that isn't 100% clear because a send can fail (destination unreachable, et=
c.) but the intent here was that the server has attempted to initiate the R=
econfigure, not that the reconfigure was not possible - reconfigure not neg=
otiated or the client no longer has any bindings.

----

We might have to look at clarifying one other issue ... if the server relay=
s the Reconfigure, does it use the relay that sent the Reconfigure-Request =
or does it use what it has stored about the client (which could be a differ=
ent relay - perhaps the relays have a high-availability (HA) feature and th=
e relay that was last used by the client may not be the one sending the Rec=
onfigure). Note that on a server that allows an administrator to request a =
Reconfigure or generates one automatically based on some configuration chan=
ge, it would only have the stored information.

The text currently reads:

  Then, the server MUST follow the procedure defined in Section 19.1 of
   [RFC3315] to construct a Reconfigure message.  This Reconfigure
   message may be sent directly to the DHCPv6 client or to a relay agent
   [RFC3315].

Note that it says "a relay agent", which is ambiguous. Perhaps that was on =
purpose?

I suppose if the relays really have some HA feature, either would be OK and=
 it would be up to the relays to deal with it?

---

And, I might as well ask now whether to rename RECONFIGURE-ACK to RECONFIGU=
RE-REPLY. ACK is more DHCPv4 terminology :) It is just a name so no big dea=
l either way, but just thought I'd mention it now just so it is thought abo=
ut.

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Friday, March 01, 2013 9:47 AM
To: Bernie Volz (volz)
Cc: mohamed.boucadair@orange.com; Tomek Mrugalski; dhcwg@ietf.org
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-=
03

On Mar 1, 2013, at 9:38 AM, "Bernie Volz (volz)" <volz@cisco.com>
 wrote:
> The server has no idea whether clients are able to receive them.

Not true-clients indicate if they are willing to be reconfigured.   That's =
what I meant with this bit; maybe the language could be clearer.


From Ted.Lemon@nominum.com  Fri Mar  1 10:41:24 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D63CD21E803F for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 10:41:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.581
X-Spam-Level: 
X-Spam-Status: No, score=-106.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TLr6sAtGSqBi for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 10:41:24 -0800 (PST)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 458A521E8047 for <dhcwg@ietf.org>; Fri,  1 Mar 2013 10:41:24 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUTD2VDGBbMQ8SbZomf6hnE/1r7tvF2c7@postini.com; Fri, 01 Mar 2013 10:41:24 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D7B9A10804E for <dhcwg@ietf.org>; Fri,  1 Mar 2013 10:41:23 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CBB70190043; Fri,  1 Mar 2013 10:41:23 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 10:41:23 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: AQHOE6O0r+FJTNnUlkKnhUGkzSCfKJiMZ76AgAAXCQCABFkeAIAAVLqAgAA5qgD//3qyIIAAjY+AgAAFRwCAAAI3AIAADIiA//+u5/U=
Date: Fri, 1 Mar 2013 18:41:23 +0000
Message-ID: <7660BFA6-F797-4C7D-B1A5-7B1EE2DFFDC8@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com> <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>, <8D23D4052ABE7A4490E77B1A012B6307474A88F1@mbx-01.win.nominum.com> <E9CAEEB7-4C9C-4BE5-B74B-CA3341E1364F@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307474A8ACE@mbx-01.win.nominum.com>, <489D13FBFA9B3E41812EA89F188F018E1848815B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1848815B@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 18:41:25 -0000

On Mar 1, 2013, at 10:31 AM, "Bernie Volz (volz)" <volz@cisco.com> wrote:
> That is my point about sending. That is the clearer language. Note that y=
es that isn't 100% clear because a send can fail (destination unreachable, =
etc.) but the intent here was that the server has attempted to initiate the=
 Reconfigure, not that the reconfigure was not possible - reconfigure not n=
egotiated or the client no longer has any bindings.

Okay, that's a good distinction to make.  Thanks!=

From volz@cisco.com  Fri Mar  1 20:18:23 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1250221E80FE for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 20:18:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.547
X-Spam-Level: 
X-Spam-Status: No, score=-10.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OVFOYQlKssYN for <dhcwg@ietfa.amsl.com>; Fri,  1 Mar 2013 20:18:21 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id A6C5921E80FB for <dhcwg@ietf.org>; Fri,  1 Mar 2013 20:18:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1029; q=dns/txt; s=iport; t=1362197901; x=1363407501; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=0uphlXOXunwQdmEiz+fw2ni7+9gkLVdb+fo0OL8b4rs=; b=JwitGd52xjj8mzXoiqlxdtfKvY2KAFS0GoKvZn+q+kEivw2LcjcpzWo4 MOA3dxxrgVSZfGfZifS1W+bp6FNhPqVyXPJ+osrZ2wy1U0WBtuVi60oXS 8HZ151W/xXcfV3lL6lp5QbRmIeb5qFIvtEJ7gRMEkk1Tluo1GVQepJYSa U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAE19MVGtJV2c/2dsb2JhbABEwkSBABZzgh8BAQEEOj8MBgEIEQQBAQsLCQk5FAkJAQQOBQiIC8BmjmwmCw0EglVhA6cugwiCJw
X-IronPort-AV: E=Sophos;i="4.84,766,1355097600"; d="scan'208";a="182693881"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 02 Mar 2013 04:18:02 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r224I2xh021214 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 2 Mar 2013 04:18:02 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 22:18:02 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: Ac4W/F3RqV2HsB64TjKx+PR9PhZ9Bw==
Date: Sat, 2 Mar 2013 04:18:01 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1848907C@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.252.143]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 02 Mar 2013 04:18:23 -0000

As Feb 28th has come and gone, I wanted to update folks on the last call st=
atus.

The chairs believe this document, draft-ietf-dhc-triggered-reconfigure-03, =
has WG consensus. However, as there were a fair number of minor clarificati=
ons with a few still outstanding, the chairs will make a final determinatio=
n after these issues are resolved and an updated draft is published.

Thanks.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of T=
ed Lemon
Sent: Thursday, February 14, 2013 11:16 AM
To: dhcwg@ietf.org WG
Subject: [dhcwg] WGLC: draft-ietf-dhc-triggered-reconfigure-03

Med has updated the draft to account for comments made during the working g=
roup last call.   This is a new WGLC: if you had comments on the previous d=
raft, please review the changes.   If you are in favor of advancing the dra=
ft, please say so.   If you oppose advancing the draft, please say so.

We will determine consensus on February 28.

Thanks!


From volz@cisco.com  Sun Mar  3 18:02:36 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E96F721F8756 for <dhcwg@ietfa.amsl.com>; Sun,  3 Mar 2013 18:02:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5VTVza-1iUMU for <dhcwg@ietfa.amsl.com>; Sun,  3 Mar 2013 18:02:32 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 16C0D21F8733 for <dhcwg@ietf.org>; Sun,  3 Mar 2013 18:02:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10629; q=dns/txt; s=iport; t=1362362551; x=1363572151; h=from:to:subject:date:message-id:mime-version; bh=NbK77fyCVHN+r9ndFUfn1LsDm/enRyW+qn9FUiW3tcU=; b=k1aHEdHigQD8c+bGycxLwZziNbc0FjfqIM32Kexm+Sq7RgfsRrqmHl0n /bsIgGoywjxQ96wUPXISLS4Ox8H+fhtr8wdRXC6O4JDyyiyZhry36MCQX 1w2pY9fgkYgsMsL7UxxlOUsYjmYb9/ylf3EWugIe6SQkbP6pZJzG3Xk8p M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAEv/M1GtJV2d/2dsb2JhbABFgkPAB3wWc4IfAQEBBC1eARkEAQELHTkUCQkBBBMIiAsMpwOgBASOXCYHCoJgYQOnMoMIgic
X-IronPort-AV: E=Sophos;i="4.84,776,1355097600";  d="scan'208,217";a="183287903"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 04 Mar 2013 02:02:25 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r2422Ppw015684 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Mon, 4 Mar 2013 02:02:25 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Sun, 3 Mar 2013 20:02:25 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: IETF-86 (Orlando) DHC WG Agenda & Slides
Thread-Index: Ac4YfE5jk7XBs/ZpTm6qjYy599EVrg==
Date: Mon, 4 Mar 2013 02:02:24 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1848B61C@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.132]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1848B61Cxmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] IETF-86 (Orlando) DHC WG Agenda & Slides
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 02:02:37 -0000

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

Hi:

I posted a revised agenda.  https://datatracker.ietf.org/meeting/86/agenda/=
dhc/

Please also note for those with presentation material (slides), please send=
 them to be so that they can be uploaded well before the DHC WG meeting. PD=
F or PPT/PPTX are recommended for slides.


-          Bernie

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of B=
ernie Volz (volz)
Sent: Thursday, February 28, 2013 12:35 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Draft IETF-86 (Orlando) agenda posted

A draft of the IETF-86 DHC WG meeting in Orlando has been posted:

https://datatracker.ietf.org/meeting/86/agenda/dhc/

If you requested time, please confirm that it is on the agenda! If not, ple=
ase let us know (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org=
>).

If you haven't requested time and want a slot, please send a request ASAP (=
to dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org>).


-          Bernie

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:241329739;
	mso-list-type:hybrid;
	mso-list-template-ids:1889167436 1740295406 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;}
@list l1
	{mso-list-id:1817185831;
	mso-list-type:hybrid;
	mso-list-template-ids:1329870914 1347600690 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:4;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I posted a revised age=
nda.&nbsp; </span>
<a href=3D"https://datatracker.ietf.org/meeting/86/agenda/dhc/">https://dat=
atracker.ietf.org/meeting/86/agenda/dhc/</a><o:p></o:p></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">Please also note for t=
hose with presentation material (slides), please send them to be so that th=
ey can be uploaded well before the DHC WG meeting. PDF or PPT/PPTX are reco=
mmended for slides.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg-bo=
unces@ietf.org [mailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Thursday, February 28, 2013 12:35 AM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] Draft IETF-86 (Orlando) agenda posted<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">A draft of the IETF-86 DHC WG meeting in Orlando has=
 been posted:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://datatracker.ietf.org/meeting/86/a=
genda/dhc/">https://datatracker.ietf.org/meeting/86/agenda/dhc/</a><o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If you requested time, please confirm that it is on =
the agenda! If not, please let us know (<a href=3D"mailto:dhc-chairs@tools.=
ietf.org">dhc-chairs@tools.ietf.org</a>).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If you haven&#8217;t requested time and want a slot,=
 please send a request ASAP (to
<a href=3D"mailto:dhc-chairs@tools.ietf.org">dhc-chairs@tools.ietf.org</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]>Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1848B61Cxmbrcdx04ciscoc_--

From volz@cisco.com  Sun Mar  3 19:10:23 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0DA421F86CA for <dhcwg@ietfa.amsl.com>; Sun,  3 Mar 2013 19:10:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z5URo0B+ndf7 for <dhcwg@ietfa.amsl.com>; Sun,  3 Mar 2013 19:10:19 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC8521F8732 for <dhcwg@ietf.org>; Sun,  3 Mar 2013 19:10:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6622; q=dns/txt; s=iport; t=1362366617; x=1363576217; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=HqpbBdBvDBSEwHJRS9NYmc2+VQ7f6B7zCqYNzcrpqjc=; b=Or93NicoS2jeiSCapjg0Ohsisms4fS9WVgzSuvDo39NRYvsc33RWZ24z OlEM1Ejnpv26aUb3fK0D0GwbswBBPiCsNIJoiWsIeYIrDr6KtRwOEjMiT n+13O3Y8BM90l0FlTIMveuQL89mlOhDk0z9HtB74YzFse1hKAdYxii6Na g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAFkPNFGtJXG+/2dsb2JhbABFgkPACXwWc4IgAQECAgEBASpBCxACAQg1CgchBgsUEQEBBA4FCRaHYgMPDL1gDYknjEWCRAQHgl9hA5RngV+LVIUYgwg
X-IronPort-AV: E=Sophos;i="4.84,777,1355097600";  d="scan'208,217";a="183252631"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 04 Mar 2013 03:10:17 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r243AGV5031565 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 4 Mar 2013 03:10:16 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Sun, 3 Mar 2013 21:10:16 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
Thread-Topic: [dhcwg] Request to make WGLC on draft-ietf-dhc-dhcpv6-prefix-pool-opt-02
Thread-Index: Ac4VCkdan65c4meqQDW2z402Hv1U+wDe4RBC
Date: Mon, 4 Mar 2013 03:10:16 +0000
Message-ID: <0F93785F-A82B-4BBA-AFC9-4C83AE547D8D@cisco.com>
References: <512e3901.6300450a.1da0.ffffa48a@mx.google.com>
In-Reply-To: <512e3901.6300450a.1da0.ffffa48a@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_0F93785FA82B4BBAAFC94C83AE547D8Dciscocom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, Dhc Chairs <dhc-chairs@tools.ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Request to make WGLC on	draft-ietf-dhc-dhcpv6-prefix-pool-opt-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 03:10:23 -0000

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

We will start a WGLC a short time after the Orlando IETF. I'd like to get f=
olks that plan to attend to focus on the documents on the agenda.

- Bernie

On Feb 27, 2013, at 11:49 AM, "Leaf Yeh" <leaf.yeh.sdo@gmail.com<mailto:lea=
f.yeh.sdo@gmail.com>> wrote:

Dear Chairs,

The authors of the draft (OPTION_PREFIX_POOL) request to make WGLC on draft=
-ietf-dhc-dhcpv6-prefix-pool-opt-02<https://datatracker.ietf.org/doc/draft-=
ietf-dhc-dhcpv6-prefix-pool-opt/>. We think it is ready to collect more tho=
rough reviews and comments on it.


Best Regards,
Leaf


PS. The following slides are for the reference to the DHC folks:

http://www.ietf.org/proceedings/85/slides/slides-85-dhc-6.pdf

http://www.ietf.org/proceedings/84/slides/slides-84-dhc-10.pdf

http://www.ietf.org/proceedings/81/slides/dhc-2.pdf

http://www.ietf.org/proceedings/80/slides/dhc-3.pdf

http://www.ietf.org/proceedings/79/slides/dhc-3.pdf
We won=92t send more slides to the WG for IETF86.

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

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>We will start a WGLC a short time after the Orlando IETF. I'd like to =
get folks that plan to attend to focus on the documents on the agenda.&nbsp=
;<br>
<br>
- Bernie</div>
<div><br>
On Feb 27, 2013, at 11:49 AM, &quot;Leaf Yeh&quot; &lt;<a href=3D"mailto:le=
af.yeh.sdo@gmail.com">leaf.yeh.sdo@gmail.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" 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;
	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:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
.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]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Dear Chairs,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The authors of the draft (OPTIO=
N_PREFIX_POOL) request to make WGLC on
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-prefix-po=
ol-opt/">
<span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-se=
rif&quot;;background:white">draft-ietf-dhc-dhcpv6-prefix-pool-opt-02</span>=
</a>. We think it is ready to collect more thorough reviews and comments on=
 it.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best Regards,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Leaf<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">PS. The following slides are fo=
r the reference to the DHC folks:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><a href=3D"http://www.ietf.o=
rg/proceedings/85/slides/slides-85-dhc-6.pdf">http://www.ietf.org/proceedin=
gs/85/slides/slides-85-dhc-6.pdf</a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><a href=3D"http://www.ietf.o=
rg/proceedings/84/slides/slides-84-dhc-10.pdf">http://www.ietf.org/proceedi=
ngs/84/slides/slides-84-dhc-10.pdf</a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><a href=3D"http://www.ietf.o=
rg/proceedings/81/slides/dhc-2.pdf">http://www.ietf.org/proceedings/81/slid=
es/dhc-2.pdf</a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><a href=3D"http://www.ietf.o=
rg/proceedings/80/slides/dhc-3.pdf">http://www.ietf.org/proceedings/80/slid=
es/dhc-3.pdf</a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><a href=3D"http://www.ietf.o=
rg/proceedings/79/slides/dhc-3.pdf">http://www.ietf.org/proceedings/79/slid=
es/dhc-3.pdf</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We won=92t send more slides to =
the WG for IETF86.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>dhcwg mailing list</span><br>
<span><a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg">https://www.i=
etf.org/mailman/listinfo/dhcwg</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_0F93785FA82B4BBAAFC94C83AE547D8Dciscocom_--

From otroan@employees.org  Mon Mar  4 00:01:41 2013
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C954321F889C for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 00:01:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wgwMEGTk-yNi for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 00:01:41 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id 76D3A21F8899 for <dhcwg@ietf.org>; Mon,  4 Mar 2013 00:01:41 -0800 (PST)
Received: from dhcp-lys01-vla250-10-147-112-117.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 5BB83C2CB; Mon,  4 Mar 2013 00:01:40 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1848B61C@xmb-rcd-x04.cisco.com>
Date: Mon, 4 Mar 2013 09:01:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7051D890-1D9F-41AE-BEE0-68DFB6E0F5A4@employees.org>
References: <489D13FBFA9B3E41812EA89F188F018E1848B61C@xmb-rcd-x04.cisco.com>
To: Bernie Volz (volz) <volz@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "softwire-chairs@tools.ietf.org Chairs" <softwire-chairs@tools.ietf.org>
Subject: Re: [dhcwg] IETF-86 (Orlando) DHC WG Agenda & Slides
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 08:01:41 -0000

> I posted a revised agenda.  =
https://datatracker.ietf.org/meeting/86/agenda/dhc/
> =20
> Please also note for those with presentation material (slides), please =
send them to be so that they can be uploaded well before the DHC WG =
meeting. PDF or PPT/PPTX are recommended for slides.

if I'm allowed to start bashing the agenda.
a "comparison of port set algorithms", isn't that squarely within =
softwire's domain?
defining the option format certainly, but choosing algorithm?

Draft:     draft-ietf-softwire-map-04
           draft-sun-dhc-port-set-option-00
Title:     Comparison of IPv4 port set algorithms
Presenter: Qi Sun
URL:       http://tools.ietf.org/html/draft-ietf-softwire-map-04
           http://tools.ietf.org/html/draft-sun-dhc-port-set-option-00
Slot:      5 min

cheers,
Ole=

From sunqi.thu@gmail.com  Mon Mar  4 01:38:12 2013
Return-Path: <sunqi.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2B2721F886E for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 01:38:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFt1Ch94xwdk for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 01:38:08 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4892D21F871E for <dhcwg@ietf.org>; Mon,  4 Mar 2013 01:38:08 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so2463771dae.17 for <dhcwg@ietf.org>; Mon, 04 Mar 2013 01:38:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:message-id:references:to:x-mailer; bh=zp9zVHENGF88H+dh73GUn1afzt9Qg2HAIDSKO15rBxI=; b=D6iLfm24xVFv5mumoaZ7xXBQJX6Ni8bHITtLMOwy49MuTO4mRguyxND1gK0NHpzd7m zMkGHIjOZMvuv5eljq0JZvEEEdmNFISGy4tY1wjaa4UTdH53ZVFoFhu3wnUTcb2ZHAtE GhSsrNbof8ybMuohTYkJEzx4Unu/amNAs8fTVjX1cTyT1WLCTsHvJbctzOUI2Z39+yyb r8aicjToJW/QFnJePXoz9gBvHaM7+TYrpH5WqdSX2O9YgHPGWzLpX7J0+NHTg70lyAHN ysvFk5NEqaBZQg3ZIzn/zFVL67aRsl7jfXVwTaJ1nh3gavdNXKvOs653gWHH6bTLiRXJ +aBA==
X-Received: by 10.68.227.129 with SMTP id sa1mr27115422pbc.107.1362389888048;  Mon, 04 Mar 2013 01:38:08 -0800 (PST)
Received: from [192.168.1.170] ([166.111.68.233]) by mx.google.com with ESMTPS id kl4sm21743816pbc.31.2013.03.04.01.38.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Mar 2013 01:38:06 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-6--316895931
From: Qi Sun <sunqi.thu@gmail.com>
In-Reply-To: <7051D890-1D9F-41AE-BEE0-68DFB6E0F5A4@employees.org>
Date: Mon, 4 Mar 2013 17:37:56 +0800
Message-Id: <F33A58A1-F673-42C8-8496-B3F34491311E@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1848B61C@xmb-rcd-x04.cisco.com> <7051D890-1D9F-41AE-BEE0-68DFB6E0F5A4@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, "softwire-chairs@tools.ietf.org Chairs" <softwire-chairs@tools.ietf.org>
Subject: Re: [dhcwg] IETF-86 (Orlando) DHC WG Agenda & Slides
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 09:38:12 -0000

--Apple-Mail-6--316895931
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Dear Chairs & all,

Back in IETF84, the WG consensus was that port-set assignment is an =
extension to DHCP =
(http://www.ietf.org/proceedings/84/minutes/minutes-84-dhc), DHC is the =
right place for the port-set related discussions.=20

In the context of requiring IPv4 address sharing, port-set has become a =
kind of IPv4 address resource to be allocated, which is the work of  DHC =
WG. We need not only to define the option, but also to explain why and =
how we can do this. It's reasonable to get comments from the DHC WG on =
which algorithm can cause less modification to DHCP/the Internet but =
achieve IPv4 address sharing effectively.=20

I think the information is useful for the WG, and more contributions =
from experts here will not do harm to the work.So the presentation is in =
the right place, IMHO.

Best Regards,
Qi Sun


On 2013-3-4, at =E4=B8=8B=E5=8D=884:01, Ole Troan wrote:

>> I posted a revised agenda.  =
https://datatracker.ietf.org/meeting/86/agenda/dhc/
>>=20
>> Please also note for those with presentation material (slides), =
please send them to be so that they can be uploaded well before the DHC =
WG meeting. PDF or PPT/PPTX are recommended for slides.
>=20
> if I'm allowed to start bashing the agenda.
> a "comparison of port set algorithms", isn't that squarely within =
softwire's domain?
> defining the option format certainly, but choosing algorithm?
>=20
> Draft:     draft-ietf-softwire-map-04
>           draft-sun-dhc-port-set-option-00
> Title:     Comparison of IPv4 port set algorithms
> Presenter: Qi Sun
> URL:       http://tools.ietf.org/html/draft-ietf-softwire-map-04
>           http://tools.ietf.org/html/draft-sun-dhc-port-set-option-00
> Slot:      5 min
>=20
> cheers,
> Ole
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


--Apple-Mail-6--316895931
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; color: rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 19px/normal 'Heiti SC Light'; ">Dear Chairs &amp; =
all,</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
19px/normal 'Heiti SC Light'; min-height: 20px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 19px/normal 'Heiti SC =
Light'; ">Back in IETF84, the WG consensus was that port-set assignment =
is an extension to DHCP (<a =
href=3D"http://www.ietf.org/proceedings/84/minutes/minutes-84-dhc">http://=
www.ietf.org/proceedings/84/minutes/minutes-84-dhc</a>), DHC is the =
right place for the port-set related discussions.&nbsp;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 19px/normal 'Heiti SC =
Light'; min-height: 20px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 19px/normal 'Heiti SC Light'; ">In the context of =
requiring IPv4 address sharing, port-set has become a kind of IPv4 =
address resource to be allocated, which is the work of&nbsp; DHC WG. We =
need not only to define the option, but also to explain why and how we =
can do this. It's reasonable to get comments from the DHC WG on which =
algorithm can cause less modification to DHCP/the Internet but achieve =
IPv4 address sharing effectively.&nbsp;</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 19px/normal 'Heiti SC Light'; min-height: 20px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
19px/normal 'Heiti SC Light'; ">I think the information is useful for =
the WG, and more contributions from experts here will not do harm to the =
work.So the presentation is in the right place, IMHO.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 19px/normal 'Heiti SC =
Light'; min-height: 20px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 19px/normal 'Heiti SC Light'; ">Best Regards,</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 19px/normal 'Heiti SC =
Light'; ">Qi Sun</div><br></div></span></div></span></div></span></span>
</div>
<br><div><div>On 2013-3-4, at =E4=B8=8B=E5=8D=884:01, Ole Troan =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><blockquote type=3D"cite">I posted a revised agenda. =
&nbsp;<a =
href=3D"https://datatracker.ietf.org/meeting/86/agenda/dhc/">https://datat=
racker.ietf.org/meeting/86/agenda/dhc/</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Please also =
note for those with presentation material (slides), please send them to =
be so that they can be uploaded well before the DHC WG meeting. PDF or =
PPT/PPTX are recommended for slides.<br></blockquote><br>if I'm allowed =
to start bashing the agenda.<br>a "comparison of port set algorithms", =
isn't that squarely within softwire's domain?<br>defining the option =
format certainly, but choosing algorithm?<br><br>Draft: =
&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-softwire-map-04<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;draft-sun-dhc-=
port-set-option-00<br>Title: &nbsp;&nbsp;&nbsp;&nbsp;Comparison of IPv4 =
port set algorithms<br>Presenter: Qi Sun<br>URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ietf-softwire-map-04">http://tool=
s.ietf.org/html/draft-ietf-softwire-map-04</a><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-sun-dhc-port-set-option-00">http:=
//tools.ietf.org/html/draft-sun-dhc-port-set-option-00</a><br>Slot: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5 =
min<br><br>cheers,<br>Ole<br>_____________________________________________=
__<br>dhcwg mailing list<br><a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/dhcwg<br></div></blockquote></div><br></body></html>=

--Apple-Mail-6--316895931--

From mohamed.boucadair@orange.com  Mon Mar  4 01:42:25 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3087421F88E1 for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 01:42:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.619
X-Spam-Level: *
X-Spam-Status: No, score=1.619 tagged_above=-999 required=5 tests=[AWL=3.867,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oKl68Vg1CEL4 for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 01:42:24 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 6836F21F8881 for <dhcwg@ietf.org>; Mon,  4 Mar 2013 01:42:24 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 68A7C32453F; Mon,  4 Mar 2013 10:42:23 +0100 (CET)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 4B33F27C07F; Mon,  4 Mar 2013 10:42:23 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Mon, 4 Mar 2013 10:42:23 +0100
From: <mohamed.boucadair@orange.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Date: Mon, 4 Mar 2013 10:42:22 +0100
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: Ac4To7U7cr4L60i/Ykinr5uevMfmMQATmaFQABQKCgAAfc7GkAAK4lGQABQ/RYAAAKQQAAAAZCMA//+gsGOAAGbMAIAAXOtA//xhCzA=
Message-ID: <94C682931C08B048B7A8645303FDC9F36EB47D7DE9@PUEXCB1B.nanterre.francetelecom.fr>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com> <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>, <8D23D4052ABE7A4490E77B1A012B6307474A88F1@mbx-01.win.nominum.com> <E9CAEEB7-4C9C-4BE5-B74B-CA3341E1364F@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307474A8ACE@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E1848815B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1848815B@xmb-rcd-x04.cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.4.73320
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 09:42:25 -0000

Hi Bernie,

* I'm OK to rename the message.=20
* The excerpt you mentioned about the server behaviour is just an extract o=
f the server's behaviour as defined in rfc3315; it is there to say the proc=
edure defined in this document does not change that behaviour. Whether the =
reconfigure it is relayed or not is out of scope.=20

Cheers,
Med=20

>-----Message d'origine-----
>De : Bernie Volz (volz) [mailto:volz@cisco.com]=20
>Envoy=E9 : vendredi 1 mars 2013 16:32
>=C0 : Ted Lemon
>Cc : BOUCADAIR Mohamed OLNC/OLN; Tomek Mrugalski; dhcwg@ietf.org
>Objet : RE: [dhcwg] Reminder - WGLC:=20
>draft-ietf-dhc-triggered-reconfigure-03
>
>That is my point about sending. That is the clearer language.=20
>Note that yes that isn't 100% clear because a send can fail=20
>(destination unreachable, etc.) but the intent here was that=20
>the server has attempted to initiate the Reconfigure, not that=20
>the reconfigure was not possible - reconfigure not negotiated=20
>or the client no longer has any bindings.
>
>----
>
>We might have to look at clarifying one other issue ... if the=20
>server relays the Reconfigure, does it use the relay that sent=20
>the Reconfigure-Request or does it use what it has stored=20
>about the client (which could be a different relay - perhaps=20
>the relays have a high-availability (HA) feature and the relay=20
>that was last used by the client may not be the one sending=20
>the Reconfigure). Note that on a server that allows an=20
>administrator to request a Reconfigure or generates one=20
>automatically based on some configuration change, it would=20
>only have the stored information.
>
>The text currently reads:
>
>  Then, the server MUST follow the procedure defined in Section 19.1 of
>   [RFC3315] to construct a Reconfigure message.  This Reconfigure
>   message may be sent directly to the DHCPv6 client or to a=20
>relay agent
>   [RFC3315].
>
>Note that it says "a relay agent", which is ambiguous. Perhaps=20
>that was on purpose?
>
>I suppose if the relays really have some HA feature, either=20
>would be OK and it would be up to the relays to deal with it?
>
>---
>
>And, I might as well ask now whether to rename RECONFIGURE-ACK=20
>to RECONFIGURE-REPLY. ACK is more DHCPv4 terminology :) It is=20
>just a name so no big deal either way, but just thought I'd=20
>mention it now just so it is thought about.
>
>- Bernie
>
>-----Original Message-----
>From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
>Sent: Friday, March 01, 2013 9:47 AM
>To: Bernie Volz (volz)
>Cc: mohamed.boucadair@orange.com; Tomek Mrugalski; dhcwg@ietf.org
>Subject: Re: [dhcwg] Reminder - WGLC:=20
>draft-ietf-dhc-triggered-reconfigure-03
>
>On Mar 1, 2013, at 9:38 AM, "Bernie Volz (volz)" <volz@cisco.com>
> wrote:
>> The server has no idea whether clients are able to receive them.
>
>Not true-clients indicate if they are willing to be=20
>reconfigured.   That's what I meant with this bit; maybe the=20
>language could be clearer.
>
>=

From Ted.Lemon@nominum.com  Mon Mar  4 05:19:48 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9880F21F892B for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 05:19:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KUJqiAP-nD-I for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 05:19:48 -0800 (PST)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD2E21F892A for <dhcwg@ietf.org>; Mon,  4 Mar 2013 05:19:48 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUTSfc/tCXxopFDJ/0kX9Fffhn2SWRwYG@postini.com; Mon, 04 Mar 2013 05:19:48 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B39331B80EA for <dhcwg@ietf.org>; Mon,  4 Mar 2013 05:19:47 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A9080190043; Mon,  4 Mar 2013 05:19:47 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 4 Mar 2013 05:19:35 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<mohamed.boucadair@orange.com> " <mohamed.boucadair@orange.com>
Thread-Topic: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
Thread-Index: AQHOE6O0r+FJTNnUlkKnhUGkzSCfKJiMZ76AgAAXCQCABFkeAIAAVLqAgAA5qgD//3qyIIAAjY+AgAAFRwCAAAI3AIAADIiAgARVaACAADytAA==
Date: Mon, 4 Mar 2013 13:19:34 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474AB9E8@mbx-01.win.nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1847C264@xmb-rcd-x04.cisco.com> <512BDF3E.3030902@gmail.com> <94C682931C08B048B7A8645303FDC9F36EB3C83288@PUEXCB1B.nanterre.francetelecom.fr> <512C94F0.8060106@gmail.com> <489D13FBFA9B3E41812EA89F188F018E18487090@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D79BB@PUEXCB1B.nanterre.francetelecom.fr> <8D23D4052ABE7A4490E77B1A012B6307474A8781@mbx-01.win.nominum.com> <94C682931C08B048B7A8645303FDC9F36EB47D7AE8@PUEXCB1B.nanterre.francetelecom.fr>, <8D23D4052ABE7A4490E77B1A012B6307474A88F1@mbx-01.win.nominum.com> <E9CAEEB7-4C9C-4BE5-B74B-CA3341E1364F@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307474A8ACE@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E1848815B@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EB47D7DE9@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EB47D7DE9@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <FC3303A7F832E7409EE4CFE618FE02A6@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Reminder - WGLC: draft-ietf-dhc-triggered-reconfigure-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 13:19:48 -0000

On Mar 4, 2013, at 4:42 AM, <mohamed.boucadair@orange.com> wrote:
> * The excerpt you mentioned about the server behaviour is just an extract=
 of the server's behaviour as defined in rfc3315; it is there to say the pr=
ocedure defined in this document does not change that behaviour. Whether th=
e reconfigure it is relayed or not is out of scope.=20

There shouldn't ever be text in a draft that reiterates what has already be=
en standardized.   If the text doesn't update RFC3315, you should take it o=
ut.


From volz@cisco.com  Mon Mar  4 06:19:27 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17E8221F893D for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 06:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zEjXFVCprVZ6 for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 06:19:26 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 06BC321F8925 for <dhcwg@ietf.org>; Mon,  4 Mar 2013 06:19:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11693; q=dns/txt; s=iport; t=1362406766; x=1363616366; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Q0U/pBq8GOxu44YOSi2RhRHKmMjZmp8jErCK72/jn0Q=; b=jaE52022rTkL8Vxj0WAdT1ZUZ4FCtO4EzbGfJDEEwgA+YbUoHa+q2W/J UxmLk6DPbzrixKyKWC9eRmao4HzfltPTWOhhzHj1yawH4rfdWzyYrO2V8 yjg3SnEcH7gTKWY+uC6AtNwLOAjLZmtzMLYvywmZujUgy9BJvQrrA1hdo c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AocFABesNFGtJXG//2dsb2JhbABFhlCzUwGIKYEBFnOCIAEBBAEBAR4BSQMLEAIBCCcYAgMCIQYLFBEBAQQOBQmHeAMPDJoomn4BiEANiSeMRYJEBAcJgiE1YQOUZ4FfgR6KNoUYgwg
X-IronPort-AV: E=Sophos;i="4.84,779,1355097600";  d="scan'208,217";a="183501359"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-4.cisco.com with ESMTP; 04 Mar 2013 14:19:25 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r24EJP7P032314 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 4 Mar 2013 14:19:25 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Mon, 4 Mar 2013 08:19:25 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Qi Sun <sunqi.thu@gmail.com>
Thread-Topic: [dhcwg] IETF-86 (Orlando) DHC WG Agenda & Slides
Thread-Index: Ac4YfE5jk7XBs/ZpTm6qjYy599EVrgAZHwmAAANc1wD//+oPFQ==
Date: Mon, 4 Mar 2013 14:19:24 +0000
Message-ID: <9E05FEFB-5DD7-4263-ADBF-4A87FC0D27C2@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1848B61C@xmb-rcd-x04.cisco.com> <7051D890-1D9F-41AE-BEE0-68DFB6E0F5A4@employees.org>, <F33A58A1-F673-42C8-8496-B3F34491311E@gmail.com>
In-Reply-To: <F33A58A1-F673-42C8-8496-B3F34491311E@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_9E05FEFB5DD74263ADBF4A87FC0D27C2ciscocom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "softwire-chairs@tools.ietf.org Chairs" <softwire-chairs@tools.ietf.org>
Subject: Re: [dhcwg] IETF-86 (Orlando) DHC WG Agenda & Slides
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 14:19:27 -0000

--_000_9E05FEFB5DD74263ADBF4A87FC0D27C2ciscocom_
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

I do believe that we should let softwire address the port set algorithm iss=
ue. DHC should focus on the option format and DHC protocol implications.

I wasn't sure at the time this was requested whether this was also a presen=
tation in softwires or not and this was to update the dhc as to the status.=
 And of course just got a title.

I also see that Ted has a 30 min slot in softwire on ipv4 conf over v6 whic=
h is also a topic to be discussed in the DHC WG.

We have a lot of overlap (there's also the sunset4 wg) and working this out=
 is, I believe, a priority for Ted.

- Bernie

On Mar 4, 2013, at 4:38 AM, "Qi Sun" <sunqi.thu@gmail.com<mailto:sunqi.thu@=
gmail.com>> wrote:

Dear Chairs & all,

Back in IETF84, the WG consensus was that port-set assignment is an extensi=
on to DHCP (http://www.ietf.org/proceedings/84/minutes/minutes-84-dhc), DHC=
 is the right place for the port-set related discussions.

In the context of requiring IPv4 address sharing, port-set has become a kin=
d of IPv4 address resource to be allocated, which is the work of  DHC WG. W=
e need not only to define the option, but also to explain why and how we ca=
n do this. It's reasonable to get comments from the DHC WG on which algorit=
hm can cause less modification to DHCP/the Internet but achieve IPv4 addres=
s sharing effectively.

I think the information is useful for the WG, and more contributions from e=
xperts here will not do harm to the work.So the presentation is in the righ=
t place, IMHO.

Best Regards,
Qi Sun


On 2013-3-4, at =1B$B2<8a=1B(B4:01, Ole Troan wrote:

I posted a revised agenda.  https://datatracker.ietf.org/meeting/86/agenda/=
dhc/

Please also note for those with presentation material (slides), please send=
 them to be so that they can be uploaded well before the DHC WG meeting. PD=
F or PPT/PPTX are recommended for slides.

if I'm allowed to start bashing the agenda.
a "comparison of port set algorithms", isn't that squarely within softwire'=
s domain?
defining the option format certainly, but choosing algorithm?

Draft:     draft-ietf-softwire-map-04
          draft-sun-dhc-port-set-option-00
Title:     Comparison of IPv4 port set algorithms
Presenter: Qi Sun
URL:       http://tools.ietf.org/html/draft-ietf-softwire-map-04
          http://tools.ietf.org/html/draft-sun-dhc-port-set-option-00
Slot:      5 min

cheers,
Ole
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg

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

--_000_9E05FEFB5DD74263ADBF4A87FC0D27C2ciscocom_
Content-Type: text/html; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-2022-=
jp">
</head>
<body dir=3D"auto">
<div>I do believe that we should let softwire address the port set algorith=
m issue. DHC should focus on the option format and DHC protocol implication=
s.</div>
<div><br>
</div>
<div>I wasn't sure at the time this was requested whether this was also a p=
resentation in softwires or not and this was to update the dhc as to the st=
atus. And of course just got a title.</div>
<div><br>
</div>
<div>I also see that Ted has a 30 min slot in softwire on ipv4 conf over v6=
 which is also a topic to be discussed in the DHC WG.&nbsp;</div>
<div><br>
</div>
<div>We have a lot of overlap (there's also the sunset4 wg) and working thi=
s out is, I believe, a priority for Ted.&nbsp;<br>
<br>
</div>
<div>- Bernie</div>
<div><br>
On Mar 4, 2013, at 4:38 AM, &quot;Qi Sun&quot; &lt;<a href=3D"mailto:sunqi.=
thu@gmail.com">sunqi.thu@gmail.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div><span class=3D"Apple-style-span" style=3D"border-collapse: separate; c=
olor: rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-varia=
nt: normal; font-weight: normal; letter-spacing: normal; line-height: norma=
l; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; wh=
ite-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-=
spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decoration=
s-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-widt=
h: 0px; font-size: medium; "><span class=3D"Apple-style-span" style=3D"bord=
er-collapse: separate; color: rgb(0, 0, 0); font-family: 'Heiti SC'; font-s=
tyle: normal; font-variant: normal; font-weight: normal; letter-spacing: no=
rmal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: no=
ne; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horiz=
ontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-deco=
rations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-strok=
e-width: 0px; font-size: medium; ">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; color:=
 rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-variant: n=
ormal; font-weight: normal; letter-spacing: normal; line-height: normal; or=
phans: 2; text-indent: 0px; text-transform: none; white-space: normal; wido=
ws: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-b=
order-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -web=
kit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medi=
um; ">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; color:=
 rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-variant: n=
ormal; font-weight: normal; letter-spacing: normal; line-height: normal; or=
phans: 2; text-indent: 0px; text-transform: none; white-space: normal; wido=
ws: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-b=
order-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -web=
kit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medi=
um; ">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; ">
Dear Chairs &amp; all,</div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; min-h=
eight: 20px; ">
<br>
</div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; ">
Back in IETF84, the WG consensus was that port-set assignment is an extensi=
on to DHCP (<a href=3D"http://www.ietf.org/proceedings/84/minutes/minutes-8=
4-dhc">http://www.ietf.org/proceedings/84/minutes/minutes-84-dhc</a>), DHC =
is the right place for the port-set
 related discussions.&nbsp;</div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; min-h=
eight: 20px; ">
<br>
</div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; ">
In the context of requiring IPv4 address sharing, port-set has become a kin=
d of IPv4 address resource to be allocated, which is the work of&nbsp; DHC =
WG. We need not only to define the option, but also to explain why and how =
we can do this. It's reasonable to get
 comments from the DHC WG on which algorithm can cause less modification to=
 DHCP/the Internet but achieve IPv4 address sharing effectively.&nbsp;</div=
>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; min-h=
eight: 20px; ">
<br>
</div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; ">
I think the information is useful for the WG, and more contributions from e=
xperts here will not do harm to the work.So the presentation is in the righ=
t place, IMHO.</div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; min-h=
eight: 20px; ">
<br>
</div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; ">
Best Regards,</div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px; font: normal normal normal 19px/normal 'Heiti SC Light'; ">
Qi Sun</div>
<br>
</div>
</span></div>
</span></div>
</span></span></div>
<br>
<div>
<div>On 2013-3-4, at =1B$B2<8a=1B(B4:01, Ole Troan wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div>
<blockquote type=3D"cite">I posted a revised agenda. &nbsp;<a href=3D"https=
://datatracker.ietf.org/meeting/86/agenda/dhc/">https://datatracker.ietf.or=
g/meeting/86/agenda/dhc/</a><br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Please also note for those with presentation mate=
rial (slides), please send them to be so that they can be uploaded well bef=
ore the DHC WG meeting. PDF or PPT/PPTX are recommended for slides.<br>
</blockquote>
<br>
if I'm allowed to start bashing the agenda.<br>
a &quot;comparison of port set algorithms&quot;, isn't that squarely within=
 softwire's domain?<br>
defining the option format certainly, but choosing algorithm?<br>
<br>
Draft: &nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-softwire-map-04<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;draft-sun-dhc-p=
ort-set-option-00<br>
Title: &nbsp;&nbsp;&nbsp;&nbsp;Comparison of IPv4 port set algorithms<br>
Presenter: Qi Sun<br>
URL: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http://tools.ietf.org/h=
tml/draft-ietf-softwire-map-04">http://tools.ietf.org/html/draft-ietf-softw=
ire-map-04</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http=
://tools.ietf.org/html/draft-sun-dhc-port-set-option-00">http://tools.ietf.=
org/html/draft-sun-dhc-port-set-option-00</a><br>
Slot: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5 min<br>
<br>
cheers,<br>
Ole<br>
_______________________________________________<br>
dhcwg mailing list<br>
<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg">https://www.ietf.or=
g/mailman/listinfo/dhcwg</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>dhcwg mailing list</span><br>
<span><a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg">https://www.i=
etf.org/mailman/listinfo/dhcwg</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_9E05FEFB5DD74263ADBF4A87FC0D27C2ciscocom_--

From Ted.Lemon@nominum.com  Mon Mar  4 06:25:06 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8609F21F86A5 for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 06:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQukkaIAFqPI for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 06:25:06 -0800 (PST)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 0BCC821F8539 for <dhcwg@ietf.org>; Mon,  4 Mar 2013 06:25:06 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUTSuwVTjd61xJeCIxE8BwJSJ/qmcQUJM@postini.com; Mon, 04 Mar 2013 06:25:06 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A26191B80EE for <dhcwg@ietf.org>; Mon,  4 Mar 2013 06:25:05 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 982F4190043; Mon,  4 Mar 2013 06:25:05 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Mon, 4 Mar 2013 06:25:05 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] IETF-86 (Orlando) DHC WG Agenda & Slides
Thread-Index: Ac4YfE5jk7XBs/ZpTm6qjYy599EVrgAdT+uAAANc1wAACdSCAAAAMoSA
Date: Mon, 4 Mar 2013 14:25:05 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474ABC79@mbx-01.win.nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1848B61C@xmb-rcd-x04.cisco.com> <7051D890-1D9F-41AE-BEE0-68DFB6E0F5A4@employees.org>, <F33A58A1-F673-42C8-8496-B3F34491311E@gmail.com> <9E05FEFB-5DD7-4263-ADBF-4A87FC0D27C2@cisco.com>
In-Reply-To: <9E05FEFB-5DD7-4263-ADBF-4A87FC0D27C2@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-2022-jp"
Content-ID: <14C8787219BC0B4AA47041615D940037@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "softwire-chairs@tools.ietf.org Chairs" <softwire-chairs@tools.ietf.org>
Subject: Re: [dhcwg] IETF-86 (Orlando) DHC WG Agenda & Slides
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 14:25:06 -0000

On Mar 4, 2013, at 9:19 AM, "Bernie Volz (volz)" <volz@cisco.com> wrote:
> We have a lot of overlap (there's also the sunset4 wg) and working this o=
ut is, I believe, a priority for Ted.=20

Yup.   The sense in which port sharing is relevant to DHCP is strictly the =
sense in which it requires extensions to the DHCP server.   For an algorith=
mic mapping like MAP, this isn't really an issue.   The other sense in whic=
h there is DHC relevance to the softwires work is the extent to which it is=
 needlessly complicated by a half dozen different incompatible algorithms, =
but this is something that can probably be resolved in softwires.


From Ted.Lemon@nominum.com  Mon Mar  4 07:04:33 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4881F21F8A1C for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 07:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SU149MpSG1Ph for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 07:04:28 -0800 (PST)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 89CD121F8826 for <dhcwg@ietf.org>; Mon,  4 Mar 2013 07:04:28 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUTS3/E0wVxtI3cFEIprjqQ7nxOYDWRIf@postini.com; Mon, 04 Mar 2013 07:04:28 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 41E6D1B80D3 for <dhcwg@ietf.org>; Mon,  4 Mar 2013 07:04:28 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 383A7190043 for <dhcwg@ietf.org>; Mon,  4 Mar 2013 07:04:28 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 4 Mar 2013 07:04:28 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: DHCP discussion list <dhcwg@ietf.org>
Thread-Topic: WGLC: draft-ietf-dhc-dhcpv6-failover-requirements-02
Thread-Index: AQHNsGwoW+LJmw3VLE2UWhN9JpdrFpiW+GMA
Date: Mon, 4 Mar 2013 15:04:27 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474ABD96@mbx-01.win.nominum.com>
References: <E8F6F4C7-074F-4023-80CF-E2C5EA3EF94B@nominum.com>
In-Reply-To: <E8F6F4C7-074F-4023-80CF-E2C5EA3EF94B@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3C9D4961F8DEDD4CA0CC8D2C323CDD30@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-failover-requirements-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Mar 2013 15:04:33 -0000

On Oct 22, 2012, at 11:44 AM, Ted Lemon <ted.lemon@nominum.com> wrote:
> There will be a discussion about this document in the DHC working group m=
eeting on November 8; depending on the outcome of that discussion and the r=
esponse to this message, we will evaluate consensus on or about November 12=
.

The last call got lost in the kerfuffle of IETF 85, but it's clear that thi=
s document has consensus.   Tomek has offered to publish a new version that=
 addresses Steinar's comments; it would be great if Steinar could review To=
mek's updates and make sure that they satisfy his concerns, but the comment=
s were essentially additive, so I don't think they affect consensus (and I'=
m sure Steinar will not be shy about it if he disagrees!).


From volz@cisco.com  Mon Mar  4 17:57:12 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA70E11E80BA for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 17:57:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ege8nfMg5JM3 for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 17:57:12 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id DAE0F11E80D9 for <dhcwg@ietf.org>; Mon,  4 Mar 2013 17:57:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1861; q=dns/txt; s=iport; t=1362448632; x=1363658232; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=kt71dNsGMtPtUEHtFqrsEfKCdoX1s1Yr7GqwgGKvMEE=; b=FxTylzng4mK8Sw+ktYNPjgHvVc6or9RpXxCKPYFBDEA97NXYe/u33tgn 0rETY6lHzg9crDtAbt8VGIaBPafTXsw3X+MSzvds3wQ97YiqNBGw8Dnjd xNlemiw2tXjzll34+584UR0wtIBzl5wX2p0gf6UedRB7BrRguIZWjWBq/ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAApQNVGtJXG8/2dsb2JhbABEwlSBCRZzgh8BAQEEAQEBGh0xAxcEAgEIEQQBAQsUCQcnCxQJCAIEARIIiAsMr1eQHwSNQIEbJhIGgllhA6cygwiCJw
X-IronPort-AV: E=Sophos;i="4.84,784,1355097600"; d="scan'208";a="183512758"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 05 Mar 2013 01:57:11 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r251vBdg013806 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Mar 2013 01:57:11 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Mon, 4 Mar 2013 19:57:11 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, dhc WG <dhcwg@ietf.org>
Thread-Topic: Call for adoption: draft-lemon-dhc-pd-01
Thread-Index: AQHNlrARAq1IuhHT2UasbuE4rMIyj5iXWJ/Q
Date: Tue, 5 Mar 2013 01:57:10 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1848F185@xmb-rcd-x04.cisco.com>
References: <EBDD0AE4-93C6-44F1-9BE0-7B7BE5EC2173@nominum.com>
In-Reply-To: <EBDD0AE4-93C6-44F1-9BE0-7B7BE5EC2173@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] Call for adoption: draft-lemon-dhc-pd-01
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Mar 2013 01:57:13 -0000

Hi:

Here's another item that seemed to have slipped through the cracks as I don=
't see any announcement regarding the result.

I reviewed the call for adoption and some of the other history on this work=
, and I conclude there is consensus to adopt this work and that it is viewe=
d as worthwhile.

There was a comment to have this work done in dnsext (which is still marked=
 as active, but no longer meets and is working to finishing up work that wa=
s already in progress). Having review from DNS experts will be appropriate.=
 Ted and I can work out what the appropriate review and when would be - whe=
ther the dnsext or dnsop working group or appropriate individuals.

Remember, we are just adopting this work as a working group document.

Thanks!

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of T=
ed Lemon
Sent: Wednesday, September 19, 2012 5:45 PM
To: dhc WG
Subject: [dhcwg] Call for adoption: draft-lemon-dhc-pd-01

I'd like the working group to work on this document.   The point of the doc=
ument is to provide a mechanism whereby DHCP requesting routers can indicat=
e their preference to the DHCP delegating router as to how the reverse zone=
 for a delegated prefix should be handled, and to provide a mechanism where=
by the delegating router can communicate back to the requesting router the =
mechanism that was chosen.

John will be evaluating consensus, since I'm the author of the draft.   He =
will evaluate consensus some time after October 2.   If you are in favor of=
 adopting this draft, please say so on the mailing list.   If you think it'=
s a bad idea, please say so on the list.

Thanks!

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

From volz@cisco.com  Mon Mar  4 18:10:58 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A83621F8581 for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 18:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nObZejF2L1wI for <dhcwg@ietfa.amsl.com>; Mon,  4 Mar 2013 18:10:57 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 326EF21F87D3 for <dhcwg@ietf.org>; Mon,  4 Mar 2013 18:10:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7390; q=dns/txt; s=iport; t=1362449457; x=1363659057; h=from:to:cc:subject:date:message-id:mime-version; bh=Cu6d26QxWZOVMc6xZzxx0ZfKZQPJ6ONsK5n8GRQj4Kc=; b=XrWR9bS5/2uZi1ga9Wk40k8xNAXIOP05RsKdYfHLRvhdPGUoFzptzRWZ zeKfYR5UZLN9Q8tKHhgUj+tDp7UfDOKr4cX5B5FPCFIpejuPf6UqQLZ9A z9aqjKZpNo5F+Y+XsfrnX5SQx1QLrv8FEb193/kpghxsT8p8S2vQdMQi0 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAN9TNVGtJV2Z/2dsb2JhbABEgkPAEYEJFnOCIQEELUwSASodORQSAQQOBQiIC69NkCKOWzGCZmEDkwOUL4J7DYIn
X-IronPort-AV: E=Sophos;i="4.84,784,1355097600";  d="scan'208,217";a="183704151"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 05 Mar 2013 02:10:47 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r252Akc4012576 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Mar 2013 02:10:46 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Mon, 4 Mar 2013 20:10:46 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Last Calls/Calls for Adoption/etc - Your help needed!
Thread-Index: Ac4ZRckia7amS2dLReiJfu1etS7s7Q==
Date: Tue, 5 Mar 2013 02:10:46 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1848F1B7@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.132]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1848F1B7xmbrcdx04ciscoc_"
MIME-Version: 1.0
Cc: "Dhc Chairs \(dhc-chairs@tools.ietf.org\)" <dhc-chairs@tools.ietf.org>
Subject: [dhcwg] Last Calls/Calls for Adoption/etc - Your help needed!
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Mar 2013 02:10:58 -0000

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

Hi:

There have been several outstanding WG last calls/calls for adoption that t=
he chairs have tried to address recently.

Please let us know if there are any others that we have missed! (Send a not=
e to dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org>).

While it is the chairs responsibility to keep things moving, we can't do it=
 alone!

The authors/co-authors of the documents are strongly encouraged to keep us =
honest and send us a note at dhc-chairs@tools.ietf.org<mailto:dhc-chairs@to=
ols.ietf.org> if we are not reasonably prompt in addressing items such as t=
his. Usually we should have a response within days of the close of a calls,=
 but there are sometimes delays (especially if there is active discussion a=
bout some issues).

There are a few last calls that will be announced about a week after IETF-8=
6 and the working groups prompt attention to these is greatly appreciated a=
s we need input in order to make a decision.

Thanks and I hope to see many of you in Orlando.


-          Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1848F1B7xmbrcdx04ciscoc_
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:1033457945;
	mso-list-type:hybrid;
	mso-list-template-ids:464414514 -637246336 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">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There have been several outstanding WG last calls/ca=
lls for adoption that the chairs have tried to address recently.<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please let us know if there are any others that we h=
ave missed! (Send a note to
<a href=3D"mailto:dhc-chairs@tools.ietf.org">dhc-chairs@tools.ietf.org</a>)=
.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While it is the chairs responsibility to keep things=
 moving, we can&#8217;t do it alone!<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The authors/co-authors of the documents are strongly=
 encouraged to keep us honest and send us a note at
<a href=3D"mailto:dhc-chairs@tools.ietf.org">dhc-chairs@tools.ietf.org</a> =
if we are not reasonably prompt in addressing items such as this. Usually w=
e should have a response within days of the close of a calls, but there are=
 sometimes delays (especially if there
 is active discussion about some issues).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There are a few last calls that will be announced ab=
out a week after IETF-86 and the working groups prompt attention to these i=
s greatly appreciated as we need input in order to make a decision.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks and I hope to see many of you in Orlando.<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]>Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1848F1B7xmbrcdx04ciscoc_--

From leaf.yeh.sdo@gmail.com  Tue Mar  5 03:05:05 2013
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D938321F89D3 for <dhcwg@ietfa.amsl.com>; Tue,  5 Mar 2013 03:05:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.932
X-Spam-Level: 
X-Spam-Status: No, score=-1.932 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_RECV_IP_219128=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s+eWBDgYyt2K for <dhcwg@ietfa.amsl.com>; Tue,  5 Mar 2013 03:05:04 -0800 (PST)
Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9D3EF21F862E for <dhcwg@ietf.org>; Tue,  5 Mar 2013 03:05:04 -0800 (PST)
Received: by mail-pb0-f49.google.com with SMTP id xa12so4260808pbc.22 for <dhcwg@ietf.org>; Tue, 05 Mar 2013 03:05:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=PgYIXaRTAcQX2qa8M4ra9x9JHzD+FTbLBqA9gg083Y4=; b=yu8Ap3fVuH6KEd2Takh09aINrk4n/tB9GFU+lsXNguJ8bIN0iSmhu5pXR+sXpqOhAt OCDBR/or/5fPtaXVzCYy19r4lJjUDyqGskXKPPOYP1WUyxSOxjVgklgHB3XWxWgHlgiz CTJAdSq85PJAvq/6x4iFexOzimeH4FYvnw3k8Wen5nylmjplwVnX+4ZaTv8wCob8np8w HMuAbldBiZmKJ9mwAWHW5eMp46++PDPFzalYlQSIFB02RK8jLWXVQ5eJNwLxIOigWJwI YR6Ein8O4EtUi/cm4I4eBd4CgMeokT4Bd57RQC46e+H2kO7tCTveqYe3AEvqPRHXfSxN H9PQ==
X-Received: by 10.68.240.103 with SMTP id vz7mr35508734pbc.112.1362481500886;  Tue, 05 Mar 2013 03:05:00 -0800 (PST)
Received: from PC ([219.133.131.71]) by mx.google.com with ESMTPS id hu2sm26187855pbc.38.2013.03.05.03.04.57 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 05 Mar 2013 03:04:59 -0800 (PST)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>, <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1848B61C@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1848B61C@xmb-rcd-x04.cisco.com>
Date: Tue, 5 Mar 2013 19:04:50 +0800
Message-ID: <5135d15b.42c2440a.2e79.ffffbbe8@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A7_01CE19D4.527BA880"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac4YfE5jk7XBs/ZpTm6qjYy599EVrgBEQUTQ
Content-Language: zh-cn
Subject: Re: [dhcwg] IETF-86 (Orlando) DHC WG Agenda & Slides
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Mar 2013 11:05:06 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_01A7_01CE19D4.527BA880
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

>https://datatracker.ietf.org/meeting/86/agenda/dhc/

 

>Draft:     None - DHC Directorate / Recharter

>Presenter: Ted Lemon / Bernie Volz

>URL:       http://datatracker.ietf.org/wg/dhc/charter/

>Slot:      10 min

 

 

It sounds a good idea to set up a DHC Directorate in INT Area, which could
at least enhance the document review in DHC WG.

 

 

Best Regards,

Leaf

 

 

 

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
Bernie Volz (volz)
Sent: Monday, March 04, 2013 10:02 AM
To: dhcwg@ietf.org
Subject: [dhcwg] IETF-86 (Orlando) DHC WG Agenda & Slides

 

Hi:

 

I posted a revised agenda.
https://datatracker.ietf.org/meeting/86/agenda/dhc/

 

Please also note for those with presentation material (slides), please send
them to be so that they can be uploaded well before the DHC WG meeting. PDF
or PPT/PPTX are recommended for slides.

 

-          Bernie

 

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
Bernie Volz (volz)
Sent: Thursday, February 28, 2013 12:35 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Draft IETF-86 (Orlando) agenda posted

 

A draft of the IETF-86 DHC WG meeting in Orlando has been posted:

 

https://datatracker.ietf.org/meeting/86/agenda/dhc/

 

If you requested time, please confirm that it is on the agenda! If not,
please let us know (dhc-chairs@tools.ietf.org).

 

If you haven't requested time and want a slot, please send a request ASAP
(to dhc-chairs@tools.ietf.org).

 

-          Bernie


------=_NextPart_000_01A7_01CE19D4.527BA880
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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 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;
	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:"\7EAF\6587\672C 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:"\6279\6CE8\6846\6587\672C 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:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;
	font-family:"Calibri","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Char0
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:241329739;
	mso-list-type:hybrid;
	mso-list-template-ids:1889167436 1740295406 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:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1817185831;
	mso-list-type:hybrid;
	mso-list-template-ids:1329870914 1347600690 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:4;
	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 l1: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 l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1: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 l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1: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 l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;<a =
href=3D"https://datatracker.ietf.org/meeting/86/agenda/dhc/">https://data=
tracker.ietf.org/meeting/86/agenda/dhc/</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;Draft:&nbsp;&nbsp;&nbsp;&nbsp; None - DHC Directorate / =
Recharter<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;Presenter: Ted Lemon / Bernie =
Volz<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&gt;URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a =
href=3D"http://datatracker.ietf.org/wg/dhc/charter/">http://datatracker.i=
etf.org/wg/dhc/charter/</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&gt;Slot:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10 =
min<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>It sounds a good idea to set up a =
DHC Directorate in INT Area, which could at least enhance the document =
review in DHC WG.<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><div><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 =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p></di=
v><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-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] <b>On Behalf Of =
</b>Bernie Volz (volz)<br><b>Sent:</b> Monday, March 04, 2013 10:02 =
AM<br><b>To:</b> dhcwg@ietf.org<br><b>Subject:</b> [dhcwg] IETF-86 =
(Orlando) DHC WG Agenda &amp; Slides<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'color:#1F497D'>Hi:<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 posted a =
revised agenda.&nbsp; </span><span lang=3DEN-US><a =
href=3D"https://datatracker.ietf.org/meeting/86/agenda/dhc/">https://data=
tracker.ietf.org/meeting/86/agenda/dhc/</a><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'>Please also =
note for those with presentation material (slides), please send them to =
be so that they can be uploaded well before the DHC WG meeting. PDF or =
PPT/PPTX are recommended for slides.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Bernie<o:p></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><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"'> <a =
href=3D"mailto:dhcwg-bounces@ietf.org">dhcwg-bounces@ietf.org</a> [<a =
href=3D"mailto:dhcwg-bounces@ietf.org">mailto:dhcwg-bounces@ietf.org</a>]=
 <b>On Behalf Of </b>Bernie Volz (volz)<br><b>Sent:</b> Thursday, =
February 28, 2013 12:35 AM<br><b>To:</b> <a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br><b>Subject:</b> =
[dhcwg] Draft IETF-86 (Orlando) agenda =
posted<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>A draft of the IETF-86 DHC WG meeting in Orlando has been =
posted:<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><a =
href=3D"https://datatracker.ietf.org/meeting/86/agenda/dhc/">https://data=
tracker.ietf.org/meeting/86/agenda/dhc/</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>If you requested time, please =
confirm that it is on the agenda! If not, please let us know (<a =
href=3D"mailto:dhc-chairs@tools.ietf.org">dhc-chairs@tools.ietf.org</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>If you haven&#8217;t requested time and want a slot, please =
send a request ASAP (to <a =
href=3D"mailto:dhc-chairs@tools.ietf.org">dhc-chairs@tools.ietf.org</a>).=
<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:l1 level1 lfo4'><![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>Bernie<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_01A7_01CE19D4.527BA880--


From msiodelski@gmail.com  Tue Mar  5 05:05:34 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13DDF21F86D2 for <dhcwg@ietfa.amsl.com>; Tue,  5 Mar 2013 05:05:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lcpSiP+WDuDz for <dhcwg@ietfa.amsl.com>; Tue,  5 Mar 2013 05:05:33 -0800 (PST)
Received: from mail-ee0-f45.google.com (mail-ee0-f45.google.com [74.125.83.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2D0FD21F86A1 for <dhcwg@ietf.org>; Tue,  5 Mar 2013 05:05:33 -0800 (PST)
Received: by mail-ee0-f45.google.com with SMTP id b57so4796912eek.32 for <dhcwg@ietf.org>; Tue, 05 Mar 2013 05:05:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:subject:from:to:cc:date:content-type:x-mailer :mime-version:content-transfer-encoding; bh=9u888YIfGvScHmmNecbD9ho/wLeNkJWOVjuSC7oIlrw=; b=g5uiD/OLuPgk6anivXgfSD1BOj51ZLjzIvw6yhXZej4m439t8CP8dD+2/lnWmV0UVX y7fzWI57N2C9I/vBwUeOhZQ93yXT4Xv1s48UQrwXWC+UsHIm4Ky0jhKcj5+h3CxUTb0X DMzPhwnXnYd+AEl4Dk9Uip6HUp6vr+//StHfKN3RZ6GmhAVSM5pzEs9lEXapB4f0jGNa NeUidzaADx/lZgUzNs2siYYeCjij3bGXbHCtd0K56K4zKRggt+L4zKFweIMT27yhRQC1 qrhl8RPgGmxhRITf2/Jz932lm1cc3XIswQi9NQZnEGDS8vijOcQBH//qNAEZoV3WAJgm F41Q==
X-Received: by 10.14.219.7 with SMTP id l7mr70585766eep.12.1362488732335; Tue, 05 Mar 2013 05:05:32 -0800 (PST)
Received: from [192.168.0.193] (89-75-115-194.dynamic.chello.pl. [89.75.115.194]) by mx.google.com with ESMTPS id 46sm37323028eea.3.2013.03.05.05.05.28 (version=SSLv3 cipher=RC4-SHA bits=128/128); Tue, 05 Mar 2013 05:05:30 -0800 (PST)
Message-ID: <1362488728.1939.104.camel@marcin-lenovo>
From: Marcin Siodelski <msiodelski@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Tue, 05 Mar 2013 14:05:28 +0100
Content-Type: text/plain; charset="ISO-8859-15"
X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Questions on draft-ietf-dhc-addr-registration
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Mar 2013 13:05:34 -0000

I have read the version -02 of the draft. 

It is interesting idea and I like the work to move forward.

A couple of questions...

Forgive me if I miss something obvious but the functionality proposed by
the draft seems to be incomplete. What I am concerned about is that the
draft well describes the procedure to register addresses but it doesn't
say a word about conditions in which the addresses may be
removed/unregistered or modified in the database. For example, the
particular host may have been disconnected or its address has changed
for any reason.

Q: Do you think it is a valid use case and should be covered in the
document?

Q: Is it handled by any form of expiration?


Please correct me if am wrong, but I understood that Edge Routers should
respond to solicitation from the registration server immediately after
receiving this solicitation and they should request registration of all
addresses they are aware of. Most of the time the ERs will be requesting
registration of addresses that have been already registered (with
previous requests). 

Q: What is the server's behavior if it finds the particular address in
the database already? Does it remove the old address and replaces it
with the new one? Or, it drops the registration request for a particular
address? Does it respond to the ER with RegistrationDenied or Success?

It is also hard to escape the impression that ER could possibly send the
registration requests when the new candidate address is discovered
rather than periodically when the Server advertises itself. Obviously,
the major role of the RA (or prefix delegation), to notify the ERs that
the server supports registration, remains. However, that could be just
to set the ERs into the mode where they are ready to send registration
requests but they don't do this until they have new address to register.

I know that it generates some additional complexity because the ER needs
to be aware which addresses have been already registered, which not. 

Q: But, have Authors given a thought to this or similar approach?


Section 3: Text says: "By received the address registration request, the
address registration server records the requested address in the address
data base". This is relevant for the example on the Figure 1 where we
have one adjacent Host. However, it gives an impression to somebody
reading it for the first time, that the whole thing is about one Host
and ER, where in fact the general use case is that each ER may have to
request address registration for many hosts. 

S: I suggest that the text AND/OR Figure is updated to reflect the fact
that multiple Hosts are supported by this use case. 

Section 6.2: "For each IA in the Release message..."

Q: Isn't "Release" used by mistake?

Cheers,
Marcin








From rajiva@cisco.com  Tue Mar  5 12:35:11 2013
Return-Path: <rajiva@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD02921F874E for <dhcwg@ietfa.amsl.com>; Tue,  5 Mar 2013 12:35:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 87UDca-l2eAW for <dhcwg@ietfa.amsl.com>; Tue,  5 Mar 2013 12:35:11 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 2EAFC21F8746 for <dhcwg@ietf.org>; Tue,  5 Mar 2013 12:35:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=177; q=dns/txt; s=iport; t=1362515711; x=1363725311; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=e35zUxtMLkOPrBdf0QNT7MIsIqYNujMLXeshXebKxoc=; b=fhSr/4BttfmVTZZlQFuTqccX2KGOleDg+viJ6iMEkwrEO6i70HLZlE25 61EfsBTN02ZcrT8Uh3GcnAILOqNi4VzprRJAScfpTqBc7nezyphiGQjlj YLvjEhWMb0DqpWiDDiCsWWANtVCav4V6i0aAsdvCrc98Hs3tetswPT8S4 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIJABpWNlGtJV2c/2dsb2JhbABEiB68RQQBgW8Wc4ItAQQ6UQEqFEImAQQbiAsMmyuRFZAsjXhkgxdhA5doj1CBUoE2gic
X-IronPort-AV: E=Sophos;i="4.84,790,1355097600"; d="scan'208";a="184071816"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-2.cisco.com with ESMTP; 05 Mar 2013 20:35:10 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r25KZAPa009492 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 5 Mar 2013 20:35:10 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.72]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Tue, 5 Mar 2013 14:35:10 -0600
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: 10 mins in the Agenda for draft-asati-dhc-ipv6-autoconfig-address-tracking needed
Thread-Index: Ac4Z4O3LnFmCOLOcSHay8o78FjbXEw==
Date: Tue, 5 Mar 2013 20:35:09 +0000
Message-ID: <B14A62A57AB87D45BB6DD7D9D2B78F0B1155C4FC@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.227.168]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] 10 mins in the Agenda for draft-asati-dhc-ipv6-autoconfig-address-tracking needed
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Mar 2013 20:35:11 -0000

Dear Chairs,

Could you please allocate 10 mins to discuss this draft?

http://tools.ietf.org/html/draft-asati-dhc-ipv6-autoconfig-address-tracking=
-00

Cheers,
Rajiv


From volz@cisco.com  Tue Mar  5 14:11:35 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D8A21F85B8 for <dhcwg@ietfa.amsl.com>; Tue,  5 Mar 2013 14:11:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.299
X-Spam-Level: 
X-Spam-Status: No, score=-9.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LpddeO14M7j4 for <dhcwg@ietfa.amsl.com>; Tue,  5 Mar 2013 14:11:35 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id C429B21F862A for <dhcwg@ietf.org>; Tue,  5 Mar 2013 14:11:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=701; q=dns/txt; s=iport; t=1362521494; x=1363731094; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=PnBwjDGIPaYhiUGGcHTkSEB4hBX9bEgJoHg3ZWa0iq8=; b=VHtzgq9iRU/JGXNLOLfqTDapmcRGI+OBmMfBxkbJqGA+zKerkme2uODq jUiFPW1No/D+LHVXIHONzzpiMQaBdkbd9fo0stIqoiQQWJhs1wl0qnX0R kN6SE+BmHJ69AlICpk8zg5Ri1G0LHJFCtlAiGs8Jj+T0C2jbY8Zwk/5Wj s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai4FAOFrNlGtJV2a/2dsb2JhbABEiCC8SoFxFnOCKwEBAQQBAQE3NBcEAgEIEQQBAQsUCQcnCxQJCAEBBAESCIgLDKwzkCOOXDgGgllhA5doj1CBUoE2gic
X-IronPort-AV: E=Sophos;i="4.84,791,1355097600"; d="scan'208";a="184133192"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-8.cisco.com with ESMTP; 05 Mar 2013 22:11:27 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r25MBRFM008253 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 5 Mar 2013 22:11:27 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Tue, 5 Mar 2013 16:11:27 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] 10 mins in the Agenda for draft-asati-dhc-ipv6-autoconfig-address-tracking needed
Thread-Index: Ac4Z4O3LnFmCOLOcSHay8o78FjbXEwADWJHg
Date: Tue, 5 Mar 2013 22:11:27 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E18491A82@xmb-rcd-x04.cisco.com>
References: <B14A62A57AB87D45BB6DD7D9D2B78F0B1155C4FC@xmb-rcd-x06.cisco.com>
In-Reply-To: <B14A62A57AB87D45BB6DD7D9D2B78F0B1155C4FC@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] 10 mins in the Agenda for draft-asati-dhc-ipv6-autoconfig-address-tracking needed
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Mar 2013 22:11:35 -0000

Done. Agenda has been updated. https://datatracker.ietf.org/meeting/86/agen=
da/dhc/

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of R=
ajiv Asati (rajiva)
Sent: Tuesday, March 05, 2013 3:35 PM
To: dhcwg@ietf.org
Subject: [dhcwg] 10 mins in the Agenda for draft-asati-dhc-ipv6-autoconfig-=
address-tracking needed

Dear Chairs,

Could you please allocate 10 mins to discuss this draft?

http://tools.ietf.org/html/draft-asati-dhc-ipv6-autoconfig-address-tracking=
-00

Cheers,
Rajiv

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

From iesg-secretary@ietf.org  Wed Mar  6 12:13:23 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 819FD11E809C; Wed,  6 Mar 2013 12:13:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ns8skNnSb3uD; Wed,  6 Mar 2013 12:13:17 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B48311E8101; Wed,  6 Mar 2013 12:13:11 -0800 (PST)
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: 4.41
Message-ID: <20130306201311.12867.84246.idtracker@ietfa.amsl.com>
Date: Wed, 06 Mar 2013 12:13:11 -0800
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: 'The DHCPv4 Relay Agent Identifier Suboption' to	Proposed Standard (draft-ietf-dhc-relay-id-suboption-13.txt)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 06 Mar 2013 20:13:23 -0000

The IESG has approved the following document:
- 'The DHCPv4 Relay Agent Identifier Suboption'
  (draft-ietf-dhc-relay-id-suboption-13.txt) as Proposed Standard

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

The IESG contact persons are Ralph Droms and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-dhc-relay-id-suboption/




Technical Summary: 

   This draft defines a new Relay Agent Identifier suboption for the
   Dynamic Host Configuration Protocol's (DHCP) Relay Agent
   Information option.  The suboption carries a value that uniquely
   identifies the relay agent device within the administrative domain.

Working Group Summary: 

   This document went through the working group, went to last call,
   and went to the IESG, but the sole active editor of the draft at
   the time wound up moving to a new job function where he no longer
   had time to work on the draft, so the work languished for several
   years.

   Recently, two new editors surfaced and began updating the document.
   The exact nature of the document changed somewhat, and memories
   have faded, so it was felt that we should restart the process from
   WGLC back through the IESG.

   This draft got quite a bit of discussion and review in the working
   group during 2011 and early 2012, and passed working group last
   call with some minor editorial comments and no opposition.  Because
   of the history of the document, there was some back-and-forth
   between me and Ralph about how to proceed with the document, with a
   lot of dead air in between, so unfortunately this shepherd doc is
   being written almost a year after the document passed last call.

   This ballot writeup was updated at the time of the submission of
   the latest revision for IETF review and publication.

Document Quality: 

   I'm not aware of any existing implementations.  There is a document
   (the DHCPv4 bulk leasequery document) that depends on this
   document.  It's pretty clear that at least Cisco will be
   implementing this, and that there is demand for it from
   enterprises.  Incognito has also indicated that they intend to
   implement.

   The document contains an acknowledgements section; obviously the
   two new editors are not mentioned there, but certainly deserve
   thanks for having revised the document and for pushing it back
   through the process to this point.

Personnel: 

   Ted Lemon is the document shepherd.  Ralph Droms is the responsible
   AD.

RFC Editor Note

Please make the following change before publication:

OLD:

5.1.  Identifier Uniqueness

  	Administrators should take special care to ensure that relay-ids
  	configured in their relay agents are not duplicated.  There are a
  	number of strategies that may be used to achieve this.

NEW:

5.1.  Identifier Uniqueness

  	It is strongly recommended that administrators take special care to ensure that relay-ids
  	configured in their relay agents are not duplicated.  There are a
  	number of strategies that may be used to achieve this.

END

From iesg-secretary@ietf.org  Wed Mar  6 12:13:27 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B733D11E8100 for <dhcwg@ietfa.amsl.com>; Wed,  6 Mar 2013 12:13:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ednxa2yWj-kH; Wed,  6 Mar 2013 12:13:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6272111E8105; Wed,  6 Mar 2013 12:13:11 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IANA <drafts-approval@icann.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.41
X-IETF-Draft-string: draft-ietf-dhc-relay-id-suboption
X-IETF-Draft-revision: 13
Message-ID: <20130306201311.12867.78292.idtracker@ietfa.amsl.com>
Date: Wed, 06 Mar 2013 12:13:11 -0800
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: 'The DHCPv4 Relay Agent Identifier Suboption' to	Proposed Standard (draft-ietf-dhc-relay-id-suboption-13.txt)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: noreply@ietf.org
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, 06 Mar 2013 20:13:27 -0000

The IESG has approved the following document:
- 'The DHCPv4 Relay Agent Identifier Suboption'
  (draft-ietf-dhc-relay-id-suboption-13.txt) as Proposed Standard

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

The IESG contact persons are Ralph Droms and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-dhc-relay-id-suboption/




Technical Summary: 

   This draft defines a new Relay Agent Identifier suboption for the
   Dynamic Host Configuration Protocol's (DHCP) Relay Agent
   Information option.  The suboption carries a value that uniquely
   identifies the relay agent device within the administrative domain.

Working Group Summary: 

   This document went through the working group, went to last call,
   and went to the IESG, but the sole active editor of the draft at
   the time wound up moving to a new job function where he no longer
   had time to work on the draft, so the work languished for several
   years.

   Recently, two new editors surfaced and began updating the document.
   The exact nature of the document changed somewhat, and memories
   have faded, so it was felt that we should restart the process from
   WGLC back through the IESG.

   This draft got quite a bit of discussion and review in the working
   group during 2011 and early 2012, and passed working group last
   call with some minor editorial comments and no opposition.  Because
   of the history of the document, there was some back-and-forth
   between me and Ralph about how to proceed with the document, with a
   lot of dead air in between, so unfortunately this shepherd doc is
   being written almost a year after the document passed last call.

   This ballot writeup was updated at the time of the submission of
   the latest revision for IETF review and publication.

Document Quality: 

   I'm not aware of any existing implementations.  There is a document
   (the DHCPv4 bulk leasequery document) that depends on this
   document.  It's pretty clear that at least Cisco will be
   implementing this, and that there is demand for it from
   enterprises.  Incognito has also indicated that they intend to
   implement.

   The document contains an acknowledgements section; obviously the
   two new editors are not mentioned there, but certainly deserve
   thanks for having revised the document and for pushing it back
   through the process to this point.

Personnel: 

   Ted Lemon is the document shepherd.  Ralph Droms is the responsible
   AD.

RFC Editor Note

Please make the following change before publication:

OLD:

5.1.  Identifier Uniqueness

  	Administrators should take special care to ensure that relay-ids
  	configured in their relay agents are not duplicated.  There are a
  	number of strategies that may be used to achieve this.

NEW:

5.1.  Identifier Uniqueness

  	It is strongly recommended that administrators take special care to ensure that relay-ids
  	configured in their relay agents are not duplicated.  There are a
  	number of strategies that may be used to achieve this.

END

From jiangsheng@huawei.com  Wed Mar  6 22:35:48 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06AE721F8610 for <dhcwg@ietfa.amsl.com>; Wed,  6 Mar 2013 22:35:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wT8m3cyTd5sM for <dhcwg@ietfa.amsl.com>; Wed,  6 Mar 2013 22:35:47 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C529821F8581 for <dhcwg@ietf.org>; Wed,  6 Mar 2013 22:35:46 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APC56026; Thu, 07 Mar 2013 06:35:45 +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.1.323.7; Thu, 7 Mar 2013 06:35:30 +0000
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 7 Mar 2013 06:35:43 +0000
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.156]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.007; Thu, 7 Mar 2013 14:35:39 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Marcin Siodelski <msiodelski@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Questions on draft-ietf-dhc-addr-registration
Thread-Index: AQHOGaIipW7GZMBxhUGrZlANtT26yZiYQXbw
Date: Thu, 7 Mar 2013 06:35:38 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923A03E190@szxeml545-mbx.china.huawei.com>
References: <1362488728.1939.104.camel@marcin-lenovo>
In-Reply-To: <1362488728.1939.104.camel@marcin-lenovo>
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
Subject: Re: [dhcwg] Questions on draft-ietf-dhc-addr-registration
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 06:35:48 -0000

SGksIE1hcmNpbiwNCg0KVGhhbmtzIGZvciB5b3VyIGVtYWlsLiBQbGVhc2Ugc2VlIG15IHJlcGxp
ZXMgaW4gbGluZXMuDQoNCj5JIGhhdmUgcmVhZCB0aGUgdmVyc2lvbiAtMDIgb2YgdGhlIGRyYWZ0
Lg0KPg0KPkl0IGlzIGludGVyZXN0aW5nIGlkZWEgYW5kIEkgbGlrZSB0aGUgd29yayB0byBtb3Zl
IGZvcndhcmQuDQo+DQo+QSBjb3VwbGUgb2YgcXVlc3Rpb25zLi4uDQo+DQo+Rm9yZ2l2ZSBtZSBp
ZiBJIG1pc3Mgc29tZXRoaW5nIG9idmlvdXMgYnV0IHRoZSBmdW5jdGlvbmFsaXR5IHByb3Bvc2Vk
IGJ5DQo+dGhlIGRyYWZ0IHNlZW1zIHRvIGJlIGluY29tcGxldGUuIFdoYXQgSSBhbSBjb25jZXJu
ZWQgYWJvdXQgaXMgdGhhdCB0aGUNCj5kcmFmdCB3ZWxsIGRlc2NyaWJlcyB0aGUgcHJvY2VkdXJl
IHRvIHJlZ2lzdGVyIGFkZHJlc3NlcyBidXQgaXQgZG9lc24ndA0KPnNheSBhIHdvcmQgYWJvdXQg
Y29uZGl0aW9ucyBpbiB3aGljaCB0aGUgYWRkcmVzc2VzIG1heSBiZQ0KPnJlbW92ZWQvdW5yZWdp
c3RlcmVkIG9yIG1vZGlmaWVkIGluIHRoZSBkYXRhYmFzZS4gRm9yIGV4YW1wbGUsIHRoZQ0KPnBh
cnRpY3VsYXIgaG9zdCBtYXkgaGF2ZSBiZWVuIGRpc2Nvbm5lY3RlZCBvciBpdHMgYWRkcmVzcyBo
YXMgY2hhbmdlZA0KPmZvciBhbnkgcmVhc29uLg0KPg0KPlE6IERvIHlvdSB0aGluayBpdCBpcyBh
IHZhbGlkIHVzZSBjYXNlIGFuZCBzaG91bGQgYmUgY292ZXJlZCBpbiB0aGUNCj5kb2N1bWVudD8N
Cg0KSSBkbyB0aGluayBpdCBpcyBhIHZhbGlkIHVzZSBjYXNlLiBCdXQgaXQgbWF5IGJlIG1vcmUg
ZG93biB0byBpbXBsZW1lbnRhdGlvbiByYXRoZXIgdGhhbiBzdGFuZGFyZCwgaW4gbXkgdW5kZXJz
dGFuZGluZy4gSG93ZXZlciwgd2UgY2FuIGFkZCBzb21lIGNvbnNpZGVyYXRpb24gc2VudGVuY2Us
IGxpa2UgInRoZSByZWdpc3RlcmVkIGFkZHJlc3NlcyBpbiB0aGUgZGF0YWJhc2Ugd291bGQgYmUg
ZXhwaXJlZCBhbmQgcmVtb3ZlZCBmcm9tIHRoZSBkYXRhYmFzZSBhZnRlciBhIHNwZWNpZmljIHRp
bWUuIFRoZSBleHBpcmUgdGltZSBpcyBkb3duIHRvIHRoZSBpbXBsZW1lbnRhdGlvbiBvciBkYXRh
YmFzZSBtYW5hZ2VtZW50LiINCg0KPlE6IElzIGl0IGhhbmRsZWQgYnkgYW55IGZvcm0gb2YgZXhw
aXJhdGlvbj8NCj4NCj4NCj5QbGVhc2UgY29ycmVjdCBtZSBpZiBhbSB3cm9uZywgYnV0IEkgdW5k
ZXJzdG9vZCB0aGF0IEVkZ2UgUm91dGVycyBzaG91bGQNCj5yZXNwb25kIHRvIHNvbGljaXRhdGlv
biBmcm9tIHRoZSByZWdpc3RyYXRpb24gc2VydmVyIGltbWVkaWF0ZWx5IGFmdGVyDQo+cmVjZWl2
aW5nIHRoaXMgc29saWNpdGF0aW9uIGFuZCB0aGV5IHNob3VsZCByZXF1ZXN0IHJlZ2lzdHJhdGlv
biBvZiBhbGwNCj5hZGRyZXNzZXMgdGhleSBhcmUgYXdhcmUgb2YuIE1vc3Qgb2YgdGhlIHRpbWUg
dGhlIEVScyB3aWxsIGJlIHJlcXVlc3RpbmcNCj5yZWdpc3RyYXRpb24gb2YgYWRkcmVzc2VzIHRo
YXQgaGF2ZSBiZWVuIGFscmVhZHkgcmVnaXN0ZXJlZCAod2l0aA0KPnByZXZpb3VzIHJlcXVlc3Rz
KS4NCj4NCj5ROiBXaGF0IGlzIHRoZSBzZXJ2ZXIncyBiZWhhdmlvciBpZiBpdCBmaW5kcyB0aGUg
cGFydGljdWxhciBhZGRyZXNzIGluDQo+dGhlIGRhdGFiYXNlIGFscmVhZHk/IERvZXMgaXQgcmVt
b3ZlIHRoZSBvbGQgYWRkcmVzcyBhbmQgcmVwbGFjZXMgaXQNCj53aXRoIHRoZSBuZXcgb25lPyBP
ciwgaXQgZHJvcHMgdGhlIHJlZ2lzdHJhdGlvbiByZXF1ZXN0IGZvciBhIHBhcnRpY3VsYXINCj5h
ZGRyZXNzPyBEb2VzIGl0IHJlc3BvbmQgdG8gdGhlIEVSIHdpdGggUmVnaXN0cmF0aW9uRGVuaWVk
IG9yIFN1Y2Nlc3M/DQoNClRoZSBzYW1lIHdpdGggYWJvdmUuIEl0IGlzIGRvd24gdG8gdGhlIGlt
cGxlbWVudGF0aW9uIGRlY2lzaW9uLiBNb3N0IHJlYXNvbmFibGUgYmVoYXZpb3IsIGluIG15IHZp
ZXcsIGlzIHRvIHVwZGF0ZSB0aGUgYWRkcmVzcyB3aXRoIG5ldyBsaWZldGltZSBpZiB0aGVyZSB3
YXMgbGlmZXRpbWUgc2V0dXAuIEluIGFueSBjYXNlLCB0aGUgcmVzcG9uc2Ugc2hvdWxkIGJlIFN1
Y2Nlc3MuDQoNCj5JdCBpcyBhbHNvIGhhcmQgdG8gZXNjYXBlIHRoZSBpbXByZXNzaW9uIHRoYXQg
RVIgY291bGQgcG9zc2libHkgc2VuZCB0aGUNCj5yZWdpc3RyYXRpb24gcmVxdWVzdHMgd2hlbiB0
aGUgbmV3IGNhbmRpZGF0ZSBhZGRyZXNzIGlzIGRpc2NvdmVyZWQNCj5yYXRoZXIgdGhhbiBwZXJp
b2RpY2FsbHkgd2hlbiB0aGUgU2VydmVyIGFkdmVydGlzZXMgaXRzZWxmLiBPYnZpb3VzbHksDQo+
dGhlIG1ham9yIHJvbGUgb2YgdGhlIFJBIChvciBwcmVmaXggZGVsZWdhdGlvbiksIHRvIG5vdGlm
eSB0aGUgRVJzIHRoYXQNCj50aGUgc2VydmVyIHN1cHBvcnRzIHJlZ2lzdHJhdGlvbiwgcmVtYWlu
cy4gSG93ZXZlciwgdGhhdCBjb3VsZCBiZSBqdXN0DQo+dG8gc2V0IHRoZSBFUnMgaW50byB0aGUg
bW9kZSB3aGVyZSB0aGV5IGFyZSByZWFkeSB0byBzZW5kIHJlZ2lzdHJhdGlvbg0KPnJlcXVlc3Rz
IGJ1dCB0aGV5IGRvbid0IGRvIHRoaXMgdW50aWwgdGhleSBoYXZlIG5ldyBhZGRyZXNzIHRvIHJl
Z2lzdGVyLg0KPg0KPkkga25vdyB0aGF0IGl0IGdlbmVyYXRlcyBzb21lIGFkZGl0aW9uYWwgY29t
cGxleGl0eSBiZWNhdXNlIHRoZSBFUiBuZWVkcw0KPnRvIGJlIGF3YXJlIHdoaWNoIGFkZHJlc3Nl
cyBoYXZlIGJlZW4gYWxyZWFkeSByZWdpc3RlcmVkLCB3aGljaCBub3QuDQoNClllcywgdGhlIEVS
IG1heSBoYXZlIHRvIHJlbWFpbiBhIHJlZ2lzdHJhdGlvbiBzdGF0dXMgZm9yIGl0cyBkaXNjb3Zl
cmVkIG5laWdoYm9yIGFkZHJlc3Nlcy4gVGhpcyBzZW50ZW5jZSBjYW4gYmUgaW50ZWdyYXRlZCBp
bnRvIHRoZSBkcmFmdCBpbiBuZXh0IHZlcnNpb24uDQoNCj5ROiBCdXQsIGhhdmUgQXV0aG9ycyBn
aXZlbiBhIHRob3VnaHQgdG8gdGhpcyBvciBzaW1pbGFyIGFwcHJvYWNoPw0KPg0KPg0KPlNlY3Rp
b24gMzogVGV4dCBzYXlzOiAiQnkgcmVjZWl2ZWQgdGhlIGFkZHJlc3MgcmVnaXN0cmF0aW9uIHJl
cXVlc3QsIHRoZQ0KPmFkZHJlc3MgcmVnaXN0cmF0aW9uIHNlcnZlciByZWNvcmRzIHRoZSByZXF1
ZXN0ZWQgYWRkcmVzcyBpbiB0aGUgYWRkcmVzcw0KPmRhdGEgYmFzZSIuIFRoaXMgaXMgcmVsZXZh
bnQgZm9yIHRoZSBleGFtcGxlIG9uIHRoZSBGaWd1cmUgMSB3aGVyZSB3ZQ0KPmhhdmUgb25lIGFk
amFjZW50IEhvc3QuIEhvd2V2ZXIsIGl0IGdpdmVzIGFuIGltcHJlc3Npb24gdG8gc29tZWJvZHkN
Cj5yZWFkaW5nIGl0IGZvciB0aGUgZmlyc3QgdGltZSwgdGhhdCB0aGUgd2hvbGUgdGhpbmcgaXMg
YWJvdXQgb25lIEhvc3QNCj5hbmQgRVIsIHdoZXJlIGluIGZhY3QgdGhlIGdlbmVyYWwgdXNlIGNh
c2UgaXMgdGhhdCBlYWNoIEVSIG1heSBoYXZlIHRvDQo+cmVxdWVzdCBhZGRyZXNzIHJlZ2lzdHJh
dGlvbiBmb3IgbWFueSBob3N0cy4NCj4NCj5TOiBJIHN1Z2dlc3QgdGhhdCB0aGUgdGV4dCBBTkQv
T1IgRmlndXJlIGlzIHVwZGF0ZWQgdG8gcmVmbGVjdCB0aGUgZmFjdA0KPnRoYXQgbXVsdGlwbGUg
SG9zdHMgYXJlIHN1cHBvcnRlZCBieSB0aGlzIHVzZSBjYXNlLg0KDQpDbGFyaWZpY2F0aW9uIHRl
eHQgd2lsbCBiZSBhZGRlZCBpbiBuZXh0IHZlcnNpb24uDQoNCj5TZWN0aW9uIDYuMjogIkZvciBl
YWNoIElBIGluIHRoZSBSZWxlYXNlIG1lc3NhZ2UuLi4iDQo+DQo+UTogSXNuJ3QgIlJlbGVhc2Ui
IHVzZWQgYnkgbWlzdGFrZT8NCg0KSXQgaXMgYSBtaXN0YWtlLiBJdCBzaG91bGQgcmVnaXN0ZXIg
cmVxdWVzdCBtZXNzYWdlLg0KDQpNYW55IHRoYW5rcyBhbmQgYmVzdCByZWdhcmRzLA0KDQpTaGVu
Zw0KDQo+Q2hlZXJzLA0KPk1hcmNpbg0KPg0KPg0KPg0KPg0KPg0KPg0KDQo=

From Ted.Lemon@nominum.com  Thu Mar  7 05:38:19 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0633421F8CCE for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 05:38:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.422
X-Spam-Level: 
X-Spam-Status: No, score=-106.422 tagged_above=-999 required=5 tests=[AWL=0.176, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AQ8PHIkpML1u for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 05:38:14 -0800 (PST)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA9221F8CBB for <dhcwg@ietf.org>; Thu,  7 Mar 2013 05:38:14 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUTiYRh5b3UJvFfK0vy6Ixys1LV33NX89@postini.com; Thu, 07 Mar 2013 05:38:14 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BE976108034 for <dhcwg@ietf.org>; Thu,  7 Mar 2013 05:38:13 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B17F7190043; Thu,  7 Mar 2013 05:38:13 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 7 Mar 2013 05:38:13 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [dhcwg] Questions on draft-ietf-dhc-addr-registration
Thread-Index: AQHOGv4EgZ+jDhjVdE2ob6FYCj2fo5iawieA
Date: Thu, 7 Mar 2013 13:38:13 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474B3A81@mbx-01.win.nominum.com>
References: <1362488728.1939.104.camel@marcin-lenovo> <5D36713D8A4E7348A7E10DF7437A4B923A03E190@szxeml545-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923A03E190@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307474B3A81mbx01winnominum_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Questions on draft-ietf-dhc-addr-registration
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 13:38:19 -0000

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

On Mar 7, 2013, at 1:35 AM, Sheng Jiang <jiangsheng@huawei.com<mailto:jiang=
sheng@huawei.com>> wrote:
I do think it is a valid use case. But it may be more down to implementatio=
n rather than standard, in my understanding. However, we can add some consi=
deration sentence, like "the registered addresses in the database would be =
expired and removed from the database after a specific time. The expire tim=
e is down to the implementation or database management."

The draft currently specifies that the server send T1 and T2 times, and tha=
t the client may not be able to use the address after the valid lifetime ex=
pires.   Why not specify that the client should re-register every T1 or, fa=
iling T1, T2?   This is what I assumed you intended, but the document doesn=
't make it explicit.   You could just say something like "the client SHOULD=
 re-register its address as in section 18.1.3 and 18.1.4 of RFC3315.   And =
then you can also say "server MAY purge registered addresses after their va=
lid lifetimes have expired."


--_000_8D23D4052ABE7A4490E77B1A012B6307474B3A81mbx01winnominum_
Content-Type: text/html; charset="us-ascii"
Content-ID: <ED49DA35168D554DB1D108F087F39E8B@nominum.com>
Content-Transfer-Encoding: quoted-printable

<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-lin=
e-break: after-white-space; ">
<div>
<div>On Mar 7, 2013, at 1:35 AM, Sheng Jiang &lt;<a href=3D"mailto:jiangshe=
ng@huawei.com">jiangsheng@huawei.com</a>&gt;&nbsp;wrote:</div>
<blockquote type=3D"cite"><span style=3D"font-family: Optima; font-size: me=
dium; font-style: normal; font-variant: normal; font-weight: normal; letter=
-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto=
; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; w=
ord-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width=
: 0px; display: inline !important; float: none; ">I
 do think it is a valid use case. But it may be more down to implementation=
 rather than standard, in my understanding. However, we can add some consid=
eration sentence, like &quot;the registered addresses in the database would=
 be expired and removed from the database
 after a specific time. The expire time is down to the implementation or da=
tabase management.&quot;</span></blockquote>
</div>
<br>
<div>The draft currently specifies that the server send T1 and T2 times, an=
d that the client may not be able to use the address after the valid lifeti=
me expires. &nbsp; Why not specify that the client should re-register every=
 T1 or, failing T1, T2? &nbsp; This is what
 I assumed you intended, but the document doesn't make it explicit. &nbsp; =
You could just say something like &quot;the client SHOULD re-register its a=
ddress as in section 18.1.3 and 18.1.4 of RFC3315. &nbsp; And then you can =
also say &quot;server MAY purge registered addresses
 after their valid lifetimes have expired.&quot;</div>
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307474B3A81mbx01winnominum_--

From volz@cisco.com  Thu Mar  7 09:19:55 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76CEE21F89CB for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 09:19:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mfWM-H4Cz5NL for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 09:19:54 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id EFA7E21F8A43 for <dhcwg@ietf.org>; Thu,  7 Mar 2013 09:19:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5488; q=dns/txt; s=iport; t=1362676794; x=1363886394; h=from:to:subject:date:message-id:mime-version; bh=vr0R+h7q8l5BhBQHNtb/SY63jL4DESQOceBViaRhD78=; b=VvCzyNan2/56ziApiTXF2RA15zXT1RRUwqyhhD8afiVQAFwZzk9tKixT TfCr6LttXCHwDflY832PwbZGzKEnXqFZ9EH7plcR09W/PZiFJy9XMR3mH bPkoTYfmXp/quu3CAxL0nkQmrsa6/W1MakGNWmjOSMNe496qVJ0QpuoF/ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmQFAJjKOFGtJV2Y/2dsb2JhbABDhBuDSLxmgWEWbQeCLgEELV4BKlYmAQQbiAsMmiSgbwSOWy2CamEDpzyDCYIn
X-IronPort-AV: E=Sophos;i="4.84,803,1355097600";  d="scan'208,217";a="184930780"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 07 Mar 2013 17:19:46 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r27HJjDX002968 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 7 Mar 2013 17:19:45 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Thu, 7 Mar 2013 11:19:45 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: IETF-86 Reminder - Presentation Materials Needed for Upload
Thread-Index: Ac4bV+7nghKp300QSKixT3rLlCvibQ==
Date: Thu, 7 Mar 2013 17:19:45 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E18495FB1@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.255.131]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E18495FB1xmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] IETF-86 Reminder - Presentation Materials Needed for Upload
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 17:19:55 -0000

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

Hi:

For those with a presentation on the DHC WG agenda (https://datatracker.iet=
f.org/meeting/86/agenda/dhc/) please make sure you get me your presentation=
 materials so that they can be uploaded.

Thanks much!


-          Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E18495FB1xmbrcdx04ciscoc_
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:599265723;
	mso-list-type:hybrid;
	mso-list-template-ids:-173794272 -2128606174 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For those with a presentation on the DHC WG agenda (=
<a href=3D"https://datatracker.ietf.org/meeting/86/agenda/dhc/">https://dat=
atracker.ietf.org/meeting/86/agenda/dhc/</a>) please make sure you get me y=
our presentation materials so that they
 can be uploaded.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks much!<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]>Bernie <o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E18495FB1xmbrcdx04ciscoc_--

From jiangsheng@huawei.com  Thu Mar  7 18:20:02 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B6C421F8691 for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 18:20:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SC0vlIu++Dtx for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 18:20:00 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9F36021F8667 for <dhcwg@ietf.org>; Thu,  7 Mar 2013 18:19:59 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQK46772; Fri, 08 Mar 2013 02:19:58 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 8 Mar 2013 02:19:39 +0000
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 8 Mar 2013 02:19:54 +0000
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.156]) by szxeml418-hub.china.huawei.com ([10.82.67.157]) with mapi id 14.01.0323.007; Fri, 8 Mar 2013 10:19:47 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Questions on draft-ietf-dhc-addr-registration
Thread-Index: AQHOGaIipW7GZMBxhUGrZlANtT26yZiYQXbwgAF3MICAAUdOsA==
Date: Fri, 8 Mar 2013 02:19:46 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923A03F87A@szxeml545-mbx.china.huawei.com>
References: <1362488728.1939.104.camel@marcin-lenovo> <5D36713D8A4E7348A7E10DF7437A4B923A03E190@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B3A81@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307474B3A81@mbx-01.win.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: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923A03F87Aszxeml545mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Questions on draft-ietf-dhc-addr-registration
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 02:20:02 -0000

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

SGksIFRlZCwNCg0KWW91ciByZXBseSBpcyBiYXNlZCBvbiBleHBpcmVkIDAxIHZlcnNpb24uIElu
IDAyIHZlcnNpb24sIHNpbmNlIHdlIGhhdmUgZGVkaWNhdGVkIHRoaXMgZHJhZnQgZm9yIGVkZ2Ug
cm91dGVyIHJlZ2lzdGVyaW5nIGFkZHJlc3Mgc2NlbmFyaW8sIHRoZSBzZXJ2ZXIgbm8gbG9uZ2Vy
IGJlIGFibGUgdG8gcmVwbHkgdG8gdGhlIGhvc3QgZGlyZWN0bHkuIFRoZXJlZm9yZSwgd2UgaGF2
ZSByZW1vdmVkIHNlcnZlciByZXNwb25zZXMgbGlmZXRpbWUgdG90YWxseS4NCg0KUGVyc29uYWxs
eSwgSSBzdGlsbCB0aGluayBob3N0IGRpcmVjdGx5IHJlZ2lzdGVycyBpdHMgYWRkcmVzcyBhbmQg
Z2V0IHBlcm1pc3Npb24gZnJvbSBzZXJ2ZXIgaXMgYSB2YWxpZCBzY2VuYXJpby4gQnV0IGl0IGhh
cyBiZWVuIG91dCBvZiB0aGUgY3VycmVudCBkcmFmdC4gSSBhbSBub3Qgc3VyZSB3aGV0aGVyIEkg
Y2FuIGZvdW5kIGEgc3BlY2lmaWMgc2NlbmFyaW8gdG8gYmUgd29ydGggYW5vdGhlciBkcmFmdC4g
TWF5IGJlIHdlIGNhbiBkaXNjdXNzIGR1cmluZyB0aGUgY29taW5nIElFVEYgODYgbWVldGluZywg
aWYgeW91IGFyZSBpbnRlcmVzdGVkIGFuZCBoYXZlIHRpbWUuDQoNCk1hbnkgdGhhbmtzIGFuZCBi
ZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQoNCkZyb206IFRlZCBMZW1vbiBbbWFpbHRvOlRlZC5MZW1v
bkBub21pbnVtLmNvbV0NClNlbnQ6IFRodXJzZGF5LCBNYXJjaCAwNywgMjAxMyA5OjM4IFBNDQpU
bzogU2hlbmcgSmlhbmcNCkNjOiBNYXJjaW4gU2lvZGVsc2tpOyBkaGN3Z0BpZXRmLm9yZw0KU3Vi
amVjdDogUmU6IFtkaGN3Z10gUXVlc3Rpb25zIG9uIGRyYWZ0LWlldGYtZGhjLWFkZHItcmVnaXN0
cmF0aW9uDQoNCk9uIE1hciA3LCAyMDEzLCBhdCAxOjM1IEFNLCBTaGVuZyBKaWFuZyA8amlhbmdz
aGVuZ0BodWF3ZWkuY29tPG1haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb20+PiB3cm90ZToNCkkg
ZG8gdGhpbmsgaXQgaXMgYSB2YWxpZCB1c2UgY2FzZS4gQnV0IGl0IG1heSBiZSBtb3JlIGRvd24g
dG8gaW1wbGVtZW50YXRpb24gcmF0aGVyIHRoYW4gc3RhbmRhcmQsIGluIG15IHVuZGVyc3RhbmRp
bmcuIEhvd2V2ZXIsIHdlIGNhbiBhZGQgc29tZSBjb25zaWRlcmF0aW9uIHNlbnRlbmNlLCBsaWtl
ICJ0aGUgcmVnaXN0ZXJlZCBhZGRyZXNzZXMgaW4gdGhlIGRhdGFiYXNlIHdvdWxkIGJlIGV4cGly
ZWQgYW5kIHJlbW92ZWQgZnJvbSB0aGUgZGF0YWJhc2UgYWZ0ZXIgYSBzcGVjaWZpYyB0aW1lLiBU
aGUgZXhwaXJlIHRpbWUgaXMgZG93biB0byB0aGUgaW1wbGVtZW50YXRpb24gb3IgZGF0YWJhc2Ug
bWFuYWdlbWVudC4iDQoNClRoZSBkcmFmdCBjdXJyZW50bHkgc3BlY2lmaWVzIHRoYXQgdGhlIHNl
cnZlciBzZW5kIFQxIGFuZCBUMiB0aW1lcywgYW5kIHRoYXQgdGhlIGNsaWVudCBtYXkgbm90IGJl
IGFibGUgdG8gdXNlIHRoZSBhZGRyZXNzIGFmdGVyIHRoZSB2YWxpZCBsaWZldGltZSBleHBpcmVz
LiAgIFdoeSBub3Qgc3BlY2lmeSB0aGF0IHRoZSBjbGllbnQgc2hvdWxkIHJlLXJlZ2lzdGVyIGV2
ZXJ5IFQxIG9yLCBmYWlsaW5nIFQxLCBUMj8gICBUaGlzIGlzIHdoYXQgSSBhc3N1bWVkIHlvdSBp
bnRlbmRlZCwgYnV0IHRoZSBkb2N1bWVudCBkb2Vzbid0IG1ha2UgaXQgZXhwbGljaXQuICAgWW91
IGNvdWxkIGp1c3Qgc2F5IHNvbWV0aGluZyBsaWtlICJ0aGUgY2xpZW50IFNIT1VMRCByZS1yZWdp
c3RlciBpdHMgYWRkcmVzcyBhcyBpbiBzZWN0aW9uIDE4LjEuMyBhbmQgMTguMS40IG9mIFJGQzMz
MTUuICAgQW5kIHRoZW4geW91IGNhbiBhbHNvIHNheSAic2VydmVyIE1BWSBwdXJnZSByZWdpc3Rl
cmVkIGFkZHJlc3NlcyBhZnRlciB0aGVpciB2YWxpZCBsaWZldGltZXMgaGF2ZSBleHBpcmVkLiIN
Cg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QOWui+S9kyI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5Ok9wdGltYTsNCglwYW5vc2UtMTowIDAgMCAwIDAgMCAwIDAgMCAwO30NCi8q
IFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNv
Tm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6
ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpi
bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5
cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7
DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28t
c3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt
c2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkw
LjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVh
ZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBzdHlsZT0i
d29yZC13cmFwOiBicmVhay13b3JkOy13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTstd2Via2l0LWxp
bmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpLCBUZWQsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPllvdXIgcmVwbHkgaXMgYmFzZWQgb24gZXhwaXJlZCAwMSB2ZXJzaW9uLiBJbiAw
MiB2ZXJzaW9uLCBzaW5jZSB3ZSBoYXZlIGRlZGljYXRlZCB0aGlzIGRyYWZ0IGZvciBlZGdlIHJv
dXRlciByZWdpc3RlcmluZyBhZGRyZXNzIHNjZW5hcmlvLCB0aGUNCiBzZXJ2ZXIgbm8gbG9uZ2Vy
IGJlIGFibGUgdG8gcmVwbHkgdG8gdGhlIGhvc3QgZGlyZWN0bHkuIFRoZXJlZm9yZSwgd2UgaGF2
ZSByZW1vdmVkIHNlcnZlciByZXNwb25zZXMgbGlmZXRpbWUgdG90YWxseS48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+UGVyc29uYWxseSwgSSBzdGlsbCB0aGluayBob3N0IGRp
cmVjdGx5IHJlZ2lzdGVycyBpdHMgYWRkcmVzcyBhbmQgZ2V0IHBlcm1pc3Npb24gZnJvbSBzZXJ2
ZXIgaXMgYSB2YWxpZCBzY2VuYXJpby4gQnV0IGl0IGhhcyBiZWVuIG91dCBvZiB0aGUgY3VycmVu
dA0KIGRyYWZ0LiBJIGFtIG5vdCBzdXJlIHdoZXRoZXIgSSBjYW4gZm91bmQgYSBzcGVjaWZpYyBz
Y2VuYXJpbyB0byBiZSB3b3J0aCBhbm90aGVyIGRyYWZ0LiBNYXkgYmUgd2UgY2FuIGRpc2N1c3Mg
ZHVyaW5nIHRoZSBjb21pbmcgSUVURiA4NiBtZWV0aW5nLCBpZiB5b3UgYXJlIGludGVyZXN0ZWQg
YW5kIGhhdmUgdGltZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+TWFueSB0
aGFua3MgYW5kIGJlc3QgcmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+U2hlbmc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1s
ZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0K
PGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3Bh
ZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1Rh
aG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1Rh
aG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gVGVkIExlbW9uIFttYWlsdG86VGVk
LkxlbW9uQG5vbWludW0uY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBNYXJjaCAw
NywgMjAxMyA5OjM4IFBNPGJyPg0KPGI+VG86PC9iPiBTaGVuZyBKaWFuZzxicj4NCjxiPkNjOjwv
Yj4gTWFyY2luIFNpb2RlbHNraTsgZGhjd2dAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4g
UmU6IFtkaGN3Z10gUXVlc3Rpb25zIG9uIGRyYWZ0LWlldGYtZGhjLWFkZHItcmVnaXN0cmF0aW9u
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5PbiBNYXIg
NywgMjAxMywgYXQgMTozNSBBTSwgU2hlbmcgSmlhbmcgJmx0OzxhIGhyZWY9Im1haWx0bzpqaWFu
Z3NoZW5nQGh1YXdlaS5jb20iPmppYW5nc2hlbmdAaHVhd2VpLmNvbTwvYT4mZ3Q7Jm5ic3A7d3Jv
dGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFy
Z2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTom
cXVvdDtPcHRpbWEmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPkkgZG8gdGhpbmsgaXQgaXMgYSB2
YWxpZCB1c2UgY2FzZS4gQnV0IGl0IG1heSBiZSBtb3JlIGRvd24gdG8gaW1wbGVtZW50YXRpb24g
cmF0aGVyIHRoYW4gc3RhbmRhcmQsIGluIG15IHVuZGVyc3RhbmRpbmcuIEhvd2V2ZXIsIHdlIGNh
biBhZGQgc29tZSBjb25zaWRlcmF0aW9uIHNlbnRlbmNlLA0KIGxpa2UgJnF1b3Q7dGhlIHJlZ2lz
dGVyZWQgYWRkcmVzc2VzIGluIHRoZSBkYXRhYmFzZSB3b3VsZCBiZSBleHBpcmVkIGFuZCByZW1v
dmVkIGZyb20gdGhlIGRhdGFiYXNlIGFmdGVyIGEgc3BlY2lmaWMgdGltZS4gVGhlIGV4cGlyZSB0
aW1lIGlzIGRvd24gdG8gdGhlIGltcGxlbWVudGF0aW9uIG9yIGRhdGFiYXNlIG1hbmFnZW1lbnQu
JnF1b3Q7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRoZSBkcmFmdCBjdXJyZW50bHkgc3BlY2lmaWVzIHRo
YXQgdGhlIHNlcnZlciBzZW5kIFQxIGFuZCBUMiB0aW1lcywgYW5kIHRoYXQgdGhlIGNsaWVudCBt
YXkgbm90IGJlIGFibGUgdG8gdXNlIHRoZSBhZGRyZXNzIGFmdGVyIHRoZSB2YWxpZCBsaWZldGlt
ZSBleHBpcmVzLiAmbmJzcDsgV2h5IG5vdCBzcGVjaWZ5IHRoYXQgdGhlIGNsaWVudCBzaG91bGQg
cmUtcmVnaXN0ZXIgZXZlcnkgVDENCiBvciwgZmFpbGluZyBUMSwgVDI/ICZuYnNwOyBUaGlzIGlz
IHdoYXQgSSBhc3N1bWVkIHlvdSBpbnRlbmRlZCwgYnV0IHRoZSBkb2N1bWVudCBkb2Vzbid0IG1h
a2UgaXQgZXhwbGljaXQuICZuYnNwOyBZb3UgY291bGQganVzdCBzYXkgc29tZXRoaW5nIGxpa2Ug
JnF1b3Q7dGhlIGNsaWVudCBTSE9VTEQgcmUtcmVnaXN0ZXIgaXRzIGFkZHJlc3MgYXMgaW4gc2Vj
dGlvbiAxOC4xLjMgYW5kIDE4LjEuNCBvZiBSRkMzMzE1LiAmbmJzcDsgQW5kIHRoZW4geW91IGNh
biBhbHNvIHNheSAmcXVvdDtzZXJ2ZXINCiBNQVkgcHVyZ2UgcmVnaXN0ZXJlZCBhZGRyZXNzZXMg
YWZ0ZXIgdGhlaXIgdmFsaWQgbGlmZXRpbWVzIGhhdmUgZXhwaXJlZC4mcXVvdDs8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_5D36713D8A4E7348A7E10DF7437A4B923A03F87Aszxeml545mbxchi_--

From Ted.Lemon@nominum.com  Thu Mar  7 18:53:45 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCBA921F86F4 for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 18:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.425
X-Spam-Level: 
X-Spam-Status: No, score=-106.425 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ye2c+WFVHXX3 for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 18:53:45 -0800 (PST)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 385FB21F86E1 for <dhcwg@ietf.org>; Thu,  7 Mar 2013 18:53:45 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUTlSuI0S7dmD4DPPsuSWypRoH1GQX1sK@postini.com; Thu, 07 Mar 2013 18:53:45 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C88DB1080D7 for <dhcwg@ietf.org>; Thu,  7 Mar 2013 18:53:44 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id BE6F0190043; Thu,  7 Mar 2013 18:53:44 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 7 Mar 2013 18:53:44 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [dhcwg] Questions on draft-ietf-dhc-addr-registration
Thread-Index: AQHOGv4EgZ+jDhjVdE2ob6FYCj2fo5iawieAgADUxwCAAAl8gA==
Date: Fri, 8 Mar 2013 02:53:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474B59C5@mbx-01.win.nominum.com>
References: <1362488728.1939.104.camel@marcin-lenovo> <5D36713D8A4E7348A7E10DF7437A4B923A03E190@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B3A81@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923A03F87A@szxeml545-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923A03F87A@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8EAADA93513CA747A99FD7330F972CE9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Questions on draft-ietf-dhc-addr-registration
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 02:53:46 -0000

On Mar 7, 2013, at 9:19 PM, Sheng Jiang <jiangsheng@huawei.com> wrote:
> Personally, I still think host directly registers its address and get per=
mission from server is a valid scenario. But it has been out of the current=
 draft. I am not sure whether I can found a specific scenario to be worth a=
nother draft. May be we can discuss during the coming IETF 86 meeting, if y=
ou are interested and have time.

I agree; in my mind the missing piece here is that in some (many?) scenario=
s a stateless client nevertheless will want to be able to do things like up=
date the DNS with the address on which it wants to receive peer-to-peer con=
nections.  I had hoped originally that your address registration draft woul=
d address this use case; if the update comes from the router, it definitely=
 does not.

I think the router-sourced update is probably useful for some scenarios, bu=
t I didn't agree with the folks in the meeting last time who thought this w=
as the only practical use case.   It's certainly true that a client that is=
 configured for privacy won't want to do this, and I don't think that they =
should be forced to in general, but the facility is in fact useful.

I am certainly interested in discussing this further, whether it's between =
meetings after DHC, or whether we have time on the agenda to have a quick d=
iscussion about it.   Do you agree that the DNS Update use case is a compel=
ling one?


From jiangsheng@huawei.com  Thu Mar  7 23:49:35 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D96C21F866F for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 23:49:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6eP5+ImOh7Rs for <dhcwg@ietfa.amsl.com>; Thu,  7 Mar 2013 23:49:33 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3D16121F861F for <dhcwg@ietf.org>; Thu,  7 Mar 2013 23:49:33 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQK65040; Fri, 08 Mar 2013 07:49:32 +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.1.323.7; Fri, 8 Mar 2013 07:49:14 +0000
Received: from szxeml459-hub.china.huawei.com (10.82.67.202) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 8 Mar 2013 07:49:32 +0000
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.156]) by szxeml459-hub.china.huawei.com ([10.82.67.202]) with mapi id 14.01.0323.007; Fri, 8 Mar 2013 15:49:23 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Questions on draft-ietf-dhc-addr-registration
Thread-Index: AQHOGaIipW7GZMBxhUGrZlANtT26yZiYQXbwgAF3MICAAUdOsP//lvYAgADU6GA=
Date: Fri, 8 Mar 2013 07:49:22 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923A0409A5@szxeml545-mbx.china.huawei.com>
References: <1362488728.1939.104.camel@marcin-lenovo> <5D36713D8A4E7348A7E10DF7437A4B923A03E190@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B3A81@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923A03F87A@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B59C5@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307474B59C5@mbx-01.win.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
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Questions on draft-ietf-dhc-addr-registration
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 07:49:35 -0000

PiBhIHN0YXRlbGVzcyBjbGllbnQgbmV2ZXJ0aGVsZXNzIHdpbGwgd2FudCB0byBiZSBhYmxlIHRv
IGRvIHRoaW5ncyBsaWtlIHVwZGF0ZSB0aGUNCj5ETlMgd2l0aCB0aGUgYWRkcmVzcyBvbiB3aGlj
aCBpdCB3YW50cyB0byByZWNlaXZlIHBlZXItdG8tcGVlciBjb25uZWN0aW9ucy4NCg0KSSBhbSBu
b3Qgc3VyZSBJIGZ1bGx5IHVuZGVyc3RhbmQgeW91ciBzY2VuYXJpby4gVGhlcmUgYXJlIERETlMg
KFJGQyAyMTM2KSBhbmQgREhDUHY2IGNsaWVudCBGUUROIG9wdGlvbiAoUkZDIDQ3MDQpLiBJdCBz
ZWVtcyB0aGUgbWlzc2luZyBwYXJ0IGlzIGhvdyB0byBzb2xpY2l0IHRoZSBhZGRyZXNzIG9mIERO
UyBzZXJ2ZXIgKGZvciBETlMgcmVjb3JkIHVwZGF0ZSwgbm90IHJlY3Vyc2l2ZSByZXNvbHZlcikg
dG8gdGhlIGNsaWVudC4gSXMgaXQgd2hhdCBpbiB5b3VyIG1pbmQ/DQoNClNoZW5nDQo=

From Ted.Lemon@nominum.com  Fri Mar  8 06:11:55 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9F3C21F8700 for <dhcwg@ietfa.amsl.com>; Fri,  8 Mar 2013 06:11:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.434
X-Spam-Level: 
X-Spam-Status: No, score=-106.434 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YEt2VPQ-lyLh for <dhcwg@ietfa.amsl.com>; Fri,  8 Mar 2013 06:11:55 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 6A45721F84F9 for <dhcwg@ietf.org>; Fri,  8 Mar 2013 06:11:55 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUTnxqmt9Ty6s/ieNtd9fxG5lFUIKg6n5@postini.com; Fri, 08 Mar 2013 06:11:55 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C31061080DB for <dhcwg@ietf.org>; Fri,  8 Mar 2013 06:11:54 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B63A9190043; Fri,  8 Mar 2013 06:11:54 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 8 Mar 2013 06:11:54 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [dhcwg] Questions on draft-ietf-dhc-addr-registration
Thread-Index: AQHOGv4EgZ+jDhjVdE2ob6FYCj2fo5iawieAgADUxwCAAAl8gIAAUpoAgABq4IA=
Date: Fri, 8 Mar 2013 14:11:53 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474B6459@mbx-01.win.nominum.com>
References: <1362488728.1939.104.camel@marcin-lenovo> <5D36713D8A4E7348A7E10DF7437A4B923A03E190@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B3A81@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923A03F87A@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B59C5@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923A0409A5@szxeml545-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923A0409A5@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DCB2C3E2361583409C9E4A86F63210F9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Questions on draft-ietf-dhc-addr-registration
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 14:11:56 -0000

On Mar 8, 2013, at 2:49 AM, Sheng Jiang <jiangsheng@huawei.com> wrote:
> I am not sure I fully understand your scenario. There are DDNS (RFC 2136)=
 and DHCPv6 client FQDN option (RFC 4704). It seems the missing part is how=
 to solicit the address of DNS server (for DNS record update, not recursive=
 resolver) to the client. Is it what in your mind?

The point is to have the DHCP server do the updates, not to configure the c=
lient so that it can do the updates.


From gvithal@gmail.com  Fri Mar  8 09:44:55 2013
Return-Path: <gvithal@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5DB21F862A for <dhcwg@ietfa.amsl.com>; Fri,  8 Mar 2013 09:44:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WUTJ31TP119M for <dhcwg@ietfa.amsl.com>; Fri,  8 Mar 2013 09:44:53 -0800 (PST)
Received: from mail-vb0-x22d.google.com (mail-vb0-x22d.google.com [IPv6:2607:f8b0:400c:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7BBB221F8621 for <dhcwg@ietf.org>; Fri,  8 Mar 2013 09:44:53 -0800 (PST)
Received: by mail-vb0-f45.google.com with SMTP id p1so735225vbi.4 for <dhcwg@ietf.org>; Fri, 08 Mar 2013 09:44:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=qjdmKdp5s0cuIxJ/5BbOr0yAhb2cjKD6GkWT2Nugz4U=; b=Sh+slY2FpCK3oV3OdTQWkjF6vhZynjWuttxOYENxwRzyD93axu4Rwdjfy+7ekOn3LZ Y8oXcu+RjP2xmuiQroDSe3rIH0wzjSAMrdQgw/IGmRncgh6Cn8QkCSoEyhxBHetpl3CO FY5MWPO6bv4zab3JVbXxvEQmDlyLHQWXw2foCaH+3lMmKjSK57x0OhPkq/upJtpZgYqr fUjbonzRgvthL2rKRMyqV8VKOR7agHEFDfQ5xapbO+e/evDZkav+JZI+uzqjg9fK27BM f69r/SUZsxZjHmcoQAyq3LoqSprGu+c94w9B5vsPAd+Zg89odkqOnAnoxObZGOBqZsTl kyGA==
MIME-Version: 1.0
X-Received: by 10.220.214.204 with SMTP id hb12mr1212034vcb.72.1362764686174;  Fri, 08 Mar 2013 09:44:46 -0800 (PST)
Received: by 10.59.6.134 with HTTP; Fri, 8 Mar 2013 09:44:45 -0800 (PST)
In-Reply-To: <CAAfac2jAg21G_f8kokmJyXFRYVytRHGLd3pL3qB0shBeGw0LyQ@mail.gmail.com>
References: <20121214022919.19971.21882.idtracker@ietfa.amsl.com> <CAAfac2gCqq4KxCUt3pd5danhhgdPbNCakBXJwGooPx1jyGEmag@mail.gmail.com> <CAAfac2i9f+nA-S6bsoRy58gOn+mj8fnniVPr3PHNgZXboDwztQ@mail.gmail.com> <CAL10_BrnrQbO4Bzq5mE_9s_e1-jtCtb=Nq5wjaUr0mE3fTUv9A@mail.gmail.com> <FB329D818C7CAB438F0C7DD772EA1025061966F0@TK5EX14MBXC253.redmond.corp.microsoft.com> <8D23D4052ABE7A4490E77B1A012B63074747458F@mbx-01.win.nominum.com> <FB329D818C7CAB438F0C7DD772EA1025061A118C@TK5EX14MBXC253.redmond.corp.microsoft.com> <8D23D4052ABE7A4490E77B1A012B6307474754C3@mbx-01.win.nominum.com> <FB329D818C7CAB438F0C7DD772EA1025061A2F00@TK5EX14MBXC253.redmond.corp.microsoft.com> <8D23D4052ABE7A4490E77B1A012B630747475B92@mbx-01.win.nominum.com> <CAL10_Bq-zkZv7hD0CVD8notzh2O5gBipLs4ACn3qQQVX8jXQ3w@mail.gmail.com> <CAOpJ=k1vt=ZQS=j-7VPRUYwOOBfO2xe5FR0r6gx3TLtQz8hcFw@mail.gmail.com> <CAL10_BqNqbCuSVX=phGPgJ65cX9L2j0FwRANw8qxDHv=wfW1cw@mail.gmail.com> <510A6327.6050506@s-carlsen.dk> <CAOpJ=k00n2_8DEgQP+bRtLzhGtOL1gy8AyFH4PO2cABQ20PAOA@mail.gmail.com> <FB329D818C7CAB438F0C7DD772EA1025061A471E@TK5EX14MBXC253.redmond.corp.microsoft.com> <489D13FBFA9B3E41812EA89F188F018E1844B249@xmb-rcd-x04.cisco.com> <FB329D818C7CAB438F0C7DD772EA1025061A8A94@TK5EX14MBXC253.redmond.corp.microsoft.com> <1FF595DD-C7F5-475D-93BB-EC7E64428EBD@gmail.com> <FB329D818C7CAB438F0C7DD772EA1025061A99BA@TK5EX14MBXC253.redmond.corp.microsoft.com> <93B6C36C-3E9F-4D11-8C08-3BB482C4A470@cisco.com> <CAAfac2h6Vz3oDnMgk1GN+L0MdnT8NK=M7U89FOR60fAoOe6HaQ@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1846E736@xmb-rcd-x04.cisco.com> <FB329D818C7CAB438F0C7DD772EA1025062001BC@TK5EX14MBXC254.redmond.corp.microsoft.com> <CAAfac2jAg21G_f8kokmJyXFRYVytRHGLd3pL3qB0shBeGw0LyQ@mail.gmail.com>
Date: Fri, 8 Mar 2013 23:14:45 +0530
Message-ID: <CAAfac2gz7rKQf8OHDztRTih+Fv8p=DQKa9sx5x8j-K4ONzUGxA@mail.gmail.com>
From: VithalPrasad Gaitonde <gvithal@gmail.com>
To: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
Content-Type: multipart/alternative; boundary=bcaec54fb78e08301504d76d61c6
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>, Bud Millwood <budm@weird-solutions.com>, Ralph Droms <rdroms.ietf@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Andre Kostur <akostur@incognito.com>, Lemon Ted <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 17:44:55 -0000

--bcaec54fb78e08301504d76d61c6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Could folks comment on the proposal below?

On Wed, Feb 27, 2013 at 12:12 AM, VithalPrasad Gaitonde
<gvithal@gmail.com>wrote:

> Agree that 3 has the best merit. In terms of number of retransmissions, i=
t
> would be preferable to go with as many retransmission (about 8?) as would
> fit in a 2 minute interval (i.e. the older SOL_MAX_RT value).
> Since existing deployments work with the 2 minute retransmission cycle,
> this will ensure that subsequent retransmissions (beyond the first hour)
> are successful.
>
> So the proposal is - the first retransmission cycle is for 1 hour with
> exponentially increasing time between retransmissions. Every subsequent
> retransmission cycle which will occur after a gap of 1 hour will last for=
 a
> 2 minute duration.
>
>
>
> On Sat, Feb 16, 2013 at 8:41 AM, Dmitry Anipko <
> Dmitry.Anipko@microsoft.com> wrote:
>
>>  My understanding is that (2) would be against one of the motivations
>> for the draft =96 reduce load on servers, as you pointed out. ****
>>
>> ** **
>>
>> So I agree (3) would be better, if at all something needs to be done for
>> this issue.****
>>
>> ** **
>>
>> *From:* Bernie Volz (volz) [mailto:volz@cisco.com]
>> *Sent:* Friday, February 15, 2013 2:45 PM
>> *To:* VithalPrasad Gaitonde
>>
>> *Cc:* Bud Millwood; Dmitry Anipko; Ralph Droms; dhcwg@ietf.org; Andre
>> Kostur; Lemon Ted
>> *Subject:* RE: [dhcwg] I-D Action:
>> draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt****
>>
>>  ** **
>>
>> (I guess I should now start saying =93WG co-chair hat off=94 =85)****
>>
>> ** **
>>
>> Interesting points.****
>>
>> ** **
>>
>> The elapsed time option only supports 16-bits and is in 100ths of a
>> second, so it will max out at 655.35 seconds (under 11 minutes).****
>>
>> ** **
>>
>> As these are a =91retransmission=92 and so the XID would be the same and=
 the
>> elapsed time should reflect the time since the client started (obviously
>> maxing out at a value of 0xffff as documented in RFC 3315).****
>>
>> ** **
>>
>> Regarding the single packet issue =85 I see:****
>>
>> **1.       **Let it be. If the original retransmissions up this point
>> didn=92t work, what=92s the chance that it will work now? And a single p=
acket
>> should generally be OK. Though there may be some ND implementations that
>> drop a packet they can=92t send instead of holding onto at least that on=
e
>> packet and that might cause things to fail =91forever=92 (the server-to-=
client
>> or relay-to-client ND entry would expire before the next packet arrives)=
.
>> ****
>>
>> **2.       **Have the client could =91restart=92 the Solicit process ins=
tead
>> of using the longer time as a cap to the retransmission delay. But this
>> means that the client would send restart sending at the normal backoff
>> intervals and that makes the clients (if there are a lot) very chatty in
>> total =96 which is what we wanted to prevent. This would also mean a new=
 XID
>> and new elapsed time base.****
>>
>> **3.       **Complicate the retransmission algorithm to allow some small
>> number (2 or 3) packets in a =93shorter=94 interval after =91long=92 ret=
ransmission
>> interval (this is what you suggested). Probably these should occur well
>> within the typical ND cache expiration interval.****
>>
>> **4.       **Something else? (Document that not retaining a packet per
>> destination when needing ND is a bad idea.)****
>>
>> ** **
>>
>> 2 may be the most attractive as it is much simpler (and means this
>> document would define an MRD for Solicit too). But the long delay betwee=
n
>> retransmissions leading up to the maximum may also suffer from the issue
>> mentioned in #1, so #3 may have the best merit.****
>>
>> ** **
>>
>> **-          **Bernie****
>>
>> ** **
>>
>> *From:* dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org<dhcwg-boun=
ces@ietf.org>]
>> *On Behalf Of *VithalPrasad Gaitonde
>> *Sent:* Thursday, February 14, 2013 10:14 PM
>> *To:* Bernie Volz (volz)
>> *Cc:* Bud Millwood; Dmitry Anipko; Ralph Droms; dhcwg@ietf.org; Andre
>> Kostur; Lemon Ted
>> *Subject:* Re: [dhcwg] I-D Action:
>> draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt****
>>
>> ** **
>>
>> Apparently, some relay agents/switches can be configured to relay packet=
s
>> based on the amount of time the client has been trying (elapsed time
>> option). Similar language exists for the behavior of the DHCP server.***=
*
>>
>>  ****
>>
>> From RFC 3315 section 22.9 - ****
>>
>> Servers and Relay Agents use the data value in this option (elapsed time=
)
>>    as input to policy controlling how a server responds to a client
>>    message.  For example, the elapsed time option allows a secondary
>>    DHCP server to respond to a request when a primary server has not
>>    answered in a reasonable time.****
>>
>>  ****
>>
>> When the client retransmits at every 1 hour interval, does the client
>> reset the elapsed time option to 0. If yes, with the above mentioned
>> behavior of relay agents and servers, the single retransmission of SOLIC=
IT
>> or INFORM will turn out inadequate.****
>>
>> Also, given the unreliability of UDP, doing only one retransmission of
>> the message every hour (beyond the first hour) may lead to situations wh=
ere
>> the server does not see the request and the client has to wait for anoth=
er
>> hour to get an IPv6 address or options.****
>>
>>  ****
>>
>> Instead of making just a single retransmission at every 1 hour interval,
>> the client should make at least a couple of retransmissions to increase =
the
>> reliability of getting an IPv6 address or options from the server.****
>>
>>  ****
>>
>> Thanks,****
>>
>> Prasad****
>>
>> On Fri, Feb 1, 2013 at 8:10 PM, Bernie Volz (volz) <volz@cisco.com>
>> wrote:****
>>
>> Fine by me too.
>>
>> - Bernie****
>>
>>
>> On Feb 1, 2013, at 9:52 PM, "Dmitry Anipko" <Dmitry.Anipko@microsoft.com=
>
>> wrote:
>>
>> >>> A client is not expected to listen for a response during the entire
>> period between transmission of Solicit or Information-Request messages
>> >
>> > Looks good to me.
>> >
>> > Thanks.
>> >
>> > -----Original Message-----
>> > From: Ralph Droms [mailto:rdroms.ietf@gmail.com]
>> > Sent: Friday, February 01, 2013 6:08 PM
>> > To: Dmitry Anipko
>> > Cc: Bernie Volz (volz); Bud Millwood; Sten Carlsen; dhcwg@ietf.org;
>> Andre Kostur; Lemon Ted
>> > Subject: Re: [dhcwg] I-D Action:
>> draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt
>> >
>> > (resending to dhcwg mailing list)
>> >
>> > On Feb 1, 2013, at 5:59 PM 2/1/13, Dmitry Anipko <
>> Dmitry.Anipko@microsoft.com>
>> > wrote:
>> >
>> >> Agree with everything you wrote. I think several minutes waiting woul=
d
>> be fine, and I understand there may be good reasons for such waiting
>> interval (as opposed to hour).
>> >>
>> >> If there is a general agreement on these 2 adjustments (allowed
>> waiting period cap and INF_MAX_RT default), how do we move forward - Ral=
ph,
>> can these be included in the next revision of the draft?
>> >>
>> >> Thank you.
>> >
>> > Adding INF_MAX_RT makes sense.
>> >
>> > In my opinion, the right thing to say about waiting for a response is
>> something vague, to the effect of "A client is not expected to listen fo=
r a
>> response during the entire period between transmission of Solicit or
>> Information-Request messages."
>> >
>> > - Ralph
>> >
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg****
>>
>> ** **
>>
>
>

--bcaec54fb78e08301504d76d61c6
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Could folks comment on the proposal below?<br><br><div class=3D"gmail_quote=
">On Wed, Feb 27, 2013 at 12:12 AM, VithalPrasad Gaitonde <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:gvithal@gmail.com" target=3D"_blank">gvithal@gmail.c=
om</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;padding=
-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-l=
eft-style:solid"><div>Agree that 3 has the best merit. In terms of number o=
f retransmissions, it would be preferable to go with as many retransmission=
 (about 8?) as would fit in a 2 minute interval (i.e. the older SOL_MAX_RT =
value). </div>

<div>Since existing deployments work with the 2 minute retransmission cycle=
, this will ensure that subsequent retransmissions (beyond the first hour) =
are successful.</div><div>=A0</div><div>So the proposal is - the first retr=
ansmission cycle is for 1 hour with exponentially increasing time between r=
etransmissions. Every subsequent retransmission cycle which will occur afte=
r a gap of 1 hour will=A0last for a 2 minute duration.=A0</div>
<div class=3D"HOEnZb"><div class=3D"h5">
<div><br><br>=A0</div><div class=3D"gmail_quote">On Sat, Feb 16, 2013 at 8:=
41 AM, Dmitry Anipko <span dir=3D"ltr">&lt;<a href=3D"mailto:Dmitry.Anipko@=
microsoft.com" target=3D"_blank">Dmitry.Anipko@microsoft.com</a>&gt;</span>=
 wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;padding=
-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-l=
eft-style:solid">





<div lang=3D"EN-US" vlink=3D"purple" link=3D"blue">
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">My understanding is =
that (2) would be against one of the motivations for the draft =96 reduce l=
oad on servers, as you pointed out.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">So I agree (3) would=
 be better, if at all something needs to be done for this issue.<u></u><u><=
/u></span></p>


<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p>
<div>
<div style=3D"border-width:1pt medium medium;border-style:solid none none;b=
order-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in"=
>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;;font-size:10pt">From:</span></b><span style=3D"font-fam=
ily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;font-size:10pt"> Bernie Volz =
(volz) [mailto:<a href=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cis=
co.com</a>]
<br>
<b>Sent:</b> Friday, February 15, 2013 2:45 PM<br>
<b>To:</b> VithalPrasad Gaitonde</span><div><br>
<b>Cc:</b> Bud Millwood; Dmitry Anipko; Ralph Droms; <a href=3D"mailto:dhcw=
g@ietf.org" target=3D"_blank">dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<b=
r>
</div><div><b>Subject:</b> RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-so=
lmaxrt-update-00.txt<u></u><u></u></div><p></p>
<p></p></p></div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">(I guess I should no=
w start saying =93WG co-chair hat off=94 =85)<u></u><u></u></span></p><div>=
<div>


<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">Interesting points.<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">The elapsed time opt=
ion only supports 16-bits and is in 100ths of a second, so it will max out =
at 655.35 seconds (under 11 minutes).<u></u><u></u></span></p>


<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">As these are a =91re=
transmission=92 and so the XID would be the same and the elapsed time shoul=
d reflect the time since the client started (obviously maxing out
 at a value of 0xffff as documented in RFC 3315).<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">Regarding the single=
 packet issue =85 I see:<u></u><u></u></span></p>
<p><u></u><span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;font-size:11pt"><span>1.<span style=3D"font:7pt/n=
ormal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal=
">=A0=A0=A0=A0=A0=A0
</span></span></span><u></u><span style=3D"color:rgb(31,73,125);font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">Let it be. If t=
he original retransmissions up this point didn=92t work, what=92s the chanc=
e that it will work now? And a single packet should generally
 be OK. Though there may be some ND implementations that drop a packet they=
 can=92t send instead of holding onto at least that one packet and that mig=
ht cause things to fail =91forever=92 (the server-to-client or relay-to-cli=
ent ND entry would expire before the next
 packet arrives). <u></u><u></u></span></p>
<p><u></u><span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;font-size:11pt"><span>2.<span style=3D"font:7pt/n=
ormal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal=
">=A0=A0=A0=A0=A0=A0
</span></span></span><u></u><span style=3D"color:rgb(31,73,125);font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">Have the client=
 could =91restart=92 the Solicit process instead of using the longer time a=
s a cap to the retransmission delay. But this means that the
 client would send restart sending at the normal backoff intervals and that=
 makes the clients (if there are a lot) very chatty in total =96 which is w=
hat we wanted to prevent. This would also mean a new XID and new elapsed ti=
me base.<u></u><u></u></span></p>


<p><u></u><span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;font-size:11pt"><span>3.<span style=3D"font:7pt/n=
ormal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal=
">=A0=A0=A0=A0=A0=A0
</span></span></span><u></u><span style=3D"color:rgb(31,73,125);font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">Complicate the =
retransmission algorithm to allow some small number (2 or 3) packets in a =
=93shorter=94 interval after =91long=92 retransmission interval (this
 is what you suggested). Probably these should occur well within the typica=
l ND cache expiration interval.<u></u><u></u></span></p>
<p><u></u><span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;font-size:11pt"><span>4.<span style=3D"font:7pt/n=
ormal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal=
">=A0=A0=A0=A0=A0=A0
</span></span></span><u></u><span style=3D"color:rgb(31,73,125);font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">Something else?=
 (Document that not retaining a packet per destination when needing ND is a=
 bad idea.)<u></u><u></u></span></p>


<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">2 may be the most at=
tractive as it is much simpler (and means this document would define an MRD=
 for Solicit too). But the long delay between retransmissions
 leading up to the maximum may also suffer from the issue mentioned in #1, =
so #3 may have the best merit.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p>
<p><u></u><span style=3D"color:rgb(31,73,125);font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;font-size:11pt"><span>-<span style=3D"font:7pt/no=
rmal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal"=
>=A0=A0=A0=A0=A0=A0=A0=A0=A0
</span></span></span><u></u><span style=3D"color:rgb(31,73,125);font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt">Bernie<u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;font-size:11pt"><u></u>=A0<u></u></s=
pan></p>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;;font-size:10pt">From:</span></b><span style=3D"font-fam=
ily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;font-size:10pt">
<a href=3D"mailto:dhcwg-bounces@ietf.org" target=3D"_blank">dhcwg-bounces@i=
etf.org</a> [<a href=3D"mailto:dhcwg-bounces@ietf.org" target=3D"_blank">ma=
ilto:dhcwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>VithalPrasad Gaitonde<br>
<b>Sent:</b> Thursday, February 14, 2013 10:14 PM<br>
<b>To:</b> Bernie Volz (volz)<br>
<b>Cc:</b> Bud Millwood; Dmitry Anipko; Ralph Droms; <a href=3D"mailto:dhcw=
g@ietf.org" target=3D"_blank">
dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<br>
<b>Subject:</b> Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-upda=
te-00.txt<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Apparently, some relay agents/switches can be config=
ured to relay packets based on the amount of time the client has been tryin=
g (elapsed time option). Similar language exists for the behavior of the DH=
CP server.<u></u><u></u></p>


</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">From RFC 3315 section 22.9 - <u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Servers and Relay Agents use the data value in this =
option (elapsed time)<br>
=A0=A0 as input to policy controlling how a server responds to a client<br>
=A0=A0 message.=A0 For example, the elapsed time option allows a secondary<=
br>
=A0=A0 DHCP server to respond to a request when a primary server has not<br=
>
=A0=A0 answered in a reasonable time.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">When the client retransmits at every 1 hour interval=
, does the client reset the elapsed time option to 0. If yes, with the abov=
e mentioned behavior of relay agents and servers, the single retransmission=
 of SOLICIT or INFORM will turn out
 inadequate.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Also, given the unreliability of UDP, doing only one=
 retransmission of the message every hour (beyond the first hour) may lead =
to situations where the server does not see the request and the client has =
to wait for another hour to get an
 IPv6 address or options.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Instead of making just a single retransmission at ev=
ery 1 hour interval, the client should make at least=A0a couple of=A0retran=
smissions to increase the reliability of getting an IPv6 address or options=
 from the server.<u></u><u></u></p>


</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Prasad<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">On Fri, Feb 1, 2013 at 8:10 PM, Bernie Volz (volz) &=
lt;<a href=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>&g=
t; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">Fine by me too.<br>
<span style=3D"color:rgb(136,136,136)"><br>
<span>- Bernie</span></span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
On Feb 1, 2013, at 9:52 PM, &quot;Dmitry Anipko&quot; &lt;<a href=3D"mailto=
:Dmitry.Anipko@microsoft.com" target=3D"_blank">Dmitry.Anipko@microsoft.com=
</a>&gt; wrote:<br>
<br>
&gt;&gt;&gt; A client is not expected to listen for a response during the e=
ntire period between transmission of Solicit or Information-Request message=
s<br>
&gt;<br>
&gt; Looks good to me.<br>
&gt;<br>
&gt; Thanks.<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Ralph Droms [mailto:<a href=3D"mailto:rdroms.ietf@gmail.com" tar=
get=3D"_blank">rdroms.ietf@gmail.com</a>]<br>
&gt; Sent: Friday, February 01, 2013 6:08 PM<br>
&gt; To: Dmitry Anipko<br>
&gt; Cc: Bernie Volz (volz); Bud Millwood; Sten Carlsen; <a href=3D"mailto:=
dhcwg@ietf.org" target=3D"_blank">
dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<br>
&gt; Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update=
-00.txt<br>
&gt;<br>
&gt; (resending to dhcwg mailing list)<br>
&gt;<br>
&gt; On Feb 1, 2013, at 5:59 PM 2/1/13, Dmitry Anipko &lt;<a href=3D"mailto=
:Dmitry.Anipko@microsoft.com" target=3D"_blank">Dmitry.Anipko@microsoft.com=
</a>&gt;<br>
&gt; wrote:<br>
&gt;<br>
&gt;&gt; Agree with everything you wrote. I think several minutes waiting w=
ould be fine, and I understand there may be good reasons for such waiting i=
nterval (as opposed to hour).<br>
&gt;&gt;<br>
&gt;&gt; If there is a general agreement on these 2 adjustments (allowed wa=
iting period cap and INF_MAX_RT default), how do we move forward - Ralph, c=
an these be included in the next revision of the draft?<br>
&gt;&gt;<br>
&gt;&gt; Thank you.<br>
&gt;<br>
&gt; Adding INF_MAX_RT makes sense.<br>
&gt;<br>
&gt; In my opinion, the right thing to say about waiting for a response is =
something vague, to the effect of &quot;A client is not expected to listen =
for a response during the entire period between transmission of Solicit or =
Information-Request messages.&quot;<br>


&gt;<br>
&gt; - Ralph<br>
&gt;<br>
_______________________________________________<br>
dhcwg mailing list<br>
<a href=3D"mailto:dhcwg@ietf.org" target=3D"_blank">dhcwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dhcwg</a><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div></div></div>
</div>

</blockquote></div><br>
</div></div></blockquote></div><br>

--bcaec54fb78e08301504d76d61c6--

From volz@cisco.com  Fri Mar  8 10:42:05 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF52021F88A0 for <dhcwg@ietfa.amsl.com>; Fri,  8 Mar 2013 10:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7XI0s5Ksr+P for <dhcwg@ietfa.amsl.com>; Fri,  8 Mar 2013 10:42:01 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id C3C3721F8836 for <dhcwg@ietf.org>; Fri,  8 Mar 2013 10:42:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=33009; q=dns/txt; s=iport; t=1362768121; x=1363977721; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=MV5OZfgFForH/JZev5eeqHze90JWORbW8Z23sKKUG2Y=; b=V9H8CoG1wXtQx+qafynq1bbj0/FKx2x5bs/OnYG6YllJy9LQH1PpCt3P wmGAvyUyNg6/71DcWlTDR32AJevASbR7L55DsrVZX567dDlnCQQLnEBFw wwu9uhy4Y9hPrX3enup/4ramXGsYqXMK46BIU0HiwiTeU0OoMuabPWQsz A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAI4vOlGtJV2Z/2dsb2JhbABDhBPAO4FbFnSCLAEBAQMBAQEBKkELDAQCAQgRBAEBAQoWAQYHIQYLFAkIAgQBDQUIh3kDCQYMsX4NiH8EjESCFwYHGQcEBgECBIJZYQOUc406hRiDCoIn
X-IronPort-AV: E=Sophos;i="4.84,809,1355097600";  d="scan'208,217";a="185426481"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP; 08 Mar 2013 18:41:59 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r28IfxOF014628 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 8 Mar 2013 18:41:59 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Fri, 8 Mar 2013 12:41:59 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: VithalPrasad Gaitonde <gvithal@gmail.com>, Dmitry Anipko <Dmitry.Anipko@microsoft.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt
Thread-Index: AQHOHCSmYplw5LJo90iXdjri0eiKaZicH0sQ
Date: Fri, 8 Mar 2013 18:41:58 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E18499D11@xmb-rcd-x04.cisco.com>
References: <20121214022919.19971.21882.idtracker@ietfa.amsl.com> <CAAfac2gCqq4KxCUt3pd5danhhgdPbNCakBXJwGooPx1jyGEmag@mail.gmail.com> <CAAfac2i9f+nA-S6bsoRy58gOn+mj8fnniVPr3PHNgZXboDwztQ@mail.gmail.com> <CAL10_BrnrQbO4Bzq5mE_9s_e1-jtCtb=Nq5wjaUr0mE3fTUv9A@mail.gmail.com> <FB329D818C7CAB438F0C7DD772EA1025061966F0@TK5EX14MBXC253.redmond.corp.microsoft.com> <8D23D4052ABE7A4490E77B1A012B63074747458F@mbx-01.win.nominum.com> <FB329D818C7CAB438F0C7DD772EA1025061A118C@TK5EX14MBXC253.redmond.corp.microsoft.com> <8D23D4052ABE7A4490E77B1A012B6307474754C3@mbx-01.win.nominum.com> <FB329D818C7CAB438F0C7DD772EA1025061A2F00@TK5EX14MBXC253.redmond.corp.microsoft.com> <8D23D4052ABE7A4490E77B1A012B630747475B92@mbx-01.win.nominum.com> <CAL10_Bq-zkZv7hD0CVD8notzh2O5gBipLs4ACn3qQQVX8jXQ3w@mail.gmail.com> <CAOpJ=k1vt=ZQS=j-7VPRUYwOOBfO2xe5FR0r6gx3TLtQz8hcFw@mail.gmail.com> <CAL10_BqNqbCuSVX=phGPgJ65cX9L2j0FwRANw8qxDHv=wfW1cw@mail.gmail.com> <510A6327.6050506@s-carlsen.dk> <CAOpJ=k00n2_8DEgQP+bRtLzhGtOL1gy8AyFH4PO2cABQ20PAOA@mail.gmail.com> <FB329D818C7CAB438F0C7DD772EA1025061A471E@TK5EX14MBXC253.redmond.corp.microsoft.com> <489D13FBFA9B3E41812EA89F188F018E1844B249@xmb-rcd-x04.cisco.com> <FB329D818C7CAB438F0C7DD772EA1025061A8A94@TK5EX14MBXC253.redmond.corp.microsoft.com> <1FF595DD-C7F5-475D-93BB-EC7E64428EBD@gmail.com> <FB329D818C7CAB438F0C7DD772EA1025061A99BA@TK5EX14MBXC253.redmond.corp.microsoft.com> <93B6C36C-3E9F-4D11-8C08-3BB482C4A470@cisco.com> <CAAfac2h6Vz3oDnMgk1GN+L0MdnT8NK=M7U89FOR60fAoOe6HaQ@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1846E736@xmb-rcd-x04.cisco.com> <FB329D818C7CAB438F0C7DD772EA1025062001BC@TK5EX14MBXC254.redmond.corp.microsoft.com> <CAAfac2jAg21G_f8kokmJyXFRYVytRHGLd3pL3qB0shBeGw0LyQ@mail.gmail.com> <CAAfac2gz7rKQf8OHDztRTih+Fv8p=DQKa9sx5x8j-K4ONzUGxA@mail.gmail.com>
In-Reply-To: <CAAfac2gz7rKQf8OHDztRTih+Fv8p=DQKa9sx5x8j-K4ONzUGxA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.254.149]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E18499D11xmbrcdx04ciscoc_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Andre Kostur <akostur@incognito.com>, Lemon Ted <Ted.Lemon@nominum.com>, Ralph Droms <rdroms.ietf@gmail.com>, Bud Millwood <budm@weird-solutions.com>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 18:42:06 -0000

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

I kind of would prefer that we keep retransmissions to a minimum - I think =
3 (total transmissions) is a good number (perhaps with normal 8 and 16 seco=
nd backoffs - slower than normal but not that slow). It may be best to have=
 this kick in whenever the time between retransmission is greater than seve=
ral x TTL (hops - probably >5 minutes) or something like that?

The whole idea with solmax was to REDUCE the retransmissions, so we do need=
 to be careful here not to end up increasing them. I think we should get by=
 with only 2 transmissions (1 retransmission).


-          Bernie

From: VithalPrasad Gaitonde [mailto:gvithal@gmail.com]
Sent: Friday, March 08, 2013 12:45 PM
To: Dmitry Anipko
Cc: Bernie Volz (volz); Bud Millwood; Ralph Droms; dhcwg@ietf.org; Andre Ko=
stur; Lemon Ted
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.t=
xt

Could folks comment on the proposal below?
On Wed, Feb 27, 2013 at 12:12 AM, VithalPrasad Gaitonde <gvithal@gmail.com<=
mailto:gvithal@gmail.com>> wrote:
Agree that 3 has the best merit. In terms of number of retransmissions, it =
would be preferable to go with as many retransmission (about 8?) as would f=
it in a 2 minute interval (i.e. the older SOL_MAX_RT value).
Since existing deployments work with the 2 minute retransmission cycle, thi=
s will ensure that subsequent retransmissions (beyond the first hour) are s=
uccessful.

So the proposal is - the first retransmission cycle is for 1 hour with expo=
nentially increasing time between retransmissions. Every subsequent retrans=
mission cycle which will occur after a gap of 1 hour will last for a 2 minu=
te duration.



On Sat, Feb 16, 2013 at 8:41 AM, Dmitry Anipko <Dmitry.Anipko@microsoft.com=
<mailto:Dmitry.Anipko@microsoft.com>> wrote:
My understanding is that (2) would be against one of the motivations for th=
e draft - reduce load on servers, as you pointed out.

So I agree (3) would be better, if at all something needs to be done for th=
is issue.

From: Bernie Volz (volz) [mailto:volz@cisco.com<mailto:volz@cisco.com>]
Sent: Friday, February 15, 2013 2:45 PM
To: VithalPrasad Gaitonde

Cc: Bud Millwood; Dmitry Anipko; Ralph Droms; dhcwg@ietf.org<mailto:dhcwg@i=
etf.org>; Andre Kostur; Lemon Ted
Subject: RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.t=
xt

(I guess I should now start saying "WG co-chair hat off" ...)

Interesting points.

The elapsed time option only supports 16-bits and is in 100ths of a second,=
 so it will max out at 655.35 seconds (under 11 minutes).

As these are a 'retransmission' and so the XID would be the same and the el=
apsed time should reflect the time since the client started (obviously maxi=
ng out at a value of 0xffff as documented in RFC 3315).

Regarding the single packet issue ... I see:

1.       Let it be. If the original retransmissions up this point didn't wo=
rk, what's the chance that it will work now? And a single packet should gen=
erally be OK. Though there may be some ND implementations that drop a packe=
t they can't send instead of holding onto at least that one packet and that=
 might cause things to fail 'forever' (the server-to-client or relay-to-cli=
ent ND entry would expire before the next packet arrives).

2.       Have the client could 'restart' the Solicit process instead of usi=
ng the longer time as a cap to the retransmission delay. But this means tha=
t the client would send restart sending at the normal backoff intervals and=
 that makes the clients (if there are a lot) very chatty in total - which i=
s what we wanted to prevent. This would also mean a new XID and new elapsed=
 time base.

3.       Complicate the retransmission algorithm to allow some small number=
 (2 or 3) packets in a "shorter" interval after 'long' retransmission inter=
val (this is what you suggested). Probably these should occur well within t=
he typical ND cache expiration interval.

4.       Something else? (Document that not retaining a packet per destinat=
ion when needing ND is a bad idea.)

2 may be the most attractive as it is much simpler (and means this document=
 would define an MRD for Solicit too). But the long delay between retransmi=
ssions leading up to the maximum may also suffer from the issue mentioned i=
n #1, so #3 may have the best merit.


-          Bernie

From: dhcwg-bounces@ietf.org<mailto:dhcwg-bounces@ietf.org> [mailto:dhcwg-b=
ounces@ietf.org] On Behalf Of VithalPrasad Gaitonde
Sent: Thursday, February 14, 2013 10:14 PM
To: Bernie Volz (volz)
Cc: Bud Millwood; Dmitry Anipko; Ralph Droms; dhcwg@ietf.org<mailto:dhcwg@i=
etf.org>; Andre Kostur; Lemon Ted
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.t=
xt

Apparently, some relay agents/switches can be configured to relay packets b=
ased on the amount of time the client has been trying (elapsed time option)=
. Similar language exists for the behavior of the DHCP server.

>From RFC 3315 section 22.9 -
Servers and Relay Agents use the data value in this option (elapsed time)
   as input to policy controlling how a server responds to a client
   message.  For example, the elapsed time option allows a secondary
   DHCP server to respond to a request when a primary server has not
   answered in a reasonable time.

When the client retransmits at every 1 hour interval, does the client reset=
 the elapsed time option to 0. If yes, with the above mentioned behavior of=
 relay agents and servers, the single retransmission of SOLICIT or INFORM w=
ill turn out inadequate.
Also, given the unreliability of UDP, doing only one retransmission of the =
message every hour (beyond the first hour) may lead to situations where the=
 server does not see the request and the client has to wait for another hou=
r to get an IPv6 address or options.

Instead of making just a single retransmission at every 1 hour interval, th=
e client should make at least a couple of retransmissions to increase the r=
eliability of getting an IPv6 address or options from the server.

Thanks,
Prasad
On Fri, Feb 1, 2013 at 8:10 PM, Bernie Volz (volz) <volz@cisco.com<mailto:v=
olz@cisco.com>> wrote:
Fine by me too.

- Bernie

On Feb 1, 2013, at 9:52 PM, "Dmitry Anipko" <Dmitry.Anipko@microsoft.com<ma=
ilto:Dmitry.Anipko@microsoft.com>> wrote:

>>> A client is not expected to listen for a response during the entire per=
iod between transmission of Solicit or Information-Request messages
>
> Looks good to me.
>
> Thanks.
>
> -----Original Message-----
> From: Ralph Droms [mailto:rdroms.ietf@gmail.com<mailto:rdroms.ietf@gmail.=
com>]
> Sent: Friday, February 01, 2013 6:08 PM
> To: Dmitry Anipko
> Cc: Bernie Volz (volz); Bud Millwood; Sten Carlsen; dhcwg@ietf.org<mailto=
:dhcwg@ietf.org>; Andre Kostur; Lemon Ted
> Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00=
.txt
>
> (resending to dhcwg mailing list)
>
> On Feb 1, 2013, at 5:59 PM 2/1/13, Dmitry Anipko <Dmitry.Anipko@microsoft=
.com<mailto:Dmitry.Anipko@microsoft.com>>
> wrote:
>
>> Agree with everything you wrote. I think several minutes waiting would b=
e fine, and I understand there may be good reasons for such waiting interva=
l (as opposed to hour).
>>
>> If there is a general agreement on these 2 adjustments (allowed waiting =
period cap and INF_MAX_RT default), how do we move forward - Ralph, can the=
se be included in the next revision of the draft?
>>
>> Thank you.
>
> Adding INF_MAX_RT makes sense.
>
> In my opinion, the right thing to say about waiting for a response is som=
ething vague, to the effect of "A client is not expected to listen for a re=
sponse during the entire period between transmission of Solicit or Informat=
ion-Request messages."
>
> - Ralph
>
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","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:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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:2100373348;
	mso-list-type:hybrid;
	mso-list-template-ids:136998982 683724146 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:2;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I kind of would prefer th=
at we keep retransmissions to a minimum &#8211; I think 3 (total transmissi=
ons) is a good number (perhaps with normal 8 and 16 second backoffs
 &#8211; slower than normal but not that slow). It may be best to have this=
 kick in whenever the time between retransmission is greater than several x=
 TTL (hops &#8211; probably &gt;5 minutes) or something like that?<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The whole idea with solma=
x was to REDUCE the retransmissions, so we do need to be careful here not t=
o end up increasing them. I think we should get by with
 only 2 transmissions (1 retransmission).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<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;"> VithalPr=
asad Gaitonde [mailto:gvithal@gmail.com]
<br>
<b>Sent:</b> Friday, March 08, 2013 12:45 PM<br>
<b>To:</b> Dmitry Anipko<br>
<b>Cc:</b> Bernie Volz (volz); Bud Millwood; Ralph Droms; dhcwg@ietf.org; A=
ndre Kostur; Lemon Ted<br>
<b>Subject:</b> Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-upda=
te-00.txt<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Could folks comment o=
n the proposal below?<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Feb 27, 2013 at 12:12 AM, VithalPrasad Gaito=
nde &lt;<a href=3D"mailto:gvithal@gmail.com" target=3D"_blank">gvithal@gmai=
l.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Agree that 3 has the best merit. In terms of number =
of retransmissions, it would be preferable to go with as many retransmissio=
n (about 8?) as would fit in a 2 minute interval (i.e. the older SOL_MAX_RT=
 value).
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Since existing deployments work with the 2 minute re=
transmission cycle, this will ensure that subsequent retransmissions (beyon=
d the first hour) are successful.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">So the proposal is - the first retransmission cycle =
is for 1 hour with exponentially increasing time between retransmissions. E=
very subsequent retransmission cycle which will occur after a gap of 1 hour=
 will&nbsp;last for a 2 minute duration.&nbsp;<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><br>
<br>
&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On Sat, Feb 16, 2013 at 8:41 AM, Dmitry Anipko &lt;<=
a href=3D"mailto:Dmitry.Anipko@microsoft.com" target=3D"_blank">Dmitry.Anip=
ko@microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">My understanding is that (2) would be a=
gainst one of the motivations for the draft &#8211; reduce load
 on servers, as you pointed out. </span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">So I agree (3) would be better, if at a=
ll something needs to be done for this issue.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0=
in 0in 0in;border-color:currentColor currentColor">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie Volz (volz) [ma=
ilto:<a href=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>=
]
<br>
<b>Sent:</b> Friday, February 15, 2013 2:45 PM<br>
<b>To:</b> VithalPrasad Gaitonde</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
<b>Cc:</b> Bud Millwood; Dmitry Anipko; Ralph Droms; <a href=3D"mailto:dhcw=
g@ietf.org" target=3D"_blank">
dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b>Subject:</b> RE: [dhcwg] I-D Action: draft-ietf-d=
hc-dhcpv6-solmaxrt-update-00.txt<o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">(I guess I should now start saying &#82=
20;WG co-chair hat off&#8221; &#8230;)</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Interesting points.</span><o:p></o:p></=
p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The elapsed time option only supports 1=
6-bits and is in 100ths of a second, so it will max out at
 655.35 seconds (under 11 minutes).</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">As these are a &#8216;retransmission&#8=
217; and so the XID would be the same and the elapsed time should reflect
 the time since the client started (obviously maxing out at a value of 0xff=
ff as documented in RFC 3315).</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Regarding the single packet issue &#823=
0; I see:</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">1.</span><span style=3D"font-size:7.0pt;color=
:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Let it be. If the original retransmission=
s up this point didn&#8217;t work, what&#8217;s the chance that it will wor=
k now? And a single packet should generally be OK. Though there may
 be some ND implementations that drop a packet they can&#8217;t send instea=
d of holding onto at least that one packet and that might cause things to f=
ail &#8216;forever&#8217; (the server-to-client or relay-to-client ND entry=
 would expire before the next packet arrives).
</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">2.</span><span style=3D"font-size:7.0pt;color=
:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Have the client could &#8216;restart&#821=
7; the Solicit process instead of using the longer time as a cap to the ret=
ransmission delay. But this means that the client would send restart
 sending at the normal backoff intervals and that makes the clients (if the=
re are a lot) very chatty in total &#8211; which is what we wanted to preve=
nt. This would also mean a new XID and new elapsed time base.</span><o:p></=
o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">3.</span><span style=3D"font-size:7.0pt;color=
:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Complicate the retransmission algorithm t=
o allow some small number (2 or 3) packets in a &#8220;shorter&#8221; inter=
val after &#8216;long&#8217; retransmission interval (this is what you sugg=
ested).
 Probably these should occur well within the typical ND cache expiration in=
terval.</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">4.</span><span style=3D"font-size:7.0pt;color=
:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Something else? (Document that not retain=
ing a packet per destination when needing ND is a bad idea.)</span><o:p></o=
:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">2 may be the most attractive as it is m=
uch simpler (and means this document would define an MRD for
 Solicit too). But the long delay between retransmissions leading up to the=
 maximum may also suffer from the issue mentioned in #1, so #3 may have the=
 best merit.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">-</span><span style=3D"font-size:7.0pt;color:=
#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Bernie</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:dhcwg-bounces@ietf.org" target=3D"_blank">dhcwg-bounces@i=
etf.org</a> [<a href=3D"mailto:dhcwg-bounces@ietf.org" target=3D"_blank">ma=
ilto:dhcwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>VithalPrasad Gaitonde<br>
<b>Sent:</b> Thursday, February 14, 2013 10:14 PM<br>
<b>To:</b> Bernie Volz (volz)<br>
<b>Cc:</b> Bud Millwood; Dmitry Anipko; Ralph Droms; <a href=3D"mailto:dhcw=
g@ietf.org" target=3D"_blank">
dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<br>
<b>Subject:</b> Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-upda=
te-00.txt</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Apparently, some relay agents/switches can be configured to relay =
packets based on the amount of time the client has been trying (elapsed tim=
e option). Similar language exists for
 the behavior of the DHCP server.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">From RFC 3315 section 22.9 -
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Servers and Relay Agents use the data value in this option (elapse=
d time)<br>
&nbsp;&nbsp; as input to policy controlling how a server responds to a clie=
nt<br>
&nbsp;&nbsp; message.&nbsp; For example, the elapsed time option allows a s=
econdary<br>
&nbsp;&nbsp; DHCP server to respond to a request when a primary server has =
not<br>
&nbsp;&nbsp; answered in a reasonable time.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">When the client retransmits at every 1 hour interval, does the cli=
ent reset the elapsed time option to 0. If yes, with the above mentioned be=
havior of relay agents and servers,
 the single retransmission of SOLICIT or INFORM will turn out inadequate.<o=
:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Also, given the unreliability of UDP, doing only one retransmissio=
n of the message every hour (beyond the first hour) may lead to situations =
where the server does not see the request
 and the client has to wait for another hour to get an IPv6 address or opti=
ons.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Instead of making just a single retransmission at every 1 hour int=
erval, the client should make at least&nbsp;a couple of&nbsp;retransmission=
s to increase the reliability of getting an IPv6
 address or options from the server.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Prasad<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Fri, Feb 1, 2013 at 8:10 PM, Bernie Volz (volz) &lt;<a href=3D"=
mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>&gt; wrote:<o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Fine by me too.<br>
<span style=3D"color:#888888"><br>
- Bernie</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
On Feb 1, 2013, at 9:52 PM, &quot;Dmitry Anipko&quot; &lt;<a href=3D"mailto=
:Dmitry.Anipko@microsoft.com" target=3D"_blank">Dmitry.Anipko@microsoft.com=
</a>&gt; wrote:<br>
<br>
&gt;&gt;&gt; A client is not expected to listen for a response during the e=
ntire period between transmission of Solicit or Information-Request message=
s<br>
&gt;<br>
&gt; Looks good to me.<br>
&gt;<br>
&gt; Thanks.<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Ralph Droms [mailto:<a href=3D"mailto:rdroms.ietf@gmail.com" tar=
get=3D"_blank">rdroms.ietf@gmail.com</a>]<br>
&gt; Sent: Friday, February 01, 2013 6:08 PM<br>
&gt; To: Dmitry Anipko<br>
&gt; Cc: Bernie Volz (volz); Bud Millwood; Sten Carlsen; <a href=3D"mailto:=
dhcwg@ietf.org" target=3D"_blank">
dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<br>
&gt; Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update=
-00.txt<br>
&gt;<br>
&gt; (resending to dhcwg mailing list)<br>
&gt;<br>
&gt; On Feb 1, 2013, at 5:59 PM 2/1/13, Dmitry Anipko &lt;<a href=3D"mailto=
:Dmitry.Anipko@microsoft.com" target=3D"_blank">Dmitry.Anipko@microsoft.com=
</a>&gt;<br>
&gt; wrote:<br>
&gt;<br>
&gt;&gt; Agree with everything you wrote. I think several minutes waiting w=
ould be fine, and I understand there may be good reasons for such waiting i=
nterval (as opposed to hour).<br>
&gt;&gt;<br>
&gt;&gt; If there is a general agreement on these 2 adjustments (allowed wa=
iting period cap and INF_MAX_RT default), how do we move forward - Ralph, c=
an these be included in the next revision of the draft?<br>
&gt;&gt;<br>
&gt;&gt; Thank you.<br>
&gt;<br>
&gt; Adding INF_MAX_RT makes sense.<br>
&gt;<br>
&gt; In my opinion, the right thing to say about waiting for a response is =
something vague, to the effect of &quot;A client is not expected to listen =
for a response during the entire period between transmission of Solicit or =
Information-Request messages.&quot;<br>
&gt;<br>
&gt; - Ralph<br>
&gt;<br>
_______________________________________________<br>
dhcwg mailing list<br>
<a href=3D"mailto:dhcwg@ietf.org" target=3D"_blank">dhcwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dhcwg</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E18499D11xmbrcdx04ciscoc_--

From Dmitry.Anipko@microsoft.com  Fri Mar  8 11:15:43 2013
Return-Path: <Dmitry.Anipko@microsoft.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC7E321F88EF for <dhcwg@ietfa.amsl.com>; Fri,  8 Mar 2013 11:15:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4Kio0LlDS3j for <dhcwg@ietfa.amsl.com>; Fri,  8 Mar 2013 11:15:38 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by ietfa.amsl.com (Postfix) with ESMTP id 9510E21F88EE for <dhcwg@ietf.org>; Fri,  8 Mar 2013 11:15:37 -0800 (PST)
Received: from BL2FFO11FD004.protection.gbl (10.173.161.201) by BL2FFO11HUB035.protection.gbl (10.173.161.115) with Microsoft SMTP Server (TLS) id 15.0.620.12; Fri, 8 Mar 2013 19:15:34 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD004.mail.protection.outlook.com (10.173.160.104) with Microsoft SMTP Server (TLS) id 15.0.620.12 via Frontend Transport; Fri, 8 Mar 2013 19:15:34 +0000
Received: from TK5EX14MBXC254.redmond.corp.microsoft.com ([169.254.2.84]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.02.0318.003; Fri, 8 Mar 2013 19:15:13 +0000
From: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, VithalPrasad Gaitonde <gvithal@gmail.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt
Thread-Index: AQHN2aLtf97Q/V2yEUWdCx2wJ5mS4phWkuiAgAPtq4CAAAO7AIAEG3nDgANu8ACAAHd7gIAADdqAgABaxPCAAA4bAIAAAv0AgACPRYCAABelAIAAAoeAgAAf1ACAAFAk8IABY85ggABtj4CAADY2AIAADETQgAAWHwCAFF5hAIABRyKAgABJg0CAELx0gIAPpzaAgAAP/QCAAAW48A==
Date: Fri, 8 Mar 2013 19:15:12 +0000
Message-ID: <FB329D818C7CAB438F0C7DD772EA10250623523D@TK5EX14MBXC254.redmond.corp.microsoft.com>
References: <20121214022919.19971.21882.idtracker@ietfa.amsl.com> <CAAfac2gCqq4KxCUt3pd5danhhgdPbNCakBXJwGooPx1jyGEmag@mail.gmail.com> <CAAfac2i9f+nA-S6bsoRy58gOn+mj8fnniVPr3PHNgZXboDwztQ@mail.gmail.com> <CAL10_BrnrQbO4Bzq5mE_9s_e1-jtCtb=Nq5wjaUr0mE3fTUv9A@mail.gmail.com> <FB329D818C7CAB438F0C7DD772EA1025061966F0@TK5EX14MBXC253.redmond.corp.microsoft.com> <8D23D4052ABE7A4490E77B1A012B63074747458F@mbx-01.win.nominum.com> <FB329D818C7CAB438F0C7DD772EA1025061A118C@TK5EX14MBXC253.redmond.corp.microsoft.com> <8D23D4052ABE7A4490E77B1A012B6307474754C3@mbx-01.win.nominum.com> <FB329D818C7CAB438F0C7DD772EA1025061A2F00@TK5EX14MBXC253.redmond.corp.microsoft.com> <8D23D4052ABE7A4490E77B1A012B630747475B92@mbx-01.win.nominum.com> <CAL10_Bq-zkZv7hD0CVD8notzh2O5gBipLs4ACn3qQQVX8jXQ3w@mail.gmail.com> <CAOpJ=k1vt=ZQS=j-7VPRUYwOOBfO2xe5FR0r6gx3TLtQz8hcFw@mail.gmail.com> <CAL10_BqNqbCuSVX=phGPgJ65cX9L2j0FwRANw8qxDHv=wfW1cw@mail.gmail.com> <510A6327.6050506@s-carlsen.dk> <CAOpJ=k00n2_8DEgQP+bRtLzhGtOL1gy8AyFH4PO2cABQ20PAOA@mail.gmail.com> <FB329D818C7CAB438F0C7DD772EA1025061A471E@TK5EX14MBXC253.redmond.corp.microsoft.com> <489D13FBFA9B3E41812EA89F188F018E1844B249@xmb-rcd-x04.cisco.com> <FB329D818C7CAB438F0C7DD772EA1025061A8A94@TK5EX14MBXC253.redmond.corp.microsoft.com> <1FF595DD-C7F5-475D-93BB-EC7E64428EBD@gmail.com> <FB329D818C7CAB438F0C7DD772EA1025061A99BA@TK5EX14MBXC253.redmond.corp.microsoft.com> <93B6C36C-3E9F-4D11-8C08-3BB482C4A470@cisco.com> <CAAfac2h6Vz3oDnMgk1GN+L0MdnT8NK=M7U89FOR60fAoOe6HaQ@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1846E736@xmb-rcd-x04.cisco.com> <FB329D818C7CAB438F0C7DD772EA1025062001BC@TK5EX14MBXC254.redmond.corp.microsoft.com> <CAAfac2jAg21G_f8kokmJyXFRYVytRHGLd3pL3qB0shBeGw0LyQ@mail.gmail.com> <CAAfac2gz7rKQf8OHDztRTih+Fv8p=DQKa9sx5x8j-K4ONzUGxA@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E18499D11@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E18499D11@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.73]
Content-Type: multipart/alternative; boundary="_000_FB329D818C7CAB438F0C7DD772EA10250623523DTK5EX14MBXC254r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454001)(13464002)(479174001)(164054002)(51704002)(24454001)(199002)(189002)(16406001)(66066001)(47446002)(54356001)(53806001)(50986001)(16236675001)(74502001)(33656001)(15202345001)(79102001)(49866001)(512954001)(65816001)(47736001)(55846006)(80022001)(31966008)(47976001)(20776003)(5343655001)(63696002)(56776001)(51856001)(59766001)(54316002)(5343635001)(77982001)(561944001)(44976002)(74662001)(69226001)(56816002)(76482001)(46102001)(4396001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB035; H:TK5EX14MLTC103.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 077929D941
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Andre Kostur <akostur@incognito.com>, Lemon Ted <Ted.Lemon@nominum.com>, Ralph Droms <rdroms.ietf@gmail.com>, Bud Millwood <budm@weird-solutions.com>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Mar 2013 19:15:43 -0000

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

>> The whole idea with solmax was to REDUCE the retransmissions, so we do n=
eed to be careful here not to end up increasing them. I think we should get=
 by with only 2 transmissions (1 retransmission).

I'd agree. 8 retransmissions sound excessive/unnecessary, 2-3 total transmi=
ssions should be sufficient. The time between such transmitted packets shou=
ld be larger than default allowed ND total timeout, to cover the case of pa=
cket loss due to ND being slow.

>> It may be best to have this kick in whenever the time between retransmis=
sion is greater than several x TTL (hops - probably >5 minutes) or somethin=
g like that?

Another possibility is to kick this in whenever the interval between transm=
issions calculated using the exponential back-off is larger than the defaul=
t max before solmaxrt-update.


From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Friday, March 08, 2013 10:42 AM
To: VithalPrasad Gaitonde; Dmitry Anipko
Cc: Bud Millwood; Ralph Droms; dhcwg@ietf.org; Andre Kostur; Lemon Ted
Subject: RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.t=
xt

I kind of would prefer that we keep retransmissions to a minimum - I think =
3 (total transmissions) is a good number (perhaps with normal 8 and 16 seco=
nd backoffs - slower than normal but not that slow). It may be best to have=
 this kick in whenever the time between retransmission is greater than seve=
ral x TTL (hops - probably >5 minutes) or something like that?

The whole idea with solmax was to REDUCE the retransmissions, so we do need=
 to be careful here not to end up increasing them. I think we should get by=
 with only 2 transmissions (1 retransmission).


-          Bernie

From: VithalPrasad Gaitonde [mailto:gvithal@gmail.com]
Sent: Friday, March 08, 2013 12:45 PM
To: Dmitry Anipko
Cc: Bernie Volz (volz); Bud Millwood; Ralph Droms; dhcwg@ietf.org<mailto:dh=
cwg@ietf.org>; Andre Kostur; Lemon Ted
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.t=
xt

Could folks comment on the proposal below?
On Wed, Feb 27, 2013 at 12:12 AM, VithalPrasad Gaitonde <gvithal@gmail.com<=
mailto:gvithal@gmail.com>> wrote:
Agree that 3 has the best merit. In terms of number of retransmissions, it =
would be preferable to go with as many retransmission (about 8?) as would f=
it in a 2 minute interval (i.e. the older SOL_MAX_RT value).
Since existing deployments work with the 2 minute retransmission cycle, thi=
s will ensure that subsequent retransmissions (beyond the first hour) are s=
uccessful.

So the proposal is - the first retransmission cycle is for 1 hour with expo=
nentially increasing time between retransmissions. Every subsequent retrans=
mission cycle which will occur after a gap of 1 hour will last for a 2 minu=
te duration.



On Sat, Feb 16, 2013 at 8:41 AM, Dmitry Anipko <Dmitry.Anipko@microsoft.com=
<mailto:Dmitry.Anipko@microsoft.com>> wrote:
My understanding is that (2) would be against one of the motivations for th=
e draft - reduce load on servers, as you pointed out.

So I agree (3) would be better, if at all something needs to be done for th=
is issue.

From: Bernie Volz (volz) [mailto:volz@cisco.com<mailto:volz@cisco.com>]
Sent: Friday, February 15, 2013 2:45 PM
To: VithalPrasad Gaitonde

Cc: Bud Millwood; Dmitry Anipko; Ralph Droms; dhcwg@ietf.org<mailto:dhcwg@i=
etf.org>; Andre Kostur; Lemon Ted
Subject: RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.t=
xt

(I guess I should now start saying "WG co-chair hat off" ...)

Interesting points.

The elapsed time option only supports 16-bits and is in 100ths of a second,=
 so it will max out at 655.35 seconds (under 11 minutes).

As these are a 'retransmission' and so the XID would be the same and the el=
apsed time should reflect the time since the client started (obviously maxi=
ng out at a value of 0xffff as documented in RFC 3315).

Regarding the single packet issue ... I see:

1.       Let it be. If the original retransmissions up this point didn't wo=
rk, what's the chance that it will work now? And a single packet should gen=
erally be OK. Though there may be some ND implementations that drop a packe=
t they can't send instead of holding onto at least that one packet and that=
 might cause things to fail 'forever' (the server-to-client or relay-to-cli=
ent ND entry would expire before the next packet arrives).

2.       Have the client could 'restart' the Solicit process instead of usi=
ng the longer time as a cap to the retransmission delay. But this means tha=
t the client would send restart sending at the normal backoff intervals and=
 that makes the clients (if there are a lot) very chatty in total - which i=
s what we wanted to prevent. This would also mean a new XID and new elapsed=
 time base.

3.       Complicate the retransmission algorithm to allow some small number=
 (2 or 3) packets in a "shorter" interval after 'long' retransmission inter=
val (this is what you suggested). Probably these should occur well within t=
he typical ND cache expiration interval.

4.       Something else? (Document that not retaining a packet per destinat=
ion when needing ND is a bad idea.)

2 may be the most attractive as it is much simpler (and means this document=
 would define an MRD for Solicit too). But the long delay between retransmi=
ssions leading up to the maximum may also suffer from the issue mentioned i=
n #1, so #3 may have the best merit.


-          Bernie

From: dhcwg-bounces@ietf.org<mailto:dhcwg-bounces@ietf.org> [mailto:dhcwg-b=
ounces@ietf.org] On Behalf Of VithalPrasad Gaitonde
Sent: Thursday, February 14, 2013 10:14 PM
To: Bernie Volz (volz)
Cc: Bud Millwood; Dmitry Anipko; Ralph Droms; dhcwg@ietf.org<mailto:dhcwg@i=
etf.org>; Andre Kostur; Lemon Ted
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00.t=
xt

Apparently, some relay agents/switches can be configured to relay packets b=
ased on the amount of time the client has been trying (elapsed time option)=
. Similar language exists for the behavior of the DHCP server.

>From RFC 3315 section 22.9 -
Servers and Relay Agents use the data value in this option (elapsed time)
   as input to policy controlling how a server responds to a client
   message.  For example, the elapsed time option allows a secondary
   DHCP server to respond to a request when a primary server has not
   answered in a reasonable time.

When the client retransmits at every 1 hour interval, does the client reset=
 the elapsed time option to 0. If yes, with the above mentioned behavior of=
 relay agents and servers, the single retransmission of SOLICIT or INFORM w=
ill turn out inadequate.
Also, given the unreliability of UDP, doing only one retransmission of the =
message every hour (beyond the first hour) may lead to situations where the=
 server does not see the request and the client has to wait for another hou=
r to get an IPv6 address or options.

Instead of making just a single retransmission at every 1 hour interval, th=
e client should make at least a couple of retransmissions to increase the r=
eliability of getting an IPv6 address or options from the server.

Thanks,
Prasad
On Fri, Feb 1, 2013 at 8:10 PM, Bernie Volz (volz) <volz@cisco.com<mailto:v=
olz@cisco.com>> wrote:
Fine by me too.

- Bernie

On Feb 1, 2013, at 9:52 PM, "Dmitry Anipko" <Dmitry.Anipko@microsoft.com<ma=
ilto:Dmitry.Anipko@microsoft.com>> wrote:

>>> A client is not expected to listen for a response during the entire per=
iod between transmission of Solicit or Information-Request messages
>
> Looks good to me.
>
> Thanks.
>
> -----Original Message-----
> From: Ralph Droms [mailto:rdroms.ietf@gmail.com<mailto:rdroms.ietf@gmail.=
com>]
> Sent: Friday, February 01, 2013 6:08 PM
> To: Dmitry Anipko
> Cc: Bernie Volz (volz); Bud Millwood; Sten Carlsen; dhcwg@ietf.org<mailto=
:dhcwg@ietf.org>; Andre Kostur; Lemon Ted
> Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update-00=
.txt
>
> (resending to dhcwg mailing list)
>
> On Feb 1, 2013, at 5:59 PM 2/1/13, Dmitry Anipko <Dmitry.Anipko@microsoft=
.com<mailto:Dmitry.Anipko@microsoft.com>>
> wrote:
>
>> Agree with everything you wrote. I think several minutes waiting would b=
e fine, and I understand there may be good reasons for such waiting interva=
l (as opposed to hour).
>>
>> If there is a general agreement on these 2 adjustments (allowed waiting =
period cap and INF_MAX_RT default), how do we move forward - Ralph, can the=
se be included in the next revision of the draft?
>>
>> Thank you.
>
> Adding INF_MAX_RT makes sense.
>
> In my opinion, the right thing to say about waiting for a response is som=
ething vague, to the effect of "A client is not expected to listen for a re=
sponse during the entire period between transmission of Solicit or Informat=
ion-Request messages."
>
> - Ralph
>
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg




--_000_FB329D818C7CAB438F0C7DD772EA10250623523DTK5EX14MBXC254r_
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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","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:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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:2100373348;
	mso-list-type:hybrid;
	mso-list-template-ids:136998982 683724146 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:2;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;">&gt;&gt;</span><span style=3D"font-size:=
11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D=
"> The whole idea with solmax was to REDUCE the retransmissions, so we do n=
eed to be
 careful here not to end up increasing them. I think we should get by with =
only 2 transmissions (1 retransmission).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I&#8217;d agree. 8 retran=
smissions sound excessive/unnecessary, 2-3 total transmissions should be su=
fficient. The time between such transmitted packets should be
 larger than default allowed ND total timeout, to cover the case of packet =
loss due to ND being slow.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;&gt;</span><span styl=
e=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:#1F497D"> It may be best to have this kick in whenever the time bet=
ween retransmission
 is greater than several x TTL (hops &#8211; probably &gt;5 minutes) or som=
ething like that?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Another possibility is to=
 kick this in whenever the interval between transmissions calculated using =
the exponential back-off is larger than the default max
 before </span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quo=
t;,&quot;sans-serif&quot;">solmaxrt-update.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<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;"> Bernie V=
olz (volz) [mailto:volz@cisco.com]
<br>
<b>Sent:</b> Friday, March 08, 2013 10:42 AM<br>
<b>To:</b> VithalPrasad Gaitonde; Dmitry Anipko<br>
<b>Cc:</b> Bud Millwood; Ralph Droms; dhcwg@ietf.org; Andre Kostur; Lemon T=
ed<br>
<b>Subject:</b> RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-upda=
te-00.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I kind of would prefer th=
at we keep retransmissions to a minimum &#8211; I think 3 (total transmissi=
ons) is a good number (perhaps with normal 8 and 16 second backoffs
 &#8211; slower than normal but not that slow). It may be best to have this=
 kick in whenever the time between retransmission is greater than several x=
 TTL (hops &#8211; probably &gt;5 minutes) or something like that?<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The whole idea with solma=
x was to REDUCE the retransmissions, so we do need to be careful here not t=
o end up increasing them. I think we should get by with
 only 2 transmissions (1 retransmission).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<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;"> VithalPr=
asad Gaitonde [<a href=3D"mailto:gvithal@gmail.com">mailto:gvithal@gmail.co=
m</a>]
<br>
<b>Sent:</b> Friday, March 08, 2013 12:45 PM<br>
<b>To:</b> Dmitry Anipko<br>
<b>Cc:</b> Bernie Volz (volz); Bud Millwood; Ralph Droms; <a href=3D"mailto=
:dhcwg@ietf.org">
dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<br>
<b>Subject:</b> Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-upda=
te-00.txt<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Could folks comment o=
n the proposal below?<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Feb 27, 2013 at 12:12 AM, VithalPrasad Gaito=
nde &lt;<a href=3D"mailto:gvithal@gmail.com" target=3D"_blank">gvithal@gmai=
l.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Agree that 3 has the best merit. In terms of number =
of retransmissions, it would be preferable to go with as many retransmissio=
n (about 8?) as would fit in a 2 minute interval (i.e. the older SOL_MAX_RT=
 value).
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Since existing deployments work with the 2 minute re=
transmission cycle, this will ensure that subsequent retransmissions (beyon=
d the first hour) are successful.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">So the proposal is - the first retransmission cycle =
is for 1 hour with exponentially increasing time between retransmissions. E=
very subsequent retransmission cycle which will occur after a gap of 1 hour=
 will&nbsp;last for a 2 minute duration.&nbsp;<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><br>
<br>
&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On Sat, Feb 16, 2013 at 8:41 AM, Dmitry Anipko &lt;<=
a href=3D"mailto:Dmitry.Anipko@microsoft.com" target=3D"_blank">Dmitry.Anip=
ko@microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">My understanding is that (2) would be a=
gainst one of the motivations for the draft &#8211; reduce load
 on servers, as you pointed out. </span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">So I agree (3) would be better, if at a=
ll something needs to be done for this issue.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0=
in 0in 0in;border-color:currentColor currentColor">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie Volz (volz) [ma=
ilto:<a href=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>=
]
<br>
<b>Sent:</b> Friday, February 15, 2013 2:45 PM<br>
<b>To:</b> VithalPrasad Gaitonde</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
<b>Cc:</b> Bud Millwood; Dmitry Anipko; Ralph Droms; <a href=3D"mailto:dhcw=
g@ietf.org" target=3D"_blank">
dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><b>Subject:</b> RE: [dhcwg] I-D Action: draft-ietf-d=
hc-dhcpv6-solmaxrt-update-00.txt<o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">(I guess I should now start saying &#82=
20;WG co-chair hat off&#8221; &#8230;)</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Interesting points.</span><o:p></o:p></=
p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The elapsed time option only supports 1=
6-bits and is in 100ths of a second, so it will max out at
 655.35 seconds (under 11 minutes).</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">As these are a &#8216;retransmission&#8=
217; and so the XID would be the same and the elapsed time should reflect
 the time since the client started (obviously maxing out at a value of 0xff=
ff as documented in RFC 3315).</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Regarding the single packet issue &#823=
0; I see:</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">1.</span><span style=3D"font-size:7.0pt;color=
:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Let it be. If the original retransmission=
s up this point didn&#8217;t work, what&#8217;s the chance that it will wor=
k now? And a single packet should generally be OK. Though there may
 be some ND implementations that drop a packet they can&#8217;t send instea=
d of holding onto at least that one packet and that might cause things to f=
ail &#8216;forever&#8217; (the server-to-client or relay-to-client ND entry=
 would expire before the next packet arrives).
</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">2.</span><span style=3D"font-size:7.0pt;color=
:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Have the client could &#8216;restart&#821=
7; the Solicit process instead of using the longer time as a cap to the ret=
ransmission delay. But this means that the client would send restart
 sending at the normal backoff intervals and that makes the clients (if the=
re are a lot) very chatty in total &#8211; which is what we wanted to preve=
nt. This would also mean a new XID and new elapsed time base.</span><o:p></=
o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">3.</span><span style=3D"font-size:7.0pt;color=
:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Complicate the retransmission algorithm t=
o allow some small number (2 or 3) packets in a &#8220;shorter&#8221; inter=
val after &#8216;long&#8217; retransmission interval (this is what you sugg=
ested).
 Probably these should occur well within the typical ND cache expiration in=
terval.</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">4.</span><span style=3D"font-size:7.0pt;color=
:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Something else? (Document that not retain=
ing a packet per destination when needing ND is a bad idea.)</span><o:p></o=
:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">2 may be the most attractive as it is m=
uch simpler (and means this document would define an MRD for
 Solicit too). But the long delay between retransmissions leading up to the=
 maximum may also suffer from the issue mentioned in #1, so #3 may have the=
 best merit.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">-</span><span style=3D"font-size:7.0pt;color:=
#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">Bernie</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:dhcwg-bounces@ietf.org" target=3D"_blank">dhcwg-bounces@i=
etf.org</a> [<a href=3D"mailto:dhcwg-bounces@ietf.org" target=3D"_blank">ma=
ilto:dhcwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>VithalPrasad Gaitonde<br>
<b>Sent:</b> Thursday, February 14, 2013 10:14 PM<br>
<b>To:</b> Bernie Volz (volz)<br>
<b>Cc:</b> Bud Millwood; Dmitry Anipko; Ralph Droms; <a href=3D"mailto:dhcw=
g@ietf.org" target=3D"_blank">
dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<br>
<b>Subject:</b> Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-upda=
te-00.txt</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Apparently, some relay agents/switches can be configured to relay =
packets based on the amount of time the client has been trying (elapsed tim=
e option). Similar language exists for
 the behavior of the DHCP server.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">From RFC 3315 section 22.9 -
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Servers and Relay Agents use the data value in this option (elapse=
d time)<br>
&nbsp;&nbsp; as input to policy controlling how a server responds to a clie=
nt<br>
&nbsp;&nbsp; message.&nbsp; For example, the elapsed time option allows a s=
econdary<br>
&nbsp;&nbsp; DHCP server to respond to a request when a primary server has =
not<br>
&nbsp;&nbsp; answered in a reasonable time.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">When the client retransmits at every 1 hour interval, does the cli=
ent reset the elapsed time option to 0. If yes, with the above mentioned be=
havior of relay agents and servers,
 the single retransmission of SOLICIT or INFORM will turn out inadequate.<o=
:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Also, given the unreliability of UDP, doing only one retransmissio=
n of the message every hour (beyond the first hour) may lead to situations =
where the server does not see the request
 and the client has to wait for another hour to get an IPv6 address or opti=
ons.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Instead of making just a single retransmission at every 1 hour int=
erval, the client should make at least&nbsp;a couple of&nbsp;retransmission=
s to increase the reliability of getting an IPv6
 address or options from the server.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Prasad<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Fri, Feb 1, 2013 at 8:10 PM, Bernie Volz (volz) &lt;<a href=3D"=
mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>&gt; wrote:<o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Fine by me too.<br>
<span style=3D"color:#888888"><br>
- Bernie</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
On Feb 1, 2013, at 9:52 PM, &quot;Dmitry Anipko&quot; &lt;<a href=3D"mailto=
:Dmitry.Anipko@microsoft.com" target=3D"_blank">Dmitry.Anipko@microsoft.com=
</a>&gt; wrote:<br>
<br>
&gt;&gt;&gt; A client is not expected to listen for a response during the e=
ntire period between transmission of Solicit or Information-Request message=
s<br>
&gt;<br>
&gt; Looks good to me.<br>
&gt;<br>
&gt; Thanks.<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Ralph Droms [mailto:<a href=3D"mailto:rdroms.ietf@gmail.com" tar=
get=3D"_blank">rdroms.ietf@gmail.com</a>]<br>
&gt; Sent: Friday, February 01, 2013 6:08 PM<br>
&gt; To: Dmitry Anipko<br>
&gt; Cc: Bernie Volz (volz); Bud Millwood; Sten Carlsen; <a href=3D"mailto:=
dhcwg@ietf.org" target=3D"_blank">
dhcwg@ietf.org</a>; Andre Kostur; Lemon Ted<br>
&gt; Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-solmaxrt-update=
-00.txt<br>
&gt;<br>
&gt; (resending to dhcwg mailing list)<br>
&gt;<br>
&gt; On Feb 1, 2013, at 5:59 PM 2/1/13, Dmitry Anipko &lt;<a href=3D"mailto=
:Dmitry.Anipko@microsoft.com" target=3D"_blank">Dmitry.Anipko@microsoft.com=
</a>&gt;<br>
&gt; wrote:<br>
&gt;<br>
&gt;&gt; Agree with everything you wrote. I think several minutes waiting w=
ould be fine, and I understand there may be good reasons for such waiting i=
nterval (as opposed to hour).<br>
&gt;&gt;<br>
&gt;&gt; If there is a general agreement on these 2 adjustments (allowed wa=
iting period cap and INF_MAX_RT default), how do we move forward - Ralph, c=
an these be included in the next revision of the draft?<br>
&gt;&gt;<br>
&gt;&gt; Thank you.<br>
&gt;<br>
&gt; Adding INF_MAX_RT makes sense.<br>
&gt;<br>
&gt; In my opinion, the right thing to say about waiting for a response is =
something vague, to the effect of &quot;A client is not expected to listen =
for a response during the entire period between transmission of Solicit or =
Information-Request messages.&quot;<br>
&gt;<br>
&gt; - Ralph<br>
&gt;<br>
_______________________________________________<br>
dhcwg mailing list<br>
<a href=3D"mailto:dhcwg@ietf.org" target=3D"_blank">dhcwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dhcwg</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_FB329D818C7CAB438F0C7DD772EA10250623523DTK5EX14MBXC254r_--

From volz@cisco.com  Sat Mar  9 18:31:21 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDF121F87D7 for <dhcwg@ietfa.amsl.com>; Sat,  9 Mar 2013 18:31:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0TibnDFyHcge for <dhcwg@ietfa.amsl.com>; Sat,  9 Mar 2013 18:31:20 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 96FE421F87D3 for <dhcwg@ietf.org>; Sat,  9 Mar 2013 18:31:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6673; q=dns/txt; s=iport; t=1362882680; x=1364092280; h=from:to:subject:date:message-id:mime-version; bh=XwoJsKHdXkEd1FRZuqKsgbC/1XpUhQvTKK1EPIx2Kmw=; b=McZ4K4x5MbxbcNcmES2oZ9S09tu+t9zhbES4UrokqVaPJpvffR7087ww 3UT5Dg3EI8bJxXxzhKXwSFQ8STB8KOGEM7d3uU4OONKk1USkpWv8oUrwJ VIn8bUWSeFcPIkAhuSDJCy1oNEO3e/KN0G6HUB0jPYJTraFdyEDIjRzPi c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj8FAEjvO1GtJV2Z/2dsb2JhbABChBiDSbQ+AYgsgV4WbQeCLgEELV4BKh05FBIBBBMIAYgKDJtNoEOOXYMXYQOXc49XgwqCKA
X-IronPort-AV: E=Sophos;i="4.84,816,1355097600";  d="scan'208,217";a="182758441"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 10 Mar 2013 02:31:20 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2A2VKl9032605 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sun, 10 Mar 2013 02:31:20 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Sat, 9 Mar 2013 20:31:19 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: IETF-86 WG meeting volunteer request(s)
Thread-Index: Ac4dNz46tbfjftW4QYOifzeZ4EXs5Q==
Date: Sun, 10 Mar 2013 02:31:19 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1849C1FB@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.252.9]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1849C1FBxmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] IETF-86 WG meeting volunteer request(s)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Mar 2013 02:31:21 -0000

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

Hi:

We need volunteers for:

-          Taking the minutes

-          Jabber scribe(s)

Please let the chairs (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ie=
tf.org>) know if you can help out!

For more details on remote participation, see http://www.ietf.org/meeting/8=
6/remote-participation.html.

For the tools agenda (with appropriate links), see http://tools.ietf.org/ag=
enda/86/.


-          Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1849C1FBxmbrcdx04ciscoc_
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:712271556;
	mso-list-type:hybrid;
	mso-list-template-ids:-999794732 -745255350 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:4;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We need volunteers for:<o:p></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]>Taking the minutes<o:p></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]>Jabber scribe(s)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please let the chairs (<a href=3D"mailto:dhc-chairs@=
tools.ietf.org">dhc-chairs@tools.ietf.org</a>) know if you can help out!
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For more details on remote participation, see <a hre=
f=3D"http://www.ietf.org/meeting/86/remote-participation.html">
http://www.ietf.org/meeting/86/remote-participation.html</a>.<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For the tools agenda (with appropriate links), see <=
a href=3D"http://tools.ietf.org/agenda/86/">
http://tools.ietf.org/agenda/86/</a>.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 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]>Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1849C1FBxmbrcdx04ciscoc_--

From jiangsheng@huawei.com  Sat Mar  9 18:35:39 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4208321F8801 for <dhcwg@ietfa.amsl.com>; Sat,  9 Mar 2013 18:35:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tIM6C6ShF-IA for <dhcwg@ietfa.amsl.com>; Sat,  9 Mar 2013 18:35:38 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id E398C21F87EA for <dhcwg@ietf.org>; Sat,  9 Mar 2013 18:35:37 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQL77742; Sun, 10 Mar 2013 02:35:36 +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.1.323.7; Sun, 10 Mar 2013 02:35:14 +0000
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Sun, 10 Mar 2013 02:35:35 +0000
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.156]) by szxeml402-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.007; Sun, 10 Mar 2013 10:35:32 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Questions on draft-ietf-dhc-addr-registration
Thread-Index: AQHOGaIipW7GZMBxhUGrZlANtT26yZiYQXbwgAF3MICAAUdOsP//lvYAgADU6GD//+iRgIAC50HG
Date: Sun, 10 Mar 2013 02:35:30 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923A042F47@szxeml545-mbx.china.huawei.com>
References: <1362488728.1939.104.camel@marcin-lenovo> <5D36713D8A4E7348A7E10DF7437A4B923A03E190@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B3A81@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923A03F87A@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B59C5@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923A0409A5@szxeml545-mbx.china.huawei.com>, <8D23D4052ABE7A4490E77B1A012B6307474B6459@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307474B6459@mbx-01.win.nominum.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.146.42]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Questions on draft-ietf-dhc-addr-registration
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Mar 2013 02:35:39 -0000

>The point is to have the DHCP server do the updates, not to configure the =
client so that it can do the updates.

I still don't get it. For this scenario, DHCPv6 client FQDN option can do t=
he communication between DHCPv6 client and server. The server can do update=
 using DDNS. Where is the missing puzzle that need our extra efford?

Regards,

Sheng=

From Ted.Lemon@nominum.com  Sun Mar 10 06:56:24 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64BE321F85C3 for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 06:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.513
X-Spam-Level: 
X-Spam-Status: No, score=-106.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Vzn6s5shhGU for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 06:56:24 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id EBF1C21F85D6 for <dhcwg@ietf.org>; Sun, 10 Mar 2013 06:56:23 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUTyRB4YxSO4quYBjebWAor1JohXUIWkM@postini.com; Sun, 10 Mar 2013 06:56:23 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 5B4A91080E2 for <dhcwg@ietf.org>; Sun, 10 Mar 2013 06:56:23 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4C00A190043; Sun, 10 Mar 2013 06:56:23 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 10 Mar 2013 06:56:17 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [dhcwg] Questions on draft-ietf-dhc-addr-registration
Thread-Index: AQHOGv4EgZ+jDhjVdE2ob6FYCj2fo5iawieAgADUxwCAAAl8gIAAUpoAgABq4ICAAmIYAIAArXQA
Date: Sun, 10 Mar 2013 13:56:17 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474B9C11@mbx-01.win.nominum.com>
References: <1362488728.1939.104.camel@marcin-lenovo> <5D36713D8A4E7348A7E10DF7437A4B923A03E190@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B3A81@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923A03F87A@szxeml545-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307474B59C5@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923A0409A5@szxeml545-mbx.china.huawei.com>, <8D23D4052ABE7A4490E77B1A012B6307474B6459@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923A042F47@szxeml545-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923A042F47@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A08A51D555372448A39188EF35415FF1@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Questions on draft-ietf-dhc-addr-registration
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Mar 2013 13:56:24 -0000

On Mar 9, 2013, at 9:35 PM, Sheng Jiang <jiangsheng@huawei.com> wrote:
> I still don't get it. For this scenario, DHCPv6 client FQDN option can do=
 the communication between DHCPv6 client and server. The server can do upda=
te using DDNS. Where is the missing puzzle that need our extra efford?

If the client autoconfigured, why is it going to be talking to the DHCP ser=
ver?


From mellon@fugue.com  Sun Mar 10 17:10:59 2013
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B52E21F882E for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 17:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eOJ+fLRBFiqr for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 17:10:58 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 375E121F882D for <dhcwg@ietf.org>; Sun, 10 Mar 2013 17:10:57 -0700 (PDT)
Received: from [192.168.1.3] (19.sub-70-193-203.myvzw.com [70.193.203.19]) by toccata.fugue.com (Postfix) with ESMTPSA id E2C282380C5D for <dhcwg@ietf.org>; Sun, 10 Mar 2013 20:10:55 -0400 (EDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <28309155-DBAB-4CA8-8A25-BBF8721CCC4E@fugue.com>
Date: Sun, 10 Mar 2013 20:10:51 -0400
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [dhcwg] RFC 3315 isn't specific about unknown message types
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 00:10:59 -0000

Bernie and I were tossing some ideas around at the reception today and =
came up with a couple of issues with RFC3315; I'm curious what other =
people think of these points.

Currently the DHCP relay agent is not explicitly required to relay =
messages it doesn't recognize.   It's not advised to drop them either.   =
I think it should be required to relay them.   Has anybody here =
implemented a v6 relay agent?   What did you do about this?

One issue that Bernie came up with was, how does the relay agent =
recognize that it should send a message toward the server or toward the =
client?   I think the answer to this is really easy: the only message =
that a relay sends toward the client is the message it unpacks from a =
relay-reply, because this message has a destination address in the relay =
message header.   All other messages implicitly must be destined for the =
server; nothing else makes sense, because the relay has no other place =
to send them.

As a corollary to this, which I think is obvious, the draft never =
explicitly instructs clients or servers to drop messages with =
unrecognized types.   I think that this is a MUST: servers and clients =
MUST drop messages if they do not recognize the message type.   I =
suspect that implementors are already doing this, and didn't have to =
think about it.

Comments?


From internet-drafts@ietf.org  Sun Mar 10 19:01:38 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF2821F8A2A; Sun, 10 Mar 2013 19:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ns7-1+0fM-Lj; Sun, 10 Mar 2013 19:01:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F48221F8A33; Sun, 10 Mar 2013 19:01:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.42
Message-ID: <20130311020137.28259.41633.idtracker@ietfa.amsl.com>
Date: Sun, 10 Mar 2013 19:01:37 -0700
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-05.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 02:01:38 -0000

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

	Title           : Client Link-layer Address Option in DHCPv6
	Author(s)       : Gaurav Halwasia
                          Shwetha Bhandari
                          Wojciech Dec
	Filename        : draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-05.txt
	Pages           : 7
	Date            : 2013-03-10

Abstract:
   This document specifies the format and mechanism that is to be used
   for encoding client link-layer address in DHCPv6 Relay-Forward
   messages by defining a new DHCPv6 Client Link-layer Address option.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-client-link-layer-ad=
dr-opt

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt=
-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dhcpv6-client-link-layer-=
addr-opt-05


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


From jiangsheng@huawei.com  Sun Mar 10 20:11:01 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C60F21F8920 for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 20:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OGvI96nEvuR6 for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 20:10:59 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4711121F87FF for <dhcwg@ietf.org>; Sun, 10 Mar 2013 20:10:58 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APG01797; Mon, 11 Mar 2013 03:10:57 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 11 Mar 2013 03:10:30 +0000
Received: from SZXEML463-HUB.china.huawei.com (10.82.67.206) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 11 Mar 2013 11:10:56 +0800
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.156]) by szxeml463-hub.china.huawei.com ([10.82.67.206]) with mapi id 14.01.0323.007; Mon, 11 Mar 2013 11:10:51 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <mellon@fugue.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] RFC 3315 isn't specific about unknown message types
Thread-Index: AQHOHezwOMRM9NCsJUqa0K3z/EZdQZifzWsR
Date: Mon, 11 Mar 2013 03:10:50 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923A04335E@szxeml545-mbx.china.huawei.com>
References: <28309155-DBAB-4CA8-8A25-BBF8721CCC4E@fugue.com>
In-Reply-To: <28309155-DBAB-4CA8-8A25-BBF8721CCC4E@fugue.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.152.247]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [dhcwg] RFC 3315 isn't specific about unknown message types
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 03:11:01 -0000

Fully agree that client and server, as the terminal of communication MUST d=
rop recognized message, maybe with a response message to the send. And the =
relay agent should forward the unknown message.

It is very similar to unknown extension header in intermedia router. Brian =
and I are doing a 6man draft to try to define intermedia router, including =
firewalls, should not drop the message with unknown extension header. draft=
-carpenter-6man-ext-transmit

The same catch 22 story will happen: if the intermedia router (relay agent =
in DHCPv6) does not forward for new extension until they are widely deploye=
d. New extension hearder / message cannot be widely deployed until they are=
 be avaible by forwarding.

Forwarding unknown message can make us easier to adopt new stuff in the fut=
ure.

Best regards,

Sheng
________________________________________
From: dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] on behalf of Ted Lemo=
n [mellon@fugue.com]
Sent: 11 March 2013 8:10
To: dhcwg@ietf.org
Subject: [dhcwg] RFC 3315 isn't specific about unknown message types

Bernie and I were tossing some ideas around at the reception today and came=
 up with a couple of issues with RFC3315; I'm curious what other people thi=
nk of these points.

Currently the DHCP relay agent is not explicitly required to relay messages=
 it doesn't recognize.   It's not advised to drop them either.   I think it=
 should be required to relay them.   Has anybody here implemented a v6 rela=
y agent?   What did you do about this?

One issue that Bernie came up with was, how does the relay agent recognize =
that it should send a message toward the server or toward the client?   I t=
hink the answer to this is really easy: the only message that a relay sends=
 toward the client is the message it unpacks from a relay-reply, because th=
is message has a destination address in the relay message header.   All oth=
er messages implicitly must be destined for the server; nothing else makes =
sense, because the relay has no other place to send them.

As a corollary to this, which I think is obvious, the draft never explicitl=
y instructs clients or servers to drop messages with unrecognized types.   =
I think that this is a MUST: servers and clients MUST drop messages if they=
 do not recognize the message type.   I suspect that implementors are alrea=
dy doing this, and didn't have to think about it.

Comments?

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

From akostur@incognito.com  Sun Mar 10 20:36:27 2013
Return-Path: <akostur@incognito.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ECFB21F8697 for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 20:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level: 
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w6pKdkVQ7msI for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 20:36:26 -0700 (PDT)
Received: from na3sys010aog105.obsmtp.com (na3sys010aog105.obsmtp.com [74.125.245.78]) by ietfa.amsl.com (Postfix) with SMTP id 6F95E21F866E for <dhcwg@ietf.org>; Sun, 10 Mar 2013 20:36:25 -0700 (PDT)
Received: from mail-ve0-f197.google.com ([209.85.128.197]) (using TLSv1) by na3sys010aob105.postini.com ([74.125.244.12]) with SMTP ID DSNKUT1ROW7DT45hMOjDviyZMiMi12J3l4SM@postini.com; Sun, 10 Mar 2013 20:36:26 PDT
Received: by mail-ve0-f197.google.com with SMTP id 15so6578058vea.0 for <dhcwg@ietf.org>; Sun, 10 Mar 2013 20:36:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=pUn2/vxtmivnuABQsg1tDCe9nIZc9JV09f5YRafQMBQ=; b=WzRb1ezKbTU3BVa/b3jMjlT7hfUYwFiOddQ/waiONwpGaZLanSZ4E22ZHE8NxbSGA5 5cm7bR7JfO5O10x3hGpzBRDHPrVA/XGNwYlt36D+Xrt6/2BA6rBiLTVDCNl//trNRUlr GOG4eLAAW1dEBv8KujTotN00EPOLqWFDPKc5BAPjsHQ6XFaa8dcLMJ7li/TqvcxYthB4 gxNaxWOAh7nvTcGt9SOtf4nIDS9csJu3hckSB5pwgv2dJEaA3OCvjpTzeyjJ1nJ4t8S1 6Y7Kn4h05f/5DR9GcCkz/cgkgzJCOTEIbfS3WJEZRE2NVSdnlu0ek+iZVuADINLvD/JO dVZg==
X-Received: by 10.58.18.201 with SMTP id y9mr4390091ved.36.1362972985000; Sun, 10 Mar 2013 20:36:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.58.18.201 with SMTP id y9mr4390089ved.36.1362972984884; Sun, 10 Mar 2013 20:36:24 -0700 (PDT)
Received: by 10.220.201.72 with HTTP; Sun, 10 Mar 2013 20:36:24 -0700 (PDT)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923A04335E@szxeml545-mbx.china.huawei.com>
References: <28309155-DBAB-4CA8-8A25-BBF8721CCC4E@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923A04335E@szxeml545-mbx.china.huawei.com>
Date: Sun, 10 Mar 2013 20:36:24 -0700
Message-ID: <CAL10_BrVy3dDMxsCLzA9ArAn46Qn_UxbarMZpismb7CV33HBRw@mail.gmail.com>
From: Andre Kostur <akostur@incognito.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmybePFHZKpCs8eTcAyan2KZyjCEKuMhsmbOsu8Y9HkaQ4CkFK1LrERil6z9MkxY9zhZ0ELyBfy8PTUO7y6AsBkk1BGuSK1Lk4PNYv/nvZpY8PS9aWT/ZP9hpvdm7jbP2nPiFNNv73OjOAGPF8pA3NUFIGTUw==
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] RFC 3315 isn't specific about unknown message types
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 03:36:27 -0000

I agree that it is eminently reasonable.  Take the non-relay reply,
wrap it with a relay forward, send it towards the server.  Take a
relay reply, unwrap it and send it along towards the client.  Servers
and clients ignore messages that they don't understand.

On Sun, Mar 10, 2013 at 8:10 PM, Sheng Jiang <jiangsheng@huawei.com> wrote:
> Fully agree that client and server, as the terminal of communication MUST=
 drop recognized message, maybe with a response message to the send. And th=
e relay agent should forward the unknown message.
>
> It is very similar to unknown extension header in intermedia router. Bria=
n and I are doing a 6man draft to try to define intermedia router, includin=
g firewalls, should not drop the message with unknown extension header. dra=
ft-carpenter-6man-ext-transmit
>
> The same catch 22 story will happen: if the intermedia router (relay agen=
t in DHCPv6) does not forward for new extension until they are widely deplo=
yed. New extension hearder / message cannot be widely deployed until they a=
re be avaible by forwarding.
>
> Forwarding unknown message can make us easier to adopt new stuff in the f=
uture.
>
> Best regards,
>
> Sheng
> ________________________________________
> From: dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] on behalf of Ted Le=
mon [mellon@fugue.com]
> Sent: 11 March 2013 8:10
> To: dhcwg@ietf.org
> Subject: [dhcwg] RFC 3315 isn't specific about unknown message types
>
> Bernie and I were tossing some ideas around at the reception today and ca=
me up with a couple of issues with RFC3315; I'm curious what other people t=
hink of these points.
>
> Currently the DHCP relay agent is not explicitly required to relay messag=
es it doesn't recognize.   It's not advised to drop them either.   I think =
it should be required to relay them.   Has anybody here implemented a v6 re=
lay agent?   What did you do about this?
>
> One issue that Bernie came up with was, how does the relay agent recogniz=
e that it should send a message toward the server or toward the client?   I=
 think the answer to this is really easy: the only message that a relay sen=
ds toward the client is the message it unpacks from a relay-reply, because =
this message has a destination address in the relay message header.   All o=
ther messages implicitly must be destined for the server; nothing else make=
s sense, because the relay has no other place to send them.
>
> As a corollary to this, which I think is obvious, the draft never explici=
tly instructs clients or servers to drop messages with unrecognized types. =
  I think that this is a MUST: servers and clients MUST drop messages if th=
ey do not recognize the message type.   I suspect that implementors are alr=
eady doing this, and didn't have to think about it.
>
> Comments?


--=20
Andre Kostur

From Ted.Lemon@nominum.com  Sun Mar 10 20:46:24 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 584D721F88BF for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 20:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.527
X-Spam-Level: 
X-Spam-Status: No, score=-106.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4kZHDu7v1fm8 for <dhcwg@ietfa.amsl.com>; Sun, 10 Mar 2013 20:46:23 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id C844221F860A for <dhcwg@ietf.org>; Sun, 10 Mar 2013 20:46:23 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUT1Tjwc0F9024BhUUXUh9SN0UkJ3HyvQ@postini.com; Sun, 10 Mar 2013 20:46:23 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 4A36E1B842C for <dhcwg@ietf.org>; Sun, 10 Mar 2013 20:46:23 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 407B4190043; Sun, 10 Mar 2013 20:46:23 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Sun, 10 Mar 2013 20:46:17 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [dhcwg] RFC 3315 isn't specific about unknown message types
Thread-Index: AQHOHezrloux1tmTM02u0V9fjTTs3pigRY8AgAAJ5AA=
Date: Mon, 11 Mar 2013 03:46:16 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474BAC6C@mbx-01.win.nominum.com>
References: <28309155-DBAB-4CA8-8A25-BBF8721CCC4E@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923A04335E@szxeml545-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923A04335E@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5687CE6A55C86848B2C77E567FC62576@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] RFC 3315 isn't specific about unknown message types
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 03:46:24 -0000

On Mar 10, 2013, at 11:10 PM, Sheng Jiang <jiangsheng@huawei.com> wrote:
> Forwarding unknown message can make us easier to adopt new stuff in the f=
uture.

Indeed, that's what Bernie and I were talking about doing... :)


From internet-drafts@ietf.org  Mon Mar 11 00:02:23 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EEF821F86FF; Mon, 11 Mar 2013 00:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.506
X-Spam-Level: 
X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTK3AUTkOvWl; Mon, 11 Mar 2013 00:02:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B58C21F87A3; Mon, 11 Mar 2013 00:02:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.42
Message-ID: <20130311070222.5295.91203.idtracker@ietfa.amsl.com>
Date: Mon, 11 Mar 2013 00:02:22 -0700
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-triggered-reconfigure-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 07:02:23 -0000

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

	Title           : Reconfigure Triggered by DHCPv6 Relay Agents
	Author(s)       : Mohamed Boucadair
                          Xavier Pougnard
	Filename        : draft-ietf-dhc-triggered-reconfigure-04.txt
	Pages           : 12
	Date            : 2013-03-10

Abstract:
   This document defines new DHCPv6 messages: Reconfigure-Request and
   Reconfigure-Reply.  Reconfigure-Request message is sent by a DHCPv6
   relay agent to notify a DHCPv6 server about a configuration
   information change, so that the DHCPv6 server can send a Reconfigure
   message accordingly.  Reconfigure-Reply message is used by the server
   to acknowledge the receipt of Reconfigure-Request.

   This document updates RFC 3315 and RFC 6422.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-triggered-reconfigure-04


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


From iesg-secretary@ietf.org  Mon Mar 11 07:37:19 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66CE621F8C4F; Mon, 11 Mar 2013 07:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZY6tAu7UnsE8; Mon, 11 Mar 2013 07:37:18 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A691921F8C68; Mon, 11 Mar 2013 07:37:17 -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: 4.42
Message-ID: <20130311143717.26361.16981.idtracker@ietfa.amsl.com>
Date: Mon, 11 Mar 2013 07:37:17 -0700
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: 'Client Link-layer Address Option in DHCPv6' to	Proposed Standard	(draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-05.txt)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 14:37:19 -0000

The IESG has approved the following document:
- 'Client Link-layer Address Option in DHCPv6'
  (draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-05.txt) as Proposed
Standard

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

The IESG contact persons are Ralph Droms and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt/




Technical Summary: 

   This document specifies the format and mechanism that is to be used
   for encoding client link-layer address in DHCPv6 Relay-Forward
   messages by defining a new DHCPv6 Client Link-layer Address option.

Working Group Summary: 

   This document was proposed in the working group about a year ago as
   an extension for DHCPv6 clients.  There was concern that it would
   turn into something that would replace DUID and create
   interoperability problems, so the working group developed a rough
   consensus that we should implement this as a relay option instead,
   since this would prevent it being misused to replace DUID.

   Those who disagreed with the consensus, because they would have
   preferred a DHCP client option, went along with this because this
   solution satisfied their actual use case.  They were encouraged to
   try pursuing the client option in the future if they felt it was
   still needed.  This was seen as an acceptable compromise by all the
   dissenters.

Document Quality: 

   I'm not aware of any existing implementations.  This is something
   that a number of enterprise folks have requested, and we expect to
   see implementation in relay agents targeted to those markets.  I
   think everyone who's reviewed the document is mentioned in the
   acknowledgements section.


Personnel: 

   Ted Lemon is the document shepherd.  Ralph Droms is the responsible
   AD.

From iesg-secretary@ietf.org  Mon Mar 11 07:37:19 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 985D521F8C5C for <dhcwg@ietfa.amsl.com>; Mon, 11 Mar 2013 07:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TX4OwZgyvV-S; Mon, 11 Mar 2013 07:37:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AED2021F8C6B; Mon, 11 Mar 2013 07:37:17 -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: IANA <drafts-approval@icann.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.42
X-IETF-Draft-string: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt
X-IETF-Draft-revision: 05
Message-ID: <20130311143717.26361.24205.idtracker@ietfa.amsl.com>
Date: Mon, 11 Mar 2013 07:37:17 -0700
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: 'Client Link-layer Address Option in DHCPv6' to	Proposed Standard	(draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-05.txt)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: noreply@ietf.org
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, 11 Mar 2013 14:37:19 -0000

The IESG has approved the following document:
- 'Client Link-layer Address Option in DHCPv6'
  (draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-05.txt) as Proposed
Standard

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

The IESG contact persons are Ralph Droms and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt/




Technical Summary: 

   This document specifies the format and mechanism that is to be used
   for encoding client link-layer address in DHCPv6 Relay-Forward
   messages by defining a new DHCPv6 Client Link-layer Address option.

Working Group Summary: 

   This document was proposed in the working group about a year ago as
   an extension for DHCPv6 clients.  There was concern that it would
   turn into something that would replace DUID and create
   interoperability problems, so the working group developed a rough
   consensus that we should implement this as a relay option instead,
   since this would prevent it being misused to replace DUID.

   Those who disagreed with the consensus, because they would have
   preferred a DHCP client option, went along with this because this
   solution satisfied their actual use case.  They were encouraged to
   try pursuing the client option in the future if they felt it was
   still needed.  This was seen as an acceptable compromise by all the
   dissenters.

Document Quality: 

   I'm not aware of any existing implementations.  This is something
   that a number of enterprise folks have requested, and we expect to
   see implementation in relay agents targeted to those markets.  I
   think everyone who's reviewed the document is mentioned in the
   acknowledgements section.


Personnel: 

   Ted Lemon is the document shepherd.  Ralph Droms is the responsible
   AD.

From internet-drafts@ietf.org  Mon Mar 11 11:13:19 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5042E11E81F8; Mon, 11 Mar 2013 11:13:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.494
X-Spam-Level: 
X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Cw1QWId5RVA; Mon, 11 Mar 2013 11:13:18 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF0B711E81E4; Mon, 11 Mar 2013 11:13:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.42
Message-ID: <20130311181318.1126.56914.idtracker@ietfa.amsl.com>
Date: Mon, 11 Mar 2013 11:13:18 -0700
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-failover-requirements-03.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 18:13:19 -0000

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

	Title           : DHCPv6 Failover Requirements
	Author(s)       : Tomasz Mrugalski
                          Kim Kinnear
	Filename        : draft-ietf-dhc-dhcpv6-failover-requirements-03.txt
	Pages           : 20
	Date            : 2013-03-11

Abstract:
   The DHCPv6 protocol, defined in [RFC3315] allows for multiple servers
   to operate on a single network, however it does not define any way
   the servers could share information about currently active clients
   and their leases.  Some sites are interested in running multiple
   servers in such a way as to provide increased availability in case of
   server failure.  In order for this to work reliably, the cooperating
   primary and secondary servers must maintain a consistent database of
   the lease information.  [RFC3315] allows for but does not define any
   redundancy or failover mechanisms.  This document outlines
   requirements for DHCPv6 failover, enumerates related problems, and
   discusses the proposed scope of work to be conducted.  This document
   does not define a DHCPv6 failover protocol.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-failover-requirements-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dhcpv6-failover-requireme=
nts-03


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


From internet-drafts@ietf.org  Mon Mar 11 11:18:42 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB7E21F8BF4; Mon, 11 Mar 2013 11:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9M5CdnZZX2N; Mon, 11 Mar 2013 11:18:41 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 53B3121F8BE7; Mon, 11 Mar 2013 11:18:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.42
Message-ID: <20130311181841.24246.56652.idtracker@ietfa.amsl.com>
Date: Mon, 11 Mar 2013 11:18:41 -0700
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dns-pd-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2013 18:18:42 -0000

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

	Title           : Populating the DNS Reverse Tree for DHCP Delegated Prefi=
xes
	Author(s)       : Ted Lemon
	Filename        : draft-ietf-dhc-dns-pd-00.txt
	Pages           : 13
	Date            : 2013-03-11

Abstract:
   This document describes three alternatives for populating the DNS
   reverse tree for prefixes delegated using DHCP, and provides
   mechanisms for implementing each alternative.


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

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


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


From tomasz.mrugalski@gmail.com  Tue Mar 12 04:07:35 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CEEC21F89E5 for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 04:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zIexjbI1+dbi for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 04:07:34 -0700 (PDT)
Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49]) by ietfa.amsl.com (Postfix) with ESMTP id D29C021F89E2 for <dhcwg@ietf.org>; Tue, 12 Mar 2013 04:07:22 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id xa12so4847006pbc.22 for <dhcwg@ietf.org>; Tue, 12 Mar 2013 04:07:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=q1EXBHqJpowsEX45oa+Z9+JBmp5NImC0Ho5FIWLtO2I=; b=vc4xX6qU+R36TOqgwtdOhz9LnKxgOkJGF4u0iervQ7gCQdzpDUoCCXSAN1xKqVE9o1 10asMp6KPKu9XbovqW1NiTmTVEeMzSmDsBkuDXE7y1OakXiNaUuXFsNQtFwcSUnTCSbJ TWqXILLL1lhgZ6jJQbLPRY2BCRqdGTF1/7ZctkUTojP7WgVM8ZKsfyuStfJ4+ZJpGXrz 6jp618YR28j5biLFSvkOwyna+zizMGrwuySy6a10hRO7FsR37e43d2oaOVAU/y4mkbyd Va6oO+aIhi7tbvQvp5yc6C0UZbeCnWTrOYr4QBW/zDlRCOX6oU9mAuBhG/uVr9hK5Xly 9rig==
X-Received: by 10.68.138.135 with SMTP id qq7mr36103599pbb.42.1363086442567; Tue, 12 Mar 2013 04:07:22 -0700 (PDT)
Received: from thomson-osx.local ([2001:df8:0:128:cabc:c8ff:fedf:daff]) by mx.google.com with ESMTPS id rl3sm24563150pbb.28.2013.03.12.04.07.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Mar 2013 04:07:21 -0700 (PDT)
Message-ID: <513F0C66.1040203@gmail.com>
Date: Tue, 12 Mar 2013 07:07:18 -0400
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: sthaug@nethelp.no
References: <E8F6F4C7-074F-4023-80CF-E2C5EA3EF94B@nominum.com> <5096192D.4020000@gmail.com> <20121104.133023.78762705.sthaug@nethelp.no>
In-Reply-To: <20121104.133023.78762705.sthaug@nethelp.no>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-failover-requirements-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 11:07:35 -0000

On 12-11-04 07:30, sthaug@nethelp.no wrote:
> I have read draft-ietf-dhc-dhcpv6-failover-requirements-02 and I support
> this work going forward.
> 
> Some comments on the document:
Hi Steinar,

Thanks a lot for your comments. I have uploaded updated -03 that takes
into consideration all of your points. Sorry it took so long.

Can you check if those changes address your comments?

http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-failover-requirements-03

Just for the reference, your comments with my responses:

> - It's possible section 5.6 "Long lived connections" should be expanded.
> Running DHCPv4 in a failover scenario for our customers, we find that
> customers really like stable addresses - because it lets them publish
> names in DNS (DynDNS etc) and run servers.
> 
> It may also be worth while mentioning that such stable DHCP addresses
> is an explicit non-goal for some SPs who want to prevent customers from
> running servers etc.
Added some text explaining that for stable addresses DNS updates may
happen infrequently and the lease change implies DNS update, which
brings in some delays which, depending on DNS settings, may be quite
large due to caching.

It was also pointed out by Krzysztof Nowicki that many monitoring and
statistics systems work on a per IP basis, so it is awkward to obtain
data for specific device if its IP changes.

Finally, there's a text about changing IP may be non-goal for some ISPs.
I'm not sure if this is the best place to have this text. On one hand it
belongs nicely to the long lived connections, but on the other hand,
there's section 4.1 "Alternatives to failover". I imagine that this
section would be read by many people who are not sure if they need
failover or not.

Anyway, I've put the text in section 5.6 as you suggested.

> - It may be worth while mentioning that section 6.2 "Synchronization
> mechanisms" uses concepts from distributed databases, and that some
> familiarity with distributed databases is useful.
Added.

> - It may be worth while mentioning in section 6.2.1 "Lockstep" that
> the large performance penalty of this method can be decreased by using
> SSDs or similar technologies (this is relevant because SSDs are becoming
> increasingly common).
Added a text about SSD and battery backed ram disks. I think this is the
part of the document that will grow old very fast.

> - It may be worth while mentioning in section 8 "DHCPv6 Failover
> Requirements" points 7 and 8 that such recovery may require manual
> intervention.
Added. I decided to not use normative language (lower case 'may') as I
consider it a clarifying comment to points that already have normative
language ('MUST' in points 7 and 8).

Thanks again for your comments.
Tomek


From sthaug@nethelp.no  Tue Mar 12 05:29:23 2013
Return-Path: <sthaug@nethelp.no>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C3121F8639 for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 05:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXpIzmNRZzIB for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 05:29:22 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 300CF21F8501 for <dhcwg@ietf.org>; Tue, 12 Mar 2013 05:29:21 -0700 (PDT)
Received: (qmail 13786 invoked from network); 12 Mar 2013 12:29:19 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 12 Mar 2013 12:29:19 -0000
Date: Tue, 12 Mar 2013 13:29:19 +0100 (CET)
Message-Id: <20130312.132919.41640929.sthaug@nethelp.no>
To: tomasz.mrugalski@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <513F0C66.1040203@gmail.com>
References: <5096192D.4020000@gmail.com> <20121104.133023.78762705.sthaug@nethelp.no> <513F0C66.1040203@gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-failover-requirements-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 12:29:23 -0000

> Thanks a lot for your comments. I have uploaded updated -03 that takes
> into consideration all of your points. Sorry it took so long.
> 
> Can you check if those changes address your comments?
> 
> http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-failover-requirements-03

I have now read the new document, and I'm happy to report that my
comments have been addressed.

Steinar Haug, AS 2116

From tomasz.mrugalski@gmail.com  Tue Mar 12 05:32:59 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D219A21F8A4A for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 05:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0V5gf6lAp+Vv for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 05:32:59 -0700 (PDT)
Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com [209.85.160.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF0221F8A3D for <dhcwg@ietf.org>; Tue, 12 Mar 2013 05:32:59 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id ro8so4967632pbb.4 for <dhcwg@ietf.org>; Tue, 12 Mar 2013 05:32:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=j0kgqVKroCPn6bdyJExoetWp2OLmng8HQh6o5YmhMho=; b=OTMEXMdONEOkpjX7TvoUcqC4Shh8JofXIPFMHvheiVRGafA9ZK6wZQ9oa/eaf1sX1b cMWvPDwAetvJNtB0/xlTuzc/a0rKUgWeyqJFjDIXjey4JOICa1Qx+9m+YprfFQnBfh7u hEh5frlTcTIwiKv44iqD7//ak3O4/Wf75xo3oEST92NyXvIJVqOIgpepZlq99+I1H3xy xmDqrmfsiq96Qo22R2o36TS0sWKOVir8P+ZR+zI7IgU897CewlHwoRv+SsKkoStqSZoN 7XIjMWh7iv5gzOSSEDO0Q4Ljt3cy5cYwKGQPFCP7XOoj+/EAu560x5RBYVkl/VjpOeeO +cmQ==
X-Received: by 10.68.196.168 with SMTP id in8mr36532755pbc.61.1363091579098; Tue, 12 Mar 2013 05:32:59 -0700 (PDT)
Received: from thomson-osx.local ([2001:df8:0:128:cabc:c8ff:fedf:daff]) by mx.google.com with ESMTPS id i10sm24887615pbd.1.2013.03.12.05.32.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Mar 2013 05:32:58 -0700 (PDT)
Message-ID: <513F2077.2020303@gmail.com>
Date: Tue, 12 Mar 2013 08:32:55 -0400
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: sthaug@nethelp.no
References: <5096192D.4020000@gmail.com> <20121104.133023.78762705.sthaug@nethelp.no> <513F0C66.1040203@gmail.com> <20130312.132919.41640929.sthaug@nethelp.no>
In-Reply-To: <20130312.132919.41640929.sthaug@nethelp.no>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-failover-requirements-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 12:32:59 -0000

On 13-03-12 08:29, sthaug@nethelp.no wrote:
>> http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-failover-requirements-03
> 
> I have now read the new document, and I'm happy to report that my
> comments have been addressed.
That was quick. Thanks a lot.

Tomek


From msiodelski@gmail.com  Tue Mar 12 12:43:13 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E2451F0C36 for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 12:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VT474HXftS86 for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 12:43:12 -0700 (PDT)
Received: from mail-pb0-f51.google.com (mail-pb0-f51.google.com [209.85.160.51]) by ietfa.amsl.com (Postfix) with ESMTP id 055A111E8121 for <dhcwg@ietf.org>; Tue, 12 Mar 2013 12:43:10 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id un15so208223pbc.10 for <dhcwg@ietf.org>; Tue, 12 Mar 2013 12:43:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:subject:from:to:cc:date:content-type:x-mailer :mime-version:content-transfer-encoding; bh=/GHw/xMD1mgg6kXyCi0eAGZqou2NwOyfrNSj6tsXD+I=; b=ajRwWYfRW2u1JLcd9vW4O82G5pQF9mCIdkkS/2gv5S2KJ32/8AOkx61VI5nbjI2T8k yvP7I5EdgC7FL4+MuveIUazrjw5Frs/AFs0ERdl+ZBYetT5wJJpa6RWnWyu/7vGMo6dI yZZnEGFwa3QqNi0X4dV/0yRN/Om1wRJd3OdK4FXBJM0pe277jzjK7h8NON5BifW/87br W+t4W/v6gujIN0TDjwcVLo8+e0WerfRqXZdJQ9qkjo2kBE6DTeBlicVqym6FwAL6noQf hXzUju+pUMSr/Gj6EaUtG7TOc2IrQZtPxnLxBscFk1RWs51LEk+WvyDS1gYKYklztpnV y00g==
X-Received: by 10.68.213.66 with SMTP id nq2mr39265464pbc.29.1363117390388; Tue, 12 Mar 2013 12:43:10 -0700 (PDT)
Received: from ?IPv6:2001:df8:0:128:120b:a9ff:fe7b:e3f0? ([2001:df8:0:128:120b:a9ff:fe7b:e3f0]) by mx.google.com with ESMTPS id iu10sm26263629pbc.13.2013.03.12.12.43.06 (version=SSLv3 cipher=RC4-SHA bits=128/128); Tue, 12 Mar 2013 12:43:08 -0700 (PDT)
Message-ID: <1363117384.2123.64.camel@marcin-lenovo>
From: Marcin Siodelski <msiodelski@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Tue, 12 Mar 2013 15:43:04 -0400
Content-Type: text/plain; charset="ISO-8859-15"
X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Cc: kkinnear@cisco.com
Subject: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-failover-design-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 19:43:13 -0000

Hi, 

I have read the version -02 of the draft. This is a useful work and I
support it move forward.

Some first round of comments...

2. Glossary:
- The "Failover transmission" is defined in the glossary but it is used
nowhere in the draft. Perhaps you meant "Failover communication" which is
common in the text.

3. Introduction
- The document says that the failover protocol is not suitable for lease
times shorter than 30sec. Then, is it suitable for lease times of 31s?
Why is that arbitrary number selected? I believe that the document
should simply mention that there is an additional overhead on the server 
related to failover transmission (that would justify use of this term in 
the glossary) and thus it is not efficient for short lease times.

3.1. Perhaps, it is worth to replace the title from "Additional
Requirements" with "Design Requirements" to indicate that it is not
extending the protocol requirements described elsewhere.

4. Protocol Overview
- The hyperlink to "Section 5.1 of DHCPv6 Bulk Leasequery [RFC5460]" is
broken because clicking on "Section 5.1" takes you to the section 5.1 in
the local document.

- Is it worth to mention that if the primary server can't establish
communication with the secondary server (because secondary is down) it
will attempt to connect with the implementation dependent interval?

4.1. Failover State Machine Overview
- It is not clear what the state the partner goes to, when the
DISCONNECT occurs. I presume it is PARTNER-DOWN state but the document
should clarify it.

- Here is a sentence: "In case of a disagreement between the simplified
and complete description, please follow Section 9". I think that there
must be no "disagreement" between those two sections. The one provides a
supplementary information for the other but they should remain
consistent in the common part.

- I don't understand the purpose of: "It frequently returns back to the
state it was in before shutdown". Perhaps, some context needs to be
provided for it?

- In the 4th paragraph "in unresponsive" should be replaced with "is
unresponsive". However, I am wondering if it is correct given that
extensions may introduce "active-active" mode in which this is not true
anymore. Perhaps, it could be mentioned that "assuming that failover
pair is in the active-passive mode, the secondary server is unresponsive
when in NORMAL state". 

- A bit of clarification would be needed on what the "auto-partner-down"
is - glossary? Is this that the server bypasses the
COMMUNICATION-INTERRUPTED state and goes straight to PARTNER-DOWN or it
goes to COMMUNICATION-INTERRUPTED state then to PARTNER-DOWN? If the
latter is the case, then would it state in the COMMUNICATION-INTERRUPTED
state for a while, trying to reconnect?

- I don't understand what is meant by "When a server does not have an
intact lease state database (e.g. due to first time run or catastrophic
failure) ..."? First of all, is the lease state data base the database
which holds leases or it holds some additional information about the
server state prior to the failure, which can be used to determine that
the catastrophic failure occured? Also, the "doesn't have an intact
lease state database" formulation is misleading because I think that the
server on its first time DOES have the intact database.

- The RECOVER-WAIT to RECOVER-DONE transition could be better described.
Specifically, what condition it is triggered by?

- Is there any way out from the RESOLUTION-INTERRUPTED? If the
communication is reestablished I presume that both servers continue
resolving conflicts?

4.2. Messages
- I suggest that the following description of the CONNECT message:
"The partner is expected to confirm by responding with CONNECTACK" is
reworded to "The partner MUST confirm by responding with CONNECT ACK".

- Perhaps, the same applies to some other types of messages but I did not
check that thoroughly enough to put this into this review.

- Minor: it would be easier to search for the specific message
description if the messages were ordered alphabetically. 

- The POOLRESP is used everywhere throughout the document, while it is
called "POOLRSP" in the list of messages.


5.1. Creating Connections
- "If it has no secondary relationships with the connecting server, it
SHOULD drop the connection". This sentence suggests that the secondary
server will not respond to the initiating server if it has no
relationship with it. A couple of paragraphs earlier, it was said the
server "is expected" or MUST respond with CONNECTACK. I suggest that it
is reworded to explain that the server MUST reject the connection by
sending the CONNECTACK with the reason for rejection instead of
"dropping".

6.1. Proportional Allocation
- The paragraph which starts with "The initial allocation when..." is
confusing. If I understand correctly, the POOLRESP is devoted to deliver
the actual resources to the secondary server. The document says that it
is to inform a secondary server "how many resources it allocated". This
doesn't sound to be the same.

- I am wondering why at all, the POOLREQ/POOLRESP exchange has to be
initiated by the secondary server. In the scenario where the failover
configuration is handled through the primary server it is primary server
who should notify the secondary that the (for example) pool balance has
been changed. This implies the primary could initiate the exchange by
notifying the secondary server that the rebalancing will start now.
On the other hand in the "Proportional Allocation" scenario the rebalancing
may be started when the secondary has returned addresses to the primary
which had been released by the client. However, in such case the primary
should also be aware of the need to rebalance and could also start the
rebalancing procedure. So again, I don't understand why the secondary is
starting the rebalancing procedure here?

- Another related question: is this really required to do an extra
POOLREQ/POOLRESP exchange while the actual transfer of addresses is
later done via BNDUPD/BNDACK? What extra information will
be carried in the POOLREQ/POOLRESP messages that needs to be delivered
prior to sending BNDUPD/BNDACK which actually delegate resources by
modifying state FREE to FREE_BACKUP or the other way around?

- "...and the secondary server is responsible for being configured in
such a way". Well, the server is not responsible for anything.
Administrator might be responsible to configure the server, the
developer is responsible to ensure the proper implementation, but the
server is not responsible...

6.2. Independent Allocation
- It is mentioned that the resources are allocated/split as a part of
initial connection establishment. How? Specifically, are resources
delegated to the secondary server using the same messages as used for
"Proportional Allocation"?  If so, what happens if the primary server
requests reallocation of resources later on? Is this rejected by the
primary server? Is this request dropped?

6.3. Choosing Allocation Algorithm
- Typo in "indepentent".

7. Information Model
- Instead of referring to "DHCP RFC" the link to the actual RFC along
with its number should be provided.

- Typo in "untile"

8. Failover Mechanisms
- The last sentence is redundant as the previous one says pretty much
the same.

8.4. MCLT Concept
- The paragraph which starts with "The fundamental relationship
which..." is a little bit obscure. I suggest that it is reworded to
something like: "The fundamental relationship on which much of the
correctness of this protocol depends is that the lease expiration time
known to DHCPv6 client MUST NOT be greater by more than MCLT, than the
potential expiration time known to a server's partner. 


8.10. Acknowledging Reception
- This section is empty. At least TBD would be useful. Otherwise it suggests
that this part has been accidentally omitted. 

9.1. State Machine Operation
-  One additional event that may cause transition from one state to
another is probably administrator's intervention?

9.3.2. Transition Out of Startup State
- The part that describes Step 2 is intricate. I read it a couple of
times and I still don't feel I understand it. Perhaps, it could be split
into a couple of simpler sentences.

9.4. PARTNER-DOWN State
- It may be worth to give a hint how the server may end-up being in this
state. Most likely it is because his partner had stopped responding.
However, in this case they are in the COMMUNICATION-INTERRUPTED state
and there is some other event (what?) that needs to occur to transition
to the PARTNER-DOWN state.

9.11. RESOLUTION-INTERRUPTED
- In the introduction to this chapter it is pointed out that if the
server's remained in the POTENTIAL-CONFLICT state and the resolution of
the conflict was interrupted, they transition to RESOLUTION-INTERRUPTED
and they are unresponsive to clients (I presume this is because they
were unresponsive when being in POTENTIAL-CONFLICT state and the
conflict is still assumed to be present). If you take a look at the
9.11.1. it is said that the server MUST respond to all DHCP client
requests. That looks contrary to the previous statement. My
understanding is that the server can't respond in the
RESOLUTION-INTERRUPTED state thus it requires administrative
intervention.

Cheers,
Marcin




From tomasz.mrugalski@gmail.com  Tue Mar 12 13:25:30 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D901411E8176 for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 13:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4cqQzyx4dhej for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 13:25:28 -0700 (PDT)
Received: from mail-da0-x236.google.com (mail-da0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 2EAE111E8163 for <dhcwg@ietf.org>; Tue, 12 Mar 2013 13:25:26 -0700 (PDT)
Received: by mail-da0-f54.google.com with SMTP id p1so87635dad.41 for <dhcwg@ietf.org>; Tue, 12 Mar 2013 13:25:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; bh=+DX/j0Pr1Ln+hcKyE2GoWfEyHXGF6AskgQuVnGV8g9w=; b=s1zEUCdkr3yqya0rwqwvC/clXzUNMjCv01DOdQx1ejXjIdNyVx0YPkPt00nyxwCI6p yDB0dTsiMV913ilAMGk/Pnr+F/plUOyG9dgqlIv+GkM52QooX/r6u2no4FdhvjByrrNQ PNhUJc8XUpbTXMRI3NXI8R6bsvc0O08zUuRsIV2dUptUnfP2GDtIcZqLoOsUX15rVcXX 8239rQFOP9lufHNj2gYruoJwUcNl07/oyCvj47iH9LZH0+x7xCq1qhSG7/wJRZ6TPvtp b6u0DKk4rmb9lUfHicZwKBMdaGcyQdgGmqQ205z5Jnfj//UkJxqbVj5p0JS95FspShWr 3ZFA==
X-Received: by 10.68.232.162 with SMTP id tp2mr39602052pbc.192.1363119925692;  Tue, 12 Mar 2013 13:25:25 -0700 (PDT)
Received: from thomson-osx.local ([2001:df8:0:128:cabc:c8ff:fedf:daff]) by mx.google.com with ESMTPS id iu10sm26391742pbc.13.2013.03.12.13.25.24 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Mar 2013 13:25:25 -0700 (PDT)
Message-ID: <513F8F32.6080807@gmail.com>
Date: Tue, 12 Mar 2013 16:25:22 -0400
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: DHC WG <dhcwg@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Social ticket available
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 20:25:30 -0000

Please ignore if you're not currently in Orlando.

I'm terribly sorry for sending this to the DHC, not 86attendees list.
I just thought that sending it here could be a small extra benefit of
being subscribed to DHC list. :)

Contact me off the list if interested.

Tomek

From brian@innovationslab.net  Tue Mar 12 15:28:20 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38C4911E816D for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 15:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iqs5g5lISnnl for <dhcwg@ietfa.amsl.com>; Tue, 12 Mar 2013 15:28:19 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id BFC9411E80FF for <dhcwg@ietf.org>; Tue, 12 Mar 2013 15:28:19 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id A4A4D8812B; Tue, 12 Mar 2013 15:28:19 -0700 (PDT)
Received: from dhcp-51ca.meeting.ietf.org (dhcp-51ca.meeting.ietf.org [130.129.81.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 347F5136823B; Tue, 12 Mar 2013 15:28:19 -0700 (PDT)
Message-ID: <513FAC01.8080200@innovationslab.net>
Date: Tue, 12 Mar 2013 18:28:17 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <513E28D9.5050303@innovationslab.net>
In-Reply-To: <513E28D9.5050303@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>
Subject: [dhcwg] DHC Review of draft-ietf-6man-addr-select-opt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Mar 2013 22:28:20 -0000

Hi all,

      I would like to ask the members of DHC to review 
draft-ietf-6man-addr-select-opt document. Based on a review by Ted 
Lemon, Tomek Mrugalski, and Bernie Volz, the following issues were raised:

1. The text regarding the prefix in the OPTION_ADDRSEL_TABLE option 
needs to be improved - it currently allows someone to send all 16 octets 
rather than the "minimum" required - int(prefix-len+7)/8). Please see 
http://datatracker.ietf.org/doc/draft-ietf-dhc-option-guideline, 5.3. 
Option with IPv6 prefix.

2. Section 3 should be dropped. This is a standard "other configuration 
option" and the client and server requirements for these are best left 
to RFC 3315. The current text has some mistakes and omissions if it were 
to duplicate what RFC 3315 already explains, and doing so risks 
inconsistencies, omissions, or conflicts which are best avoided.

Others are encouraged to look at the document and raise any additional 
concerns they may have regarding this work.  I would like to have 
comments by 2013-03-26.

https://datatracker.ietf.org/doc/draft-ietf-6man-addr-select-opt/

Regards,
Brian

From otroan@employees.org  Wed Mar 13 07:07:27 2013
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 816D121F8D9A for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 07:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tqfgOWA6JgOa for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 07:07:26 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) by ietfa.amsl.com (Postfix) with ESMTP id EA63221F8D90 for <dhcwg@ietf.org>; Wed, 13 Mar 2013 07:07:26 -0700 (PDT)
Received: from dhcp-10-61-103-142.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id CED971707D9 for <dhcwg@ietf.org>; Wed, 13 Mar 2013 07:07:25 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <513FAC01.8080200@innovationslab.net>
Date: Wed, 13 Mar 2013 10:07:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD9B1458-0674-4CBB-94E4-2D6DA0B75B67@employees.org>
References: <513E28D9.5050303@innovationslab.net> <513FAC01.8080200@innovationslab.net>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1499)
Subject: Re: [dhcwg] DHC Review of draft-ietf-6man-addr-select-opt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 14:07:27 -0000

>    I would like to ask the members of DHC to review =
draft-ietf-6man-addr-select-opt document. Based on a review by Ted =
Lemon, Tomek Mrugalski, and Bernie Volz, the following issues were =
raised:
>=20
> 1. The text regarding the prefix in the OPTION_ADDRSEL_TABLE option =
needs to be improved - it currently allows someone to send all 16 octets =
rather than the "minimum" required - int(prefix-len+7)/8). Please see =
http://datatracker.ietf.org/doc/draft-ietf-dhc-option-guideline, 5.3. =
Option with IPv6 prefix.

take the option-guideline text verbatim.

> 2. Section 3 should be dropped. This is a standard "other =
configuration option" and the client and server requirements for these =
are best left to RFC 3315. The current text has some mistakes and =
omissions if it were to duplicate what RFC 3315 already explains, and =
doing so risks inconsistencies, omissions, or conflicts which are best =
avoided.
>=20
> Others are encouraged to look at the document and raise any additional =
concerns they may have regarding this work.  I would like to have =
comments by 2013-03-26.

I agree with Brian's suggested changes.

cheers,
Ole=

From trac+dhc@trac.tools.ietf.org  Mon Mar 11 13:17:02 2013
Return-Path: <trac+dhc@trac.tools.ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2D1221F8FDD for <dhcwg@ietfa.amsl.com>; Mon, 11 Mar 2013 13:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44DMO9kZCHDl for <dhcwg@ietfa.amsl.com>; Mon, 11 Mar 2013 13:17:01 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 273C121F8E09 for <dhcwg@ietf.org>; Mon, 11 Mar 2013 13:17:01 -0700 (PDT)
Received: from localhost ([127.0.0.1]:41630 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+dhc@trac.tools.ietf.org>) id 1UF99Q-00032q-H8; Mon, 11 Mar 2013 21:16:52 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "dhc issue tracker" <trac+dhc@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: volz@cisco.com
X-Trac-Project: dhc
Date: Mon, 11 Mar 2013 20:16:52 -0000
X-URL: http://tools.ietf.org/wg/dhc/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/dhc/trac/ticket/23#comment:1
Message-ID: <072.96a6c08cbdc3718b83625d44eee07318@trac.tools.ietf.org>
References: <057.b22c918e0f518d4acfed62eb2d2914dd@trac.tools.ietf.org>
X-Trac-Ticket-ID: 23
In-Reply-To: <057.b22c918e0f518d4acfed62eb2d2914dd@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: volz@cisco.com, dhcwg@ietf.org
X-SA-Exim-Mail-From: trac+dhc@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
X-Mailman-Approved-At: Wed, 13 Mar 2013 07:10:25 -0700
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] [dhc] #23: WG last call for draft-ietf-dhc-dhcpv4-vendor-message
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: dhcwg@ietf.org
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, 11 Mar 2013 20:17:02 -0000

#23: WG last call for draft-ietf-dhc-dhcpv4-vendor-message

Changes (by volz@cisco.com):

 * status:  new => closed
 * resolution:   => wontfix
 * severity:  In WG Last Call => Dead WG Document


Comment:

 This document did not pass WG last call as the WG did not think this was a
 useful capability.

-- 
-----------------------------------+----------------------
 Reporter:  rdroms@cisco.com       |       Owner:
     Type:  state                  |      Status:  closed
 Priority:  major                  |   Milestone:
Component:  dhcpv4-vendor-message  |     Version:
 Severity:  Dead WG Document       |  Resolution:  wontfix
 Keywords:                         |
-----------------------------------+----------------------

Ticket URL: <http://tools.ietf.org/wg/dhc/trac/ticket/23#comment:1>
dhc <http://tools.ietf.org/wg/dhc/>


From msiodelski@gmail.com  Wed Mar 13 07:19:27 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2775A21F84A1 for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 07:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aVcTE+7tHbK8 for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 07:19:26 -0700 (PDT)
Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) by ietfa.amsl.com (Postfix) with ESMTP id 802BD21F852A for <dhcwg@ietf.org>; Wed, 13 Mar 2013 07:19:26 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rp2so1066846pbb.6 for <dhcwg@ietf.org>; Wed, 13 Mar 2013 07:19:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:x-mailer:mime-version :content-transfer-encoding; bh=6s4bwpYyr5WLJWoVh/bLUDjwhDnXtH1g8SOOzKDames=; b=OmHRIyvSIRNh+ZwvjidHozWAH/2cjYoygY2bmsptSeGl/dqZtM8mkfr1zTTa/YgTwh gy326GhGAKjWJPVOrCDoeYjlfrwbYZ6JJWS7H4dywwxyDll3sBz0hC8zBOF9GAjn6Hoj X7ZHADo8+FnxCZYOwjHaOLP3uwphXHpLftF13CdwOjUOA0SCVjWNLu1+p5/Z6q2gVzye O41ba6z+JsZffLN6iMbULJ3Yv0flnNVjHduPwSE4wku1mY4U21uXoEFCN0mmwO7I4SVx eQ3k+9MiJ2NfJZJhsQLpQxduW0/6qmZCSLl/qvXSJ+ti995fDv6pf+QaDdtqVsyuu+8D +bcg==
X-Received: by 10.68.201.227 with SMTP id kd3mr45489127pbc.65.1363184366269; Wed, 13 Mar 2013 07:19:26 -0700 (PDT)
Received: from ?IPv6:2001:df8:0:16:120b:a9ff:fe7b:e3f0? ([2001:df8:0:16:120b:a9ff:fe7b:e3f0]) by mx.google.com with ESMTPS id ol7sm29826974pbb.14.2013.03.13.07.19.22 (version=SSLv3 cipher=RC4-SHA bits=128/128); Wed, 13 Mar 2013 07:19:24 -0700 (PDT)
Message-ID: <1363184361.2123.99.camel@marcin-lenovo>
From: Marcin Siodelski <msiodelski@gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Date: Wed, 13 Mar 2013 10:19:21 -0400
In-Reply-To: <513FAC01.8080200@innovationslab.net>
References: <513E28D9.5050303@innovationslab.net> <513FAC01.8080200@innovationslab.net>
Content-Type: text/plain; charset="ISO-8859-15"
X-Mailer: Evolution 3.6.3 (3.6.3-2.fc18) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, dhcwg@ietf.org, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>
Subject: Re: [dhcwg] DHC Review of draft-ietf-6man-addr-select-opt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 14:19:27 -0000

On Tue, 2013-03-12 at 18:28 -0400, Brian Haberman wrote:
> Hi all,
> 
>       I would like to ask the members of DHC to review 
> draft-ietf-6man-addr-select-opt document. Based on a review by Ted 
> Lemon, Tomek Mrugalski, and Bernie Volz, the following issues were raised:
> 

In the section 5 (Implementation Considerations) the last bullet is
redundant because the problem of large number of rules has been
addressed by the previous bullet.

Marcin





From cas@trans-nt.com  Wed Mar 13 11:18:26 2013
Return-Path: <cas@trans-nt.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 916C221F8EBE for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 11:18:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.233
X-Spam-Level: 
X-Spam-Status: No, score=-0.233 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T5VgHM2NqE+w for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 11:18:26 -0700 (PDT)
Received: from dump.fs.trans-nt.com (smtp.trans-nt.co.jp [202.10.98.251]) by ietfa.amsl.com (Postfix) with SMTP id A7CE421F8E8E for <dhcwg@ietf.org>; Wed, 13 Mar 2013 11:18:25 -0700 (PDT)
Received: (qmail 15967 invoked from network); 14 Mar 2013 03:18:21 +0900
Received: from red.fs.trans-nt.co.jp (HELO dhcp-524e.meeting.ietf.org) (202.10.98.240) by smtp.trans-nt.co.jp with SMTP; 14 Mar 2013 03:18:21 +0900
Message-ID: <5140C2EB.6060707@trans-nt.com>
Date: Thu, 14 Mar 2013 03:18:19 +0900
From: Hiroki Nakano <cas@trans-nt.com>
Organization: cas authorized 53a6c6e30f1471298320e605c741e412
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com>
In-Reply-To: <511B85B3.8030705@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 18:18:26 -0000

I talked with Volz and Tomek yesterday and we also agree
that DHCPv4 with Rapid Commit Option has no problem
for IPv4 configuration by one round trip exchange of packets.
DHCPv6 has a little missing part related to default route,
but another idea using RS and RA solves this as Alex mentioned.
Other potential problems are DAD and M-flag of RA, but we have
Optimistic DAD mechanism and Volz pointed out that DHCPv6 could
be used without RA.  However, I recognize that dhcpv6-route-option
has some difficulty to reach a consensus in IETF.

Bacause 802.11ai is just one of "specific link layer",
I'm not sure this working group is suitable for discussion
about implementation issues related to DHCPv4 and 802.11ai,
(at least, not for RS and RA...)
but if anyone having interests in this topic, I'd like to
talk about this topic after the dhcwg session informally
and please let me hear your comments.
Especially, I am wondering who decides detailed use of DHCPv4 on
802.11ai, IEEE people or IETF people? and who should write
specification for it as an 802.11 document or as a RFC?
if you are writing I-D for this topic, which working group
will you submit to? dhc? 6man? v6ops??, etc...
Of course, technical topics are welcome.

Regards,

Hiroki Nakano
Trans New Technology, Inc. <cas@trans-nt.com>



(13/02/13 21:23), Alexandru Petrescu wrote:
> Le 12/02/2013 21:25, Hiroki Nakano a Ã©crit :
>> Dear all,
>>
>> I'm participating in IEEE 802.11 WG TGai task group which is for
>> FILS (Fast Initiali Link Setup). They are working for speeding up of
>> 802.11 process and trying to provide a new framework for higher
>> layer protocols.
>>
>> I'd like to introduce the overview of prospective 802.11ai
>> specification and discuss usages of DHCP on it with DHC WG people in
>> March. The followings are a brief introduction.
>>
>> TGai supposes Wireless LAN is used in very crowded envirionment such
>> as railway stations in a giant metropolis. TGai also supposes moving
>> hosts through the front of Access Points. In these cases, it is
>> effective to reduce management frames of 802.11, especially frames
>> for probing APs, authentication and association. The current
>> framework takes a few seconds to set up network connectivity before
>> starting to communicate. The target of TGai is under one second.
>>
>> TGai is trying to reduce management frames of 802.11 itself, and in
>> addition provide framework for higher layers such as IP to send and
>> receive packets during 802.11 association process. The currently
>> proposed framework provides "ONE round-trip packet exchange" by
>> piggybacking on 802.11 Association Request/Response frames.
>>
>> My interest is how to fit DHCP to this framework. In case of DHCPv4,
>> this is achieved by using Rapid Commit Option (RFC4039) and making
>> some additional and trivial rules. In case of DHCPv6, we have to use
>> both RA and DHCPv6. In addition, DAD and randomly generated
>> addresses have to be considered. Share your idea, please.
>
> For DHCPv6 - it is possible to use a DHCPv6 single roundtrip to realize
> complete configuration to the Client (IPv6 address, default route, DNS
> resolver address).
>
> The straightforward means to achieve complete configuration is to use RA
> _and_ DHCP (because only RA provides the default route), for a total of
> 6 messages .
>
> But the better means (single DHCPv6 roundtrip - 2 messages) is to use
> DHCPv6 to configure the default route as well, and not use RA:
> draft-ietf-mif-dhcpv6-route-option-05 "DHCPv6 Route Options" and
> draft-mouton-mif-dhcpv6-drlo-02.txt "Default Router List Option for
> DHCPv6 (DRLO)"
>
> Alternatively, use RS/RA single exchange (and not DHCPv6), with DNS
> resolver address:
> RFC6106 "IPv6 Router Advertisement Options for DNS Configuration"
>
> DAD and MLD are two other protocols which may get in the way to fast
> exchanges.  They could be avoided with proper tweaking of specification
> and implementation.
>
>> 802.11 TGai is still going on and its specification is subject to
>> change, but I'd like to discuss in IETF DHCP issues related to
>> 802.11ai and arrange I-D according to the progress of TGai task
>> group.
>
> I think it is indeed a good point to discuss such an I-D.
>
> Alex
>
>>
>> Regards,
>>
>> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
>>
>> _______________________________________________ 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 volz@cisco.com  Wed Mar 13 11:25:19 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 666E321F8D5B for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 11:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXyT9EfOZb+k for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 11:25:18 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id A64AB21F8B71 for <dhcwg@ietf.org>; Wed, 13 Mar 2013 11:25:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5441; q=dns/txt; s=iport; t=1363199117; x=1364408717; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=AwvCSCByGJgRc/pVIAkAydMDpyn/lNhY1+3r9I59QrU=; b=eC+v6PXcD2Upevr6Hrl29DNPw6UbujS5FhBxHj/hWJmCSkwoBX4gTZOX bHg07k3aUB88avvIPwiw34kuXWf5bMf3Fb0vD4RACl4b5vkQ8AQK23X8O RxiCxLuy3F6sHta5AUexciXwd4DTwcgrK+Dar7/UMwUXrDh3Ji3J1oWT3 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAPrCQFGtJXG//2dsb2JhbABDxFmBWRZ0gioBAQEDAQEBAWsLBQsCAQgOCi4nCyUCBA4FiA4GDMMJEwSOWjMHgl9hA4g9jhmQdoMK
X-IronPort-AV: E=Sophos;i="4.84,838,1355097600"; d="scan'208";a="187092824"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-2.cisco.com with ESMTP; 13 Mar 2013 18:25:16 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2DIPGbo008603 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Mar 2013 18:25:16 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Wed, 13 Mar 2013 13:25:05 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Hiroki Nakano <cas@trans-nt.com>
Thread-Topic: [dhcwg] IEEE 802.11ai and DHCP
Thread-Index: AQHOIBc4Dr+VanOVykm056tro9m7cpij7/xs
Date: Wed, 13 Mar 2013 18:25:05 +0000
Message-ID: <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com>,<5140C2EB.6060707@trans-nt.com>
In-Reply-To: <5140C2EB.6060707@trans-nt.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 18:25:19 -0000

There may also be some areas to explore further - such as what happens if t=
here are multiple DHCP servers or if Rapid Commit is not allowed and how th=
at plays into this. But it likely is just a minor issue as the first respon=
se may be optimized but additional are forwarded to client normally,

- Bernie

On Mar 13, 2013, at 2:18 PM, "Hiroki Nakano" <cas@trans-nt.com> wrote:

> I talked with Volz and Tomek yesterday and we also agree
> that DHCPv4 with Rapid Commit Option has no problem
> for IPv4 configuration by one round trip exchange of packets.
> DHCPv6 has a little missing part related to default route,
> but another idea using RS and RA solves this as Alex mentioned.
> Other potential problems are DAD and M-flag of RA, but we have
> Optimistic DAD mechanism and Volz pointed out that DHCPv6 could
> be used without RA.  However, I recognize that dhcpv6-route-option
> has some difficulty to reach a consensus in IETF.
>=20
> Bacause 802.11ai is just one of "specific link layer",
> I'm not sure this working group is suitable for discussion
> about implementation issues related to DHCPv4 and 802.11ai,
> (at least, not for RS and RA...)
> but if anyone having interests in this topic, I'd like to
> talk about this topic after the dhcwg session informally
> and please let me hear your comments.
> Especially, I am wondering who decides detailed use of DHCPv4 on
> 802.11ai, IEEE people or IETF people? and who should write
> specification for it as an 802.11 document or as a RFC?
> if you are writing I-D for this topic, which working group
> will you submit to? dhc? 6man? v6ops??, etc...
> Of course, technical topics are welcome.
>=20
> Regards,
>=20
> Hiroki Nakano
> Trans New Technology, Inc. <cas@trans-nt.com>
>=20
>=20
>=20
> (13/02/13 21:23), Alexandru Petrescu wrote:
>> Le 12/02/2013 21:25, Hiroki Nakano a =E9crit :
>>> Dear all,
>>>=20
>>> I'm participating in IEEE 802.11 WG TGai task group which is for
>>> FILS (Fast Initiali Link Setup). They are working for speeding up of
>>> 802.11 process and trying to provide a new framework for higher
>>> layer protocols.
>>>=20
>>> I'd like to introduce the overview of prospective 802.11ai
>>> specification and discuss usages of DHCP on it with DHC WG people in
>>> March. The followings are a brief introduction.
>>>=20
>>> TGai supposes Wireless LAN is used in very crowded envirionment such
>>> as railway stations in a giant metropolis. TGai also supposes moving
>>> hosts through the front of Access Points. In these cases, it is
>>> effective to reduce management frames of 802.11, especially frames
>>> for probing APs, authentication and association. The current
>>> framework takes a few seconds to set up network connectivity before
>>> starting to communicate. The target of TGai is under one second.
>>>=20
>>> TGai is trying to reduce management frames of 802.11 itself, and in
>>> addition provide framework for higher layers such as IP to send and
>>> receive packets during 802.11 association process. The currently
>>> proposed framework provides "ONE round-trip packet exchange" by
>>> piggybacking on 802.11 Association Request/Response frames.
>>>=20
>>> My interest is how to fit DHCP to this framework. In case of DHCPv4,
>>> this is achieved by using Rapid Commit Option (RFC4039) and making
>>> some additional and trivial rules. In case of DHCPv6, we have to use
>>> both RA and DHCPv6. In addition, DAD and randomly generated
>>> addresses have to be considered. Share your idea, please.
>>=20
>> For DHCPv6 - it is possible to use a DHCPv6 single roundtrip to realize
>> complete configuration to the Client (IPv6 address, default route, DNS
>> resolver address).
>>=20
>> The straightforward means to achieve complete configuration is to use RA
>> _and_ DHCP (because only RA provides the default route), for a total of
>> 6 messages .
>>=20
>> But the better means (single DHCPv6 roundtrip - 2 messages) is to use
>> DHCPv6 to configure the default route as well, and not use RA:
>> draft-ietf-mif-dhcpv6-route-option-05 "DHCPv6 Route Options" and
>> draft-mouton-mif-dhcpv6-drlo-02.txt "Default Router List Option for
>> DHCPv6 (DRLO)"
>>=20
>> Alternatively, use RS/RA single exchange (and not DHCPv6), with DNS
>> resolver address:
>> RFC6106 "IPv6 Router Advertisement Options for DNS Configuration"
>>=20
>> DAD and MLD are two other protocols which may get in the way to fast
>> exchanges.  They could be avoided with proper tweaking of specification
>> and implementation.
>>=20
>>> 802.11 TGai is still going on and its specification is subject to
>>> change, but I'd like to discuss in IETF DHCP issues related to
>>> 802.11ai and arrange I-D according to the progress of TGai task
>>> group.
>>=20
>> I think it is indeed a good point to discuss such an I-D.
>>=20
>> Alex
>>=20
>>>=20
>>> Regards,
>>>=20
>>> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
>>>=20
>>> _______________________________________________ dhcwg mailing list
>>> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>>=20
>>=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 cas@trans-nt.com  Wed Mar 13 12:36:33 2013
Return-Path: <cas@trans-nt.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 661D521F8C9F for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 12:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.22
X-Spam-Level: 
X-Spam-Status: No, score=-0.22 tagged_above=-999 required=5 tests=[AWL=-0.039,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tqVdUL9hdtVL for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 12:36:32 -0700 (PDT)
Received: from dump.fs.trans-nt.com (smtp.trans-nt.co.jp [202.10.98.251]) by ietfa.amsl.com (Postfix) with SMTP id 38E0E21F8C71 for <dhcwg@ietf.org>; Wed, 13 Mar 2013 12:36:31 -0700 (PDT)
Received: (qmail 17497 invoked from network); 14 Mar 2013 04:36:27 +0900
Received: from red.fs.trans-nt.co.jp (HELO dhcp-524e.meeting.ietf.org) (202.10.98.240) by smtp.trans-nt.co.jp with SMTP; 14 Mar 2013 04:36:27 +0900
Message-ID: <5140D539.4060408@trans-nt.com>
Date: Thu, 14 Mar 2013 04:36:25 +0900
From: Hiroki Nakano <cas@trans-nt.com>
Organization: cas authorized 53a6c6e30f1471298320e605c741e412
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com>, <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com>
In-Reply-To: <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 19:36:33 -0000

Sure.
It is important that we have the new optimized sequence
applicable to most cases and the other cases work
as well as what we currently have.  It can make us happy.
Nobody will oppose this basic idea.
The problem is, when, where and who agree and write down
the details of combination and implemenation of protocols.

Regards,

Hiroki Nakano
Trans New Technology, Inc. <cas@trans-nt.com>


(13/03/14 3:25), Bernie Volz (volz) wrote:
> There may also be some areas to explore further - such as what happens if there are multiple DHCP servers or if Rapid Commit is not allowed and how that plays into this. But it likely is just a minor issue as the first response may be optimized but additional are forwarded to client normally,
>
> - Bernie
>
> On Mar 13, 2013, at 2:18 PM, "Hiroki Nakano" <cas@trans-nt.com> wrote:
>
>> I talked with Volz and Tomek yesterday and we also agree
>> that DHCPv4 with Rapid Commit Option has no problem
>> for IPv4 configuration by one round trip exchange of packets.
>> DHCPv6 has a little missing part related to default route,
>> but another idea using RS and RA solves this as Alex mentioned.
>> Other potential problems are DAD and M-flag of RA, but we have
>> Optimistic DAD mechanism and Volz pointed out that DHCPv6 could
>> be used without RA.  However, I recognize that dhcpv6-route-option
>> has some difficulty to reach a consensus in IETF.
>>
>> Bacause 802.11ai is just one of "specific link layer",
>> I'm not sure this working group is suitable for discussion
>> about implementation issues related to DHCPv4 and 802.11ai,
>> (at least, not for RS and RA...)
>> but if anyone having interests in this topic, I'd like to
>> talk about this topic after the dhcwg session informally
>> and please let me hear your comments.
>> Especially, I am wondering who decides detailed use of DHCPv4 on
>> 802.11ai, IEEE people or IETF people? and who should write
>> specification for it as an 802.11 document or as a RFC?
>> if you are writing I-D for this topic, which working group
>> will you submit to? dhc? 6man? v6ops??, etc...
>> Of course, technical topics are welcome.
>>
>> Regards,
>>
>> Hiroki Nakano
>> Trans New Technology, Inc. <cas@trans-nt.com>
>>
>>
>>
>> (13/02/13 21:23), Alexandru Petrescu wrote:
>>> Le 12/02/2013 21:25, Hiroki Nakano a Ã©crit :
>>>> Dear all,
>>>>
>>>> I'm participating in IEEE 802.11 WG TGai task group which is for
>>>> FILS (Fast Initiali Link Setup). They are working for speeding up of
>>>> 802.11 process and trying to provide a new framework for higher
>>>> layer protocols.
>>>>
>>>> I'd like to introduce the overview of prospective 802.11ai
>>>> specification and discuss usages of DHCP on it with DHC WG people in
>>>> March. The followings are a brief introduction.
>>>>
>>>> TGai supposes Wireless LAN is used in very crowded envirionment such
>>>> as railway stations in a giant metropolis. TGai also supposes moving
>>>> hosts through the front of Access Points. In these cases, it is
>>>> effective to reduce management frames of 802.11, especially frames
>>>> for probing APs, authentication and association. The current
>>>> framework takes a few seconds to set up network connectivity before
>>>> starting to communicate. The target of TGai is under one second.
>>>>
>>>> TGai is trying to reduce management frames of 802.11 itself, and in
>>>> addition provide framework for higher layers such as IP to send and
>>>> receive packets during 802.11 association process. The currently
>>>> proposed framework provides "ONE round-trip packet exchange" by
>>>> piggybacking on 802.11 Association Request/Response frames.
>>>>
>>>> My interest is how to fit DHCP to this framework. In case of DHCPv4,
>>>> this is achieved by using Rapid Commit Option (RFC4039) and making
>>>> some additional and trivial rules. In case of DHCPv6, we have to use
>>>> both RA and DHCPv6. In addition, DAD and randomly generated
>>>> addresses have to be considered. Share your idea, please.
>>>
>>> For DHCPv6 - it is possible to use a DHCPv6 single roundtrip to realize
>>> complete configuration to the Client (IPv6 address, default route, DNS
>>> resolver address).
>>>
>>> The straightforward means to achieve complete configuration is to use RA
>>> _and_ DHCP (because only RA provides the default route), for a total of
>>> 6 messages .
>>>
>>> But the better means (single DHCPv6 roundtrip - 2 messages) is to use
>>> DHCPv6 to configure the default route as well, and not use RA:
>>> draft-ietf-mif-dhcpv6-route-option-05 "DHCPv6 Route Options" and
>>> draft-mouton-mif-dhcpv6-drlo-02.txt "Default Router List Option for
>>> DHCPv6 (DRLO)"
>>>
>>> Alternatively, use RS/RA single exchange (and not DHCPv6), with DNS
>>> resolver address:
>>> RFC6106 "IPv6 Router Advertisement Options for DNS Configuration"
>>>
>>> DAD and MLD are two other protocols which may get in the way to fast
>>> exchanges.  They could be avoided with proper tweaking of specification
>>> and implementation.
>>>
>>>> 802.11 TGai is still going on and its specification is subject to
>>>> change, but I'd like to discuss in IETF DHCP issues related to
>>>> 802.11ai and arrange I-D according to the progress of TGai task
>>>> group.
>>>
>>> I think it is indeed a good point to discuss such an I-D.
>>>
>>> Alex
>>>
>>>>
>>>> Regards,
>>>>
>>>> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
>>>>
>>>> _______________________________________________ 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 volz@cisco.com  Wed Mar 13 14:00:36 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E40521F8D2F for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 14:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.937
X-Spam-Level: 
X-Spam-Status: No, score=-9.937 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NBMljX9o5MvF for <dhcwg@ietfa.amsl.com>; Wed, 13 Mar 2013 14:00:32 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id DDB7421F8DB6 for <dhcwg@ietf.org>; Wed, 13 Mar 2013 14:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7316; q=dns/txt; s=iport; t=1363208432; x=1364418032; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=zgOKgJ8abnrlIo5DzL26YwP0SG6lYLYLTpWEKisPHlQ=; b=jxbdY7Bynin3mRrsvz2rbxYd2GGN51kAlp7Abf2Df/764bwYN3Q0l3cD +UN0kiga89pC/tp8eeN95BvXt3rodr62ytFzRLSBDbw4MNyUNn4QHGcjp //LKaeOWc7pHWnRrmd9CC4nZRSNE0XQjwyge8miFeIL+lAkUZ1OcVkJ7j M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAJLoQFGtJXG+/2dsb2JhbABDxFmBWRZ0gioBAQEDAQEBAWsLBQsCAQgOCi4nCyUCBA4FiA4GDMMmEwSOWjMHgl9hA4g9ihqDf5B2gwo
X-IronPort-AV: E=Sophos;i="4.84,840,1355097600"; d="scan'208";a="187145960"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-2.cisco.com with ESMTP; 13 Mar 2013 21:00:27 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2DL0Q7d027212 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Mar 2013 21:00:26 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Wed, 13 Mar 2013 16:00:26 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Hiroki Nakano <cas@trans-nt.com>
Thread-Topic: [dhcwg] IEEE 802.11ai and DHCP
Thread-Index: AQHOIBc4Dr+VanOVykm056tro9m7cpij7/xsgABnwID//8Ongw==
Date: Wed, 13 Mar 2013 21:00:25 +0000
Message-ID: <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com>,<5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com>, <5140D539.4060408@trans-nt.com>
In-Reply-To: <5140D539.4060408@trans-nt.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 21:00:36 -0000

My 2 cents (hat off as co-chair) is this is an IEEE effort - using existing=
 standards.

IEEE has lots of standards. Isn't that why there is IEEE 802.11ai standard =
committee?

We (dhc, ietf) also aren't involved in all of the issues and alternatives s=
o it would hardly be fair to ask us to do this.

I don't think anyone sees issues with what you intend to do as you are just=
 altering how packets transit the network (encapsulating) and perhaps tweak=
ing when things occur (as you want dhcp to start earlier than it would othe=
rwise - before link is "up" - and that might be more of an issue for device=
 vendors as it may require changes in dhcp client implementations).

But it should work even if that isn't done as DHCP would just happen a bit =
later and you would lose some of the 11ai improvements.

You are certainly free to write a draft - most drafts start out as individu=
al submissions. And take it to a few people to figure out if it is really n=
eeded and if so where it may best be placed.

- Bernie

On Mar 13, 2013, at 3:36 PM, "Hiroki Nakano" <cas@trans-nt.com> wrote:

> Sure.
> It is important that we have the new optimized sequence
> applicable to most cases and the other cases work
> as well as what we currently have.  It can make us happy.
> Nobody will oppose this basic idea.
> The problem is, when, where and who agree and write down
> the details of combination and implemenation of protocols.
>=20
> Regards,
>=20
> Hiroki Nakano
> Trans New Technology, Inc. <cas@trans-nt.com>
>=20
>=20
> (13/03/14 3:25), Bernie Volz (volz) wrote:
>> There may also be some areas to explore further - such as what happens i=
f there are multiple DHCP servers or if Rapid Commit is not allowed and how=
 that plays into this. But it likely is just a minor issue as the first res=
ponse may be optimized but additional are forwarded to client normally,
>>=20
>> - Bernie
>>=20
>> On Mar 13, 2013, at 2:18 PM, "Hiroki Nakano" <cas@trans-nt.com> wrote:
>>=20
>>> I talked with Volz and Tomek yesterday and we also agree
>>> that DHCPv4 with Rapid Commit Option has no problem
>>> for IPv4 configuration by one round trip exchange of packets.
>>> DHCPv6 has a little missing part related to default route,
>>> but another idea using RS and RA solves this as Alex mentioned.
>>> Other potential problems are DAD and M-flag of RA, but we have
>>> Optimistic DAD mechanism and Volz pointed out that DHCPv6 could
>>> be used without RA.  However, I recognize that dhcpv6-route-option
>>> has some difficulty to reach a consensus in IETF.
>>>=20
>>> Bacause 802.11ai is just one of "specific link layer",
>>> I'm not sure this working group is suitable for discussion
>>> about implementation issues related to DHCPv4 and 802.11ai,
>>> (at least, not for RS and RA...)
>>> but if anyone having interests in this topic, I'd like to
>>> talk about this topic after the dhcwg session informally
>>> and please let me hear your comments.
>>> Especially, I am wondering who decides detailed use of DHCPv4 on
>>> 802.11ai, IEEE people or IETF people? and who should write
>>> specification for it as an 802.11 document or as a RFC?
>>> if you are writing I-D for this topic, which working group
>>> will you submit to? dhc? 6man? v6ops??, etc...
>>> Of course, technical topics are welcome.
>>>=20
>>> Regards,
>>>=20
>>> Hiroki Nakano
>>> Trans New Technology, Inc. <cas@trans-nt.com>
>>>=20
>>>=20
>>>=20
>>> (13/02/13 21:23), Alexandru Petrescu wrote:
>>>> Le 12/02/2013 21:25, Hiroki Nakano a =E9crit :
>>>>> Dear all,
>>>>>=20
>>>>> I'm participating in IEEE 802.11 WG TGai task group which is for
>>>>> FILS (Fast Initiali Link Setup). They are working for speeding up of
>>>>> 802.11 process and trying to provide a new framework for higher
>>>>> layer protocols.
>>>>>=20
>>>>> I'd like to introduce the overview of prospective 802.11ai
>>>>> specification and discuss usages of DHCP on it with DHC WG people in
>>>>> March. The followings are a brief introduction.
>>>>>=20
>>>>> TGai supposes Wireless LAN is used in very crowded envirionment such
>>>>> as railway stations in a giant metropolis. TGai also supposes moving
>>>>> hosts through the front of Access Points. In these cases, it is
>>>>> effective to reduce management frames of 802.11, especially frames
>>>>> for probing APs, authentication and association. The current
>>>>> framework takes a few seconds to set up network connectivity before
>>>>> starting to communicate. The target of TGai is under one second.
>>>>>=20
>>>>> TGai is trying to reduce management frames of 802.11 itself, and in
>>>>> addition provide framework for higher layers such as IP to send and
>>>>> receive packets during 802.11 association process. The currently
>>>>> proposed framework provides "ONE round-trip packet exchange" by
>>>>> piggybacking on 802.11 Association Request/Response frames.
>>>>>=20
>>>>> My interest is how to fit DHCP to this framework. In case of DHCPv4,
>>>>> this is achieved by using Rapid Commit Option (RFC4039) and making
>>>>> some additional and trivial rules. In case of DHCPv6, we have to use
>>>>> both RA and DHCPv6. In addition, DAD and randomly generated
>>>>> addresses have to be considered. Share your idea, please.
>>>>=20
>>>> For DHCPv6 - it is possible to use a DHCPv6 single roundtrip to realiz=
e
>>>> complete configuration to the Client (IPv6 address, default route, DNS
>>>> resolver address).
>>>>=20
>>>> The straightforward means to achieve complete configuration is to use =
RA
>>>> _and_ DHCP (because only RA provides the default route), for a total o=
f
>>>> 6 messages .
>>>>=20
>>>> But the better means (single DHCPv6 roundtrip - 2 messages) is to use
>>>> DHCPv6 to configure the default route as well, and not use RA:
>>>> draft-ietf-mif-dhcpv6-route-option-05 "DHCPv6 Route Options" and
>>>> draft-mouton-mif-dhcpv6-drlo-02.txt "Default Router List Option for
>>>> DHCPv6 (DRLO)"
>>>>=20
>>>> Alternatively, use RS/RA single exchange (and not DHCPv6), with DNS
>>>> resolver address:
>>>> RFC6106 "IPv6 Router Advertisement Options for DNS Configuration"
>>>>=20
>>>> DAD and MLD are two other protocols which may get in the way to fast
>>>> exchanges.  They could be avoided with proper tweaking of specificatio=
n
>>>> and implementation.
>>>>=20
>>>>> 802.11 TGai is still going on and its specification is subject to
>>>>> change, but I'd like to discuss in IETF DHCP issues related to
>>>>> 802.11ai and arrange I-D according to the progress of TGai task
>>>>> group.
>>>>=20
>>>> I think it is indeed a good point to discuss such an I-D.
>>>>=20
>>>> Alex
>>>>=20
>>>>>=20
>>>>> Regards,
>>>>>=20
>>>>> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
>>>>>=20
>>>>> _______________________________________________ dhcwg mailing list
>>>>> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>>>>=20
>>>>=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 cas@trans-nt.com  Thu Mar 14 07:45:36 2013
Return-Path: <cas@trans-nt.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 778A811E81BF for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 07:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.181
X-Spam-Level: 
X-Spam-Status: No, score=-0.181 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aDMcNEEwuQ5D for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 07:45:35 -0700 (PDT)
Received: from dump.fs.trans-nt.com (smtp.trans-nt.co.jp [202.10.98.251]) by ietfa.amsl.com (Postfix) with SMTP id 38C1F11E81BD for <dhcwg@ietf.org>; Thu, 14 Mar 2013 07:45:34 -0700 (PDT)
Received: (qmail 63558 invoked from network); 14 Mar 2013 23:45:28 +0900
Received: from red.fs.trans-nt.co.jp (HELO dhcp-524e.meeting.ietf.org) (202.10.98.240) by smtp.trans-nt.co.jp with SMTP; 14 Mar 2013 23:45:28 +0900
Message-ID: <5141E286.6050305@trans-nt.com>
Date: Thu, 14 Mar 2013 23:45:26 +0900
From: Hiroki Nakano <cas@trans-nt.com>
Organization: cas authorized 53a6c6e30f1471298320e605c741e412
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Thunderbird/20.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com>, <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com>, <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com>
In-Reply-To: <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Mar 2013 14:45:36 -0000

Barnie, thank you for your opinion.

I understand protocols generally want to stay independent
from their adjacent layers, while someone have to make
glue between layers to build up the whole system.
The old days, IP people made glue by theirselves in order
to use IP on various link layers.  Today, IP is the winner.
Other protocols else want to have relation with IP and
make glue between them and IP in the outside of IETF.
My concern is that bad glues undermine the heart of IP
little by little and I believe IETF is the only group
who can prevent it.

Anyway, we are competing right now in 802.11WG TGai.
I am supporting an DHCP-based protocol for IP address
assignment and against an 802.11ai original protocol.
Please help me if you agree with me.
I can provide more information if you have interest.

Regards,

Hiroki Nakano
Trans New Technology, Inc. <cas@trans-nt.com>


(13/03/14 6:00), Bernie Volz (volz) wrote:
> My 2 cents (hat off as co-chair) is this is an IEEE effort - using existing standards.
>
> IEEE has lots of standards. Isn't that why there is IEEE 802.11ai standard committee?
>
> We (dhc, ietf) also aren't involved in all of the issues and alternatives so it would hardly be fair to ask us to do this.
>
> I don't think anyone sees issues with what you intend to do as you are just altering how packets transit the network (encapsulating) and perhaps tweaking when things occur (as you want dhcp to start earlier than it would otherwise - before link is "up" - and that might be more of an issue for device vendors as it may require changes in dhcp client implementations).
>
> But it should work even if that isn't done as DHCP would just happen a bit later and you would lose some of the 11ai improvements.
>
> You are certainly free to write a draft - most drafts start out as individual submissions. And take it to a few people to figure out if it is really needed and if so where it may best be placed.
>
> - Bernie
>
> On Mar 13, 2013, at 3:36 PM, "Hiroki Nakano" <cas@trans-nt.com> wrote:
>
>> Sure.
>> It is important that we have the new optimized sequence
>> applicable to most cases and the other cases work
>> as well as what we currently have.  It can make us happy.
>> Nobody will oppose this basic idea.
>> The problem is, when, where and who agree and write down
>> the details of combination and implemenation of protocols.
>>
>> Regards,
>>
>> Hiroki Nakano
>> Trans New Technology, Inc. <cas@trans-nt.com>
>>
>>
>> (13/03/14 3:25), Bernie Volz (volz) wrote:
>>> There may also be some areas to explore further - such as what happens if there are multiple DHCP servers or if Rapid Commit is not allowed and how that plays into this. But it likely is just a minor issue as the first response may be optimized but additional are forwarded to client normally,
>>>
>>> - Bernie
>>>
>>> On Mar 13, 2013, at 2:18 PM, "Hiroki Nakano" <cas@trans-nt.com> wrote:
>>>
>>>> I talked with Volz and Tomek yesterday and we also agree
>>>> that DHCPv4 with Rapid Commit Option has no problem
>>>> for IPv4 configuration by one round trip exchange of packets.
>>>> DHCPv6 has a little missing part related to default route,
>>>> but another idea using RS and RA solves this as Alex mentioned.
>>>> Other potential problems are DAD and M-flag of RA, but we have
>>>> Optimistic DAD mechanism and Volz pointed out that DHCPv6 could
>>>> be used without RA.  However, I recognize that dhcpv6-route-option
>>>> has some difficulty to reach a consensus in IETF.
>>>>
>>>> Bacause 802.11ai is just one of "specific link layer",
>>>> I'm not sure this working group is suitable for discussion
>>>> about implementation issues related to DHCPv4 and 802.11ai,
>>>> (at least, not for RS and RA...)
>>>> but if anyone having interests in this topic, I'd like to
>>>> talk about this topic after the dhcwg session informally
>>>> and please let me hear your comments.
>>>> Especially, I am wondering who decides detailed use of DHCPv4 on
>>>> 802.11ai, IEEE people or IETF people? and who should write
>>>> specification for it as an 802.11 document or as a RFC?
>>>> if you are writing I-D for this topic, which working group
>>>> will you submit to? dhc? 6man? v6ops??, etc...
>>>> Of course, technical topics are welcome.
>>>>
>>>> Regards,
>>>>
>>>> Hiroki Nakano
>>>> Trans New Technology, Inc. <cas@trans-nt.com>
>>>>
>>>>
>>>>
>>>> (13/02/13 21:23), Alexandru Petrescu wrote:
>>>>> Le 12/02/2013 21:25, Hiroki Nakano a Ã©crit :
>>>>>> Dear all,
>>>>>>
>>>>>> I'm participating in IEEE 802.11 WG TGai task group which is for
>>>>>> FILS (Fast Initiali Link Setup). They are working for speeding up of
>>>>>> 802.11 process and trying to provide a new framework for higher
>>>>>> layer protocols.
>>>>>>
>>>>>> I'd like to introduce the overview of prospective 802.11ai
>>>>>> specification and discuss usages of DHCP on it with DHC WG people in
>>>>>> March. The followings are a brief introduction.
>>>>>>
>>>>>> TGai supposes Wireless LAN is used in very crowded envirionment such
>>>>>> as railway stations in a giant metropolis. TGai also supposes moving
>>>>>> hosts through the front of Access Points. In these cases, it is
>>>>>> effective to reduce management frames of 802.11, especially frames
>>>>>> for probing APs, authentication and association. The current
>>>>>> framework takes a few seconds to set up network connectivity before
>>>>>> starting to communicate. The target of TGai is under one second.
>>>>>>
>>>>>> TGai is trying to reduce management frames of 802.11 itself, and in
>>>>>> addition provide framework for higher layers such as IP to send and
>>>>>> receive packets during 802.11 association process. The currently
>>>>>> proposed framework provides "ONE round-trip packet exchange" by
>>>>>> piggybacking on 802.11 Association Request/Response frames.
>>>>>>
>>>>>> My interest is how to fit DHCP to this framework. In case of DHCPv4,
>>>>>> this is achieved by using Rapid Commit Option (RFC4039) and making
>>>>>> some additional and trivial rules. In case of DHCPv6, we have to use
>>>>>> both RA and DHCPv6. In addition, DAD and randomly generated
>>>>>> addresses have to be considered. Share your idea, please.
>>>>>
>>>>> For DHCPv6 - it is possible to use a DHCPv6 single roundtrip to realize
>>>>> complete configuration to the Client (IPv6 address, default route, DNS
>>>>> resolver address).
>>>>>
>>>>> The straightforward means to achieve complete configuration is to use RA
>>>>> _and_ DHCP (because only RA provides the default route), for a total of
>>>>> 6 messages .
>>>>>
>>>>> But the better means (single DHCPv6 roundtrip - 2 messages) is to use
>>>>> DHCPv6 to configure the default route as well, and not use RA:
>>>>> draft-ietf-mif-dhcpv6-route-option-05 "DHCPv6 Route Options" and
>>>>> draft-mouton-mif-dhcpv6-drlo-02.txt "Default Router List Option for
>>>>> DHCPv6 (DRLO)"
>>>>>
>>>>> Alternatively, use RS/RA single exchange (and not DHCPv6), with DNS
>>>>> resolver address:
>>>>> RFC6106 "IPv6 Router Advertisement Options for DNS Configuration"
>>>>>
>>>>> DAD and MLD are two other protocols which may get in the way to fast
>>>>> exchanges.  They could be avoided with proper tweaking of specification
>>>>> and implementation.
>>>>>
>>>>>> 802.11 TGai is still going on and its specification is subject to
>>>>>> change, but I'd like to discuss in IETF DHCP issues related to
>>>>>> 802.11ai and arrange I-D according to the progress of TGai task
>>>>>> group.
>>>>>
>>>>> I think it is indeed a good point to discuss such an I-D.
>>>>>
>>>>> Alex
>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
>>>>>>
>>>>>> _______________________________________________ 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 volz@cisco.com  Thu Mar 14 07:56:09 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12F0611E81F2 for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 07:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWDpGRO4Bjyf for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 07:56:04 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 59BF211E819F for <dhcwg@ietf.org>; Thu, 14 Mar 2013 07:56:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13084; q=dns/txt; s=iport; t=1363272963; x=1364482563; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=bqrVty+mhtwAUOKo18q9b5b9RCM+7yx9AgQKMLfFdR0=; b=gRd49xHhMO656+4azTGP8mAwjCC0GpEhcYj3ImWROIvkJhxkRs6v3gDr Waoz5DyXmaI/TLvf4lno4ywIURI0D0htPSUjLMaZ+JcX7EHklSPSjKozk PqgKJ5LBYqLzVlB2gNnlSLYDmHNKM8y89FQxoyE94t2h97UAWvAOx46qM Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAMnjQVGtJV2d/2dsb2JhbABEiCq8Tm50FnSCKgEBAQQBAQEgEToEBwwEAgEIDgMEAQEBAgIGHQMCAgIlCxQBCAgCBA4FCAERh3oMrlKST4EjjTwWEAsHBoInMmEDklk6hGSPY4MKgig
X-IronPort-AV: E=Sophos;i="4.84,845,1355097600"; d="scan'208";a="187439389"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-2.cisco.com with ESMTP; 14 Mar 2013 14:56:02 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r2EEu2Ei012276 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Mar 2013 14:56:02 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Thu, 14 Mar 2013 09:56:02 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Hiroki Nakano <cas@trans-nt.com>
Thread-Topic: [dhcwg] IEEE 802.11ai and DHCP
Thread-Index: AQHOIBc4Dr+VanOVykm056tro9m7cpij7/xsgABnwID//8Ong4ABfWEA//+sshA=
Date: Thu, 14 Mar 2013 14:56:01 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E184ACDD7@xmb-rcd-x04.cisco.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com>, <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com>, <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com>
In-Reply-To: <5141E286.6050305@trans-nt.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.245.173]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Mar 2013 14:56:09 -0000

SXQgd291bGQgYmUgYmFkIG5ld3MgaWYgREhDUCBpcyBhYmFuZG9uZWQgLSB0aGVyZSBpcyBubyBk
aXNhZ3JlZW1lbnQgdGhlcmUuIERIQ1AgaXMgYWxzbyBpbXBvcnRhbnQgdG8gY29uZmlndXJlIG1v
cmUgdGhhbiBqdXN0IHRoZSBhZGRyZXNzIChhbmQgdGhlc2UgYXJlIGNyaXRpY2FsIGZvciBjb21w
bGV0ZSBjb25uZWN0aXZpdHkpLg0KDQpJIHRoaW5rIHlvdSBoYXZlIGhhZCBzb21lIGFkZGl0aW9u
YWwgZGlzY3Vzc2lvbnMgd2l0aCBUZWQ/DQoNCkkgdGhpbmsgaXQgaXMgYmVzdCBpZiBJRUVFIHVz
ZXMgdGhlIG9mZmljaWFsIGxpYWlzb24gcHJvY2VzcyBpZiB0aGV5IHdhbnQgYW4gb3BpbmlvbiBm
cm9tIHRoZSBJRVRGIChvciBESEMgV0cpIC0tIHNvcnJ5LCBidXQgSSBkb24ndCBrbm93IHRoZSBm
dWxsIGRldGFpbHMgb2YgdGhpcyBwcm9jZXNzLiBUaGVyZSBpcyBhIGRvY3VtZW50IHRoYXQgZGVz
Y3JpYmVzIHRoaXMgLSAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNDQ0MSB0aG91Z2gg
aXQgbG9va3MgbGlrZSB0aGlzIGlzIHVuZGVyIHJldmlldywgc2VlIGh0dHA6Ly93d3cuaWFiLm9y
Zy8yMDEzLzAxLzA5L2lhYi1hZG9wdHMtdGhlLWllZWUtODAyaWV0Zi1yZWxhdGlvbnNoaXAvIGFu
ZCBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1kYXdraW5zLWlhYi1yZmM0NDQxcmV2
LTAyLg0KDQpZb3UgbWlnaHQgYWxzbyBzcGVhayB3aXRoIHRoZSBhdXRob3JzIG9mIHRoZXNlIGRv
Y3VtZW50cyB0byBzZWUgd2hldGhlciB0aGV5IGNhbiBwcm92aWRlIHlvdSBzb21lIGd1aWRhbmNl
Lg0KDQotIEJlcm5pZQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogZGhjd2ct
Ym91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmRoY3dnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFs
ZiBPZiBIaXJva2kgTmFrYW5vDQpTZW50OiBUaHVyc2RheSwgTWFyY2ggMTQsIDIwMTMgMTA6NDUg
QU0NClRvOiBCZXJuaWUgVm9seiAodm9seikNCkNjOiBkaGN3Z0BpZXRmLm9yZw0KU3ViamVjdDog
UmU6IFtkaGN3Z10gSUVFRSA4MDIuMTFhaSBhbmQgREhDUA0KDQpCYXJuaWUsIHRoYW5rIHlvdSBm
b3IgeW91ciBvcGluaW9uLg0KDQpJIHVuZGVyc3RhbmQgcHJvdG9jb2xzIGdlbmVyYWxseSB3YW50
IHRvIHN0YXkgaW5kZXBlbmRlbnQgZnJvbSB0aGVpciBhZGphY2VudCBsYXllcnMsIHdoaWxlIHNv
bWVvbmUgaGF2ZSB0byBtYWtlIGdsdWUgYmV0d2VlbiBsYXllcnMgdG8gYnVpbGQgdXAgdGhlIHdo
b2xlIHN5c3RlbS4NClRoZSBvbGQgZGF5cywgSVAgcGVvcGxlIG1hZGUgZ2x1ZSBieSB0aGVpcnNl
bHZlcyBpbiBvcmRlciB0byB1c2UgSVAgb24gdmFyaW91cyBsaW5rIGxheWVycy4gIFRvZGF5LCBJ
UCBpcyB0aGUgd2lubmVyLg0KT3RoZXIgcHJvdG9jb2xzIGVsc2Ugd2FudCB0byBoYXZlIHJlbGF0
aW9uIHdpdGggSVAgYW5kIG1ha2UgZ2x1ZSBiZXR3ZWVuIHRoZW0gYW5kIElQIGluIHRoZSBvdXRz
aWRlIG9mIElFVEYuDQpNeSBjb25jZXJuIGlzIHRoYXQgYmFkIGdsdWVzIHVuZGVybWluZSB0aGUg
aGVhcnQgb2YgSVAgbGl0dGxlIGJ5IGxpdHRsZSBhbmQgSSBiZWxpZXZlIElFVEYgaXMgdGhlIG9u
bHkgZ3JvdXAgd2hvIGNhbiBwcmV2ZW50IGl0Lg0KDQpBbnl3YXksIHdlIGFyZSBjb21wZXRpbmcg
cmlnaHQgbm93IGluIDgwMi4xMVdHIFRHYWkuDQpJIGFtIHN1cHBvcnRpbmcgYW4gREhDUC1iYXNl
ZCBwcm90b2NvbCBmb3IgSVAgYWRkcmVzcyBhc3NpZ25tZW50IGFuZCBhZ2FpbnN0IGFuIDgwMi4x
MWFpIG9yaWdpbmFsIHByb3RvY29sLg0KUGxlYXNlIGhlbHAgbWUgaWYgeW91IGFncmVlIHdpdGgg
bWUuDQpJIGNhbiBwcm92aWRlIG1vcmUgaW5mb3JtYXRpb24gaWYgeW91IGhhdmUgaW50ZXJlc3Qu
DQoNClJlZ2FyZHMsDQoNCkhpcm9raSBOYWthbm8NClRyYW5zIE5ldyBUZWNobm9sb2d5LCBJbmMu
IDxjYXNAdHJhbnMtbnQuY29tPg0KDQoNCigxMy8wMy8xNCA2OjAwKSwgQmVybmllIFZvbHogKHZv
bHopIHdyb3RlOg0KPiBNeSAyIGNlbnRzIChoYXQgb2ZmIGFzIGNvLWNoYWlyKSBpcyB0aGlzIGlz
IGFuIElFRUUgZWZmb3J0IC0gdXNpbmcgZXhpc3Rpbmcgc3RhbmRhcmRzLg0KPg0KPiBJRUVFIGhh
cyBsb3RzIG9mIHN0YW5kYXJkcy4gSXNuJ3QgdGhhdCB3aHkgdGhlcmUgaXMgSUVFRSA4MDIuMTFh
aSBzdGFuZGFyZCBjb21taXR0ZWU/DQo+DQo+IFdlIChkaGMsIGlldGYpIGFsc28gYXJlbid0IGlu
dm9sdmVkIGluIGFsbCBvZiB0aGUgaXNzdWVzIGFuZCBhbHRlcm5hdGl2ZXMgc28gaXQgd291bGQg
aGFyZGx5IGJlIGZhaXIgdG8gYXNrIHVzIHRvIGRvIHRoaXMuDQo+DQo+IEkgZG9uJ3QgdGhpbmsg
YW55b25lIHNlZXMgaXNzdWVzIHdpdGggd2hhdCB5b3UgaW50ZW5kIHRvIGRvIGFzIHlvdSBhcmUg
anVzdCBhbHRlcmluZyBob3cgcGFja2V0cyB0cmFuc2l0IHRoZSBuZXR3b3JrIChlbmNhcHN1bGF0
aW5nKSBhbmQgcGVyaGFwcyB0d2Vha2luZyB3aGVuIHRoaW5ncyBvY2N1ciAoYXMgeW91IHdhbnQg
ZGhjcCB0byBzdGFydCBlYXJsaWVyIHRoYW4gaXQgd291bGQgb3RoZXJ3aXNlIC0gYmVmb3JlIGxp
bmsgaXMgInVwIiAtIGFuZCB0aGF0IG1pZ2h0IGJlIG1vcmUgb2YgYW4gaXNzdWUgZm9yIGRldmlj
ZSB2ZW5kb3JzIGFzIGl0IG1heSByZXF1aXJlIGNoYW5nZXMgaW4gZGhjcCBjbGllbnQgaW1wbGVt
ZW50YXRpb25zKS4NCj4NCj4gQnV0IGl0IHNob3VsZCB3b3JrIGV2ZW4gaWYgdGhhdCBpc24ndCBk
b25lIGFzIERIQ1Agd291bGQganVzdCBoYXBwZW4gYSBiaXQgbGF0ZXIgYW5kIHlvdSB3b3VsZCBs
b3NlIHNvbWUgb2YgdGhlIDExYWkgaW1wcm92ZW1lbnRzLg0KPg0KPiBZb3UgYXJlIGNlcnRhaW5s
eSBmcmVlIHRvIHdyaXRlIGEgZHJhZnQgLSBtb3N0IGRyYWZ0cyBzdGFydCBvdXQgYXMgaW5kaXZp
ZHVhbCBzdWJtaXNzaW9ucy4gQW5kIHRha2UgaXQgdG8gYSBmZXcgcGVvcGxlIHRvIGZpZ3VyZSBv
dXQgaWYgaXQgaXMgcmVhbGx5IG5lZWRlZCBhbmQgaWYgc28gd2hlcmUgaXQgbWF5IGJlc3QgYmUg
cGxhY2VkLg0KPg0KPiAtIEJlcm5pZQ0KPg0KPiBPbiBNYXIgMTMsIDIwMTMsIGF0IDM6MzYgUE0s
ICJIaXJva2kgTmFrYW5vIiA8Y2FzQHRyYW5zLW50LmNvbT4gd3JvdGU6DQo+DQo+PiBTdXJlLg0K
Pj4gSXQgaXMgaW1wb3J0YW50IHRoYXQgd2UgaGF2ZSB0aGUgbmV3IG9wdGltaXplZCBzZXF1ZW5j
ZSBhcHBsaWNhYmxlIHRvIA0KPj4gbW9zdCBjYXNlcyBhbmQgdGhlIG90aGVyIGNhc2VzIHdvcmsg
YXMgd2VsbCBhcyB3aGF0IHdlIGN1cnJlbnRseSANCj4+IGhhdmUuICBJdCBjYW4gbWFrZSB1cyBo
YXBweS4NCj4+IE5vYm9keSB3aWxsIG9wcG9zZSB0aGlzIGJhc2ljIGlkZWEuDQo+PiBUaGUgcHJv
YmxlbSBpcywgd2hlbiwgd2hlcmUgYW5kIHdobyBhZ3JlZSBhbmQgd3JpdGUgZG93biB0aGUgZGV0
YWlscyANCj4+IG9mIGNvbWJpbmF0aW9uIGFuZCBpbXBsZW1lbmF0aW9uIG9mIHByb3RvY29scy4N
Cj4+DQo+PiBSZWdhcmRzLA0KPj4NCj4+IEhpcm9raSBOYWthbm8NCj4+IFRyYW5zIE5ldyBUZWNo
bm9sb2d5LCBJbmMuIDxjYXNAdHJhbnMtbnQuY29tPg0KPj4NCj4+DQo+PiAoMTMvMDMvMTQgMzoy
NSksIEJlcm5pZSBWb2x6ICh2b2x6KSB3cm90ZToNCj4+PiBUaGVyZSBtYXkgYWxzbyBiZSBzb21l
IGFyZWFzIHRvIGV4cGxvcmUgZnVydGhlciAtIHN1Y2ggYXMgd2hhdCANCj4+PiBoYXBwZW5zIGlm
IHRoZXJlIGFyZSBtdWx0aXBsZSBESENQIHNlcnZlcnMgb3IgaWYgUmFwaWQgQ29tbWl0IGlzIG5v
dCANCj4+PiBhbGxvd2VkIGFuZCBob3cgdGhhdCBwbGF5cyBpbnRvIHRoaXMuIEJ1dCBpdCBsaWtl
bHkgaXMganVzdCBhIG1pbm9yIA0KPj4+IGlzc3VlIGFzIHRoZSBmaXJzdCByZXNwb25zZSBtYXkg
YmUgb3B0aW1pemVkIGJ1dCBhZGRpdGlvbmFsIGFyZSANCj4+PiBmb3J3YXJkZWQgdG8gY2xpZW50
IG5vcm1hbGx5LA0KPj4+DQo+Pj4gLSBCZXJuaWUNCj4+Pg0KPj4+IE9uIE1hciAxMywgMjAxMywg
YXQgMjoxOCBQTSwgIkhpcm9raSBOYWthbm8iIDxjYXNAdHJhbnMtbnQuY29tPiB3cm90ZToNCj4+
Pg0KPj4+PiBJIHRhbGtlZCB3aXRoIFZvbHogYW5kIFRvbWVrIHllc3RlcmRheSBhbmQgd2UgYWxz
byBhZ3JlZSB0aGF0IA0KPj4+PiBESENQdjQgd2l0aCBSYXBpZCBDb21taXQgT3B0aW9uIGhhcyBu
byBwcm9ibGVtIGZvciBJUHY0IA0KPj4+PiBjb25maWd1cmF0aW9uIGJ5IG9uZSByb3VuZCB0cmlw
IGV4Y2hhbmdlIG9mIHBhY2tldHMuDQo+Pj4+IERIQ1B2NiBoYXMgYSBsaXR0bGUgbWlzc2luZyBw
YXJ0IHJlbGF0ZWQgdG8gZGVmYXVsdCByb3V0ZSwgYnV0IA0KPj4+PiBhbm90aGVyIGlkZWEgdXNp
bmcgUlMgYW5kIFJBIHNvbHZlcyB0aGlzIGFzIEFsZXggbWVudGlvbmVkLg0KPj4+PiBPdGhlciBw
b3RlbnRpYWwgcHJvYmxlbXMgYXJlIERBRCBhbmQgTS1mbGFnIG9mIFJBLCBidXQgd2UgaGF2ZSAN
Cj4+Pj4gT3B0aW1pc3RpYyBEQUQgbWVjaGFuaXNtIGFuZCBWb2x6IHBvaW50ZWQgb3V0IHRoYXQg
REhDUHY2IGNvdWxkIGJlIA0KPj4+PiB1c2VkIHdpdGhvdXQgUkEuICBIb3dldmVyLCBJIHJlY29n
bml6ZSB0aGF0IGRoY3B2Ni1yb3V0ZS1vcHRpb24gaGFzIA0KPj4+PiBzb21lIGRpZmZpY3VsdHkg
dG8gcmVhY2ggYSBjb25zZW5zdXMgaW4gSUVURi4NCj4+Pj4NCj4+Pj4gQmFjYXVzZSA4MDIuMTFh
aSBpcyBqdXN0IG9uZSBvZiAic3BlY2lmaWMgbGluayBsYXllciIsIEknbSBub3Qgc3VyZSANCj4+
Pj4gdGhpcyB3b3JraW5nIGdyb3VwIGlzIHN1aXRhYmxlIGZvciBkaXNjdXNzaW9uIGFib3V0IGlt
cGxlbWVudGF0aW9uIA0KPj4+PiBpc3N1ZXMgcmVsYXRlZCB0byBESENQdjQgYW5kIDgwMi4xMWFp
LCAoYXQgbGVhc3QsIG5vdCBmb3IgUlMgYW5kIA0KPj4+PiBSQS4uLikgYnV0IGlmIGFueW9uZSBo
YXZpbmcgaW50ZXJlc3RzIGluIHRoaXMgdG9waWMsIEknZCBsaWtlIHRvIA0KPj4+PiB0YWxrIGFi
b3V0IHRoaXMgdG9waWMgYWZ0ZXIgdGhlIGRoY3dnIHNlc3Npb24gaW5mb3JtYWxseSBhbmQgcGxl
YXNlIA0KPj4+PiBsZXQgbWUgaGVhciB5b3VyIGNvbW1lbnRzLg0KPj4+PiBFc3BlY2lhbGx5LCBJ
IGFtIHdvbmRlcmluZyB3aG8gZGVjaWRlcyBkZXRhaWxlZCB1c2Ugb2YgREhDUHY0IG9uIA0KPj4+
PiA4MDIuMTFhaSwgSUVFRSBwZW9wbGUgb3IgSUVURiBwZW9wbGU/IGFuZCB3aG8gc2hvdWxkIHdy
aXRlIA0KPj4+PiBzcGVjaWZpY2F0aW9uIGZvciBpdCBhcyBhbiA4MDIuMTEgZG9jdW1lbnQgb3Ig
YXMgYSBSRkM/DQo+Pj4+IGlmIHlvdSBhcmUgd3JpdGluZyBJLUQgZm9yIHRoaXMgdG9waWMsIHdo
aWNoIHdvcmtpbmcgZ3JvdXAgd2lsbCB5b3UgDQo+Pj4+IHN1Ym1pdCB0bz8gZGhjPyA2bWFuPyB2
Nm9wcz8/LCBldGMuLi4NCj4+Pj4gT2YgY291cnNlLCB0ZWNobmljYWwgdG9waWNzIGFyZSB3ZWxj
b21lLg0KPj4+Pg0KPj4+PiBSZWdhcmRzLA0KPj4+Pg0KPj4+PiBIaXJva2kgTmFrYW5vDQo+Pj4+
IFRyYW5zIE5ldyBUZWNobm9sb2d5LCBJbmMuIDxjYXNAdHJhbnMtbnQuY29tPg0KPj4+Pg0KPj4+
Pg0KPj4+Pg0KPj4+PiAoMTMvMDIvMTMgMjE6MjMpLCBBbGV4YW5kcnUgUGV0cmVzY3Ugd3JvdGU6
DQo+Pj4+PiBMZSAxMi8wMi8yMDEzIDIxOjI1LCBIaXJva2kgTmFrYW5vIGEgw6ljcml0IDoNCj4+
Pj4+PiBEZWFyIGFsbCwNCj4+Pj4+Pg0KPj4+Pj4+IEknbSBwYXJ0aWNpcGF0aW5nIGluIElFRUUg
ODAyLjExIFdHIFRHYWkgdGFzayBncm91cCB3aGljaCBpcyBmb3IgDQo+Pj4+Pj4gRklMUyAoRmFz
dCBJbml0aWFsaSBMaW5rIFNldHVwKS4gVGhleSBhcmUgd29ya2luZyBmb3Igc3BlZWRpbmcgdXAg
DQo+Pj4+Pj4gb2YNCj4+Pj4+PiA4MDIuMTEgcHJvY2VzcyBhbmQgdHJ5aW5nIHRvIHByb3ZpZGUg
YSBuZXcgZnJhbWV3b3JrIGZvciBoaWdoZXIgDQo+Pj4+Pj4gbGF5ZXIgcHJvdG9jb2xzLg0KPj4+
Pj4+DQo+Pj4+Pj4gSSdkIGxpa2UgdG8gaW50cm9kdWNlIHRoZSBvdmVydmlldyBvZiBwcm9zcGVj
dGl2ZSA4MDIuMTFhaSANCj4+Pj4+PiBzcGVjaWZpY2F0aW9uIGFuZCBkaXNjdXNzIHVzYWdlcyBv
ZiBESENQIG9uIGl0IHdpdGggREhDIFdHIHBlb3BsZSANCj4+Pj4+PiBpbiBNYXJjaC4gVGhlIGZv
bGxvd2luZ3MgYXJlIGEgYnJpZWYgaW50cm9kdWN0aW9uLg0KPj4+Pj4+DQo+Pj4+Pj4gVEdhaSBz
dXBwb3NlcyBXaXJlbGVzcyBMQU4gaXMgdXNlZCBpbiB2ZXJ5IGNyb3dkZWQgZW52aXJpb25tZW50
IA0KPj4+Pj4+IHN1Y2ggYXMgcmFpbHdheSBzdGF0aW9ucyBpbiBhIGdpYW50IG1ldHJvcG9saXMu
IFRHYWkgYWxzbyANCj4+Pj4+PiBzdXBwb3NlcyBtb3ZpbmcgaG9zdHMgdGhyb3VnaCB0aGUgZnJv
bnQgb2YgQWNjZXNzIFBvaW50cy4gSW4gDQo+Pj4+Pj4gdGhlc2UgY2FzZXMsIGl0IGlzIGVmZmVj
dGl2ZSB0byByZWR1Y2UgbWFuYWdlbWVudCBmcmFtZXMgb2YgDQo+Pj4+Pj4gODAyLjExLCBlc3Bl
Y2lhbGx5IGZyYW1lcyBmb3IgcHJvYmluZyBBUHMsIGF1dGhlbnRpY2F0aW9uIGFuZCANCj4+Pj4+
PiBhc3NvY2lhdGlvbi4gVGhlIGN1cnJlbnQgZnJhbWV3b3JrIHRha2VzIGEgZmV3IHNlY29uZHMg
dG8gc2V0IHVwIA0KPj4+Pj4+IG5ldHdvcmsgY29ubmVjdGl2aXR5IGJlZm9yZSBzdGFydGluZyB0
byBjb21tdW5pY2F0ZS4gVGhlIHRhcmdldCBvZiBUR2FpIGlzIHVuZGVyIG9uZSBzZWNvbmQuDQo+
Pj4+Pj4NCj4+Pj4+PiBUR2FpIGlzIHRyeWluZyB0byByZWR1Y2UgbWFuYWdlbWVudCBmcmFtZXMg
b2YgODAyLjExIGl0c2VsZiwgYW5kIA0KPj4+Pj4+IGluIGFkZGl0aW9uIHByb3ZpZGUgZnJhbWV3
b3JrIGZvciBoaWdoZXIgbGF5ZXJzIHN1Y2ggYXMgSVAgdG8gDQo+Pj4+Pj4gc2VuZCBhbmQgcmVj
ZWl2ZSBwYWNrZXRzIGR1cmluZyA4MDIuMTEgYXNzb2NpYXRpb24gcHJvY2Vzcy4gVGhlIA0KPj4+
Pj4+IGN1cnJlbnRseSBwcm9wb3NlZCBmcmFtZXdvcmsgcHJvdmlkZXMgIk9ORSByb3VuZC10cmlw
IHBhY2tldCANCj4+Pj4+PiBleGNoYW5nZSIgYnkgcGlnZ3liYWNraW5nIG9uIDgwMi4xMSBBc3Nv
Y2lhdGlvbiBSZXF1ZXN0L1Jlc3BvbnNlIGZyYW1lcy4NCj4+Pj4+Pg0KPj4+Pj4+IE15IGludGVy
ZXN0IGlzIGhvdyB0byBmaXQgREhDUCB0byB0aGlzIGZyYW1ld29yay4gSW4gY2FzZSBvZiANCj4+
Pj4+PiBESENQdjQsIHRoaXMgaXMgYWNoaWV2ZWQgYnkgdXNpbmcgUmFwaWQgQ29tbWl0IE9wdGlv
biAoUkZDNDAzOSkgDQo+Pj4+Pj4gYW5kIG1ha2luZyBzb21lIGFkZGl0aW9uYWwgYW5kIHRyaXZp
YWwgcnVsZXMuIEluIGNhc2Ugb2YgREhDUHY2LCANCj4+Pj4+PiB3ZSBoYXZlIHRvIHVzZSBib3Ro
IFJBIGFuZCBESENQdjYuIEluIGFkZGl0aW9uLCBEQUQgYW5kIHJhbmRvbWx5IA0KPj4+Pj4+IGdl
bmVyYXRlZCBhZGRyZXNzZXMgaGF2ZSB0byBiZSBjb25zaWRlcmVkLiBTaGFyZSB5b3VyIGlkZWEs
IHBsZWFzZS4NCj4+Pj4+DQo+Pj4+PiBGb3IgREhDUHY2IC0gaXQgaXMgcG9zc2libGUgdG8gdXNl
IGEgREhDUHY2IHNpbmdsZSByb3VuZHRyaXAgdG8gDQo+Pj4+PiByZWFsaXplIGNvbXBsZXRlIGNv
bmZpZ3VyYXRpb24gdG8gdGhlIENsaWVudCAoSVB2NiBhZGRyZXNzLCANCj4+Pj4+IGRlZmF1bHQg
cm91dGUsIEROUyByZXNvbHZlciBhZGRyZXNzKS4NCj4+Pj4+DQo+Pj4+PiBUaGUgc3RyYWlnaHRm
b3J3YXJkIG1lYW5zIHRvIGFjaGlldmUgY29tcGxldGUgY29uZmlndXJhdGlvbiBpcyB0byANCj4+
Pj4+IHVzZSBSQSBfYW5kXyBESENQIChiZWNhdXNlIG9ubHkgUkEgcHJvdmlkZXMgdGhlIGRlZmF1
bHQgcm91dGUpLCANCj4+Pj4+IGZvciBhIHRvdGFsIG9mDQo+Pj4+PiA2IG1lc3NhZ2VzIC4NCj4+
Pj4+DQo+Pj4+PiBCdXQgdGhlIGJldHRlciBtZWFucyAoc2luZ2xlIERIQ1B2NiByb3VuZHRyaXAg
LSAyIG1lc3NhZ2VzKSBpcyB0byANCj4+Pj4+IHVzZQ0KPj4+Pj4gREhDUHY2IHRvIGNvbmZpZ3Vy
ZSB0aGUgZGVmYXVsdCByb3V0ZSBhcyB3ZWxsLCBhbmQgbm90IHVzZSBSQToNCj4+Pj4+IGRyYWZ0
LWlldGYtbWlmLWRoY3B2Ni1yb3V0ZS1vcHRpb24tMDUgIkRIQ1B2NiBSb3V0ZSBPcHRpb25zIiBh
bmQgDQo+Pj4+PiBkcmFmdC1tb3V0b24tbWlmLWRoY3B2Ni1kcmxvLTAyLnR4dCAiRGVmYXVsdCBS
b3V0ZXIgTGlzdCBPcHRpb24gDQo+Pj4+PiBmb3INCj4+Pj4+IERIQ1B2NiAoRFJMTykiDQo+Pj4+
Pg0KPj4+Pj4gQWx0ZXJuYXRpdmVseSwgdXNlIFJTL1JBIHNpbmdsZSBleGNoYW5nZSAoYW5kIG5v
dCBESENQdjYpLCB3aXRoIA0KPj4+Pj4gRE5TIHJlc29sdmVyIGFkZHJlc3M6DQo+Pj4+PiBSRkM2
MTA2ICJJUHY2IFJvdXRlciBBZHZlcnRpc2VtZW50IE9wdGlvbnMgZm9yIEROUyBDb25maWd1cmF0
aW9uIg0KPj4+Pj4NCj4+Pj4+IERBRCBhbmQgTUxEIGFyZSB0d28gb3RoZXIgcHJvdG9jb2xzIHdo
aWNoIG1heSBnZXQgaW4gdGhlIHdheSB0byANCj4+Pj4+IGZhc3QgZXhjaGFuZ2VzLiAgVGhleSBj
b3VsZCBiZSBhdm9pZGVkIHdpdGggcHJvcGVyIHR3ZWFraW5nIG9mIA0KPj4+Pj4gc3BlY2lmaWNh
dGlvbiBhbmQgaW1wbGVtZW50YXRpb24uDQo+Pj4+Pg0KPj4+Pj4+IDgwMi4xMSBUR2FpIGlzIHN0
aWxsIGdvaW5nIG9uIGFuZCBpdHMgc3BlY2lmaWNhdGlvbiBpcyBzdWJqZWN0IHRvIA0KPj4+Pj4+
IGNoYW5nZSwgYnV0IEknZCBsaWtlIHRvIGRpc2N1c3MgaW4gSUVURiBESENQIGlzc3VlcyByZWxh
dGVkIHRvIA0KPj4+Pj4+IDgwMi4xMWFpIGFuZCBhcnJhbmdlIEktRCBhY2NvcmRpbmcgdG8gdGhl
IHByb2dyZXNzIG9mIFRHYWkgdGFzayANCj4+Pj4+PiBncm91cC4NCj4+Pj4+DQo+Pj4+PiBJIHRo
aW5rIGl0IGlzIGluZGVlZCBhIGdvb2QgcG9pbnQgdG8gZGlzY3VzcyBzdWNoIGFuIEktRC4NCj4+
Pj4+DQo+Pj4+PiBBbGV4DQo+Pj4+Pg0KPj4+Pj4+DQo+Pj4+Pj4gUmVnYXJkcywNCj4+Pj4+Pg0K
Pj4+Pj4+IEhpcm9raSBOYWthbm8gVHJhbnMgTmV3IFRlY2hub2xvZ3ksIEluYy4gPGNhc0B0cmFu
cy1udC5jb20+DQo+Pj4+Pj4NCj4+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXyBkaGN3ZyBtYWlsaW5nIA0KPj4+Pj4+IGxpc3QgZGhjd2dAaWV0Zi5v
cmcgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaGN3Zw0KPj4+Pj4NCj4+
Pj4+DQo+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPj4+Pj4gZGhjd2cgbWFpbGluZyBsaXN0DQo+Pj4+PiBkaGN3Z0BpZXRmLm9yZw0KPj4+Pj4g
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaGN3Zw0KPj4+PiBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+PiBkaGN3ZyBtYWls
aW5nIGxpc3QNCj4+Pj4gZGhjd2dAaWV0Zi5vcmcNCj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9kaGN3Zw0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCmRoY3dnIG1haWxpbmcgbGlzdA0KZGhjd2dAaWV0Zi5vcmcNCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhjd2cNCg==

From ek@google.com  Thu Mar 14 07:58:29 2013
Return-Path: <ek@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3B0811E81F3 for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 07:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level: 
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCYG2b9pJYZv for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 07:58:29 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id E472A11E820D for <dhcwg@ietf.org>; Thu, 14 Mar 2013 07:58:27 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id tb18so2265156obb.3 for <dhcwg@ietf.org>; Thu, 14 Mar 2013 07:58:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=Bate+ABqB5hXvuQ6dUXUFg/XtWJHItLKHIX8u2thfX8=; b=OrIdEAz7LAKYt9XdEExvAx+AfoBgDle6EucHBzTHLBd+Y18HogpgXGDDaG+BT1cMPQ pJRS+aHEIjtuCai9Dg7EfFFfgrpfj5zizF5W5g0JKxkLPaQXOuQknmS1nP9ZF3UVhyeB EOfIrpEK2uT3vkn/wlcvgje0D/LFNusc5RnyM/I7aj6//lyBZTsDp+O6psHDsEjn27PT +VbngeUAv0pNJeknXginHqDYDSOqyUIuohdegKen9vbwvdN/7dqqZStfrHwoY6qgPoUI Y86MpOjVecejFF/K6aW/6hUUJ2eCLv7EudLT3Vejc4l4rO6PfuLLxE60MYoo5uFkjRAx E1vg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=Bate+ABqB5hXvuQ6dUXUFg/XtWJHItLKHIX8u2thfX8=; b=mYhiP4zLSFtwNVMNhVdbF3i+6wDQs94+qgm28smfpPtUL8IJc3b9i1x5Egc1ndB26J ChsEoWjJjqFYV7uQMVMrddiNWDT48ibxTMdp8v7OFdXpS+d0kydsRA3Veb7gQhvd6iVm oTet8JWGPhX1R1/b32DYm6iMkWAtVqVY95hA78tLRctwx9WoPVwNbcxzQXQwaKizyjAn xbm4TgPLzDj0nubYkYs17g2WOagN30PIK87d4UQe9XkWacKUharE/TDcG6S7uHxJKqjs K6GneFeQW6tyN2zpQexbgaYNhehv//VN/pb6zh6DX4C/0wHFfEJPtN3kWNSjL1Rdztvc vFyg==
X-Received: by 10.60.24.197 with SMTP id w5mr1322336oef.6.1363273107509; Thu, 14 Mar 2013 07:58:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.50.227 with HTTP; Thu, 14 Mar 2013 07:58:07 -0700 (PDT)
In-Reply-To: <5141E286.6050305@trans-nt.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com>
From: Erik Kline <ek@google.com>
Date: Thu, 14 Mar 2013 10:58:07 -0400
Message-ID: <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com>
To: Hiroki Nakano <cas@trans-nt.com>
Content-Type: multipart/alternative; boundary=e89a8ff1c30e4e2a4c04d7e3c166
X-Gm-Message-State: ALoCoQk9KKj/EgaMeVDynkxMAZh3nKpG+zeuVNbDfyx0vUPJZHlirDZCGJUifILV3uwacA+R9Xj3aSOMnHpeUzggL/9u9/jmkIvzQWdo+GJV9ImVonppLmSSUbu7XnTI0wSRR3cZs6YWiewB1esLN/B3v5rzHiSJ7AO3ldiZ1zSkkzKJRDDdkt/6bcp7Ry29+7v356fDzz4N
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Mar 2013 14:58:29 -0000

--e89a8ff1c30e4e2a4c04d7e3c166
Content-Type: text/plain; charset=UTF-8

> Anyway, we are competing right now in 802.11WG TGai.
> I am supporting an DHCP-based protocol for IP address
> assignment and against an 802.11ai original protocol.
> Please help me if you agree with me.
> I can provide more information if you have interest.


Is there a link to a document we can review?

I do not think that anything requiring DHCPv6 for IPv6 address assignment
will work in the general case (furthermore: I think it's a bad idea).

--e89a8ff1c30e4e2a4c04d7e3c166
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Anyway, we are competing right now in 802.11WG TGai.<br>
I am supporting an DHCP-based protocol for IP address<br>
assignment and against an 802.11ai original protocol.<br>
Please help me if you agree with me.<br>
I can provide more information if you have interest.</blockquote><div><br><=
/div><div style>Is there a link to a document we can review?</div><div styl=
e><br></div><div style>I do not think that anything requiring DHCPv6 for IP=
v6 address assignment will work in the general case (furthermore: I think i=
t&#39;s a bad idea).</div>

</div></div></div>

--e89a8ff1c30e4e2a4c04d7e3c166--

From tomasz.mrugalski@gmail.com  Thu Mar 14 08:16:35 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A3CA11E8221 for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 08:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d0db8QguvMd3 for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 08:16:34 -0700 (PDT)
Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) by ietfa.amsl.com (Postfix) with ESMTP id 9686611E8171 for <dhcwg@ietf.org>; Thu, 14 Mar 2013 08:16:34 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rp2so2347218pbb.6 for <dhcwg@ietf.org>; Thu, 14 Mar 2013 08:16:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=biynaEGwSjEFhvPKvCbJE6hEb8Q4/6zIVJSiKKc88Z0=; b=YRWtXhDWm6qgDgafUUbdf1O+dqEBgtQNNL58qWNXoejcSRQsCQKvTC3tYSE5XHvl3t sO86YvD1lHLSFr8TXObcjnUck60DhONNf/RrzJDB+DpyI4Zuv/5DWcp1fmjDEVjzuTIh i2HTY9HILqro2plZrBHJx0ddTV1F7F24mWV1U7RshKy4t6tvs2V2GbWF3CYNuZlpqRnF V0TESV9J2HvWGb+rQV0+8/I7JBiHDhcYCAcL11s7JaX4KCNz9RdKoZHCMTxKEDlAW6Cu HagvKpdeHhpKhvhBiX3EGH+yk66xZAje/1vr8APw4wi9t8QY3+mLzDxMErB3pT+VXySr 2o3w==
X-Received: by 10.68.197.193 with SMTP id iw1mr6764614pbc.86.1363274194343; Thu, 14 Mar 2013 08:16:34 -0700 (PDT)
Received: from dhcp-108b.meeting.ietf.org ([2001:df8:0:16:cabc:c8ff:fedf:daff]) by mx.google.com with ESMTPS id rr14sm3706386pbb.34.2013.03.14.08.16.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 14 Mar 2013 08:16:33 -0700 (PDT)
Message-ID: <5141E9CE.4050407@gmail.com>
Date: Thu, 14 Mar 2013 11:16:30 -0400
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com>, <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com>, <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com>
In-Reply-To: <5141E286.6050305@trans-nt.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Mar 2013 15:16:35 -0000

On 13-03-14 10:45, Hiroki Nakano wrote:
> Other protocols else want to have relation with IP and
> make glue between them and IP in the outside of IETF.
> My concern is that bad glues undermine the heart of IP
> little by little and I believe IETF is the only group
> who can prevent it.
DHCPv4 and v6 are generic protocols that can work on many access
technologies. It would be infeasible to bring in specification on how to
run DHCP on things like Bluetooth, WiMAX, LTE, UMTS and other.

Long time ago I was involved in 802.16 (WiMAX) project. I remember that
there were IEEE documents that explained if/when to use DHCP, should
it be v4 or v6, what specific options to request etc. I still have
802.16-2004 document that discusses in section 9.1.1 DHCP usage. You may
want to take a look at it and shape your TGai document in a similar fashion.

During our discussion it came to my attention that in your scenario
speed is of essence. DHCP mostly (all except elapsed time) uses timer
specified in seconds. If you want change that behavior (e.g.
retransmissions happening much sooner than after 1 second), this would
require changing DHCP protocol. It could potentially warrant a new draft
discussing this issue and potentially proposing solution. If you want to
follow that path, it recommend that you discuss the proposed solution
first on this mailing list before jumping immediately into writing a draft.

Hope that helps,
Tomek


From Ted.Lemon@nominum.com  Thu Mar 14 09:45:25 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C486D11E8120 for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 09:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wr3omIjxVlyu for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 09:45:24 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id 5F25721F8545 for <dhcwg@ietf.org>; Thu, 14 Mar 2013 09:45:24 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUUH+pL/Ta8GmnREoj2x2EWbylsxqUKWc@postini.com; Thu, 14 Mar 2013 09:45:24 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 EDAC91B8974 for <dhcwg@ietf.org>; Thu, 14 Mar 2013 09:45:23 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id E5225190043 for <dhcwg@ietf.org>; Thu, 14 Mar 2013 09:45:23 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 14 Mar 2013 09:45:23 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Late IPR on draft-ietf-dhc-secure-dhcpv6
Thread-Index: AQHOINNRwPBIw8oVoEGpUy+4FiS7cw==
Date: Thu, 14 Mar 2013 16:45:22 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474C392E@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <FE511B35E17D9B4AA5FBD817C380F552@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] Late IPR on draft-ietf-dhc-secure-dhcpv6
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Mar 2013 16:45:26 -0000

This is a formal notice of an IPR policy violation according to rfC3979, se=
ction 6.2.1, by Sheng Jiang, regarding the secure DHCPv6 draft mentioned in=
 the subject of this message.   The working group chairs or AD are responsi=
ble for keeping track of IPR policy violations and imposing appropriate san=
ctions.

The nature of the policy violation is that disclosure of IPR that the autho=
r of the draft believed to cover the draft was made two years after the pub=
lication of the initial individual submission.   DIsclosure of IPR is requi=
red of IETF participants, as documented in the Note Well policy, and it is =
required to be done in a timely manner.   Please see the text here:

	http://tools.ietf.org/html/rfc3979#section-6.2

I do not know the fine details of the sequence of events, but here is the h=
istory from a publication perspective:

=95draft-jiang-dhc-secure-dhcpv6-00 published July 4, 2008
=95draft-ietf-dhc-secure-dhcpv6-00 published April 12, 2010
=95IPR 1343 published June 23, 2010
=95WGLC June 16, 2011

The working group was aware of the IPR at the time of the WGLC, and indeed =
well before the WGLC, and discussed it as it related to the draft.   So thi=
s is not a situation where there is a question as to the consensus to proce=
ed.   The advancement of the draft through the IESG is not affected by conc=
ern for consensus.   However, the late disclosure does affect the advanceme=
nt of the draft, and is what triggered this review of the history of the la=
te IPR disclosure.

RFC6701 requires working group chairs and/or ADs to impose sanctions when I=
PR policy violations have occurred.   RFC6701 provides a list of potential =
sanctions up to and including removing authors from drafts and restricting =
their ability to post on working group mailing lists for periods of time.

The sanction that I have chosen in this case is option d in section 4 of RF=
C6701, which is to announce what happened on the mailing list.   I will als=
o be mentioning this in the working group meeting this afternoon.

I would encourage any and all participants in the working group who have an=
y thoughts of acquiring IPR on IETF work that they may be doing, or are awa=
re of patent applications or similar efforts relating to work they are doin=
g, to review BCP79 and RFC6701 to obtain a clear understanding of what is r=
equired of you in relation to these efforts.


From alexandru.petrescu@gmail.com  Thu Mar 14 18:05:05 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C31811E8151 for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 18:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.044
X-Spam-Level: 
X-Spam-Status: No, score=-10.044 tagged_above=-999 required=5 tests=[AWL=0.205, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id peBvGFtZ6cBC for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 18:05:04 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 384F311E812A for <dhcwg@ietf.org>; Thu, 14 Mar 2013 18:05:04 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2F1525c026623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Fri, 15 Mar 2013 02:05:03 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2F152EW029139 for <dhcwg@ietf.org>; Fri, 15 Mar 2013 02:05:02 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.86.2]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2F14qUm002440 for <dhcwg@ietf.org>; Fri, 15 Mar 2013 02:05:02 +0100
Message-ID: <51427396.1060803@gmail.com>
Date: Fri, 15 Mar 2013 02:04:22 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com>
In-Reply-To: <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Mar 2013 01:05:05 -0000

Le 14/03/2013 15:58, Erik Kline a écrit :
>
> Anyway, we are competing right now in 802.11WG TGai. I am supporting
> an DHCP-based protocol for IP address assignment and against an
> 802.11ai original protocol. Please help me if you agree with me. I
> can provide more information if you have interest.
>
>
> Is there a link to a document we can review?
>
> I do not think that anything requiring DHCPv6 for IPv6 address
> assignment will work in the general case (furthermore: I think it's a
>  bad idea).

Erik, I need to get a moment to discuss about this.

Generally speaking, I think the implicit conclusions of RA for address
autoconfiguration everywhere is little useful.  There exist explicit
cases where only DHCPv6 can help (e.g. Prefix Delegation to a
Machine-class Router needing addresses as well).

On one hand people oppose ND Prefix Delegation and on another hand
people oppose DHCPv6 Default Route.  That obviously leads to the
necessity to use _both_.  Both means double software implementation,
double message exchanges and so on.

Alex

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



From volz@cisco.com  Thu Mar 14 18:11:34 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3F5E21F8CE7 for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 18:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0MXNb+w5PecF for <dhcwg@ietfa.amsl.com>; Thu, 14 Mar 2013 18:11:34 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 10B2B21F8CDE for <dhcwg@ietf.org>; Thu, 14 Mar 2013 18:11:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1679; q=dns/txt; s=iport; t=1363309892; x=1364519492; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=S2G+jZik0J7+68vzKWFm2ARjIYi7KGdEl38+1lOtqto=; b=HAvf5IEW2ytyLl2fNXbVff8nCzJpwJrFH5c2kePQlg+Y69d1rFM4sSsY XssJNa0RHqFZnlWtIYVXVkfziJzq2kn2W5vC/P9GwwNt3wKkikbVvdBqp VuOTvJpPOwXODulX7OD1YrEgBIXj2SpLCnLzLLDSQGz2YTyomlcSOfhZ2 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAMB0QlGtJXHB/2dsb2JhbABDxQSBaxZtB4IyOjcIEgE+QiYBBA6IGcIAjxaCZmEDlliRAoMK
X-IronPort-AV: E=Sophos;i="4.84,848,1355097600"; d="scan'208";a="184699953"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 15 Mar 2013 01:11:29 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r2F1BTdi016558 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 15 Mar 2013 01:11:29 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Thu, 14 Mar 2013 20:11:29 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: draft-bhandari-dhc-class-based-prefix
Thread-Index: Ac4hGgV943Ndq1TURIqrn7irUGh5lQ==
Date: Fri, 15 Mar 2013 01:11:28 +0000
Message-ID: <22247284-28D7-4B6B-B0CE-C272DF36F98A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3E9D50E2C45C8E4AAF3A86DD04C604F2@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] draft-bhandari-dhc-class-based-prefix
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Mar 2013 01:11:35 -0000

I was thinking:

- when prefix classes or properties come via an authenticated interface suc=
h as the mobile (3g/lte) radio interface, the trust and meaning of the "loc=
al" bits might be clear (mapping provided by provider) and perhaps little f=
urther authentication is needed. Though roaming makes this interesting as t=
he "local" meaning of the roaming partner may not be known - and therefore =
only useful when connected to "home" provider. Unlocked devices are also li=
kely to have issues.

- in other cases (i.e., wifi or roaming), the information is unlikely to be=
 trusted and there is no good way to map it to useful things.

So, why not use the DNS for this information? It can be "trusted" with dnss=
ec and use well known names perhaps in the reverse zone for the first hop r=
outer or elsewhere in the tree can be queried and the information exchange =
can be much richer ... perhaps using txt RRs.

This is a bit like mdns advertises services and capabilities of devices, bu=
t in this case it provides the class/property information. It would only be=
 looked up when needed.=20

An application could also query this for application specific information. =
Service providers would need to populate this information as they desire (o=
r not). Some "default" value(s) can also be present which would only be use=
d if the application specific wasn't available.

TTL on records provides an ability to cache them (for appropriate length of=
 time).

Anyway, this may be something to think about as it would be significantly r=
icher it is descriptive ability and be able to provide much finer grained i=
nformation.

- Bernie=

From shwethab@cisco.com  Fri Mar 15 03:59:58 2013
Return-Path: <shwethab@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3808621F8D03 for <dhcwg@ietfa.amsl.com>; Fri, 15 Mar 2013 03:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5W37IWCASiEW for <dhcwg@ietfa.amsl.com>; Fri, 15 Mar 2013 03:59:57 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 6035621F8CF4 for <dhcwg@ietf.org>; Fri, 15 Mar 2013 03:59:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2997; q=dns/txt; s=iport; t=1363345197; x=1364554797; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=cDgYj4I8vjILv6+afg+0vP367JaIjIElmr5rIJr9ooI=; b=guSB+bUijh+NO5TrXq6QRShY6YjapC+9BA0ryHIGYApJwLdYhXKfAAki HPtDqEUn3m7IoyQdDmjO5e84evGdCMHtP88b8NgihBC67Otlp0XkyouGe fIgGCkiQs3VIvEYQSA1+aVkgPCiL2QTs3gQdKtVvHke52c2SGwT8/t7RM s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAIv+QlGtJXHB/2dsb2JhbABDxROBbhZ0giwBBAEBATc0AxoBCCIUNwslAQEEARIIiAwMwiYEjmQ4gl9hA6dcgwqCKA
X-IronPort-AV: E=Sophos;i="4.84,850,1355097600"; d="scan'208";a="187859733"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-3.cisco.com with ESMTP; 15 Mar 2013 10:59:52 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r2FAxp5m007059 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Fri, 15 Mar 2013 10:59:51 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Fri, 15 Mar 2013 05:59:51 -0500
From: "Shwetha Bhandari (shwethab)" <shwethab@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] draft-bhandari-dhc-class-based-prefix
Thread-Index: Ac4hGgV943Ndq1TURIqrn7irUGh5lQAqkLGA
Date: Fri, 15 Mar 2013 10:59:50 +0000
Message-ID: <D760207426D56242BAF68F47647CF1071C585B81@xmb-rcd-x04.cisco.com>
In-Reply-To: <22247284-28D7-4B6B-B0CE-C272DF36F98A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
x-originating-ip: [10.142.105.76]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3663A831310FA64F959BC50D35D9B4B7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] draft-bhandari-dhc-class-based-prefix
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 15 Mar 2013 10:59:58 -0000

Bernie,

We are trying to address:

1. Mapping prefix to metadata
2. Understanding what the metadata means

 For providing the metadata that is attached to prefix itself providing it
via DHCP or RA seems to be inline with what we do in DHCP/SLAAC to make
the prefix usable. draft-bhandari-dhc-class-based-prefix-04 splits
metadata into property that has a well defined meaning. And the
colour/class that is local significance and could be treated as a service.

What you are proposing is useful for (2) to derive addition information
especially for class/colour as it is of local significance and may need a
DNS-SD/mdns or any new proposal that will be made for conveying multiple
provisioning domains. How this will be used by the applications for
influencing SAS - e.g. Will the application be hardcoded to prefer a
certain class in a certain domain or learns this information somehow needs
more thought. If application is picking the class via user interface may
be providing more information will help a user choose and hence more
descriptive information about the class be useful.

Shwetha

On 3/15/13 6:41 AM, "Bernie Volz (volz)" <volz@cisco.com> wrote:

>I was thinking:
>
>- when prefix classes or properties come via an authenticated interface
>such as the mobile (3g/lte) radio interface, the trust and meaning of the
>"local" bits might be clear (mapping provided by provider) and perhaps
>little further authentication is needed. Though roaming makes this
>interesting as the "local" meaning of the roaming partner may not be
>known - and therefore only useful when connected to "home" provider.
>Unlocked devices are also likely to have issues.
>
>- in other cases (i.e., wifi or roaming), the information is unlikely to
>be trusted and there is no good way to map it to useful things.
>
>So, why not use the DNS for this information? It can be "trusted" with
>dnssec and use well known names perhaps in the reverse zone for the first
>hop router or elsewhere in the tree can be queried and the information
>exchange can be much richer ... perhaps using txt RRs.
>
>This is a bit like mdns advertises services and capabilities of devices,
>but in this case it provides the class/property information. It would
>only be looked up when needed.
>
>An application could also query this for application specific
>information. Service providers would need to populate this information as
>they desire (or not). Some "default" value(s) can also be present which
>would only be used if the application specific wasn't available.
>
>TTL on records provides an ability to cache them (for appropriate length
>of time).
>
>Anyway, this may be something to think about as it would be significantly
>richer it is descriptive ability and be able to provide much finer
>grained information.
>
>- Bernie
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg


From mohta@necom830.hpcl.titech.ac.jp  Sun Mar 17 00:19:57 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CFAD21F8745 for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 00:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QktGyvttyFh4 for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 00:19:56 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 4D4F121F8739 for <dhcwg@ietf.org>; Sun, 17 Mar 2013 00:19:56 -0700 (PDT)
Received: (qmail 32106 invoked from network); 17 Mar 2013 07:18:00 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 17 Mar 2013 07:18:00 -0000
Message-ID: <51456E7D.1030600@necom830.hpcl.titech.ac.jp>
Date: Sun, 17 Mar 2013 16:19:25 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com>
In-Reply-To: <51427396.1060803@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Mar 2013 07:19:57 -0000

Alexandru Petrescu wrote:

> On one hand people oppose ND Prefix Delegation and on another hand
> people oppose DHCPv6 Default Route.  That obviously leads to the
> necessity to use _both_.  Both means double software implementation,
> double message exchanges and so on.

Default route may be provided by an 802.11ai original mechanism.

						Masataka Ohta


From ek@google.com  Sun Mar 17 05:23:03 2013
Return-Path: <ek@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB5621F8771 for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 05:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.977
X-Spam-Level: 
X-Spam-Status: No, score=-100.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_BACKHAIR_44=1, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nqBKebznHhIy for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 05:23:02 -0700 (PDT)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 80CEB21F873D for <dhcwg@ietf.org>; Sun, 17 Mar 2013 05:22:59 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id ta14so4526314obb.28 for <dhcwg@ietf.org>; Sun, 17 Mar 2013 05:22:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=vKZ7vgxJZnSNqBqU+G9LQMimxwm3hSzhh4ngccn3/rE=; b=N1DT7Y19Tnuo29Z4ux5YamZ80VSeqrkAaziojiTeQCTIvHoPwesGmlvUqmdubl7kQh JREKyUJ5VnrFcwZjYg1xPtqEgmKnYs4ORk1A4upcCVvGN3jP0+U3HGE0qh+qaLPrnpw1 pOOetFvZum3u4dg3esz7eFWygLpKs2cURqXwmIXQZWn2alVRbRp/Gzg9Qm0F6drROxrM G1+ednlESwkDYUV4i+RlW6GJGqeDL0AY0upGWKoVA2jNFh1b3d05NcTT0tEDAQaHY3qg iC0DzOVhl5Y2f61d76MlbWC2y/C2rin5r/of19VBlAkenXHc1uWHOaY4DN3wO2nQMoGn RWdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=vKZ7vgxJZnSNqBqU+G9LQMimxwm3hSzhh4ngccn3/rE=; b=Nd/hz14XM12/JUXQV1KKG6kipzTX1PTsN3OCRClNU9NpNNg2QxNExdrQ3NDo0ooPQk +ks7DtwpP8SDH0xLOeEFi8IIJN/qkwC60LtS3hu6ocfCUlAwSehdGIc9AkLuOUcw/1dd w4lTzKrajXT+UvLo+wpNjsccDhPGldBwJTkhkr2gN/dNQ4FA0iSwcN6TiI1UQHZ3YKxw 6dJvjoM+gduVzuJnQrdz27zDxmaG/jqrTO6ZctFXcYBZ9ENFYVrPCaCaJAmYWBvUPVlR IdZ0imv5qJCvuxCiYPC6vEAMGIZm5aU4TOcmB6njrJOy1VA9cKg7gy3PtFXYsLLUzXfp EcxA==
X-Received: by 10.60.31.170 with SMTP id b10mr5452757oei.34.1363522978757; Sun, 17 Mar 2013 05:22:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.50.227 with HTTP; Sun, 17 Mar 2013 05:22:38 -0700 (PDT)
In-Reply-To: <51456E7D.1030600@necom830.hpcl.titech.ac.jp>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp>
From: Erik Kline <ek@google.com>
Date: Sun, 17 Mar 2013 08:22:38 -0400
Message-ID: <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Content-Type: multipart/alternative; boundary=e89a8fb1fda4cae49e04d81dee1d
X-Gm-Message-State: ALoCoQnRwvx4b2ODfWiOxTSdaMCNf0/FY7UYmB3XU4VYJ0bnMWeIbuxrb6icM+xeVBmMyVdTdX+N+Usgoe9w6c0/qOnN0s22QYvyjxYGedMgi9MfIMskQUUhy2Ym6ean6qp96IujJznxEThUNfckCMEURtbQaI68y9yV5IpoEVRQCZ2fuhk0KcFTMYFQDbV8dTzqLSB4/JhU
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Mar 2013 12:23:03 -0000

--e89a8fb1fda4cae49e04d81dee1d
Content-Type: text/plain; charset=UTF-8

On 17 March 2013 03:19, Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>wrote:

> Alexandru Petrescu wrote:
>
> > On one hand people oppose ND Prefix Delegation and on another hand
> > people oppose DHCPv6 Default Route.  That obviously leads to the
> > necessity to use _both_.  Both means double software implementation,
> > double message exchanges and so on.
>
> Default route may be provided by an 802.11ai original mechanism.
>

What's the best way to get IETF<->IEEE communication on this then?  If they
(accidentally) do anything that alters the existing IPv6 architecture
requirements without IETF/6man review then...we'll have to sort it all out
somehow.

--e89a8fb1fda4cae49e04d81dee1d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On 17 March 2013 03:19, Masataka Ohta <span dir=3D"ltr">&l=
t;<a href=3D"mailto:mohta@necom830.hpcl.titech.ac.jp" target=3D"_blank">moh=
ta@necom830.hpcl.titech.ac.jp</a>&gt;</span> wrote:<br><div class=3D"gmail_=
extra">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im"=
>Alexandru Petrescu wrote:<br>
<br>
&gt; On one hand people oppose ND Prefix Delegation and on another hand<br>
&gt; people oppose DHCPv6 Default Route. =C2=A0That obviously leads to the<=
br>
&gt; necessity to use _both_. =C2=A0Both means double software implementati=
on,<br>
&gt; double message exchanges and so on.<br>
<br>
</div>Default route may be provided by an 802.11ai original mechanism.<br><=
/blockquote><div><br></div><div style>What&#39;s the best way to get IETF&l=
t;-&gt;IEEE communication on this then? =C2=A0If they (accidentally) do any=
thing that alters the existing IPv6 architecture requirements without IETF/=
6man review then...we&#39;ll have to sort it all out somehow.</div>

</div></div></div>

--e89a8fb1fda4cae49e04d81dee1d--

From Ted.Lemon@nominum.com  Sun Mar 17 05:45:26 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7522C21F87BB for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 05:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.099
X-Spam-Level: 
X-Spam-Status: No, score=-106.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, J_BACKHAIR_44=1, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1v+e3msr3KA for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 05:45:25 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 6B19121F8782 for <dhcwg@ietf.org>; Sun, 17 Mar 2013 05:45:25 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUUW65aWtKY9cokMVDqd/rlSycWNqRslw@postini.com; Sun, 17 Mar 2013 05:45:25 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 089B41B8F62 for <dhcwg@ietf.org>; Sun, 17 Mar 2013 05:45:25 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 000DF190043; Sun, 17 Mar 2013 05:45:24 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 17 Mar 2013 05:45:24 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Erik Kline <ek@google.com>
Thread-Topic: [dhcwg] IEEE 802.11ai and DHCP
Thread-Index: AQHOCV8l67TaS/hjlkqOnzgfAu5xSph4PSmAgCxTuICAAAHkgIAAE+6AgAAXeICAASmQAIAAA4uAgACpYgCAA410gIAAVLgAgAAGXYA=
Date: Sun, 17 Mar 2013 12:45:24 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775110F19@mbx-01.win.nominum.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com>
In-Reply-To: <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <73991F842C500D4EAA319D41106BD79C@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Mar 2013 12:45:26 -0000

On Mar 17, 2013, at 8:22 AM, Erik Kline <ek@google.com> wrote:
> What's the best way to get IETF<->IEEE communication on this then?  If th=
ey (accidentally) do anything that alters the existing IPv6 architecture re=
quirements without IETF/6man review then...we'll have to sort it all out so=
mehow.

I don't think 802.11ai wants to do this by accident.   They want to do it b=
ecause the IETF doesn't have consensus to do it.   So I think it's unrealis=
tic to propose that the IEEE would not do this work because it wouldn't get=
 past 6man.   That's not the relationship that exists between IETF and IEEE=
.   If you want to participate in IEEE's process, you pretty much have to g=
o to IEEE.


From mohta@necom830.hpcl.titech.ac.jp  Sun Mar 17 07:54:18 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D4F21F85D7 for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 07:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xycuqF-gcJTQ for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 07:54:18 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id B602921F85DA for <dhcwg@ietf.org>; Sun, 17 Mar 2013 07:54:17 -0700 (PDT)
Received: (qmail 39816 invoked from network); 17 Mar 2013 14:52:19 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 17 Mar 2013 14:52:19 -0000
Message-ID: <5145D901.2030406@necom830.hpcl.titech.ac.jp>
Date: Sun, 17 Mar 2013 23:53:53 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775110F19@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775110F19@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Mar 2013 14:54:18 -0000

Ted Lemon wrote:

> I don't think 802.11ai wants to do this by accident.   They want
> to do it because the IETF doesn't have consensus to do it.
> So I think it's unrealistic to propose that the IEEE would not do
> this work because it wouldn't get past 6man.

And, it will motivate IETF to make its protocols consistent.

						Masataka Ohta

From ek@google.com  Sun Mar 17 08:03:19 2013
Return-Path: <ek@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF8D21F8921 for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 08:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.477
X-Spam-Level: 
X-Spam-Status: No, score=-101.477 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7IR2yz8qX+rQ for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 08:03:19 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id E4A7421F88E5 for <dhcwg@ietf.org>; Sun, 17 Mar 2013 08:03:18 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id ni5so4587912obc.26 for <dhcwg@ietf.org>; Sun, 17 Mar 2013 08:03:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=VpUbdQNmAPjQdOG4CrjgxOS8ROaHszNy4diQbnfmPcY=; b=M76EmQ2a49nuGMrh664VnQHzDBuEhwgLogK8GmeYZmeFrPTu7GlajtL0cWmV9W8JQV 9x53mm4NNaQXV6UcEgZhQFeR7SZmtT+nMWp86wK9CQrRJoPdVgRVMufIjg/5ok/BmLbp ilcYg7reFiZbVlnWIV75ZcJ9bgMyCItUR7PAaUfBjlv7DKUuy3IKOVcpQFcuAKXDPleW /mrCgsgTWT1eF/JBxC56J82TGj5ENfKSFsgoCBN+KmxiwJ85oyOCN/Ug89KMGd79ICxo Wi0+lzPkWJMWC3Q+ROzJTN+dsfsi8CZUNwFqAqcu8oUzJEnFmM572ruy2kVpPyE4U87h crPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=VpUbdQNmAPjQdOG4CrjgxOS8ROaHszNy4diQbnfmPcY=; b=Yi5dkkTxZQKxoi1YaPY8SC1dGqADOV6WtdcjbkpHodON95lL+I9Q5iApjE7dtkZ2Pp 1aI5Bb6L4nQJL7yW7TT2TsdVvBzmm6sy1En3jfcIr3KU14onXJTCLhg3y5S2SPVCISdd ud2ZprNBrL8Q9VoTQX+Dyc0EwgkJq+wd5isG19Lj4/3VbwQqiSKPaph73kOYmFFWX+g6 +ZmrCRocmZdoybQXTwvdrrmGe0VgWAE7cojRzk0+TWl72RqCURcZhT2aktKE1zI12pB8 M0LwNk3QEm3wWBLaKBOC672N7jJSn+SCDKWVWcZFWlRzMdhI7fFa45IngEbhIAGtETWX I6+g==
X-Received: by 10.60.10.226 with SMTP id l2mr5758182oeb.67.1363532598343; Sun, 17 Mar 2013 08:03:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.50.227 with HTTP; Sun, 17 Mar 2013 08:02:57 -0700 (PDT)
In-Reply-To: <5145D901.2030406@necom830.hpcl.titech.ac.jp>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775110F19@mbx-01.win.nominum.com> <5145D901.2030406@necom830.hpcl.titech.ac.jp>
From: Erik Kline <ek@google.com>
Date: Sun, 17 Mar 2013 11:02:57 -0400
Message-ID: <CAAedzxrS3FP9sCUYTewj2rxqbWAHTfNxZ3KpQAsd9b2p2PghNw@mail.gmail.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Content-Type: multipart/alternative; boundary=e89a8fb1f8d02ac6e304d8202c6d
X-Gm-Message-State: ALoCoQlNXxQK0BArewECZniH8qAP9FEch8mN3CBq+kMEGH/NDGtOHQaBx3yiiXrvLGAyW684EEsS65WteOABZkr67uQNSvtqKwe3229saDbSN/l0+coPqhYhge1eUPym9q0Xm1QR65S67yF/xCUlqf3Etpe4fORBLKcYvFTTudMfnkl+XHUVimxOKxfMSSVyeo6NBn2FHWDh
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Mar 2013 15:03:19 -0000

--e89a8fb1f8d02ac6e304d8202c6d
Content-Type: text/plain; charset=UTF-8

On 17 March 2013 10:53, Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>wrote:

> Ted Lemon wrote:
>
> > I don't think 802.11ai wants to do this by accident.   They want
> > to do it because the IETF doesn't have consensus to do it.
> > So I think it's unrealistic to propose that the IEEE would not do
> > this work because it wouldn't get past 6man.
>
> And, it will motivate IETF to make its protocols consistent.


In the minds of those for whom RAs are satisfactory, they are (pretty)
consistent.

--e89a8fb1f8d02ac6e304d8202c6d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On 17 March 2013 10:53, Masataka Ohta <span dir=3D"ltr">&l=
t;<a href=3D"mailto:mohta@necom830.hpcl.titech.ac.jp" target=3D"_blank">moh=
ta@necom830.hpcl.titech.ac.jp</a>&gt;</span> wrote:<br><div class=3D"gmail_=
extra">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im"=
>Ted Lemon wrote:<br>
<br>
&gt; I don&#39;t think 802.11ai wants to do this by accident. =C2=A0 They w=
ant<br>
&gt; to do it because the IETF doesn&#39;t have consensus to do it.<br>
&gt; So I think it&#39;s unrealistic to propose that the IEEE would not do<=
br>
&gt; this work because it wouldn&#39;t get past 6man.<br>
<br>
</div>And, it will motivate IETF to make its protocols consistent.</blockqu=
ote><div><br></div><div style>In the minds of those for whom RAs are satisf=
actory, they are (pretty) consistent.</div></div></div></div>

--e89a8fb1f8d02ac6e304d8202c6d--

From alexandru.petrescu@gmail.com  Sun Mar 17 09:17:28 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8389621F8C96 for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 09:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.734
X-Spam-Level: *
X-Spam-Status: No, score=1.734 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, J_BACKHAIR_44=1, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6aoJk9ysYa6O for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 09:17:28 -0700 (PDT)
Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id AD49B21F8C8F for <dhcwg@ietf.org>; Sun, 17 Mar 2013 09:17:26 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr (Postfix) with ESMTP id B1A5794015E for <dhcwg@ietf.org>; Sun, 17 Mar 2013 17:17:18 +0100 (CET)
Message-ID: <5145EC8D.3020502@gmail.com>
Date: Sun, 17 Mar 2013 17:17:17 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com>
In-Reply-To: <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 130317-0, 17/03/2013), Outbound message
X-Antivirus-Status: Clean
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Mar 2013 16:17:28 -0000

Le 17/03/2013 13:22, Erik Kline a écrit :
> On 17 March 2013 03:19, Masataka Ohta
> <mohta@necom830.hpcl.titech.ac.jp
> <mailto:mohta@necom830.hpcl.titech.ac.jp>> wrote:
>
> Alexandru Petrescu wrote:
>
>> On one hand people oppose ND Prefix Delegation and on another hand
>>  people oppose DHCPv6 Default Route.  That obviously leads to the
>> necessity to use _both_.  Both means double software
>> implementation, double message exchanges and so on.
>
> Default route may be provided by an 802.11ai original mechanism.
>
>
> What's the best way to get IETF<->IEEE communication on this then?

At IETF there are several people involved in the liaison process IETF-IEEE.

I noticed this in the 802.11p and 802.15.4 contexts.

> If they (accidentally) do anything that alters the existing IPv6
> architecture requirements without IETF/6man review then...we'll have
> to sort it all out somehow.

I agree.  Yes, and I can explain why this is needed, depending on the
existing status of advancement of 802.11ai and default route assignment.
(e.g. is the default router assigned by an exclusively link-layer message?)

This could be discussed.

Alex

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


From ek@google.com  Sun Mar 17 10:29:41 2013
Return-Path: <ek@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A012A21F8A64 for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 10:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.726
X-Spam-Level: 
X-Spam-Status: No, score=-102.726 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njWe9URfNY+z for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 10:29:40 -0700 (PDT)
Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46]) by ietfa.amsl.com (Postfix) with ESMTP id BF85321F8A4A for <dhcwg@ietf.org>; Sun, 17 Mar 2013 10:29:40 -0700 (PDT)
Received: by mail-oa0-f46.google.com with SMTP id k1so4901182oag.19 for <dhcwg@ietf.org>; Sun, 17 Mar 2013 10:29:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=LJec7yRij/ZGsgzpdNbKKibgVKpwTklhTPN4WwUDJOk=; b=Cv2e9R+MPyRdJ9bV5F/dZgIucAIE5LWCNmdxIKhx/m53QM/lakxq0zSYvsyXdIUO5s C4uxPPMda5ijB8J3yT2WyXmNott1pobk5GKXYhmtZWUEFy9M4cFGpjuB2emLK3nzUONF Y6XKzWQ1Lyd0RtuKrb4o98sqL3xyOkw3kpgbG3a7Jwug4Lm3NcJ1SPNNKVVJVMmi+Xz8 m6tuLcrm3AVnhT29sxOKv6sm0ny+glBHCnkIXdVh/QdqouIFLCTrhYXnEqOTbvQZYJZ5 XpgmNgOEx1n4My8f2PwcvGHfZ1zN5FEAtaoUjyDS5DrL8NVR/yMlIKzHl1kt8hmD+xYp Z8Vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=LJec7yRij/ZGsgzpdNbKKibgVKpwTklhTPN4WwUDJOk=; b=TsssJHh7AgAuvm39LP7ymvm/v89KQhpJmzUbyFsoSWFn7bdCDtV1vTAS9cNuAk+7Wz 4Ql3wRl6+0sigUVPnicag8903beWRraXOXcEuYxBZJpMeo8ZGUh2X49UWCHXJ0E9/jAx tewko71sKIPzzWi5EEScYKCrk0TbB4k2Gik5fbiPx6pLrQ9m6Xg/5FV4IT45rR/wyZxH mK8R3QPk/OzKe4ACAoFyxQnugLw0lrHdo4epCJMTSMF5V03pU+hpS841SX8NMwDiBtoM pbLx7dox6BjXn18SPjXh0x/NjFhHB1WavaKAo3ToEtfD1BonJRf4yV7PkLOgWAy9oPVA /7EA==
X-Received: by 10.182.144.73 with SMTP id sk9mr813794obb.20.1363541380260; Sun, 17 Mar 2013 10:29:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.50.227 with HTTP; Sun, 17 Mar 2013 10:29:20 -0700 (PDT)
In-Reply-To: <5145EC8D.3020502@gmail.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com>
From: Erik Kline <ek@google.com>
Date: Sun, 17 Mar 2013 13:29:20 -0400
Message-ID: <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=14dae9340d499b7bd704d82237da
X-Gm-Message-State: ALoCoQnWguLYjY84yEvXfI+WLlWaHcetIeWyt2JH4cVweitFE/D+LYbfzZH3JrAoTYeqKRqqELqxGTc5e6BP/4LIgZvoCbROmRPY3BPdq8wuT0ly4ul33IPA+4kX9FMe3RvQtwQD9tjC/9dMgiC1V9/W02JVKZLnbci4RDyrPnhyDI84zS3a1LyHiKchZEsiCTkJJE9XO70J
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Mar 2013 17:29:41 -0000

--14dae9340d499b7bd704d82237da
Content-Type: text/plain; charset=UTF-8

If they (accidentally) do anything that alters the existing IPv6

>  architecture requirements without IETF/6man review then...we'll have
>> to sort it all out somehow.
>>
>
> I agree.  Yes, and I can explain why this is needed, depending on the
> existing status of advancement of 802.11ai and default route assignment.
> (e.g. is the default router assigned by an exclusively link-layer message?)
>
> This could be discussed.
>

Well, we know that we disagree.

Of course, if there is to be a discussion I suspect that this list is
probably not the right venue, meaning that I suspect that >80-90% of the
subscribers don't care about this particular issue and there are probably
those not on this list who do.

To clarify, might we be talking about the contents of section 5 of:


https://mentor.ieee.org/802.11/dcn/12/11-12-0151-15-00ai-proposed-specification-framework-for-tgai.docx

I'm not sure I've got the right doc, but anyway, I'll see about how
possible participation in the IEEE process, I guess.

--14dae9340d499b7bd704d82237da
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"color:rgb(80,0,80)">If they (accidentally) =
do anything that alters the existing IPv6</span><br><div class=3D"gmail_ext=
ra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204=
,204);border-left-style:solid;padding-left:1ex">

<div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-=
left-style:solid;padding-left:1ex">
architecture requirements without IETF/6man review then...we&#39;ll have<br=
>
to sort it all out somehow.<br>
</blockquote>
<br></div>
I agree. =C2=A0Yes, and I can explain why this is needed, depending on the<=
br>
existing status of advancement of 802.11ai and default route assignment.<br=
>
(e.g. is the default router assigned by an exclusively link-layer message?)=
<br>
<br>
This could be discussed.<br></blockquote><div><br></div><div style>Well, we=
 know that we disagree.</div><div style><br></div><div style>Of course, if =
there is to be a discussion I suspect that this list is probably not the ri=
ght venue, meaning that I suspect that &gt;80-90% of the subscribers don&#3=
9;t care about this particular issue and there are probably those not on th=
is list who do.</div>

<div style><br></div><div style>To clarify, might we be talking about the c=
ontents of section 5 of:</div><div style><br></div><div style>=C2=A0 =C2=A0=
=C2=A0<a href=3D"https://mentor.ieee.org/802.11/dcn/12/11-12-0151-15-00ai-p=
roposed-specification-framework-for-tgai.docx">https://mentor.ieee.org/802.=
11/dcn/12/11-12-0151-15-00ai-proposed-specification-framework-for-tgai.docx=
</a></div>

<div style><br></div><div style>I&#39;m not sure I&#39;ve got the right doc=
, but anyway, I&#39;ll see about how possible participation in the IEEE pro=
cess, I guess.</div></div></div></div>

--14dae9340d499b7bd704d82237da--

From alexandru.petrescu@gmail.com  Sun Mar 17 11:09:23 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F11B721F8A8E for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 11:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.534
X-Spam-Level: *
X-Spam-Status: No, score=1.534 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, J_CHICKENPOX_13=0.6, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uNA6u8i0-OUp for <dhcwg@ietfa.amsl.com>; Sun, 17 Mar 2013 11:09:22 -0700 (PDT)
Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id E5C8F21F8A85 for <dhcwg@ietf.org>; Sun, 17 Mar 2013 11:09:20 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr (Postfix) with ESMTP id E0D149401BA; Sun, 17 Mar 2013 19:09:14 +0100 (CET)
Message-ID: <514606CA.5010703@gmail.com>
Date: Sun, 17 Mar 2013 19:09:14 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Erik Kline <ek@google.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com>
In-Reply-To: <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 130317-0, 17/03/2013), Outbound message
X-Antivirus-Status: Clean
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Mar 2013 18:09:23 -0000

Le 17/03/2013 18:29, Erik Kline a Ã©crit :
> If they (accidentally) do anything that alters the existing IPv6
>
> architecture requirements without IETF/6man review then...we'll have
>  to sort it all out somehow.
>
>
> I agree.  Yes, and I can explain why this is needed, depending on the
> existing status of advancement of 802.11ai and default route
> assignment. (e.g. is the default router assigned by an exclusively
> link-layer message?)
>
> This could be discussed.
>
>
> Well, we know that we disagree.
>
> Of course, if there is to be a discussion I suspect that this list
> is probably not the right venue, meaning that I suspect that >80-90%
> of the subscribers don't care about this particular issue and there
> are probably those not on this list who do.

It's not the only group where this particular topic is of interest only
to a minority.  There is 6MAN, v6ops, MIF.  MIF drops this out of its
new Charter.

When one requests a new email list at IETF one needs to think about its
name... what would a name be?

Alex

>
> To clarify, might we be talking about the contents of section 5 of:
>
> https://mentor.ieee.org/802.11/dcn/12/11-12-0151-15-00ai-proposed-specification-framework-for-tgai.docx
>
>
>
I'm not sure I've got the right doc, but anyway, I'll see about how
> possible participation in the IEEE process, I guess.


From cas@trans-nt.com  Mon Mar 18 12:55:12 2013
Return-Path: <cas@trans-nt.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61DEA21F90CA for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 12:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.481
X-Spam-Level: 
X-Spam-Status: No, score=-0.481 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sctQfEt5qt0W for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 12:55:10 -0700 (PDT)
Received: from dump.fs.trans-nt.com (smtp.trans-nt.co.jp [202.10.98.251]) by ietfa.amsl.com (Postfix) with SMTP id 758D321F90C8 for <dhcwg@ietf.org>; Mon, 18 Mar 2013 12:55:10 -0700 (PDT)
Received: (qmail 10485 invoked from network); 19 Mar 2013 04:55:02 +0900
Received: from red.fs.trans-nt.co.jp (HELO platinum.local) (202.10.98.240) by smtp.trans-nt.co.jp with SMTP; 19 Mar 2013 04:55:02 +0900
Message-ID: <51477117.8090702@trans-nt.com>
Date: Tue, 19 Mar 2013 04:55:03 +0900
From: Hiroki Nakano <cas@trans-nt.com>
Organization: cas authorized 53a6c6e30f1471298320e605c741e412
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com>
In-Reply-To: <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 18 Mar 2013 19:55:12 -0000

(13/03/18 2:29), Erik Kline wrote:
> I'm not sure I've got the right doc, but anyway, I'll see about how
> possible participation in the IEEE process, I guess.

The bimonthly week of TGai has been started today
in the same place as IETF86 of the last week.
The battle is a draw for now.

https://mentor.ieee.org/802.11/dcn/13/11-13-0040-04-00ai-higher-layer-packet-container-proposal-text.doc
https://mentor.ieee.org/802.11/dcn/13/11-13-0267-00-00ai-fils-ip-address-setup.doc

Come and join us, please.

Regards,

Hiroki Nakano
Trans New Technology, Inc. <cas@trans-nt.com>

From Ted.Lemon@nominum.com  Mon Mar 18 13:12:44 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCB5E21F90E0 for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 13:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.584
X-Spam-Level: 
X-Spam-Status: No, score=-106.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PaucsBiGiCOY for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 13:12:44 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 451A521F90DB for <dhcwg@ietf.org>; Mon, 18 Mar 2013 13:12:44 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUUd1O7lzmwZ+UGH7BEWNioXB4+cIixwX@postini.com; Mon, 18 Mar 2013 13:12:44 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 529B61B845D for <dhcwg@ietf.org>; Mon, 18 Mar 2013 13:12:43 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 49D69190043; Mon, 18 Mar 2013 13:12:43 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 18 Mar 2013 13:12:43 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Hiroki Nakano <cas@trans-nt.com>
Thread-Topic: [dhcwg] IEEE 802.11ai and DHCP
Thread-Index: AQHOCV8l67TaS/hjlkqOnzgfAu5xSph4PSmAgCxTuICAAAHkgIAAE+6AgAAXeICAASmQAIAAA4uAgACpYgCAA410gIAAVLgAgABBj4CAABQhAIABuwyAgAAE7gA=
Date: Mon, 18 Mar 2013 20:12:43 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077511326B@mbx-01.win.nominum.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com>
In-Reply-To: <51477117.8090702@trans-nt.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D0ED63BB953C18449C1E3CD006584F93@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 18 Mar 2013 20:12:45 -0000

On Mar 18, 2013, at 3:55 PM, Hiroki Nakano <cas@trans-nt.com> wrote:
> The bimonthly week of TGai has been started today
> in the same place as IETF86 of the last week.
> The battle is a draw for now.

Are you going to discuss this further in this IEEE meeting, or is that it u=
ntil next time?


From volz@cisco.com  Mon Mar 18 19:08:48 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1068921F8AB8 for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 19:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmabK+Gx48Zo for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 19:08:47 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 59F9A21F89EE for <dhcwg@ietf.org>; Mon, 18 Mar 2013 19:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2837; q=dns/txt; s=iport; t=1363658925; x=1364868525; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Y5O79gse155F1NdN4ooAv5K1NtCU5iOuBkylhCxpIz8=; b=bqfhk1wPQY1tx10iechRQfNdORMEroQL06y08oH7yuTMVjSU8SO+8dkJ VB8gZA3+uXqX5/aRzNczOc8vjF6anF1hmx6djHku6nDRTeJx29Qtl4/7L kzlkraUdCP4uIaWI08pYY/2BjKd+cvvvpFWUTGTglUGliJW86LevlrJ6+ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGrHR1GtJV2Z/2dsb2JhbABDxUCBYBZ0giQBAQEEAQEBNzQLDAQCAQgOAwQBAQEKFAkHJwsUCQgCBA4FCIgMDLIkkBIEjU+BECYLBwaCWWEDkl6VAoJ9DYIo
X-IronPort-AV: E=Sophos;i="4.84,868,1355097600"; d="scan'208";a="188915168"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP; 19 Mar 2013 02:08:45 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2J28hdH026673 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Mar 2013 02:08:43 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Mon, 18 Mar 2013 21:08:44 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Hiroki Nakano <cas@trans-nt.com>
Thread-Topic: [dhcwg] IEEE 802.11ai and DHCP
Thread-Index: AQHOJBKEJJu+cpOVXkawlUU3s7UPxZisP8SA
Date: Tue, 19 Mar 2013 02:08:43 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E184B6468@xmb-rcd-x04.cisco.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com>	<51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com>
In-Reply-To: <51477117.8090702@trans-nt.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 02:08:48 -0000

You might work DHCPv6 into your proposal (similar to DHCPv4 - though it isn=
't explicitly mentioned whereas stateless is).

It is important to note in your design that if the client doesn't do all of=
 the things, it can still work (although a bit slower). Whereas with the ot=
her technique a lot has to change.

You might note that there are a lot of other configuration items that come =
along for virtually nothing when doing DHCP and, although in many Wi-Fi net=
works it probably isn't used a lot, but the DHCP could be set up to do DNS =
updates on the client's behalf. It also doesn't look like there is any way =
to communicate the domain name search list (clients could do DHCPINFORMs / =
INFORMATION-REQUEST later to get at least these other configuration items).

Also, how will the other technique work when the client attempts to do DHCP=
? Seems like a lot of change to the client stack, especially as hopefully t=
his switch between 802.11ai and non-802.11ai interfaces should be smooth an=
d transparent? I don't believe these would usually look like different inte=
rfaces to the client? But we don't know what the full standard says. So how=
 will this other technique co-exist with non-802.11ai interfaces in a provi=
ders network (i.e., they have been using DHCP to configure their clients an=
d now when they switch to 802.11ai they need to do something new or differe=
nt).

Also, there is no way to move between APs (even 802.11ai) since there are d=
ifferent address allocation techniques (in your approach as the DHCP server=
 is used, it could give out the same address if the network supports a flat=
 address space). In the other technique the AP might communicate to some ce=
ntral controller, but now you'd need a protocol for conveying the address i=
nformation between the AP and central controller?

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of H=
iroki Nakano
Sent: Monday, March 18, 2013 3:55 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP

(13/03/18 2:29), Erik Kline wrote:
> I'm not sure I've got the right doc, but anyway, I'll see about how=20
> possible participation in the IEEE process, I guess.

The bimonthly week of TGai has been started today in the same place as IETF=
86 of the last week.
The battle is a draw for now.

https://mentor.ieee.org/802.11/dcn/13/11-13-0040-04-00ai-higher-layer-packe=
t-container-proposal-text.doc
https://mentor.ieee.org/802.11/dcn/13/11-13-0267-00-00ai-fils-ip-address-se=
tup.doc

Come and join us, please.

Regards,

Hiroki Nakano
Trans New Technology, Inc. <cas@trans-nt.com> _____________________________=
__________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

From alexandru.petrescu@gmail.com  Mon Mar 18 19:28:09 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5AA421F8BBB for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 19:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.131
X-Spam-Level: 
X-Spam-Status: No, score=-11.131 tagged_above=-999 required=5 tests=[AWL=1.118, BAYES_00=-2.599, GB_I_INVITATION=-2, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vW5I3fGvj2Wa for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 19:28:08 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 5BCFE21F8EDE for <dhcwg@ietf.org>; Mon, 18 Mar 2013 19:28:08 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2J2S5dh024949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Tue, 19 Mar 2013 03:28:05 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2J2S5aN007532 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 03:28:05 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.86.1]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2J2Rr3I004579 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 03:28:04 +0100
Message-ID: <5147CD03.7060105@gmail.com>
Date: Tue, 19 Mar 2013 03:27:15 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com>
In-Reply-To: <51477117.8090702@trans-nt.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP and IPv6 Gateway assignment
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 02:28:09 -0000

Hello,

In this, there are two questions:
- is is appropriate to assign this Gateway IPv6 Address and its MAC
   address by using a link-layer protocol instead of IPv6 protocols?
- is it appropriate to assign this Gateway IPv6 Address and its MAC
   address by using DHCPv6 instead of ND protocol?

My responses is yes and yes, depending on context.

What do you think?

And, I must check whether the way of assignment by using the link layer
protocol is enough for what the IPv6 ND protocol needs.  Does the link 
layer protocol way of assigning the IPv6 Gateway provide a lifetime? 
(the lifetime is necessary in the ND's data structures for this 
Gateway).  Is it able to provide _several_ such IPv6 Gateways? 
(typically it is not forbidden by IPv6 implementations to have several 
default routes).

See below for my interpretation.

Le 18/03/2013 20:55, Hiroki Nakano a écrit :
> (13/03/18 2:29), Erik Kline wrote:
>> I'm not sure I've got the right doc, but anyway, I'll see about
>> how possible participation in the IEEE process, I guess.
>
> The bimonthly week of TGai has been started today in the same place
> as IETF86 of the last week. The battle is a draw for now.
>
> https://mentor.ieee.org/802.11/dcn/13/11-13-0040-04-00ai-higher-layer-packet-container-proposal-text.doc
>
>
https://mentor.ieee.org/802.11/dcn/13/11-13-0267-00-00ai-fils-ip-address-setup.doc
>


I quickly went through the documents.

In the first, there is this new parameter to the function
MLME-ASSOCIATE.confirm(...FILS IP Address Assignment Data...)

Associate.Confirm is a link layer message sent to the Client, in
response to a request.

This containq "Assigned IPv6 address, Gateway IPv6 address and IPv6
Gateway MAC Address are included if this bit is set to ‘1’" as the Table
-8.4.2.ai1.ai2-1 "IP Address Response Control" says.

This is a mix of what IETF protocols do.  The 'IPv6 address'
is currently provided by either the couple RFC4862 "Stateless Address
Autoconfiguration" and RFC2464 "IPv6 over Ethernet", or by RFC3315
"DHCPv6".  The 'Gateway IPv6 Address' is provided only by RFC4861
"Neighbor Discovery in IPv6" by setting the Router Lifetime to non-zero;
the MAC address of this Gateway is present in the Neigbor Advertisement
message of same RFC4861 (only ND RFC4861, not DHCPv6).

Remark, currently DHCPv6 contrary to DHCPv4 does not provide neither the
Gateway IPv6 Address nor its corresponding MAC Address. (except the
following individual IETF submission draft-mouton-mif-dhcpv6-drlo-02.txt
"Default Router List Option for DHCPv6 (DRLO)" - which does assign the
IPv6 address of the Default Router and its MAC address by using DHCPv6.)

In this, there are two questions:
- is is appropriate to assign this Gateway IPv6 Address and its MAC
   address by using a link-layer protocol instead of IPv6 protocols?
- is it appropriate to assign this Gateway IPv6 Address and its MAC
   address by using DHCPv6 instead of ND protocol?

My oppinion is yes and yes, because of the context.

What do you think?

And, I must check whether the way of assignment by using the link layer
protocol is enough for what the ND protocol needs. Is the link layer
protocol way of assigning the IPv6 Gateway provide a lifetime? (the
lifetime is necessary in the ND's data structures for this Gateway). Is
it able to provide _several_ such IPv6 Gateways? (typically it is not
forbidden by IPv6 implementations to have several default routes).

> Come and join us, please.

Thank you for the invitation!  Noted.  I guess IETFers are already
there.

I would like to add that there is much ongoing private discussion right
now about the use of DHCPv6 to assign routes/defaultRouters/src-based
routes to a Client.  It was discussed until now since 3-4 years in 6MAN
Working Group, DHC WG, MIF WG.  Right now much of this discussion
happens privately.  I would like there to be a common unique place where
to discuss this DHCPv6 routes/DefRoutes/src-based routes, and 
relationship to 802.11ai.

Our new Area Director expressed will for setting up such a list, if 
there is enough interest:
http://www.ietf.org/mail-archive/web/mif/current/msg02068.html

Alex


>
> Regards,
>
> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>



From volz@cisco.com  Mon Mar 18 20:25:15 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56C0321F8613 for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 20:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFqMsKW1vA9V for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 20:25:14 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 29D1C21F860B for <dhcwg@ietf.org>; Mon, 18 Mar 2013 20:25:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11850; q=dns/txt; s=iport; t=1363663514; x=1364873114; h=from:to:subject:date:message-id:mime-version; bh=MhwiFUpfJTMXK+DK1eCZEgfwVZBsSm5ncKEMgf89npA=; b=ISH1qae6wYuAEM4LLDg2tPkNrVnhMSDm8GxzcLQwsudG4ii4Sb93/Kvb QamMnro+JBC7UyvIbO2dUCY0yOQVs6uz1Z8jhHGOYbRkuKRPjvTzhmtfp avm9wiORcWMkoudHs3uFwp9gspg7M1Npt20aqEqjYGqlewr4n63BMzl3m Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAOvZR1GtJV2d/2dsb2JhbABDiDK9fnQWbQeCKyNLHQE9DQIEMCYBBByICwyhGY5VgkCQFI1FC4N0MmEDkxiDRpECgn0NgXM
X-IronPort-AV: E=Sophos;i="4.84,868,1355097600";  d="scan'208,217";a="188932012"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 19 Mar 2013 03:25:13 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r2J3PD7p016961 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 19 Mar 2013 03:25:13 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Mon, 18 Mar 2013 22:25:13 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Reminder about IETF IPR Policy
Thread-Index: Ac4kUV4d5RWdm6zMQTKymlHt0wp7Pg==
Date: Tue, 19 Mar 2013 03:25:13 +0000
Message-ID: <33789EF9-2EBA-42E4-9902-98D320ED4846@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_33789EF92EBA42E4990298D320ED4846ciscocom_"
MIME-Version: 1.0
Subject: [dhcwg] Reminder about IETF IPR Policy
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 03:25:15 -0000

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

VGhlIGZvbGxvd2luZyBpcyBhIGdvb2QgcmVtaW5kZXIgYWJvdXQgdGhlIElFVEYgSVBSIHBvbGlj
eSB0aGUgS2F0bGVlbiBNb3JpYXJ0eSBzZW50IHRvIHRoZSBNSUxFIFdHIGluIEF1Z3VzdCAyMDEy
LiBJIHJlcGxhY2VkIE1JTEUgd2l0aCBESEM6DQoNCkRlYXIgREhDIFdHOg0KDQpBcyBESEMgV0cg
Y2hhaXJzLCB3ZSB3b3VsZCBsaWtlIHRvIG1pbmltaXplIG9yIGhvcGVmdWxseSBldmVuIGVsaW1p
bmF0ZSBsYXRlIGRpc2Nsb3N1cmVzIHJlbGF0aW5nIHRvIGRvY3VtZW50cyB1bmRlciBjb25zaWRl
cmF0aW9uIHdpdGhpbiB0aGUgREhDIFdHLiAgVGhlcmVmb3JlIHlvdSBtaWdodCBzZWUgdXMgc2Vu
ZCAicmVtaW5kZXIiIG1lc3NhZ2VzIGluIHRoZSBmdXR1cmUgdG8gYXV0aG9ycyBvciB0byB0aGUg
REhDIFdHIGVtYWlsIGxpc3QgYXMgYSB3aG9sZSwgYXNraW5nIHBlb3BsZSB3aGV0aGVyIHRoZXkg
a25vdyBvZiBJbnRlbGxlY3R1YWwgUHJvcGVydHkgUmlnaHRzIChJUFIpIHJlbGF0aW5nIHRvIHNw
ZWNpZmljIGRvY3VtZW50cy4gIEluIG9yZGVyIHRvIGNvbXBseSB3aXRoIElFVEYgcHJvY2Vzc2Vz
IGFuZCBhdm9pZCB1bm5lY2Vzc2FyeSBkZWxheXMsIGRvY3VtZW50IGF1dGhvcnMgYW5kIGNvbnRy
aWJ1dG9ycyB0byBvdXIgZGlzY3Vzc2lvbnMgaW4gdGhlIERIQyBXRyBhcmUgYXNrZWQgdG8gcGF5
IGNhcmVmdWwgYXR0ZW50aW9uIHRvIHRoZXNlIG1lc3NhZ2VzIGFuZCB0byByZXBseSBpbiBhIHRp
bWVseSBmYXNoaW9uLg0KDQpQbGVhc2Ugbm90ZSB0aGF0IHRoZXNlIG1lc3NhZ2VzIGFyZSBvbmx5
IHJlbWluZGVycyBvZiBleGlzdGluZyBJRVRGIHBvbGljeSwgYW5kIHdlIGFyZSBhbGwgYm91bmQg
YnkgdGhhdCBwb2xpY3kgZXZlbiBpbiB0aGUgYWJzZW5jZSBvZiBzdWNoIHJlbWluZGVyIG1lc3Nh
Z2VzLiAgRXZlcnlvbmUgd2hvIHBhcnRpY2lwYXRlcyBpbiB0aGUgSW50ZXJuZXQgU3RhbmRhcmRz
IFByb2Nlc3MgKHdoZXRoZXIgYnkgcG9zdGluZyB0byBJRVRGIG1haWxpbmcgbGlzdHMsIGF1dGhv
cmluZyBkb2N1bWVudHMsIGF0dGVuZGluZyBJRVRGIG1lZXRpbmdzLCBvciBpbiBvdGhlciB3YXlz
KSBuZWVkcyB0byBiZSBhd2FyZSBvZiB0aGUgSUVURiBydWxlcyB3aXRoIHJlZ2FyZCB0byBJUFIu
ICBUaGVzZSBydWxlcyBhcmUgZGVzY3JpYmVkIGluIEJDUDc5IGFuZCBjYW4gYmUgcmVmZXJlbmNl
ZCB0aHJvdWdoIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaXByL3BvbGljeS5odG1sLiAgSW4gYWRkaXRp
b24sIG9ubGluZSB0b29scyBmb3IgZmlsaW5nIElQUiBkaXNjbG9zdXJlcyBjYW4gYmUgZm91bmQg
YXQgaHR0cDovL3d3dy5pZXRmLm9yZy9pcHIvZmlsZS1kaXNjbG9zdXJlLiAgRmluYWxseSwgZXhp
c3RpbmcgZGlzY2xvc3VyZXMgY2FuIGJlIHNlYXJjaGVkIG9ubGluZSBhdCBodHRwczovL2RhdGF0
cmFja2VyLmlldGYub3JnL2lwci9zZWFyY2gvLg0KDQpBbHNvIG5vdGUgdGhhdCB0aGVzZSBhcmUg
cGVyc29uYWwgcmVxdWlyZW1lbnRzIGFwcGx5aW5nIHRvIGFsbCBJRVRGIHBhcnRpY2lwYW50cyBh
cyBpbmRpdmlkdWFscywgYW5kIHRoYXQgdGhlc2UgcmVxdWlyZW1lbnRzIGFsc28gYXBwbHkgdG8g
YWxsIHBhcnRpY2lwYW50cyBpbiB0aGUgREhDIFdHLg0KDQpUaGFua3MsDQoNCkJlcm5pZSAmIFRv
bWVrDQooREhDIFdHIENvLWNoYWlycykNCg0K

--_000_33789EF92EBA42E4990298D320ED4846ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <906A10EF42C79E4C90480DC5920CA732@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IGRpcj0iYXV0byI+DQo8
Zm9udD4NCjxkaXYgc3R5bGU9Ii13ZWJraXQtdGV4dC1zaXplLWFkanVzdDogYXV0bzsgYmFja2dy
b3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj4NClRoZSBmb2xsb3dpbmcgaXMg
YSBnb29kIHJlbWluZGVyIGFib3V0IHRoZSBJRVRGIElQUiBwb2xpY3kgdGhlIEthdGxlZW4gTW9y
aWFydHkgc2VudCB0byB0aGUgTUlMRSBXRyBpbiBBdWd1c3QgMjAxMi4gSSByZXBsYWNlZCBNSUxF
IHdpdGggREhDOjwvZGl2Pg0KPGRpdiBzdHlsZT0iLXdlYmtpdC10ZXh0LXNpemUtYWRqdXN0OiBh
dXRvOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyAiPg0KPGJyPg0K
PC9kaXY+DQo8ZGl2IHN0eWxlPSItd2Via2l0LXRleHQtc2l6ZS1hZGp1c3Q6IGF1dG87IGJhY2tn
cm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7ICI+DQpEZWFyIERIQyBXRzo8L2Rp
dj4NCjxkaXYgc3R5bGU9Ii13ZWJraXQtdGV4dC1zaXplLWFkanVzdDogYXV0bzsgYmFja2dyb3Vu
ZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj4NCiZuYnNwOzwvZGl2Pg0KPGRpdiBz
dHlsZT0iLXdlYmtpdC10ZXh0LXNpemUtYWRqdXN0OiBhdXRvOyBiYWNrZ3JvdW5kLWNvbG9yOiBy
Z2JhKDI1NSwgMjU1LCAyNTUsIDApOyAiPg0KQXMmbmJzcDs8c3BhbiBzdHlsZT0iLXdlYmtpdC10
YXAtaGlnaGxpZ2h0LWNvbG9yOiByZ2JhKDI2LCAyNiwgMjYsIDAuMjk2ODc1KTsgLXdlYmtpdC1j
b21wb3NpdGlvbi1maWxsLWNvbG9yOiByZ2JhKDE3NSwgMTkyLCAyMjcsIDAuMjMwNDY5KTsgLXdl
YmtpdC1jb21wb3NpdGlvbi1mcmFtZS1jb2xvcjogcmdiYSg3NywgMTI4LCAxODAsIDAuMjMwNDY5
KTsgIj5ESEM8L3NwYW4+Jm5ic3A7V0cgY2hhaXJzLCB3ZSB3b3VsZCBsaWtlIHRvIG1pbmltaXpl
IG9yIGhvcGVmdWxseQ0KIGV2ZW4mbmJzcDs8c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjog
cmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj5lbGltaW5hdGUgbGF0ZSBkaXNjbG9zdXJlcyByZWxh
dGluZyB0byBkb2N1bWVudHMgdW5kZXIgY29uc2lkZXJhdGlvbjwvc3Bhbj48c3BhbiBzdHlsZT0i
YmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj4mbmJzcDt3aXRoaW4g
dGhlJm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSItd2Via2l0LXRhcC1oaWdobGlnaHQtY29sb3I6
IHJnYmEoMjYsIDI2LCAyNiwgMC4yOTI5NjkpOyAtd2Via2l0LWNvbXBvc2l0aW9uLWZpbGwtY29s
b3I6IHJnYmEoMTc1LCAxOTIsIDIyNywgMC4yMzA0NjkpOyAtd2Via2l0LWNvbXBvc2l0aW9uLWZy
YW1lLWNvbG9yOiByZ2JhKDc3LCAxMjgsIDE4MCwgMC4yMzA0NjkpOyAiPkRIQzwvc3Bhbj48c3Bh
biBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj4mbmJz
cDtXRy4mbmJzcDsNCiBUaGVyZWZvcmUgeW91IG1pZ2h0IHNlZSB1cyBzZW5kICZxdW90O3JlbWlu
ZGVyJnF1b3Q7PC9zcGFuPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwg
MjU1LCAyNTUsIDApOyAiPiZuYnNwO21lc3NhZ2VzIGluIHRoZSBmdXR1cmUgdG8gYXV0aG9ycyBv
ciB0byB0aGUmbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9Ii13ZWJraXQtdGFwLWhpZ2hsaWdodC1j
b2xvcjogcmdiYSgyNiwgMjYsIDI2LCAwLjI5Mjk2OSk7IC13ZWJraXQtY29tcG9zaXRpb24tZmls
bC1jb2xvcjogcmdiYSgxNzUsIDE5MiwgMjI3LCAwLjIzMDQ2OSk7IC13ZWJraXQtY29tcG9zaXRp
b24tZnJhbWUtY29sb3I6IHJnYmEoNzcsIDEyOCwgMTgwLCAwLjIzMDQ2OSk7ICI+REhDPC9zcGFu
PjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyAi
PiZuYnNwO1dHDQogZW1haWwgbGlzdCBhcyBhJm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJiYWNr
Z3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyAiPndob2xlLCBhc2tpbmcgcGVv
cGxlIHdoZXRoZXIgdGhleSBrbm93IG9mIEludGVsbGVjdHVhbCBQcm9wZXJ0eSZuYnNwOzwvc3Bh
bj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsg
Ij5SaWdodHMgKElQUikgcmVsYXRpbmcgdG8gc3BlY2lmaWMgZG9jdW1lbnRzLiZuYnNwOyBJbg0K
IG9yZGVyIHRvIGNvbXBseSB3aXRoJm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5k
LWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyAiPklFVEYgcHJvY2Vzc2VzIGFuZCBhdm9p
ZCB1bm5lY2Vzc2FyeSBkZWxheXMsIGRvY3VtZW50IGF1dGhvcnMgYW5kJm5ic3A7PC9zcGFuPjxz
cGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyAiPmNv
bnRyaWJ1dG9ycyB0byBvdXIgZGlzY3Vzc2lvbnMgaW4gdGhlJm5ic3A7PC9zcGFuPjxzcGFuIHN0
eWxlPSItd2Via2l0LXRhcC1oaWdobGlnaHQtY29sb3I6IHJnYmEoMjYsIDI2LCAyNiwgMC4yOTI5
NjkpOyAtd2Via2l0LWNvbXBvc2l0aW9uLWZpbGwtY29sb3I6IHJnYmEoMTc1LCAxOTIsIDIyNywg
MC4yMzA0NjkpOyAtd2Via2l0LWNvbXBvc2l0aW9uLWZyYW1lLWNvbG9yOiByZ2JhKDc3LCAxMjgs
IDE4MCwgMC4yMzA0NjkpOyAiPkRIQzwvc3Bhbj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xv
cjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj4mbmJzcDtXRw0KIGFyZSBhc2tlZCB0byBwYXkm
bmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9ImJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUs
IDI1NSwgMCk7ICI+Y2FyZWZ1bCBhdHRlbnRpb24gdG8gdGhlc2UgbWVzc2FnZXMgYW5kIHRvIHJl
cGx5IGluIGEgdGltZWx5IGZhc2hpb24uPC9zcGFuPjwvZGl2Pg0KPGRpdiBzdHlsZT0iLXdlYmtp
dC10ZXh0LXNpemUtYWRqdXN0OiBhdXRvOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1
LCAyNTUsIDApOyAiPg0KJm5ic3A7PC9kaXY+DQo8ZGl2IHN0eWxlPSItd2Via2l0LXRleHQtc2l6
ZS1hZGp1c3Q6IGF1dG87IGJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7
ICI+DQo8c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAw
KTsgIj5QbGVhc2Ugbm90ZSB0aGF0IHRoZXNlIG1lc3NhZ2VzIGFyZSBvbmx5IHJlbWluZGVycyBv
ZiBleGlzdGluZyBJRVRGJm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9y
OiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyAiPnBvbGljeSwgYW5kIHdlIGFyZSBhbGwgYm91bmQg
YnkgdGhhdCBwb2xpY3kgZXZlbiBpbiB0aGUgYWJzZW5jZSBvZjwvc3Bhbj48c3BhbiBzdHlsZT0i
YmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj4mbmJzcDtzdWNoDQog
cmVtaW5kZXIgbWVzc2FnZXMuJm5ic3A7IEV2ZXJ5b25lIHdobyBwYXJ0aWNpcGF0ZXMgaW4gdGhl
IEludGVybmV0Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiByZ2Jh
KDI1NSwgMjU1LCAyNTUsIDApOyAiPlN0YW5kYXJkcyBQcm9jZXNzICh3aGV0aGVyIGJ5IHBvc3Rp
bmcgdG8gSUVURiBtYWlsaW5nIGxpc3RzLCZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iYmFja2dy
b3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj5hdXRob3JpbmcNCiBkb2N1bWVu
dHMsIGF0dGVuZGluZyBJRVRGIG1lZXRpbmdzLCBvciBpbiBvdGhlciB3YXlzKSBuZWVkcyZuYnNw
Ozwvc3Bhbj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1
LCAwKTsgIj50byBiZSBhd2FyZSBvZiB0aGUgSUVURiBydWxlcyB3aXRoIHJlZ2FyZCB0byBJUFIu
Jm5ic3A7IFRoZXNlIHJ1bGVzIGFyZSZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iYmFja2dyb3Vu
ZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj5kZXNjcmliZWQNCiBpbiBCQ1A3OSBh
bmQgY2FuIGJlIHJlZmVyZW5jZWQgdGhyb3VnaCZuYnNwOzwvc3Bhbj48YSByZWw9Im5vZm9sbG93
IiBocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL2lwci9wb2xpY3kuaHRtbCI+aHR0cDovL3d3dy5p
ZXRmLm9yZy9pcHIvcG9saWN5Lmh0bWw8L2E+PHNwYW4gc3R5bGU9ImJhY2tncm91bmQtY29sb3I6
IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7ICI+LiZuYnNwOyBJbiBhZGRpdGlvbiwgb25saW5lIHRv
b2xzIGZvcjwvc3Bhbj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1
NSwgMjU1LCAwKTsgIj4mbmJzcDtmaWxpbmcNCiBJUFIgZGlzY2xvc3VyZXMgY2FuIGJlIGZvdW5k
IGF0Jm5ic3A7PC9zcGFuPjxhIHJlbD0ibm9mb2xsb3ciIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5v
cmcvaXByL2ZpbGUtZGlzY2xvc3VyZSI+aHR0cDovL3d3dy5pZXRmLm9yZy9pcHIvZmlsZS1kaXNj
bG9zdXJlPC9hPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAy
NTUsIDApOyAiPi4mbmJzcDsgRmluYWxseSwgZXhpc3RpbmcmbmJzcDs8L3NwYW4+PHNwYW4gc3R5
bGU9ImJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7ICI+ZGlzY2xvc3Vy
ZXMNCiBjYW4gYmUgc2VhcmNoZWQgb25saW5lIGF0Jm5ic3A7PC9zcGFuPjxhIHJlbD0ibm9mb2xs
b3ciIGhyZWY9Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvaXByL3NlYXJjaC8iPmh0dHBz
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvaXByL3NlYXJjaC88L2E+PHNwYW4gc3R5bGU9ImJhY2tn
cm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7ICI+Ljwvc3Bhbj48L2Rpdj4NCjxk
aXYgc3R5bGU9Ii13ZWJraXQtdGV4dC1zaXplLWFkanVzdDogYXV0bzsgYmFja2dyb3VuZC1jb2xv
cjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj4NCiZuYnNwOzwvZGl2Pg0KPGRpdiBzdHlsZT0i
LXdlYmtpdC10ZXh0LXNpemUtYWRqdXN0OiBhdXRvOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1
NSwgMjU1LCAyNTUsIDApOyAiPg0KQWxzbyBub3RlIHRoYXQgdGhlc2UgYXJlIHBlcnNvbmFsIHJl
cXVpcmVtZW50cyBhcHBseWluZyB0byBhbGwgSUVURiZuYnNwOzxzcGFuIHN0eWxlPSJiYWNrZ3Jv
dW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyAiPnBhcnRpY2lwYW50cyBhcyBpbmRp
dmlkdWFscywgYW5kIHRoYXQgdGhlc2UgcmVxdWlyZW1lbnRzIGFsc28gYXBwbHkmbmJzcDs8L3Nw
YW4+PHNwYW4gc3R5bGU9ImJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7
ICI+dG8NCiBhbGwgcGFydGljaXBhbnRzIGluIHRoZSZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0i
LXdlYmtpdC10YXAtaGlnaGxpZ2h0LWNvbG9yOiByZ2JhKDI2LCAyNiwgMjYsIDAuMjkyOTY5KTsg
LXdlYmtpdC1jb21wb3NpdGlvbi1maWxsLWNvbG9yOiByZ2JhKDE3NSwgMTkyLCAyMjcsIDAuMjMw
NDY5KTsgLXdlYmtpdC1jb21wb3NpdGlvbi1mcmFtZS1jb2xvcjogcmdiYSg3NywgMTI4LCAxODAs
IDAuMjMwNDY5KTsgIj5ESEM8L3NwYW4+PHNwYW4gc3R5bGU9ImJhY2tncm91bmQtY29sb3I6IHJn
YmEoMjU1LCAyNTUsIDI1NSwgMCk7ICI+Jm5ic3A7V0cuPC9zcGFuPjwvZGl2Pg0KPGRpdiBzdHls
ZT0iLXdlYmtpdC10ZXh0LXNpemUtYWRqdXN0OiBhdXRvOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2Jh
KDI1NSwgMjU1LCAyNTUsIDApOyAiPg0KJm5ic3A7PC9kaXY+DQo8ZGl2IHN0eWxlPSItd2Via2l0
LXRleHQtc2l6ZS1hZGp1c3Q6IGF1dG87IGJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUs
IDI1NSwgMCk7ICI+DQpUaGFua3MsPC9kaXY+DQo8ZGl2IHN0eWxlPSItd2Via2l0LXRleHQtc2l6
ZS1hZGp1c3Q6IGF1dG87IGJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7
ICI+DQombmJzcDs8L2Rpdj4NCjxkaXYgc3R5bGU9Ii13ZWJraXQtdGV4dC1zaXplLWFkanVzdDog
YXV0bzsgYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj4NCkJlcm5p
ZSAmYW1wOyBUb21lazwvZGl2Pg0KPGRpdiBzdHlsZT0iLXdlYmtpdC10ZXh0LXNpemUtYWRqdXN0
OiBhdXRvOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyAiPg0KKDxz
cGFuIHN0eWxlPSItd2Via2l0LXRhcC1oaWdobGlnaHQtY29sb3I6IHJnYmEoMjYsIDI2LCAyNiwg
MC4yOTI5NjkpOyAtd2Via2l0LWNvbXBvc2l0aW9uLWZpbGwtY29sb3I6IHJnYmEoMTc1LCAxOTIs
IDIyNywgMC4yMzA0NjkpOyAtd2Via2l0LWNvbXBvc2l0aW9uLWZyYW1lLWNvbG9yOiByZ2JhKDc3
LCAxMjgsIDE4MCwgMC4yMzA0NjkpOyAiPkRIQzwvc3Bhbj48c3BhbiBzdHlsZT0iYmFja2dyb3Vu
ZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsgIj4mbmJzcDtXRw0KIENvLWNoYWlycyk8
L3NwYW4+PC9kaXY+DQo8ZGl2IHN0eWxlPSItd2Via2l0LXRleHQtc2l6ZS1hZGp1c3Q6IGF1dG87
IGJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7ICI+DQombmJzcDs8L2Rp
dj4NCjwvZm9udD4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_33789EF92EBA42E4990298D320ED4846ciscocom_--

From mohta@necom830.hpcl.titech.ac.jp  Mon Mar 18 20:34:57 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A453721F85D6 for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 20:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vH42gOwEiClI for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 20:34:57 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id C335A21F88DB for <dhcwg@ietf.org>; Mon, 18 Mar 2013 20:34:50 -0700 (PDT)
Received: (qmail 69629 invoked from network); 19 Mar 2013 03:32:52 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 19 Mar 2013 03:32:52 -0000
Message-ID: <5147DCC3.8010002@necom830.hpcl.titech.ac.jp>
Date: Tue, 19 Mar 2013 12:34:27 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com>	<51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com> <489D13FBFA9B3E41812EA89F188F018E184B6468@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E184B6468@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 03:34:57 -0000

Bernie Volz (volz) wrote:

> It also doesn't look like there is any way to communicate the
> domain name search list (clients could do DHCPINFORMs /
> INFORMATION-REQUEST later to get at least these other
> configuration items).

FYI, domain name search list is considered evil in IETF DNS
related WGs.

Even ignoring an obvious security problem, the list should
be configured statically by users, who know frequently used
domain names by them, which has nothing to do with the current
locations of the users.

						Masataka Ohta

From alexandru.petrescu@gmail.com  Mon Mar 18 20:55:32 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED9AA21F8AA6 for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 20:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.158
X-Spam-Level: 
X-Spam-Status: No, score=-10.158 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVWldWnsC+hE for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 20:55:32 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 4E72421F8A93 for <dhcwg@ietf.org>; Mon, 18 Mar 2013 20:55:31 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2J3tUE1006456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Tue, 19 Mar 2013 04:55:30 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2J3tTNf017236 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 04:55:30 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.86.2]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2J3tPvj027579 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 04:55:29 +0100
Message-ID: <5147E187.6040407@gmail.com>
Date: Tue, 19 Mar 2013 04:54:47 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com>	<51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com> <489D13FBFA9B3E41812EA89F188F018E184B6468@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E184B6468@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 03:55:33 -0000

Le 19/03/2013 03:08, Bernie Volz (volz) a écrit :
[...]
> Also, there is no way to move between APs (even 802.11ai) since
> there are different address allocation techniques (in your approach
> as the DHCP server is used, it could give out the same address if
> the network supports a flat address space). In the other technique
> the AP might communicate to some central controller, but now you'd
> need a protocol for conveying the address information between the AP
> and central controller?

This reads as a technique similar to what RFC5213 "Proxy Mobile IPv6" does.

Remark this topology described in the document referred at IEEE 802.11ai:

                STA ---- AP ---- Router

is also considered by both DHCPv6 (Client---Relay---Server) and by Proxy
Mobile IPv6 (MobileNode---MAG---LMA).  These multihop networks are less
pertinent to Neighbor Discovery.

Alex

>
> - Bernie
>
> -----Original Message----- From: dhcwg-bounces@ietf.org
> [mailto:dhcwg-bounces@ietf.org] On Behalf Of Hiroki Nakano Sent:
> Monday, March 18, 2013 3:55 PM To: dhcwg@ietf.org Subject: Re:
> [dhcwg] IEEE 802.11ai and DHCP
>
> (13/03/18 2:29), Erik Kline wrote:
>> I'm not sure I've got the right doc, but anyway, I'll see about how
>> possible participation in the IEEE process, I guess.
>
> The bimonthly week of TGai has been started today in the same place
> as IETF86 of the last week. The battle is a draw for now.
>
> https://mentor.ieee.org/802.11/dcn/13/11-13-0040-04-00ai-higher-layer-packet-container-proposal-text.doc
>
>
>
https://mentor.ieee.org/802.11/dcn/13/11-13-0267-00-00ai-fils-ip-address-setup.doc
>
> Come and join us, please.
>
> Regards,
>
> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
> _______________________________________________ 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 alexandru.petrescu@gmail.com  Mon Mar 18 21:03:38 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7917321F8B74 for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 21:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.16
X-Spam-Level: 
X-Spam-Status: No, score=-10.16 tagged_above=-999 required=5 tests=[AWL=0.089,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0S6CbyXpzh9s for <dhcwg@ietfa.amsl.com>; Mon, 18 Mar 2013 21:03:37 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF5421F8B64 for <dhcwg@ietf.org>; Mon, 18 Mar 2013 21:03:37 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2J43aHI010310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Tue, 19 Mar 2013 05:03:36 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2J43ZoL018078 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 05:03:36 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.86.2]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2J43VqK021392 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 05:03:35 +0100
Message-ID: <5147E36D.1060003@gmail.com>
Date: Tue, 19 Mar 2013 05:02:53 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com>	<51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com> <489D13FBFA9B3E41812EA89F188F018E184B6468@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E184B6468@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 04:03:38 -0000

Le 19/03/2013 03:08, Bernie Volz (volz) a écrit :
[...]
> Also, how will the other technique work when the client attempts to
> do DHCP? Seems like a lot of change to the client stack,

I agree with the question and it seems to me as well that a lof of
change in the client IP stack may be needed.

In addition to DHCPv6, the basic IPv6-over-Ethernet RFCs may need to get
updated to make sure they dont auto-configure addresses, nor defroutes,
when running over 802.11ai.

It would be strange to see an IPv6-over-802.11ai IETF document, because
one would expect IPv6 over 'ai' to work just like IPv6 over 802.11b
which is same as IPv6-over-Ethernet.

(which reminds of IPv6-over-802.16... 16ng IETF Working Group).

Alex

> especially as hopefully this switch between 802.11ai and non-802.11ai
> interfaces should be smooth and transparent? I don't believe these
> would usually look like different interfaces to the client? But we
> don't know what the full standard says. So how will this other
> technique co-exist with non-802.11ai interfaces in a providers
> network (i.e., they have been using DHCP to configure their clients
> and now when they switch to 802.11ai they need to do something new or
> different).
>
> Also, there is no way to move between APs (even 802.11ai) since
> there are different address allocation techniques (in your approach
> as the DHCP server is used, it could give out the same address if
> the network supports a flat address space). In the other technique
> the AP might communicate to some central controller, but now you'd
> need a protocol for conveying the address information between the AP
> and central controller?
>
> - Bernie
>
> -----Original Message----- From: dhcwg-bounces@ietf.org
> [mailto:dhcwg-bounces@ietf.org] On Behalf Of Hiroki Nakano Sent:
> Monday, March 18, 2013 3:55 PM To: dhcwg@ietf.org Subject: Re:
> [dhcwg] IEEE 802.11ai and DHCP
>
> (13/03/18 2:29), Erik Kline wrote:
>> I'm not sure I've got the right doc, but anyway, I'll see about how
>> possible participation in the IEEE process, I guess.
>
> The bimonthly week of TGai has been started today in the same place
> as IETF86 of the last week. The battle is a draw for now.
>
> https://mentor.ieee.org/802.11/dcn/13/11-13-0040-04-00ai-higher-layer-packet-container-proposal-text.doc
>
>
>
>
>
https://mentor.ieee.org/802.11/dcn/13/11-13-0267-00-00ai-fils-ip-address-setup.doc
>
> Come and join us, please.
>
> Regards,
>
> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
> _______________________________________________ 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 Ted.Lemon@nominum.com  Tue Mar 19 04:53:59 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A33E921F842A for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 04:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.585
X-Spam-Level: 
X-Spam-Status: No, score=-106.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sWDF3ZwhnaZl for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 04:53:59 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 1F13E21F8417 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 04:53:58 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUUhR04ePzkUnuE2XdI06vVx/CurT1RL8@postini.com; Tue, 19 Mar 2013 04:53:59 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 0ED3A1B85FE for <dhcwg@ietf.org>; Tue, 19 Mar 2013 04:53:55 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 05264190043; Tue, 19 Mar 2013 04:53:55 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 04:53:55 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] Reminder about IETF IPR Policy
Thread-Index: Ac4kUV4d5RWdm6zMQTKymlHt0wp7PgAgbuyA
Date: Tue, 19 Mar 2013 11:53:54 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775114825@mbx-01.win.nominum.com>
References: <33789EF9-2EBA-42E4-9902-98D320ED4846@cisco.com>
In-Reply-To: <33789EF9-2EBA-42E4-9902-98D320ED4846@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <92C471BE028DFD498B878CBA7E0C1D6E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder about IETF IPR Policy
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 11:53:59 -0000

Some additional advice I got from Barry Leiba (one of the Apps area directo=
rs):

Disclosures are required on individual submissions, as soon as practical af=
ter the -00 version... not just on
working group documents.   There are many people who think it's okay to dis=
close only after adoption, and everyone needs to be reminded that it's not.

Also, do not be concerned that the working group might not accept your idea=
 if you disclose IPR on it.  You must disclose.    Working groups will usua=
lly accept the terms we provide (he works for Huawei, and they tend to say =
"we won't sue you if you don't sue us."    Even if the working group wouldn=
't accept the work with the IPR, the consequences of not disclosing it are =
worse.


From Ted.Lemon@nominum.com  Tue Mar 19 12:32:52 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6E1621F8801 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 12:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.586
X-Spam-Level: 
X-Spam-Status: No, score=-106.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wkKb9JIv2BuS for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 12:32:51 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 38CCC21F87AB for <dhcwg@ietf.org>; Tue, 19 Mar 2013 12:32:51 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUUi9Y926H2/ieIOXuV55nVC0Ca6pHEYp@postini.com; Tue, 19 Mar 2013 12:32:51 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 ACC5D1B8885 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 12:32:50 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A3D36190043; Tue, 19 Mar 2013 12:32:50 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 12:32:50 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: Volunteer to work on configuring IPv4 over IPv6 network
Thread-Index: AQHOITYqlpwdJNkYY0+mtV8vRI/hsJinH9aAgAAJBwCAAARngIAAAcyAgASvVoCAAAIYAIAAFO0AgAAWWgCAAAPpAIAABReAgAADLgCAABU+gIAAA0gAgACWUwCAAJrggIAADRaAgAAGxYCAAAKBgIAAEgiAgAAXUwCAAAt4gIAAAxOAgAAOZICAACWugA==
Date: Tue, 19 Mar 2013 19:32:49 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775115A0C@mbx-01.win.nominum.com>
References: <CD6CC9A8.5BCCE%ian.farrer@telekom.de> <8D23D4052ABE7A4490E77B1A012B63077511205D@mbx-01.win.nominum.com> <51471E7E.1000103@gmail.com> <8D23D4052ABE7A4490E77B1A012B63077511247C@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184B5058@xmb-rcd-x04.cisco.com> <514738CB.7070807@ericsson.com> <8D23D4052ABE7A4490E77B1A012B630775112704@mbx-01.win.nominum.com> <1363627335.5820.19.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775112B10@mbx-01.win.nominum.com> <8A60B830-C601-42B3-8AD1-5FA71A253435@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751147B1@mbx-01.win.nominum.com> <1219647D-8408-41E7-BEA7-28E28E8E7B8B@gmail.com> <1363697845.2579.3.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775114AF8@mbx-01.win.nominum.com> <3901ACCE-E7A1-4F93-80EE-0BE961E7A6C2@gmail.com> <1363707264.2579.10.camel@marcin-lenovo> <CABsovMkSmnqcE6=xNq3AKatrHXM3bfRkh-iEFmOFqNQTbq3_yA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751153BB@mbx-01.win.nominum.com> <51489DC5.3090208@gmail.com>
In-Reply-To: <51489DC5.3090208@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <857E3ECA9A4D35438B1B4EC6B8ABB974@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 19 Mar 2013 12:54:39 -0700
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>, Yuchi Chen <chenycmx@gmail.com>, "weapon9@gmail.com" <weapon9@gmail.com>, "cuiyong@tsinghua.edu.cn" <cuiyong@tsinghua.edu.cn>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Cong Liu <gnocuil@gmail.com>, Qi Sun <sunqibupt@gmail.com>
Subject: Re: [dhcwg] Volunteer to work on configuring IPv4 over IPv6 network
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 19:32:52 -0000

On Mar 19, 2013, at 1:17 PM, Tomek Mrugalski <tomasz.mrugalski@gmail.com> w=
rote:
> But still method 2 requires client update, which is a major pain. It is
> easier to update relays and server. Operators control their server and
> their relays, but they typically do not control the hosts. Operators
> can't force their customers to upgrade their software or hardware.

I think client update is a non-issue here, and in fact both options should =
require that the client be updated.   The reason is that an unmodified clie=
nt isn't going to do the right thing with the answer anyway.   So although =
in principle you are right that the client is the hardest thing to modify, =
in this case we _have_ to modify it, so we might as well modify it complete=
ly, and not only halfway.

The only solution that makes sense to me is the one where the client sends =
a DHCPv4 packet wrapped in a special client header to the All_Relays_And_Se=
rvers multicast address on the DHCPv6 server port.   This uses the exact sa=
me infrastructure as DHCPv6, and requires no special DHCPv4-specific modifi=
cations other than on the server.

We have also talked about two other variations.   The first is the variatio=
n where the first relay agent knows the difference between a DHCPv6 message=
 and a DHCPv4 message, and can send DHCPv6 messages to a different IPv6 add=
ress than DHCPv4 messages.

The other variation we talked about is the one where at the end of the rela=
y chain, either the DHCP server or a DHCP relay agent that is connected to =
both the IPv6 network and an IPv4 network recognizes DHCPv4 packets being r=
elayed to it and relays them over IPv4 to a DHCPv4 server.

These variations are just optional enhancements.   We don't need them, but =
someone might like them.   So they are probably worth clearly documenting, =
but the main thing that needs to be documented is how the client works, and=
 this should be the same in all three cases: the main case and the two vari=
ations.


From msiodelski@gmail.com  Tue Mar 19 13:03:22 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 148CF21F8D90 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.936
X-Spam-Level: 
X-Spam-Status: No, score=0.936 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877,  RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ep9J5ww9DoO1 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:03:21 -0700 (PDT)
Received: from mail-ea0-x22c.google.com (mail-ea0-x22c.google.com [IPv6:2a00:1450:4013:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 5467221F8D45 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 13:03:21 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id d10so427467eaj.17 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 13:03:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:x-mailer:mime-version :content-transfer-encoding; bh=lxCLuvFRy0YuYuQE/7RZGj4DvyikqGz0PoU3MQ00ENA=; b=PGwqvMQmLr21XQfD5kuSKrR5Z881bBh0O2z/M0YtE184sSEeGYtbhoxb2mqnUO+thp rEZQLzjsZh2r2DxpZSlogD24lMm6mEfBIZ5cI9kmqy8ZX+Czkkp/jqinwr14dH+1LOh5 j5AW3yfe3qbfqWa81Aao/CcU/CUQCHj6gvAyjNj7dHmKHHsLN9mfxAdzHkGcZcsff8nu ZZA6ieyltdsHGTNPKwlX1rOsTtuAi57uoAw75ItCfpnEcMrk2BXjJcD5snakONbEp6Lx 0p0QPA3yZgbjQ2diDSP5t0QVYeedXFZG8UtcKAt6hZmP7dRP26wv62z4RxQQ94ZMHdCb od1A==
X-Received: by 10.14.204.195 with SMTP id h43mr35760966eeo.14.1363723400363; Tue, 19 Mar 2013 13:03:20 -0700 (PDT)
Received: from [192.168.0.193] (89-75-115-194.dynamic.chello.pl. [89.75.115.194]) by mx.google.com with ESMTPS id t4sm35176055eel.0.2013.03.19.13.03.17 (version=SSLv3 cipher=RC4-SHA bits=128/128); Tue, 19 Mar 2013 13:03:19 -0700 (PDT)
Message-ID: <1363723396.2579.42.camel@marcin-lenovo>
From: Marcin Siodelski <msiodelski@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Date: Tue, 19 Mar 2013 21:03:16 +0100
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775115A0C@mbx-01.win.nominum.com>
References: <CD6CC9A8.5BCCE%ian.farrer@telekom.de> <8D23D4052ABE7A4490E77B1A012B63077511205D@mbx-01.win.nominum.com> <51471E7E.1000103@gmail.com> <8D23D4052ABE7A4490E77B1A012B63077511247C@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184B5058@xmb-rcd-x04.cisco.com> <514738CB.7070807@ericsson.com> <8D23D4052ABE7A4490E77B1A012B630775112704@mbx-01.win.nominum.com> <1363627335.5820.19.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775112B10@mbx-01.win.nominum.com> <8A60B830-C601-42B3-8AD1-5FA71A253435@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751147B1@mbx-01.win.nominum.com> <1219647D-8408-41E7-BEA7-28E28E8E7B8B@gmail.com> <1363697845.2579.3.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775114AF8@mbx-01.win.nominum.com> <3901ACCE-E7A1-4F93-80EE-0BE961E7A6C2@gmail.com> <1363707264.2579.10.camel@marcin-lenovo> <CABsovMkSmnqcE6=xNq3AKatrHXM3bfRkh-iEFmOFqNQTbq3_yA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751153BB@mbx-01.win.nominum.com> <51489DC5.3090208@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775115A0C@mbx-01.win.nominum.com>
Content-Type: text/plain; charset="ISO-8859-15"
X-Mailer: Evolution 3.6.4 (3.6.4-2.fc18) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 19 Mar 2013 13:14:27 -0700
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>, Yuchi Chen <chenycmx@gmail.com>, "weapon9@gmail.com" <weapon9@gmail.com>, "cuiyong@tsinghua.edu.cn" <cuiyong@tsinghua.edu.cn>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Cong Liu <gnocuil@gmail.com>, Qi Sun <sunqibupt@gmail.com>
Subject: Re: [dhcwg] Volunteer to work on configuring IPv4 over IPv6 network
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 20:03:22 -0000

On Tue, 2013-03-19 at 19:32 +0000, Ted Lemon wrote:
> On Mar 19, 2013, at 1:17 PM, Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:
> > But still method 2 requires client update, which is a major pain. It is
> > easier to update relays and server. Operators control their server and
> > their relays, but they typically do not control the hosts. Operators
> > can't force their customers to upgrade their software or hardware.
> 
> I think client update is a non-issue here, and in fact both options should require that the client be updated.   The reason is that an unmodified client isn't going to do the right thing with the answer anyway.   So although in principle you are right that the client is the hardest thing to modify, in this case we _have_ to modify it, so we might as well modify it completely, and not only halfway.

Ted,

I am not questioning that you're right but I don't understand why
"client isn't going to do the right thing with the answer". Can you
please elaborate?

Marcin





From Ted.Lemon@nominum.com  Tue Mar 19 13:14:05 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD2821F84B0 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.587
X-Spam-Level: 
X-Spam-Status: No, score=-106.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vmYg5Hkos2J for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:14:04 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 4545921F84AF for <dhcwg@ietf.org>; Tue, 19 Mar 2013 13:14:04 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUUjHDO5Q2aPG+ZRiGde56A87X3vYSq1u@postini.com; Tue, 19 Mar 2013 13:14:04 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 E17BC1B882F for <dhcwg@ietf.org>; Tue, 19 Mar 2013 13:14:03 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id C80FB190043; Tue, 19 Mar 2013 13:14:03 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 13:14:03 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Marcin Siodelski <msiodelski@gmail.com>
Thread-Topic: Volunteer to work on configuring IPv4 over IPv6 network
Thread-Index: AQHOITYqlpwdJNkYY0+mtV8vRI/hsJinH9aAgAAJBwCAAARngIAAAcyAgASvVoCAAAIYAIAAFO0AgAAWWgCAAAPpAIAABReAgAADLgCAABU+gIAAA0gAgACWUwCAAJrggIAADRaAgAAGxYCAAAKBgIAAEgiAgAAXUwCAAAt4gIAAAxOAgAAOZICAACWugIAACIIAgAADAgA=
Date: Tue, 19 Mar 2013 20:14:03 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775115DFA@mbx-01.win.nominum.com>
References: <CD6CC9A8.5BCCE%ian.farrer@telekom.de> <8D23D4052ABE7A4490E77B1A012B63077511205D@mbx-01.win.nominum.com> <51471E7E.1000103@gmail.com> <8D23D4052ABE7A4490E77B1A012B63077511247C@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184B5058@xmb-rcd-x04.cisco.com> <514738CB.7070807@ericsson.com> <8D23D4052ABE7A4490E77B1A012B630775112704@mbx-01.win.nominum.com> <1363627335.5820.19.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775112B10@mbx-01.win.nominum.com> <8A60B830-C601-42B3-8AD1-5FA71A253435@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751147B1@mbx-01.win.nominum.com> <1219647D-8408-41E7-BEA7-28E28E8E7B8B@gmail.com> <1363697845.2579.3.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775114AF8@mbx-01.win.nominum.com> <3901ACCE-E7A1-4F93-80EE-0BE961E7A6C2@gmail.com> <1363707264.2579.10.camel@marcin-lenovo> <CABsovMkSmnqcE6=xNq3AKatrHXM3bfRkh-iEFmOFqNQTbq3_yA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751153BB@mbx-01.win.nominum.com> <51489DC5.3090208@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775115A0C@mbx-01.win.nominum.com> <1363723396.2579.42.camel@marcin-lenovo>
In-Reply-To: <1363723396.2579.42.camel@marcin-lenovo>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9F901D6D48C7724389B6EF2CD7792FD5@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 19 Mar 2013 13:14:32 -0700
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>, Yuchi Chen <chenycmx@gmail.com>, "weapon9@gmail.com" <weapon9@gmail.com>, "cuiyong@tsinghua.edu.cn" <cuiyong@tsinghua.edu.cn>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Cong Liu <gnocuil@gmail.com>, Qi Sun <sunqibupt@gmail.com>
Subject: Re: [dhcwg] Volunteer to work on configuring IPv4 over IPv6 network
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 20:14:05 -0000

On Mar 19, 2013, at 4:03 PM, Marcin Siodelski <msiodelski@gmail.com> wrote:
> I am not questioning that you're right but I don't understand why
> "client isn't going to do the right thing with the answer". Can you
> please elaborate?

A client sends a DHCPDISCOVER over IPv4 to configure the interface from whi=
ch it sends the DHCPDISCOVER.   Whatever response it gets, it will use to c=
onfigure that interface.

Here, we are using the DHCPDISCOVER to configure the tunnel endpoint, not t=
he broadcast interface.   So an unmodified client has no hope of doing the =
right thing with the configuration it gets from the server.   It will try t=
o use the response it gets on its broadcast interface, and every IPv4 packe=
t it sends will be dropped, because there's no router to carry it.

This brings up the point that the draft probably ought to give some guidanc=
e as to *which* broadcast interface to use to send the DHCPDISCOVER, since =
a typical HG has multiple interfaces, and at least the current use case tar=
gets HGs.


From volz@cisco.com  Tue Mar 19 13:54:17 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1963021F86C5 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIIPHDxA-Mm8 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 13:54:16 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 18E7221F86A6 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 13:54:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5243; q=dns/txt; s=iport; t=1363726456; x=1364936056; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=lZ29tomDPPLirkJ5I3fZf7cM5bQ++kLpRE66e0HxeFA=; b=Og08MOFEqQm9m8pL0FgNlC1WCxSqKzrfa2xZQQSOzL8/LgpQy7fYy3O1 5TR3NK0jehW1pzW3VkBVByc3B8hw+S0yffhvHSWEUxwfCd8Gdv5nVhrB7 8wUzyCenUzuwul/HJLhD701nEHKYr+Ie+zVdFzsJixzap+SNSBq8jSaM4 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAADQSFGtJV2b/2dsb2JhbABDxR2BXBZ0giQBAQEEJxM/DAQCAQgRBAEBAQoUCQchERQJCAIEAQ0FCBOHZwMPsgaGIw2JW4xFgROBBSYLBwaCWWEDlH+NSIUagwqBaj4
X-IronPort-AV: E=Sophos;i="4.84,873,1355097600"; d="scan'208";a="189246473"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-5.cisco.com with ESMTP; 19 Mar 2013 20:54:15 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2JKsFH1031875 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Mar 2013 20:54:15 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 15:54:15 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: Volunteer to work on configuring IPv4 over IPv6 network
Thread-Index: AQHOITYxNl6kawVQtkSiPIt1pltJd5im/kyAgAAJCgCAAARlAP//rf2kgAUDJ4CAAAIXAIAAFO4AgAAWWgD//61UYIAAW6yAgAADLgCAABU9gIAAA0sAgACWUQCAAJrggIAADRaAgAAGxYCAAAKBgIAAEgiAgAAXUwCAAAt4gIAAAxQAgAAOY4CAACWugP//ukWA
Date: Tue, 19 Mar 2013 20:54:14 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E184B7FF3@xmb-rcd-x04.cisco.com>
References: <CD6CC9A8.5BCCE%ian.farrer@telekom.de> <8D23D4052ABE7A4490E77B1A012B63077511205D@mbx-01.win.nominum.com> <51471E7E.1000103@gmail.com> <8D23D4052ABE7A4490E77B1A012B63077511247C@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184B5058@xmb-rcd-x04.cisco.com> <514738CB.7070807@ericsson.com> <8D23D4052ABE7A4490E77B1A012B630775112704@mbx-01.win.nominum.com> <1363627335.5820.19.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775112B10@mbx-01.win.nominum.com> <8A60B830-C601-42B3-8AD1-5FA71A253435@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751147B1@mbx-01.win.nominum.com> <1219647D-8408-41E7-BEA7-28E28E8E7B8B@gmail.com> <1363697845.2579.3.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775114AF8@mbx-01.win.nominum.com> <3901ACCE-E7A1-4F93-80EE-0BE961E7A6C2@gmail.com> <1363707264.2579.10.camel@marcin-lenovo> <CABsovMkSmnqcE6=xNq3AKatrHXM3bfRkh-iEFmOFqNQTbq3_yA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751153BB@mbx-01.win.nominum.com> <51489DC5.3090208@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775115A0C@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775115A0C@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 19 Mar 2013 14:05:56 -0700
Cc: Yuchi Chen <chenycmx@gmail.com>, "weapon9@gmail.com" <weapon9@gmail.com>, "cuiyong@tsinghua.edu.cn" <cuiyong@tsinghua.edu.cn>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Cong Liu <gnocuil@gmail.com>, Qi Sun <sunqibupt@gmail.com>
Subject: Re: [dhcwg] Volunteer to work on configuring IPv4 over IPv6 network
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 20:54:17 -0000

I believe ... One important thing to keep in mind is that the DHCP client h=
ere is on the CPE device (router) and not a Windows, iOS, Linux, Android, .=
.. device. So, changing the client isn't really that significant a concern.=
 (The CPE device will also have NAT and a DHCP server just as they do today=
 to use that one IPv4 address.) I think the diagram and document needs to b=
e clear on this as the term "client" is often confusing (at least to me). C=
PE, gateway, residential router, "the network box", ... are probably better=
 terms to use?

There were a few times where I had my model confused and was thinking host =
or 'end client' (Windows, IOS, Linux, ... device) instead of CPE. And, that=
 wrong model seems to be reflected in the artwork Marcin's draft currently =
has which shows V4/V6 going to the "Unified Relay". And while we could have=
 such a model, I don't think it is correct and realistic. The DHCPv4 Client=
 and DHCPv6 Client are in one box. The uplink side of that box communicatio=
ns IPv6 only to the SP. The v4/v6 side of the box communicates to "hosts" w=
hich are running standard operating systems. The "hosts" will do DHCPv4 and=
 DHCPv6/SLAC to get addresses from the "box". The "box" will do NAT for v4 =
and tunnel v4 over v6 to the some tunnel endpoint.

I do think we need to make sure we're all on the same page as to the model:

    Home Network with v4/v6 ----> CPE ----- v6-only link (DSL, Cable, ...) =
----> SP network [with relays] -----> DHCPv6/v4 server

The CPE has NAT for v4 and also supports tunneling v4 over v6. The CPE has =
v6 only uplink. SP network is mostly v6 (has limited v4 for tunnel endpoint=
s and perhaps some limited v4 services -- v4 is mostly for connectivity to =
Internet). The devices in the home use v4 pretty much as they would today b=
ehind a CPE that provides native v4 service (via NAT). They can use 'native=
' v6 (either via SLAC or DHCPv6).


Ted wrote:
"The only solution that makes sense to me is the one where the client sends=
 a DHCPv4 packet wrapped in a special client header to the All_Relays_And_S=
ervers multicast address on the DHCPv6 server port.   This uses the exact s=
ame infrastructure as DHCPv6, and requires no special DHCPv4-specific modif=
ications other than on the server."

I agree. The uplink is only capable of IPv6 and so this packet must go over=
 IPv6. And, as we assume that the CPE was given a PD (and perhaps v6 addres=
s) via DHCPv6, DHCPv6 support (relay or server) must be at the other end of=
 this link.


I think it best to focus on the "base" solution without the optional enhanc=
ements? Once we get the "base" solution worked out, we can add the optional=
 enhancements (either in the base document or as a separate one).

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Tuesday, March 19, 2013 3:33 PM
To: Tomek Mrugalski
Cc: Qi Sun; Marcin Siodelski; Suresh Krishnan; Bernie Volz (volz); ian.farr=
er@telekom.de; cuiyong@tsinghua.edu.cn; weapon9@gmail.com; Cong Liu; Yuchi =
Chen; dhcwg@ietf.org
Subject: Re: Volunteer to work on configuring IPv4 over IPv6 network

On Mar 19, 2013, at 1:17 PM, Tomek Mrugalski <tomasz.mrugalski@gmail.com> w=
rote:
> But still method 2 requires client update, which is a major pain. It=20
> is easier to update relays and server. Operators control their server=20
> and their relays, but they typically do not control the hosts.=20
> Operators can't force their customers to upgrade their software or hardwa=
re.

I think client update is a non-issue here, and in fact both options should =
require that the client be updated.   The reason is that an unmodified clie=
nt isn't going to do the right thing with the answer anyway.   So although =
in principle you are right that the client is the hardest thing to modify, =
in this case we _have_ to modify it, so we might as well modify it complete=
ly, and not only halfway.

The only solution that makes sense to me is the one where the client sends =
a DHCPv4 packet wrapped in a special client header to the All_Relays_And_Se=
rvers multicast address on the DHCPv6 server port.   This uses the exact sa=
me infrastructure as DHCPv6, and requires no special DHCPv4-specific modifi=
cations other than on the server.

We have also talked about two other variations.   The first is the variatio=
n where the first relay agent knows the difference between a DHCPv6 message=
 and a DHCPv4 message, and can send DHCPv6 messages to a different IPv6 add=
ress than DHCPv4 messages.

The other variation we talked about is the one where at the end of the rela=
y chain, either the DHCP server or a DHCP relay agent that is connected to =
both the IPv6 network and an IPv4 network recognizes DHCPv4 packets being r=
elayed to it and relays them over IPv4 to a DHCPv4 server.

These variations are just optional enhancements.   We don't need them, but =
someone might like them.   So they are probably worth clearly documenting, =
but the main thing that needs to be documented is how the client works, and=
 this should be the same in all three cases: the main case and the two vari=
ations.


From msiodelski@gmail.com  Tue Mar 19 14:16:36 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A10521F8F17 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 14:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.332
X-Spam-Level: 
X-Spam-Status: No, score=-1.332 tagged_above=-999 required=5 tests=[AWL=2.268,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CfZMP+CJR6Eu for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 14:16:35 -0700 (PDT)
Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) by ietfa.amsl.com (Postfix) with ESMTP id 2C09B21F8E1C for <dhcwg@ietf.org>; Tue, 19 Mar 2013 14:16:35 -0700 (PDT)
Received: by mail-ee0-f43.google.com with SMTP id c50so461962eek.30 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 14:16:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:subject:from:to:cc:date:in-reply-to :references:content-type:x-mailer:mime-version :content-transfer-encoding; bh=M1GnmuSr8MX03oNWOJRV9dbL3xdcSWAniSrj769g5qA=; b=rDfyEkqFRAtfxSpSiH96+YbCS3A4WeQDGnIXkQqM0Yl8tDc/0ApoQeUCY8O33KThn6 wr6Zhn02pHhWKcFbeIZyLSmrFJYE9/0k5+aEp2Ir7maLsxbT24vyR40izP9qxdY+zmre Lmjkwc2yVmKSYpGUwggfLkNUIfGH8I70Gd4JKj2NQRswHoE5CNKDLkS2c7ZW9z+8rtMx r0u+O5YU7fFinU1HWY4OqiHyxfbzhHggCfRETsOqF0mKzIV/OmWd7yZIlSaC5vGUgI/E ku5iuB8WNub/67JWoaJsUJbQEJcWakYm8WvuA9bOsR+8mnfr6C6JTseIy1/prO8AIF+I +xUg==
X-Received: by 10.14.207.73 with SMTP id m49mr64643770eeo.24.1363727794310; Tue, 19 Mar 2013 14:16:34 -0700 (PDT)
Received: from [192.168.0.193] (89-75-115-194.dynamic.chello.pl. [89.75.115.194]) by mx.google.com with ESMTPS id q42sm35483567eem.14.2013.03.19.14.16.31 (version=SSLv3 cipher=RC4-SHA bits=128/128); Tue, 19 Mar 2013 14:16:33 -0700 (PDT)
Message-ID: <1363727791.2579.54.camel@marcin-lenovo>
From: Marcin Siodelski <msiodelski@gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Date: Tue, 19 Mar 2013 22:16:31 +0100
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E184B7FF3@xmb-rcd-x04.cisco.com>
References: <CD6CC9A8.5BCCE%ian.farrer@telekom.de> <8D23D4052ABE7A4490E77B1A012B63077511205D@mbx-01.win.nominum.com> <51471E7E.1000103@gmail.com> <8D23D4052ABE7A4490E77B1A012B63077511247C@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184B5058@xmb-rcd-x04.cisco.com> <514738CB.7070807@ericsson.com> <8D23D4052ABE7A4490E77B1A012B630775112704@mbx-01.win.nominum.com> <1363627335.5820.19.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775112B10@mbx-01.win.nominum.com> <8A60B830-C601-42B3-8AD1-5FA71A253435@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751147B1@mbx-01.win.nominum.com> <1219647D-8408-41E7-BEA7-28E28E8E7B8B@gmail.com> <1363697845.2579.3.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775114AF8@mbx-01.win.nominum.com> <3901ACCE-E7A1-4F93-80EE-0BE961E7A6C2@gmail.com> <1363707264.2579.10.camel@marcin-lenovo> <CABsovMkSmnqcE6=xNq3AKatrHXM3bfRkh-iEFmOFqNQTbq3_yA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751153BB@mbx-01.win.nominum.com> <51489DC5.3090208@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775115A0C@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184B7FF3@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset="ISO-8859-15"
X-Mailer: Evolution 3.6.4 (3.6.4-2.fc18) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 19 Mar 2013 14:59:59 -0700
Cc: Yuchi Chen <chenycmx@gmail.com>, "weapon9@gmail.com" <weapon9@gmail.com>, "cuiyong@tsinghua.edu.cn" <cuiyong@tsinghua.edu.cn>, Ted Lemon <Ted.Lemon@nominum.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Cong Liu <gnocuil@gmail.com>, Qi Sun <sunqibupt@gmail.com>
Subject: Re: [dhcwg] Volunteer to work on configuring IPv4 over IPv6 network
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 21:16:36 -0000

On Tue, 2013-03-19 at 20:54 +0000, Bernie Volz (volz) wrote:
> I believe ... One important thing to keep in mind is that the DHCP client here is on the CPE device (router) and not a Windows, iOS, Linux, Android, ... device. So, changing the client isn't really that significant a concern. (The CPE device will also have NAT and a DHCP server just as they do today to use that one IPv4 address.) I think the diagram and document needs to be clear on this as the term "client" is often confusing (at least to me). CPE, gateway, residential router, "the network box", ... are probably better terms to use?

Yes. I agree that this is confusing and thus I suggest that we stop
using term "DHCP client".

> 
> There were a few times where I had my model confused and was thinking host or 'end client' (Windows, IOS, Linux, ... device) instead of CPE. And, that wrong model seems to be reflected in the artwork Marcin's draft currently has which shows V4/V6 going to the "Unified Relay". And while we could have such a model, I don't think it is correct and realistic. The DHCPv4 Client and DHCPv6 Client are in one box. The uplink side of that box communications IPv6 only to the SP. The v4/v6 side of the box communicates to "hosts" which are running standard operating systems. The "hosts" will do DHCPv4 and DHCPv6/SLAC to get addresses from the "box". The "box" will do NAT for v4 and tunnel v4 over v6 to the some tunnel endpoint.

What I think then is that we make a document that Qi Sun has sent a base
document for further work because it definitely better reflects the
goal. I removed the document that I have created to avoid confusion for
somebody looking into the repo and will eventually merge some parts of
it to the base document later on.

> 
> I do think we need to make sure we're all on the same page as to the model:
> 
>     Home Network with v4/v6 ----> CPE ----- v6-only link (DSL, Cable, ...) ----> SP network [with relays] -----> DHCPv6/v4 server
> 
> The CPE has NAT for v4 and also supports tunneling v4 over v6. The CPE has v6 only uplink. SP network is mostly v6 (has limited v4 for tunnel endpoints and perhaps some limited v4 services -- v4 is mostly for connectivity to Internet). The devices in the home use v4 pretty much as they would today behind a CPE that provides native v4 service (via NAT). They can use 'native' v6 (either via SLAC or DHCPv6).
> 
> 
> Ted wrote:
> "The only solution that makes sense to me is the one where the client sends a DHCPv4 packet wrapped in a special client header to the All_Relays_And_Servers multicast address on the DHCPv6 server port.   This uses the exact same infrastructure as DHCPv6, and requires no special DHCPv4-specific modifications other than on the server."
> 
> I agree. The uplink is only capable of IPv6 and so this packet must go over IPv6. And, as we assume that the CPE was given a PD (and perhaps v6 address) via DHCPv6, DHCPv6 support (relay or server) must be at the other end of this link.
> 
In this case we should probably remove the "Method 2 from the document
provided by Qi Sun" as we should move towards only one solution. 

> 
> I think it best to focus on the "base" solution without the optional enhancements? Once we get the "base" solution worked out, we can add the optional enhancements (either in the base document or as a separate one).

Yes, but maybe we could list the ideas for enhancements (as they already
exist) in a temporary section so as people reading this draft have big
picture of what work is planned that may affect the way the protocol is
working.

> - Bernie

Marcin

> 
> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com] 
> Sent: Tuesday, March 19, 2013 3:33 PM
> To: Tomek Mrugalski
> Cc: Qi Sun; Marcin Siodelski; Suresh Krishnan; Bernie Volz (volz); ian.farrer@telekom.de; cuiyong@tsinghua.edu.cn; weapon9@gmail.com; Cong Liu; Yuchi Chen; dhcwg@ietf.org
> Subject: Re: Volunteer to work on configuring IPv4 over IPv6 network
> 
> On Mar 19, 2013, at 1:17 PM, Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:
> > But still method 2 requires client update, which is a major pain. It 
> > is easier to update relays and server. Operators control their server 
> > and their relays, but they typically do not control the hosts. 
> > Operators can't force their customers to upgrade their software or hardware.
> 
> I think client update is a non-issue here, and in fact both options should require that the client be updated.   The reason is that an unmodified client isn't going to do the right thing with the answer anyway.   So although in principle you are right that the client is the hardest thing to modify, in this case we _have_ to modify it, so we might as well modify it completely, and not only halfway.
> 
> The only solution that makes sense to me is the one where the client sends a DHCPv4 packet wrapped in a special client header to the All_Relays_And_Servers multicast address on the DHCPv6 server port.   This uses the exact same infrastructure as DHCPv6, and requires no special DHCPv4-specific modifications other than on the server.
> 
> We have also talked about two other variations.   The first is the variation where the first relay agent knows the difference between a DHCPv6 message and a DHCPv4 message, and can send DHCPv6 messages to a different IPv6 address than DHCPv4 messages.
> 
> The other variation we talked about is the one where at the end of the relay chain, either the DHCP server or a DHCP relay agent that is connected to both the IPv6 network and an IPv4 network recognizes DHCPv4 packets being relayed to it and relays them over IPv4 to a DHCPv4 server.
> 
> These variations are just optional enhancements.   We don't need them, but someone might like them.   So they are probably worth clearly documenting, but the main thing that needs to be documented is how the client works, and this should be the same in all three cases: the main case and the two variations.
> 



From Ted.Lemon@nominum.com  Tue Mar 19 15:17:47 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E41F21F8D87 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 15:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level: 
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxHc3yH-oYG5 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 15:17:46 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 7EB1121F8D86 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 15:17:46 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUUjkCYgHNnPzHSqGzqgfdeoCWe6wH+id@postini.com; Tue, 19 Mar 2013 15:17:46 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 327C61B87E7 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 15:17:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 19975190043; Tue, 19 Mar 2013 15:17:45 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 19 Mar 2013 15:17:45 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: Volunteer to work on configuring IPv4 over IPv6 network
Thread-Index: AQHOITYqlpwdJNkYY0+mtV8vRI/hsJinH9aAgAAJBwCAAARngIAAAcyAgASvVoCAAAIYAIAAFO0AgAAWWgCAAAPpAIAABReAgAADLgCAABU+gIAAA0gAgACWUwCAAJrggIAADRaAgAAGxYCAAAKBgIAAEgiAgAAXUwCAAAt4gIAAAxOAgAAOZICAACWugIAAFsAAgAAXVAA=
Date: Tue, 19 Mar 2013 22:17:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751160B3@mbx-01.win.nominum.com>
References: <CD6CC9A8.5BCCE%ian.farrer@telekom.de> <8D23D4052ABE7A4490E77B1A012B63077511205D@mbx-01.win.nominum.com> <51471E7E.1000103@gmail.com> <8D23D4052ABE7A4490E77B1A012B63077511247C@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184B5058@xmb-rcd-x04.cisco.com> <514738CB.7070807@ericsson.com> <8D23D4052ABE7A4490E77B1A012B630775112704@mbx-01.win.nominum.com> <1363627335.5820.19.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775112B10@mbx-01.win.nominum.com> <8A60B830-C601-42B3-8AD1-5FA71A253435@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751147B1@mbx-01.win.nominum.com> <1219647D-8408-41E7-BEA7-28E28E8E7B8B@gmail.com> <1363697845.2579.3.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775114AF8@mbx-01.win.nominum.com> <3901ACCE-E7A1-4F93-80EE-0BE961E7A6C2@gmail.com> <1363707264.2579.10.camel@marcin-lenovo> <CABsovMkSmnqcE6=xNq3AKatrHXM3bfRkh-iEFmOFqNQTbq3_yA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751153BB@mbx-01.win.nominum.com> <51489DC5.3090208@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775115A0C@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184B7FF3@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E184B7FF3@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0D24B24744E83745946F4037255FB489@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 19 Mar 2013 15:33:19 -0700
Cc: Yuchi Chen <chenycmx@gmail.com>, "weapon9@gmail.com" <weapon9@gmail.com>, "cuiyong@tsinghua.edu.cn" <cuiyong@tsinghua.edu.cn>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Cong Liu <gnocuil@gmail.com>, Qi Sun <sunqibupt@gmail.com>
Subject: Re: [dhcwg] Volunteer to work on configuring IPv4 over IPv6 network
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 22:17:47 -0000

On Mar 19, 2013, at 4:54 PM, "Bernie Volz (volz)" <volz@cisco.com> wrote:
> I do think we need to make sure we're all on the same page as to the mode=
l:
>=20
>    Home Network with v4/v6 ----> CPE ----- v6-only link (DSL, Cable, ...)=
 ----> SP network [with relays] -----> DHCPv6/v4 server

It's possible that some other use model will surface in the future, so I do=
n't think we should insist that the client has to be a CPE device.   But th=
at should definitely be the model that's used to explain the protocol; we s=
hould just include a disclaimer in the applicability statement that says th=
at while the currently identified use case is a CPE device with a tunnel, t=
his should not be read as excluding other use cases that are identified in =
the future.


From mohta@necom830.hpcl.titech.ac.jp  Tue Mar 19 16:08:02 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA39C21F8C71 for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 16:07:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-oIllYqllig for <dhcwg@ietfa.amsl.com>; Tue, 19 Mar 2013 16:07:50 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id D4D3821F8C45 for <dhcwg@ietf.org>; Tue, 19 Mar 2013 16:07:49 -0700 (PDT)
Received: (qmail 88694 invoked from network); 19 Mar 2013 23:05:52 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 19 Mar 2013 23:05:52 -0000
Message-ID: <5148EFAC.9010904@necom830.hpcl.titech.ac.jp>
Date: Wed, 20 Mar 2013 08:07:24 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com>	<51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com> <489D13FBFA9B3E41812EA89F188F018E184B6468@xmb-rcd-x04.cisco.com> <5147E36D.1060003@gmail.com>
In-Reply-To: <5147E36D.1060003@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Mar 2013 23:08:02 -0000

Alexandru Petrescu wrote:

> It would be strange to see an IPv6-over-802.11ai IETF document, because
> one would expect IPv6 over 'ai' to work just like IPv6 over 802.11b
> which is same as IPv6-over-Ethernet.

Actually, Ethernet with CSMA/CD and Wifi with CSMA/CA behaves
differently for broadcast/multicast packets.

With Wifi, as it is impossible to detect collisions, every
packet is ACKed to confirm collision did not occur. Otherwise,
the packet is resent. However, ACK is applicable only to unicast.

Thus, broadcast/multicast over Wifi is not as reliable as
that over Ethernet.

Thus, though IP-over-Ethernet works as IP-over-Wifi, it sometimes
loss broadcast/multicast packets and may not be very efficient.

						Masataka Ohta


From cas@trans-nt.com  Wed Mar 20 05:43:47 2013
Return-Path: <cas@trans-nt.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F2DD21F87A4 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 05:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.631
X-Spam-Level: 
X-Spam-Status: No, score=-0.631 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4nyl3Ts1uKyz for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 05:43:46 -0700 (PDT)
Received: from dump.fs.trans-nt.com (smtp.trans-nt.co.jp [202.10.98.251]) by ietfa.amsl.com (Postfix) with SMTP id 3005821F8200 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 05:43:45 -0700 (PDT)
Received: (qmail 78875 invoked from network); 20 Mar 2013 21:43:36 +0900
Received: from red.fs.trans-nt.co.jp (HELO platinum.local) (202.10.98.240) by smtp.trans-nt.co.jp with SMTP; 20 Mar 2013 21:43:36 +0900
Message-ID: <5149AEF9.3050309@trans-nt.com>
Date: Wed, 20 Mar 2013 21:43:37 +0900
From: Hiroki Nakano <cas@trans-nt.com>
Organization: cas authorized 53a6c6e30f1471298320e605c741e412
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <4F5EA754.50403@trans-nt.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63077511326B@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077511326B@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Mar 2013 12:43:47 -0000

(13/03/19 5:12), Ted Lemon wrote:
> On Mar 18, 2013, at 3:55 PM, Hiroki Nakano <cas@trans-nt.com> wrote:
>> The bimonthly week of TGai has been started today
>> in the same place as IETF86 of the last week.
>> The battle is a draw for now.
> 
> Are you going to discuss this further in this IEEE meeting,
> or is that it until next time?

I'm participating in the discussion at Caribe Royale.
We are making effort to have a conclusion in this week.
If TGai decides to provide a generic container framework
which can be used to transfer DHCP messages,
why don't you continue to talk about DHCP and 802.11ai? :)

Regards,

Hiroki Nakano
Trans New Technology, Inc. <cas@trans-nt.com>

From alexandru.petrescu@gmail.com  Wed Mar 20 06:00:20 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7D921F8C97 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 06:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.167
X-Spam-Level: 
X-Spam-Status: No, score=-10.167 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JjZv7Mn7sYYC for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 06:00:19 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 4CFF321F8C9B for <dhcwg@ietf.org>; Wed, 20 Mar 2013 06:00:19 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2KD0IV8030268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Wed, 20 Mar 2013 14:00:18 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2KD0I9t032392 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 14:00:18 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2KD0Dsx031150 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 14:00:18 +0100
Message-ID: <5149B2B5.3020202@gmail.com>
Date: Wed, 20 Mar 2013 13:59:33 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63077511326B@mbx-01.win.nominum.com> <5149AEF9.3050309@trans-nt.com>
In-Reply-To: <5149AEF9.3050309@trans-nt.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCPv6-and-Routes-Routers-to-Client
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Mar 2013 13:00:20 -0000

Le 20/03/2013 13:43, Hiroki Nakano a écrit :
> (13/03/19 5:12), Ted Lemon wrote:
>> On Mar 18, 2013, at 3:55 PM, Hiroki Nakano <cas@trans-nt.com>
>> wrote:
>>> The bimonthly week of TGai has been started today in the same
>>> place as IETF86 of the last week. The battle is a draw for now.
>>
>> Are you going to discuss this further in this IEEE meeting, or is
>> that it until next time?
>
> I'm participating in the discussion at Caribe Royale. We are making
> effort to have a conclusion in this week. If TGai decides to provide
> a generic container framework which can be used to transfer DHCP
> messages,

To transfer DHCP messages?  Or to transfer parameters which are usually
configured by DHCPv6 and by Stateless-Address-Auto-configuration?

Do you mean a typical Ethernet frame which would carry a DHCPv6 message
with EtherType 0x86DD?

Or other kind of Ethernet container which would be dedicated to transfer
specifically DHCPv6 messages?

There may be interest to realize fast configuration with DHCPv6.  There
are some IP tools at our disposal.  One that may be useful is also the
RAPID COMMIT option of DHCP.

> why don't you continue to talk about DHCP and 802.11ai? :)

Because we must be careful about this discussion DHCPv6-and-routes
discussion.

DHCPv6-and-routes/routers-to-Client have been discussed in public in few
mailing lists (6MAN, MIF, DHC), since 2-5 years, and in private.  There
is risk of contingency, it is sensitive.  There are risks of being
qualified as architecturally incompatible.

For the particular case of DHCPv6-defaultroute - this approaches in some
way very much the IEEE 802.16ai documents that were pointed in this list.

The IEEE 802.11ai documents propose - among other things - to put the
IPv6 Gateway address in the 802.16ai message.  The 'IPv6 Gateway' is
practically the IPv6 address of the router which should be used as
Default Router by the Client STA.

Regardless of the discussion whether the IPv6 Gateway should be present
in a link-layer message (rather than in a DHCPv6, or Router
Advertisement message)...

... there is lack of consensus - read strong disagreements at IETF -
about whether the IPv6 Gateway should be present in DHCPv6 message at
all (because typically the Default Router's address is present in a
Router Advertisement message - currently DHCPv6 doesnt have an option to
deliver default routes to Client).  These disagreements hurt at many places.

(I have my own oppinion about this idea of using IPv6 Gateway address in
a DHCPv6 message vs RA message;  there are several Internet Drafts which
propose to use DHCPv6 to configure routes, default routes, etc.)

Alex


>
> Regards,
>
> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From internet-drafts@ietf.org  Wed Mar 20 07:11:05 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 949F321F8FA4; Wed, 20 Mar 2013 07:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.427
X-Spam-Level: 
X-Spam-Status: No, score=-102.427 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m-Cl+WTrqBcH; Wed, 20 Mar 2013 07:11:05 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 291CF21F8AD4; Wed, 20 Mar 2013 07:11:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43
Message-ID: <20130320141105.10827.50644.idtracker@ietfa.amsl.com>
Date: Wed, 20 Mar 2013 07:11:05 -0700
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-06.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Mar 2013 14:11:05 -0000

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

	Title           : DHCPv4 over IPv6 Transport
	Author(s)       : Yong Cui
                          Peng Wu
                          Jianping Wu
                          Ted Lemon
	Filename        : draft-ietf-dhc-dhcpv4-over-ipv6-06.txt
	Pages           : 14
	Date            : 2013-03-20

Abstract:
   In IPv6 networks, there remains a need to provide IPv4 service for
   some residual devices.  This document describes a mechanism for
   allocating IPv4 addresses to such devices, using DHCPv4 with an IPv6
   transport.  It is done by putting a special relay agent function
   (Client Relay Agent) on the client side, as well as extending the
   behavior of the server; in the case where DHCP server only supports
   IPv4 transport, a relay agent is extended to support IPv6 transport
   (IPv6-Transport Relay Agent) and relay DHCP traffic for the server,
   with a new Relay Agent Information sub-option added to carry the IPv6
   address of the Client Relay Agent.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dhcpv4-over-ipv6-06


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


From Ted.Lemon@nominum.com  Wed Mar 20 04:48:54 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF2021F8414 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 04:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.584
X-Spam-Level: 
X-Spam-Status: No, score=-106.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UUlQARyHU7IC for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 04:48:53 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 6B6B321F841C for <dhcwg@ietf.org>; Wed, 20 Mar 2013 04:48:48 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUUmiIFkn091FT8vo855yRPy+ZsCtsBiB@postini.com; Wed, 20 Mar 2013 04:48:52 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 B70431B87A3 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 04:48:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A73DA19005C; Wed, 20 Mar 2013 04:48:47 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 20 Mar 2013 04:48:41 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: Volunteer to work on configuring IPv4 over IPv6 network
Thread-Index: AQHOITYqlpwdJNkYY0+mtV8vRI/hsJinH9aAgAAJBwCAAARngIAAAcyAgASvVoCAAAIYAIAAFO0AgAAWWgCAAAPpAIAABReAgAADLgCAABU+gIAAA0gAgACWUwCAAJrggIAADRaAgAAGxYCAAAKBgIAAEgiAgAAXUwCAAAt4gIAAAxOAgAAOZICAACWugIAAFsAAgAAXVACAAG50AIAAdB2A
Date: Wed, 20 Mar 2013 11:48:40 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775116CA9@mbx-01.win.nominum.com>
References: <CD6CC9A8.5BCCE%ian.farrer@telekom.de> <514738CB.7070807@ericsson.com> <8D23D4052ABE7A4490E77B1A012B630775112704@mbx-01.win.nominum.com> <1363627335.5820.19.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775112B10@mbx-01.win.nominum.com> <8A60B830-C601-42B3-8AD1-5FA71A253435@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751147B1@mbx-01.win.nominum.com> <1219647D-8408-41E7-BEA7-28E28E8E7B8B@gmail.com> <1363697845.2579.3.camel@marcin-lenovo> <8D23D4052ABE7A4490E77B1A012B630775114AF8@mbx-01.win.nominum.com> <3901ACCE-E7A1-4F93-80EE-0BE961E7A6C2@gmail.com> <1363707264.2579.10.camel@marcin-lenovo> <CABsovMkSmnqcE6=xNq3AKatrHXM3bfRkh-iEFmOFqNQTbq3_yA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751153BB@mbx-01.win.nominum.com> <51489DC5.3090208@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775115A0C@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184B7FF3@xmb-rcd-x04.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751160B3@mbx-01.win.nominum.com> <514940B0.1060009@ericsson.com>
In-Reply-To: <514940B0.1060009@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C66308CC2A0B32448BB804BDBE498305@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 20 Mar 2013 08:09:50 -0700
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>, Yuchi Chen <chenycmx@gmail.com>, "weapon9@gmail.com" <weapon9@gmail.com>, "cuiyong@tsinghua.edu.cn" <cuiyong@tsinghua.edu.cn>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Cong Liu <gnocuil@gmail.com>, Qi Sun <sunqibupt@gmail.com>
Subject: Re: [dhcwg] Volunteer to work on configuring IPv4 over IPv6 network
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Mar 2013 11:48:54 -0000

On Mar 20, 2013, at 12:53 AM, Suresh Krishnan <suresh.krishnan@ericsson.com=
> wrote:
> where the unmodified clients send out DHCPv4 messages that are
> encapsulated by a relay (which I call an IFRA) into a DHCPv6
> Relay-forward message? Or do people think this case is not important?

In a real dual-stack network, can't you just do DHCPv4 directly?=

From alexandru.petrescu@gmail.com  Wed Mar 20 10:52:52 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8623C21F8FC4 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 10:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.179
X-Spam-Level: 
X-Spam-Status: No, score=-10.179 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECh3dLTPHChQ for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 10:52:52 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id E97C221F8FB0 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 10:52:42 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2KHqfcK013440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Wed, 20 Mar 2013 18:52:41 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2KHqf2d026574 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 18:52:41 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2KHqeoG001611 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 18:52:41 +0100
Message-ID: <5149F73F.1090503@gmail.com>
Date: Wed, 20 Mar 2013 18:51:59 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Mar 2013 17:52:52 -0000

DHC participants,

Should the IPv6 Gateway address be put in the 802.11ai message? (or in
DHCPv6 message?)  Or both?  Or none?

Alex


From otroan@employees.org  Wed Mar 20 14:39:48 2013
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA3121F8BBD for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 14:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BV+2ZwiTPLZe for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 14:39:47 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id B696421F8B7C for <dhcwg@ietf.org>; Wed, 20 Mar 2013 14:39:47 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 5369D5EC7; Wed, 20 Mar 2013 14:39:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=LLkg4vVgeWnCnCF8do/kKQ7eKoY=; b=pc2EJp+XfOvRMOwYU3 l9z5BGT/tShNlHiOfnqWOJayNxoDucLHeznyqzXo3NOFqX4y6OkzauBceYDKHhjH qJTDFw75OCKc6O6W1DK0pQfAPBdzcw6A2y4ZLYWhhvIkKlYcFX9pQPXvC51RK1rW BOrxCcxN/m1lRpJetxRZzoxFY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=pWDr3HmUCWPJZrXb6wDEx0vC07DOag37H196sctFAVc3vqW/g/k 1DFV47a1N+IOOehEFIeLi45LuAsnQp8Q75waf3jkd4PwRSm6iZo3e9jIjNvRikR9 nl4HQsgb4PGrQqXOELD9ol2XUsmqPipJFykk+28dhHWzidRqn5TT8tvY=
Received: from dhcp-10-61-103-185.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id B39BB5EBC; Wed, 20 Mar 2013 14:39:46 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <5149F73F.1090503@gmail.com>
Date: Wed, 20 Mar 2013 22:39:45 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org>
References: <5149F73F.1090503@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Mar 2013 21:39:48 -0000

> Should the IPv6 Gateway address be put in the 802.11ai message? (or in
> DHCPv6 message?)  Or both?  Or none?

I think we understand the tradeoffs of using ND for router discovery.
(dynamic, fate-sharing, supports multiple provisioning domains).

what are the benefits of using DHCP for this?

and speaking as someone who has very little clue about 802.11ai,
what makes it so different?

cheers,
Ole

From Ted.Lemon@nominum.com  Wed Mar 20 14:44:27 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E23F211E80F5 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 14:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.585
X-Spam-Level: 
X-Spam-Status: No, score=-106.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gI4QD8LPSa9o for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 14:44:27 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 652B311E80F4 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 14:44:27 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUUottkjCW3iT8rAJuXhBe6KYCpRkii1j@postini.com; Wed, 20 Mar 2013 14:44:27 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 D6F1D1B873B for <dhcwg@ietf.org>; Wed, 20 Mar 2013 14:44:21 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id C9BB519005C; Wed, 20 Mar 2013 14:44:21 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 20 Mar 2013 14:44:21 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
Thread-Index: AQHOJZPBKoHr2gkBTEugM3upxKrsdZivkRGAgAABSAA=
Date: Wed, 20 Mar 2013 21:44:20 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com>
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org>
In-Reply-To: <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6C4381244C42314FA8DA6D0F75A98D65@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai	message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Mar 2013 21:44:28 -0000

On Mar 20, 2013, at 5:39 PM, Ole Troan <otroan@employees.org> wrote:
> what are the benefits of using DHCP for this?

The stated goal is to speed up the address assignment process.

> and speaking as someone who has very little clue about 802.11ai,
> what makes it so different?

The 802.11 stack is fairly heavyweight at this point, so it takes a long ti=
me to connect; reducing the address assignment time is one way to decrease =
the over all connect time.

I think this is going to turn out to be a manageability nightmare, but what=
 do I know?


From otroan@employees.org  Wed Mar 20 15:15:34 2013
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3CDA21F8C4C for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 15:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pyy6HdQE4guS for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 15:15:33 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0120C21F8C3E for <dhcwg@ietf.org>; Wed, 20 Mar 2013 15:15:32 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAOUzSlGQ/khM/2dsb2JhbABExCGBDYFSFnSCJAEBBAE6PwULC0ZXBoghBsJbjlwzB4JfYQOnYoMLOw
X-IronPort-AV: E=Sophos;i="4.84,880,1355097600"; d="scan'208";a="152017751"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 20 Mar 2013 22:15:30 +0000
Received: from dhcp-10-61-103-185.cisco.com (dhcp-10-61-103-185.cisco.com [10.61.103.185]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2KMFVT0017386 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 20 Mar 2013 22:15:31 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com>
Date: Wed, 20 Mar 2013 23:15:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <56B910CB-3D2B-4F84-A1F2-97FD85E8064C@employees.org>
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1499)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 20 Mar 2013 22:15:34 -0000

>> what are the benefits of using DHCP for this?
>=20
> The stated goal is to speed up the address assignment process.

OK, but what does that have to do with router discovery?

>> and speaking as someone who has very little clue about 802.11ai,
>> what makes it so different?
>=20
> The 802.11 stack is fairly heavyweight at this point, so it takes a =
long time to connect; reducing the address assignment time is one way to =
decrease the over all connect time.

reducing connection time seems to be a good goal. has anyone done =
measurements of what actually takes time?
before we get around to changing specifications I mean.

> I think this is going to turn out to be a manageability nightmare, but =
what do I know?

or a deployment one...

cheers,
Ole



From Ted.Lemon@nominum.com  Wed Mar 20 17:14:23 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DC9711E8115 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 17:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.586
X-Spam-Level: 
X-Spam-Status: No, score=-106.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZRiv4GaKk73 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 17:14:22 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB0911E810D for <dhcwg@ietf.org>; Wed, 20 Mar 2013 17:14:22 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUUpQ3jhh54/90pqUvVL8Rn8YgVd97e37@postini.com; Wed, 20 Mar 2013 17:14:22 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 F35DA1B873F for <dhcwg@ietf.org>; Wed, 20 Mar 2013 17:14:20 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id E23BF19005C; Wed, 20 Mar 2013 17:14:20 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 20 Mar 2013 17:14:20 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
Thread-Index: AQHOJZPBKoHr2gkBTEugM3upxKrsdZivkRGAgAABSACAAAi2gIAAITGA
Date: Thu, 21 Mar 2013 00:14:20 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775117FF3@mbx-01.win.nominum.com>
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com> <56B910CB-3D2B-4F84-A1F2-97FD85E8064C@employees.org>
In-Reply-To: <56B910CB-3D2B-4F84-A1F2-97FD85E8064C@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4639ACD791D6F54CAFF3D96BC42D6163@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai	message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 00:14:23 -0000

On Mar 20, 2013, at 6:15 PM, Ole Troan <otroan@employees.org> wrote:
>> The stated goal is to speed up the address assignment process.
> OK, but what does that have to do with router discovery?

ND is an extra round trip.

Honestly, the burning question in my mind is how, given that you are gettin=
g a new IP address, you avoid glitches on reconnect.   But the bottom line =
is that this work is being done in the IEEE, not here, so none of this disc=
ussion here is going to make much difference.


From mohta@necom830.hpcl.titech.ac.jp  Wed Mar 20 17:31:02 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 657BA21F8DE3 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 17:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.84
X-Spam-Level: 
X-Spam-Status: No, score=0.84 tagged_above=-999 required=5 tests=[AWL=-0.930,  BAYES_20=-0.74, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tmgt+hyPk3D5 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 17:31:01 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 7141921F8DDF for <dhcwg@ietf.org>; Wed, 20 Mar 2013 17:31:01 -0700 (PDT)
Received: (qmail 13605 invoked from network); 21 Mar 2013 00:29:04 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 21 Mar 2013 00:29:04 -0000
Message-ID: <514A54AF.1070808@necom830.hpcl.titech.ac.jp>
Date: Thu, 21 Mar 2013 09:30:39 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 00:31:02 -0000

Ted Lemon wrote:

> The stated goal is to speed up the address assignment process.

Another important goal is to reduce the number of packets,
because PPS (packets per second) of Wifi is limited.

> I think this is going to turn out to be a manageability nightmare,
> but what do I know?

?

					Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Wed Mar 20 17:46:08 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FECD21F8DDF for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 17:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.096
X-Spam-Level: 
X-Spam-Status: No, score=0.096 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ahwo60Arv6h for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 17:46:07 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 665FE21F8DD6 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 17:46:05 -0700 (PDT)
Received: (qmail 13817 invoked from network); 21 Mar 2013 00:44:08 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 21 Mar 2013 00:44:08 -0000
Message-ID: <514A5837.1040509@necom830.hpcl.titech.ac.jp>
Date: Thu, 21 Mar 2013 09:45:43 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com> <56B910CB-3D2B-4F84-A1F2-97FD85E8064C@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117FF3@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775117FF3@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 00:46:08 -0000

Ted Lemon wrote:

> ND is an extra round trip.
> 
> Honestly, the burning question in my mind is how, given that
> you are getting a new IP address, you avoid glitches on reconnect.

By using IP mobility and by simultaneously connecting to both the
current and a new base stations, there are no glitches.

						Masataka Ohta


From Ted.Lemon@nominum.com  Wed Mar 20 18:20:19 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2C5421F8C48 for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 18:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.586
X-Spam-Level: 
X-Spam-Status: No, score=-106.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBVQSs1jeXEl for <dhcwg@ietfa.amsl.com>; Wed, 20 Mar 2013 18:20:17 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA2021F8B65 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 18:20:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKUUpgTWCVkj8Uo+jG8fa0WrTDvpc59iEQ@postini.com; Wed, 20 Mar 2013 18:20:17 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 64FEC1B8741 for <dhcwg@ietf.org>; Wed, 20 Mar 2013 18:20:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 5EBAD19005C; Wed, 20 Mar 2013 18:20:13 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 20 Mar 2013 18:20:13 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Thread-Topic: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
Thread-Index: AQHOJctf4X9JCfWlt0+8Rs58HtIveZivzduA
Date: Thu, 21 Mar 2013 01:20:12 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751180E3@mbx-01.win.nominum.com>
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com> <514A54AF.1070808@necom830.hpcl.titech.ac.jp>
In-Reply-To: <514A54AF.1070808@necom830.hpcl.titech.ac.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9E4F50BE874E3D45962DD14EF774F12A@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 01:20:20 -0000

On Mar 20, 2013, at 8:30 PM, Masataka Ohta <mohta@necom830.hpcl.titech.ac.j=
p> wrote:
> Another important goal is to reduce the number of packets,
> because PPS (packets per second) of Wifi is limited.

That's adorable.


From internet-drafts@ietf.org  Thu Mar 21 00:07:28 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6EE21F9047; Thu, 21 Mar 2013 00:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.437
X-Spam-Level: 
X-Spam-Status: No, score=-102.437 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id It5-A5invTU4; Thu, 21 Mar 2013 00:07:27 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 960A121F9020; Thu, 21 Mar 2013 00:07:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43
Message-ID: <20130321070727.28795.20395.idtracker@ietfa.amsl.com>
Date: Thu, 21 Mar 2013 00:07:27 -0700
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-triggered-reconfigure-05.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 07:07:28 -0000

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

	Title           : Reconfigure Triggered by DHCPv6 Relay Agents
	Author(s)       : Mohamed Boucadair
                          Xavier Pougnard
	Filename        : draft-ietf-dhc-triggered-reconfigure-05.txt
	Pages           : 13
	Date            : 2013-03-21

Abstract:
   This document defines new DHCPv6 messages: Reconfigure-Request and
   Reconfigure-Reply.  Reconfigure-Request message is sent by a DHCPv6
   relay agent to notify a DHCPv6 server about a configuration
   information change, so that the DHCPv6 server can send a Reconfigure
   message accordingly.  Reconfigure-Reply message is used by the server
   to acknowledge the receipt of Reconfigure-Request.

   This document updates RFC 3315 and RFC 6422.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-triggered-reconfigure-05


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


From alexandru.petrescu@gmail.com  Thu Mar 21 00:36:22 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B35021F8FFA for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.181
X-Spam-Level: 
X-Spam-Status: No, score=-10.181 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W6WF+ydM8ckS for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:36:17 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 34E1921F899E for <dhcwg@ietf.org>; Thu, 21 Mar 2013 00:36:17 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2L7aBiW022241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 21 Mar 2013 08:36:11 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2L7aBN5025063; Thu, 21 Mar 2013 08:36:11 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2L7aAf6020684; Thu, 21 Mar 2013 08:36:11 +0100
Message-ID: <514AB83F.3060006@gmail.com>
Date: Thu, 21 Mar 2013 08:35:27 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org>
In-Reply-To: <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 07:36:22 -0000

Le 20/03/2013 22:39, Ole Troan a écrit :
>> Should the IPv6 Gateway address be put in the 802.11ai message? (or
>> in DHCPv6 message?)  Or both?  Or none?
>
> I think we understand the tradeoffs of using ND for router
> discovery. (dynamic, fate-sharing, supports multiple provisioning
> domains).
>
> what are the benefits of using DHCP for this?

DHCPv6-alone could be provide faster configuration than a combination of
ND and DHCPv6 which is mandatory in some cases.

In IPv4 DHCPv4 could be used alone.

> and speaking as someone who has very little clue about 802.11ai, what
> makes it so different?

I have little clue as well and I am looking for education about 802.11ai.

I also wonder whether 802.11ai could transport IP messages (like 802.11b
does).

Alex

>
> cheers, Ole
>
>



From alexandru.petrescu@gmail.com  Thu Mar 21 00:38:04 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 291FC21F8F9E for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.182
X-Spam-Level: 
X-Spam-Status: No, score=-10.182 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5S5duwirvX07 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:37:55 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1C121F902C for <dhcwg@ietf.org>; Thu, 21 Mar 2013 00:37:52 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2L7bqCX026123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:37:52 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2L7bpvN025564 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:37:52 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2L7bpsI021506 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:37:51 +0100
Message-ID: <514AB8A4.1070305@gmail.com>
Date: Thu, 21 Mar 2013 08:37:08 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com> <56B910CB-3D2B-4F84-A1F2-97FD85E8064C@employees.org>
In-Reply-To: <56B910CB-3D2B-4F84-A1F2-97FD85E8064C@employees.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 07:38:04 -0000

Le 20/03/2013 23:15, Ole Troan a écrit :
>>> what are the benefits of using DHCP for this?
>>
>> The stated goal is to speed up the address assignment process.
>
> OK, but what does that have to do with router discovery?
>
>>> and speaking as someone who has very little clue about 802.11ai,
>>>  what makes it so different?
>>
>> The 802.11 stack is fairly heavyweight at this point, so it takes
>> a long time to connect; reducing the address assignment time is
>> one way to decrease the over all connect time.
>
> reducing connection time seems to be a good goal. has anyone done
> measurements of what actually takes time? before we get around to
> changing specifications I mean.

We did some measurements about how fast a client can get full yet
minimal configuration in IPv6 with ND and DHCPv6.  Basically it comes
down to reducing from something like 4 to 2 messages (if only DHCPv6
were used).

>> I think this is going to turn out to be a manageability nightmare,
>> but what do I know?
>
> or a deployment one...

Lets see which one.

Alex

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



From alexandru.petrescu@gmail.com  Thu Mar 21 00:40:00 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8CD21F9013 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.183
X-Spam-Level: 
X-Spam-Status: No, score=-10.183 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWLHdMA58VoC for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:39:56 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB3A21F8F9E for <dhcwg@ietf.org>; Thu, 21 Mar 2013 00:39:56 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2L7dtls024337 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:39:55 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2L7dtYi026255 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:39:55 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2L7dsmb022587 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:39:55 +0100
Message-ID: <514AB91F.3090505@gmail.com>
Date: Thu, 21 Mar 2013 08:39:11 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com> <56B910CB-3D2B-4F84-A1F2-97FD85E8064C@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117FF3@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775117FF3@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 07:40:00 -0000

Le 21/03/2013 01:14, Ted Lemon a écrit :
> On Mar 20, 2013, at 6:15 PM, Ole Troan <otroan@employees.org> wrote:
>>> The stated goal is to speed up the address assignment process.
>> OK, but what does that have to do with router discovery?
>
> ND is an extra round trip.
>
> Honestly, the burning question in my mind is how, given that you are
> getting a new IP address, you avoid glitches on reconnect.   But the
> bottom line is that this work is being done in the IEEE, not here,
> so none of this discussion here is going to make much difference.

I think it could make a little difference.

If the IPv6 Gateway is provided by a link-layer message of 802.11ai then
one must make sure the Router Advertisement sets the Lifetime to 0 (i.e.
imply that the src of that IP packet RA should _not_ be used as default
router).

In this way there is no risk of misconfiguration.

Alex

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



From alexandru.petrescu@gmail.com  Thu Mar 21 00:41:03 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E22B21F8F9E for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.184
X-Spam-Level: 
X-Spam-Status: No, score=-10.184 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8u6orGF2AHg for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:40:59 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 199A321F8F44 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 00:40:58 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2L7ew3u024887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:40:58 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2L7evi9026729 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:40:58 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2L7evQs023240 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:40:57 +0100
Message-ID: <514AB95E.1020301@gmail.com>
Date: Thu, 21 Mar 2013 08:40:14 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com> <514A54AF.1070808@necom830.hpcl.titech.ac.jp>
In-Reply-To: <514A54AF.1070808@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 07:41:03 -0000

Le 21/03/2013 01:30, Masataka Ohta a écrit :
> Ted Lemon wrote:
>
>> The stated goal is to speed up the address assignment process.
>
> Another important goal is to reduce the number of packets, because
> PPS (packets per second) of Wifi is limited.

Yes, depending on the bandwidth (from 1Mbit/s up to 1Gbit/s), the number
of packets per second in WiFi is limited to a certain number.

Alex

>
>> I think this is going to turn out to be a manageability nightmare,
>> but what do I know?
>
> ?
>
> Masataka Ohta _______________________________________________ dhcwg
> mailing list dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From alexandru.petrescu@gmail.com  Thu Mar 21 00:41:41 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 297B621F8F9E for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.186
X-Spam-Level: 
X-Spam-Status: No, score=-10.186 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fVe4clTKaOI5 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 00:41:37 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id E274721F8F44 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 00:41:36 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2L7faVO027649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:41:36 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2L7fZ9F026938 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:41:35 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2L7fZrE023551 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:41:35 +0100
Message-ID: <514AB984.7030502@gmail.com>
Date: Thu, 21 Mar 2013 08:40:52 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <5149F73F.1090503@gmail.com> <DFD8A16A-13A2-4614-96D5-7B5332C4A744@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117D87@mbx-01.win.nominum.com> <56B910CB-3D2B-4F84-A1F2-97FD85E8064C@employees.org> <8D23D4052ABE7A4490E77B1A012B630775117FF3@mbx-01.win.nominum.com> <514A5837.1040509@necom830.hpcl.titech.ac.jp>
In-Reply-To: <514A5837.1040509@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] 802.11ai - should IPv6 Gateway be put in the 802.11ai message?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 07:41:41 -0000

Le 21/03/2013 01:45, Masataka Ohta a écrit :
> Ted Lemon wrote:
>
>> ND is an extra round trip.
>>
>> Honestly, the burning question in my mind is how, given that you
>> are getting a new IP address, you avoid glitches on reconnect.
>
> By using IP mobility and by simultaneously connecting to both the
> current and a new base stations, there are no glitches.

But if by IP mobility is meant Mobile IP then that has additional
roundtrips to involve (in addition to address autoconfiguration).

Alex

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



From cas@trans-nt.com  Thu Mar 21 06:48:47 2013
Return-Path: <cas@trans-nt.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B2F221F856F for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 06:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.681
X-Spam-Level: 
X-Spam-Status: No, score=-0.681 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HPJrAkQzhOD8 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 06:48:46 -0700 (PDT)
Received: from dump.fs.trans-nt.com (smtp.trans-nt.co.jp [202.10.98.251]) by ietfa.amsl.com (Postfix) with SMTP id 0710B21F84BC for <dhcwg@ietf.org>; Thu, 21 Mar 2013 06:48:45 -0700 (PDT)
Received: (qmail 14624 invoked from network); 21 Mar 2013 22:48:40 +0900
Received: from red.fs.trans-nt.co.jp (HELO platinum.local) (202.10.98.240) by smtp.trans-nt.co.jp with SMTP; 21 Mar 2013 22:48:40 +0900
Message-ID: <514B0FB8.9070502@trans-nt.com>
Date: Thu, 21 Mar 2013 22:48:40 +0900
From: Hiroki Nakano <cas@trans-nt.com>
Organization: cas authorized 53a6c6e30f1471298320e605c741e412
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63077511326B@mbx-01.win.nominum.com> <5149AEF9.3050309@trans-nt.com> <5149B2B5.3020202@gmail.com>
In-Reply-To: <5149B2B5.3020202@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCPv6-and-Routes-Routers-to-Client
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 13:48:47 -0000

(13/03/20 21:59), Alexandru Petrescu wrote:
>> I'm participating in the discussion at Caribe Royale. We are making
>> effort to have a conclusion in this week. If TGai decides to provide
>> a generic container framework which can be used to transfer DHCP
>> messages,
> 
> To transfer DHCP messages?  Or to transfer parameters which are usually
> configured by DHCPv6 and by Stateless-Address-Auto-configuration?

My position is that generic container should be defined to transfer
packets of upper layers such as DHCPv4, RS/RA, DHCPv6 etc.

> Do you mean a typical Ethernet frame which would carry a DHCPv6 message
> with EtherType 0x86DD?

Yes.

The newest proposal is at the URL below.
https://mentor.ieee.org/802.11/dcn/13/11-13-0235-02-00ai-ip-address-setup.doc
We finally have merged two proposals and implementors can choose them.
And this framework has been approved by TGai yesterday.

IEEE 802.11ai is just A link layer.
Therefore, how to use 802.11ai should be discussed by people of
upper layers and it is none of business of TGai itself.

On the other hand,
TGai has its own use cases and the principle.
As Tomek pointed out before, speed is of essence of TGai.
Imagine that you go through in front of an AP by car.
You have only 10 seconds.  It's only for 10 seconds you can
communicate with the AP!  You never want to waste even one
round trip of packets.
Accommodating numerous STA is the other aspect of TGai.
Assume that an AP is installed at Tokyo station.
1000 people per minute are passing beside the AP.
They all perform 802.11 association process and
IP layer configuration process such as DHCP.
All of piled protocols should be required to be as
efficient as possible for such environments.

I hope to share these principles with IETF people widely
and discuss the whole protocol stack from the link layer
to application layers.  Some people already have
the understanding and I'm so happy:)

P.S.
An interesting report is below.
https://mentor.ieee.org/802.11/dcn/13/11-13-0323-02-00ai-tgai-experimental-test-report-of-fils.pptx
Check it out.
If you can not play video in ppt, you can see at
http://www.youtube.com/watch?v=xOKaVOPWXTU
I'm also in this video. hehe:)

Regards,

Hiroki Nakano
Trans New Technology, Inc. <cas@trans-nt.com>

From h.wahl@ifw-dresden.de  Thu Mar 21 08:51:36 2013
Return-Path: <h.wahl@ifw-dresden.de>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FDDA21F9125 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 08:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8rUtmzdgeXc9 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 08:51:35 -0700 (PDT)
Received: from mailout01.ifw-dresden.de (mailout01.ifw-dresden.de [IPv6:2001:638:90a:d00:feed:b0:3:1]) by ietfa.amsl.com (Postfix) with ESMTP id DF05621F912C for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:51:34 -0700 (PDT)
Received: from mailin01i.ifw-dresden.de (mailin01i.ifw-dresden.de [172.19.2.2]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout01.ifw-dresden.de (Postfix) with ESMTP id 9896E7CECE for <dhcwg@ietf.org>; Thu, 21 Mar 2013 16:51:26 +0100 (CET)
Received: from [172.16.101.25] (w73lx-wahl.ifw-dresden.de [172.16.101.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailin01i.ifw-dresden.de (Postfix) with ESMTP id 8C60D7CE4F for <dhcwg@ietf.org>; Thu, 21 Mar 2013 16:51:26 +0100 (CET)
Message-ID: <514B2C7E.9000907@ifw-dresden.de>
Date: Thu, 21 Mar 2013 16:51:26 +0100
From: Henri Wahl <h.wahl@ifw-dresden.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020303050408080604070204"
Subject: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 15:51:36 -0000

Dies ist eine kryptografisch unterzeichnete Nachricht im MIME-Format.

--------------ms020303050408080604070204
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

We want to deliver multiple addresses to clients via DHCPv6 which raises
some questions. RFC 3315 is somehow unclear, how multiple addresses have
to be delivered to clients via DHCPv6. Section 22.4 states:

"...The Identity Association for Non-temporary Addresses option (IA_NA
option) is used to carry an IA_NA, the parameters associated with the
IA_NA, and the non-temporary addresses associated with the IA_NA....".

This lets assume that the server sends multiple address options in one
IA_NA. On the other hand section 17.1.1:

"...The client uses IA_NA options to request the assignment of
non-temporary addresses and uses IA_TA options to request the assignment
of temporary addresses...".

This lets assume that clients have to send IA_NA options for every
address they want to have. This is for another aspect a bad situation:
why should not the server decide which addresses a client deserves?

How do you interprete RFC 3315 at this point? How do servers and clients?=


We run a network with aproximately 500 IPv6 clients which get their
addresses via stateful DHCPv6. We use our self-written server
(http://dhcpy6d.ifw-dresden.de), what allowed us, to decide as in
section 22.4 and deliver several addresses in one IA_NA. This works well
with Windows 7+ clients, dhclient and dibbler-client.

Best regards
Henri Wahl


--=20
Henri Wahl

IT Department
Leibniz-Institut f=FCr Festk=F6rper- u.
Werkstoffforschung Dresden

tel: (03 51) 46 59 - 797
email: h.wahl@ifw-dresden.de
http://www.ifw-dresden.de

Nagios status monitor Nagstamon:
http://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d:
http://dhcpy6d.ifw-dresden.de

IFW Dresden e.V., Helmholtzstra=DFe 20, D-01069 Dresden
VR Dresden Nr. 1369
Vorstand: Prof. Dr. Ludwig Schultz, Dr. h.c. Dipl.-Finw. Rolf Pfrengle


--------------ms020303050408080604070204
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Kryptografische Unterschrift

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOYDCC
BCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVy
MSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBa
Fw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAw
DgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U
1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6
fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869
080UME/15eOkyGKbghoDJzANAmVgTe3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqD
oZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkh
nSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYwcAYDVR0fBGkwZzBloGOgYYZfaHR0cDov
L3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNy
bF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/
6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMA4GA1UdDwEB
/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0GCSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX
3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0ZMfYTK3S9vYCyufdnyTmieTvhERHua3iR
M347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0Ja6ba
hWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJ
hp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyH
xQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA9/IcMIIFFTCCA/2gAwIBAgIEDBQODDAN
BgkqhkiG9w0BAQUFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQMA4G
A1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTA4MDQwMzA4MDgzMFoXDTE5MDYzMDAwMDAwMFowgYcxCzAJBgNVBAYTAkRFMRAwDgYDVQQI
EwdTYWNoc2VuMRAwDgYDVQQHEwdEcmVzZGVuMRkwFwYDVQQKExBJRlcgRHJlc2RlbiBlLlYu
MRcwFQYDVQQDEw5JRlcgRHJlc2RlbiBDQTEgMB4GCSqGSIb3DQEJARYRY2FAaWZ3LWRyZXNk
ZW4uZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtaVHQKqI4m9r+SPwQinJK
OrXekndyD8KDeeND5GuwC5o9lSjKhtsV6IRYZL8m+e45XXMu8td3dzUn42CIt1FdYk9rRPwn
yOLWkrrLn2hzRUrDJlZYl5OfFbBgx3zMIWDx1lAt2ypUOKkIKpR7NqdlnDGO4XrZb7am5TjC
Pzqjyahlim/xfAcQKC47sVPA5uuSbURGhxQZ/W9CuP90ZCTuEOHsvV2EaP+EJv6Io6O4sMX9
oWtCtNvOQdLWeMgEius4uasBcZ1srhmhFyFK1OOnQJcic2OJ8+8XMbHGQURtI3BN2h1aYOtj
WeztmIoGyMEaUV5iV+sTCd46+qQvSDhDAgMBAAGjggGzMIIBrzASBgNVHRMBAf8ECDAGAQH/
AgEBMAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQULvMLHRbD7LdO9ZIlHsCPQEJxh/8wHwYDVR0j
BBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwHAYDVR0RBBUwE4ERY2FAaWZ3LWRyZXNkZW4u
ZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1y
b290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRl
L2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBH
BggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIv
Y2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUv
Z2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IB
AQDWzEgwolQCnshrwyViMVZkiwlYt6r0S/km/vRC9ZDi8paxJYu3Qe4MicYsDc27eb1V7rPB
1oKOgAGK1MUr6/yYp9y/ChTS9iabazUib+ox4pgERGnX7qcHeALqPKAWuyVhEQ3Wiqi32ZYm
2bn9e2Qe+0O4KcPcmyYJOs+TBSYJtNgdW2deYEclTtvybxMYhxOorB88qlPMdN9LTrK8S2kY
63Oeo2v6SkgFwHUv8c8J5Cilc5Wj6vPDSjGrn3Rc3d9XDKomq8iQNkW2XRNno+cc5CV3vBmH
ZUIHjktDVk498P/MbEYZsowo6eFnhnzrsmPiQBWu8JlF3OU/eKG/ebb7MIIFHjCCBAagAwIB
AgIEEcy5NTANBgkqhkiG9w0BAQUFADCBhzELMAkGA1UEBhMCREUxEDAOBgNVBAgTB1NhY2hz
ZW4xEDAOBgNVBAcTB0RyZXNkZW4xGTAXBgNVBAoTEElGVyBEcmVzZGVuIGUuVi4xFzAVBgNV
BAMTDklGVyBEcmVzZGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUBpZnctZHJlc2Rlbi5kZTAe
Fw0xMTA0MTkwNzM3MDlaFw0xNDA0MTgwNzM3MDlaMD0xCzAJBgNVBAYTAkRFMRkwFwYDVQQK
ExBJRlcgRHJlc2RlbiBlLlYuMRMwEQYDVQQDEwpIZW5yaSBXYWhsMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA5mGCzWbUMWYyM7SVAoS0VbbzOfpZ+Ae+s0t3+2RMdwU4RadM
ZVCUQzWiEkX1goBW87T/GmDbb7fXSf7WrUyFjZxAyrF5YiOZhNlcm0PvYsHF2GUiK29bqL9H
zKNWMuwtMGkjqAUFPpJPtpreuUXxT9Fi40Q11XByN45xV4BaNOG6/O7o4p516/uWf2DEj3Q/
TZYA1GdXmyxRHMMtMIvw5pMz6Tm6gHIOoP1dF2ty0mYk6ywcEXLq3o8ecWMZiJm9vhPWzfGn
6/2HDk72KjGzPKjCi1qCRHpZTs5VaCAIkpBGqBOk1QZYxWjLGmhzcc3MZgUcmfuoIsxR2m9g
AZB2IwIDAQABo4IB2TCCAdUwCQYDVR0TBAIwADALBgNVHQ8EBAMCBeAwKQYDVR0lBCIwIAYI
KwYBBQUHAwIGCCsGAQUFBwMEBgorBgEEAYI3FAICMB0GA1UdDgQWBBTRJ5bAf/hkK34SrM/z
/fsonOI3GDAfBgNVHSMEGDAWgBQu8wsdFsPst071kiUewI9AQnGH/zAgBgNVHREEGTAXgRVo
LndhaGxAaWZ3LWRyZXNkZW4uZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5w
Y2EuZGZuLmRlL2lmdy1kcmVzZGVuLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRw
Oi8vY2RwMi5wY2EuZGZuLmRlL2lmdy1kcmVzZGVuLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGi
BggrBgEFBQcBAQSBlTCBkjBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9p
ZnctZHJlc2Rlbi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6
Ly9jZHAyLnBjYS5kZm4uZGUvaWZ3LWRyZXNkZW4tY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0
MA0GCSqGSIb3DQEBBQUAA4IBAQArHA8FqV5hAppyrDhXi5rsEp21lBbNCniwzwasff+lyWNm
IiEvjAcMkSwXoIjxP2HM87SUFijO7J+g9tQY2W4yaIU/OX8FkorzDH1NcI3RWoCjdhddWlEJ
eM0R/2+AQbJaPXFtilFjjPFC4/a6XZMSUCvfxrQGbxMRj6czBVM2LkOwRi2FfAMBP3qO6fQ6
IQNnjq0UppqT3O3W2acG/KIQgor06RrYVhWrDCOejW/xFSE1JFu+Dko4wHBO4/NUllxYXabS
0TDuzuQzQnRmG+ymeg/I1Cpd0JRvzPXgO4H6uXROPfnWTqd1wbK4daDPtde2e/qPB8+r2D1g
ZBKt6nr+MYID0TCCA80CAQEwgZAwgYcxCzAJBgNVBAYTAkRFMRAwDgYDVQQIEwdTYWNoc2Vu
MRAwDgYDVQQHEwdEcmVzZGVuMRkwFwYDVQQKExBJRlcgRHJlc2RlbiBlLlYuMRcwFQYDVQQD
Ew5JRlcgRHJlc2RlbiBDQTEgMB4GCSqGSIb3DQEJARYRY2FAaWZ3LWRyZXNkZW4uZGUCBBHM
uTUwCQYFKw4DAhoFAKCCAhUwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B
CQUxDxcNMTMwMzIxMTU1MTI2WjAjBgkqhkiG9w0BCQQxFgQUO7Qwvu+T+xXbc6d+QdRbypoB
bf0wbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3
DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0D
AgIBKDCBoQYJKwYBBAGCNxAEMYGTMIGQMIGHMQswCQYDVQQGEwJERTEQMA4GA1UECBMHU2Fj
aHNlbjEQMA4GA1UEBxMHRHJlc2RlbjEZMBcGA1UEChMQSUZXIERyZXNkZW4gZS5WLjEXMBUG
A1UEAxMOSUZXIERyZXNkZW4gQ0ExIDAeBgkqhkiG9w0BCQEWEWNhQGlmdy1kcmVzZGVuLmRl
AgQRzLk1MIGjBgsqhkiG9w0BCRACCzGBk6CBkDCBhzELMAkGA1UEBhMCREUxEDAOBgNVBAgT
B1NhY2hzZW4xEDAOBgNVBAcTB0RyZXNkZW4xGTAXBgNVBAoTEElGVyBEcmVzZGVuIGUuVi4x
FzAVBgNVBAMTDklGVyBEcmVzZGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUBpZnctZHJlc2Rl
bi5kZQIEEcy5NTANBgkqhkiG9w0BAQEFAASCAQB1IzTfDc/Hqc1HLkP+Gx/bKI6Rj//ZtIuQ
ntPKKPuGARswghjZIDeNG3V/MGxTMCibEDZGPXTbQvLKb7050/bFMlz9K4kc7zkyNh7oiJzq
E8zroReIrdQ+1l77FqTQPN3RoSGyVAISmG08v8cNvKm6fXj4nTgAtl7FLXQxbpISZGWrogFa
9YcME4dSUdatlQLkFdFR0MV1v3T4zymh+MaFXvtZPfF2rK6OC7lUGZXwwWJUtiRBMAcaRLgH
2SO346YszTPKsekR+zxhpo7ktFzI37l8N45sMVVahTQ/527U6CmQ2uEqSLmnauMWTmXL4RUJ
TtY/cgHbBoo1gQQtDPMnAAAAAAAA
--------------ms020303050408080604070204--

From Carl.Wuyts@technicolor.com  Thu Mar 21 08:59:39 2013
Return-Path: <Carl.Wuyts@technicolor.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E500221F9063 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 08:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fjxf3soCSyGM for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 08:59:39 -0700 (PDT)
Received: from na3sys009aog124.obsmtp.com (na3sys009aog124.obsmtp.com [74.125.149.151]) by ietfa.amsl.com (Postfix) with ESMTP id B9B2321F9060 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 08:59:27 -0700 (PDT)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob124.postini.com ([74.125.148.12]) with SMTP ID DSNKUUsuXbkVbAUokfHyg4zf6XcKQksUSzu8@postini.com; Thu, 21 Mar 2013 08:59:39 PDT
Received: from MOPESMAILHC02.eu.thmulti.com (141.11.100.29) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.297.1; Thu, 21 Mar 2013 16:55:55 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.135]) by MOPESMAILHC02.eu.thmulti.com ([141.11.100.29]) with mapi; Thu, 21 Mar 2013 16:56:02 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Henri Wahl <h.wahl@ifw-dresden.de>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Thu, 21 Mar 2013 16:55:36 +0100
Thread-Topic: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address
Thread-Index: Ac4mS//NT7IF6XEfRnmYuiDe+7/35gAADcsw
Message-ID: <3135C2851EB6764BACEF35D8B495596806E51C4EA9@MOPESMBX01.eu.thmulti.com>
References: <514B2C7E.9000907@ifw-dresden.de>
In-Reply-To: <514B2C7E.9000907@ifw-dresden.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 15:59:40 -0000

If you need more IA_NA's, you just request the # you want, and the server s=
ends the option multiple times (as many as being served) into its return me=
ssages, so you'll see multiple entries of ia_na
E.g. The DHCPv6 client configuration on our CPEs allow to set a number of I=
A_NA requested.

Regs
Carl





-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of H=
enri Wahl
Sent: donderdag 21 maart 2013 16:51
To: dhcwg@ietf.org
Subject: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address

Hi all,

We want to deliver multiple addresses to clients via DHCPv6 which raises so=
me questions. RFC 3315 is somehow unclear, how multiple addresses have to b=
e delivered to clients via DHCPv6. Section 22.4 states:

"...The Identity Association for Non-temporary Addresses option (IA_NA
option) is used to carry an IA_NA, the parameters associated with the IA_NA=
, and the non-temporary addresses associated with the IA_NA....".

This lets assume that the server sends multiple address options in one IA_N=
A. On the other hand section 17.1.1:

"...The client uses IA_NA options to request the assignment of non-temporar=
y addresses and uses IA_TA options to request the assignment of temporary a=
ddresses...".

This lets assume that clients have to send IA_NA options for every address =
they want to have. This is for another aspect a bad situation:
why should not the server decide which addresses a client deserves?

How do you interprete RFC 3315 at this point? How do servers and clients?

We run a network with aproximately 500 IPv6 clients which get their address=
es via stateful DHCPv6. We use our self-written server (http://dhcpy6d.ifw-=
dresden.de), what allowed us, to decide as in section 22.4 and deliver seve=
ral addresses in one IA_NA. This works well with Windows 7+ clients, dhclie=
nt and dibbler-client.

Best regards
Henri Wahl


--
Henri Wahl

IT Department
Leibniz-Institut f=FCr Festk=F6rper- u.
Werkstoffforschung Dresden

tel: (03 51) 46 59 - 797
email: h.wahl@ifw-dresden.de
http://www.ifw-dresden.de

Nagios status monitor Nagstamon:
http://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d:
http://dhcpy6d.ifw-dresden.de

IFW Dresden e.V., Helmholtzstra=DFe 20, D-01069 Dresden VR Dresden Nr. 1369
Vorstand: Prof. Dr. Ludwig Schultz, Dr. h.c. Dipl.-Finw. Rolf Pfrengle


From tomasz.mrugalski@gmail.com  Thu Mar 21 09:59:09 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EB7E21F9172 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 09:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.667
X-Spam-Level: 
X-Spam-Status: No, score=-2.667 tagged_above=-999 required=5 tests=[AWL=0.933,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OkTA9ajBDAKo for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 09:59:08 -0700 (PDT)
Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) by ietfa.amsl.com (Postfix) with ESMTP id 520CB21F9174 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 09:59:08 -0700 (PDT)
Received: by mail-ee0-f50.google.com with SMTP id e51so1895756eek.23 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 09:59:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-tagtoolbar-keys:content-type :content-transfer-encoding; bh=yJr/TPHYK4aTIQh9cwmNZERdUm1x0QqAUY6Lpd8TiYs=; b=jpyu6CgwQfWc4zftd88YJFazSGHoQGt0q7y0uhOQBRcvF8p7rE2cHtat0qHAOem7MR gDqZwg/OFXhIDdb1yrhg1LthPxcjrQKK/ddUKXHwf/XieIQuFDHxlztORcAIUnctyIjI k9sDwQbrtgYmlw2DyLP+e4FDHjHwb4sefEi9aP5tKG73G8ObwcRSuxFkgFsGD21il7Os 6cJVC1/aw+3RpRFDM6PVkutMFQmvrUpTmY9r+gvDx8m5IEdaXXuFr7i2tQmtGPFp/QFM K+Pq19g+QhhhdEnRKvDJ8CaXgmJNMS/cHy5j7GBW/SD/iyCmjTnezns8xOo5oMkJkru1 REYw==
X-Received: by 10.15.22.197 with SMTP id f45mr83567585eeu.46.1363885147316; Thu, 21 Mar 2013 09:59:07 -0700 (PDT)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPS id h5sm9547568eem.1.2013.03.21.09.59.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Mar 2013 09:59:06 -0700 (PDT)
Message-ID: <514B3C55.7060207@gmail.com>
Date: Thu, 21 Mar 2013 17:59:01 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <514B2C7E.9000907@ifw-dresden.de>
In-Reply-To: <514B2C7E.9000907@ifw-dresden.de>
X-TagToolbar-Keys: D20130321175901381
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 16:59:09 -0000

On 21.03.2013 16:51, Henri Wahl wrote:
> Hi all,
> 
> We want to deliver multiple addresses to clients via DHCPv6 which raises
> some questions. RFC 3315 is somehow unclear, how multiple addresses have
> to be delivered to clients via DHCPv6. Section 22.4 states:
> 
> "...The Identity Association for Non-temporary Addresses option (IA_NA
> option) is used to carry an IA_NA, the parameters associated with the
> IA_NA, and the non-temporary addresses associated with the IA_NA....".
> 
> This lets assume that the server sends multiple address options in one
> IA_NA. On the other hand section 17.1.1:
> 
> "...The client uses IA_NA options to request the assignment of
> non-temporary addresses and uses IA_TA options to request the assignment
> of temporary addresses...".
> 
> This lets assume that clients have to send IA_NA options for every
> address they want to have. This is for another aspect a bad situation:
> why should not the server decide which addresses a client deserves?
> 
> How do you interprete RFC 3315 at this point? How do servers and clients?

You may also want to read section 11 of RFC3315. This particular piece
is interesting:
   "A server selects addresses to be assigned to an IA according to the
   address assignment policies determined by the server administrator"

Note the plural/singular form: [many] addresses to an [single] IA.

So technically speaking both "many addresses in a single IA_NA" and
"many IA_NAs, each with one address" are valid and how you assign them
is a matter of assignment policy. The question here is really about how
common those 2 approaches are. My understanding is that "many IA_NAs" is
much more popular and supported by many more implementations, so I'd
recommend doing that for better interoperability.

The problem with having multiple addresses assigned is usually a client
business, because it is a client that knows that more than one address
is needed, e.g. because some extra services will be provided. There is
no easy way for the client to communicate to the server that it wants
specific number of addresses in a given IA_NA. Dibbler client can send
multiple addresses and Dibbler server will understand and honor it, but
I have serious doubts other implementations will behave that way. One
reason I chose to implement this is that including an address is the
only way for the client to specify its preference for preferred and
valid lifetimes. Dibbler server tries to accept those hints if possible.

Perhaps this is something that could be clarified in stateful-issues
draft? If not, this is definitely another thing for 3315bis work.

Tomek


From otroan@employees.org  Thu Mar 21 10:11:34 2013
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C59B121F917A for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 10:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMLNoec9G1Lm for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 10:11:34 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id F16F421F9148 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 10:11:33 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANI+S1GQ/khN/2dsb2JhbAA6CcU+gV0WdIIkAQEEATo/BQsLDgouITYGE4gCAwkGuQkNiVuMSIEQgQYzB4JfYQOVBItMgXyFGoMLO4EuJA
X-IronPort-AV: E=Sophos;i="4.84,887,1355097600"; d="scan'208";a="81448101"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 21 Mar 2013 17:11:31 +0000
Received: from dhcp-10-61-104-228.cisco.com (dhcp-10-61-104-228.cisco.com [10.61.104.228]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2LHBVPi021216 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 21 Mar 2013 17:11:31 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <514B3C55.7060207@gmail.com>
Date: Thu, 21 Mar 2013 18:11:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D5E1858-8EDA-419B-8AF9-45203D7779F7@employees.org>
References: <514B2C7E.9000907@ifw-dresden.de> <514B3C55.7060207@gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 17:11:34 -0000

On Mar 21, 2013, at 17:59 , Tomek Mrugalski <tomasz.mrugalski@gmail.com> =
wrote:

> On 21.03.2013 16:51, Henri Wahl wrote:
>> Hi all,
>>=20
>> We want to deliver multiple addresses to clients via DHCPv6 which =
raises
>> some questions. RFC 3315 is somehow unclear, how multiple addresses =
have
>> to be delivered to clients via DHCPv6. Section 22.4 states:
>>=20
>> "...The Identity Association for Non-temporary Addresses option =
(IA_NA
>> option) is used to carry an IA_NA, the parameters associated with the
>> IA_NA, and the non-temporary addresses associated with the =
IA_NA....".
>>=20
>> This lets assume that the server sends multiple address options in =
one
>> IA_NA. On the other hand section 17.1.1:
>>=20
>> "...The client uses IA_NA options to request the assignment of
>> non-temporary addresses and uses IA_TA options to request the =
assignment
>> of temporary addresses...".
>>=20
>> This lets assume that clients have to send IA_NA options for every
>> address they want to have. This is for another aspect a bad =
situation:
>> why should not the server decide which addresses a client deserves?
>>=20
>> How do you interprete RFC 3315 at this point? How do servers and =
clients?
>=20
> You may also want to read section 11 of RFC3315. This particular piece
> is interesting:
>   "A server selects addresses to be assigned to an IA according to the
>   address assignment policies determined by the server administrator"
>=20
> Note the plural/singular form: [many] addresses to an [single] IA.
>=20
> So technically speaking both "many addresses in a single IA_NA" and
> "many IA_NAs, each with one address" are valid and how you assign them
> is a matter of assignment policy. The question here is really about =
how
> common those 2 approaches are. My understanding is that "many IA_NAs" =
is
> much more popular and supported by many more implementations, so I'd
> recommend doing that for better interoperability.
>=20
> The problem with having multiple addresses assigned is usually a =
client
> business, because it is a client that knows that more than one address
> is needed, e.g. because some extra services will be provided. There is
> no easy way for the client to communicate to the server that it wants
> specific number of addresses in a given IA_NA. Dibbler client can send
> multiple addresses and Dibbler server will understand and honor it, =
but
> I have serious doubts other implementations will behave that way. One
> reason I chose to implement this is that including an address is the
> only way for the client to specify its preference for preferred and
> valid lifetimes. Dibbler server tries to accept those hints if =
possible.
>=20
> Perhaps this is something that could be clarified in stateful-issues
> draft? If not, this is definitely another thing for 3315bis work.

agree.
in RFC3633 multiple IA_PDs versus multiple IAPrefixes inside one IA_PD =
are very different things.

the example given in both 3315 and 3633 for multiple IAIDs are the one =
where a client requests an
address or prefix for a different interface.

cheers,
Ole=

From volz@cisco.com  Thu Mar 21 10:59:33 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 099A221F906A for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 10:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level: 
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WSEb0xI8ffDM for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 10:59:32 -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 2D49D21F907E for <dhcwg@ietf.org>; Thu, 21 Mar 2013 10:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3391; q=dns/txt; s=iport; t=1363888772; x=1365098372; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=QEzIkc9hQiM40ZsI2BPEqLgD493inhcWTbq3GBbyrRE=; b=kfbpW5PHKFDC8Cw/FoZu1+cjceaaz/rsln9w/FNeqLHdLILvZtZgfAFW LH/JBJIbLhx9nwAtw5yjWOUFPwjSoa2xSNoZhP4Zt1v6THndfKBc9pTbE BjTFT+CeZzk6M/ylD4oAiFf/JusDm2tjnz2vOsuv+y6wF7ZHn6sVFp5uZ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFANVJS1GtJV2c/2dsb2JhbAA6CcVAgVwWdIIkAQEBAwEBAQE3NAsFCwIBCA4KHhAhBgslAgQOBYgCAwkGDLh9DYlXBIxIgRCBBjMHgl9hA5UEgWCJbIF8hRqDCoFqJA
X-IronPort-AV: E=Sophos;i="4.84,887,1355097600"; d="scan'208";a="190076855"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP; 21 Mar 2013 17:59:30 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r2LHxUs9032181 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Mar 2013 17:59:30 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Thu, 21 Mar 2013 12:59:30 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address
Thread-Index: AQHOJlVusO8YCw3oLECM4bu4YQQDkpiwbv84
Date: Thu, 21 Mar 2013 17:59:29 +0000
Message-ID: <2D6695B2-5AA6-4E80-B0F8-E4F5F936EAA5@cisco.com>
References: <514B2C7E.9000907@ifw-dresden.de>,<514B3C55.7060207@gmail.com>
In-Reply-To: <514B3C55.7060207@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per	address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 17:59:33 -0000

There are two things here - one is server policy which allows the server to=
 deliver 0 to n addresses (or prefixes). The other is the client's policy w=
hich might want more than one.

I think a client has two choices - send multiple IA_* options with unique I=
AID values in the request or send one and if it needs more, send separate r=
equests.

- Bernie

On Mar 21, 2013, at 12:59 PM, "Tomek Mrugalski" <tomasz.mrugalski@gmail.com=
> wrote:

> On 21.03.2013 16:51, Henri Wahl wrote:
>> Hi all,
>>=20
>> We want to deliver multiple addresses to clients via DHCPv6 which raises
>> some questions. RFC 3315 is somehow unclear, how multiple addresses have
>> to be delivered to clients via DHCPv6. Section 22.4 states:
>>=20
>> "...The Identity Association for Non-temporary Addresses option (IA_NA
>> option) is used to carry an IA_NA, the parameters associated with the
>> IA_NA, and the non-temporary addresses associated with the IA_NA....".
>>=20
>> This lets assume that the server sends multiple address options in one
>> IA_NA. On the other hand section 17.1.1:
>>=20
>> "...The client uses IA_NA options to request the assignment of
>> non-temporary addresses and uses IA_TA options to request the assignment
>> of temporary addresses...".
>>=20
>> This lets assume that clients have to send IA_NA options for every
>> address they want to have. This is for another aspect a bad situation:
>> why should not the server decide which addresses a client deserves?
>>=20
>> How do you interprete RFC 3315 at this point? How do servers and clients=
?
>=20
> You may also want to read section 11 of RFC3315. This particular piece
> is interesting:
>   "A server selects addresses to be assigned to an IA according to the
>   address assignment policies determined by the server administrator"
>=20
> Note the plural/singular form: [many] addresses to an [single] IA.
>=20
> So technically speaking both "many addresses in a single IA_NA" and
> "many IA_NAs, each with one address" are valid and how you assign them
> is a matter of assignment policy. The question here is really about how
> common those 2 approaches are. My understanding is that "many IA_NAs" is
> much more popular and supported by many more implementations, so I'd
> recommend doing that for better interoperability.
>=20
> The problem with having multiple addresses assigned is usually a client
> business, because it is a client that knows that more than one address
> is needed, e.g. because some extra services will be provided. There is
> no easy way for the client to communicate to the server that it wants
> specific number of addresses in a given IA_NA. Dibbler client can send
> multiple addresses and Dibbler server will understand and honor it, but
> I have serious doubts other implementations will behave that way. One
> reason I chose to implement this is that including an address is the
> only way for the client to specify its preference for preferred and
> valid lifetimes. Dibbler server tries to accept those hints if possible.
>=20
> Perhaps this is something that could be clarified in stateful-issues
> draft? If not, this is definitely another thing for 3315bis work.
>=20
> Tomek
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

From alexandru.petrescu@gmail.com  Thu Mar 21 11:25:06 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1196721F8FE9 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.175
X-Spam-Level: 
X-Spam-Status: No, score=-10.175 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03ZQj9DbWLfv for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 11:25:00 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 241B921F90AC for <dhcwg@ietf.org>; Thu, 21 Mar 2013 11:24:57 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2LIOvCU012646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Thu, 21 Mar 2013 19:24:57 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2LIOuNV027778 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 19:24:57 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2LIOqPW024124 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 19:24:56 +0100
Message-ID: <514B5049.4010106@gmail.com>
Date: Thu, 21 Mar 2013 19:24:09 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <511B85B3.8030705@gmail.com> <5140C2EB.6060707@trans-nt.com> <F63EE2C4-693E-4DEF-ABCD-41020AD3821F@cisco.com> <5140D539.4060408@trans-nt.com> <848988B6-4DAC-4FEB-94FC-5B45E345E95E@cisco.com> <5141E286.6050305@trans-nt.com> <CAAedzxrVPKYhr=u2xcSx-wTUdQBpTcVbt1UVCmJraUPVRx_Vyg@mail.gmail.com> <51427396.1060803@gmail.com> <51456E7D.1030600@necom830.hpcl.titech.ac.jp> <CAAedzxrzkbedeT_jsteYhei-xS6JN9ko_-kpeThJW_be8JzAjQ@mail.gmail.com> <5145EC8D.3020502@gmail.com> <CAAedzxoeAfCtn8gV5rBd_2uYRCJYj5Kr5Wx2N0vvec6roE_EhQ@mail.gmail.com> <51477117.8090702@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63077511326B@mbx-01.win.nominum.com> <5149AEF9.3050309@trans-nt.com> <5149B2B5.3020202@gmail.com> <514B0FB8.9070502@trans-nt.com>
In-Reply-To: <514B0FB8.9070502@trans-nt.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] IEEE 802.11ai and DHCPv6-and-Routes-Routers-to-Client
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 18:25:06 -0000

Le 21/03/2013 14:48, Hiroki Nakano a écrit :
> (13/03/20 21:59), Alexandru Petrescu wrote:
>>> I'm participating in the discussion at Caribe Royale. We are
>>> making effort to have a conclusion in this week. If TGai decides
>>> to provide a generic container framework which can be used to
>>> transfer DHCP messages,
>>
>> To transfer DHCP messages?  Or to transfer parameters which are
>> usually configured by DHCPv6 and by
>> Stateless-Address-Auto-configuration?
>
> My position is that generic container should be defined to transfer
> packets of upper layers such as DHCPv4, RS/RA, DHCPv6 etc.

I can understand that position to which I could agree.

>> Do you mean a typical Ethernet frame which would carry a DHCPv6
>> message with EtherType 0x86DD?
>
> Yes.

Makes sense to me.

> The newest proposal is at the URL below.
> https://mentor.ieee.org/802.11/dcn/13/11-13-0235-02-00ai-ip-address-setup.doc

Thank
>
you for providing the link and thanks IEEE for making public
ongoing working documents.

But, this proposal seems to put the IPv6 Gateway address and the MAC
address of the IPv6 Gateway into MAC messages, and not IP messages.

For example on page 12, Figure 8.4.2.ai2.ai3-1 and figure below it.

I may be ignorant about how IEEE specifications are expressed - sorry if
I misunderstand.

> We finally have merged two proposals and implementors can choose
> them.

Do you mean there are two different proposals in the same document?

May I ask you - with respect to the assignment of the IPv6 Gateway
address, and its MAC address: are there two different methods, in this
document, about assigning these parameters to a Client?

Is any of the described methods likely to considering IPv6 Router
Advertisements ('RA') to configure these two parameters?  Is any of the
described methods likely to be considering DHCPv6 to configure these two
parameters?

> And this framework has been approved by TGai yesterday.

I read this as good news and I am happy for the group.

> IEEE 802.11ai is just A link layer. Therefore, how to use 802.11ai
> should be discussed by people of upper layers and it is none of
> business of TGai itself.

Ok.

> On the other hand, TGai has its own use cases and the principle. As
> Tomek pointed out before, speed is of essence of TGai. Imagine that
> you go through in front of an AP by car. You have only 10 seconds.
> It's only for 10 seconds you can communicate with the AP!  You never
> want to waste even one round trip of packets.

Ok, I can understand that.  For vehicle communication the situation may
be that way, and even a bit more complicated.  In a vehicle there may be
a need of more than just one IPv6 address - maybe an entire prefix is
needed within the vehicle, in addition to the address for the egress
interface of the Router in the vehicle.  At that point maybe DHCPv6
PRefix Delegation is needed (in addition to just DHCPv6 for address, or
just RA for address and default route).

> Accommodating numerous STA is the other aspect of TGai. Assume that
> an AP is installed at Tokyo station. 1000 people per minute are
> passing beside the AP. They all perform 802.11 association process
> and IP layer configuration process such as DHCP. All of piled
> protocols should be required to be as efficient as possible for such
> environments.

Efficiency is a good requirement.

I dont know how many STAs are supported with IPv6 and RA on a single
WiFi Access Point... all communicating simultaneously.

I could guess that the WiFi situation could be improved if more than one
Access Point were deployed, with some channel number selection.

I could guess that numerous periodic beacons IPv6 RAs may be too much
aditional noise that could be avoided if DHCP were used (DHCP doesn't
beacon periodic advertisements).

> I hope to share these principles with IETF people widely and discuss
> the whole protocol stack from the link layer to application layers.
> Some people already have the understanding and I'm so happy:)

Ok - the details you presented until now are interesting to me.  I think
there may be other people interested.

I can explain why I am interested.

I am working on a method to use DHCPv6 to communicate Default Routers to
Clients.  This is also for efficiency reasons, but not quite the
scenario you describe.

I consider an LTE Machine-class device which is constrained in terms of
power consumption, memory size, clock speed.  This connects to LTE but
also offers WiFi to a group of other devices deployed in a vehicle.  One
would like this to be quickly configured.

But the full set of configuration parameters is IPv6 address, IPv6
Default Router, maybe DNS Resolvers address, maybe MAC address and IPv6
Delegated Prefix (this is not the prefix of that IPv6 address).  To
configure all these one may need to  use both DHCPv6 and ND.

It's practically impossible today to do all in one shot
Request-Response.  One can do e.g. Neighbour Discovery (or SLAAC) to
configure the address and the default route but must do DHCPv6 to
delegate the prefix.  This is too many messages.

If DHCPv6 could do Default Router then a single message exchange would
be sufficient.

If RA could do Prefix Delegation, then also a single message exchange
would be sufficient.

That said, a few other people expressed interest in using DHCPv6 to
communicate routes to Clients.  And to communicate maybe src-based
routes to Clients.

However, the situation right now is that we dont know where to discuss
these aspects of DHCPv6 and route to Client options.

I believe the 802.11ai aspects are ok to discuss here - the Chair has
allowed this discussion although I doubt it's in the DHC Charter (I have
to read).

All in all - this is why I am interested in 802.11ai.

Yours,

Alex


Alex

>
> P.S. An interesting report is below.
> https://mentor.ieee.org/802.11/dcn/13/11-13-0323-02-00ai-tgai-experimental-test-report-of-fils.pptx
>
>
Check it out.
> If you can not play video in ppt, you can see at
> http://www.youtube.com/watch?v=xOKaVOPWXTU I'm also in this video.
> hehe:)
>
> Regards,
>
> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From h.wahl@ifw-dresden.de  Thu Mar 21 14:01:04 2013
Return-Path: <h.wahl@ifw-dresden.de>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34FF321F8CD1 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 14:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level: 
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, HELO_EQ_DE=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1BFux8GsO5fY for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 14:01:02 -0700 (PDT)
Received: from mailout06.t-online.de (mailout06.t-online.de [194.25.134.19]) by ietfa.amsl.com (Postfix) with ESMTP id B033421F8CCB for <dhcwg@ietf.org>; Thu, 21 Mar 2013 14:01:01 -0700 (PDT)
Received: from fwd17.aul.t-online.de (fwd17.aul.t-online.de ) by mailout06.t-online.de with smtp  id 1UImbc-0003LS-4p; Thu, 21 Mar 2013 22:01:00 +0100
Received: from sparky2.oldnickern (SaAYnoZXwhAs4ZomGis714Gga-cbafaetgFFwfQ-yHdCVXr0Nne0eHSXgGeQMvFw7A@[87.157.36.129]) by fwd17.aul.t-online.de with esmtp id 1UImbb-28XZY00; Thu, 21 Mar 2013 22:00:59 +0100
Received: from smtp.oldnickern (intern [IPv6:fd00::1:0:0:3]) by sparky2.oldnickern (Postfix) with ESMTP id CF72CC0366; Thu, 21 Mar 2013 22:00:58 +0100 (CET)
Received: from w73lx-wahl-nb.ifw-dresden.de (w73lx-wahl-nb-wlan.oldnickern [192.168.0.143]) by smtp.oldnickern (Postfix) with ESMTP id 5515520A18; Thu, 21 Mar 2013 22:00:58 +0100 (CET)
Message-ID: <514B7509.4010405@ifw-dresden.de>
Date: Thu, 21 Mar 2013 22:00:57 +0100
From: Henri Wahl <h.wahl@ifw-dresden.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
References: <514B2C7E.9000907@ifw-dresden.de> <514B3C55.7060207@gmail.com>
In-Reply-To: <514B3C55.7060207@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030808090800080907020503"
X-ID: SaAYnoZXwhAs4ZomGis714Gga-cbafaetgFFwfQ-yHdCVXr0Nne0eHSXgGeQMvFw7A@t-dialin.net
X-TOI-MSGID: bd4e6b9b-6e2b-4201-bf18-b9aedff8aa9e
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 21:01:04 -0000

Dies ist eine kryptografisch unterzeichnete Nachricht im MIME-Format.

--------------ms030808090800080907020503
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


> You may also want to read section 11 of RFC3315. This particular piece
> is interesting:
>    "A server selects addresses to be assigned to an IA according to the=

>    address assignment policies determined by the server administrator"
>
> Note the plural/singular form: [many] addresses to an [single] IA.

Sorry I missed that - so even in RFC 3315 both ways are OK.
>
> So technically speaking both "many addresses in a single IA_NA" and
> "many IA_NAs, each with one address" are valid and how you assign them
> is a matter of assignment policy. The question here is really about how=

> common those 2 approaches are. My understanding is that "many IA_NAs" i=
s
> much more popular and supported by many more implementations, so I'd
> recommend doing that for better interoperability.
>
> The problem with having multiple addresses assigned is usually a client=

> business, because it is a client that knows that more than one address
> is needed, e.g. because some extra services will be provided.=20
Depends... on the clients' role in the network. If it has no right to
chose at all and gets all its configuration from server the
one-IA_NA-to-rule-them-all-approach is OK. Wouldn't this be normally the
case if you use stateful DHCPv6 instead of SLAAC ?
> There is
> no easy way for the client to communicate to the server that it wants
> specific number of addresses in a given IA_NA.=20
Agree.
> Dibbler client can send
> multiple addresses and Dibbler server will understand and honor it, but=

> I have serious doubts other implementations will behave that way. One
> reason I chose to implement this is that including an address is the
> only way for the client to specify its preference for preferred and
> valid lifetimes. Dibbler server tries to accept those hints if possible=
=2E
>
> Perhaps this is something that could be clarified in stateful-issues
> draft? If not, this is definitely another thing for 3315bis work.
Regards

--=20
Henri Wahl

IT Department
Leibniz-Institut f=FCr Festk=F6rper- u.
Werkstoffforschung Dresden

tel: (03 51) 46 59 - 797
email: h.wahl@ifw-dresden.de
http://www.ifw-dresden.de

Nagios status monitor Nagstamon:
http://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d:
http://dhcpy6d.ifw-dresden.de

IFW Dresden e.V., Helmholtzstra=DFe 20, D-01069 Dresden
VR Dresden Nr. 1369
Vorstand: Prof. Dr. Ludwig Schultz, Dr. h.c. Rolf Pfrengle




--------------ms030808090800080907020503
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Kryptografische Unterschrift

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOYDCC
BCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVy
MSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBa
Fw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAw
DgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U
1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6
fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869
080UME/15eOkyGKbghoDJzANAmVgTe3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqD
oZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkh
nSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYwcAYDVR0fBGkwZzBloGOgYYZfaHR0cDov
L3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNy
bF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/
6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMA4GA1UdDwEB
/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0GCSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX
3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0ZMfYTK3S9vYCyufdnyTmieTvhERHua3iR
M347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0Ja6ba
hWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJ
hp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyH
xQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA9/IcMIIFFTCCA/2gAwIBAgIEDBQODDAN
BgkqhkiG9w0BAQUFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQMA4G
A1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTA4MDQwMzA4MDgzMFoXDTE5MDYzMDAwMDAwMFowgYcxCzAJBgNVBAYTAkRFMRAwDgYDVQQI
EwdTYWNoc2VuMRAwDgYDVQQHEwdEcmVzZGVuMRkwFwYDVQQKExBJRlcgRHJlc2RlbiBlLlYu
MRcwFQYDVQQDEw5JRlcgRHJlc2RlbiBDQTEgMB4GCSqGSIb3DQEJARYRY2FAaWZ3LWRyZXNk
ZW4uZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtaVHQKqI4m9r+SPwQinJK
OrXekndyD8KDeeND5GuwC5o9lSjKhtsV6IRYZL8m+e45XXMu8td3dzUn42CIt1FdYk9rRPwn
yOLWkrrLn2hzRUrDJlZYl5OfFbBgx3zMIWDx1lAt2ypUOKkIKpR7NqdlnDGO4XrZb7am5TjC
Pzqjyahlim/xfAcQKC47sVPA5uuSbURGhxQZ/W9CuP90ZCTuEOHsvV2EaP+EJv6Io6O4sMX9
oWtCtNvOQdLWeMgEius4uasBcZ1srhmhFyFK1OOnQJcic2OJ8+8XMbHGQURtI3BN2h1aYOtj
WeztmIoGyMEaUV5iV+sTCd46+qQvSDhDAgMBAAGjggGzMIIBrzASBgNVHRMBAf8ECDAGAQH/
AgEBMAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQULvMLHRbD7LdO9ZIlHsCPQEJxh/8wHwYDVR0j
BBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwHAYDVR0RBBUwE4ERY2FAaWZ3LWRyZXNkZW4u
ZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1y
b290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRl
L2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBH
BggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIv
Y2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUv
Z2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IB
AQDWzEgwolQCnshrwyViMVZkiwlYt6r0S/km/vRC9ZDi8paxJYu3Qe4MicYsDc27eb1V7rPB
1oKOgAGK1MUr6/yYp9y/ChTS9iabazUib+ox4pgERGnX7qcHeALqPKAWuyVhEQ3Wiqi32ZYm
2bn9e2Qe+0O4KcPcmyYJOs+TBSYJtNgdW2deYEclTtvybxMYhxOorB88qlPMdN9LTrK8S2kY
63Oeo2v6SkgFwHUv8c8J5Cilc5Wj6vPDSjGrn3Rc3d9XDKomq8iQNkW2XRNno+cc5CV3vBmH
ZUIHjktDVk498P/MbEYZsowo6eFnhnzrsmPiQBWu8JlF3OU/eKG/ebb7MIIFHjCCBAagAwIB
AgIEEcy5NTANBgkqhkiG9w0BAQUFADCBhzELMAkGA1UEBhMCREUxEDAOBgNVBAgTB1NhY2hz
ZW4xEDAOBgNVBAcTB0RyZXNkZW4xGTAXBgNVBAoTEElGVyBEcmVzZGVuIGUuVi4xFzAVBgNV
BAMTDklGVyBEcmVzZGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUBpZnctZHJlc2Rlbi5kZTAe
Fw0xMTA0MTkwNzM3MDlaFw0xNDA0MTgwNzM3MDlaMD0xCzAJBgNVBAYTAkRFMRkwFwYDVQQK
ExBJRlcgRHJlc2RlbiBlLlYuMRMwEQYDVQQDEwpIZW5yaSBXYWhsMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA5mGCzWbUMWYyM7SVAoS0VbbzOfpZ+Ae+s0t3+2RMdwU4RadM
ZVCUQzWiEkX1goBW87T/GmDbb7fXSf7WrUyFjZxAyrF5YiOZhNlcm0PvYsHF2GUiK29bqL9H
zKNWMuwtMGkjqAUFPpJPtpreuUXxT9Fi40Q11XByN45xV4BaNOG6/O7o4p516/uWf2DEj3Q/
TZYA1GdXmyxRHMMtMIvw5pMz6Tm6gHIOoP1dF2ty0mYk6ywcEXLq3o8ecWMZiJm9vhPWzfGn
6/2HDk72KjGzPKjCi1qCRHpZTs5VaCAIkpBGqBOk1QZYxWjLGmhzcc3MZgUcmfuoIsxR2m9g
AZB2IwIDAQABo4IB2TCCAdUwCQYDVR0TBAIwADALBgNVHQ8EBAMCBeAwKQYDVR0lBCIwIAYI
KwYBBQUHAwIGCCsGAQUFBwMEBgorBgEEAYI3FAICMB0GA1UdDgQWBBTRJ5bAf/hkK34SrM/z
/fsonOI3GDAfBgNVHSMEGDAWgBQu8wsdFsPst071kiUewI9AQnGH/zAgBgNVHREEGTAXgRVo
LndhaGxAaWZ3LWRyZXNkZW4uZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5w
Y2EuZGZuLmRlL2lmdy1kcmVzZGVuLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRw
Oi8vY2RwMi5wY2EuZGZuLmRlL2lmdy1kcmVzZGVuLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGi
BggrBgEFBQcBAQSBlTCBkjBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9p
ZnctZHJlc2Rlbi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6
Ly9jZHAyLnBjYS5kZm4uZGUvaWZ3LWRyZXNkZW4tY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0
MA0GCSqGSIb3DQEBBQUAA4IBAQArHA8FqV5hAppyrDhXi5rsEp21lBbNCniwzwasff+lyWNm
IiEvjAcMkSwXoIjxP2HM87SUFijO7J+g9tQY2W4yaIU/OX8FkorzDH1NcI3RWoCjdhddWlEJ
eM0R/2+AQbJaPXFtilFjjPFC4/a6XZMSUCvfxrQGbxMRj6czBVM2LkOwRi2FfAMBP3qO6fQ6
IQNnjq0UppqT3O3W2acG/KIQgor06RrYVhWrDCOejW/xFSE1JFu+Dko4wHBO4/NUllxYXabS
0TDuzuQzQnRmG+ymeg/I1Cpd0JRvzPXgO4H6uXROPfnWTqd1wbK4daDPtde2e/qPB8+r2D1g
ZBKt6nr+MYID0TCCA80CAQEwgZAwgYcxCzAJBgNVBAYTAkRFMRAwDgYDVQQIEwdTYWNoc2Vu
MRAwDgYDVQQHEwdEcmVzZGVuMRkwFwYDVQQKExBJRlcgRHJlc2RlbiBlLlYuMRcwFQYDVQQD
Ew5JRlcgRHJlc2RlbiBDQTEgMB4GCSqGSIb3DQEJARYRY2FAaWZ3LWRyZXNkZW4uZGUCBBHM
uTUwCQYFKw4DAhoFAKCCAhUwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B
CQUxDxcNMTMwMzIxMjEwMDU3WjAjBgkqhkiG9w0BCQQxFgQUbqpMjLYE4aCaddrTu54E/N0r
igEwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3
DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0D
AgIBKDCBoQYJKwYBBAGCNxAEMYGTMIGQMIGHMQswCQYDVQQGEwJERTEQMA4GA1UECBMHU2Fj
aHNlbjEQMA4GA1UEBxMHRHJlc2RlbjEZMBcGA1UEChMQSUZXIERyZXNkZW4gZS5WLjEXMBUG
A1UEAxMOSUZXIERyZXNkZW4gQ0ExIDAeBgkqhkiG9w0BCQEWEWNhQGlmdy1kcmVzZGVuLmRl
AgQRzLk1MIGjBgsqhkiG9w0BCRACCzGBk6CBkDCBhzELMAkGA1UEBhMCREUxEDAOBgNVBAgT
B1NhY2hzZW4xEDAOBgNVBAcTB0RyZXNkZW4xGTAXBgNVBAoTEElGVyBEcmVzZGVuIGUuVi4x
FzAVBgNVBAMTDklGVyBEcmVzZGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUBpZnctZHJlc2Rl
bi5kZQIEEcy5NTANBgkqhkiG9w0BAQEFAASCAQCw/L7CaPQnn0X3SC7B42nFF5kTXvQ1ihZ/
1hFOrVQaE05L94ozBSwhuHqJRmLr4gJVs/5QVTpgsQB8mBLP95bElq4MrYhqY29WTQXViA9x
9GFkdH2UiJ1utiC1YYW9Jk8EKOdboSV+HzP13KZzZNVvR6lKH6alGJCkLcONIrgpqJrH3V+V
VJP2yXShjKOOwG4jOpkS7pyHiIh41bi3B05mRMwYst7PrUhhvKpROAyCdI7ZLidV457pcZE1
+tSIyWHwobtuRA2FrHiuoNWfAOEE/qOFzMnji+y5Uh1i64XiQb1Tf5FVY7ADIQXQmoPR71Qx
8XT7oLAyNogH0xJDn44ZAAAAAAAA
--------------ms030808090800080907020503--

From h.wahl@ifw-dresden.de  Thu Mar 21 14:02:34 2013
Return-Path: <h.wahl@ifw-dresden.de>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 873D621F86EC for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 14:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level: 
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_00=-2.599, HELO_EQ_DE=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0DE5+w9pyDak for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 14:02:34 -0700 (PDT)
Received: from mailout02.t-online.de (mailout02.t-online.de [194.25.134.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8043D21F8629 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 14:02:33 -0700 (PDT)
Received: from fwd02.aul.t-online.de (fwd02.aul.t-online.de ) by mailout02.t-online.de with smtp  id 1UImd6-0004hp-33; Thu, 21 Mar 2013 22:02:32 +0100
Received: from sparky2.oldnickern (ECv4jUZfwhCb-gijW3e--JqIkdAgeL6Ryhjz0peGNuUzsCjjFbXP79PZei2-vwrQdf@[87.157.36.129]) by fwd02.aul.t-online.de with esmtp id 1UImd3-3WR9jk0; Thu, 21 Mar 2013 22:02:29 +0100
Received: from smtp.oldnickern (intern [IPv6:fd00::1:0:0:3]) by sparky2.oldnickern (Postfix) with ESMTP id D73ABC0366; Thu, 21 Mar 2013 22:02:28 +0100 (CET)
Received: from w73lx-wahl-nb.ifw-dresden.de (w73lx-wahl-nb-wlan.oldnickern [192.168.0.143]) by smtp.oldnickern (Postfix) with ESMTP id 6DC3A20A18; Thu, 21 Mar 2013 22:02:28 +0100 (CET)
Message-ID: <514B7563.4040408@ifw-dresden.de>
Date: Thu, 21 Mar 2013 22:02:27 +0100
From: Henri Wahl <h.wahl@ifw-dresden.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
References: <514B2C7E.9000907@ifw-dresden.de>, <514B3C55.7060207@gmail.com> <2D6695B2-5AA6-4E80-B0F8-E4F5F936EAA5@cisco.com>
In-Reply-To: <2D6695B2-5AA6-4E80-B0F8-E4F5F936EAA5@cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080209020109000300080908"
X-ID: ECv4jUZfwhCb-gijW3e--JqIkdAgeL6Ryhjz0peGNuUzsCjjFbXP79PZei2-vwrQdf@t-dialin.net
X-TOI-MSGID: 2ad51ce1-87a0-4e0c-bc52-4720880f01c0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per	address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 21:02:34 -0000

Dies ist eine kryptografisch unterzeichnete Nachricht im MIME-Format.

--------------ms080209020109000300080908
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


> There are two things here - one is server policy which allows the serve=
r to deliver 0 to n addresses (or prefixes). The other is the client's po=
licy which might want more than one.
>
> I think a client has two choices - send multiple IA_* options with uniq=
ue IAID values in the request or send one and if it needs more, send sepa=
rate requests.
>
With different IAIDs or the same in every request?

--=20
Henri Wahl

IT Department
Leibniz-Institut f=FCr Festk=F6rper- u.
Werkstoffforschung Dresden

tel: (03 51) 46 59 - 797
email: h.wahl@ifw-dresden.de
http://www.ifw-dresden.de

Nagios status monitor Nagstamon:
http://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d:
http://dhcpy6d.ifw-dresden.de

IFW Dresden e.V., Helmholtzstra=DFe 20, D-01069 Dresden
VR Dresden Nr. 1369
Vorstand: Prof. Dr. Ludwig Schultz, Dr. h.c. Rolf Pfrengle




--------------ms080209020109000300080908
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Kryptografische Unterschrift

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOYDCC
BCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVy
MSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBa
Fw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAw
DgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U
1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6
fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869
080UME/15eOkyGKbghoDJzANAmVgTe3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqD
oZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkh
nSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYwcAYDVR0fBGkwZzBloGOgYYZfaHR0cDov
L3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNy
bF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/
6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMA4GA1UdDwEB
/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0GCSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX
3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0ZMfYTK3S9vYCyufdnyTmieTvhERHua3iR
M347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0Ja6ba
hWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJ
hp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyH
xQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA9/IcMIIFFTCCA/2gAwIBAgIEDBQODDAN
BgkqhkiG9w0BAQUFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQMA4G
A1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTA4MDQwMzA4MDgzMFoXDTE5MDYzMDAwMDAwMFowgYcxCzAJBgNVBAYTAkRFMRAwDgYDVQQI
EwdTYWNoc2VuMRAwDgYDVQQHEwdEcmVzZGVuMRkwFwYDVQQKExBJRlcgRHJlc2RlbiBlLlYu
MRcwFQYDVQQDEw5JRlcgRHJlc2RlbiBDQTEgMB4GCSqGSIb3DQEJARYRY2FAaWZ3LWRyZXNk
ZW4uZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtaVHQKqI4m9r+SPwQinJK
OrXekndyD8KDeeND5GuwC5o9lSjKhtsV6IRYZL8m+e45XXMu8td3dzUn42CIt1FdYk9rRPwn
yOLWkrrLn2hzRUrDJlZYl5OfFbBgx3zMIWDx1lAt2ypUOKkIKpR7NqdlnDGO4XrZb7am5TjC
Pzqjyahlim/xfAcQKC47sVPA5uuSbURGhxQZ/W9CuP90ZCTuEOHsvV2EaP+EJv6Io6O4sMX9
oWtCtNvOQdLWeMgEius4uasBcZ1srhmhFyFK1OOnQJcic2OJ8+8XMbHGQURtI3BN2h1aYOtj
WeztmIoGyMEaUV5iV+sTCd46+qQvSDhDAgMBAAGjggGzMIIBrzASBgNVHRMBAf8ECDAGAQH/
AgEBMAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQULvMLHRbD7LdO9ZIlHsCPQEJxh/8wHwYDVR0j
BBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwHAYDVR0RBBUwE4ERY2FAaWZ3LWRyZXNkZW4u
ZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1y
b290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRl
L2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBH
BggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIv
Y2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUv
Z2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IB
AQDWzEgwolQCnshrwyViMVZkiwlYt6r0S/km/vRC9ZDi8paxJYu3Qe4MicYsDc27eb1V7rPB
1oKOgAGK1MUr6/yYp9y/ChTS9iabazUib+ox4pgERGnX7qcHeALqPKAWuyVhEQ3Wiqi32ZYm
2bn9e2Qe+0O4KcPcmyYJOs+TBSYJtNgdW2deYEclTtvybxMYhxOorB88qlPMdN9LTrK8S2kY
63Oeo2v6SkgFwHUv8c8J5Cilc5Wj6vPDSjGrn3Rc3d9XDKomq8iQNkW2XRNno+cc5CV3vBmH
ZUIHjktDVk498P/MbEYZsowo6eFnhnzrsmPiQBWu8JlF3OU/eKG/ebb7MIIFHjCCBAagAwIB
AgIEEcy5NTANBgkqhkiG9w0BAQUFADCBhzELMAkGA1UEBhMCREUxEDAOBgNVBAgTB1NhY2hz
ZW4xEDAOBgNVBAcTB0RyZXNkZW4xGTAXBgNVBAoTEElGVyBEcmVzZGVuIGUuVi4xFzAVBgNV
BAMTDklGVyBEcmVzZGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUBpZnctZHJlc2Rlbi5kZTAe
Fw0xMTA0MTkwNzM3MDlaFw0xNDA0MTgwNzM3MDlaMD0xCzAJBgNVBAYTAkRFMRkwFwYDVQQK
ExBJRlcgRHJlc2RlbiBlLlYuMRMwEQYDVQQDEwpIZW5yaSBXYWhsMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA5mGCzWbUMWYyM7SVAoS0VbbzOfpZ+Ae+s0t3+2RMdwU4RadM
ZVCUQzWiEkX1goBW87T/GmDbb7fXSf7WrUyFjZxAyrF5YiOZhNlcm0PvYsHF2GUiK29bqL9H
zKNWMuwtMGkjqAUFPpJPtpreuUXxT9Fi40Q11XByN45xV4BaNOG6/O7o4p516/uWf2DEj3Q/
TZYA1GdXmyxRHMMtMIvw5pMz6Tm6gHIOoP1dF2ty0mYk6ywcEXLq3o8ecWMZiJm9vhPWzfGn
6/2HDk72KjGzPKjCi1qCRHpZTs5VaCAIkpBGqBOk1QZYxWjLGmhzcc3MZgUcmfuoIsxR2m9g
AZB2IwIDAQABo4IB2TCCAdUwCQYDVR0TBAIwADALBgNVHQ8EBAMCBeAwKQYDVR0lBCIwIAYI
KwYBBQUHAwIGCCsGAQUFBwMEBgorBgEEAYI3FAICMB0GA1UdDgQWBBTRJ5bAf/hkK34SrM/z
/fsonOI3GDAfBgNVHSMEGDAWgBQu8wsdFsPst071kiUewI9AQnGH/zAgBgNVHREEGTAXgRVo
LndhaGxAaWZ3LWRyZXNkZW4uZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5w
Y2EuZGZuLmRlL2lmdy1kcmVzZGVuLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRw
Oi8vY2RwMi5wY2EuZGZuLmRlL2lmdy1kcmVzZGVuLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGi
BggrBgEFBQcBAQSBlTCBkjBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9p
ZnctZHJlc2Rlbi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6
Ly9jZHAyLnBjYS5kZm4uZGUvaWZ3LWRyZXNkZW4tY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0
MA0GCSqGSIb3DQEBBQUAA4IBAQArHA8FqV5hAppyrDhXi5rsEp21lBbNCniwzwasff+lyWNm
IiEvjAcMkSwXoIjxP2HM87SUFijO7J+g9tQY2W4yaIU/OX8FkorzDH1NcI3RWoCjdhddWlEJ
eM0R/2+AQbJaPXFtilFjjPFC4/a6XZMSUCvfxrQGbxMRj6czBVM2LkOwRi2FfAMBP3qO6fQ6
IQNnjq0UppqT3O3W2acG/KIQgor06RrYVhWrDCOejW/xFSE1JFu+Dko4wHBO4/NUllxYXabS
0TDuzuQzQnRmG+ymeg/I1Cpd0JRvzPXgO4H6uXROPfnWTqd1wbK4daDPtde2e/qPB8+r2D1g
ZBKt6nr+MYID0TCCA80CAQEwgZAwgYcxCzAJBgNVBAYTAkRFMRAwDgYDVQQIEwdTYWNoc2Vu
MRAwDgYDVQQHEwdEcmVzZGVuMRkwFwYDVQQKExBJRlcgRHJlc2RlbiBlLlYuMRcwFQYDVQQD
Ew5JRlcgRHJlc2RlbiBDQTEgMB4GCSqGSIb3DQEJARYRY2FAaWZ3LWRyZXNkZW4uZGUCBBHM
uTUwCQYFKw4DAhoFAKCCAhUwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B
CQUxDxcNMTMwMzIxMjEwMjI3WjAjBgkqhkiG9w0BCQQxFgQUpm/fwWoqf5RPrsBqLBY23Rvq
VaYwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3
DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0D
AgIBKDCBoQYJKwYBBAGCNxAEMYGTMIGQMIGHMQswCQYDVQQGEwJERTEQMA4GA1UECBMHU2Fj
aHNlbjEQMA4GA1UEBxMHRHJlc2RlbjEZMBcGA1UEChMQSUZXIERyZXNkZW4gZS5WLjEXMBUG
A1UEAxMOSUZXIERyZXNkZW4gQ0ExIDAeBgkqhkiG9w0BCQEWEWNhQGlmdy1kcmVzZGVuLmRl
AgQRzLk1MIGjBgsqhkiG9w0BCRACCzGBk6CBkDCBhzELMAkGA1UEBhMCREUxEDAOBgNVBAgT
B1NhY2hzZW4xEDAOBgNVBAcTB0RyZXNkZW4xGTAXBgNVBAoTEElGVyBEcmVzZGVuIGUuVi4x
FzAVBgNVBAMTDklGVyBEcmVzZGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUBpZnctZHJlc2Rl
bi5kZQIEEcy5NTANBgkqhkiG9w0BAQEFAASCAQBsmQL+cnawWV0KiPX5AmKorkwvGv6qi4Fw
KauP5FrZ0NntQViXWc9CKSYxyNDOADTKtNye9AuvEaOFixk+1BifQAUbvcermuAOJPZPzfos
AZzIYVBVveZGnDC+wYcCOh+kgiwLvR8TNtLvCG+nhQdghlo+STxcJEwJFU45Axo+yVVzRhD1
ESYzzcwr9uuK0OJYB14NJgAWtaavKkWdSjJT/v4yAbls2NDF5TMWq27BmsESvBb0OxALLJ01
T81rjX14bBmqmm3GsqqTObyL31tWGhN1v08+N8P3/fmLnYNyKlKeJ8CONqRMTsOBfwgzBibT
k2Zkxb+TAtzcTvyMYu3pAAAAAAAA
--------------ms080209020109000300080908--

From volz@cisco.com  Thu Mar 21 14:06:39 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CDCE21F8C71 for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 14:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1EEY9iG0Iqia for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 14:06:38 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 95AEA21F88CA for <dhcwg@ietf.org>; Thu, 21 Mar 2013 14:06:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1196; q=dns/txt; s=iport; t=1363899998; x=1365109598; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=QZh0VAI3Dr7/2/iu3LDht2RRkZIKAtlAs42NzPDBOsU=; b=bCdd0lVa69lgI5KYRP/1LzqQSVDNyQDS++eyTqBV0VIqGWpnBZy9raU2 NCQEmX5kq1oneEiIFJg6M5OIWafrj31QRn5ZSTu1la6vs1L0xJqRrcUKt r7oAuO0QVP1wwUt3iVSErQXixOK3w0Ehsp5yQePa4ryPuVOdj0nMrOamv I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAKl1S1GtJV2Y/2dsb2JhbABDxU6BXBZ0giQBAQEDAXkFBwQCAQgOAwQBAQsdBzIUCQgCBA4FCIgGBsJIjVGBDyYLBwaCWWEDiD+PRIhNhxaDCoFzNQ
X-IronPort-AV: E=Sophos;i="4.84,888,1355097600"; d="scan'208";a="190176933"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-3.cisco.com with ESMTP; 21 Mar 2013 21:06:38 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2LL6c61025597 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Mar 2013 21:06:38 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Thu, 21 Mar 2013 16:06:37 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Henri Wahl <h.wahl@ifw-dresden.de>
Thread-Topic: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address
Thread-Index: AQHOJlVusO8YCw3oLECM4bu4YQQDkpiwbv84gACG8ID//6z8kA==
Date: Thu, 21 Mar 2013 21:06:37 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E184BC489@xmb-rcd-x04.cisco.com>
References: <514B2C7E.9000907@ifw-dresden.de>,<514B3C55.7060207@gmail.com> <2D6695B2-5AA6-4E80-B0F8-E4F5F936EAA5@cisco.com> <514B7563.4040408@ifw-dresden.de>
In-Reply-To: <514B7563.4040408@ifw-dresden.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.247.98]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per	address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 21:06:39 -0000

This requires a different IAID value.

- Bernie

-----Original Message-----
From: Henri Wahl [mailto:h.wahl@ifw-dresden.de]=20
Sent: Thursday, March 21, 2013 5:02 PM
To: Bernie Volz (volz)
Cc: Tomek Mrugalski; dhcwg@ietf.org
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per add=
ress


> There are two things here - one is server policy which allows the server =
to deliver 0 to n addresses (or prefixes). The other is the client's policy=
 which might want more than one.
>
> I think a client has two choices - send multiple IA_* options with unique=
 IAID values in the request or send one and if it needs more, send separate=
 requests.
>
With different IAIDs or the same in every request?

--=20
Henri Wahl

IT Department
Leibniz-Institut f=FCr Festk=F6rper- u.
Werkstoffforschung Dresden

tel: (03 51) 46 59 - 797
email: h.wahl@ifw-dresden.de
http://www.ifw-dresden.de

Nagios status monitor Nagstamon:
http://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d:
http://dhcpy6d.ifw-dresden.de

IFW Dresden e.V., Helmholtzstra=DFe 20, D-01069 Dresden
VR Dresden Nr. 1369
Vorstand: Prof. Dr. Ludwig Schultz, Dr. h.c. Rolf Pfrengle




From volz@cisco.com  Thu Mar 21 14:10:48 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D347021F8CAC for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 14:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09BvdEN81YXY for <dhcwg@ietfa.amsl.com>; Thu, 21 Mar 2013 14:10:48 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id E107B21F8C71 for <dhcwg@ietf.org>; Thu, 21 Mar 2013 14:10:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3639; q=dns/txt; s=iport; t=1363900248; x=1365109848; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=w+cLJKP49NuXWV3k4ek8DPD2Lp/N/CJOy+9PxMHj5K8=; b=PSqQWTpsKdJleIOD0ipT6GK+gTMdzXli+yxFEjizo0E2DU20NZGZa/ds XPLYTxJZ6zUgg6bEZBN58FEru1D8fJgS6dmq/atx6jwawV+G8C7Y/CpJM BwfkZr4Nlrl6hgvACKErdGO9Bebay8P8/g1hrUw51Wl4Z+7AV5mye8a+F s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAKl1S1GtJV2b/2dsb2JhbABDxU6BXBZ0giQBAQEDAXkFBwQCAQgOAwQBAQsdBzIUCQgCBAENBQiIBgbCSI1RgQ8mCwcGgllhA4g/j0SITYcWgwqBczU
X-IronPort-AV: E=Sophos;i="4.84,888,1355097600"; d="scan'208";a="187152779"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 21 Mar 2013 21:10:47 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2LLAk6T006054 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Mar 2013 21:10:46 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Thu, 21 Mar 2013 16:10:46 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Henri Wahl <h.wahl@ifw-dresden.de>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per address
Thread-Index: AQHOJlVusO8YCw3oLECM4bu4YQQDkpiw9YSA//+t+/A=
Date: Thu, 21 Mar 2013 21:10:45 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E184BC504@xmb-rcd-x04.cisco.com>
References: <514B2C7E.9000907@ifw-dresden.de> <514B3C55.7060207@gmail.com> <514B7509.4010405@ifw-dresden.de>
In-Reply-To: <514B7509.4010405@ifw-dresden.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.247.98]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per	address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 21:10:49 -0000

> Dibbler client can send
> multiple addresses and Dibbler server will understand and honor it,=20
> but I have serious doubts other implementations will behave that way.=20
> One reason I chose to implement this is that including an address is=20
> the only way for the client to specify its preference for preferred=20
> and valid lifetimes. Dibbler server tries to accept those hints if possib=
le.

And, our server for one, ignores these requests (for :: addresses) -- thoug=
h if configured, we do consider the lifetimes (though we would only conside=
r one of the values).

The addresses to assign or prefixes to delegate for a single binding is a s=
erver issue - it might be that there are multiple prefixes (ULA + GLA or mu=
ltiple GLA/ULAs if renumbering or multi-homed) from which the addresses wer=
e allocated or prefixes were delegated.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of H=
enri Wahl
Sent: Thursday, March 21, 2013 5:01 PM
To: Tomek Mrugalski
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Multiple IPv6 addresses in IA_NA vs. one IA_NA per add=
ress


> You may also want to read section 11 of RFC3315. This particular piece=20
> is interesting:
>    "A server selects addresses to be assigned to an IA according to the
>    address assignment policies determined by the server administrator"
>
> Note the plural/singular form: [many] addresses to an [single] IA.

Sorry I missed that - so even in RFC 3315 both ways are OK.
>
> So technically speaking both "many addresses in a single IA_NA" and=20
> "many IA_NAs, each with one address" are valid and how you assign them=20
> is a matter of assignment policy. The question here is really about=20
> how common those 2 approaches are. My understanding is that "many=20
> IA_NAs" is much more popular and supported by many more=20
> implementations, so I'd recommend doing that for better interoperability.
>
> The problem with having multiple addresses assigned is usually a=20
> client business, because it is a client that knows that more than one=20
> address is needed, e.g. because some extra services will be provided.
Depends... on the clients' role in the network. If it has no right to chose=
 at all and gets all its configuration from server the one-IA_NA-to-rule-th=
em-all-approach is OK. Wouldn't this be normally the case if you use statef=
ul DHCPv6 instead of SLAAC ?
> There is
> no easy way for the client to communicate to the server that it wants=20
> specific number of addresses in a given IA_NA.
Agree.
> Dibbler client can send
> multiple addresses and Dibbler server will understand and honor it,=20
> but I have serious doubts other implementations will behave that way.=20
> One reason I chose to implement this is that including an address is=20
> the only way for the client to specify its preference for preferred=20
> and valid lifetimes. Dibbler server tries to accept those hints if possib=
le.
>
> Perhaps this is something that could be clarified in stateful-issues=20
> draft? If not, this is definitely another thing for 3315bis work.
Regards

--
Henri Wahl

IT Department
Leibniz-Institut f=FCr Festk=F6rper- u.
Werkstoffforschung Dresden

tel: (03 51) 46 59 - 797
email: h.wahl@ifw-dresden.de
http://www.ifw-dresden.de

Nagios status monitor Nagstamon:
http://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d:
http://dhcpy6d.ifw-dresden.de

IFW Dresden e.V., Helmholtzstra=DFe 20, D-01069 Dresden VR Dresden Nr. 1369
Vorstand: Prof. Dr. Ludwig Schultz, Dr. h.c. Rolf Pfrengle




From mohamed.boucadair@orange.com  Fri Mar 22 09:10:52 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF48121F8959 for <dhcwg@ietfa.amsl.com>; Fri, 22 Mar 2013 09:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.084
X-Spam-Level: 
X-Spam-Status: No, score=-2.084 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id me7vST1H-0yS for <dhcwg@ietfa.amsl.com>; Fri, 22 Mar 2013 09:10:52 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 1FDF021F8928 for <dhcwg@ietf.org>; Fri, 22 Mar 2013 09:10:52 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 0CDA0264376 for <dhcwg@ietf.org>; Fri, 22 Mar 2013 17:10:51 +0100 (CET)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id E620B23804B for <dhcwg@ietf.org>; Fri, 22 Mar 2013 17:10:50 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.11]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Fri, 22 Mar 2013 17:10:50 +0100
From: <mohamed.boucadair@orange.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Fri, 22 Mar 2013 17:10:50 +0100
Thread-Topic: I-D Action: draft-ietf-dhc-triggered-reconfigure-05.txt
Thread-Index: Ac4mAssUHIkTi7rvSyKGjmE43jbbNABDvxqA
Message-ID: <94C682931C08B048B7A8645303FDC9F36EBA754A58@PUEXCB1B.nanterre.francetelecom.fr>
References: <20130321070727.28795.20395.idtracker@ietfa.amsl.com>
In-Reply-To: <20130321070727.28795.20395.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.22.135416
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-triggered-reconfigure-05.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Mar 2013 16:10:53 -0000

Dear All,

After discussion with Bernie, several editorial and minor technical modific=
ations were added to -05. The main changes are as follows:

* Re-structure the introduction text
* The relay agent is now able to insert a relay-id option
* The server may use the content of relay-id to enforce some security polic=
ies
* Add some text to clarify the behaviour when multiple servers are configur=
ed

A detailed diff can be found here: http://www.ietf.org/rfcdiff?url2=3Ddraft=
-ietf-dhc-triggered-reconfigure-05

Cheers,
Med

>-----Message d'origine-----
>De : i-d-announce-bounces@ietf.org=20
>[mailto:i-d-announce-bounces@ietf.org] De la part de=20
>internet-drafts@ietf.org
>Envoy=E9 : jeudi 21 mars 2013 08:07
>=C0 : i-d-announce@ietf.org
>Cc : dhcwg@ietf.org
>Objet : I-D Action: draft-ietf-dhc-triggered-reconfigure-05.txt
>
>
>A New Internet-Draft is available from the on-line=20
>Internet-Drafts directories.
> This draft is a work item of the Dynamic Host Configuration=20
>Working Group of the IETF.
>
>	Title           : Reconfigure Triggered by DHCPv6 Relay Agents
>	Author(s)       : Mohamed Boucadair
>                          Xavier Pougnard
>	Filename        : draft-ietf-dhc-triggered-reconfigure-05.txt
>	Pages           : 13
>	Date            : 2013-03-21
>
>Abstract:
>   This document defines new DHCPv6 messages: Reconfigure-Request and
>   Reconfigure-Reply.  Reconfigure-Request message is sent by a DHCPv6
>   relay agent to notify a DHCPv6 server about a configuration
>   information change, so that the DHCPv6 server can send a Reconfigure
>   message accordingly.  Reconfigure-Reply message is used by=20
>the server
>   to acknowledge the receipt of Reconfigure-Request.
>
>   This document updates RFC 3315 and RFC 6422.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-dhc-triggered-reconfigure
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-dhc-triggered-reconfigure-05
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-triggered-recon
>figure-05
>
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>I-D-Announce mailing list
>I-D-Announce@ietf.org
>https://www.ietf.org/mailman/listinfo/i-d-announce
>Internet-Draft directories: http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=

From msiodelski@gmail.com  Fri Mar 22 11:23:57 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FAF621F902E for <dhcwg@ietfa.amsl.com>; Fri, 22 Mar 2013 11:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.465
X-Spam-Level: 
X-Spam-Status: No, score=-2.465 tagged_above=-999 required=5 tests=[AWL=1.134,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WUUMYmjA-MFF for <dhcwg@ietfa.amsl.com>; Fri, 22 Mar 2013 11:23:56 -0700 (PDT)
Received: from mail-ee0-f41.google.com (mail-ee0-f41.google.com [74.125.83.41]) by ietfa.amsl.com (Postfix) with ESMTP id 873CD21F902A for <dhcwg@ietf.org>; Fri, 22 Mar 2013 11:23:56 -0700 (PDT)
Received: by mail-ee0-f41.google.com with SMTP id c1so18993eek.28 for <dhcwg@ietf.org>; Fri, 22 Mar 2013 11:23:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:subject:from:to:date:content-type:x-mailer :mime-version; bh=N6Qass5fcS/02Ca+NYkr1+Dk+nubPKrs87l1V5kY72o=; b=KMtxZVY35I0gAWo1MdYGIVLixBl5ezdPXGLHHQeb0yfHvqSX71J3HP9a0FAFhVjlHo q+Br0CwuC4RQx8F7wX9aWgEVdncOlh1JAIii3S7A+cofgboHYWxKghqT8ct9fLoDBsxB SewETI+8FWTSc4lPCo+8LmHB7+5I7PPFoo4OF5km/rPEqEmdQUb/+aGqk3S6a5s3C9f4 imJIy1TpaZiEiTXvfyTOf2+bMYCZ7GkcdLFZt47c86LlZc3So7kAVfbDSKunaM6IyxSv v/Au1ycYIkUN09pdWJ+x59g1K2pi9jYHcB0xXLX7G1wSklXZ8gIRqVCBGTu8e+++CSWc jWhQ==
X-Received: by 10.14.182.137 with SMTP id o9mr7673692eem.13.1363976635664; Fri, 22 Mar 2013 11:23:55 -0700 (PDT)
Received: from [192.168.0.193] (89-75-115-194.dynamic.chello.pl. [89.75.115.194]) by mx.google.com with ESMTPS id a1sm4513644eep.2.2013.03.22.11.23.54 (version=SSLv3 cipher=RC4-SHA bits=128/128); Fri, 22 Mar 2013 11:23:54 -0700 (PDT)
Message-ID: <1363976633.2579.130.camel@marcin-lenovo>
From: Marcin Siodelski <msiodelski@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Fri, 22 Mar 2013 19:23:53 +0100
Content-Type: multipart/mixed; boundary="=-1k6Q2n4IvSS6M8Qor9Ya"
X-Mailer: Evolution 3.6.4 (3.6.4-2.fc18) 
Mime-Version: 1.0
Subject: [dhcwg] [Fwd: New Version Notification for draft-scskf-dhc-dhcpv4-over-dhcpv6-00.txt]
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Mar 2013 18:23:57 -0000

--=-1k6Q2n4IvSS6M8Qor9Ya
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: 7bit

All, 

It is an initial version of the new draft, which proposes another
solution to provision the DHCPv4 service for the client, separated from
the DHCPv4 server by IPv6 network. This proposal is briefly called
DHCPv4-over-DHCPv6. It makes use of the DHCPv6 message to carry DHCPv4
message in the newly defined option.

Please review. Comments welcome.

Marcin

--=-1k6Q2n4IvSS6M8Qor9Ya
Content-Disposition: inline
Content-Description: Forwarded message =?UTF-8?Q?=E2=80=94?= New Version
 Notification for draft-scskf-dhc-dhcpv4-over-dhcpv6-00.txt
Content-Type: message/rfc822

Delivered-To: msiodelski@gmail.com
Received: by 10.112.68.140 with SMTP id w12csp114385lbt; Fri, 22 Mar 2013
 11:00:11 -0700 (PDT)
X-Received: by 10.68.10.227 with SMTP id l3mr4114604pbb.100.1363975210229;
 Fri, 22 Mar 2013 11:00:10 -0700 (PDT)
Return-Path: <internet-drafts@ietf.org>
Received: from mail.ietf.org (mail.ietf.org. [2001:1890:123a::1:1e]) by
 mx.google.com with ESMTP id tp7si3480205pbc.141.2013.03.22.11.00.09; Fri,
 22 Mar 2013 11:00:10 -0700 (PDT)
Received-SPF: pass (google.com: domain of internet-drafts@ietf.org
 designates 2001:1890:123a::1:1e as permitted sender)
 client-ip=2001:1890:123a::1:1e;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of
 internet-drafts@ietf.org designates 2001:1890:123a::1:1e as permitted
 sender) smtp.mail=internet-drafts@ietf.org
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com
 (Postfix) with ESMTP id 6F6CB21F8CF9; Fri, 22 Mar 2013 11:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j1x86qwVKYOq; Fri, 22
 Mar 2013 11:00:08 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com
 (Postfix) with ESMTP id 6EBF021F8E2C; Fri, 22 Mar 2013 11:00:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: internet-drafts@ietf.org
To: msiodelski@gmail.com
Cc: ian.farrer@telekom.de, sunqi@csnet1.cs.tsinghua.edu.cn,
 suresh.krishnan@ericsson.com, yong@csnet1.cs.tsinghua.edu.cn
Subject: New Version Notification for
 draft-scskf-dhc-dhcpv4-over-dhcpv6-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.43
Message-ID: <20130322180008.14803.3001.idtracker@ietfa.amsl.com>
Date: Fri, 22 Mar 2013 11:00:08 -0700
Content-Transfer-Encoding: 7bit


A new version of I-D, draft-scskf-dhc-dhcpv4-over-dhcpv6-00.txt
has been successfully submitted by Marcin Siodelski and posted to the
IETF repository.

Filename:	 draft-scskf-dhc-dhcpv4-over-dhcpv6
Revision:	 00
Title:		 DHCPv4 over DHCPv6 Transport
Creation date:	 2013-03-22
Group:		 Individual Submission
Number of pages: 7
URL:             http://www.ietf.org/internet-drafts/draft-scskf-dhc-dhcpv4-over-dhcpv6-00.txt
Status:          http://datatracker.ietf.org/doc/draft-scskf-dhc-dhcpv4-over-dhcpv6
Htmlized:        http://tools.ietf.org/html/draft-scskf-dhc-dhcpv4-over-dhcpv6-00


Abstract:
   This document describes a mechanism for obtaining IPv4 parameters in
   IPv6 networks by carrying DHCPv4 messages over DHCPv6 transport.

                                                                                  


The IETF Secretariat


--=-1k6Q2n4IvSS6M8Qor9Ya--


From volz@cisco.com  Sun Mar 24 13:25:50 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE3A721F8D34 for <dhcwg@ietfa.amsl.com>; Sun, 24 Mar 2013 13:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEu1yCqcShL2 for <dhcwg@ietfa.amsl.com>; Sun, 24 Mar 2013 13:25:50 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id D89CC21F8B19 for <dhcwg@ietf.org>; Sun, 24 Mar 2013 13:25:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6465; q=dns/txt; s=iport; t=1364156749; x=1365366349; h=from:to:subject:date:message-id:mime-version; bh=Io+WQaL1XPiBCjoo6tzmMXVdyJ/P5B/JiLd1BSEzJE0=; b=UZHKpmFd9xvyMeEn4yVyO9kjFfpGyIyzylZ6I1GTufRi+shyL5U0/kNB D4LHsyFZ8ITyeeGLr7DsZ6pM/FazbeBKvXP8vCP7n23JOiKSOCMB24NyC Skju0FJAG4TgqcXTcJmr0DTNXZyQTe+ShqpVbkPB5JBZ2lizEFOQMQo7B A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8FAAVhT1GtJV2Z/2dsb2JhbABDhCW5IQGIKYFyFm0HgiYBBC1eASpWJgEEG4gMDKEtoBmJCIVfgxdhA5gGj2WDCoIo
X-IronPort-AV: E=Sophos;i="4.84,901,1355097600";  d="scan'208,217";a="190933601"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 24 Mar 2013 20:25:36 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2OKPaJH007451 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sun, 24 Mar 2013 20:25:36 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Sun, 24 Mar 2013 15:25:36 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC - draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 - Respond by April 8, 2013
Thread-Index: Ac4ozYfaibHYbpaWSZS5v8sktAaRTw==
Date: Sun, 24 Mar 2013 20:25:35 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E184C093B@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.247.98]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E184C093Bxmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] WGLC - draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 - Respond by April 8, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Mar 2013 20:25:51 -0000

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

Folks, the authors of draft-ietf-dhc-dhcpv6-prefix-pool-opt-02<http://tools=
.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-02> feel it's ready fo=
r a WGLC.  There's been discussion and comment already, but more eyes on th=
is work are definitely needed to advance it.

At the time of this writing, there is no IPR reported against this draft.

Please review the draft and indicate whether or not you feel it is ready to=
 be published.  We have been getting very anemic responses to working group=
 messages recently.   Your response matters, so please do respond.

Tomek and I will evaluate consensus after April 8, 2013.

Thanks!


-          Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E184C093Bxmbrcdx04ciscoc_
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:1241215036;
	mso-list-type:hybrid;
	mso-list-template-ids:328336620 1899551708 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">Folks, the authors of <a href=3D"http://tools.ietf.o=
rg/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-02">
draft-ietf-dhc-dhcpv6-prefix-pool-opt-02</a> feel it's ready for a WGLC.&nb=
sp; There's been discussion and comment already, but more eyes on this work=
 are definitely needed to advance it.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">At the time of this writing, there is no IPR reporte=
d against this draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please review the draft and indicate whether or not =
you feel it is ready to be published.&nbsp; We have been getting very anemi=
c responses to working group messages recently.&nbsp;&nbsp; Your response m=
atters, so please do respond.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Tomek and I will evaluate consensus after April 8, 2=
013.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks!<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]>Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E184C093Bxmbrcdx04ciscoc_--

From volz@cisco.com  Mon Mar 25 08:50:55 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A42321F8D35 for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 08:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCsBEBgsa0Jf for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 08:50:54 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 8220021F8D2F for <dhcwg@ietf.org>; Mon, 25 Mar 2013 08:50:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5573; q=dns/txt; s=iport; t=1364226654; x=1365436254; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=TljIRw1pVdTFzMDUfP5psS6Iy1eWR0xbW11gw6hDWkc=; b=SjUFZIX0wkxCNu7DuuvGaI0GvhZF0F2eYAsQ0FDodRsdkp8/C1GZGzHE YMUvD/lTPUj2wisjp0wgtvJ8kW085XvVXrCQFNjL/3PSMIAuYkWwuy8/o AzRkPiuoo6UWRjio0CaxeRBk2RcXW5W4xKrZeD5HdtxnnL8MtIhHU2l1M 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAAJxUFGtJXG8/2dsb2JhbABEvTkBiCmCAxZtB4IlAQECAnkQAgEIPwcyFBEBAQQOBQmICwzDAI8YB4JfYQOWZ4Efj2WDCg
X-IronPort-AV: E=Sophos;i="4.84,905,1355097600";  d="scan'208,217";a="191158106"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-8.cisco.com with ESMTP; 25 Mar 2013 15:50:44 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2PFoiQD015933 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Mar 2013 15:50:44 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Mon, 25 Mar 2013 10:50:44 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: draft-ietf-pcp-dhcp: Exit from the loop
Thread-Index: Ac4pbclNF6ugk1fSTtSaAP9fTWNoigAArkm7
Date: Mon, 25 Mar 2013 15:50:44 +0000
Message-ID: <34AF6119-6069-4012-90BF-D1EF3BB29251@cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36EBA754E5C@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EBA754E5C@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_34AF61196069401290BFD1EF3BB29251ciscocom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Dhc Chairs \(dhc-chairs@tools.ietf.org\)" <dhc-chairs@tools.ietf.org>, "draft-ietf-pcp-dhcp@tools.ietf.org" <draft-ietf-pcp-dhcp@tools.ietf.org>, "pcp-chairs@tools.ietf.org" <pcp-chairs@tools.ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-pcp-dhcp: Exit from the loop
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Mar 2013 15:50:55 -0000

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

You need to pick either fqdn or address - not both. See the option guidelin=
es draft. DHC is unlikely to support this work if you don't follow option g=
uidelines.

- Bernie

On Mar 25, 2013, at 11:31 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Dear all,

I understood no conclusion was reached in the previous pcp meeting for this=
 I-D.
The version available at http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06 =
reflects the consensus of the pcp wg but Ted is not happy with that design.

It seems we are looping here:
* The approach of using two formats was documented in a previous version bu=
t it was removed after a review from Bernie.
* RFC1035-based encoding was documented in a previous version but it was re=
moved because the consensus of the pcp working group is no to over specify =
the options to be dns-specific.
* A more detailed background is provided here: http://www.ietf.org/proceedi=
ngs/86/slides/slides-86-pcp-4.pdf.

As I have two opposite signals, I don't know how to proceed. This is why I'=
m expanding this to dhc chairs to have your feedback too.

Cheers,
Med

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>You need to pick either fqdn or address - not both. See the option gui=
delines draft. DHC is unlikely to support this work if you don't follow opt=
ion guidelines.</div>
<div><br>
- Bernie</div>
<div><br>
On Mar 25, 2013, at 11:31 AM, &quot;<a href=3D"mailto:mohamed.boucadair@ora=
nge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:moham=
ed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Dear&nbsp;all,</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">I understood&nbsp;no conclusion was r=
eached in the previous pcp meeting for this I-D.</span></span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">The version available at
<a href=3D"http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06">http://tools.=
ietf.org/html/draft-ietf-pcp-dhcp-06</a>&nbsp;reflects the consensus of the=
 pcp wg but Ted is not happy with that design.</span></span></font></div>
</span></span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013"></span></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">It seems we are looping here:</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">* The approach of using two formats was documented in a previous version=
 but it was removed after a review from Bernie.</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">* RFC1035-based encoding was documented in a previous version but it was=
 removed because the consensus of the pcp working group is no to over speci=
fy the options to be dns-specific.</span></font></div>
</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005=
5514-25032013">*
</span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005551=
4-25032013"><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-=
25032013">A more detailed background is provided here:
</span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005551=
4-25032013"><a href=3D"http://www.ietf.org/proceedings/86/slides/slides-86-=
pcp-4.pdf">http://www.ietf.org/proceedings/86/slides/slides-86-pcp-4.pdf</a=
>.</span></font></span></font></div>
<font size=3D"2" face=3D"Courier New">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
</font>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">As&nbsp;I have two opposite signals,&nbsp;I don't know how to proceed. T=
his is why I'm expanding this to dhc chairs to have your feedback too.</spa=
n></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Cheers,</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Med</span></font></div>
</div>
</blockquote>
</body>
</html>

--_000_34AF61196069401290BFD1EF3BB29251ciscocom_--

From mohamed.boucadair@orange.com  Mon Mar 25 08:56:53 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13EF721F8FFA for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 08:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.444
X-Spam-Level: 
X-Spam-Status: No, score=-1.444 tagged_above=-999 required=5 tests=[AWL=0.803,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8ZI2Dz6T4e5 for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 08:56:52 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 2CAE321F8FFB for <dhcwg@ietf.org>; Mon, 25 Mar 2013 08:56:51 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id AD08F22C484; Mon, 25 Mar 2013 16:56:43 +0100 (CET)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 3113323805E; Mon, 25 Mar 2013 16:56:43 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.11]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Mon, 25 Mar 2013 16:56:43 +0100
From: <mohamed.boucadair@orange.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Date: Mon, 25 Mar 2013 16:56:41 +0100
Thread-Topic: draft-ietf-pcp-dhcp: Exit from the loop
Thread-Index: Ac4pbclNF6ugk1fSTtSaAP9fTWNoigAArkm7AAAJODA=
Message-ID: <94C682931C08B048B7A8645303FDC9F36EBA754E92@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36EBA754E5C@PUEXCB1B.nanterre.francetelecom.fr> <34AF6119-6069-4012-90BF-D1EF3BB29251@cisco.com>
In-Reply-To: <34AF6119-6069-4012-90BF-D1EF3BB29251@cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F36EBA754E92PUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.25.85421
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Dhc Chairs \(dhc-chairs@tools.ietf.org\)" <dhc-chairs@tools.ietf.org>, "draft-ietf-pcp-dhcp@tools.ietf.org" <draft-ietf-pcp-dhcp@tools.ietf.org>, "pcp-chairs@tools.ietf.org" <pcp-chairs@tools.ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-pcp-dhcp: Exit from the loop
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Mar 2013 15:56:53 -0000

--_000_94C682931C08B048B7A8645303FDC9F36EBA754E92PUEXCB1Bnante_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Re-,

The draft does not define both; only one format is defined.

The issue is more related to what was discussed in this list: the use of ut=
f-8 encoding.
The conclusion of that discussion is there was no consensus to adopt nor to=
 reject that approach.

Cheers,
Med

________________________________
De : Bernie Volz (volz) [mailto:volz@cisco.com]
Envoy=E9 : lundi 25 mars 2013 16:51
=C0 : BOUCADAIR Mohamed OLNC/OLN
Cc : Dhc Chairs (dhc-chairs@tools.ietf.org); Ted Lemon; pcp-chairs@tools.ie=
tf.org; draft-ietf-pcp-dhcp@tools.ietf.org; dhcwg@ietf.org
Objet : Re: draft-ietf-pcp-dhcp: Exit from the loop

You need to pick either fqdn or address - not both. See the option guidelin=
es draft. DHC is unlikely to support this work if you don't follow option g=
uidelines.

- Bernie

On Mar 25, 2013, at 11:31 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Dear all,

I understood no conclusion was reached in the previous pcp meeting for this=
 I-D.
The version available at http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06 =
reflects the consensus of the pcp wg but Ted is not happy with that design.

It seems we are looping here:
* The approach of using two formats was documented in a previous version bu=
t it was removed after a review from Bernie.
* RFC1035-based encoding was documented in a previous version but it was re=
moved because the consensus of the pcp working group is no to over specify =
the options to be dns-specific.
* A more detailed background is provided here: http://www.ietf.org/proceedi=
ngs/86/slides/slides-86-pcp-4.pdf.

As I have two opposite signals, I don't know how to proceed. This is why I'=
m expanding this to dhc chairs to have your feedback too.

Cheers,
Med

--_000_94C682931C08B048B7A8645303FDC9F36EBA754E92PUEXCB1Bnante_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18702"></HEAD>
<BODY dir=3Dauto>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Re-,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">The draft does not define both; only one form=
at is=20
defined.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">The issue is more related to&nbsp;what was di=
scussed=20
in this list:&nbsp;the use of utf-8 encoding.&nbsp;</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">The conclusion of that&nbsp;discussion is the=
re was no=20
consensus to adopt nor to reject that&nbsp;approach.&nbsp;</FONT></SPAN></D=
IV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Med</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; MARGIN-RIGHT: 0px"=20
dir=3Dltr>
  <DIV dir=3Dltr lang=3Dfr class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>De&nbsp;:</B> Bernie Volz (volz)=20
  [mailto:volz@cisco.com] <BR><B>Envoy=E9&nbsp;:</B> lundi 25 mars 2013=20
  16:51<BR><B>=C0&nbsp;:</B> BOUCADAIR Mohamed OLNC/OLN<BR><B>Cc&nbsp;:</B>=
 Dhc=20
  Chairs (dhc-chairs@tools.ietf.org); Ted Lemon; pcp-chairs@tools.ietf.org;=
=20
  draft-ietf-pcp-dhcp@tools.ietf.org; dhcwg@ietf.org<BR><B>Objet&nbsp;:</B>=
 Re:=20
  draft-ietf-pcp-dhcp: Exit from the loop<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>You need to pick either fqdn or address - not both. See the option=20
  guidelines draft. DHC is unlikely to support this work if you don't follo=
w=20
  option guidelines.</DIV>
  <DIV><BR>- Bernie</DIV>
  <DIV><BR>On Mar 25, 2013, at 11:31 AM, "<A=20
  href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</A>"=20
  &lt;<A=20
  href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</A>&gt;=20
  wrote:<BR><BR></DIV>
  <BLOCKQUOTE type=3D"cite">
    <DIV>
    <META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18702">
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
    class=3D620055514-25032013>Dear&nbsp;all,</SPAN></FONT></DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
    class=3D620055514-25032013></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-250320=
13><SPAN=20
    class=3D620055514-25032013>I understood&nbsp;no conclusion was reached =
in the=20
    previous pcp meeting for this I-D.</SPAN></SPAN></FONT></DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-250320=
13><SPAN=20
    class=3D620055514-25032013>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-250320=
13><SPAN=20
    class=3D620055514-25032013>The version available at <A=20
    href=3D"http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06">http://tools=
.ietf.org/html/draft-ietf-pcp-dhcp-06</A>&nbsp;reflects=20
    the consensus of the pcp wg but Ted is not happy with that=20
    design.</SPAN></SPAN></FONT></DIV></SPAN></SPAN></FONT></DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-250320=
13><SPAN=20
    class=3D620055514-25032013></SPAN></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-250320=
13>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-250320=
13>It seems=20
    we are looping here:</SPAN></FONT></DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-250320=
13>* The=20
    approach of using two formats was documented in a previous version but =
it=20
    was removed after a review from Bernie.</SPAN></FONT></DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-250320=
13>*=20
    RFC1035-based encoding was documented in a previous version but it was=
=20
    removed because the consensus of the pcp working group is no to over sp=
ecify=20
    the options to be dns-specific.</SPAN></FONT></DIV></SPAN></FONT></DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
    class=3D620055514-25032013></SPAN></FONT><FONT size=3D2 face=3D"Courier=
 New"><SPAN=20
    class=3D620055514-25032013>* </SPAN></FONT><FONT size=3D2=20
    face=3D"Courier New"><SPAN class=3D620055514-25032013><FONT size=3D2=20
    face=3D"Courier New"><SPAN class=3D620055514-25032013>A more detailed b=
ackground=20
    is provided here: </SPAN></FONT><FONT size=3D2 face=3D"Courier New"><SP=
AN=20
    class=3D620055514-25032013><A=20
    href=3D"http://www.ietf.org/proceedings/86/slides/slides-86-pcp-4.pdf">=
http://www.ietf.org/proceedings/86/slides/slides-86-pcp-4.pdf</A>.</SPAN></=
FONT></SPAN></FONT></DIV><FONT=20
    size=3D2 face=3D"Courier New">
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
    class=3D620055514-25032013></SPAN></FONT>&nbsp;</DIV></FONT>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
    class=3D620055514-25032013>As&nbsp;I have two opposite signals,&nbsp;I =
don't=20
    know how to proceed. This is why I'm expanding this to dhc chairs to ha=
ve=20
    your feedback too.</SPAN></FONT></DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
    class=3D620055514-25032013></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
    class=3D620055514-25032013>Cheers,</SPAN></FONT></DIV>
    <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
    class=3D620055514-25032013>Med</SPAN></FONT></DIV></DIV></BLOCKQUOTE></=
BLOCKQUOTE></BODY></HTML>

--_000_94C682931C08B048B7A8645303FDC9F36EBA754E92PUEXCB1Bnante_--

From volz@cisco.com  Mon Mar 25 09:00:05 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42B1721E804A for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 09:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zPF2UmM6PKdU for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 09:00:03 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id D42EB21F8FFF for <dhcwg@ietf.org>; Mon, 25 Mar 2013 09:00:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9894; q=dns/txt; s=iport; t=1364227202; x=1365436802; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=z2QN41//c8u3IafmUsnzcFKZcYAKEFOLp5WqMVZvUdc=; b=btbO+y0tzFTFg2R/Gb6euRY2EqEuRLk/n6rkOecbxdijLMAXFYDh6q82 tmi2i7GAeOY49l4KpdOhfpF7WMmz4N7nEJW8SbvybaX68KxDj7/M2M5mT dRx+jk+uOOwJpOqnq0TSbFRg4iu2kN0UBKv5SfNZ7mAOp7fX7DAcDDR4x Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFABd0UFGtJXG9/2dsb2JhbABEvUIBiCmCBBZtB4IkAQEBAgJ5EAIBCD8HMhQRAQEEDgUJiAsMwn2PGAYBgl9hA4hBjiaBH49lgwo
X-IronPort-AV: E=Sophos;i="4.84,905,1355097600";  d="scan'208,217";a="191157753"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-5.cisco.com with ESMTP; 25 Mar 2013 16:00:01 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r2PG01GW020991 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Mar 2013 16:00:01 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Mon, 25 Mar 2013 11:00:01 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: draft-ietf-pcp-dhcp: Exit from the loop
Thread-Index: Ac4pbclNF6ugk1fSTtSaAP9fTWNoigAArkm7AAAJODAAAEmdqw==
Date: Mon, 25 Mar 2013 16:00:00 +0000
Message-ID: <870B688F-BD7B-486E-8877-F55FBC464A60@cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36EBA754E5C@PUEXCB1B.nanterre.francetelecom.fr> <34AF6119-6069-4012-90BF-D1EF3BB29251@cisco.com>, <94C682931C08B048B7A8645303FDC9F36EBA754E92@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EBA754E92@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_870B688FBD7B486E8877F55FBC464A60ciscocom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Dhc Chairs \(dhc-chairs@tools.ietf.org\)" <dhc-chairs@tools.ietf.org>, "draft-ietf-pcp-dhcp@tools.ietf.org" <draft-ietf-pcp-dhcp@tools.ietf.org>, "pcp-chairs@tools.ietf.org" <pcp-chairs@tools.ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-pcp-dhcp: Exit from the loop
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Mar 2013 16:00:05 -0000

--_000_870B688FBD7B486E8877F55FBC464A60ciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I understand - but draft does not follow option guidelines -- use only fqdn=
 encoding or ipv6 address data type; utf 8 which can hold anything is not a=
llowed.

- Bernie

On Mar 25, 2013, at 11:56 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Re-,

The draft does not define both; only one format is defined.

The issue is more related to what was discussed in this list: the use of ut=
f-8 encoding.
The conclusion of that discussion is there was no consensus to adopt nor to=
 reject that approach.

Cheers,
Med

________________________________
De : Bernie Volz (volz) [mailto:volz@cisco.com]
Envoy=E9 : lundi 25 mars 2013 16:51
=C0 : BOUCADAIR Mohamed OLNC/OLN
Cc : Dhc Chairs (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org=
>); Ted Lemon; pcp-chairs@tools.ietf.org<mailto:pcp-chairs@tools.ietf.org>;=
 draft-ietf-pcp-dhcp@tools.ietf.org<mailto:draft-ietf-pcp-dhcp@tools.ietf.o=
rg>; dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Objet : Re: draft-ietf-pcp-dhcp: Exit from the loop

You need to pick either fqdn or address - not both. See the option guidelin=
es draft. DHC is unlikely to support this work if you don't follow option g=
uidelines.

- Bernie

On Mar 25, 2013, at 11:31 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Dear all,

I understood no conclusion was reached in the previous pcp meeting for this=
 I-D.
The version available at http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06 =
reflects the consensus of the pcp wg but Ted is not happy with that design.

It seems we are looping here:
* The approach of using two formats was documented in a previous version bu=
t it was removed after a review from Bernie.
* RFC1035-based encoding was documented in a previous version but it was re=
moved because the consensus of the pcp working group is no to over specify =
the options to be dns-specific.
* A more detailed background is provided here: http://www.ietf.org/proceedi=
ngs/86/slides/slides-86-pcp-4.pdf.

As I have two opposite signals, I don't know how to proceed. This is why I'=
m expanding this to dhc chairs to have your feedback too.

Cheers,
Med

--_000_870B688FBD7B486E8877F55FBC464A60ciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body dir=3D"auto">
<div>I understand - but draft does not follow option guidelines -- use only=
 fqdn encoding or ipv6 address data type; utf 8 which can hold anything is =
not allowed.</div>
<div><br>
- Bernie</div>
<div><br>
On Mar 25, 2013, at 11:56 AM, &quot;<a href=3D"mailto:mohamed.boucadair@ora=
nge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:moham=
ed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Re-,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">The draft does not define b=
oth; only one format is defined.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">The issue is more related t=
o&nbsp;what was discussed in this list:&nbsp;the use of utf-8 encoding.&nbs=
p;</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">The conclusion of that&nbsp=
;discussion is there was no consensus to adopt nor to reject that&nbsp;appr=
oach.&nbsp;</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Cheers,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Med</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"fr" class=3D"OutlookMessageHeader" align=3D"left">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>De&nbsp;:</b> Bernie Volz (volz) [<a hr=
ef=3D"mailto:volz@cisco.com">mailto:volz@cisco.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> lundi 25 mars 2013 16:51<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed OLNC/OLN<br>
<b>Cc&nbsp;:</b> Dhc Chairs (<a href=3D"mailto:dhc-chairs@tools.ietf.org">d=
hc-chairs@tools.ietf.org</a>); Ted Lemon;
<a href=3D"mailto:pcp-chairs@tools.ietf.org">pcp-chairs@tools.ietf.org</a>;=
 <a href=3D"mailto:draft-ietf-pcp-dhcp@tools.ietf.org">
draft-ietf-pcp-dhcp@tools.ietf.org</a>; <a href=3D"mailto:dhcwg@ietf.org">d=
hcwg@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: draft-ietf-pcp-dhcp: Exit from the loop<br>
</font><br>
</div>
<div></div>
<div>You need to pick either fqdn or address - not both. See the option gui=
delines draft. DHC is unlikely to support this work if you don't follow opt=
ion guidelines.</div>
<div><br>
- Bernie</div>
<div><br>
On Mar 25, 2013, at 11:31 AM, &quot;<a href=3D"mailto:mohamed.boucadair@ora=
nge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:moham=
ed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Dear&nbsp;all,</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">I understood&nbsp;no conclusion was r=
eached in the previous pcp meeting for this I-D.</span></span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">The version available at
<a href=3D"http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06">http://tools.=
ietf.org/html/draft-ietf-pcp-dhcp-06</a>&nbsp;reflects the consensus of the=
 pcp wg but Ted is not happy with that design.</span></span></font></div>
</span></span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013"></span></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">It seems we are looping here:</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">* The approach of using two formats was documented in a previous version=
 but it was removed after a review from Bernie.</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">* RFC1035-based encoding was documented in a previous version but it was=
 removed because the consensus of the pcp working group is no to over speci=
fy the options to be dns-specific.</span></font></div>
</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005=
5514-25032013">*
</span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005551=
4-25032013"><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-=
25032013">A more detailed background is provided here:
</span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005551=
4-25032013"><a href=3D"http://www.ietf.org/proceedings/86/slides/slides-86-=
pcp-4.pdf">http://www.ietf.org/proceedings/86/slides/slides-86-pcp-4.pdf</a=
>.</span></font></span></font></div>
<font size=3D"2" face=3D"Courier New">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
</font>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">As&nbsp;I have two opposite signals,&nbsp;I don't know how to proceed. T=
his is why I'm expanding this to dhc chairs to have your feedback too.</spa=
n></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Cheers,</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Med</span></font></div>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</body>
</html>

--_000_870B688FBD7B486E8877F55FBC464A60ciscocom_--

From volz@cisco.com  Mon Mar 25 09:01:27 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 751EF21E8053 for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 09:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O40wsh4hHQJE for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 09:01:26 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 6CAF521F900A for <dhcwg@ietf.org>; Mon, 25 Mar 2013 09:01:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9770; q=dns/txt; s=iport; t=1364227286; x=1365436886; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=eN7XCBCRPT7iwDc5nQ+zzlvusZSQbQZXpE4P1xYCfis=; b=VpsyDigInky+IZSUJk8KQw27JFif0xBGed+eKOrTbXVE7Po9nIQyZ5CN m5+fvqCzK+igVWLP68kCFZRQUlhiGxf1Tc2Q4fTlhOw5vlZjqhx0UwQh3 2fKUhU5jUTPQDWyHhxkZWw+r62hpIw4x/gNPmatMg7vIVU0N6du8AHalN E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFABd0UFGtJXG+/2dsb2JhbABEvUIBiCmCBBZtB4IkAQEBAgJ5EAIBCD8HMhQRAQEEDgUJiAsMwn2PGAYBgl9hA4hBjiaBH49lgwo
X-IronPort-AV: E=Sophos;i="4.84,905,1355097600";  d="scan'208,217";a="191158878"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 25 Mar 2013 16:01:26 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2PG1PxF015121 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Mar 2013 16:01:25 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Mon, 25 Mar 2013 11:01:25 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: draft-ietf-pcp-dhcp: Exit from the loop
Thread-Index: Ac4pbclNF6ugk1fSTtSaAP9fTWNoigAArkm7AAAJODAAAFYy3w==
Date: Mon, 25 Mar 2013 16:01:24 +0000
Message-ID: <A8111535-B94B-4CB1-98A3-95C582DFFAD0@cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36EBA754E5C@PUEXCB1B.nanterre.francetelecom.fr> <34AF6119-6069-4012-90BF-D1EF3BB29251@cisco.com>, <94C682931C08B048B7A8645303FDC9F36EBA754E92@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EBA754E92@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_A8111535B94B4CB198A395C582DFFAD0ciscocom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Dhc Chairs \(dhc-chairs@tools.ietf.org\)" <dhc-chairs@tools.ietf.org>, "draft-ietf-pcp-dhcp@tools.ietf.org" <draft-ietf-pcp-dhcp@tools.ietf.org>, "pcp-chairs@tools.ietf.org" <pcp-chairs@tools.ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-pcp-dhcp: Exit from the loop
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Mar 2013 16:01:27 -0000

--_000_A8111535B94B4CB198A395C582DFFAD0ciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Just to be clear - that approach was rejected. There is discussion in the o=
ption guidelines draft.

- Bernie

On Mar 25, 2013, at 11:56 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Re-,

The draft does not define both; only one format is defined.

The issue is more related to what was discussed in this list: the use of ut=
f-8 encoding.
The conclusion of that discussion is there was no consensus to adopt nor to=
 reject that approach.

Cheers,
Med

________________________________
De : Bernie Volz (volz) [mailto:volz@cisco.com]
Envoy=E9 : lundi 25 mars 2013 16:51
=C0 : BOUCADAIR Mohamed OLNC/OLN
Cc : Dhc Chairs (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org=
>); Ted Lemon; pcp-chairs@tools.ietf.org<mailto:pcp-chairs@tools.ietf.org>;=
 draft-ietf-pcp-dhcp@tools.ietf.org<mailto:draft-ietf-pcp-dhcp@tools.ietf.o=
rg>; dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Objet : Re: draft-ietf-pcp-dhcp: Exit from the loop

You need to pick either fqdn or address - not both. See the option guidelin=
es draft. DHC is unlikely to support this work if you don't follow option g=
uidelines.

- Bernie

On Mar 25, 2013, at 11:31 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Dear all,

I understood no conclusion was reached in the previous pcp meeting for this=
 I-D.
The version available at http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06 =
reflects the consensus of the pcp wg but Ted is not happy with that design.

It seems we are looping here:
* The approach of using two formats was documented in a previous version bu=
t it was removed after a review from Bernie.
* RFC1035-based encoding was documented in a previous version but it was re=
moved because the consensus of the pcp working group is no to over specify =
the options to be dns-specific.
* A more detailed background is provided here: http://www.ietf.org/proceedi=
ngs/86/slides/slides-86-pcp-4.pdf.

As I have two opposite signals, I don't know how to proceed. This is why I'=
m expanding this to dhc chairs to have your feedback too.

Cheers,
Med

--_000_A8111535B94B4CB198A395C582DFFAD0ciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body dir=3D"auto">
<div>Just to be clear - that approach was rejected. There is discussion in =
the option guidelines draft.</div>
<div><br>
- Bernie</div>
<div><br>
On Mar 25, 2013, at 11:56 AM, &quot;<a href=3D"mailto:mohamed.boucadair@ora=
nge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:moham=
ed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Re-,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">The draft does not define b=
oth; only one format is defined.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">The issue is more related t=
o&nbsp;what was discussed in this list:&nbsp;the use of utf-8 encoding.&nbs=
p;</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">The conclusion of that&nbsp=
;discussion is there was no consensus to adopt nor to reject that&nbsp;appr=
oach.&nbsp;</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Cheers,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Med</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"fr" class=3D"OutlookMessageHeader" align=3D"left">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>De&nbsp;:</b> Bernie Volz (volz) [<a hr=
ef=3D"mailto:volz@cisco.com">mailto:volz@cisco.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> lundi 25 mars 2013 16:51<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed OLNC/OLN<br>
<b>Cc&nbsp;:</b> Dhc Chairs (<a href=3D"mailto:dhc-chairs@tools.ietf.org">d=
hc-chairs@tools.ietf.org</a>); Ted Lemon;
<a href=3D"mailto:pcp-chairs@tools.ietf.org">pcp-chairs@tools.ietf.org</a>;=
 <a href=3D"mailto:draft-ietf-pcp-dhcp@tools.ietf.org">
draft-ietf-pcp-dhcp@tools.ietf.org</a>; <a href=3D"mailto:dhcwg@ietf.org">d=
hcwg@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: draft-ietf-pcp-dhcp: Exit from the loop<br>
</font><br>
</div>
<div></div>
<div>You need to pick either fqdn or address - not both. See the option gui=
delines draft. DHC is unlikely to support this work if you don't follow opt=
ion guidelines.</div>
<div><br>
- Bernie</div>
<div><br>
On Mar 25, 2013, at 11:31 AM, &quot;<a href=3D"mailto:mohamed.boucadair@ora=
nge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:moham=
ed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Dear&nbsp;all,</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">I understood&nbsp;no conclusion was r=
eached in the previous pcp meeting for this I-D.</span></span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">The version available at
<a href=3D"http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06">http://tools.=
ietf.org/html/draft-ietf-pcp-dhcp-06</a>&nbsp;reflects the consensus of the=
 pcp wg but Ted is not happy with that design.</span></span></font></div>
</span></span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013"></span></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">It seems we are looping here:</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">* The approach of using two formats was documented in a previous version=
 but it was removed after a review from Bernie.</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">* RFC1035-based encoding was documented in a previous version but it was=
 removed because the consensus of the pcp working group is no to over speci=
fy the options to be dns-specific.</span></font></div>
</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005=
5514-25032013">*
</span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005551=
4-25032013"><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-=
25032013">A more detailed background is provided here:
</span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005551=
4-25032013"><a href=3D"http://www.ietf.org/proceedings/86/slides/slides-86-=
pcp-4.pdf">http://www.ietf.org/proceedings/86/slides/slides-86-pcp-4.pdf</a=
>.</span></font></span></font></div>
<font size=3D"2" face=3D"Courier New">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
</font>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">As&nbsp;I have two opposite signals,&nbsp;I don't know how to proceed. T=
his is why I'm expanding this to dhc chairs to have your feedback too.</spa=
n></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Cheers,</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Med</span></font></div>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</body>
</html>

--_000_A8111535B94B4CB198A395C582DFFAD0ciscocom_--

From mohamed.boucadair@orange.com  Mon Mar 25 09:06:20 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A33021E8086 for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 09:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.712
X-Spam-Level: 
X-Spam-Status: No, score=-1.712 tagged_above=-999 required=5 tests=[AWL=0.535,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3-9bEb3t5m5H for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 09:06:19 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 3700C21F9018 for <dhcwg@ietf.org>; Mon, 25 Mar 2013 09:06:19 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 9368318C462; Mon, 25 Mar 2013 17:06:18 +0100 (CET)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 6F4B435C07E; Mon, 25 Mar 2013 17:06:18 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.11]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Mon, 25 Mar 2013 17:06:18 +0100
From: <mohamed.boucadair@orange.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Date: Mon, 25 Mar 2013 17:06:16 +0100
Thread-Topic: draft-ietf-pcp-dhcp: Exit from the loop
Thread-Index: Ac4pbclNF6ugk1fSTtSaAP9fTWNoigAArkm7AAAJODAAAFYy3wAAI9rg
Message-ID: <94C682931C08B048B7A8645303FDC9F36EBA754EAE@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36EBA754E5C@PUEXCB1B.nanterre.francetelecom.fr> <34AF6119-6069-4012-90BF-D1EF3BB29251@cisco.com>, <94C682931C08B048B7A8645303FDC9F36EBA754E92@PUEXCB1B.nanterre.francetelecom.fr> <A8111535-B94B-4CB1-98A3-95C582DFFAD0@cisco.com>
In-Reply-To: <A8111535-B94B-4CB1-98A3-95C582DFFAD0@cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F36EBA754EAEPUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.25.85421
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Dhc Chairs \(dhc-chairs@tools.ietf.org\)" <dhc-chairs@tools.ietf.org>, "draft-ietf-pcp-dhcp@tools.ietf.org" <draft-ietf-pcp-dhcp@tools.ietf.org>, "pcp-chairs@tools.ietf.org" <pcp-chairs@tools.ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-pcp-dhcp: Exit from the loop
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Mar 2013 16:06:20 -0000

--_000_94C682931C08B048B7A8645303FDC9F36EBA754EAEPUEXCB1Bnante_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Re-,

To be more accurate, it was not rejected as per Ted's conclusion available =
here: http://www.ietf.org/mail-archive/web/dhcwg/current/msg13646.html

Cheers,
Med

________________________________
De : Bernie Volz (volz) [mailto:volz@cisco.com]
Envoy=E9 : lundi 25 mars 2013 17:01
=C0 : BOUCADAIR Mohamed OLNC/OLN
Cc : Dhc Chairs (dhc-chairs@tools.ietf.org); Ted Lemon; pcp-chairs@tools.ie=
tf.org; draft-ietf-pcp-dhcp@tools.ietf.org; dhcwg@ietf.org
Objet : Re: draft-ietf-pcp-dhcp: Exit from the loop

Just to be clear - that approach was rejected. There is discussion in the o=
ption guidelines draft.

- Bernie

On Mar 25, 2013, at 11:56 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Re-,

The draft does not define both; only one format is defined.

The issue is more related to what was discussed in this list: the use of ut=
f-8 encoding.
The conclusion of that discussion is there was no consensus to adopt nor to=
 reject that approach.

Cheers,
Med

________________________________
De : Bernie Volz (volz) [mailto:volz@cisco.com]
Envoy=E9 : lundi 25 mars 2013 16:51
=C0 : BOUCADAIR Mohamed OLNC/OLN
Cc : Dhc Chairs (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org=
>); Ted Lemon; pcp-chairs@tools.ietf.org<mailto:pcp-chairs@tools.ietf.org>;=
 draft-ietf-pcp-dhcp@tools.ietf.org<mailto:draft-ietf-pcp-dhcp@tools.ietf.o=
rg>; dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Objet : Re: draft-ietf-pcp-dhcp: Exit from the loop

You need to pick either fqdn or address - not both. See the option guidelin=
es draft. DHC is unlikely to support this work if you don't follow option g=
uidelines.

- Bernie

On Mar 25, 2013, at 11:31 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Dear all,

I understood no conclusion was reached in the previous pcp meeting for this=
 I-D.
The version available at http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06 =
reflects the consensus of the pcp wg but Ted is not happy with that design.

It seems we are looping here:
* The approach of using two formats was documented in a previous version bu=
t it was removed after a review from Bernie.
* RFC1035-based encoding was documented in a previous version but it was re=
moved because the consensus of the pcp working group is no to over specify =
the options to be dns-specific.
* A more detailed background is provided here: http://www.ietf.org/proceedi=
ngs/86/slides/slides-86-pcp-4.pdf.

As I have two opposite signals, I don't know how to proceed. This is why I'=
m expanding this to dhc chairs to have your feedback too.

Cheers,
Med

--_000_94C682931C08B048B7A8645303FDC9F36EBA754EAEPUEXCB1Bnante_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18702"></HEAD>
<BODY dir=3Dauto>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D120250516-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Re-,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D120250516-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D120250516-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">To be more accurate, it was not rejected as p=
er Ted's=20
conclusion available here: </FONT></SPAN><SPAN class=3D120250516-25032013><=
FONT=20
color=3D#0000ff size=3D2 face=3D"Courier New"><A=20
href=3D"http://www.ietf.org/mail-archive/web/dhcwg/current/msg13646.html">h=
ttp://www.ietf.org/mail-archive/web/dhcwg/current/msg13646.html</A></FONT><=
/SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D120250516-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D120250516-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D120250516-25032013><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Med</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; MARGIN-RIGHT: 0px"=20
dir=3Dltr>
  <DIV dir=3Dltr lang=3Dfr class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>De&nbsp;:</B> Bernie Volz (volz)=20
  [mailto:volz@cisco.com] <BR><B>Envoy=E9&nbsp;:</B> lundi 25 mars 2013=20
  17:01<BR><B>=C0&nbsp;:</B> BOUCADAIR Mohamed OLNC/OLN<BR><B>Cc&nbsp;:</B>=
 Dhc=20
  Chairs (dhc-chairs@tools.ietf.org); Ted Lemon; pcp-chairs@tools.ietf.org;=
=20
  draft-ietf-pcp-dhcp@tools.ietf.org; dhcwg@ietf.org<BR><B>Objet&nbsp;:</B>=
 Re:=20
  draft-ietf-pcp-dhcp: Exit from the loop<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>Just to be clear - that approach was rejected. There is discussion i=
n the=20
  option guidelines draft.</DIV>
  <DIV><BR>- Bernie</DIV>
  <DIV><BR>On Mar 25, 2013, at 11:56 AM, "<A=20
  href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</A>"=20
  &lt;<A=20
  href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</A>&gt;=20
  wrote:<BR><BR></DIV>
  <BLOCKQUOTE type=3D"cite">
    <DIV>
    <META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18702">
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3D"Courier New">Re-,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3D"Courier New">The draft does not define both; only one =
format is=20
    defined.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3D"Courier New">The issue is more related to&nbsp;what wa=
s=20
    discussed in this list:&nbsp;the use of utf-8=20
    encoding.&nbsp;</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3D"Courier New">The conclusion of that&nbsp;discussion is=
 there=20
    was no consensus to adopt nor to reject=20
    that&nbsp;approach.&nbsp;</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3D"Courier New">Cheers,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D111465115-25032013><FONT colo=
r=3D#0000ff=20
    size=3D2 face=3D"Courier New">Med</FONT></SPAN></DIV><BR>
    <BLOCKQUOTE=20
    style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px"=20
    dir=3Dltr>
      <DIV dir=3Dltr lang=3Dfr class=3DOutlookMessageHeader align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT size=3D2 face=3DTahoma><B>De&nbsp;:</B> Bernie Volz (volz) [<A=
=20
      href=3D"mailto:volz@cisco.com">mailto:volz@cisco.com</A>]=20
      <BR><B>Envoy=E9&nbsp;:</B> lundi 25 mars 2013 16:51<BR><B>=C0&nbsp;:<=
/B>=20
      BOUCADAIR Mohamed OLNC/OLN<BR><B>Cc&nbsp;:</B> Dhc Chairs (<A=20
      href=3D"mailto:dhc-chairs@tools.ietf.org">dhc-chairs@tools.ietf.org</=
A>);=20
      Ted Lemon; <A=20
      href=3D"mailto:pcp-chairs@tools.ietf.org">pcp-chairs@tools.ietf.org</=
A>; <A=20
      href=3D"mailto:draft-ietf-pcp-dhcp@tools.ietf.org">draft-ietf-pcp-dhc=
p@tools.ietf.org</A>;=20
      <A href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</A><BR><B>Objet&nbsp=
;:</B>=20
      Re: draft-ietf-pcp-dhcp: Exit from the loop<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV>You need to pick either fqdn or address - not both. See the opti=
on=20
      guidelines draft. DHC is unlikely to support this work if you don't f=
ollow=20
      option guidelines.</DIV>
      <DIV><BR>- Bernie</DIV>
      <DIV><BR>On Mar 25, 2013, at 11:31 AM, "<A=20
      href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange=
.com</A>"=20
      &lt;<A=20
      href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange=
.com</A>&gt;=20
      wrote:<BR><BR></DIV>
      <BLOCKQUOTE type=3D"cite">
        <DIV>
        <META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18702">
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013>Dear&nbsp;all,</SPAN></FONT></DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013><SPAN class=3D620055514-25032013>I=20
        understood&nbsp;no conclusion was reached in the previous pcp meeti=
ng=20
        for this I-D.</SPAN></SPAN></FONT></DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013><SPAN class=3D620055514-25032013>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013><SPAN class=3D620055514-25032013>The ver=
sion=20
        available at <A=20
        href=3D"http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06">http://t=
ools.ietf.org/html/draft-ietf-pcp-dhcp-06</A>&nbsp;reflects=20
        the consensus of the pcp wg but Ted is not happy with that=20
        design.</SPAN></SPAN></FONT></DIV></SPAN></SPAN></FONT></DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013><SPAN=20
        class=3D620055514-25032013></SPAN></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-25=
032013>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-25=
032013>It=20
        seems we are looping here:</SPAN></FONT></DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-25=
032013>*=20
        The approach of using two formats was documented in a previous vers=
ion=20
        but it was removed after a review from Bernie.</SPAN></FONT></DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN class=3D620055514-25=
032013>*=20
        RFC1035-based encoding was documented in a previous version but it =
was=20
        removed because the consensus of the pcp working group is no to ove=
r=20
        specify the options to be=20
        dns-specific.</SPAN></FONT></DIV></SPAN></FONT></DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013></SPAN></FONT><FONT size=3D2=20
        face=3D"Courier New"><SPAN class=3D620055514-25032013>* </SPAN></FO=
NT><FONT=20
        size=3D2 face=3D"Courier New"><SPAN class=3D620055514-25032013><FON=
T size=3D2=20
        face=3D"Courier New"><SPAN class=3D620055514-25032013>A more detail=
ed=20
        background is provided here: </SPAN></FONT><FONT size=3D2=20
        face=3D"Courier New"><SPAN class=3D620055514-25032013><A=20
        href=3D"http://www.ietf.org/proceedings/86/slides/slides-86-pcp-4.p=
df">http://www.ietf.org/proceedings/86/slides/slides-86-pcp-4.pdf</A>.</SPA=
N></FONT></SPAN></FONT></DIV><FONT=20
        size=3D2 face=3D"Courier New">
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013></SPAN></FONT>&nbsp;</DIV></FONT>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013>As&nbsp;I have two opposite signals,&nbs=
p;I=20
        don't know how to proceed. This is why I'm expanding this to dhc ch=
airs=20
        to have your feedback too.</SPAN></FONT></DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013></SPAN></FONT>&nbsp;</DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013>Cheers,</SPAN></FONT></DIV>
        <DIV><FONT size=3D2 face=3D"Courier New"><SPAN=20
        class=3D620055514-25032013>Med</SPAN></FONT></DIV></DIV></BLOCKQUOT=
E></BLOCKQUOTE></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--_000_94C682931C08B048B7A8645303FDC9F36EBA754EAEPUEXCB1Bnante_--

From volz@cisco.com  Mon Mar 25 09:12:38 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A64D121E8054 for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 09:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vIjek9taEx9b for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 09:12:37 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 644A621F9022 for <dhcwg@ietf.org>; Mon, 25 Mar 2013 09:12:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14701; q=dns/txt; s=iport; t=1364227957; x=1365437557; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=NO+xiJ1FKWODPuF5zrXBhAl2smnG2pZ64/NYZEaPKgg=; b=Uzl7Pl2fMCq8c8028Gx+NwhkxBABTXBt1Nnhs87Gi2QP9hgo/AHJQBLX IHc5gD5/AJQHAAQjZTPz1KwY0TMwVIVR/8uhJ6U8YhmLr88dQ352e0Ivh kfRAkL2vYCLkzOKtF7iLKZDnxqqaiG5sM/GO2s2SlYLkC3ZVq6OOmIJ2t o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAPR1UFGtJXG8/2dsb2JhbABDvUQBiCmCBhZtB4IkAQEBAgJsDRACAQg/BzIUEQEBBA4FCYgLDMJ1jVgQgTAGAYJfYQOIQY4mgR+PZYMKgXM
X-IronPort-AV: E=Sophos;i="4.84,905,1355097600";  d="scan'208,217";a="188176027"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-9.cisco.com with ESMTP; 25 Mar 2013 16:12:37 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2PGCa8R010459 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Mar 2013 16:12:36 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Mon, 25 Mar 2013 11:12:36 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: draft-ietf-pcp-dhcp: Exit from the loop
Thread-Index: Ac4pbclNF6ugk1fSTtSaAP9fTWNoigAArkm7AAAJODAAAFYy3wAAI9rgAABALcM=
Date: Mon, 25 Mar 2013 16:12:35 +0000
Message-ID: <29E6AEC7-9D1F-4137-BB0D-0455095FA336@cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36EBA754E5C@PUEXCB1B.nanterre.francetelecom.fr> <34AF6119-6069-4012-90BF-D1EF3BB29251@cisco.com>, <94C682931C08B048B7A8645303FDC9F36EBA754E92@PUEXCB1B.nanterre.francetelecom.fr> <A8111535-B94B-4CB1-98A3-95C582DFFAD0@cisco.com>, <94C682931C08B048B7A8645303FDC9F36EBA754EAE@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EBA754EAE@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_29E6AEC79D1F4137BB0D0455095FA336ciscocom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Dhc Chairs \(dhc-chairs@tools.ietf.org\)" <dhc-chairs@tools.ietf.org>, "draft-ietf-pcp-dhcp@tools.ietf.org" <draft-ietf-pcp-dhcp@tools.ietf.org>, "pcp-chairs@tools.ietf.org" <pcp-chairs@tools.ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-pcp-dhcp: Exit from the loop
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Mar 2013 16:12:38 -0000
X-List-Received-Date: Mon, 25 Mar 2013 16:12:38 -0000

--_000_29E6AEC79D1F4137BB0D0455095FA336ciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Ted's email said:

While this does not mean that this option format has been formally rejected=
 by the working group, I would expect that an option that attempted to use =
this format would have similar difficulty gaining consensus in the working =
group.

My interpretation is that it will have a difficult road and if you want it =
to be OKed, follow the option guidelines.

I should have indicated all of my discussion is with WG hat chair off as th=
ese are my opinions.

- Bernie

On Mar 25, 2013, at 12:06 PM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Re-,

To be more accurate, it was not rejected as per Ted's conclusion available =
here: http://www.ietf.org/mail-archive/web/dhcwg/current/msg13646.html

Cheers,
Med

________________________________
De : Bernie Volz (volz) [mailto:volz@cisco.com]
Envoy=E9 : lundi 25 mars 2013 17:01
=C0 : BOUCADAIR Mohamed OLNC/OLN
Cc : Dhc Chairs (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org=
>); Ted Lemon; pcp-chairs@tools.ietf.org<mailto:pcp-chairs@tools.ietf.org>;=
 draft-ietf-pcp-dhcp@tools.ietf.org<mailto:draft-ietf-pcp-dhcp@tools.ietf.o=
rg>; dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Objet : Re: draft-ietf-pcp-dhcp: Exit from the loop

Just to be clear - that approach was rejected. There is discussion in the o=
ption guidelines draft.

- Bernie

On Mar 25, 2013, at 11:56 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Re-,

The draft does not define both; only one format is defined.

The issue is more related to what was discussed in this list: the use of ut=
f-8 encoding.
The conclusion of that discussion is there was no consensus to adopt nor to=
 reject that approach.

Cheers,
Med

________________________________
De : Bernie Volz (volz) [mailto:volz@cisco.com]
Envoy=E9 : lundi 25 mars 2013 16:51
=C0 : BOUCADAIR Mohamed OLNC/OLN
Cc : Dhc Chairs (dhc-chairs@tools.ietf.org<mailto:dhc-chairs@tools.ietf.org=
>); Ted Lemon; pcp-chairs@tools.ietf.org<mailto:pcp-chairs@tools.ietf.org>;=
 draft-ietf-pcp-dhcp@tools.ietf.org<mailto:draft-ietf-pcp-dhcp@tools.ietf.o=
rg>; dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Objet : Re: draft-ietf-pcp-dhcp: Exit from the loop

You need to pick either fqdn or address - not both. See the option guidelin=
es draft. DHC is unlikely to support this work if you don't follow option g=
uidelines.

- Bernie

On Mar 25, 2013, at 11:31 AM, "mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucada=
ir@orange.com>> wrote:

Dear all,

I understood no conclusion was reached in the previous pcp meeting for this=
 I-D.
The version available at http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06 =
reflects the consensus of the pcp wg but Ted is not happy with that design.

It seems we are looping here:
* The approach of using two formats was documented in a previous version bu=
t it was removed after a review from Bernie.
* RFC1035-based encoding was documented in a previous version but it was re=
moved because the consensus of the pcp working group is no to over specify =
the options to be dns-specific.
* A more detailed background is provided here: http://www.ietf.org/proceedi=
ngs/86/slides/slides-86-pcp-4.pdf.

As I have two opposite signals, I don't know how to proceed. This is why I'=
m expanding this to dhc chairs to have your feedback too.

Cheers,
Med

--_000_29E6AEC79D1F4137BB0D0455095FA336ciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body dir=3D"auto">
<div style=3D"-webkit-text-size-adjust: auto; ">Ted's email said:&nbsp;</di=
v>
<div>
<pre style=3D"-webkit-text-size-adjust: auto; word-wrap: break-word; width:=
 867px; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-co=
mposition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-fr=
ame-color: rgba(77, 128, 180, 0.230469); ">While this does not mean that th=
is option format has been formally rejected by the working group, I would e=
xpect that an option that attempted to use this format would have similar d=
ifficulty gaining consensus in the working group.<br></pre>
My interpretation is that it will have a difficult road and if you want it =
to be OKed, follow the option guidelines.</div>
<div><br>
</div>
<div>I should have indicated all of my discussion is with WG hat chair off =
as these are my opinions.</div>
<div><br>
</div>
<div>- Bernie</div>
<div style=3D"-webkit-text-size-adjust: auto; "><br>
On Mar 25, 2013, at 12:06 PM, &quot;<a href=3D"mailto:mohamed.boucadair@ora=
nge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:moham=
ed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite" style=3D"-webkit-text-size-adjust: auto; ">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<div dir=3D"ltr" align=3D"left"><span class=3D"120250516-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Re-,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"120250516-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"120250516-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">To be more accurate, it was=
 not rejected as per Ted's conclusion available here:
</font></span><span class=3D"120250516-25032013"><font color=3D"#0000ff" si=
ze=3D"2" face=3D"Courier New"><a href=3D"http://www.ietf.org/mail-archive/w=
eb/dhcwg/current/msg13646.html">http://www.ietf.org/mail-archive/web/dhcwg/=
current/msg13646.html</a></font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"120250516-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"120250516-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Cheers,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"120250516-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Med</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"fr" class=3D"OutlookMessageHeader" align=3D"left">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>De&nbsp;:</b> Bernie Volz (volz) [<a hr=
ef=3D"mailto:volz@cisco.com">mailto:volz@cisco.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> lundi 25 mars 2013 17:01<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed OLNC/OLN<br>
<b>Cc&nbsp;:</b> Dhc Chairs (<a href=3D"mailto:dhc-chairs@tools.ietf.org">d=
hc-chairs@tools.ietf.org</a>); Ted Lemon;
<a href=3D"mailto:pcp-chairs@tools.ietf.org">pcp-chairs@tools.ietf.org</a>;=
 <a href=3D"mailto:draft-ietf-pcp-dhcp@tools.ietf.org">
draft-ietf-pcp-dhcp@tools.ietf.org</a>; <a href=3D"mailto:dhcwg@ietf.org">d=
hcwg@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: draft-ietf-pcp-dhcp: Exit from the loop<br>
</font><br>
</div>
<div></div>
<div>Just to be clear - that approach was rejected. There is discussion in =
the option guidelines draft.</div>
<div><br>
- Bernie</div>
<div><br>
On Mar 25, 2013, at 11:56 AM, &quot;<a href=3D"mailto:mohamed.boucadair@ora=
nge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:moham=
ed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Re-,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">The draft does not define b=
oth; only one format is defined.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">The issue is more related t=
o&nbsp;what was discussed in this list:&nbsp;the use of utf-8 encoding.&nbs=
p;</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">The conclusion of that&nbsp=
;discussion is there was no consensus to adopt nor to reject that&nbsp;appr=
oach.&nbsp;</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Cheers,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"111465115-25032013"><font co=
lor=3D"#0000ff" size=3D"2" face=3D"Courier New">Med</font></span></div>
<br>
<blockquote style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MAR=
GIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir=3D"ltr">
<div dir=3D"ltr" lang=3D"fr" class=3D"OutlookMessageHeader" align=3D"left">
<hr tabindex=3D"-1">
<font size=3D"2" face=3D"Tahoma"><b>De&nbsp;:</b> Bernie Volz (volz) [<a hr=
ef=3D"mailto:volz@cisco.com">mailto:volz@cisco.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> lundi 25 mars 2013 16:51<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed OLNC/OLN<br>
<b>Cc&nbsp;:</b> Dhc Chairs (<a href=3D"mailto:dhc-chairs@tools.ietf.org">d=
hc-chairs@tools.ietf.org</a>); Ted Lemon;
<a href=3D"mailto:pcp-chairs@tools.ietf.org">pcp-chairs@tools.ietf.org</a>;=
 <a href=3D"mailto:draft-ietf-pcp-dhcp@tools.ietf.org">
draft-ietf-pcp-dhcp@tools.ietf.org</a>; <a href=3D"mailto:dhcwg@ietf.org">d=
hcwg@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: draft-ietf-pcp-dhcp: Exit from the loop<br>
</font><br>
</div>
<div></div>
<div>You need to pick either fqdn or address - not both. See the option gui=
delines draft. DHC is unlikely to support this work if you don't follow opt=
ion guidelines.</div>
<div><br>
- Bernie</div>
<div><br>
On Mar 25, 2013, at 11:31 AM, &quot;<a href=3D"mailto:mohamed.boucadair@ora=
nge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:moham=
ed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.18702">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Dear&nbsp;all,</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">I understood&nbsp;no conclusion was r=
eached in the previous pcp meeting for this I-D.</span></span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013">The version available at
<a href=3D"http://tools.ietf.org/html/draft-ietf-pcp-dhcp-06">http://tools.=
ietf.org/html/draft-ietf-pcp-dhcp-06</a>&nbsp;reflects the consensus of the=
 pcp wg but Ted is not happy with that design.</span></span></font></div>
</span></span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"><span class=3D"620055514-25032013"></span></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">It seems we are looping here:</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">* The approach of using two formats was documented in a previous version=
 but it was removed after a review from Bernie.</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">* RFC1035-based encoding was documented in a previous version but it was=
 removed because the consensus of the pcp working group is no to over speci=
fy the options to be dns-specific.</span></font></div>
</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005=
5514-25032013">*
</span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005551=
4-25032013"><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-=
25032013">A more detailed background is provided here:
</span></font><font size=3D"2" face=3D"Courier New"><span class=3D"62005551=
4-25032013"><a href=3D"http://www.ietf.org/proceedings/86/slides/slides-86-=
pcp-4.pdf">http://www.ietf.org/proceedings/86/slides/slides-86-pcp-4.pdf</a=
>.</span></font></span></font></div>
<font size=3D"2" face=3D"Courier New">
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
</font>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">As&nbsp;I have two opposite signals,&nbsp;I don't know how to proceed. T=
his is why I'm expanding this to dhc chairs to have your feedback too.</spa=
n></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3"></span></font>&nbsp;</div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Cheers,</span></font></div>
<div><font size=3D"2" face=3D"Courier New"><span class=3D"620055514-2503201=
3">Med</span></font></div>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</body>
</html>

--_000_29E6AEC79D1F4137BB0D0455095FA336ciscocom_--

From tomasz.mrugalski@gmail.com  Mon Mar 25 10:00:54 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695FC21F9517 for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 10:00:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Czvz7q+kDuZn for <dhcwg@ietfa.amsl.com>; Mon, 25 Mar 2013 10:00:53 -0700 (PDT)
Received: from mail-ee0-f51.google.com (mail-ee0-f51.google.com [74.125.83.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7A321F9513 for <dhcwg@ietf.org>; Mon, 25 Mar 2013 10:00:53 -0700 (PDT)
Received: by mail-ee0-f51.google.com with SMTP id c4so240245eek.24 for <dhcwg@ietf.org>; Mon, 25 Mar 2013 10:00:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-tagtoolbar-keys:content-type :content-transfer-encoding; bh=aA1vBcgp5SEvL/fOEmDtaXhLRcQA2CKLwA0rDdaWvV8=; b=mRgx28vtS1heVw89B0UDoYb8VhCO5YiM5j2LwiKKE/iYNy3Iyra2PC9gzxT+eppSu5 Zox+AcnU0ZpB8SImctsspTXLlYA1DSzcAHrN6Hou2gf55mDSEIfoSw99dZamx4iVNBsp Wr+Fi9oPumyxLaSqDK0Kgapek/5Ell4NZcMvtBK37mbtQyHdzVYPaPOfHFy89qcCqZIp YS2/tOIYGcRbdypRXEpY1M0yIx8PpICbFkkegZREdOzEfzMgMCLyD4TmzCW/EbF4FBl+ EA8jTdusZdk8sRq+/DPxiM1qy3h8HKleZME7v1b4d1xODBSKvG+QxpFllMdKH6O0+B3g UhMQ==
X-Received: by 10.14.5.137 with SMTP id 9mr23206095eel.30.1364230852703; Mon, 25 Mar 2013 10:00:52 -0700 (PDT)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPS id r4sm20229480eeo.12.2013.03.25.10.00.49 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 25 Mar 2013 10:00:50 -0700 (PDT)
Message-ID: <515082BD.3080403@gmail.com>
Date: Mon, 25 Mar 2013 18:00:45 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <94C682931C08B048B7A8645303FDC9F36EBA754E5C@PUEXCB1B.nanterre.francetelecom.fr> <34AF6119-6069-4012-90BF-D1EF3BB29251@cisco.com>, <94C682931C08B048B7A8645303FDC9F36EBA754E92@PUEXCB1B.nanterre.francetelecom.fr> <A8111535-B94B-4CB1-98A3-95C582DFFAD0@cisco.com>, <94C682931C08B048B7A8645303FDC9F36EBA754EAE@PUEXCB1B.nanterre.francetelecom.fr> <29E6AEC7-9D1F-4137-BB0D-0455095FA336@cisco.com>
In-Reply-To: <29E6AEC7-9D1F-4137-BB0D-0455095FA336@cisco.com>
X-TagToolbar-Keys: D20130325180045429
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-pcp-dhcp@tools.ietf.org" <draft-ietf-pcp-dhcp@tools.ietf.org>, "pcp-chairs@tools.ietf.org" <pcp-chairs@tools.ietf.org>
Subject: Re: [dhcwg] draft-ietf-pcp-dhcp: Exit from the loop
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 25 Mar 2013 17:00:54 -0000

On 25.03.2013 17:12, Bernie Volz (volz) wrote:
> Ted's email said:
> 
> While this does not mean that this option format has been formally
> rejected by the working group, I would expect that an option that
> attempted to use this format would have similar difficulty gaining
> consensus in the working group.
> 
> My interpretation is that it will have a difficult road and if you
> want it to be OKed, follow the option guidelines.
> 
> I should have indicated all of my discussion is with WG hat chair off
> as these are my opinions.
With my DHC WG hat chair off: Although my name is mentioned in the
acknowledgements section, I did not support this particular option
format. When I was reviewing it a long time ago (-00), it had a single
FQDN option defined.

It seems that you don't care about IP family and use DHCPv4 and DHCPv6
as a transparent delivery mechanism. I remember that Dave Thaler
commented on it some time ago. For example it is ok to deliver PCP
server IPv4 address over DHCPv6 or have fqdn delivered over DHCPv4 which
resolves to AAAA only? If that is the case, I strongly suggest you
should use FQDN format.

If you need multiple PCP servers to communicate to the clients, just put
multiple instances of the option. This is normal in DHCPv6 as each
option is handled independently.

I haven't read the whole -06 draft, but just briefly looked through it
and it raises some question marks. The validation rules mentioned in
section 4.2 and 3.2 are not sufficient. We had this discussion before
(when talking about address-name-encoding draft), but some of the issues
are:

- There are more rules that govern valid fqdn. Label length equal or
shorter than 63 octets is just one of them. See RFC3315, section 8 (or
RFC1035, section 3.1 directly).

- the rules for delivering PCP server info over DHCPv4 and DHCPv6 are
inconsistent. For example you allow IPv6 address enclosed in brackets in
DHCPv4, but not in DHCPv6.

- by allowing UTF8 you bring in a lot of complexity with it. This is
something that will make all DHCPv6 clients noticeably larger and more
complex to implement. It is difficult to write validation rules for UTF8
string as there are many nuances there (e.g. many different hyphens,
accented characters or even completely different charsets, like chineese
or japaneese are there? Which of them are allowed and which are not?).
The end result is that the implementors would likely be forced to pass
received verbatim content to getaddrinfo() or choose to not support this
option. Passing the unverified content directly to internal host API is
a big security issue as it allows to exploit any discovered
vulnerabilities remotely.

In general I'd like to just +1 to what Bernie said. Please try to follow
dhc-option-guidelines if possible. This is what the DHC WG recommends.
At least that's my perception.

BTW dhc-option-guidelines will go into WGLC in around 2 weeks, so you
can bring in the UTF-8 encoding issue there.

Tomek

p.s.
Removing Bernie, Med, Ted and dhc-chairs from the recipients list as
they are all subscribed to dhcwg list.

From jouni.nospam@gmail.com  Tue Mar 26 02:09:27 2013
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5927A21F8837 for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 02:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bzaot3gNM716 for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 02:09:26 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 556E621F8825 for <dhcwg@ietf.org>; Tue, 26 Mar 2013 02:09:26 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id er20so13214544lab.32 for <dhcwg@ietf.org>; Tue, 26 Mar 2013 02:09:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=6WS3eT5jS+CIIjf/KyzSjR/Qc5aVqVF7sMHHM+eE4T0=; b=OGMyBrUVPZW+lW8nPGBKkyKP5tFQrKLdamvJsjfDTr0KOwUn5tyB+cxjaK83bNA5EI HGHw23njCqN+2InEOep0jZni8lBZXahqe42bcPEeyvS3hmGY1lQxX9LSpVkfBBG/smd2 r+n6WOKsW+pVj8DhMd2Smucbo35fLhFfTwuha7GK/83UHfFVlyKF3Og+hztQX02VpZO0 aE0jN9HAdyLVkhT/i8F4c/bYrpjMN+IlksoRNXcE6MaBdCk6xQu7zyXBDv+FblSqrM14 v/WWM5JOsxKCLg+uy7ZPfR8pB/nycthhk6UbT5BEzeX21XTLoGlZ71ctoNjLBFX26m5p HlIA==
X-Received: by 10.152.87.243 with SMTP id bb19mr5956070lab.12.1364288965307; Tue, 26 Mar 2013 02:09:25 -0700 (PDT)
Received: from [192.168.250.232] ([194.100.71.98]) by mx.google.com with ESMTPS id mq7sm6302456lab.1.2013.03.26.02.09.23 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Mar 2013 02:09:24 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <511AA538.2000902@trans-nt.com>
Date: Tue, 26 Mar 2013 11:09:21 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <4C872C87-9D7E-473C-86CE-F1D7CD7FCCA9@gmail.com>
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com>
To: Hiroki Nakano <cas@trans-nt.com>
X-Mailer: Apple Mail (2.1503)
Cc: dhcwg@ietf.org, "<dhc-chairs@tools.ietf.org>" <dhc-chairs@tools.ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "cas.nakano@gmail.com" <cas.nakano@gmail.com>
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Mar 2013 09:09:27 -0000

I find it quite interesting and slightly surprising IEEE is
working on this. In cellular space (3gpp) we have had about
equivalent mechanism at the NAS protocol layer from the
beginning. It works but has always been a bit of headache,
since multiple ways to do the same thing with loads of optional
features on different layers caused nasty implementation/deployment
challenges. I hope IEEE does this better now that they are doing it ;)

- Jouni


On Feb 12, 2013, at 10:25 PM, Hiroki Nakano <cas@trans-nt.com> wrote:

> Dear all,
> 
> I'm participating in IEEE 802.11 WG TGai task group
> which is for FILS (Fast Initiali Link Setup).
> They are working for speeding up of 802.11 process
> and trying to provide a new framework for higher
> layer protocols.
> 
> I'd like to introduce the overview of prospective
> 802.11ai specification and discuss usages of DHCP
> on it with DHC WG people in March.
> The followings are a brief introduction.
> 
> TGai supposes Wireless LAN is used in very crowded
> envirionment such as railway stations in a giant metropolis.
> TGai also supposes moving hosts through the front of
> Access Points. In these cases, it is effective to
> reduce management frames of 802.11, especially
> frames for probing APs, authentication and association.
> The current framework takes a few seconds to set up
> network connectivity before starting to communicate.
> The target of TGai is under one second.
> 
> TGai is trying to reduce management frames of 802.11 itself,
> and in addition provide framework for higher layers such as
> IP to send and receive packets during 802.11 association
> process. The currently proposed framework provides
> "ONE round-trip packet exchange" by piggybacking on
> 802.11 Association Request/Response frames.
> 
> My interest is how to fit DHCP to this framework.
> In case of DHCPv4, this is achieved by using
> Rapid Commit Option (RFC4039) and making some additional
> and trivial rules.
> In case of DHCPv6, we have to use both RA and DHCPv6.
> In addition, DAD and randomly generated addresses have
> to be considered. Share your idea, please.
> 
> 802.11 TGai is still going on and its specification is
> subject to change, but I'd like to discuss in IETF
> DHCP issues related to 802.11ai and arrange I-D according
> to the progress of TGai task group.
> 
> Regards,
> 
> Hiroki Nakano
> Trans New Technology, Inc. <cas@trans-nt.com>
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From tomasz.mrugalski@gmail.com  Tue Mar 26 04:29:04 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9321D21F8A4E; Tue, 26 Mar 2013 04:29:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ss6cyTcXq-7S; Tue, 26 Mar 2013 04:29:04 -0700 (PDT)
Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com [74.125.83.47]) by ietfa.amsl.com (Postfix) with ESMTP id BE87921F8A3F; Tue, 26 Mar 2013 04:28:53 -0700 (PDT)
Received: by mail-ee0-f47.google.com with SMTP id t10so701773eei.6 for <multiple recipients>; Tue, 26 Mar 2013 04:28:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-tagtoolbar-keys :x-forwarded-message-id:content-type:content-transfer-encoding; bh=PzOP7Mf9rfhmWYDUSlprk4hhyrBssBoac0px/11dHY8=; b=Q+N1jLD6aAMWWiyUBHckiQyLS6h8DCCXork7S2cUUtU0+hBGHnA2WYD0hL/POtZfCs o0h313JxrFsN7aC+kYMGFT6XlKZKpl3I19Bmcn3RerfCer21pHHwVr/n8oEqSyrWCoK3 5i4QV7VcjDex5pt2La2xlHuuByXQ3NEUBdy8SgFaRlMgbV+bf9Q7/d8NeIR/46AqhKjr guoCaH4ca6tgppIuLb9sZFgyJCfRi6wXjA7dW3HGhobuvZfsTDnWWC7oYH61WotXpApA CIt33y4Iz7MlAnfE1CSInmZ3A8cpP3EjWAkUOsvwSazIEtdG1O0t7ZMhYinMtH36+FRZ pRoQ==
X-Received: by 10.14.0.73 with SMTP id 49mr44370775eea.21.1364297332840; Tue, 26 Mar 2013 04:28:52 -0700 (PDT)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPS id t4sm24476616eel.0.2013.03.26.04.28.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Mar 2013 04:28:51 -0700 (PDT)
Message-ID: <5151866D.8010500@gmail.com>
Date: Tue, 26 Mar 2013 12:28:45 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
References: <515123B7.2010303@ericsson.com>
In-Reply-To: <515123B7.2010303@ericsson.com>
X-TagToolbar-Keys: D20130326122845900
X-Forwarded-Message-Id: <515123B7.2010303@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Softwires-wg <softwires@ietf.org>
Subject: [dhcwg] Softwires WG last call for draft-ietf-softwire-multicast-prefix-option-03
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Mar 2013 11:29:04 -0000

Hi,
I just wanted to bring up this draft to DHC WG attention. There's a
draft that started WGLC in Softwires today. Please comment on it.

Tomek

-------- Original Message --------
Subject: [Softwires] Working group last call for
draft-ietf-softwire-multicast-prefix-option-03
Date: Tue, 26 Mar 2013 00:27:35 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Softwires WG <softwires@ietf.org>
CC: Yong Cui <cuiyong@tsinghua.edu.cn>, Ralph Droms <rdroms@cisco.com>

Hi all,
  This message starts a two week softwire working group last call on
advancing the draft defining the DHCPv6 Option for IPv4-Embedded
Multicast and Unicast IPv6 Prefixes as a Standards Track RFC. The
authors believe that this version has addressed all the issues raised on
the document. The latest version of the draft is available at

http://www.ietf.org/id/draft-ietf-softwire-multicast-prefix-option-03.txt
http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-03

Substantive comments and statements of support/opposition for advancing
this document should be directed to the mailing list. Editorial
suggestions can be sent directly to the authors. The chairs will send in
their comments as well during the last call period. This last call will
conclude on April 9, 2013.

Regards,
Suresh & Yong
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires



From leaf.yeh.sdo@gmail.com  Tue Mar 26 05:51:02 2013
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9713321F8992 for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 05:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.552
X-Spam-Level: 
X-Spam-Status: No, score=-0.552 tagged_above=-999 required=5 tests=[AWL=3.046,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SNFB6du2pvrw for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 05:51:02 -0700 (PDT)
Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com [209.85.220.53]) by ietfa.amsl.com (Postfix) with ESMTP id 0B33D21F8928 for <dhcwg@ietf.org>; Tue, 26 Mar 2013 05:51:02 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id bh4so1370345pad.12 for <dhcwg@ietf.org>; Tue, 26 Mar 2013 05:51:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=ZZ2s8YnokBiIaEIwGi6G4eXJpSEYvnfJrDfc8XTzUBY=; b=BoqXCJv/Z3TK//FSqib+KacVKu4PEI2SiAg2eNm8GOSBXt2QGh6uYrRJnBbdegvgE0 5K0nhIZotGqBsThn8v1MbiRvLRP2vQKb3Dz2WUDNzy9k+n1C5rG/3QZ7md+ppnDKBytF b76e9ylp8M1bTHXUrSzjchkvOFk2lOufDljOhbSuaq5v+qSK9bEX7RNKouwNc8pUJtYv 98PVxpU+qE8CrMdwtYUgWRWvXbKnGElEsU3TKzik0fVhTlz8FOOzq3AsJziWmbs8QPIV HpYUAUsjINpejCgF0ySZHSgnNaBgMOqQ4dHmKForGgAOf1pskeKD4eXu/qDRSE4X0Pck RF4g==
X-Received: by 10.68.8.69 with SMTP id p5mr22924612pba.212.1364302261735; Tue, 26 Mar 2013 05:51:01 -0700 (PDT)
Received: from PC ([111.193.222.101]) by mx.google.com with ESMTPS id mz8sm17457556pbc.9.2013.03.26.05.50.57 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 26 Mar 2013 05:51:00 -0700 (PDT)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E184C093B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E184C093B@xmb-rcd-x04.cisco.com>
Date: Tue, 26 Mar 2013 20:50:53 +0800
Message-ID: <515199b4.28d3440a.3e9f.ffff9426@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0046_01CE2A63.9DBC3810"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac4ozYfaibHYbpaWSZS5v8sktAaRTwBUNORA
Content-Language: zh-cn
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 - Respond by April 8, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Mar 2013 12:51:02 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0046_01CE2A63.9DBC3810
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi folks,

 

Pls. feel free to review & comment on this draft. The authors will
appreciate those efforts to make it better.

 

 

Best Regards,

Leaf

 

 

 

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
Bernie Volz (volz)
Sent: Monday, March 25, 2013 4:26 AM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC - draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 - Respond
by April 8, 2013

 

Folks, the authors of draft-ietf-dhc-dhcpv6-prefix-pool-opt-02
<http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-02>  feel
it's ready for a WGLC.  There's been discussion and comment already, but
more eyes on this work are definitely needed to advance it.

 

At the time of this writing, there is no IPR reported against this draft.

 

Please review the draft and indicate whether or not you feel it is ready to
be published.  We have been getting very anemic responses to working group
messages recently.   Your response matters, so please do respond.

 

Tomek and I will evaluate consensus after April 8, 2013.

 

Thanks!

 

-          Bernie


------=_NextPart_000_0046_01CE2A63.9DBC3810
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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 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;
	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: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-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:1241215036;
	mso-list-type:hybrid;
	mso-list-template-ids:328336620 1899551708 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:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Hi folks,<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'>Pls. feel =
free to review &amp; comment on this draft. The authors will appreciate =
those efforts to make it better.<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><div><p =
class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US style=3D'color:#1F497D'>Best =
Regards,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US style=3D'color:#1F497D'>Leaf<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><span =
lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p></div><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><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-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] <b>On Behalf Of =
</b>Bernie Volz (volz)<br><b>Sent:</b> Monday, March 25, 2013 4:26 =
AM<br><b>To:</b> dhcwg@ietf.org<br><b>Subject:</b> [dhcwg] WGLC - =
draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 - Respond by April 8, =
2013<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>Folks, the authors of <a =
href=3D"http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-=
02">draft-ietf-dhc-dhcpv6-prefix-pool-opt-02</a> feel it's ready for a =
WGLC.&nbsp; There's been discussion and comment already, but more eyes =
on this work are definitely needed to advance =
it.<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>At the time of this writing, there is no IPR reported =
against this draft.<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>Please review the draft and indicate whether or not you =
feel it is ready to be published.&nbsp; We have been getting very anemic =
responses to working group messages recently.&nbsp;&nbsp; Your response =
matters, so please do respond.<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 evaluate consensus =
after April 8, 2013.<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!<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>Bernie<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0046_01CE2A63.9DBC3810--


From sunqi.csnet.thu@gmail.com  Tue Mar 26 08:39:51 2013
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26D4A21F8C4C for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 08:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wIdxxTSqMF0u for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 08:39:50 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 405D421F8C3B for <dhcwg@ietf.org>; Tue, 26 Mar 2013 08:39:50 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id y10so3078302pdj.41 for <dhcwg@ietf.org>; Tue, 26 Mar 2013 08:39:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:date:references:to:message-id :mime-version:x-mailer; bh=K1X5stbU+EsrAz9wO+eiZxrtwvSOTE+USPu7oJwMKpY=; b=jOIVuVUwiC3/yJ6Cds1GedT34T6BNsZiwlF98vBiyaPrkBPYhgk84lzwp72FvNUTie 2dHdgVJv1ntHm+Pr+FGR7xZyuy8R+20iSSTz+M029VTus7SQ4nQR6avO4lw1Igvy/C1I 5R8V9hkHEn3ndwY922rT9sqhcpBU8A8Iu9IPirqs2xbNaGNcbvx6YqJq7pWDblQ4ZAJX 8ACD/1uV9Dqcot/2hf/pPrumqdeJHRv56cbPRXPukAntJ7lXsYpm9oo35tvbJ9oDjupz Fc193gEhXbHpKOgXJx5gKg0T5hsUJ6I3V5KuULG/H3jpfUIqVPUQTXi8yF8Z/IAKnVk6 oquQ==
X-Received: by 10.66.76.170 with SMTP id l10mr24347121paw.190.1364312386889; Tue, 26 Mar 2013 08:39:46 -0700 (PDT)
Received: from [192.168.1.102] ([124.207.32.214]) by mx.google.com with ESMTPS id zm1sm17904148pbc.26.2013.03.26.08.39.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Mar 2013 08:39:46 -0700 (PDT)
From: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-6--541882723
Date: Tue, 26 Mar 2013 23:39:33 +0800
References: <20130326150709.22188.23330.idtracker@ietfa.amsl.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Message-Id: <ADADE1B9-D6FA-4A3C-83CE-E0318644C517@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [dhcwg] Fwd: New Version Notification for draft-csl-dhc-dhcpv6-unknown-msg-3315update-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Mar 2013 15:39:51 -0000

--Apple-Mail-6--541882723
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


Dear all ,

Here is an initial version of a new draft, which describes what a DHCPv6 =
functional node should do if it receives an unknown message.  This =
specification aims to update RFC 3315, which didn't  specify the =
handling of unknown messages.

Please can you review the document. Comments are welcome.

Best Regards,
Qi Sun


Begin forwarded message:

> From: internet-drafts@ietf.org
> Date: 2013=E5=B9=B43=E6=9C=8826=E6=97=A5 =
=E4=B8=8B=E5=8D=8811=E6=97=B607=E5=88=8609=E7=A7=92=E6=A0=BC=E6=9E=97=E5=B0=
=BC=E6=B2=BB=E6=A0=87=E5=87=86=E6=97=B6=E9=97=B4+0800
> To: sunqi@csnet1.cs.tsinghua.edu.cn
> Cc: yong@csnet1.cs.tsinghua.edu.cn, mellon@nominum.com
> Subject: New Version Notification for =
draft-csl-dhc-dhcpv6-unknown-msg-3315update-00.txt
>=20
>=20
> A new version of I-D, =
draft-csl-dhc-dhcpv6-unknown-msg-3315update-00.txt
> has been successfully submitted by Qi Sun and posted to the
> IETF repository.
>=20
> Filename:	 draft-csl-dhc-dhcpv6-unknown-msg-3315update
> Revision:	 00
> Title:		 Handling Unknown DHCPv6 Messages
> Creation date:	 2013-03-26
> Group:		 Individual Submission
> Number of pages: 4
> URL:             =
http://www.ietf.org/internet-drafts/draft-csl-dhc-dhcpv6-unknown-msg-3315u=
pdate-00.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-csl-dhc-dhcpv6-unknown-msg-3315updat=
e
> Htmlized:        =
http://tools.ietf.org/html/draft-csl-dhc-dhcpv6-unknown-msg-3315update-00
>=20
>=20
> Abstract:
>   Dynamic Host Configuration Protocol version 6 (DHCPv6) isn't =
specific
>   about handling messages with unknown types.  This document describes
>   the problems and defines how a DHCPv6 function node should behave in
>   this case.
>=20
>=20
>=20
>=20
> The IETF Secretariat
>=20
>=20


--Apple-Mail-6--541882723
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">Dear all ,</div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><br></div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Here =
is an initial version of a new draft, which describes what a DHCPv6 =
functional node should do if it receives an unknown message. &nbsp;This =
specification aims to update RFC 3315, which didn't &nbsp;specify the =
handling of unknown messages.</div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br></div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">Please can you review =
the document. Comments are welcome.</div></div><div><br></div><div>Best =
Regards,</div>Qi =
Sun<br><br></div></span></div></span></div></span></span>
</div>

<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'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br><=
/span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>Date: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">2013=E5=B9=B43=E6=9C=8826=E6=97=A5 =
=E4=B8=8B=E5=8D=8811=E6=97=B607=E5=88=8609=E7=A7=92=E6=A0=BC=E6=9E=97=E5=B0=
=BC=E6=B2=BB=E6=A0=87=E5=87=86=E6=97=B6=E9=97=B4+0800<br></span></div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>To: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:sunqi@csnet1.cs.tsinghua.edu.cn">sunqi@csnet1.cs.tsinghua.e=
du.cn</a><br></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>Cc: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><a =
href=3D"mailto:yong@csnet1.cs.tsinghua.edu.cn">yong@csnet1.cs.tsinghua.edu=
.cn</a>, <a =
href=3D"mailto:mellon@nominum.com">mellon@nominum.com</a><br></span></div>=
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>New Version =
Notification for  =
draft-csl-dhc-dhcpv6-unknown-msg-3315update-00.txt</b><br></span></div><br=
><div><br>A new version of I-D, =
draft-csl-dhc-dhcpv6-unknown-msg-3315update-00.txt<br>has been =
successfully submitted by Qi Sun and posted to the<br>IETF =
repository.<br><br>Filename:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> =
draft-csl-dhc-dhcpv6-unknown-msg-3315update<br>Revision:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
00<br>Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span> Handling Unknown DHCPv6 Messages<br>Creation date:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
2013-03-26<br>Group:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> Individual Submission<br>Number =
of pages: 4<br>URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a=
 =
href=3D"http://www.ietf.org/internet-drafts/draft-csl-dhc-dhcpv6-unknown-m=
sg-3315update-00.txt">http://www.ietf.org/internet-drafts/draft-csl-dhc-dh=
cpv6-unknown-msg-3315update-00.txt</a><br>Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://datatracker.ietf.org/doc/draft-csl-dhc-dhcpv6-unknown-msg-3=
315update">http://datatracker.ietf.org/doc/draft-csl-dhc-dhcpv6-unknown-ms=
g-3315update</a><br>Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-csl-dhc-dhcpv6-unknown-msg-3315up=
date-00">http://tools.ietf.org/html/draft-csl-dhc-dhcpv6-unknown-msg-3315u=
pdate-00</a><br><br><br>Abstract:<br> &nbsp;&nbsp;Dynamic Host =
Configuration Protocol version 6 (DHCPv6) isn't specific<br> =
&nbsp;&nbsp;about handling messages with unknown types. &nbsp;This =
document describes<br> &nbsp;&nbsp;the problems and defines how a DHCPv6 =
function node should behave in<br> &nbsp;&nbsp;this =
case.<br><br><br><br><br>The IETF =
Secretariat<br><br><br></div></blockquote></div><br></body></html>=

--Apple-Mail-6--541882723--

From volz@cisco.com  Tue Mar 26 10:38:24 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D91521F86C1 for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 10:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l2nvP7DUv58m for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 10:38:23 -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 18A9B21F8558 for <dhcwg@ietf.org>; Tue, 26 Mar 2013 10:38:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6377; q=dns/txt; s=iport; t=1364319503; x=1365529103; h=from:to:subject:date:message-id:mime-version; bh=+5N2tK5xG6jJL5ah3+ZCGSBOfw6IjSz6ODKpqTdPFSk=; b=cGAX3PtRcXD3iiJE5U7Q3rwspAK4gImQFy6s3oZ0AlWGPnveRWAZnhc+ Qi2+h34nTc2GsoalV0hY/CqddAHoUCn3qFQbPefa9bBAssHRIOLU3gbOR 2BDe9oegNoZP35k0H+rfqIRKZJYBXVDKFldEfaKFrAUF4g07aCcm9YeVL Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAIDcUVGtJXHA/2dsb2JhbABDgkTBQYEGFm09giEBBC1BHQEqViYBBBuIDJ9/kRWPdokEhV2DF2EDp26DCoIo
X-IronPort-AV: E=Sophos;i="4.84,913,1355097600";  d="scan'208,217";a="191460989"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 26 Mar 2013 17:38:22 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r2QHcMBH025382 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 26 Mar 2013 17:38:22 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.004; Tue, 26 Mar 2013 12:38:20 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Interest in draft-ietf-dhc-host-gen-id-05 & draft-ietf-dhc-cga-config-dhcpv6-04
Thread-Index: Ac4qRzJCyXQ8x3r+QbOIdLOjhVdPkQ==
Date: Tue, 26 Mar 2013 17:38:21 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E184C46F7@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.65.135]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E184C46F7xmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] Interest in draft-ietf-dhc-host-gen-id-05 & draft-ietf-dhc-cga-config-dhcpv6-04
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Mar 2013 17:38:24 -0000

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

The authors of draft-ietf-dhc-host-gen-id-05 and draft-ietf-dhc-cga-config-=
dhcpv6-04 would like to know if the WG still has interest in this work or s=
omeone finds it of value and thus would like to see work continue.

When I asked at the Orlando IETF-86 DHC WG meeting, no one indicated any in=
terest.

But, the chairs would like to confirm this on the mailing list.

If we receive no expressions of interest by April 8th, 2013, the authors wi=
ll let these drafts expire (they are both adopted work items) and the chair=
s will change the status of these drafts to "Dead WG Document" (see RFC 617=
4, section 4.2.6).


-          Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E184C46F7xmbrcdx04ciscoc_
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:43064191;
	mso-list-type:hybrid;
	mso-list-template-ids:618274366 439503332 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:5;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New","serif";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
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">The authors of draft-ietf-dhc-host-gen-id-05 and dra=
ft-ietf-dhc-cga-config-dhcpv6-04 would like to know if the WG still has int=
erest in this work or someone finds it of value and thus would like to see =
work continue.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">When I asked at the Orlando IETF-86 DHC WG meeting, =
no one indicated any interest.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">But, the chairs would like to confirm this on the ma=
iling list.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If we receive no expressions of interest by April 8<=
sup>th</sup>, 2013, the authors will let these drafts expire (they are both=
 adopted work items) and the chairs will change the status of these drafts =
to &#8220;Dead WG Document&#8221; (see RFC 6174,
 section 4.2.6).<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]>Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E184C46F7xmbrcdx04ciscoc_--

From volz@cisco.com  Tue Mar 26 10:40:51 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5225C21F8BDE for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 10:40:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xtcc7KDfr1Qr for <dhcwg@ietfa.amsl.com>; Tue, 26 Mar 2013 10:40:50 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id A93C421F8BBC for <dhcwg@ietf.org>; Tue, 26 Mar 2013 10:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1673; q=dns/txt; s=iport; t=1364319650; x=1365529250; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=LSk+nXi8Z7w2/hP1KqHvOchkM1ygXGKZZ36cNwgls80=; b=f6ftDX33ATHXFzG+vIzoRg458qKxSIclPQQh15oT8ujzyINs9ubME4nw 2ugedqm540LrT3vgjcR4N90sKEcebkmFl5f/4VNz/1uE/w7riMKbNcvkl QZGjcGLzhK7FFcC/1lxTIVXqsh/pijumYNxEt9V5LqgJnXdXqMkg2NZGN c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFANTcUVGtJV2Y/2dsb2JhbABDxAWBBhZtPYIfAQEBBAEBATc0FwQCAQgRBAEBCxQJBycLFAcBAQUDAgQTCIgMDLEJj3IEgk6MEyYSBoJZYQOnboFUgTaCKA
X-IronPort-AV: E=Sophos;i="4.84,913,1355097600"; d="scan'208";a="191718086"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP; 26 Mar 2013 17:40:50 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2QHeoOx021963 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 26 Mar 2013 17:40:50 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0318.004; Tue, 26 Mar 2013 12:40:49 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [v6ops] Interest in DHCPv6 Route/DefRouter/Src-basedRoute configuration to Client?
Thread-Index: AQHOKjyZ+pj/pqSGEEy03Ze6s9V0b5i4PSpw
Date: Tue, 26 Mar 2013 17:40:49 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E184C4747@xmb-rcd-x04.cisco.com>
References: <5151C83B.1010203@gmail.com>
In-Reply-To: <5151C83B.1010203@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.65.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] FW: [v6ops] Interest in DHCPv6 Route/DefRouter/Src-basedRoute configuration to Client?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Mar 2013 17:40:51 -0000

This is an FYI. If you have opinions, please comment on the v6ops mailing l=
ist.

- Bernie

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of A=
lexandru Petrescu
Sent: Tuesday, March 26, 2013 12:10 PM
To: v6ops@ietf.org
Subject: [v6ops] Interest in DHCPv6 Route/DefRouter/Src-basedRoute configur=
ation to Client?

Dear participants to V6OPS,

Is there an interest in DHCPv6 Route/DefRouter/Src-basedRoute configuration=
 to Client?

As one may remember, there was much discussion in several groups about
DHCPv6 delivering routing information to Clients: generic routes, default r=
outers' addresses and routes keyed by source address.

The MIF WG has produced a document
draft-ietf-mif-dhcpv6-route-option-05
but it is recently dropped from the MIF Charter to allow group to re-focus =
on a MIF topic.

An individual proposal about DHCPv6 Default Routers List that I co-author i=
s in draft-mouton-mif-dhcpv6-drlo-02.txt
which takes on an earlier  draft-droms-dhc-dhcpv6-default-router

In the DHCWG there was recently discussion about IEEE 802.11ai needing to c=
onfigure DefaultRouters by using link-layer messaging, or alternatively DHC=
P.  With a purpose to realize fast configuration in crowded hotspot areas f=
or highly mobile STAs.

Also in DHCWG there was discussion about the src-based routes being communi=
cated to Client with DHCPv6.

Is there an interest in DHCPv6 Route/DefRouter/Src-basedRoute configuration=
 to Client?

Alex

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

From phdgang@gmail.com  Thu Mar 28 00:52:18 2013
Return-Path: <phdgang@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E17B221F902A for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 00:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CT9CmLgIIrXI for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 00:52:18 -0700 (PDT)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF5C21F8FE6 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 00:52:18 -0700 (PDT)
Received: by mail-qc0-f169.google.com with SMTP id t2so4106723qcq.28 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 00:52:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=XOtTzbIFX+VwzqcwBigt5PhT/TTpETbhx8pOc8UzrCE=; b=LTUbrF1dx3g+WID63C5e32pTllmwpw1sPgmg+ZzWsXitnnPdTuQBLghVI4R0o2If7j wAfQJIuUTV7QvRH6YyfJhUwkcAR0mR8LggeCw5b4vs84ZQcxDjb+8tdga46C1hpoICf0 sPhhgtmrvOZtbwbbzWiixrya8QCh1mOazzuhYlSMHaF6g0LWJtAmofEbGtC8ETF+nkg0 fGcKS0PQGQ6DKSCEOULuKRzA3D0464BsBLQRs5JnMVtGb25BYYpbzQUTvGjYsVelyK0k lNLcM5vDtu4VKfB5CMzMl90Z8oE5exsl9P2erBJmjDCNWnMhj7pj7ekPYlJTEdLNO2lP Q8+Q==
MIME-Version: 1.0
X-Received: by 10.49.64.72 with SMTP id m8mr20951879qes.51.1364457137410; Thu, 28 Mar 2013 00:52:17 -0700 (PDT)
Received: by 10.49.71.18 with HTTP; Thu, 28 Mar 2013 00:52:17 -0700 (PDT)
In-Reply-To: <515199b4.28d3440a.3e9f.ffff9426@mx.google.com>
References: <489D13FBFA9B3E41812EA89F188F018E184C093B@xmb-rcd-x04.cisco.com> <515199b4.28d3440a.3e9f.ffff9426@mx.google.com>
Date: Thu, 28 Mar 2013 15:52:17 +0800
Message-ID: <CAM+vMEQkGE5ZN2dtXSmcjdGUX49ePiN04n72_0969OLq4_eadw@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 - Respond by April 8, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Mar 2013 07:52:19 -0000

Hello Authors,

I finish my first read to the current draft. Some preliminary comments
are just for your considerations.

1) If I understood correctly, the draft is targeted to resolve two issues
   a) enable automatic routing advertisement linking to prefix pool
   b) enhance routing aggregation on PE routers

I guess it's worth to try making Introduction Section more
tight/focused on those two issues

It would also be good to state some considerations how could the draft
help to aggregate the routing on PE routers.

2) Section 3 lists two cases. I guess you may want to add some texts
to describe the differences, especially there is a plenty of
configuration data.

BRs

Gang

2013/3/26, Leaf Yeh <leaf.yeh.sdo@gmail.com>:
> Hi folks,
>
>
>
> Pls. feel free to review & comment on this draft. The authors will
> appreciate those efforts to make it better.
>
>
>
>
>
> Best Regards,
>
> Leaf
>
>
>
>
>
>
>
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
> Bernie Volz (volz)
> Sent: Monday, March 25, 2013 4:26 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] WGLC - draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 - Respond
> by April 8, 2013
>
>
>
> Folks, the authors of draft-ietf-dhc-dhcpv6-prefix-pool-opt-02
> <http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-02>  feel
> it's ready for a WGLC.  There's been discussion and comment already, but
> more eyes on this work are definitely needed to advance it.
>
>
>
> At the time of this writing, there is no IPR reported against this draft.
>
>
>
> Please review the draft and indicate whether or not you feel it is ready to
> be published.  We have been getting very anemic responses to working group
> messages recently.   Your response matters, so please do respond.
>
>
>
> Tomek and I will evaluate consensus after April 8, 2013.
>
>
>
> Thanks!
>
>
>
> -          Bernie
>
>

From leaf.yeh.sdo@gmail.com  Thu Mar 28 02:15:08 2013
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A985F21F906F for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 02:15:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.917
X-Spam-Level: 
X-Spam-Status: No, score=-2.917 tagged_above=-999 required=5 tests=[AWL=0.683,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0vxV9tZqjyB2 for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 02:15:06 -0700 (PDT)
Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) by ietfa.amsl.com (Postfix) with ESMTP id 9F56C21F9043 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 02:14:55 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id lj1so1417096pab.21 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 02:14:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=CJu7KvGyE5kl4Nnv0xzXXm5nQpBY77GGO4IuzifehXE=; b=bF7cyCVA7mlyurLgxuehf8fNXjYDrt14jIuos/Cs12ftqYLba+cs2L8w3cJCZC/qTV 6nmZ6kXPHhJuM4WiwlxBYDQD2ij/Z7yTnqfTQgqW6sQEbdCfqOzHfuXxxFIitWRGsK67 PCdB4JblYgNeQXzPKevJHJC+u4H/wAnAjJkn2jjfOYDgfUoxwqgYmevIw9/SQQkYNxvb GOpXI4Sty3102RLxEp1CWPsGJfTqxqfKoYnCmk1twfCYu1PvdJC/ykBpKC3aaikW6b5y 3cYZ9Nb5+JGYwFxO+cUKvQ0c5iOOj5g9pcV0m9XlgUjb9DcR/Dop6RiX7wbfEZOiSAOv Oa5w==
X-Received: by 10.68.179.1 with SMTP id dc1mr33904230pbc.128.1364462095432; Thu, 28 Mar 2013 02:14:55 -0700 (PDT)
Received: from PC ([111.193.222.101]) by mx.google.com with ESMTPS id fk1sm24832680pbd.36.2013.03.28.02.14.52 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 28 Mar 2013 02:14:54 -0700 (PDT)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'GangChen'" <phdgang@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E184C093B@xmb-rcd-x04.cisco.com>	<515199b4.28d3440a.3e9f.ffff9426@mx.google.com> <CAM+vMEQkGE5ZN2dtXSmcjdGUX49ePiN04n72_0969OLq4_eadw@mail.gmail.com>
In-Reply-To: <CAM+vMEQkGE5ZN2dtXSmcjdGUX49ePiN04n72_0969OLq4_eadw@mail.gmail.com>
Date: Thu, 28 Mar 2013 17:14:46 +0800
Message-ID: <51540a0e.010f450a.34b3.ffff8712@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac4riSt2tw7D23ymRWizmnO9bdFqjAABUKvQ
Content-Language: zh-cn
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 - Respond by April 8, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Mar 2013 09:15:08 -0000

Hi Gang,

Thanks for your kind review.

<Gang> the draft is targeted to resolve two issues
   a) enable automatic routing advertisement linking to prefix pool
   b) enhance routing aggregation on PE routers
I guess it's worth to try making Introduction Section more tight/focused on
those two issues
</Gang>

You're right about the draft's purpose, but the proposed OPTION_PREFIX_POOL
(& the DHCPv6 mechanism) is only designed to provide PE the information (&
status) about the pools. PE (and the routing protocol on it) will take the
responsibility (or build the functionality) to do the proper routing
aggregation & automatic advertisement. Right?

<Gang>2) Section 3 lists two cases. I guess you may want to add some texts
to describe the differences, especially there is a plenty of configuration
data. </Gang>

Same reasons as the above. The draft only touches the DHCPv6 part of the
mechanism. It implies that PE could do the proper routing aggregation &
automatic advertisement after (or if) it gets the information about the
pools. (Yes, in section 1. Is text there enough or you want something new?)

The difference between 2 use cases in section 3 are in the titles of the
Fig.1 & Fig.2, In Fig.1, the PE employs the pool for itself (or the whole
device), while in Fig.2, the PE employs the pool for its specified interface
. But I suppose the configuration associated with each prefix pool on the PE
router is the same.


Best Regards,
Leaf



-----Original Message-----
From: GangChen [mailto:phdgang@gmail.com] 
Sent: Thursday, March 28, 2013 3:52 PM
To: Leaf Yeh
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 -
Respond by April 8, 2013

Hello Authors,

I finish my first read to the current draft. Some preliminary comments are
just for your considerations.

1) If I understood correctly, the draft is targeted to resolve two issues
   a) enable automatic routing advertisement linking to prefix pool
   b) enhance routing aggregation on PE routers

I guess it's worth to try making Introduction Section more tight/focused on
those two issues

It would also be good to state some considerations how could the draft help
to aggregate the routing on PE routers.

2) Section 3 lists two cases. I guess you may want to add some texts to
describe the differences, especially there is a plenty of configuration
data.

BRs

Gang

2013/3/26, Leaf Yeh <leaf.yeh.sdo@gmail.com>:
> Hi folks,
>
>
>
> Pls. feel free to review & comment on this draft. The authors will 
> appreciate those efforts to make it better.
>
>
>
>
>
> Best Regards,
>
> Leaf
>
>
>
>
>
>
>
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf 
> Of Bernie Volz (volz)
> Sent: Monday, March 25, 2013 4:26 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] WGLC - draft-ietf-dhc-dhcpv6-prefix-pool-opt-02 - 
> Respond by April 8, 2013
>
>
>
> Folks, the authors of draft-ietf-dhc-dhcpv6-prefix-pool-opt-02
> <http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-02>  
> feel it's ready for a WGLC.  There's been discussion and comment 
> already, but more eyes on this work are definitely needed to advance it.
>
>
>
> At the time of this writing, there is no IPR reported against this draft.
>
>
>
> Please review the draft and indicate whether or not you feel it is 
> ready to be published.  We have been getting very anemic responses to
working group
> messages recently.   Your response matters, so please do respond.
>
>
>
> Tomek and I will evaluate consensus after April 8, 2013.
>
>
>
> Thanks!
>
>
>
> -          Bernie
>
>


From wwwrun@rfc-editor.org  Thu Mar 28 04:07:17 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECD0521F9318 for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 04:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Level: 
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.373, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9+f3xUp-w6ER for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 04:07:16 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 7103F21F92F2 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 04:07:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 91D0762186; Thu, 28 Mar 2013 04:06:44 -0700 (PDT)
To: mjs@cisco.com, brian@innovationslab.net, ted.lemon@nominum.com, volz@cisco.com, tomasz.mrugalski@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20130328110644.91D0762186@rfc-editor.org>
Date: Thu, 28 Mar 2013 04:06:44 -0700 (PDT)
Cc: dhcwg@ietf.org, sgandhewar@juniper.net, rfc-editor@rfc-editor.org
Subject: [dhcwg] [Technical Errata Reported] RFC5460 (3571)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Mar 2013 11:07:17 -0000

The following errata report has been submitted for RFC5460,
"DHCPv6 Bulk Leasequery".

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

--------------------------------------
Type: Technical
Reported by: Sunil M Gandhewar <sgandhewar@juniper.net>

Section: 5.2.1

Original Text
-------------
5.2.1. LEASEQUERY-DATA

The LEASEQUERY-DATA message carries data about a single DHCPv6
client’s leases and/or PD bindings on a single link. The purpose of
the message is to reduce redundant data when there are multiple
bindings to be sent. The LEASEQUERY-DATA message MUST be preceded by
a LEASEQUERY-REPLY message. The LEASEQUERY-REPLY carries the query’s
status, the Leasequery’s Client-ID and Server-ID options, and the
first client’s binding data if the query was successful.

LEASEQUERY-DATA MUST ONLY be sent in response to a successful
LEASEQUERY, and only if more than one client’s data is to be sent.
The LEASEQUERY-DATA message’s transaction-id field MUST match the
transaction-id of the LEASEQUERY request message. The Server-ID,
Client-ID, and OPTION_STATUS_CODE options SHOULD NOT be included:
that data should be constant for any one Bulk Leasequery reply, and
should have been conveyed in the LEASEQUERY-REPLY message.

Corrected Text
--------------
5.2.1. LEASEQUERY-DATA

The LEASEQUERY-DATA message carries data about a single DHCPv6
client’s leases and/or PD bindings on a single link. The purpose of
the message is to reduce redundant data when there are multiple
bindings to be sent. The LEASEQUERY-DATA message MUST be preceded by
a LEASEQUERY-REPLY message. The LEASEQUERY-REPLY carries the query’s
status, the Leasequery’s Client-ID and Server-ID options, and the
first client’s binding data if the query was successful.

LEASEQUERY-DATA MUST ONLY be sent in response to a successful
LEASEQUERY, and only if more than one client’s data is to be sent.
The LEASEQUERY-DATA message’s transaction-id field MUST match the
transaction-id of the LEASEQUERY request message. The Server-ID,
requestor's Client-ID, and OPTION_STATUS_CODE options SHOULD NOT be included:
that data should be constant for any one Bulk Leasequery reply, and
should have been conveyed in the LEASEQUERY-REPLY message.

Notes
-----
The term "Client-Id" in second paragraph sounds like client's Client-Id and it will be different for more than one client's data. So it should be corrected to "requestor's Client-ID" or "Leasequery's Client-ID" instead of just "Client-ID".

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

--------------------------------------
RFC5460 (draft-ietf-dhc-dhcpv6-bulk-leasequery-06)
--------------------------------------
Title               : DHCPv6 Bulk Leasequery
Publication Date    : February 2009
Author(s)           : M. Stapp
Category            : PROPOSED STANDARD
Source              : Dynamic Host Configuration
Area                : Internet
Stream              : IETF
Verifying Party     : IESG

From alexandru.petrescu@gmail.com  Thu Mar 28 09:13:40 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E266A21F8E9E for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 09:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.918
X-Spam-Level: 
X-Spam-Status: No, score=-9.918 tagged_above=-999 required=5 tests=[AWL=0.331,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2uONxy5-c+UV for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 09:13:37 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 7879A21F8E87 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 09:13:34 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r2SGDXxr023555 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Thu, 28 Mar 2013 17:13:33 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r2SGDX9P007048 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 17:13:33 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r2SGDRIP000493 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 17:13:33 +0100
Message-ID: <51546BEF.2000206@gmail.com>
Date: Thu, 28 Mar 2013 17:12:31 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <4F5EA754.50403@trans-nt.com> <56269277-D110-4052-A388-E56CD23DD8B5@nominum.com> <4F5EE6B9.4050704@trans-nt.com> <44C2AE51-D4AD-49CA-BA84-B4B6447823D4@nominum.com> <4F5F953C.5000504@trans-nt.com> <5115BCAB.9050104@trans-nt.com> <8D23D4052ABE7A4490E77B1A012B63074748554A@mbx-01.win.nominum.com> <5116E9A7.2010304@trans-nt.com> <511AA538.2000902@trans-nt.com> <4C872C87-9D7E-473C-86CE-F1D7CD7FCCA9@gmail.com>
In-Reply-To: <4C872C87-9D7E-473C-86CE-F1D7CD7FCCA9@gmail.com>
Content-Type: multipart/mixed; boundary="------------020403030003050007030801"
Subject: Re: [dhcwg] IEEE 802.11ai and DHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Mar 2013 16:13:40 -0000

This is a multi-part message in MIME format.
--------------020403030003050007030801
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Le 26/03/2013 10:09, Jouni Korhonen a écrit :
>
> I find it quite interesting and slightly surprising IEEE is working
> on this. In cellular space (3gpp) we have had about equivalent
> mechanism at the NAS protocol layer from the beginning.

I tend to agree.

For example, there is this link-layer RANAP protocol.  In this, the
UserEquipment sends a "Activate PDP Context Request" with a "DNS Server
IPv6 Address Request", and receives the IPv6 address of the DNS Server 
in a "Activate PDP Context Accept".

This link-layer messaging is redundant with two other IP protocols: (1)
Router Advertisement sending the DNS IPv6 address (RFC61606 "IPv6 Router
Advertisement Options for DNS Configuration") _and_ with (2) DHCPv6
configuration options containing the address of the DNS server.

> It works but has always been a bit of headache, since multiple ways
> to do the same thing with loads of optional features on different
> layers caused nasty implementation/deployment challenges. I hope
> IEEE does this better now that they are doing it ;)

I think that _if_ at IETF there were such protocol to realize this fast
configuration in the same way that IEEE needs for crowded hotspot then
one could suggest it to IEEE.

Alex

>
> - Jouni
>
>
> On Feb 12, 2013, at 10:25 PM, Hiroki Nakano <cas@trans-nt.com>
> wrote:
>
>> Dear all,
>>
>> I'm participating in IEEE 802.11 WG TGai task group which is for
>> FILS (Fast Initiali Link Setup). They are working for speeding up
>> of 802.11 process and trying to provide a new framework for higher
>>  layer protocols.
>>
>> I'd like to introduce the overview of prospective 802.11ai
>> specification and discuss usages of DHCP on it with DHC WG people
>> in March. The followings are a brief introduction.
>>
>> TGai supposes Wireless LAN is used in very crowded envirionment
>> such as railway stations in a giant metropolis. TGai also supposes
>> moving hosts through the front of Access Points. In these cases,
>> it is effective to reduce management frames of 802.11, especially
>> frames for probing APs, authentication and association. The
>> current framework takes a few seconds to set up network
>> connectivity before starting to communicate. The target of TGai is
>> under one second.
>>
>> TGai is trying to reduce management frames of 802.11 itself, and
>> in addition provide framework for higher layers such as IP to send
>> and receive packets during 802.11 association process. The
>> currently proposed framework provides "ONE round-trip packet
>> exchange" by piggybacking on 802.11 Association Request/Response
>> frames.
>>
>> My interest is how to fit DHCP to this framework. In case of
>> DHCPv4, this is achieved by using Rapid Commit Option (RFC4039)
>> and making some additional and trivial rules. In case of DHCPv6,
>> we have to use both RA and DHCPv6. In addition, DAD and randomly
>> generated addresses have to be considered. Share your idea,
>> please.
>>
>> 802.11 TGai is still going on and its specification is subject to
>> change, but I'd like to discuss in IETF DHCP issues related to
>> 802.11ai and arrange I-D according to the progress of TGai task
>> group.
>>
>> Regards,
>>
>> Hiroki Nakano Trans New Technology, Inc. <cas@trans-nt.com>
>>
>> _______________________________________________ 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
>
>


--------------020403030003050007030801
Content-Type: application/octet-stream;
 name="ranap-capture.pcap"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="ranap-capture.pcap"

1MOyoQIABAAAAAAAAAAAAP//AAABAAAA8/rKUIgTAACyAAAAsgAAAAAZB6hCQAAh4faXgIEA
ALkIAEWIAKDZQAAAP4TMmwoPYUoKD18OC1kJABPYXxARKqdlAAMAgBqIIqAAAd8XAAAAAwEA
AQEAAABwAhAAZgAAE5EAABOHAwMACgYX1SAAAU8AFEBLAAAEABBAKSgKQQUDDgAAHxAAAAAA
AAAAAAAAAgFXKAoEaXB2NgR0ZXN0JwSAAAMAAA9ABgAC+BA4BQA3QAEBADpACAAC+BA4Bft3
AAD0+spQULEDALIAAACyAAAAACHh9pfAABkHqEHAgQCguggARbgAoGleAAA5hEJOCg9fDgoP
YUoJAAtZAACMlZtkbDAAAwCAMZ0XxQABAcAAAAADAQABAQAAAHACEABlAAAThwAAE5EDAwAK
BgBo6gABTgAUQEoAAAIAEEA+PYpCAw4Tkh9zlpf+dIIQQAAAAAIrEgFXKgHNAU8qAAQzeF9Y
I7ukzicUgAADECoBzQCA8AAAAAAAAAAAAAIAO0ABAAAAAA==
--------------020403030003050007030801--


From tomasz.mrugalski@gmail.com  Thu Mar 28 11:56:25 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD9B21F8EE8 for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 11:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pnC6pIOlfJ7n for <dhcwg@ietfa.amsl.com>; Thu, 28 Mar 2013 11:56:24 -0700 (PDT)
Received: from mail-ee0-f42.google.com (mail-ee0-f42.google.com [74.125.83.42]) by ietfa.amsl.com (Postfix) with ESMTP id 5F0A521F8ED6 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 11:56:24 -0700 (PDT)
Received: by mail-ee0-f42.google.com with SMTP id b47so4933415eek.15 for <dhcwg@ietf.org>; Thu, 28 Mar 2013 11:56:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=DVTS+JkPDDFHWL0WJsScivEjdaIgffo0oTmDFQq4aJU=; b=fBNbt8jMvYze0JGiVqXKogC2mDkVMjgbhQFfsvW9/gK5AWZLbJIcVh3Or/CwZi3NFM rzSmq0tisbvVfWrf9QD8PuiTUF1opgy6KSbcNXmBoEe8g/qLp/ev0f1ilXV2cxJ9hIzf KxCua+uVCg24xcUFKvKzBrh4++aSewyJKnGWqwHfOIiWpHRnx/qzZrdKNczXrPRPbbcP DRdCnqQwpg4WYLjf0qH9c45rHjGC7m20VoGlVO5gj6F1RTBHLKenbO7r0X7pFWh8uHcK gH9t0lNd5yyRXRSajz//0WGtVEW5EkC/mjIo0Wc4CzLbK3lLJCuYcaouK3wd5qlIIMND uEXA==
X-Received: by 10.14.0.73 with SMTP id 49mr69952674eea.21.1364496983329; Thu, 28 Mar 2013 11:56:23 -0700 (PDT)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPS id u44sm39505942eel.7.2013.03.28.11.56.21 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Mar 2013 11:56:22 -0700 (PDT)
Message-ID: <5154924E.3080403@gmail.com>
Date: Thu, 28 Mar 2013 19:56:14 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] IETF86 DHC minutes available
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Mar 2013 18:56:25 -0000

Hi all,
THe draft minutes from Orlando DHC meeting are now available at

http://www.ietf.org/proceedings/86/minutes/minutes-86-dhc

Please review these minutes and send us changes/additions by April 14th,
2013.

Regards,
Tomek & Bernie

From wwwrun@rfc-editor.org  Sun Mar 31 10:35:24 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36C0721F843A for <dhcwg@ietfa.amsl.com>; Sun, 31 Mar 2013 10:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.39
X-Spam-Level: 
X-Spam-Status: No, score=-102.39 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aIz2IiXP90VV for <dhcwg@ietfa.amsl.com>; Sun, 31 Mar 2013 10:35:23 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id A8F7D21F8435 for <dhcwg@ietf.org>; Sun, 31 Mar 2013 10:35:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 55F9AB1E002; Sun, 31 Mar 2013 10:33:57 -0700 (PDT)
To: Jim.Bound@hp.com, volz@metrocast.net, Ted.Lemon@nominum.com, charles.perkins@nokia.com, michael.carney@sun.com, brian@innovationslab.net, ted.lemon@nominum.com, volz@cisco.com, tomasz.mrugalski@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20130331173357.55F9AB1E002@rfc-editor.org>
Date: Sun, 31 Mar 2013 10:33:57 -0700 (PDT)
X-Mailman-Approved-At: Sun, 31 Mar 2013 14:13:30 -0700
Cc: dhcwg@ietf.org, p_armando@hotmail.com, rfc-editor@rfc-editor.org
Subject: [dhcwg] [Editorial Errata Reported] RFC3315 (3577)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Mar 2013 17:35:24 -0000

The following errata report has been submitted for RFC3315,
"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".

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

--------------------------------------
Type: Editorial
Reported by: Pablo Armando <p_armando@hotmail.com>

Section: 9.3

Original Text
-------------
An example DUID of this type might look like this:

    +---+---+---+---+---+---+---+---+
    | 0 | 2 | 0 | 0 | 0 |  9| 12|192|
    +---+---+---+---+---+---+---+---+
    |132|221| 3 | 0 | 9 | 18|
    +---+---+---+---+---+---+

   This example includes the two-octet type of 2, the Enterprise Number
   (9), followed by eight octets of identifier data
   (0x0CC084D303000912).

Corrected Text
--------------
An example DUID of this type might look like this:

    +---+---+---+---+---+---+---+---+
    | 0 | 2 | 0 | 0 | 0 |  9| 12|192|
    +---+---+---+---+---+---+---+---+
    |132|211| 3 | 0 | 9 | 18|
    +---+---+---+---+---+---+

   This example includes the two-octet type of 2, the Enterprise Number
   (9), followed by eight octets of identifier data
   (0x0CC084D303000912).

Notes
-----
0xD3 is 211 decimal, not 221.

I am assuming that this number is the correct one: 0x0CC084D303000912

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

--------------------------------------
RFC3315 (draft-ietf-dhc-dhcpv6-28)
--------------------------------------
Title               : Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Publication Date    : July 2003
Author(s)           : R. Droms, Ed., J. Bound, B. Volz, T. Lemon, C. Perkins, M. Carney
Category            : PROPOSED STANDARD
Source              : Dynamic Host Configuration
Area                : Internet
Stream              : IETF
Verifying Party     : IESG
