[v6ops] Interest in DHCPv6 Route/DefRouter/Src-basedRoute configuration to Client?

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 26 March 2013 16:11 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89E2921F8C11 for <v6ops@ietfa.amsl.com>; Tue, 26 Mar 2013 09:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.474
X-Spam-Level:
X-Spam-Status: No, score=-9.474 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 esSDrPQe0dtQ for <v6ops@ietfa.amsl.com>; Tue, 26 Mar 2013 09:11:12 -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 3233621F8546 for <v6ops@ietf.org>; Tue, 26 Mar 2013 09:10:34 -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 r2QGAXgv009435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <v6ops@ietf.org>; Tue, 26 Mar 2013 17:10: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 r2QGAXFt002349 for <v6ops@ietf.org>; Tue, 26 Mar 2013 17:10: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 r2QGAOFr000309 for <v6ops@ietf.org>; Tue, 26 Mar 2013 17:10:32 +0100
Message-ID: <5151C83B.1010203@gmail.com>
Date: Tue, 26 Mar 2013 17:09: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: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [v6ops] Interest in DHCPv6 Route/DefRouter/Src-basedRoute configuration to Client?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2013 16:11:22 -0000

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 routers' 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 is 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 configure DefaultRouters by using link-layer messaging, or
alternatively DHCP.  With a purpose to realize fast configuration in
crowded hotspot areas for highly mobile STAs.

Also in DHCWG there was discussion about the src-based routes being
communicated to Client with DHCPv6.

Is there an interest in DHCPv6 Route/DefRouter/Src-basedRoute
configuration to Client?

Alex