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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 29 October 2013 13:04 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 CA23B11E8244 for <v6ops@ietfa.amsl.com>; Tue, 29 Oct 2013 06:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.282
X-Spam-Level:
X-Spam-Status: No, score=-10.282 tagged_above=-999 required=5 tests=[AWL=-0.033, 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 7ZhjI6BJjdfV for <v6ops@ietfa.amsl.com>; Tue, 29 Oct 2013 06:03:57 -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 189FB11E8239 for <v6ops@ietf.org>; Tue, 29 Oct 2013 06:03:56 -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 r9TD3tYn030005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 Oct 2013 14:03:55 +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 r9TD3tnw020001; Tue, 29 Oct 2013 14:03:55 +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 r9TD3ngB017794; Tue, 29 Oct 2013 14:03:55 +0100
Message-ID: <526FB236.3090106@gmail.com>
Date: Tue, 29 Oct 2013 14:03:50 +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: Gert Doering <gert@space.net>
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> <526E7FCA.60702@gmail.com> <20131028161219.GQ50205@Space.Net>
In-Reply-To: <20131028161219.GQ50205@Space.Net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: v6ops@ietf.org
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: Tue, 29 Oct 2013 13:04:02 -0000

Le 28/10/2013 17:12, Gert Doering a écrit :
> Hi,
>
> On Mon, Oct 28, 2013 at 04:16:26PM +0100, Alexandru Petrescu wrote:
>> I thought the goal was to not modify RA, whereas the above does
>> modify the RA to include a DNS resolver.
>
> Uh.  *That* train has sailed 6 years ago with RFC5006...

Right.

But in this thread some say we should no longer do DHCP-typical-info in
the RA, and at the same time they propose to do it, provided the backend
info comes from a DHCP server.  Hence my question about whether a
delegated prefix (another DHCP-typical-info) would be ok for this
concept. (I author an earlier draft in this space).

>> 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).
>
> What use would that be?  The benefit of RA is that "everyone can see
> them and the information contained applies to *all* consumers, and is
> periodically refreshed without having to poll".  PD is, by
> definition, very specific to the device where you delegate to...

I tend to agree that RA's content is generally valid for everyone
receiving that RA, and that typically RAs are multicasted to all nodes
on a link.

However, there are some specific cases where the RA is unicast to
particular nodes and contain information specific to that node.  For
example in Proxy Mobile IPv6 RFC5213 an access router sends an RA to a
particular mobile host attaching to it, and it puts inside a prefix to
make believe that particular node to be at its home.  Each node has a
different home prefix.  Another example is in Fast Mobile IPv6 protocol
RFC4068 where a Proxy RA contains an address specific to a mobile.  A
more remote example is that of RPL RFC6550 which uses a new ICMP message
'RPL Control Message' remotely similar to RA, and whose destination is
unicast.

Apart from that, the use case I am considering is fast exchanges of IP
messages to establish quickly short-lived communications (10ms IP
establishment address/defroute, and app-layer communications during a
few minutes).  Used in vehicular communications.  A vehicle containing a
cellular link (SIM subscription) may offer Internet connectivity to a
SIM-less vehicle nearby - mobile billboard vehicle, like in this figure
http://en.wikipedia.org/wiki/File:MSNBC_mobile_billboard_at_Union_Station.jpg
(check the "Free WiFi" banner).

Alex

>
> This thread is full of weirdness.
>
> Gert Doering -- NetMaster
>