Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 28 October 2013 15:17 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 23A5D11E817F for <v6ops@ietfa.amsl.com>; Mon, 28 Oct 2013 08:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.993
X-Spam-Level:
X-Spam-Status: No, score=-9.993 tagged_above=-999 required=5 tests=[AWL=-0.344, 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 LklL61imEhvR for <v6ops@ietfa.amsl.com>; Mon, 28 Oct 2013 08:16:57 -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 EDBE511E814C for <v6ops@ietf.org>; Mon, 28 Oct 2013 08:16:33 -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 r9SFGWcj006800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <v6ops@ietf.org>; Mon, 28 Oct 2013 16:16:32 +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 r9SFGVKM028605 for <v6ops@ietf.org>; Mon, 28 Oct 2013 16:16:31 +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 r9SFGQ4u017954 for <v6ops@ietf.org>; Mon, 28 Oct 2013 16:16:31 +0100
Message-ID: <526E7FCA.60702@gmail.com>
Date: Mon, 28 Oct 2013 16:16:26 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: v6ops@ietf.org
References: <CE8E8EC3.59F3A%victor@jvknet.com> <06601039-CAFD-49B0-918B-A8ACD51B978D@fugue.com> <526D17A5.9050804@cernet.edu.cn> <C8C148BF-08F0-488A-BF1A-8B4BEAC39156@fugue.com> <526D18F2.8040103@cernet.edu.cn> <20131027145224.GT50205@Space.Net> <CAKD1Yr13YGiRfHm0RoOoGe+02SCXcPFE7rgBG=RiT1-dTfEnrg@mail.gmail.com> <526D9FFC.9060307@cernet.edu.cn>
In-Reply-To: <526D9FFC.9060307@cernet.edu.cn>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem
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: Mon, 28 Oct 2013 15:17:02 -0000

Le 28/10/2013 00:21, Xing Li a écrit :
> Lorenzo Colitti 写道:
>> On Sun, Oct 27, 2013 at 11:52 PM, Gert Doering <gert@space.net
>> <mailto:gert@space.net>> wrote:
>>
>>     > > I do not think that I made an actual proposal here.
>>     > I mean "Stateful RA could actually be piggybacked onto DHCP, so
>>     that the
>>     > router just creates a DHCP message and forwards it upstream, or
>>     answers
>>     > it locally, depending on the circumstances." xing
>>
>>     This is called "DHCP relay or DHCP server on the router". I can't see
>>     what this has to do with RA ("periodically multicasted to everyone
>> who
>>     wants to receive it").
>>
>>     This idea is... completely lacking the understanding of the
>> difference
>>     between solicited and unsolicited information, and also of the
>>     existing
>>     possibilities of just having a DHCPv6 server (or relay) on the router
>>     itself.
>>
>>
>> The way I read that was:
>>
>> 1. Host sends RS.
>> 2. Router gets RS, encapsulates it in DHCPv6 option to DHCPv6 server.
>> 3. Server replies with RA parameters.
>> 4. Router sends unicast RA to host.
>>
>> The unicast RA would have more information than the multicast RA
>> (e.g., more specific routes). The idea being that you if you do this
>> you can send different clients different information (which is one of
>> the things that DHCPv6 offers but RAs typically do not).
>>
>> So it's basically a RA-to-DHCPv6 translator in the router.
>>
>> If you want to do it this way, I don't see why you would use DHCPv6
>> and not something like radius, but I suppose you might want to do that
>> if you need to keep state on the server (radius is stateless).
 >
> +1. The stateful configuration is required in CERNET2 case. xing

This was proposed in the past and it has advantages to which I could agree.

I thought the goal was to not modify RA, whereas the above does modify 
the RA to include a DNS resolver.

If yes, would it be ok to include a Prefix Delegation option as well in 
the RA? (not an RFC4191 option, but a new Prefix Delegation option 
pasted from DHCPv6 Prefix Delegation).

Alex

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