Re: [OPSAWG] Review of draft-ietf-opsawg-lsn-deployment-01
Christopher LILJENSTOLPE <liljenstolpe@gmail.com> Wed, 07 November 2012 18:17 UTC
Return-Path: <liljenstolpe@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6D7B21F8C72 for <opsawg@ietfa.amsl.com>; Wed, 7 Nov 2012 10:17:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4zi0LkLsksrK for <opsawg@ietfa.amsl.com>; Wed, 7 Nov 2012 10:17:44 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB2221F8C71 for <opsawg@ietf.org>; Wed, 7 Nov 2012 10:17:44 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so834799dan.31 for <opsawg@ietf.org>; Wed, 07 Nov 2012 10:17:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=JIuULkXkET6ZF2RTTSBl5xiOSphOaHp/QbOU0EJp6cQ=; b=yMgrfuZeA6IRdsat92OKPf48rZby3+ij8MSeX/PTW7Wg5qpykBBLwvjlS+0JsAYJRh rT4CD3V/IoPEoY05p4IT9vpAAVx7Du5uS1zeObIHia136RiMiKoIp+ADOiSElRt+iGHl HLI6o73PwOfECLLjPvKJkczjJUcuIwDjX4LaGMaOV+1ogCSScZw84d7bNYwtjGpekZQs b1eb4taPDBhh5HgqBUE+EAF8q7mAxikPZbg40534/O+KbHnAnghDEhC3LrkBZl9hb4Vl Wphn9gQQ1OnTafSm9GMYMUiqc18TX9ITq3DzHVyGKnt2Y3aReEFLtWuzSFS3Y/Hzj6RP HdIQ==
Received: by 10.68.234.201 with SMTP id ug9mr9505835pbc.63.1352312263883; Wed, 07 Nov 2012 10:17:43 -0800 (PST)
Received: from ?IPv6:2001:df8::96:c56a:9740:ff9a:54d? ([2001:df8:0:96:c56a:9740:ff9a:54d]) by mx.google.com with ESMTPS id az8sm14636011pab.24.2012.11.07.10.17.42 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Nov 2012 10:17:42 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Christopher LILJENSTOLPE <liljenstolpe@gmail.com>
In-Reply-To: <CCC00708.399D3%victor.kuarsingh@gmail.com>
Date: Wed, 07 Nov 2012 10:17:40 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <03B90D35-4CBA-4968-8219-38FA85D071E8@gmail.com>
References: <CCC00708.399D3%victor.kuarsingh@gmail.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Review of draft-ietf-opsawg-lsn-deployment-01
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 18:17:44 -0000
You are welcome. Chris On 07Nov2012, at 09.40, Victor Kuarsingh <victor.kuarsingh@gmail.com> wrote: > Chris, > > Thanks for review. I will collect comments from the other two reviews and > then make updates accordingly. > > If discussions are required for particular points, I will pose those to > the list. > > Regards, > > Victor K > > On 2012-11-07 11:37 AM, "Christopher LILJENSTOLPE" > <liljenstolpe@gmail.com> wrote: > >> Greetings all, >> >> </chair hat> >> >> I've re-reviewed this version of the draft, and think that, on balance, >> it is a useful draft explaining how an operator may utilize IP VRF based >> VPN's to ease the deployment o NAT44 based CGN's. There are a few >> suggestions for the authors, outlined below. >> >> 1) I would indicate that the use of a services VRF is a MAY (in IETF >> parlance). I could have the services address space either in a services >> VRF, or I could actually have it in my non VRF tables (reducing the >> number of VRFs that I have to maintain in the network). >> >> 2) There is an assumption that appears in the document that the use of >> CGN's will increase over-time, leading to a decentralized model. I would >> instead phrase it that the model could be centralized or decentralized >> based on architectural, operational, or engineering requirements. As far >> as CGN use growth, I would phrase it that CGN deployment will probably >> follow a bell-like curve. It grows as I am adding more IPv4 customers >> when I have exhausted my IPv4 public block, and then will shrink as >> IPv6-only or the other transition mechanisms take hold. Forecasting a >> continual growth of CGN is probably (hopefully) incorrect. >> >> Christopher >> _______________________________________________ >> OPSAWG mailing list >> OPSAWG@ietf.org >> https://www.ietf.org/mailman/listinfo/opsawg > >
- [OPSAWG] Review of draft-ietf-opsawg-lsn-deployme… Christopher LILJENSTOLPE
- Re: [OPSAWG] Review of draft-ietf-opsawg-lsn-depl… Victor Kuarsingh
- Re: [OPSAWG] Review of draft-ietf-opsawg-lsn-depl… Christopher LILJENSTOLPE
- [OPSAWG] Review of draft-ietf-opsawg-lsn-deployme… Tom Taylor