Re: [dhcwg] IEEE 802.11ai and DHCP

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 13 February 2013 12:23 UTC

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 1F0DA21F87F5 for <dhcwg@ietfa.amsl.com>; Wed, 13 Feb 2013 04:23:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.313
X-Spam-Level:
X-Spam-Status: No, score=-10.313 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 5I2r73yGLg1M for <dhcwg@ietfa.amsl.com>; Wed, 13 Feb 2013 04:23:27 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 138EA21F87F3 for <dhcwg@ietf.org>; Wed, 13 Feb 2013 04:23:26 -0800 (PST)
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 r1DCNPYS000449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <dhcwg@ietf.org>; Wed, 13 Feb 2013 13:23:26 +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 r1DCNPIC013664 for <dhcwg@ietf.org>; Wed, 13 Feb 2013 13:23:25 +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 r1DCNF7t021508 for <dhcwg@ietf.org>; Wed, 13 Feb 2013 13:23:25 +0100
Message-ID: <511B85B3.8030705@gmail.com>
Date: Wed, 13 Feb 2013 13:23:15 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
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>
In-Reply-To: <511AA538.2000902@trans-nt.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: Wed, 13 Feb 2013 12:23:28 -0000

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