Re: [Softwires] WG Review: Recharter of Softwires (softwire)

"Jan Zorz @ go6.si" <jan@go6.si> Fri, 29 April 2011 14:28 UTC

Return-Path: <jan@go6.si>
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 97E3CE0773 for <softwires@ietfa.amsl.com>; Fri, 29 Apr 2011 07:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j0IctUxT9APv for <softwires@ietfa.amsl.com>; Fri, 29 Apr 2011 07:28:15 -0700 (PDT)
Received: from ipv6.go6.si (go6.si [212.44.108.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD40E0772 for <softwires@ietf.org>; Fri, 29 Apr 2011 07:28:15 -0700 (PDT)
Received: from jan-mac.local (unknown [IPv6:2001:470:d422:1:1293:e9ff:fe07:182c]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jan) by ipv6.go6.si (Postfix) with ESMTP id 7062C237800A for <softwires@ietf.org>; Fri, 29 Apr 2011 16:28:10 +0200 (CEST)
Message-ID: <4DBACC47.7090006@go6.si>
Date: Fri, 29 Apr 2011 16:33:43 +0200
From: "Jan Zorz @ go6.si" <jan@go6.si>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: softwires@ietf.org
References: <C9D5A4EF.6F00%yong@csnet1.cs.tsinghua.edu.cn> <0D0DE337-ACB9-49F1-B061-E5AD6C4B20B6@gmail.com>
In-Reply-To: <0D0DE337-ACB9-49F1-B061-E5AD6C4B20B6@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Softwires] WG Review: Recharter of Softwires (softwire)
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: Fri, 29 Apr 2011 14:28:15 -0000

On 4/25/11 11:14 AM, Satoru Matsushima wrote:
> I'm very confused to understand what DS-Lite is.
>
> On 2011/04/21, at 10:22, Yong Cui wrote:
>
>> Change "DS-Lite with no NAT or NAT on the B4 element" to "No NAT on AFTR"
>
> However, "draft-ietf-softwire-dual-stack-lite-07" clearly express AFTR is carrier grade NAT44,
> and B4(CPE) should not operate a NAT function. So my question is what does the DS-Lite function deployment model include.
> Current DS-Lite definition does not accept any extension for "DS-Lite with no NAT or NAT on the B4 element" to "No NAT on AFTR".
> I think that to do this as a charter item, we need definition change of DS-Lite, or use another terminology instead of DS-Lite.

"DS-Lite with no NAT or NAT on the B4 element" or "No NAT on AFTR" are 
fancy new names for A+P.

A+P was defined in DS-Lite as possible way of doing it some versions ago 
but disappeared through the time.

No idea why, but anyway. Basically DS-Lite and A+P are similar 
mechanisms with NAT at different places. See ymbk-aplusp draft, section 
"Overall architecture".

Cheers, Jan Zorz