Re: [shara] dynamic allocation of port ranges in draft-bajko-v6ops-port-restricted-ipaddr-assign
<Gabor.Bajko@nokia.com> Tue, 17 March 2009 01:04 UTC
Return-Path: <Gabor.Bajko@nokia.com>
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 42F133A67F7 for <shara@core3.amsl.com>;
Mon, 16 Mar 2009 18:04:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,
BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 QGpZkoz8IE2e for
<shara@core3.amsl.com>; Mon, 16 Mar 2009 18:04:27 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by
core3.amsl.com (Postfix) with ESMTP id 4F0603A63EC for <shara@ietf.org>;
Mon, 16 Mar 2009 18:04:27 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com
[172.21.138.211]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with
ESMTP id n2H14vS8031103; Mon, 16 Mar 2009 20:05:07 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 17 Mar 2009 03:05:03 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by esebh102.NOE.Nokia.com
over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 17 Mar 2009 03:05:03 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by
nok-am1mhub-02.mgdnok.nokia.com ([65.54.30.6]) with mapi;
Tue, 17 Mar 2009 02:05:03 +0100
From: <Gabor.Bajko@nokia.com>
To: <dwing@cisco.com>, <shara@ietf.org>
Date: Tue, 17 Mar 2009 02:05:06 +0100
Thread-Topic: [shara] dynamic allocation of port ranges in
draft-bajko-v6ops-port-restricted-ipaddr-assign
Thread-Index: Acmiqys4doeQlz8/TqSaYAuofSBJEwD8La3g
Message-ID: <A99B171D26E1564B92D36826128CD66127EE106A91@NOK-EUMSG-01.mgdnok.nokia.com>
References: <022601c9a2ab$2b6f46b0$fd736b80@cisco.com>
In-Reply-To: <022601c9a2ab$2b6f46b0$fd736b80@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Mar 2009 01:05:03.0670 (UTC)
FILETIME=[67674560:01C9A69C]
X-Nokia-AV: Clean
Subject: Re: [shara] dynamic allocation of port ranges
in draft-bajko-v6ops-port-restricted-ipaddr-assign
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: Tue, 17 Mar 2009 01:04:28 -0000
>I interpret the highlighted phrase to mean the PRR provides a range of >ports on a *different* IP address. Is that the intent? The intention was to say that the server may allocate an additional set of ports, which may belong to the same or different IP address. >Is that the intent? I had expected >that sentence in the I-D to conclude with "... offer the client >additional ports on the same IP address as previously allocated." Yes, that would simplify considerably both the client and server operation. I can add a clarification that the server should allocate additional ports belonging to the same IP address (if possible). - gabor >-----Original Message----- >From: shara-bounces@ietf.org [mailto:shara-bounces@ietf.org] On Behalf Of >ext Dan Wing >Sent: Wednesday, March 11, 2009 5:41 PM >To: shara@ietf.org >Subject: [shara] dynamic allocation of port ranges in draft-bajko-v6ops- >port-restricted-ipaddr-assign > >I was pleased to see the new "Dynamic allocation of port ranges" section >in >draft-ymbk-aplusp-03. While digging into the details a bit, I saw in >Section 4.2 of draft-bajko-v6ops-port-restricted-ipaddr-assign-02: > > When the server detects that a client with a specific hardware > address, having already been allocated with a port restricted IP > address, sent another DHCPDISCOVER, it MAY, based on local policy, > offer the client with additional port restricted IP address. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >I interpret the highlighted phrase to mean the PRR provides a range of >ports on a *different* IP address. Is that the intent? I had expected >that sentence in the I-D to conclude with "... offer the client >additional ports on the same IP address as previously allocated." > >-d > >_______________________________________________ >shara mailing list >shara@ietf.org >https://www.ietf.org/mailman/listinfo/shara