Re: [Softwires] [Softwire] draft-ietf-softwire-map-00 does NOT reflect the consensus from the WG

Tom Taylor <tom.taylor.stds@gmail.com> Wed, 27 June 2012 12:21 UTC

Return-Path: <tom.taylor.stds@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 D021821F8692 for <softwires@ietfa.amsl.com>; Wed, 27 Jun 2012 05:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 elgBsg9v04WE for <softwires@ietfa.amsl.com>; Wed, 27 Jun 2012 05:21:16 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 95AA121F8691 for <softwires@ietf.org>; Wed, 27 Jun 2012 05:21:13 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so895981ggn.31 for <softwires@ietf.org>; Wed, 27 Jun 2012 05:21:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=j9XBJE8utpKYA9hs/d7n4jQnnrTxzHbWQR38EkDW0qI=; b=sqnJyvjgDkljgCicYQAVgYpJtVTJePKnc8TUBd/uqgKKzLGRHyl8l9yoS7xTj9qatg /5QAbbhzGDwMdw9thqyCg3rGH4rsnPmiu1Ddz1/7iBzw9gwy7qXdxyH8m+myPFomo94S rlMHqdVBrlSHDJ3C50/ZU8CYIvq2AT9hzF1YUVMt0SZ6hEXnjzZXecmLicbe8s7PQ+tV w6vTfOJqi9Xy6OIk/gVMI1sxaZ7eW7bmFrQkjL1fzqOi06W4ch30eG7gK59t4uEuR403 ZJXLVcHAHMklBdRd7UexxWSeJd5n4iRkpAktHvI/8yZOtu68/c7tSpnk8ztBNzrFMuVK G2VA==
Received: by 10.60.22.5 with SMTP id z5mr15642701oee.2.1340799673037; Wed, 27 Jun 2012 05:21:13 -0700 (PDT)
Received: from [127.0.0.1] (dsl-173-206-19-146.tor.primus.ca. [173.206.19.146]) by mx.google.com with ESMTPS id j10sm12752493oej.10.2012.06.27.05.21.08 (version=SSLv3 cipher=OTHER); Wed, 27 Jun 2012 05:21:11 -0700 (PDT)
Message-ID: <4FEAFAB3.5020200@gmail.com>
Date: Wed, 27 Jun 2012 08:21:07 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Maoke <fibrib@gmail.com>
References: <CC0F2D82.285F4%ian.farrer@telekom.de> <CAFFjW4ireDBzacCFDYgh3kn3+MXx1=m3Kab6Wp7TFwnHeyfwDw@mail.gmail.com> <CAH3bfADW1LN5nr1trd+Hu0tu4R3cHNEcx5yppN4p4Rh1bHaq1w@mail.gmail.com> <04DCBF0D-2B31-42E8-A363-22656FBAF447@gmail.com> <CAFUBMqURHk_AJfaTmx0vVJVuVFL0QaKZp15p=fZXX+Ftpf50cg@mail.gmail.com>
In-Reply-To: <CAFUBMqURHk_AJfaTmx0vVJVuVFL0QaKZp15p=fZXX+Ftpf50cg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120627-0, 27/06/2012), Outbound message
X-Antivirus-Status: Clean
Cc: softwires@ietf.org
Subject: Re: [Softwires] [Softwire] draft-ietf-softwire-map-00 does NOT reflect the consensus from the WG
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, 27 Jun 2012 12:21:17 -0000

An old cartoon I once saw, making fun of ISDN IIRC, showed a single 
socket on the outside of the wall, connected to a rat's-nest of 
connections on the inside. This seems apt for the present enterprise.

Tom Taylor

On 26/06/2012 9:48 PM, Maoke wrote:
> dear Satoru,
>
> 2012/6/26 Satoru Matsushima <satoru.matsushima@gmail.com>
>
>> On 2012/06/27, at 0:11, Qiong wrote:
>>
>>> Agree with Ian.
>>>
>>> MAP is designed and optimized for algorithmatic address mapping, but not
>> for per-subscriber rule mapping. Actually, the more you would like to
>> solve, more complicated it will become.
>>>
>>> I will certainly not buy MAP for per-subscriber case when MAP-T, MAP-E,
>> map-dhcp all becomes useless or not optimized. And I will not deploy
>> per-subscriber stateful and stateless solutions at the same.
>>>
>>> So I encourage two seperated approaches optimized for different
>> scenarios. It will be good for both.
>>>
>>> Do we really all forget about the "KISS" principle ?
>>
>> Not quite.
>> I believe that the most motivate to start this work in the wg has destined
>> MAP to be 'multi-protocol socket v2.0' that's what the former wg chair
>> wished to. Do you remember that?
>>
>
> i like the philosophy of "multi-protocol socket". however, i moderately
> doubt the "multi-protocol socket v2.0" is a perfect plan for every cases.
> in a quite good hotel, we see typically one 'multi-protocol socket' while a
> lot of local-standard sockets. i never think it will make me happy if i see
> every socket in my room is *multi-protocol*, occupying much spaces and
> quite noticeable on the walls. we need one to deploy somewhere not the only
> one type to deploy anywhere. ;-)
>
> therefore i understand the motivation of the wg is making a unified
> solution covering both encapsulation and translation in the framework of
> stateless, WITHOUT the exclusiveness against other solutions, more
> specifically suitable for a certain use case.
>
> cheers,
> maoke
>
>
>>
>> cheers,
>> --satoru
>>
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>
>
>
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>