Re: RE: RE: New Version Notification for draft-jiang-v6ops-incremental-cgn
JiangSheng 66104 <shengjiang@huawei.com> Thu, 21 May 2009 18:13 UTC
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 687E83A6B4C for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 21 May 2009 11:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.324
X-Spam-Level:
X-Spam-Status: No, score=-0.324 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VgVy-oNs0Wpr for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 21 May 2009 11:13:25 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1AC9E3A6A33 for <v6ops-archive@lists.ietf.org>; Thu, 21 May 2009 11:13:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1M7ChT-000Mcu-Ry for v6ops-data0@psg.com; Thu, 21 May 2009 18:09:03 +0000
Received: from [119.145.14.66] (helo=szxga03-in.huawei.com) by psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from <shengjiang@huawei.com>) id 1M7ChE-000Mbo-Go for v6ops@ops.ietf.org; Thu, 21 May 2009 18:08:56 +0000
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KK00052NAEMIF@szxga03-in.huawei.com> for v6ops@ops.ietf.org; Fri, 22 May 2009 02:08:46 +0800 (CST)
Received: from huawei.com ([172.17.1.36]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KK000349AEMP3@szxga03-in.huawei.com> for v6ops@ops.ietf.org; Fri, 22 May 2009 02:08:46 +0800 (CST)
Received: from [172.24.1.6] (Forwarded-For: [213.3.13.134]) by szxmc04-in.huawei.com (mshttpd); Fri, 22 May 2009 02:08:46 +0800
Date: Fri, 22 May 2009 02:08:46 +0800
From: JiangSheng 66104 <shengjiang@huawei.com>
Subject: Re: RE: RE: New Version Notification for draft-jiang-v6ops-incremental-cgn
In-reply-to: <474EEBD229DF754FB83D256004D021080BC9A4B2@XCH-NW-6V1.nw.nos.boeing.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
Cc: v6ops@ops.ietf.org, shengjiang@huawei.com
Message-id: <fbb185b5445d.445dfbb185b5@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug 8 2006)
Content-type: text/plain; charset="iso-8859-1"
Content-language: en
Content-transfer-encoding: quoted-printable
Content-disposition: inline
X-Accept-Language: en
References: <39C363776A4E8C4A94691D2BD9D1C9A105F0719F@XCH-NW-7V2.nw.nos.boeing.com> <000001c9d502$9843c980$5b0c6f0a@china.huawei.com> <39C363776A4E8C4A94691D2BD9D1C9A105F0726E@XCH-NW-7V2.nw.nos.boeing.com> <39C363776A4E8C4A94691D2BD9D1C9A105F075C2@XCH-NW-7V2.nw.nos.boeing.com> <4A127FA0.6050603@free.fr> <39C363776A4E8C4A94691D2BD9D1C9A105F43989@XCH-NW-7V2.nw.nos.boeing.com> <20090519192430.GK2776@Space.Net> <474EEBD229DF754FB83D256004D021080BC9A0D9@XCH-NW-6V1.nw.nos.boeing.com> <f995b50563b8.63b8f995b505@huawei.com> <474EEBD229DF754FB83D256004D021080BC9A4B2@XCH-NW-6V1.nw.nos.boeing.com>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>
Hi, Fleischman, We all work hard to contribute the fast change Internet world. Althrough we may have different opinions from time to time, our ultimate goals are the same, I believe. I will read and comment on RANGER. Best regards, Sheng ----- Original Message ----- From: "Fleischman, Eric" <eric.fleischman@boeing.com> Date: Wednesday, May 20, 2009 11:51 pm Subject: RE: RE: New Version Notification for draft-jiang-v6ops-incremental-cgn To: JiangSheng 66104 <shengjiang@huawei.com> Cc: Gert Doering <gert@space.net>, "Templin, Fred L" <Fred.L.Templin@boeing.com>,Rémi Després <remi.despres@free.fr>, Brian E Carpenter <brian.e.carpenter@gmail.com>, v6ops@ops.ietf.org, guoseu@huawei.com, "Russert, Steven W" <steven.w.russert@boeing.com> > Sheng, > > I'm glad that our views are congruent. I believe that our shared > viewpoint is a reasonable one though I recognize that other > vectors are also possible. > > I apologize for my previous long posting. In hindsight, I wish > that I had solely stated that because the Internet is likely to > face a period of accelerated change in the next few years, with > accompanying challenges within the network operations domain, it > behooves us to adopt techniques that will help our community > weather these anticipated events. > > This is the reason why I personally have been encouraging > coworkers to consider RANGER because I believe that it has > preserved the original intent of the founders of the Internet in a > manner that would enable today's Internet to flourish and evolve > during the difficult challenges ahead. > > I would appreciate it if you all would please read and consider > RANGER and the new RANGERS I-D and share your insights on those > concepts. A strength of our community is the quality of our > technical discussions together. > > Best wishes, > > --Eric Fleischman > > -----Original Message----- > From: JiangSheng 66104 [mailto:shengjiang@huawei.com] > Sent: Tuesday, May 19, 2009 11:48 PM > To: Fleischman, Eric > Cc: Gert Doering; Templin, Fred L; Rémi Després; Brian E > Carpenter; v6ops@ops.ietf.org; guoseu@huawei.com; Russert, Steven > W; shengjiang@huawei.com > Subject: Re: RE: New Version Notification for draft-jiang-v6ops- > incremental-cgn > > > end users view networks as a business overhead expense and are > > unlikely to needlessly spend money on networking technology > without a > > solid business motivation to do so. I went on to explain that > IPng is > > unlikely to be deployed by us end users unless it becomes > bundled with > > a business requirement, the most compelling of which would be a > new > > Killer Application that demanded IPv6 capabilities in order to > > function. > > Fully agreed. This is particularly true for IPv6 deployment in > last ten year - failure to find a killer application. A right > business model is actually more important than technology itself. > > > At this current time, IPv6 is very immature and IPv6 deployments > have > > very high risk when compared to IPv4 for the end user. There are > only > > negative business reasons for deploying IPv6 at this time (i.e., > I can > > articulate many compelling business reasons to NOT deploy IPv6 > but the > > only reason to deploy it in the USA today is government decree -- > > > which didn't work for OSI and is unlikely to work alone by > itself for > > IPv6.). There are currently no technical reasons for the end > user to > > prefer or want IPv6 over IPv4. > > I believe this situation is changed. IPv4 has reached its > limitation. End-user will soon find that they could NOT obtain a > public IPv4 address and with private IPv4 address (maybe more than > one NAT in the way) they were only able to communicate with part > of Internet world. ISP has met the problem that they cannot adopt > new services due to the lack of public address. > > > Unless this changes in the future, IPv6 will continue to not be > > deployed by end users despite the efforts of Apple and Microsoft > and > > others to ease its adoption. But then, since not all ISPs > support IPv6 > > today and the DFZ Internet is currently unprepared for the BGP > scaling > > problems that would arise with a mixed IPv4- > > IPv6 infrastructure this is probably A Good Thing. > > This is a real issue which has been ignored by IPv6 community for > years. My guess is IPv6 community does not want to discuss this > because it may even more block IPv6 deployment. However, it is > time for us to face it and solve it or avaoid it. > > > I personally *HOPE* that IPv6 will become deployed -- after all, > I > > spent many years helping to create it. But my experience with > pre- > > TCP/IP protocols (I used to be an SNA and BSC "expert") is that > even > > if IPv6 becomes widely deployed, IPv4 will endure for a > surprisingly > > long time (decades). > > Yes, it will be years. I believe the whole internet society has > accepted this and be prepared for a 25+ year co-existing period. > > Best regards, > > Sheng > >
- FW:New Version Notification for draft-jiang-v6ops… Sheng Jiang
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- Re: New Version Notification for draft-jiang-v6op… Brian E Carpenter
- Re: New Version Notification for draft-jiang-v6op… Brian E Carpenter
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- RE: New Version Notification for draft-jiang-v6op… Sheng Jiang
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- Re: New Version Notification for draft-jiang-v6op… Rémi Després
- Re: New Version Notification for draft-jiang-v6op… Rémi Després
- Re: New Version Notification for draft-jiang-v6op… Rémi Després
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- Re: New Version Notification for draft-jiang-v6op… Rémi Després
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- Re: New Version Notification for draft-jiang-v6op… Gert Doering
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- Re: New Version Notification for draft-jiang-v6op… Gert Doering
- Re: RE: New Version Notification for draft-jiang-… JiangSheng 66104
- Re: New Version Notification for draft-jiang-v6op… Mark Townsley
- Re: RE: New Version Notification for draft-jiang-… Mohacsi Janos
- Re: New Version Notification for draft-jiang-v6op… Seiichi Kawamura
- Re: New Version Notification for draft-jiang-v6op… Rémi Després
- Re: New Version Notification for draft-jiang-v6op… Mohacsi Janos
- Re: New Version Notification for draft-jiang-v6op… JORDI PALET MARTINEZ
- Re: New Version Notification for draft-jiang-v6op… JiangSheng 66104
- Re: RE: New Version Notification for draft-jiang-… JiangSheng 66104
- Re: New Version Notification for draft-jiang-v6op… Rémi Després
- Re: New Version Notification for draft-jiang-v6op… Mark Townsley
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- Re: New Version Notification for draft-jiang-v6op… Mohacsi Janos
- Re: RE: RE: New Version Notification for draft-ji… JiangSheng 66104
- Re: New Version Notification for draft-jiang-v6op… Brian E Carpenter
- Re: New Version Notification for draft-jiang-v6op… Mohacsi Janos
- RE: New Version Notification for draft-jiang-v6op… Templin, Fred L
- RFC4890 question (was: RE: New Version Notificati… Templin, Fred L
- Re: RFC4890 question (was: RE: New Version Notifi… Mohacsi Janos
- draft-jiang-v6ops-incremental-cgn Brian E Carpenter
- Re: draft-jiang-v6ops-incremental-cgn Fred Baker
- RE: draft-jiang-v6ops-incremental-cgn Templin, Fred L
- Re: draft-jiang-v6ops-incremental-cgn Fred Baker
- RE: draft-jiang-v6ops-incremental-cgn Templin, Fred L
- Re: draft-jiang-v6ops-incremental-cgn Brian E Carpenter