IETF Logo Mail Archive

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

Wojciech Dec <wdec.ietf@gmail.com> Mon, 03 March 2014 13:48 UTC

Return-Path: <wdec.ietf@gmail.com>
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 ACB011A0184 for <softwires@ietfa.amsl.com>; Mon, 3 Mar 2014 05:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 mUQSegFEJmW8 for <softwires@ietfa.amsl.com>; Mon, 3 Mar 2014 05:47:58 -0800 (PST)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 2D84E1A0187 for <softwires@ietf.org>; Mon, 3 Mar 2014 05:47:58 -0800 (PST)
Received: by mail-pd0-f173.google.com with SMTP id z10so3725679pdj.18 for <softwires@ietf.org>; Mon, 03 Mar 2014 05:47:55 -0800 (PST)
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=JuWZf2I42N9pECGgrBHy+QaE3CiIg9m5liZJlITIWSM=; b=BDFHQyMOHZ3Wn519R1vZCDpJzvfGRBtRrMPme4my8hcnKKRM6dPgcCQ8j+xByjx2O4 JaxFSRGljIZsh4SMlqvc0yFITiL0FjJX6JoulozYrHQhxYYjqaTi143V+e1qRZ4LkYTP YjzTvueBn0xLQzHzJ+pRgbp6jXcO+l+hmKaBHCB/vGtXib7Puv2N8jn6n9xfEra7FnZt 8F7l+8it4CCf+SvNi90IBYLBFMnWQsx3dZy8N3DgUSXsRaVUr9/QsybCWUZs7RE7UOfJ EEPxFeJOAYUyIM547GwTb4uCfz2lr/SrhpzmQP7YtO85fIeB0EBsDzDMKkVvuC4/mRix WPDA==
MIME-Version: 1.0
X-Received: by 10.66.144.200 with SMTP id so8mr19973191pab.15.1393854475308; Mon, 03 Mar 2014 05:47:55 -0800 (PST)
Received: by 10.70.1.70 with HTTP; Mon, 3 Mar 2014 05:47:55 -0800 (PST)
In-Reply-To: <CAFFjW4hv5WBiqyw9jM+ZoLMGR5k49pjKXG0epnhrsOGoBBKMYA@mail.gmail.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>
Date: Mon, 03 Mar 2014 14:47:55 +0100
Message-ID: <CAFFjW4gyvcBTBDjE8nzGbPz8BcHUasHizzzry0cRF+J2T82uSQ@mail.gmail.com>
From: Wojciech Dec <wdec.ietf@gmail.com>
To: "ian.farrer@telekom.de" <ian.farrer@telekom.de>
Content-Type: multipart/alternative; boundary="047d7b6d9284de948004f3b408c9"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/gLbI8lu_YAJ2IFwm0on1DokxzQQ
Cc: Softwires-wg <softwires@ietf.org>
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 13:48:00 -0000

Hi Ian,

following up with some proposed text re relation to MAP


> On 26 February 2014 10:31, <ian.farrer@telekom.de> wrote:
>
>> Hi Woj,
>>
>> I've been out of the office for a couple of days, so sorry for the be
>> late reply.
>>
>> Please see inline.
>>
>> Cheers,
>> Ian
>>
>> From: Wojciech Dec <wdec.ietf@gmail.com>
>> Date: Wednesday, 19 February 2014 09:34
>> To: Ian Farrer <ianfarrer@gmx.com>
>> Cc: Softwires-wg <softwires@ietf.org>
>> Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt
>>
>> Hi Ian,
>>
>> Just to be clear: I'm ok with lw46 defining a specific functional mode as
>> I believe it does in this draft, also leaving "as-is" the DHCP part of it
>> (i.e. it's a capability that can be signalled using the lw46 container,
>> etc).
>>
>> [ian] It would help if you could propose text for what you would like to
>> see. The inline discussion has become quite protracted.
>>
>
> I'll follow up on that...
>
>
>>
>>
Here I'm pointing out that IPinIP dataplane + ICMP wise there should be no
difference between lw46 and MAP-E, and in effect a single BR or lw46 AFTR
implementation can be made of these.

Current text in Section 1 reads:

Lightweight 4over6 provides a solution for a hub-and-spoke softwire
   architecture only.  It does not offer direct, meshed IPv4
   connectivity between subscribers without packets traversing the AFTR.
   If this type of meshed interconnectivity is required,
   [I-D.ietf-softwire-map
<http://tools.ietf.org/html/draft-ietf-softwire-lw4over6-07#ref-I-D.ietf-softwire-map>]
provides a suitable solution.


Propose changing the above to:

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, 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.

Cheers,

Wojciech.

v2.23.0 | Report a Bug | By Email