IETF Logo Mail Archive

Re: [dhcwg] Client Port Option?

Shane Kerr <Shane_Kerr@isc.org> Tue, 13 November 2007 12:02 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IruTU-0000vc-1E; Tue, 13 Nov 2007 07:02:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IruTR-0000ur-2j for dhcwg@ietf.org; Tue, 13 Nov 2007 07:02:33 -0500
Received: from mx.isc.org ([2001:4f8:0:2::1c]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IruTP-00077Z-PB for dhcwg@ietf.org; Tue, 13 Nov 2007 07:02:33 -0500
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.isc.org (Postfix) with ESMTP id B88ED11401F for <dhcwg@ietf.org>; Tue, 13 Nov 2007 12:02:30 +0000 (UTC) (envelope-from Shane_Kerr@isc.org)
Received: from [199.6.1.234] (unknown [199.6.1.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by farside.isc.org (Postfix) with ESMTP id 4A47EE6065; Tue, 13 Nov 2007 12:02:30 +0000 (UTC) (envelope-from shane@isc.org)
Message-ID: <47399253.60408@isc.org>
Date: Tue, 13 Nov 2007 13:02:27 +0100
From: Shane Kerr <Shane_Kerr@isc.org>
Organization: ISC
User-Agent: Thunderbird 2.0.0.6 (X11/20070806)
MIME-Version: 1.0
To: shane_kerr@isc.org
Subject: Re: [dhcwg] Client Port Option?
References: <473991A0.2060009@isc.org>
In-Reply-To: <473991A0.2060009@isc.org>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: DHCP discussion list <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: shane_kerr@isc.org
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Shane Kerr wrote:
> I think it might be useful for DHCP clients to use a different port, other than
> 68/546.

Hm... I just realized that I didn't explain the actual proposal. :(

The idea is that if clients did want to use a different port, they would include
an option with the port number when the sent a packet.

I know some DHCP servers would drop the queries, and there are firewalling
issues, but these can be addressed in the long term.

- --
Shane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHOZJSMsfZxBO4kbQRAvOiAKDivc0O8YqF6nX4FZyCJN2yQJzSKgCgtyLm
8kDQjNqwYnQk26RGrA6Nv1o=
=auim
-----END PGP SIGNATURE-----

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email