IETF Logo Mail Archive

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

"Lee, Yiu" <Yiu_Lee@Cable.Comcast.com> Mon, 03 March 2014 14:18 UTC

Return-Path: <yiu_lee@cable.comcast.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 99F911A0108 for <softwires@ietfa.amsl.com>; Mon, 3 Mar 2014 06:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.745
X-Spam-Level:
X-Spam-Status: No, score=-0.745 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 V7zXgtqlrsVY for <softwires@ietfa.amsl.com>; Mon, 3 Mar 2014 06:18:54 -0800 (PST)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1071A0198 for <softwires@ietf.org>; Mon, 3 Mar 2014 06:18:52 -0800 (PST)
Received: from ([24.40.56.121]) by pacdcavout01.cable.comcast.com with ESMTP id 97wm3m1.85131457; Mon, 03 Mar 2014 09:18:44 -0500
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.116]) by pacdcexhub04.cable.comcast.com ([fe80::1532:d330:f9a5:c8a1%18]) with mapi id 14.03.0158.001; Mon, 3 Mar 2014 09:18:44 -0500
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Wojciech Dec <wdec.ietf@gmail.com>, "ian.farrer@telekom.de" <ian.farrer@telekom.de>
Thread-Topic: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt
Thread-Index: AQHPNut7LPMj86F0sUC9ewHL9p7baQ==
Date: Mon, 03 Mar 2014 14:19:58 +0000
Message-ID: <CF3A3F56.3B435%yiu_lee@cable.comcast.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>
In-Reply-To: <CAFFjW4gyvcBTBDjE8nzGbPz8BcHUasHizzzry0cRF+J2T82uSQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [68.87.16.247]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3476701122_1356043"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/61yjer3nRyqXtzbxg5oQsDSI3Fo
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 14:18:56 -0000

Sorry for my ignorance. How MAP-E optimizes states In hub-and-spoke mode
compared to lw4o6? 

From:  Wojciech Dec <wdec.ietf@gmail.com>
Date:  Monday, March 3, 2014 at 1:47 PM
To:  "ian.farrer@telekom.de" <ian.farrer@telekom.de>
Cc:  Softwires-wg <softwires@ietf.org>
Subject:  Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt

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-sof
twire-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-sof
twire-map> ] solution.

Cheers,
Wojciech.

v2.23.0 | Report a Bug | By Email