Re: [shara] [BEHAVE] TR: I-DAction:draft-boucadair-pppext-portrang e-option-00.txt
<teemu.savolainen@nokia.com> Fri, 06 February 2009 06:21 UTC
Return-Path: <teemu.savolainen@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 ADEBF3A6B3D; Thu, 5 Feb 2009 22:21:14 -0800 (PST)
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 aYu+i1vazT8R;
Thu, 5 Feb 2009 22:21:13 -0800 (PST)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by
core3.amsl.com (Postfix) with ESMTP id 664233A6827;
Thu, 5 Feb 2009 22:21:13 -0800 (PST)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com
[172.21.138.213]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with
ESMTP id n166Kto9005769; Fri, 6 Feb 2009 08:21:09 +0200
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by
esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);
Fri, 6 Feb 2009 08:20:53 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh104.NOE.Nokia.com
over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);
Fri, 6 Feb 2009 08:20:49 +0200
Received: from nok-am1mhub-07.mgdnok.nokia.com (65.54.30.14) by
NOK-am1MHUB-02.mgdnok.nokia.com (65.54.30.6) with Microsoft SMTP Server (TLS)
id 8.1.291.1; Fri, 6 Feb 2009 07:20:48 +0100
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.106]) by
nok-am1mhub-07.mgdnok.nokia.com ([65.54.30.14]) with mapi;
Fri, 6 Feb 2009 07:20:48 +0100
From: <teemu.savolainen@nokia.com>
To: <dwing@cisco.com>, <mohamed.boucadair@orange-ftgroup.com>, <shara@ietf.org>
Date: Fri, 6 Feb 2009 07:20:47 +0100
Thread-Topic: [shara] [BEHAVE] TR: I-DAction:draft-boucadair-pppext-portrang
e-option-00.txt
Thread-Index: AQHJiCMNTzrmZ0dtOk+kwKu3E6/2ng==
Message-ID: <NMzqHmMvlmGW@w4L1DxlL>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 06 Feb 2009 06:20:49.0454 (UTC)
FILETIME=[0DDC3CE0:01C98823]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [shara] [BEHAVE] TR: I-DAction:draft-boucadair-pppext-portrang
e-option-00.txt
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: Fri, 06 Feb 2009 06:21:14 -0000
Hi, Continuous, especially if small, port ranges make it difficult for a host to pick good random source ports. We have I-D related to this on the way. Best regards, Teemu --- original message --- From: "ext Dan Wing" <dwing@cisco.com> Subject: Re: [shara] [BEHAVE] TR: I-DAction:draft-boucadair-pppext-portrange-option-00.txt Date: 6th February 2009 Time: 1:29:27 am I like this draft overall, but I would restrict this so that only contiguous port ranges are permitted. Non-contiguous subnet masks are difficult for many people to understand (even today) and I expect there would be similar confusion with non-contiguous port ranges. -d > -----Original Message----- > From: behave-bounces@ietf.org > [mailto:behave-bounces@ietf.org] On Behalf Of > mohamed.boucadair@orange-ftgroup.com > Sent: Thursday, February 05, 2009 6:09 AM > To: behave@ietf.org; shara@ietf.org > Subject: [BEHAVE] TR: > I-DAction:draft-boucadair-pppext-portrange-option-00.txt > > > > FYI. A new ID has been submitted to IETF. This draft > specifies new PPP IPCP options to be used in the context of > Port Range solutions. > > Comments are more than welcome. > > Cheers, > Med > > > > > -----Message d'origine----- > De : i-d-announce-bounces@ietf.org > [mailto:i-d-announce-bounces@ietf.org] De la part de > Internet-Drafts@ietf.org > Envoyé : jeudi 5 février 2009 15:00 > À : i-d-announce@ietf.org > Objet : I-D Action:draft-boucadair-pppext-portrange-option-00.txt > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > > Title : Port Range Configuration Options for PPP IPCP > Author(s) : M. Boucadair, et al. > Filename : draft-boucadair-pppext-portrange-option-00.txt > Pages : 13 > Date : 2009-02-05 > > This memo defines two IPCP (IP Configuration Protocol, > [RFC1332]) Options to be used in the context of Port Range > solutions. IPCP is the configuration protocol used when PPP > (Point-to-Point Protocol, > [RFC1548]) is deployed. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-boucadair-pppext-por > trange-option-00.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail > reader implementation to automatically retrieve the ASCII > version of the Internet-Draft. > _______________________________________________ shara mailing list shara@ietf.org https://www.ietf.org/mailman/listinfo/shara
- Re: [shara] [BEHAVE] TR: I-DAction:draft-boucadai… teemu.savolainen