IETF Logo Mail Archive

Re: [v6ops] IPv4 trajectory

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 02 April 2015 17:53 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B68EF1A870C for <v6ops@ietfa.amsl.com>; Thu, 2 Apr 2015 10:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I9ImtGWYzNJz for <v6ops@ietfa.amsl.com>; Thu, 2 Apr 2015 10:53:05 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BFAD1A002D for <v6ops@ietf.org>; Thu, 2 Apr 2015 10:53:03 -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 t32Hr2Hd018967 for <v6ops@ietf.org>; Thu, 2 Apr 2015 19:53:02 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A46112076C2 for <v6ops@ietf.org>; Thu, 2 Apr 2015 19:53:57 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9C1A9207486 for <v6ops@ietf.org>; Thu, 2 Apr 2015 19:53:57 +0200 (CEST)
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 t32HqkaV017645 for <v6ops@ietf.org>; Thu, 2 Apr 2015 19:53:02 +0200
Message-ID: <551D81EE.2030403@gmail.com>
Date: Thu, 02 Apr 2015 19:52:46 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: v6ops@ietf.org
References: <63C03012-C7DD-497E-A1EF-019711E95FD0@cisco.com> <551BFBA9.5070103@gmail.com> <CADhXe5395L-HC-bQ7JzgVijLwBaovz7xJ27Rp7LrbHbOp98D6A@mail.gmail.com> <551CE518.7040202@gmail.com>
In-Reply-To: <551CE518.7040202@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/azbgL5wcUsz0QiVts8qec0DvlSA>
Subject: Re: [v6ops] IPv4 trajectory
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 02 Apr 2015 17:53:06 -0000

Le 02/04/2015 08:43, Alexandru Petrescu a écrit :
> Le 02/04/2015 01:30, James Woodyatt a écrit :
>> On Wed, Apr 1, 2015 at 9:07 AM, Alexandru Petrescu
>> <alexandru.petrescu@gmail.com
>> <mailto:alexandru.petrescu@gmail.com>> wrote:
>>
>>
>> It is customary to see current computers having both an IPv6 stack
>>  and an IPv4 stack on them.  But some computers only have IPv4,
>> whereas the rest have IPv4 and IPv6 stacks.  There are no computers
>> (to my knowledge) which have only IPv6 stacks.
>>
>>
>> Sigh. Computing platforms where the only network interfaces are
>> 6LoWPAN-over-foo. These exist today, and they are not just
>> laboratory toys.
>
> Right, this is something that deserves consideration.
>
> I wonder though whether they are directly connectable to the
> Internet. Last time I checked a 6lowpan IPv6-only computer it was a
> reduced IPv6 - one had to go through a form of middle-box to reach
> it.  E.g. one wouldnt ssh into a 6lowpan device, would not manage it
> directly, but would need a CoAP gw, or a PC attached with USB to be
> on it.
>
> But I will ask around to see the current situation.

I asked around for some 6lowpan Contiki situation.  We still need to
check serial output of modem verbose looking for IPv4 literals.

But, in general, contiki does have this ability to only include IPv6,
and no IPv4 stack.

There are other questions there, though.

For example, some contiki devices still use fec0 addresses.

IPv6 contiki devices are not reachable by other means than CoAP (there
is no TCP or HTTP for example), by using a particular plugin in some
browser.  You can't telnet or rsh into it.

You can't imagine sending a 6lowpan device a pure RA (it must be an RPL
ICMP message).

You can't connect a 6lowpan-enabled-Router somewhere at an edge of the
Internet where prefixes are already /64, because 6lowpan needs /64 as well.

I may be wrong in some of these aspects, but for these doubts I still
dont think 6lowpan is IPv6, and I dont think 6lowpan devices are on the
IPv6 Internet.

Or is there an address of an IPv6-only 6lowpan device I could ping6?

Alex

>
> Alex
>
>>
>>
>> -- james woodyatt <jhw@nestlabs.com <mailto:jhw@nestlabs.com>> Nest
>> Labs, Communications Engineering
>
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email