Re: [Softwires] draft-murakami-softwire-4v6-translation

Nejc Škoberne <nejc@skoberne.net> Fri, 19 August 2011 23:40 UTC

Return-Path: <nejc@skoberne.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 B4F6211E80A2 for <softwires@ietfa.amsl.com>; Fri, 19 Aug 2011 16:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.211
X-Spam-Level:
X-Spam-Status: No, score=-2.211 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 qkaLG2YbU7Kq for <softwires@ietfa.amsl.com>; Fri, 19 Aug 2011 16:40:06 -0700 (PDT)
Received: from mail.tnode.com (common.tnode.com [91.185.203.243]) by ietfa.amsl.com (Postfix) with ESMTP id 3478D11E8083 for <softwires@ietf.org>; Fri, 19 Aug 2011 16:40:06 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.tnode.com (Postfix) with ESMTP id A9D05227876A; Sat, 20 Aug 2011 01:41:03 +0200 (CEST)
Received: from mail.tnode.com ([127.0.0.1]) by localhost (mail.tnode.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BeZrQ8zCCQV6; Sat, 20 Aug 2011 01:41:03 +0200 (CEST)
Received: from [192.168.15.112] (eduroam-staff-227-202.lut.ac.uk [158.125.227.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: nejc@skoberne.net) by mail.tnode.com (Postfix) with ESMTPSA id 651132278769; Sat, 20 Aug 2011 01:41:02 +0200 (CEST)
Message-ID: <4E4EF48D.6020500@skoberne.net>
Date: Sat, 20 Aug 2011 00:41:01 +0100
From: Nejc Škoberne <nejc@skoberne.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4E4B96CB.2020004@skoberne.net> <CAFFjW4hw5_7STGB5VoxLJdAgiwLqjUU-SFrkjJs48iNxkpH2pw@mail.gmail.com> <4E4D9D97.1030500@skoberne.net> <4E4DA1C2.40307@gmail.com> <4E4ED337.3070100@skoberne.net> <4E4EEDF0.5090400@gmail.com>
In-Reply-To: <4E4EEDF0.5090400@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "softwires@ietf.org" <softwires@ietf.org>, draft-murakami-softwire-4v6-translation@tools.ietf.org
Subject: Re: [Softwires] draft-murakami-softwire-4v6-translation
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, 19 Aug 2011 23:40:06 -0000

>> It will not, because I don't have a legacy SOHO LAN. If I have legacy
>> SOHO LAN, I can use (optional) NAT44.
> 
> Exactly, resulting in NAT444 . But if I'm forced to use NAT444
> via a 4 in 6 tunnel anyway, A+P is pointless.

I don't think you understood what I was saying. There is no need for NAT444. 

Let me explain again. The provider has an A+P solution in place. They will,
by default, provide me with their CPE, which supports A+P and also does
NAPT44 for my legacy SOHO LAN. In this case, I just plug my computers and
everything will work like today, just with not-so-many ports.

However, there are at least two more possible scenarios I can imagine:

1.) I don't want the provider's CPE since I have my home gateway-server, 
which supports A+P and is connected directly to the ISP. This server will 
have a public IPv4 address configured and if I need, it /can/ then do 
NAPT44 (instead of the CPE) for the rest of my legacy LAN.

2.) I don't want the provider's CPE since my computers actually support
A+P mechanism of the provider. I have IPv6-only network in my LAN and
IPv4 addressing is brought directly to hosts via A+P mechanism. So it
is like "extending" the access network to my home. This scenario is also
shown on page 16, Figure 6 in draft-ymbk-aplusp-10.

Nejc