IETF Logo Mail Archive

Re: [v6ops] IPv4 trajectory

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 02 April 2015 06:43 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 B0E611B2B30 for <v6ops@ietfa.amsl.com>; Wed, 1 Apr 2015 23:43:50 -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 qoAmjGS1LrVv for <v6ops@ietfa.amsl.com>; Wed, 1 Apr 2015 23:43:48 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93DD61B2B28 for <v6ops@ietf.org>; Wed, 1 Apr 2015 23:43:48 -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 t326hkXv014132; Thu, 2 Apr 2015 08:43:46 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 61E8C205C9E; Thu, 2 Apr 2015 08:44:41 +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 4C895205C4C; Thu, 2 Apr 2015 08:44:41 +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 t326haGI009118; Thu, 2 Apr 2015 08:43:46 +0200
Message-ID: <551CE518.7040202@gmail.com>
Date: Thu, 02 Apr 2015 08:43:36 +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: James Woodyatt <jhw@nestlabs.com>
References: <63C03012-C7DD-497E-A1EF-019711E95FD0@cisco.com> <551BFBA9.5070103@gmail.com> <CADhXe5395L-HC-bQ7JzgVijLwBaovz7xJ27Rp7LrbHbOp98D6A@mail.gmail.com>
In-Reply-To: <CADhXe5395L-HC-bQ7JzgVijLwBaovz7xJ27Rp7LrbHbOp98D6A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/0cHS5Mf48tn31vrFcJxFMRGZQ8Q>
Cc: IPv6 Ops WG <v6ops@ietf.org>
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 06:43:50 -0000

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.

Alex

>
>
> -- james woodyatt <jhw@nestlabs.com <mailto:jhw@nestlabs.com>> Nest
> Labs, Communications Engineering

v2.23.0 | Report a Bug | By Email