IETF Logo Mail Archive

Re: [dhcwg] Fwd: I-D ACTION:draft-deng-dhc-service-identifiers-00.txt

Shane Kerr <Shane_Kerr@isc.org> Mon, 19 November 2007 10: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 1Iu3Sa-0002tu-D2; Mon, 19 Nov 2007 05:02:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu3SY-0002tC-ER for dhcwg@ietf.org; Mon, 19 Nov 2007 05:02:30 -0500
Received: from mx.isc.org ([2001:4f8:0:2::1c]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iu3SV-000752-Vo for dhcwg@ietf.org; Mon, 19 Nov 2007 05:02:30 -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 C4A1C11401E; Mon, 19 Nov 2007 10:02:26 +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 11908E6056; Mon, 19 Nov 2007 10:02:25 +0000 (UTC) (envelope-from shane@isc.org)
Message-ID: <47415F29.1080903@isc.org>
Date: Mon, 19 Nov 2007 11:02:17 +0100
From: Shane Kerr <Shane_Kerr@isc.org>
Organization: ISC
User-Agent: Thunderbird 2.0.0.9 (X11/20071116)
MIME-Version: 1.0
To: Hui Deng <denghui02@gmail.com>
Subject: Re: [dhcwg] Fwd: I-D ACTION:draft-deng-dhc-service-identifiers-00.txt
References: <E1IshMr-0004u3-PD@stiedprstage1.ietf.org> <1d38a3350711152313s49656e90yab73b1a21d21d396@mail.gmail.com> <473D5620.4090009@isc.org> <1d38a3350711161738m2e6f83b9q7c925feac9f21624@mail.gmail.com>
In-Reply-To: <1d38a3350711161738m2e6f83b9q7c925feac9f21624@mail.gmail.com>
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: 52e1467c2184c31006318542db5614d5
Cc: 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

Hui Deng wrote:
> Hi, Shane,
> 
> Thanks for your comments, reply as below,
> 
>> Interesting idea, but it's not clear to me what it means when a service is
>> advertised. For instance, if I advertise "ntp", does that mean that the local
>> network has a reachable NTP server, or that the network allows port 123 traffic
>> through it's firewall, or what?
> 
> I guess for some operator, they would like to say they allow such kind of
> port 123 traffic,  for others operator,
> this draft could be extended to show there is a reachable NTP server.

Clients need to be able to know exactly what the server means when it sends a
service identifier.

Also, if you are going to be sending lists of ports that are open, perhaps it
makes more sense to send those, instead of giving service names. Clients will
need to know how these ports are handled.

I think the draft needs more work before wider consideration.

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

iD8DBQFHQV8lMsfZxBO4kbQRAgWKAJ9Z3wUuaBQ11Hgv3fzHtAifZ6OyVQCeOrls
9ZylQ5krx74pyGgBO9TyKk0=
=v08B
-----END PGP SIGNATURE-----

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

v2.23.0 | Report a Bug | By Email