Re: [Softwires] Fw: New Version Notification fordraft-cui-softwire-b4-translated-ds-lite-04.txt

Reinaldo Penno <rpenno@juniper.net> Thu, 03 November 2011 20:49 UTC

Return-Path: <rpenno@juniper.net>
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 1C8CB21F9AA7 for <softwires@ietfa.amsl.com>; Thu, 3 Nov 2011 13:49:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.279
X-Spam-Level:
X-Spam-Status: No, score=-6.279 tagged_above=-999 required=5 tests=[AWL=-0.280, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_MED=-4]
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 s3b46t+yk0hi for <softwires@ietfa.amsl.com>; Thu, 3 Nov 2011 13:49:19 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id C88B921F9163 for <softwires@ietf.org>; Thu, 3 Nov 2011 13:49:14 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP; Thu, 03 Nov 2011 13:49:19 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 3 Nov 2011 13:48:22 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 3 Nov 2011 16:48:21 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: peng-wu <peng-wu@foxmail.com>, Olivier Vautrin <ovautrin@juniper.net>, softwires <softwires@ietf.org>
Date: Thu, 03 Nov 2011 16:48:21 -0400
Thread-Topic: [Softwires] Fw: New Version Notification fordraft-cui-softwire-b4-translated-ds-lite-04.txt
Thread-Index: AcyaIewtVkD/7/VSQQKWwnj987R2kQAR//rZ
Message-ID: <CAD84C25.575C7%rpenno@juniper.net>
In-Reply-To: <2011110320123984925532@foxmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Softwires] Fw: New Version Notification fordraft-cui-softwire-b4-translated-ds-lite-04.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: Thu, 03 Nov 2011 20:49:20 -0000

Hello Peng,

Some comments inline...


On 11/3/11 5:12 AM, "Peng Wu" <peng-wu@foxmail.com> wrote:

> Hi Olivier,
> 
> see inlines :)
> --------------
> Peng Wu
>> Hello, thanks for this interesting draft.
>> 
>> In your use case, could you explain if every CPE/Host need to reach
>> Internet? That would be the case in a typical Broadband deployment but
>> perhaps not in your deployment scenario.
> Could be every CPE/Host.
>> 
>> If all CPE needs Internet access, all of them with an IP@ need a dedicated
>> "bucket of ports" installed in the Concentrator. Which means that we could
>> just have a static allocation of ports in the Concentrator instead of
>> DHCP/PCP mechanism as described in your draft.
> Well, we've thought of this.
> There're two differences here.
> 
> The first and the major one is that, if we just take ds-lite and have static
> port set allocation in the concentrator, the concentrator still has to keep
> the per-session NAT table and perform the translation, while in lightweight
> 4over6, NAT happens on CPE and the concentrator just perform
> encapsulation/decapsulation, with a per-subscriber mapping table.

Per-session NAT is not needed if:

- the B4 performs NAT or
- Each host has a unique IP and a known port space.

Our implementation performs NAT without any per session state.

> 
> The second one is that in lightweight 4over6, with one-time DHCP/PCP,
> the subscriber learns its public IPv4 address. This brings convenience and
> eases the ALG problem to a certain extent.

I think ALG is an application issue and can only be fully solved when all
applications make use of PCP.

> In ds-lite with static concentrator
> port allocation, the subscriber still doesn't know its public IPv4
> address/port 
> without per-session PCP process.

Yes, that is a good point. We devised an extension to PCP to return the
public IP and port range. Therefore a single message would be needed.

>> 
>> My point is we could have a Stateless mechanism in the Concentrator as
>> described in SD-NAT (draft-penno-softwire-sdnat-01) and just use regular
>> DHCP/Radius on the CPE to get a dynamic address allocation with the same
>> result.
>> 
>> What do you think?
>> 
>> Cheers,
>> Olivier
>> 
>> 
>> On 11/2/11 8:06 AM, "peng-wu@foxmail" <peng-wu@foxmail.com> wrote:
>> 
>>> Hi all,
>>> 
>>> We've submitted a -04 version of the b4-translated-ds-lite draft.
>>> It describes the per-user-state IPv4-over-IPv6 mechanism with port set
>>> support, which can be achieved through some extensions to ds-lite.
>>> There are discussions going on upon this topic during and after the
>>> Interim meeting.
>>> We've received quite a lot offline comments/suggestions, and made
>>> progresses accordingly.
>>> 
>>> The draft is available on
>>> http://tools.ietf.org/html/draft-cui-softwire-b4-translated-ds-lite-04
>>> Please provide your valuable comments. And hopefully we'll present it in
>>> Taipei.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> u---
>>> A new version of I-D, draft-cui-softwire-b4-translated-ds-lite-04.txt has
>>> been successfully submitted by Qiong Sun and posted to the IETF
>>> repository.
>>> 
>>> Filename:  draft-cui-softwire-b4-translated-ds-lite
>>> Revision:  04
>>> Title:   Lightweight 4over6 in access network
>>> Creation date:  2011-10-30
>>> WG ID:   Individual Submission
>>> Number of pages: 24
>>> 
>>> Abstract:
>>>   The dual-stack lite mechanism provide an IPv4 access method over IPv6
>>>   ISP network for end users.  Dual-Stack Lite enables an IPv6 provider
>>>   to share IPv4 addresses among customers by combining IPv4-in-IPv6
>>>   tunnel and Carrier Grade NAT.  However, in dual-stack lite, CGN has
>>>   to maintain active NAT sessions, which could become the performance
>>>   bottom-neck due to high dynamics of NAT entries, memory cost and log
>>>   issue.  This document propose the lightweight 4over6 mechanism which
>>>   moves the translation function from tunnel concentrator (AFTR) to
>>>   initiators (B4s), and hence reduces the mapping scale on the
>>>   concentrator to per-customer level.  For NAT44 translation usage, the
>>>   mechanism allocates port restricted IPv4 addresses to initiators in a
>>>   flexible way independent of IPv6 network in the middle.
>>> 
>>>                
>>>        
>>> 
>>> 
>>> The IETF Secretariat
>>> 
>>> _______________________________________________
>>> 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