Re: [v6ops] I-D Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 17 March 2011 19:41 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0279E3A6B07 for <v6ops@core3.amsl.com>; Thu, 17 Mar 2011 12:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level:
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599]
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 sQx34dYsBiAM for <v6ops@core3.amsl.com>; Thu, 17 Mar 2011 12:41:56 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id DC0D53A6B09 for <v6ops@ietf.org>; Thu, 17 Mar 2011 12:41:54 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id A2A589C; Thu, 17 Mar 2011 20:43:17 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A082C9A for <v6ops@ietf.org>; Thu, 17 Mar 2011 20:43:17 +0100 (CET)
Date: Thu, 17 Mar 2011 20:43:17 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: IPv6 Ops WG <v6ops@ietf.org>
In-Reply-To: <4D8260E2.2080600@gmail.com>
Message-ID: <alpine.DEB.2.00.1103172035400.4842@uplift.swm.pp.se>
References: <20110305184502.18531.25548.idtracker@localhost> <76C43B2A-FEE5-4328-AB05-A10C38B23B2C@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3F8B93C@XMB-RCD-109.cisco.com> <C895B643-E461-4191-BAC3-EF735311F2F0@apple.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3F8B9B0@XMB-RCD-109.cisco.com><E76372ED-41A1-4987-9ECF-888B285DD606@apple.com> <4D7E685A.80202@bogus.com> <5B6B2B64C9FE2A489045EEEADDAFF2C301049872@XMB-RCD-109.cisco.com> <alpine.DEB.2.00.1103152011560.4842@uplift.swm.pp.se> <5B6B2B64C9FE2A489045EEEADDAFF2C301049924@XMB-RCD-109.cisco.com> <4D7FE427.7000201@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C30104A0ED@XMB-RCD-109.cisco.com> <4D8260E2.2080600@gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 17 Mar 2011 19:41:57 -0000

On Fri, 18 Mar 2011, Brian E Carpenter wrote:

> Nothing, I think. Until we have clarity on the issues in 
> draft-v6ops-multihoming-without-nat66 I don't see what we can say, 
> beyond MUST support multiple prefixes and MAY support multiple WAN 
> interfaces.

A long time ago I did exactly this scenario, moved an enterprise from 
PA-subnet1 from ISP1 to PA-subnet2 at ISP2 over one month period, and both 
needed to work, and both ISPs did uRPF checking.

I normally say that whatever process came up with the answer "policy 
routing" (routing based on source IP address) you made a serious mistake 
way before you came to that answer, but in this case I think it's actually 
a valid mechanism.

In the draft I didn't see any mention of it, was it considered and 
rejected?

If one CPE has two WAN links and it gets two different PD prefixes, then 
it can send traffic to each one based on source IP address. How this would 
be discovered in a two WAN CPE router scenario I don't have an answer for. 
Whatever is done, it would also cause suboptimal routing for one of the 
prefixes since traffic would be routed via whatever default gw the host 
chose.

The major problem I see is how the two different CPEs would discover each 
others PD prefixes so they can do source based routing.

... or am I totally out in my thinking, perhaps this has been discussed 
and rejected before?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se