Re: [v6ops] Enterprise Guidance on IPv6 (draft-chkpvc-enterprise-incremental-ipv6-00)

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 13 June 2012 18:46 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C9A011E8096 for <v6ops@ietfa.amsl.com>; Wed, 13 Jun 2012 11:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.732
X-Spam-Level:
X-Spam-Status: No, score=-1.732 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vrkWjA1ZSqWx for <v6ops@ietfa.amsl.com>; Wed, 13 Jun 2012 11:46:40 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 92D6911E809F for <v6ops@ietf.org>; Wed, 13 Jun 2012 11:46:40 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q5DIkaB4028154 for <v6ops@ietf.org>; Wed, 13 Jun 2012 11:46:37 -0700
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [130.247.228.54]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q5DIkZoM028137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 13 Jun 2012 11:46:36 -0700
Received: from stl-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q5DIkcXa013188; Wed, 13 Jun 2012 13:46:38 -0500
Received: from XCH-NWHT-10.nw.nos.boeing.com (xch-nwht-10.nw.nos.boeing.com [130.247.25.113]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q5DIkb8i013162 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 13 Jun 2012 13:46:38 -0500
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-10.nw.nos.boeing.com ([130.247.25.113]) with mapi; Wed, 13 Jun 2012 11:46:37 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>, Lee Howard <lee@asgard.org>, 'IPv6 Operations' <v6ops@ietf.org>
Date: Wed, 13 Jun 2012 11:46:36 -0700
Thread-Topic: [v6ops] Enterprise Guidance on IPv6 (draft-chkpvc-enterprise-incremental-ipv6-00)
Thread-Index: Ac1JlIV7xKPWBw6lR6iqb8BN2ADWUQAABFUg
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65D37583235@XCH-NW-01V.nw.nos.boeing.com>
References: <E1829B60731D1740BB7A0626B4FAF0A65D375830E1@XCH-NW-01V.nw.nos.boeing.com> <CBFE5509.1B8D5%victor.kuarsingh@gmail.com>
In-Reply-To: <CBFE5509.1B8D5%victor.kuarsingh@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Subject: Re: [v6ops] Enterprise Guidance on IPv6 (draft-chkpvc-enterprise-incremental-ipv6-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 13 Jun 2012 18:46:41 -0000

Hi Victor,

> -----Original Message-----
> From: Victor Kuarsingh [mailto:victor.kuarsingh@gmail.com]
> Sent: Wednesday, June 13, 2012 11:44 AM
> To: Templin, Fred L; Lee Howard; 'IPv6 Operations'
> Subject: Re: [v6ops] Enterprise Guidance on IPv6 (draft-chkpvc-enterprise-
> incremental-ipv6-00)
> 
> Fred,
> 
> I would (personally) tend to agree.  Given the details from
> "draft-templin-v6ops-ispos", would a reference to that document fit the
> bill?

Assuming the authors decide to pursue this work further, then
a reference to "draft-templin-v6ops-isops" would be fine.

Thanks - Fred
fred.l.templin@boeing.com

 
> Regards,
> 
> Victor K
> 
> 
> 
> On 12-06-13 12:20 PM, "Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:
> 
> >Hi Lee,
> >
> >If you do decide to pursue this further, here are two
> >documents that fit this space:
> >
> >https://datatracker.ietf.org/doc/draft-templin-v6ops-isops/
> >https://datatracker.ietf.org/doc/rfc5214/
> >
> >Fred
> >fred.l.templin@boeing.com
> >
> >> -----Original Message-----
> >> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> >>Of
> >> Lee Howard
> >> Sent: Monday, June 11, 2012 11:37 AM
> >> To: 'Victor Kuarsingh'; 'IPv6 Operations'
> >> Subject: [v6ops] Enterprise Guidance on IPv6 (draft-chkpvc-enterprise-
> >> incremental-ipv6-00)
> >>
> >> When discussed in Taipei, it seemed there was real interest in updating
> >> guidance for
> >> enterprise networks.  From lack of list discussion, it now appears
> >>there's
> >> no interest in
> >> the WG.
> >>
> >> 1.  Are people interested?
> >> 2.  Should we let it die?
> >> 3.  Should we pursue other avenues of publication?
> >>
> >> Lee
> >>
> >> > -----Original Message-----
> >> > From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On
> Behalf
> >> Of
> >> Victor
> >> > Kuarsingh
> >> > Sent: Monday, March 26, 2012 7:42 AM
> >> > To: IPv6 Operations
> >> > Subject: Re: [v6ops] draft-chkpvc-enterprise-incremental-ipv6-00
> >> >
> >> > IPv6 WG,
> >> >
> >> > I would like to kick off some comments on this draft for other group
> >> members to comment.
> >> >
> >> > I do think (Bias noted) that this material is useful for Enterprises
> >>who
> >> need to being and/or
> >> > move their IPv6 deployments.  Many (of those I have worked with thus
> >> far)
> >> are bogged
> >> > down with personnel who are overwhelmed with what it may take to get
> >> IPv6
> >> moving on
> >> > their networks.
> >> >
> >> > The draft breaks the challenge down by areas of focus (rolled into
> >> > "Phases") which can help put this large challenge into bite size
> >>chunks
> >> for them. The draft
> >> > also provides some valid contextual information around
> >> > IPv6 and highlights areas which should be looked at.
> >> >
> >> > Given the good momentum we now have in the operator space, it would
> be
> >> good to see this
> >> > move forward into the Enterprise space.  I think such documents can
> >>help
> >> many of those still
> >> > waffling (too many to count) to start acting.
> >> >
> >> > Regards,
> >> >
> >> > Victor K
> >> >
> >> >
> >> > On 12-03-22 8:02 AM, "Tim Chown" <tjc@ecs.soton.ac.uk> wrote:
> >> >
> >> > >Hi,
> >> > >
> >> > >Due to a typo in the draft name, this draft didn't hit Fred's
> >>automated
> >> > >WG tools, so the authors would like to raise the draft on the list
> >>now
> >> > >with a view to securing a slot in Paris to discuss its value and
> >> content.
> >> > >
> >> > >In Taipei there was a comment in the WG session that there is no
> >> > >up-to-date v6ops guidance on enterprise networks, while other
> >>scenarios
> >> > >do have such texts.  So at the mic I invited people to join an
> effort
> >> > >to put something together.  There is a good breadth of experience
> >> > >across the people who stepped forward, and the result is available
> as
> >> > >
> >> >
> >>>http://www.ietf.org/id/draft-chkpvc-enterprise-incremental-ipv6-00.txt
> >> > >
> >> > >Does the WG think the subject matter of this draft is one we should
> >> > >pursue in the WG?  If so, is the structure and content appropriate?
> >>We
> >> > >need some positive feedback and comments in order for Fred to
> >>schedule
> >> > >us time in Paris.
> >> > >
> >> > >We have had a couple of people contact us off-list offering to help
> >> > >develop the content.  But we'd like some feedback from the WG before
> >> > >investing more time in doing so.  The -00 text is somewhat "rough",
> >>but
> >> > >we feel it could be polished into something quite useful for the
> >> > >community.
> >> > >
> >> > >Tim
> >> > >
> >> > >_______________________________________________
> >> > >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
> >>
> >>
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
>