Re: [Softwires] sharing restricted addresses by hosts in 4rd (draft-despres-intarea-4rd-01)

Mark Townsley <mark@townsley.net> Tue, 12 April 2011 20:04 UTC

Return-Path: <mark@townsley.net>
X-Original-To: softwires@ietfc.amsl.com
Delivered-To: softwires@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 85DCBE08F5 for <softwires@ietfc.amsl.com>; Tue, 12 Apr 2011 13:04:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bBSiCgUNtp9S for <softwires@ietfc.amsl.com>; Tue, 12 Apr 2011 13:04:03 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfc.amsl.com (Postfix) with ESMTP id 9FD7AE0870 for <softwires@ietf.org>; Tue, 12 Apr 2011 13:04:03 -0700 (PDT)
Received: by wyb29 with SMTP id 29so6641551wyb.31 for <softwires@ietf.org>; Tue, 12 Apr 2011 13:04:03 -0700 (PDT)
Received: by 10.227.139.164 with SMTP id e36mr1851693wbu.94.1302638642874; Tue, 12 Apr 2011 13:04:02 -0700 (PDT)
Received: from ams-townsley-8712.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id y12sm4246696wby.59.2011.04.12.13.04.01 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2011 13:04:02 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <DD1A73D9E9C89144A927C5080F70285A015E3F1E01DE@NA-EXMSG-S702.segroup.winse.corp.microsoft.com>
Date: Tue, 12 Apr 2011 22:03:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C4F8A4C-A7AE-4E6E-960B-650DED19982F@townsley.net>
References: <DD1A73D9E9C89144A927C5080F70285A015E3F1E01DE@NA-EXMSG-S702.segroup.winse.corp.microsoft.com>
To: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
X-Mailer: Apple Mail (2.1084)
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] sharing restricted addresses by hosts in 4rd (draft-despres-intarea-4rd-01)
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: Tue, 12 Apr 2011 20:04:04 -0000

Hello Dmitry,

My view is that 4rd is most easily understood if and only if it connects to a CE function that is performing NAPT. The CE function may be in what is traditionally considered a host, or in what is clearly a router.

More specifically, a device that is forwarding packets from one interface (virtual or otherwise) to another through a NAPT that has one interface with IPv6 configured (via DHCPv6 or otherwise) as performing 4rd (which enables dual-stack via a port-restricted IPv4 address for the NAPT using IPv6 as the transport) then you a have a 4rd CE. That could be a "host" in that it is a Windows PC with internet connection sharing for IPv4 turned on and hence forwards packets between interfaces with a NAPT due to the IPv4-enabled interface created when 4rd is configured. 

I would avoid anything that requires the host forwarding table to be altered to accommodate 4rd. Instead, the NAPT function that is already present in a small router or host configured to look like a router is modified to use a set of ports that it is allowed to use when 4rd is enabled. 

- Mark

On Apr 12, 2011, at 2:11 AM, Dmitry Anipko wrote:

> Hi,
> 
> Since re-chartering to include 4rd has not been approved yet (as far as I know), I'm not sure if softwires is the right forum for this question, please let me know if intarea is a better one for the time being.
> 
> Draft-despres-intarea-4rd-01 allows for configuration of end hosts (since it defines CE as "a host, a router or both") with shared addresses with restricted port sets. My understanding is that usage by applications of such addresses, assigned to interfaces, may have issues - for example, those are discussed in http://tools.ietf.org/html/draft-dec-stateless-4v6-00 . 
> 
> Should the draft include a recommendation to either avoid assigning such addresses to interfaces, and use it only in the NAT function, even when CE is a host, or, as draft-dec-stateless-4v6-00 suggests in section 3.1.2, modify the 4rd DHCP option to provide for CE ability to specify whether it is capable to function with a shared address? (since 4rd can also distribute not shared addresses / address ranges)
> 
> Thank you,
> Dmitry
> 
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires