Re: [Softwires] Fwd: New Version Notification for draft-chen-softwire-4rd-u-comment-00.txt

Maoke <fibrib@gmail.com> Wed, 11 April 2012 04:28 UTC

Return-Path: <fibrib@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 435B711E809B for <softwires@ietfa.amsl.com>; Tue, 10 Apr 2012 21:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.319
X-Spam-Level:
X-Spam-Status: No, score=-3.319 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 rWaOHeiFL3h9 for <softwires@ietfa.amsl.com>; Tue, 10 Apr 2012 21:28:55 -0700 (PDT)
Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by ietfa.amsl.com (Postfix) with ESMTP id 9298D11E8079 for <softwires@ietf.org>; Tue, 10 Apr 2012 21:28:53 -0700 (PDT)
Received: by qafi31 with SMTP id i31so3237949qaf.15 for <softwires@ietf.org>; Tue, 10 Apr 2012 21:28:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TsDptgaPBTPpA2e5FHNjv05m7VZtjNeHcb3jyC5Y8eI=; b=UUJrmSHvLT7eZ2dHzCSQ3AeKAmVZO7VP50PYsD09cOyHHIXQkkqYbB3Byci1jsvATj oyUWgVgGpfIVFoetKh/abUVGJrqknf/E4wEAojtk+a9ZDBQm5SUZ81YrdV1EF5iOEqxX 86HLOFb3MRkY/7XeyFoxdQ/l4ooBOAUA9WUxjS1rRM+WxFX5X+10NLNqbbfzSE/LJsEM nu8FYMXZrCBpDWxgWQ1mfSopmKvAEyFFR93WBEi4DPJh8ryH90oy0VBBOK0Omq5OWS9i PDmt6q2Vq4eoZuxbNoJQYcC/yls+s/XOnhPtdWpY9RpO26NrkC0QsyK6WV19LTdNo6kM ZQrQ==
MIME-Version: 1.0
Received: by 10.224.211.72 with SMTP id gn8mr18116049qab.10.1334118533116; Tue, 10 Apr 2012 21:28:53 -0700 (PDT)
Received: by 10.229.123.197 with HTTP; Tue, 10 Apr 2012 21:28:53 -0700 (PDT)
In-Reply-To: <DB75E76A-C29F-4499-AC4C-C47D58FEC3C0@huawei.com>
References: <20120410094728.8936.48011.idtracker@ietfa.amsl.com> <CAFUBMqXjnUK+-9eA4WwY27x_kkdNWO7vAJCYDpJk5jfd2K81xQ@mail.gmail.com> <CAC8QAcfDOVw7snGuDrm-+T-T4mSH4EMxpTVf__zQ0-ur5sX54A@mail.gmail.com> <DB75E76A-C29F-4499-AC4C-C47D58FEC3C0@huawei.com>
Date: Wed, 11 Apr 2012 04:28:53 +0000
Message-ID: <CAFUBMqUAPEWMhFqd-85vKVAzhMfySEkSHcaUVwBLP1WxJ-2NdA@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: "<sarikaya@ieee.org>" <sarikaya@ieee.org>
Content-Type: multipart/alternative; boundary="20cf300fac9741340d04bd5fad36"
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] Fwd: New Version Notification for draft-chen-softwire-4rd-u-comment-00.txt
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: Wed, 11 Apr 2012 04:28:56 -0000

hi Behcet,

2012/4/10 Tina TSOU <Tina.Tsou.Zouting@huawei.com>

>
>
> Sent from my iPad
>
> On Apr 10, 2012, at 10:12 AM, "Behcet Sarikaya" <sarikaya2012@gmail.com>
> wrote:
>
> > Hi Maoke,
> >
> > Thank you for your efforts in technical details of one specific
> > proposal on the table.
> >
> > However, I for one think that probably it is time to concentrate on
> > commonalities rather than the differences. As Alain indicated, these
> > proposals do have a lot of common points.
> >
>

that proposal is basically of a response to people's call for "describing
technical concerns in mind" about 4rd-U. commonality and difference is the
two sides of the same coin. if we don't understand what makes them exactly
different, we are also hard to understand how common they are. this
document is purposed in sharing such an understanding and therefore it
focuses only on the essential concerns -- the concerns regarding
architecture and protocol semantics.


> > Why don't (whoever) write a draft putting together all the common
> > points concentrating on CE to BR and abstracting out BIH, XLAT, etc.?
> > Such a draft can be of great value at this point, I think.
> That's MAP-D document.
> >
>

yes. as Tina points out, MAP deployment draft that we are working on plays
the role of clarifying the common deployment considerations with MAP
series. thanks!

best,
maoke


> > Regards,
> >
> > Behcet
> >
>
>