Re: [v6ops] Enterprise Guidance on IPv6 (draft-chkpvc-enterprise-incremental-ipv6-00)
Victor Kuarsingh <victor.kuarsingh@gmail.com> Wed, 13 June 2012 18:32 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 DC3C711E8089 for <v6ops@ietfa.amsl.com>; Wed, 13 Jun 2012 11:32:09 -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 9h7omYq4xNiu for <v6ops@ietfa.amsl.com>; Wed, 13 Jun 2012 11:32:09 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B6B5811E807F for <v6ops@ietf.org>; Wed, 13 Jun 2012 11:32:08 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so671467vbb.31 for <v6ops@ietf.org>; Wed, 13 Jun 2012 11:32:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :in-reply-to:mime-version:content-type:content-transfer-encoding; bh=jdl4IvydH0c+/fozfcWaj2Gf7wnUH2fTLcoFru9bQAo=; b=0nJN63kuVw5rDI4ygxsOHe1HBVFIvRuqEPlr3ncd2u1YfBR52eZ15u3GBUydElLLZZ GAdGVxwlb6liMHGlflECp4MkN5xWD4JJ6p1401QBHmt2eC8KlO0sO0t0AGGY+OXsTgbO o17BcRFOOh2rA52xx0LPqDfAVuOorEUhdaCKtel2BHNl/O1fjlfAiedRO8JURFQs8Oh1 LEGeCZKYVKV42BG685WjklES41HKDfeY7AtIHzbwPw1hjoFbHbY9Tlt9ju30P78nXeJh BAhwJewdFVSG0QLcH202OJuB/lk69PbEzwbr3OBUUfzwN9WdyFi3jufsP4L1effh2FeC DuTA==
Received: by 10.220.150.134 with SMTP id y6mr17572662vcv.43.1339612328226; Wed, 13 Jun 2012 11:32:08 -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 c17sm2777747vdj.11.2012.06.13.11.32.04 (version=SSLv3 cipher=OTHER); Wed, 13 Jun 2012 11:32:07 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Date: Wed, 13 Jun 2012 14:32:03 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Ray Hunter <v6ops@globis.net>, Lee Howard <lee@asgard.org>
Message-ID: <CBFE5433.1B8CF%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] Enterprise Guidance on IPv6 (draft-chkpvc-enterprise-incremental-ipv6-00)
In-Reply-To: <4FD8B188.1000403@globis.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: 'IPv6 Operations' <v6ops@ietf.org>
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:32:10 -0000
Ray, How would you propose we work this concept in? These are good points overall, but would we expect a document focused IPv6 in the enterprise to also tackle fallout of architectural enhancements possible with IPv6? I would think that such a document/concept would be best managed in a separate document which was focused on that subject. I may have missed your point, but these are my initial thoughts. Regards, Victor K On 12-06-13 11:28 AM, "Ray Hunter" <v6ops@globis.net> wrote: >Regardless of whether this draft is the vehicle or not, one thing that I >think is missing is that large enterprises currently almost universally >use some sort of centralized gateway or proxy to access the Internet, >coupled with "split DNS" (whether the IETF likes that or not). > >Many enterprises have expressed a desire to become "Internet Centric" >whatever that is. They're also moving very rapidly to cloud services for >generic applications. However, they'll still need private enterprise >networks with SLAs for many other business critical services ad interim, >at least until the generic Internet supports an equivalent of Diffserv. >Multiple IPv6 addresses per node, with a combination of PI space for the >enterprise network and PA space fromlocal providers, is making direct >proxy-free nat-free local Internet breakout potentially possible >(together with MIF and appropriate address selection). DNSSEC is also >potentially attractive to facilitate/ restore a basic end to end trust >model. > >So I think we know where we're starting, and I think we know where we >end up, but is there any operational advice available on the steps that >would be required to e.g. "unsplit DNS" (and remove proxies) when >introducing IPv6? > >In other words, how do we restore the end to end model without breaking >stuff on the way? > >regards, >RayH > >Lee Howard wrote: >> 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] Enterprise Guidance on IPv6 (draft-chkpvc… Lee Howard
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Ray Hunter
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Templin, Fred L
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Victor Kuarsingh
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Victor Kuarsingh
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Templin, Fred L
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Lee Howard
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Ray Hunter
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Brian E Carpenter
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Fred Baker
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Fred Baker
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Brian E Carpenter
- Re: [v6ops] Enterprise Guidance on IPv6 (draft-ch… Tina TSOU