IETF Logo Mail Archive

Re: [v6ops] Update IPv6 Wireline Incremental

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Tue, 04 October 2011 00:39 UTC

Return-Path: <Tina.Tsou.Zouting@huawei.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 3DA6021F8D4F for <v6ops@ietfa.amsl.com>; Mon, 3 Oct 2011 17:39:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.286
X-Spam-Level:
X-Spam-Status: No, score=-6.286 tagged_above=-999 required=5 tests=[AWL=0.312, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 74s0rwUULqOM for <v6ops@ietfa.amsl.com>; Mon, 3 Oct 2011 17:39:19 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 01AC721F8D1D for <v6ops@ietf.org>; Mon, 3 Oct 2011 17:39:19 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSI00FKTNAKVC@szxga05-in.huawei.com> for v6ops@ietf.org; Tue, 04 Oct 2011 08:42:20 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSI00LHUNAJYV@szxga05-in.huawei.com> for v6ops@ietf.org; Tue, 04 Oct 2011 08:42:20 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEA82227; Tue, 04 Oct 2011 08:42:19 +0800
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 04 Oct 2011 08:42:17 +0800
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.147]) by szxeml405-hub.china.huawei.com ([10.82.67.60]) with mapi id 14.01.0270.001; Tue, 04 Oct 2011 08:42:12 +0800
Date: Tue, 04 Oct 2011 00:42:11 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <CADiurz3-Spt-6o8U_fmMRLVvGrkD_CHkWQFfQDOEzrL++L15cQ@mail.gmail.com>
X-Originating-IP: [10.193.34.158]
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A88DC76B@szxeml526-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_9lGXli/0Zok6TJ5N5Oz4HQ)"
Content-language: en-US
Accept-Language: en-US, zh-CN
Thread-topic: [v6ops] Update IPv6 Wireline Incremental
Thread-index: AQHMgiJqs6ee1mEnVUqO9TAERtKqApVrWASQ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-cr-hashedpuzzle: Edg0 Gjeo Hrt4 JMAX JUjo LpYS L8s0 MU7u PoCA Qe4b SjmQ Ul4y Uo/c WngM Ws31 Wzh8; 2; dgA2AG8AcABzAEAAaQBlAHQAZgAuAG8AcgBnADsAdgBpAGMAdABvAHIALgBrAHUAYQByAHMAaQBuAGcAaABAAGcAbQBhAGkAbAAuAGMAbwBtAA==; Sosha1_v1; 7; {9F2EACF3-FF93-4AB1-85AD-B1D059C05E67}; dABpAG4AYQAuAHQAcwBvAHUALgB6AG8AdQB0AGkAbgBnAEAAaAB1AGEAdwBlAGkALgBjAG8AbQA=; Tue, 04 Oct 2011 00:42:05 GMT; UgBFADoAIABbAHYANgBvAHAAcwBdACAAVQBwAGQAYQB0AGUAIABJAFAAdgA2ACAAVwBpAHIAZQBsAGkAbgBlACAASQBuAGMAcgBlAG0AZQBuAHQAYQBsAA==
x-cr-puzzleid: {9F2EACF3-FF93-4AB1-85AD-B1D059C05E67}
X-CFilter-Loop: Reflected
References: <CADiurz3-Spt-6o8U_fmMRLVvGrkD_CHkWQFfQDOEzrL++L15cQ@mail.gmail.com>
Subject: Re: [v6ops] Update IPv6 Wireline Incremental
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: Tue, 04 Oct 2011 00:39:20 -0000

Victor,
Support in general.

6.4.1.  CGN Deployment Considerations

   This section will be expanded to include deployment considerations
   for CGN


A full stop here is missing.

You may want to add some general description here. For example, as Chris said,

CGNs may be deployed using a phased hybrid approach
Deploy CGNs regionally to start
Add CGNs at large headends as needed
Rule-of-thumb: xxK subscribers/CGN


Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html


From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of Victor Kuarsingh
Sent: Monday, October 03, 2011 4:16 PM
To: v6ops@ietf.org
Subject: [v6ops] Update IPv6 Wireline Incremental

WG,

Updated version of draft-kuarsingh-wireline-incremental-ipv6-01.

The intent here is to provide a potential path for Wireline Operators who may be looking to support IPv6 in an incremental fashion but may not be fully up to speed on all the various technologies out there, or may not have a full grasp on how to boil it down to a potential plan for their network.

The draft also presents a view on what technologies may be used to solve some of the issues the face many operators over the next few years (introduction of IPv6, infancy IPv6 on access network equipment, exhaustion of IPv4,  future optimizations etc).

This also attempts to build on the v4v6framework draft (draft-ietf-v6ops-v4v6tran-framework)

Future version will also supply further suggestions on some deployment considerations including diagrams.

Comments, suggestions and attacks welcome.

regards,

Victor Kuarsingh

v2.23.0 | Report a Bug | By Email