Re: [shara] draft-thaler-port-restricted-ip-issues: Host Implementation Issues
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 01 March 2010 13:37 UTC
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: shara@core3.amsl.com
Delivered-To: shara@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAD6C28C462 for <shara@core3.amsl.com>; Mon, 1 Mar 2010 05:37:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level:
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u0vMLSDI9Ytj for <shara@core3.amsl.com>; Mon, 1 Mar 2010 05:37:48 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id F09D03A8B75 for <shara@ietf.org>; Mon, 1 Mar 2010 05:27:56 -0800 (PST)
Received: (qmail 19689 invoked from network); 1 Mar 2010 14:32:18 -0000
Received: from softbank219001188004.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.1.188.4) by necom830.hpcl.titech.ac.jp with SMTP; 1 Mar 2010 14:32:18 -0000
Message-ID: <4B8BC0C2.2090300@necom830.hpcl.titech.ac.jp>
Date: Mon, 01 Mar 2010 22:27:30 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: mohamed.boucadair@orange-ftgroup.com
References: <4233_1267439756_4B8B988C_4233_6698_1_94C682931C08B048B7A8645303FDC9F30EFAFF530F@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <4233_1267439756_4B8B988C_4233_6698_1_94C682931C08B048B7A8645303FDC9F30EFAFF530F@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: "shara@ietf.org" <shara@ietf.org>
Subject: Re: [shara] draft-thaler-port-restricted-ip-issues: Host Implementation Issues
X-BeenThere: shara@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Sharing of an IPv4 Address discussion list <shara.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shara>
List-Post: <mailto:shara@ietf.org>
List-Help: <mailto:shara-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2010 13:37:49 -0000
mohamed.boucadair@orange-ftgroup.com wrote: > In your draft, you wrote: "To actually apply a port restriction, host stack implementations > would need to change. It merely means PR-IP does require host stack changes. All of the PR-IP proposals do require host stack changes. So? Masataka Ohta
- [shara] draft-thaler-port-restricted-ip-issues: H… mohamed.boucadair
- Re: [shara] draft-thaler-port-restricted-ip-issue… Masataka Ohta
- Re: [shara] draft-thaler-port-restricted-ip-issue… pierre.levis
- Re: [shara] draft-thaler-port-restricted-ip-issue… Dave Thaler
- Re: [shara] draft-thaler-port-restricted-ip-issue… pierre.levis
- Re: [shara] draft-thaler-port-restricted-ip-issue… Masataka Ohta
- Re: [shara] draft-thaler-port-restricted-ip-issue… mohamed.boucadair
- Re: [shara] draft-thaler-port-restricted-ip-issue… Dave Thaler
- Re: [shara] draft-thaler-port-restricted-ip-issue… mohamed.boucadair