Re: [MBONED] draft-zhou-mboned-multrans-path-optimization

"Lee, Yiu" <Yiu_Lee@Cable.Comcast.com> Fri, 23 March 2012 22:14 UTC

Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF2EA21E8087 for <mboned@ietfa.amsl.com>; Fri, 23 Mar 2012 15:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.08
X-Spam-Level:
X-Spam-Status: No, score=-101.08 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, 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 sbhWdRd9b62S for <mboned@ietfa.amsl.com>; Fri, 23 Mar 2012 15:14:57 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 52A3A21E8028 for <mboned@ietf.org>; Fri, 23 Mar 2012 15:14:57 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP id C7WM3M1.10723178; Fri, 23 Mar 2012 16:02:49 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%17]) with mapi id 14.01.0355.002; Fri, 23 Mar 2012 18:14:52 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Stig Venaas <stig@venaas.com>
Thread-Topic: [MBONED] draft-zhou-mboned-multrans-path-optimization
Thread-Index: AQHNCUJd/AgD57Uvr02hWDglqOH3PA==
Date: Fri, 23 Mar 2012 22:14:51 +0000
Message-ID: <CB926C04.1E70F%yiu_lee@cable.comcast.com>
In-Reply-To: <4F6CC439.8030608@venaas.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3415371290_368191"
MIME-Version: 1.0
Cc: "mboned@ietf.org" <mboned@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [MBONED] draft-zhou-mboned-multrans-path-optimization
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 22:14:58 -0000

Hi Stig,

On 3/23/12 2:43 PM, "Stig Venaas" <stig@venaas.com> wrote:

>Please don't get me wrong. I want to avoid translation as much as
>possible. Hence I also want to avoid double translation, although it
>might in some cases be better than tunneling.
>
>Some general things to consider are IMO
>
>1. Is it bad if multiple independent devices are performing the same
>    translation of the same data?
>
>    Translation at the source may guarantee it happens at most once.
>    Translation further down the tree may result in multiple devices
>    doing the same translation. Bandwidth is the main reason not to do
>    it at the source in a dual-stack network.
>
>2. With multiple translators, can we ensure that packets don't get
>    double translated unnecessary?
>
>    Basically if the network is dual-stack, can one make sure that
>    there never will be more than one translator on the path between
>    any source-receiver pair?

These are interesting questions. IMHO, if we can deploy the translator
closer to the access network and connect the source directly to the
translator, this could be the most trivial setup. If the sources are
placed high-up in the network and multiple translators are involved, that
may require some intelligence in the translator. I agree what you said, we
may need more than simple matrix to design what situation the translate
should translate the stream. It is also not simple to decide a v6 stream
using native v6 address is equal to a v4 stream using v4-embedded v6
address in term on content. When we have a mixed environment, we need to
know what deployment problem we are trying to solve.

B.R.,
Yiu