IETF Logo Mail Archive

Re: [v6ops] new draft: draft-ietf-v6ops-6204bis

Fred Baker <fred@cisco.com> Wed, 12 October 2011 20:59 UTC

Return-Path: <fred@cisco.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 EC49E21F8C1F for <v6ops@ietfa.amsl.com>; Wed, 12 Oct 2011 13:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.407
X-Spam-Level:
X-Spam-Status: No, score=-102.407 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ZJaBnVD9eR6J for <v6ops@ietfa.amsl.com>; Wed, 12 Oct 2011 13:59:49 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 36BC021F8B55 for <v6ops@ietf.org>; Wed, 12 Oct 2011 13:59:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=721; q=dns/txt; s=iport; t=1318453189; x=1319662789; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=2lTkMpucJ1N0aQBdtKywL7OVbqQOMfhcgDfMmmuLEiI=; b=UX+9cD06yMPNOlNrsx5EgAIW9sdugz3vwiCOxoLD89piJWOuLNkmp3+U 8aKZrbgkjqFpWUiY2wJQus164KoOwTK12ZSvSGOh5N9Ncz1i1/t71EdNc PHP8K7Qiir1dFslZCV8FgKnLxhMs85C4Nsvg/duOf9/j8WDftGLCrEkl9 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAC//lU6tJXG8/2dsb2JhbABDqDmBBYFTAQEBAQIBEgEnPwULC0ZXBjWHXJpsAZ5LhndhBJN1hSiMSA
X-IronPort-AV: E=Sophos;i="4.69,336,1315180800"; d="scan'208";a="27974599"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-5.cisco.com with ESMTP; 12 Oct 2011 20:59:48 +0000
Received: from Freds-Computer.local (rtp-vpn3-1394.cisco.com [10.82.221.120]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9CKxfKU013327; Wed, 12 Oct 2011 20:59:44 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 12 Oct 2011 16:59:46 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 12 Oct 2011 16:59:46 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4E95ED46.1010404@viagenie.ca>
Date: Wed, 12 Oct 2011 16:59:26 -0400
Message-Id: <24BE1240-F514-4408-BEE6-F37A9AB1E932@cisco.com>
References: <201110111355.p9BDt1M23806@ftpeng-update.cisco.com> <282BBE8A501E1F4DA9C775F964BB21FE3EB758B7A8@GRFMBX704BA020.griffon.local> <1B8E4C5A-D08B-4F37-B701-A39745136A33@cisco.com> <4E95ED46.1010404@viagenie.ca>
To: Simon Perreault <simon.perreault@viagenie.ca>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-ietf-v6ops-6204bis@tools.ietf.org" <draft-ietf-v6ops-6204bis@tools.ietf.org>
Subject: Re: [v6ops] new draft: draft-ietf-v6ops-6204bis
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, 12 Oct 2011 20:59:50 -0000

On Oct 12, 2011, at 3:40 PM, Simon Perreault wrote:

> On this point: we already have consensus in BEHAVE to make PCP a
> requirement for the CGN requirements draft, even though the situation is
> pretty much the same (operators wanting to quote an RFC number in RFPs).
> So there's precedent.

Hmm. If there's a CGM requirements draft, does that extend to IPv4 CPE Routers appropriate in a CGN environment? If so, that might be the "IPv4 CGN" document I suggested Roberta write.

I'm not certain that an IPv6 CPE Routers document should be giving instructions for IPv4 CPE Routers... I'd personally rather keep this one clean and pull the rest into an IPv4-related draft. Color me biased.

v2.23.0 | Report a Bug | By Email