IETF Logo Mail Archive

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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 09 January 2014 17:29 UTC

Return-Path: <Fred.L.Templin@boeing.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 611F11AE3DC for <v6ops@ietfa.amsl.com>; Thu, 9 Jan 2014 09:29:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level:
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] 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 gkFaLx-OxNRk for <v6ops@ietfa.amsl.com>; Thu, 9 Jan 2014 09:29:07 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 03C741AE391 for <v6ops@ietf.org>; Thu, 9 Jan 2014 09:29:06 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s09HSvhp032248; Thu, 9 Jan 2014 09:28:57 -0800
Received: from XCH-PHX-112.sw.nos.boeing.com (xch-phx-112.sw.nos.boeing.com [130.247.25.134]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s09HSq8m032180 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 9 Jan 2014 09:28:52 -0800
Received: from XCH-BLV-108.nw.nos.boeing.com (130.247.25.137) by XCH-PHX-112.sw.nos.boeing.com (130.247.25.134) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Jan 2014 09:28:51 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.203]) by XCH-BLV-108.nw.nos.boeing.com ([169.254.13.207]) with mapi id 14.03.0158.001; Thu, 9 Jan 2014 09:28:51 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Thread-Topic: [v6ops] Enterprises won't deploy IPv6 for IPv6's sake (as they didn't IPv4, IPX, XNS, or DECNet)
Thread-Index: AQHPDV+sxP36KFapgEy8h/U9IKX/EJp8pOLA
Date: Thu, 09 Jan 2014 17:28:50 +0000
Message-ID: <2134F8430051B64F815C691A62D98318193D30@XCH-BLV-504.nw.nos.boeing.com>
References: <1386274786.29351.YahooMailNeo@web142501.mail.bf1.yahoo.com> <alpine.OSX.2.00.1312060759220.68814@ayourtch-mac> <1386378082.99914.YahooMailNeo@web161901.mail.bf1.yahoo.com> <alpine.OSX.2.00.1312072028290.68814@ayourtch-mac> <F024FF5B-35A6-4221-952C-4A730A68C59D@delong.com> <alpine.OSX.2.00.1312080643090.68814@ayourtch-mac> <B561C767-677A-4A37-BA69-EB24951B2817@delong.com> <52A4C6FD.1080504@gmail.com> <98CACA9B-AD61-460A-93AC-D5EEA1176706@delong.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>
In-Reply-To: <EMEW3|04e90b90dff954d2bc6d2a53888d4abdq08HOU03tjc|ecs.soton.ac.uk|597F58BD-DCEA-4C4E-B7AB-DCCB416B3CFD@ecs.soton.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
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: Thu, 09 Jan 2014 17:29:09 -0000

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. 
 
> > 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).

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.

v2.23.0 | Report a Bug | By Email