Re: [v6ops] I-D Action: draft-ietf-v6ops-enterprise-incremental-ipv6-05.txt

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 14 January 2014 15:43 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 58ED81AE0DA for <v6ops@ietfa.amsl.com>; Tue, 14 Jan 2014 07:43:10 -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 GwfF8hhn5Jcz for <v6ops@ietfa.amsl.com>; Tue, 14 Jan 2014 07:43:08 -0800 (PST)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id E7CD81ADF7F for <v6ops@ietf.org>; Tue, 14 Jan 2014 07:43:07 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s0EFgui7023576; Tue, 14 Jan 2014 09:42:56 -0600
Received: from XCH-PHX-310.sw.nos.boeing.com (xch-phx-310.sw.nos.boeing.com [130.247.25.169]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s0EFgpgY023550 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 14 Jan 2014 09:42:51 -0600
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.203]) by XCH-PHX-310.sw.nos.boeing.com ([169.254.10.30]) with mapi id 14.03.0158.001; Tue, 14 Jan 2014 07:42:50 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-enterprise-incremental-ipv6-05.txt
Thread-Index: AQHPEL1zbcMfkfj46kOaQyEoH+klm5qEWg4w
Date: Tue, 14 Jan 2014 15:42:49 +0000
Message-ID: <2134F8430051B64F815C691A62D9831819A9C8@XCH-BLV-504.nw.nos.boeing.com>
References: <20140112192103.21333.46615.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D98318198D2F@XCH-BLV-504.nw.nos.boeing.com> <1AB324DF-C922-4049-BB4D-77BFF50ACFDE@ecs.soton.ac.uk> <EMEW3|0fc2d12317b61936ed13b278a0779a3cq0D0DY03tjc|ecs.soton.ac.uk|1AB324DF-C922-4049-BB4D-77BFF50ACFDE@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|0fc2d12317b61936ed13b278a0779a3cq0D0DY03tjc|ecs.soton.ac.uk|1AB324DF-C922-4049-BB4D-77BFF50ACFDE@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] I-D Action: draft-ietf-v6ops-enterprise-incremental-ipv6-05.txt
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: Tue, 14 Jan 2014 15:43:10 -0000

Hi Tim,

> -----Original Message-----
> From: Tim Chown [mailto:tjc@ecs.soton.ac.uk]
> Sent: Monday, January 13, 2014 4:13 PM
> To: Templin, Fred L
> Cc: v6ops@ietf.org
> Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-enterprise-incremental-ipv6-05.txt
> 
> Hi Fred,
> 
> My concern with that is that we're tending towards methods and processes that have been proven in the
> document.
> 
> I'm not at all sure that AERO has had any widespread use in IPv6 enterprise sites.  What
> implementations/deployments have there been?

AERO is a simple set of modifications to standard IPv6 ND. I have created
an early implementation here:

http://linkupnetworks.com/seal/sealv2-1.0.tgz

but needs to be updated to more closely match the latest draft version.

With AERO, enterprise IPv6 deployment can be accomplished by simply
touching the end systems and by deploying a few servers - nothing else
needs to change. So, for example, if a handset manufacturer wanted to
supply an enterprise with IPv6-enabled product, they could add AERO
to their handset code base and have the enterprise stand up a few
servers (maybe something like a linux box).

Thanks - Fred
fred.l.templin@boeing.com 
 
> Tim
> 
> On 13 Jan 2014, at 22:42, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
> 
> > Authors,
> >
> > Please see the following for input to your document:
> >
> > http://www.ietf.org/mail-archive/web/v6ops/current/msg18488.html
> >
> > Please add a reference for AERO, and preferably a new section
> > describing incremental deployment of IPv6 in enterprise networks
> > using AERO.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> -----Original Message-----
> >> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> >> Sent: Sunday, January 12, 2014 11:21 AM
> >> To: i-d-announce@ietf.org
> >> Cc: v6ops@ietf.org
> >> Subject: [v6ops] I-D Action: draft-ietf-v6ops-enterprise-incremental-ipv6-05.txt
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >> This draft is a work item of the IPv6 Operations Working Group of the IETF.
> >>
> >>        Title           : Enterprise IPv6 Deployment Guidelines
> >>        Authors         : Kiran K. Chittimaneni
> >>                          Tim Chown
> >>                          Lee Howard
> >>                          Victor Kuarsingh
> >>                          Yanick Pouffary
> >>                          Eric Vyncke
> >> 	Filename        : draft-ietf-v6ops-enterprise-incremental-ipv6-05.txt
> >> 	Pages           : 34
> >> 	Date            : 2014-01-12
> >>
> >> Abstract:
> >>   Enterprise network administrators worldwide are in various stages of
> >>   preparing for or deploying IPv6 into their networks.  The
> >>   administrators face different challenges than operators of Internet
> >>   access providers, and have reasons for different priorities.  The
> >>   overall problem for many administrators will be to offer Internet-
> >>   facing services over IPv6, while continuing to support IPv4, and
> >>   while introducing IPv6 access within the enterprise IT network.  The
> >>   overall transition will take most networks from an IPv4-only
> >>   environment to a dual stack network environment and eventually an
> >>   IPv6-only operating mode.  This document helps provide a framework
> >>   for enterprise network architects or administrators who may be faced
> >>   with many of these challenges as they consider their IPv6 support
> >>   strategies.
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-v6ops-enterprise-incremental-ipv6/
> >>
> >> There's also a htmlized version available at:
> >> http://tools.ietf.org/html/draft-ietf-v6ops-enterprise-incremental-ipv6-05
> >>
> >> A diff from the previous version is available at:
> >> http://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-enterprise-incremental-ipv6-05
> >>
> >>
> >> Please note that it may take a couple of minutes from the time of submission
> >> until the htmlized version and diff are available at tools.ietf.org.
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops