Re: [shara] port randomization (draft-ymbk-aplusp-03)

"Jan Zorz @ go6.si" <jan@go6.si> Mon, 16 March 2009 18:48 UTC

Return-Path: <jan@go6.si>
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 887DB28C133 for <shara@core3.amsl.com>; Mon, 16 Mar 2009 11:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level:
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.309, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 3h82Sosw5Zjb for <shara@core3.amsl.com>; Mon, 16 Mar 2009 11:48:11 -0700 (PDT)
Received: from ipv6.go6.si (go6.si [212.44.108.1]) by core3.amsl.com (Postfix) with ESMTP id 6B6C828C0E3 for <shara@ietf.org>; Mon, 16 Mar 2009 11:48:11 -0700 (PDT)
Received: from [IPv6:2001:470:9b8e::219:e3ff:fed4:9252] (unknown [IPv6:2001:470:9b8e:0:219:e3ff:fed4:9252]) (Authenticated sender: jan) by ipv6.go6.si (Postfix) with ESMTP id 1032046F1046; Mon, 16 Mar 2009 19:48:47 +0100 (CET)
Message-ID: <49BE9F0D.2080804@go6.si>
Date: Mon, 16 Mar 2009 19:48:45 +0100
From: "Jan Zorz @ go6.si" <jan@go6.si>
Organization: go6.si
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <022a01c9a2ab$fd5abf60$fd736b80@cisco.com><49B91C8B.5010906@go6.si><04a201c9a338$d5ce8f70$fd736b80@cisco.com> <49B9752B.8030407@go6.si> <051901c9a64a$0256bf40$fd55150a@cisco.com>
In-Reply-To: <051901c9a64a$0256bf40$fd55150a@cisco.com>
Content-Type: multipart/alternative; boundary="------------090802070907070305090704"
Cc: shara@ietf.org
Subject: Re: [shara] port randomization (draft-ymbk-aplusp-03)
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, 16 Mar 2009 18:48:12 -0000

Dan, hi.
>>
>> I'm also curious to hear some aproximation from any HW 
>> vendor, what does allocating "one port per request" means for 
>> PRR in larger scale.
>>     
>
> This is what today's NAPT devices do today, but without a separate
> protocol to request each port.
>   
I meant PRR on a big scale in ISP's access network.
> And, the CPE does not necessarily need to request each port; it
> could ask for ~5 or ~10 ports and then utilize them as it needs,
> and then get another batch of ~10 ports.  It comes down to
> the design decisions for the protocol between the CPE and the 
> PRR so that it is possible to utilize the entire 64K port 
> range.
>   
Yes, this is possible within described mechanism in A+P proposal, as 
minimum port range is not limited, so you can define 10 ports as a 
range, but preferably a range, that can be described with a bitmask.

Thank you, Jan Zorz