Re: [Softwires] MAP&4rd-U - DS routing replaced by v6-only routing in hub&spoke topology

Satoru Matsushima <satoru.matsushima@gmail.com> Tue, 07 February 2012 15:24 UTC

Return-Path: <satoru.matsushima@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20BC421F87C4 for <softwires@ietfa.amsl.com>; Tue, 7 Feb 2012 07:24:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_35=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 xfVA7awZAyLO for <softwires@ietfa.amsl.com>; Tue, 7 Feb 2012 07:24:16 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0FAB521F8771 for <softwires@ietf.org>; Tue, 7 Feb 2012 07:24:15 -0800 (PST)
Received: by wgbdt10 with SMTP id dt10so5409254wgb.13 for <softwires@ietf.org>; Tue, 07 Feb 2012 07:24:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=admP0pLNt6cDkPxvUTHj9mga7ClsKtezOSqmSbPO8oY=; b=WEVqGMINZQFs0Yq6hE83gp0gS50S3wCRosM0vFKDX9Pk/TqYdPQlyPoZJsa6Fah1c9 uU7mWjL3vju1W7SJTBzYJ2WC+VkEFtGzGQlAL1WijeFasxsxo8FO8YPD+0/YS3JuSo4r drzRmY/0lw3fLNQiVwSxhiv5eVEckU260gpdY=
Received: by 10.180.93.132 with SMTP id cu4mr20339953wib.9.1328628254980; Tue, 07 Feb 2012 07:24:14 -0800 (PST)
Received: from [10.115.194.117] (62-50-193-163.client.stsn.net. [62.50.193.163]) by mx.google.com with ESMTPS id s8sm24024165wiz.8.2012.02.07.07.24.13 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Feb 2012 07:24:14 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <3168C356-BDB1-4067-B4FB-3DBC993FA997@laposte.net>
Date: Tue, 7 Feb 2012 16:24:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <656A0695-607C-4006-AC21-43E3FED31159@gmail.com>
References: <554901A7-F23C-4197-8783-85D51B502EA3@laposte.net> <80C2DFB3-0E21-44F2-9FCA-F0B4CF88DA22@gmail.com> <2698466B-C775-4534-B60C-F4C0C2576B4A@laposte.net> <91E90DC9-99EC-44C2-89A9-7ED42E83701C@gmail.com> <3168C356-BDB1-4067-B4FB-3DBC993FA997@laposte.net>
To: =?utf-8?Q?R=C3=A9mi_Despr=C3=A9s?= <despres.remi@laposte.net>
X-Mailer: Apple Mail (2.1257)
Cc: Softwires WG <softwires@ietf.org>, Wojciech Dec <wdec@cisco.com>
Subject: Re: [Softwires] MAP&4rd-U - DS routing replaced by v6-only routing in hub&spoke topology
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2012 15:24:17 -0000

On 2012/02/07, at 16:10, Rémi Després wrote:

> 
> Le 2012-02-07 à 15:26, Satoru Matsushima a écrit :
> 
>> On 2012/02/07, at 14:03, Rémi Després wrote:
>> 
>>> 
>>> Le 2012-02-07 à 13:07, Satoru Matsushima a écrit :
>>> 
>>>> Hi Remi-san,
>>>> 
>>>> On 2012/02/07, at 11:13, Rémi Després wrote:
>>>> 
>>>>> Hello Ole, Tetsuya-san, Wojciech,
>>>>> 
>>>>> In a use case described in the 4rd-U draft (sec 5.3), an ISP replaces its dual-stack routing by IPv6-only routing.
>>>>> For this, independently from the number of IPv4 prefixes it has to support, it uses only one mapping rule.
>>>>> (By replacing each IPv4 route by an equivalent IPv6 route, it ensures that all customers keep their IPv4 addresses.)
>>>>> 
>>>> 
>>>> I don't think that it could work as you explained in that section. For example, the BR would need to check a received packet from a CE whether it has correct source address in mapping rule or not. It means that the BR must know all address mappings for CE between IPv4 addresses and IPv6 prefixes. Is it correct understanding?
>>> 
>>> Ingress filtering of the domain has checked that the IPv6 source starts with the delegated IPv6 prefix, a /112 which includes the IPv4 address. In the 4rd-E case, the BR checks that the source address in the IPv4 header matches that of the IPv6 address. There is therefore no need for the BR to know all IPv4 prefixes. At its IPv4 interface, all received packets start with one of them. At its IPv6 interface, all packets it receives have an embedded address that starts with one of these prefixes. 
>>> 
>> 
>> It looks like that you treat default mapping rule as a basic mapping rule to check source address consistency on the BR. It should work,
> 
> Yes, thanks.
> 
>> and the MAP too.
> 
> I don't see that.
> The bit that, in 4rd-U hub&spoke, is changed for the CE-to-BR direction has been included precisely to support this case. 
> Otherwise, packets sent by a CE to another CE would be routed directly to its destination, without a detour via a BR. 
> 

I don't think so. I just mention BR behavior here.
You mention CE behavior for whether the bit is set or not.

> 
>>>> I think that operators who already deploy such dual-stack network is supposed that they have address mapping table,
>>> 
>>> I would rather suppose that ISPs that have added IPv6-prefix delegation, say /56s, to an existing IPv4 network did it without mixing their IPv6 plan with their IPv4 prefixes.
>>> I am ready, however, to look seriously at individual cases where choices were different.
>> 
>> Basically provision MAP CE is based on its delegated IPv6 prefix in concept. It is opposed to your case but technically possible.
> 
> 
>> Now I concern that it requires much complicated CE implementation.
> 
> All what is required is that CEs set an address bit if hub&spoke topology is required.
> 

So how CE decide to set the bit, and when the CE figure it out?
--satoru



> 
> Cheers,
> RD
> 
> 
> 
>> 
>> 
>> cheers,
>> --satoru
>> 
>>> 
>>> Regards,
>>> RD
>>> 
>>> 
>>> 
>>>> they can provision each CE individually, and also they are capable to distribute the default mapping rule since they should install it into the CEs. In that situation, what's the motivation of why the operator want to provision with only default mapping rule?
>>>> 
>>>> cheers,
>>>> --satoru
>>>> 
>>>>> For this to work, the 4rd-U draft has a bit that, in the hub&spoke case, differs between CE-to-BR and BR-to-CE directions. Thus, packets sent to a CE take different routes depending on whether sent by a CE or a BR.
>>>>> 
>>>>> I don't see how the equivalent could work with the MAP documents you edited.
>>>>> Is it that such a use case is out of scope for MAP?
>>>>> Or did I miss something?
>>>>> 
>>>>> Cheers,
>>>>> RD
>>>>> 
>>>>> _______________________________________________
>>>>> Softwires mailing list
>>>>> Softwires@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/softwires
>>>> 
>>> 
>>