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

Victor Kuarsingh <victor.kuarsingh@gmail.com> Wed, 13 June 2012 18:44 UTC

Return-Path: <victor.kuarsingh@gmail.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 55D8C11E8079 for <v6ops@ietfa.amsl.com>; Wed, 13 Jun 2012 11:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.643
X-Spam-Level:
X-Spam-Status: No, score=-2.643 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, 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 BieP4DOHk6ju for <v6ops@ietfa.amsl.com>; Wed, 13 Jun 2012 11:44:02 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7500511E8072 for <v6ops@ietf.org>; Wed, 13 Jun 2012 11:44:01 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so596506vcq.31 for <v6ops@ietf.org>; Wed, 13 Jun 2012 11:44:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:date:subject:from:to:message-id:thread-topic:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=Qo4hF3Ng9weE5XshVxC9ojaYCQSMNZu2BaO7EC8Xzu8=; b=fnRRSzLEoltOVN7CC3a5ieTpAGzgnPCirBdIHdNijykMd2TdO4RKYPDcXrj81Tsw6j 6rVFmMvYu9lXb7CIBu+xnLW3kw4HmzicNZclQr2fjhl6uxvICb9JK/KG2DOlbhavGZFO eJwIenpNgj9u5XvFhC2VMDOxcQQN09cAOznSzqeTUn0SfIMVe7WZoAVvLUUnrWK+Ddmk xwNvRDBEkc9+lcwT6J82izey1L43TuowiNXSOxzuHFdtXrWr8TqCNgz2corYkeCFB4iw sM/AxKxmgCpZ2g8Zhb0hjFz0Zw+28GZHQdnP0gWK3KNeZnm4D20rJbpOYzeLNjyVVL55 AV+w==
Received: by 10.220.215.136 with SMTP id he8mr17758916vcb.13.1339613040945; Wed, 13 Jun 2012 11:44:00 -0700 (PDT)
Received: from [192.168.1.123] (CPEc0c1c0d0a27e-CM001bd7a9dea0.cpe.net.cable.rogers.com. [173.34.66.20]) by mx.google.com with ESMTPS id l4sm2832894vdh.1.2012.06.13.11.43.54 (version=SSLv3 cipher=OTHER); Wed, 13 Jun 2012 11:43:59 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Date: Wed, 13 Jun 2012 14:43:47 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Lee Howard <lee@asgard.org>, 'IPv6 Operations' <v6ops@ietf.org>
Message-ID: <CBFE5509.1B8D5%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] Enterprise Guidance on IPv6 (draft-chkpvc-enterprise-incremental-ipv6-00)
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65D375830E1@XCH-NW-01V.nw.nos.boeing.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
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:44:03 -0000

Fred,

I would (personally) tend to agree.  Given the details from
"draft-templin-v6ops-ispos", would a reference to that document fit the
bill?  

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