IETF Logo Mail Archive

Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt

<Axel.Clauberg@telekom.de> Mon, 03 March 2014 16:58 UTC

Return-Path: <Axel.Clauberg@telekom.de>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 612B01A01E4 for <softwires@ietfa.amsl.com>; Mon, 3 Mar 2014 08:58:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aLU0tYKHzIQC for <softwires@ietfa.amsl.com>; Mon, 3 Mar 2014 08:58:06 -0800 (PST)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) by ietfa.amsl.com (Postfix) with ESMTP id B00501A00B6 for <softwires@ietf.org>; Mon, 3 Mar 2014 08:58:05 -0800 (PST)
Received: from he113445.emea1.cds.t-internal.com ([10.134.93.105]) by tcmail41.telekom.de with ESMTP/TLS/AES128-SHA; 03 Mar 2014 17:57:44 +0100
Received: from HE113454.emea1.cds.t-internal.com ([169.254.1.32]) by HE113445.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 3 Mar 2014 17:57:44 +0100
From: Axel.Clauberg@telekom.de
To: simon.perreault@viagenie.ca, softwires@ietf.org
Date: Mon, 03 Mar 2014 17:57:42 +0100
Thread-Topic: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt
Thread-Index: Ac83ABYwqCuIwqG0SMytNOuTMTtuiAAAHXrg
Message-ID: <68624C71FC488640828CBCD2FFCEB8D98597BAAD70@HE113454.emea1.cds.t-internal.com>
References: <20140211075445.17615.61208.idtracker@ietfa.amsl.com> <FD878467-904B-4441-95B4-11D4461A612E@employees.org> <CF237FDE.AACEB%ian.farrer@telekom.de> <CAFFjW4jOBfvnqCV4UH8qt0HA5zZ-35f+q5ZepzjnwGX5_Oj9Gg@mail.gmail.com> <8A1B81989BCFAE44A22B2B86BF2B76318A2CDB8ED2@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CAFFjW4iP2KqNJFtJPr5rp0tzRwM5TPjaqiSP5r13JqbX46ao7w@mail.gmail.com> <CD1D4FF6-9509-43B4-AFC4-4F1AF99D0C4D@gmx.com> <CAFFjW4ibkj_xpTuXrbYjxkdxD=+qNzapCGPHJwXsZ-k0ZvGg-g@mail.gmail.com> <CF335888.AE89D%ian.farrer@telekom.de> <CAFFjW4hv5WBiqyw9jM+ZoLMGR5k49pjKXG0epnhrsOGoBBKMYA@mail.gmail.com> <CAFFjW4gyvcBTBDjE8nzGbPz8BcHUasHizzzry0cRF+J2T82uSQ@mail.gmail.com> <CF3A3F56.3B435%yiu_lee@cable.comcast.com> <CAFFjW4j-R03WJdUe5Zb9Q2yuCMBtCOtO490NRjhaWMQ+d3a1xQ@mail.gmail.com> <CAFFjW4jLN0ieOmVx6-Wxfve2b0X=QHVK3vHbV7AWYGmFUeu_Ng@mail.gmail.com> <36155A81-243E-4BEA-9086-31DC802EB0D0@gmx.com> <CAFFjW4h=FuAf=g3EC7gf444Ne4TpePNJOmFLF2+_9bviiP5LTQ@mail.gmail.com> <5314B1CA.8030701@viagenie.ca>
In-Reply-To: <5314B1CA.8030701@viagenie.ca>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/GIYUmnchQ8J4ZVonIMwAzSur_wk
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 03 Mar 2014 16:58:08 -0000

Sounds like we are time warped back to the Taipeh and Paris IETF where we had this discussion in all levels of detail ? 
We (==operator) needed more flexibility than MAP could offer and were willing to accept the cost of managing some state... Woj did not want to hear it by then, and this seems to be a never-ending story... :-).

If a figure helps to document that, fine. Just avoid to get back to square 1.

Axel

-----Original Message-----
From: Softwires [mailto:softwires-bounces@ietf.org] On Behalf Of Simon Perreault
Sent: Monday, March 03, 2014 5:46 PM
To: softwires@ietf.org
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt

Le 2014-03-03 14:52, Wojciech Dec a écrit :
> Lightweight 4over6 provides a solution for a hub-and-spoke softwire 
> architecture only, where the AFTR maintains (softwire) state for each 
> subscriber. A means for optmizing the amount of such state using 
> IPv4-IPv6 address mapping rules, as well as the option of meshed IPv4 connectivity between subscribers, are features of the [I-D.ietf-softwire-map <http://tools.ietf.org/html/draft-ietf-softwire-lw4over6-07#ref-I-D.ietf-softwire-map>] solution.

Optimality is in the eye of the operator.

What MAP does is *minimize* the amount of state at the cost of flexibility. It may be more or less optimal depending on what you need.

Suggestion: create a two-axis ASCII graph labeled "state" and "flexibility". Put MAP, lw4o6, and heck even DS-Lite in it at the appropriate spots.

(This is not wordsmithing since I'm proposing a figure. It's
figure-smithing.)

Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

v2.23.0 | Report a Bug | By Email