Re: [Softwires] Comments on MAP-E draft

Tetsuya Murakami <tetsuya@ipinfusion.com> Thu, 01 March 2012 02:14 UTC

Return-Path: <tetsuya@ipinfusion.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 51EEF21E801E for <softwires@ietfa.amsl.com>; Wed, 29 Feb 2012 18:14:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level:
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, 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 uIAWKQSOw6x1 for <softwires@ietfa.amsl.com>; Wed, 29 Feb 2012 18:14:08 -0800 (PST)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE0921E801C for <softwires@ietf.org>; Wed, 29 Feb 2012 18:14:08 -0800 (PST)
Received: by daec6 with SMTP id c6so172137dae.27 for <softwires@ietf.org>; Wed, 29 Feb 2012 18:14:08 -0800 (PST)
Received-SPF: pass (google.com: domain of tetsuya@ipinfusion.com designates 10.68.228.193 as permitted sender) client-ip=10.68.228.193;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of tetsuya@ipinfusion.com designates 10.68.228.193 as permitted sender) smtp.mail=tetsuya@ipinfusion.com
Received: from mr.google.com ([10.68.228.193]) by 10.68.228.193 with SMTP id sk1mr14233255pbc.60.1330568048100 (num_hops = 1); Wed, 29 Feb 2012 18:14:08 -0800 (PST)
Received: by 10.68.228.193 with SMTP id sk1mr11807985pbc.60.1330568048035; Wed, 29 Feb 2012 18:14:08 -0800 (PST)
Received: from [10.70.2.197] ([12.248.239.142]) by mx.google.com with ESMTPS id f8sm674490pbe.42.2012.02.29.18.14.06 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 29 Feb 2012 18:14:07 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_02611177-E200-41F9-9438-2BB3B9E429B6"
From: Tetsuya Murakami <tetsuya@ipinfusion.com>
X-Priority: 3
In-Reply-To: <2012022917183726704470@gmail.com>
Date: Wed, 29 Feb 2012 18:14:04 -0800
Message-Id: <D0B7051C-215E-40EE-B79C-15F6D74308B7@ipinfusion.com>
References: <2012022917183726704470@gmail.com>
To: "sunqi.csnet.thu" <sunqi.csnet.thu@gmail.com>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQkK3vwLqXAMFkBWHLG/CMAntQ6e00jei7QC4voi0mIUQy21yJagAuQdRsgGLDnSvquHkAPs
Cc: softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Comments on MAP-E draft
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: Thu, 01 Mar 2012 02:14:09 -0000

Hi Qi,

Thank you for your comments. Please see my comments in line.

On 2012/02/29, at 1:18, Qi Sun wrote:

> Hi Murakami,
>      It's a good draft and makes a nice support for the MAP mechanism. I would like to propose some comments on the draft(sorry if they've been discussed ever). Please check below.
> -----------------------------------------------------------------
>  Section 
> 5.2 Packet Forwarding 
> Behavior on MAP-E BR
> Part (b) BR reception of an IPv6 packet
>             BR derives a CE IPv6 address from
>             the IPv4 source address or the IPv4 source
>             address and the source port in the encapsulated
>             IPv4 packet based on the BMR.  If the CE IPv6
>             address is eqaul to the IPv6 source address in
>             the received IPv6 packet, BR decapsulates the
>             IPv4 packet and then forward it via the IPv4
>             interface.
> I have a few questions here.
> 1. How can the BR get from an IPv6 packet the IPv4 source address or the IPv4 source address and the source port in the encapsulated IPv4 packet?
In case of MAP-E, IPv4 packet is encapsulated in IPv6. The above text is for check the validation of the received packet. In terms of IPv6 packet received at BR, the IPv6 source address should be based on the IPv6 prefix delegated to CE. Also, according to the MAP rule, IPv4 address and port number can be derived from the same delegated IPv6 prefix. So, BR can calculate CE IPv6 address from the IPv4 source address and source port number in IPv4 packet encapsulated in the received IPv6 packet. If the calculation is failed, then the packet could be dropped. If the calculation is succeeded but the calculated CE IPv6 address is not matched to the source IPv6 address in the received IPv6 packet, then the packet could be dropped.

> 2. If the received IPv6 packet is a normal one, instead of an IPv4-encapsulated packet, what will the BR do?  That is, dose the BR can act as a normal router?

In this case, BR should handle this IPv6 packet based on the normal IPv6 routing because the next header is not IPv4 in this case.

> 3. What can cause the inequality between the derived CE IPv6 address and the IPv6 source address in the received IPv6 packet? And what will BR do with it, discard it ?

It might depend on the implementation. But the derived CE IPv6 address must be same as the IPv6 source address in case of MAP-E because the derived CE IPv6 address should be the tunnel end-point address on the CE. So, the received packet should be discarded or not processed as MAP-E packet.

Thanks,
Tetsuya Murakami

> I'm looking forward to your reply~
>  
> Best Regards,
>  
> Qi Sun
> Tsinghua University, Beijing, China
>