Re: [v6ops] Enterprises won't deploy IPv6 for IPv6's sake (as they didn't IPv4, IPX, XNS, or DECNet)

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 10 January 2014 09:18 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 752371AD8CD for <v6ops@ietfa.amsl.com>; Fri, 10 Jan 2014 01:18:03 -0800 (PST)
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 sLR_7QAcc7Vt for <v6ops@ietfa.amsl.com>; Fri, 10 Jan 2014 01:18:01 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id CA8A61ACCE6 for <v6ops@ietf.org>; Fri, 10 Jan 2014 01:18:00 -0800 (PST)
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 s0A9HoWS016808 for <v6ops@ietf.org>; Fri, 10 Jan 2014 10:17:50 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AF541207043 for <v6ops@ietf.org>; Fri, 10 Jan 2014 10:18:52 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4158F20700F for <v6ops@ietf.org>; Fri, 10 Jan 2014 10:18:46 +0100 (CET)
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 s0A9HeeR027233 for <v6ops@ietf.org>; Fri, 10 Jan 2014 10:17:43 +0100
Message-ID: <52CFBAB4.4040105@gmail.com>
Date: Fri, 10 Jan 2014 10:17:40 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: v6ops@ietf.org
References: <1386274786.29351.YahooMailNeo@web142501.mail.bf1.yahoo.com> <CAEmG1=qLxqWdB8JR4rbAS-TyqQtPcGnZvVb7DSBCrmFcrm0vUA@mail.gmail.com> <20140107104001.GM81676@Space.Net> <m2lhyqb354.wl%randy@psg.com> <72626BC4-CB9E-49E8-8A54-48A141F52C0C@nominum.com> <m2k3eab1op.wl%randy@psg.com> <6A64F619-4A0E-423A-A5E7-4C3234B461AE@nominum.com> <m2fvoyb0hd.wl%randy@psg.com> <1389261993.72423.YahooMailNeo@web161906.mail.bf1.yahoo.com> <2134F8430051B64F815C691A62D98318193C5C@XCH-BLV-504.nw.nos.boeing.com> <C2A091EA-6B9F-47C0-9D50-2260D4DA0D57@ecs.soton.ac.uk> <EMEW3|4c4e9aa60cad1e97207c58631caba379q! 08H4x03tjc|ecs.soton.ac.uk|C2A091EA-6B9F-47C0-9D50-2260D4DA0D57@ecs.soton.ac.uk> <2134F8430051B64F815C691A62D98318193CD6@XCH-BLV-504.nw.nos.boeing.com> <597F58BD-DCEA-4C4E-B7AB-DCCB416B3CFD@ecs.soton.ac.uk> <EMEW3|04e90b90dff954d2bc6d2a53888d4abdq08HOU03tjc|ecs.soton.ac.uk|597F58BD-DCEA-4C4E-B7AB-DCCB416B3CFD@ecs.soton.ac.uk> <2134F8430051B64F815C691A62D98318193D30@XCH-BLV-504.nw.nos.boei! ng.com>
In-Reply-To: <2134F8430051B64F815C691A62D98318193D30@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [v6ops] Enterprises won't deploy IPv6 for IPv6's sake (as they didn't IPv4, IPX, XNS, or DECNet)
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: Fri, 10 Jan 2014 09:18:03 -0000

Le 09/01/2014 18:28, Templin, Fred L a écrit :
> Hi Tim,
>
>> -----Original Message----- From: Tim Chown
>> [mailto:tjc@ecs.soton.ac.uk] Sent: Thursday, January 09, 2014 9:24
>> AM To: Templin, Fred L Cc: Mark ZZZ Smith; Randy Bush; Ted Lemon;
>> v6ops@ietf.org Subject: Re: [v6ops] Enterprises won't deploy IPv6
>> for IPv6's sake (as they didn't IPv4, IPX, XNS, or DECNet)
>>
>>
>> On 9 Jan 2014, at 17:21, "Templin, Fred L"
>> <Fred.L.Templin@boeing.com> wrote:
>>
>>> Hi Tim,
>>>
>>>> The campus wireless solutions I've seen from vendors to date
>>>> that support IPv6 do some "interesting" things to support
>>>> devices roaming between IPv6 wireless subnets.  They certainly
>>>> don't seem to use MIPv6, rather it seems common to use either
>>>> unicast RAs and/or L2 tunnelling between controllers. e.g. see
>>>
>>> http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bae506.shtml#mobility.
>>>
>>>
>>>
I am thinking of mobiles that have WiFi plus 3G/4G. When the mobile is
>>> in proximity of my enterprise infrastructure then it can
>>> certainly be managed as it hops between WLCs as you suggest. But,
>>> when the mobile leaves the campus and goes in via a Starbucks
>>> WiFi (or maybe my home WiFi) it is beyond the management realm of
>>> the enterprise and has to do something if it wants to maintain a
>>> stable IP address/subnet. Or, if the mobile goes off the "WiFi
>>> grid" it has to fire up its 3G/4G link and then still somehow
>>> maintain stability.
>>
>> MPTCP?  A la Siri on iOS7 etc :)
>
> That won't get me to a mobile router - it only addresses the apps on
> the mobile itself.

YEs, and only apps using a particular transport protocols, not all.

(and yes the news of MPTCP at Apple is encouraging about that
  particular protocol).

>
>>> This is not about MIPv6 - it is about AERO:
>>
>> Well, the thread is about something else, so back to that....
>
> The thread is about IPv6 deployment in enterprise networks. AERO is
> about IPv6 deployment in enterprise networks (which should also be
> taken as input to your IPv6 enterprise deployment doc).

Right.  But since this thread relates to the DHCP discussion, would AERO
have an aspect related to DHCP?  Or to RA?  How would an AERO
Router self-configure its address, its mobile network prefix and its
default route?  Would it accept many combinations or just one?

Alex

>
> Thanks - Fred fred.l.templin@boeing.com
>
>> Tim
>>
>>>
>>> http://tools.ietf.org/html/draft-templin-aerolink
>>>
>>> Thanks - Fred fred.l.templin@boeing.com
>>>
>>> PS I shouldn't have to ask, but please keep this as plaintext
>>> instead of converting to something else.
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>
>