Re: [dhcwg] What sorts of services does DHCP configure?

"Reinaldo Penno (repenno)" <repenno@cisco.com> Tue, 15 October 2013 14:45 UTC

Return-Path: <repenno@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5B4721E80BB for <dhcwg@ietfa.amsl.com>; Tue, 15 Oct 2013 07:45:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lhT1NT274OIT for <dhcwg@ietfa.amsl.com>; Tue, 15 Oct 2013 07:45:05 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0094F21F9D0E for <dhcwg@ietf.org>; Tue, 15 Oct 2013 07:44:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2053; q=dns/txt; s=iport; t=1381848300; x=1383057900; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=9WLHFtnG2MDHRxLGaWxaSZgiIRxn9aJ0ckbLej5XfUA=; b=a93dKTMcjYzUB1FxQ8WhbZ1N+iSEx3bNU+bHtPIeuYS9bvzlHOkqJLpq MeWV7/i9i5qnP7eWoWPNpbBO8su0umGbXNF+YNV9a+humTWGOEEE8aJaD 9f4XhHz1FZ/WXzvxXwRNKYZ3veBIN6Gz6RxpajCvWj+LIzHxdoKhBTgiO Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFANRTXVKtJXG+/2dsb2JhbABagwc4UsFaS4EgFnSCJQEBAQMBGGESAQgOFFYlAgQOBQiHeAYMvSqPFwIxB4MfgQYDmTOQU4MkgWkkHA
X-IronPort-AV: E=Sophos;i="4.93,499,1378857600"; d="scan'208";a="272324481"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 15 Oct 2013 14:44:59 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9FEixVf012719 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 15 Oct 2013 14:44:59 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.27]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Tue, 15 Oct 2013 09:44:59 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Ted Lemon <mellon@fugue.com>
Thread-Topic: [dhcwg] What sorts of services does DHCP configure?
Thread-Index: AQHOyQrfiAXKk6KM3ESJzga2BnKmuZn1VvoAgAABtoCAAAbSAIAAs2QA//+R8YCAAH6KgP//kz6A
Date: Tue, 15 Oct 2013 14:44:58 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040B7337D7@xmb-rcd-x04.cisco.com>
In-Reply-To: <468A1C46-7425-4499-BBF2-50EED2DBD248@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.69.5]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <56BC7D284D774D4FBCB5C148B9B7A1AC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] What sorts of services does DHCP configure?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2013 14:45:12 -0000

On 10/15/13 7:14 AM, "Ted Lemon" <mellon@fugue.com> wrote:

>On Oct 15, 2013, at 9:41 AM, Reinaldo Penno (repenno) <repenno@cisco.com>
>wrote:
>> Would it make sense to determine which DHCP options are used today in
>>wild
>> and reasoning behind them?
>> 
>> I have done a few captures before and noticed that DHCP options vary
>> between home, Hotel, Hotspot, Airport, etc.
>
>It can't hurt to ask this question, but I'm not convinced that it's
>necessary.   DHCP clients don't use options they don't request, so it
>doesn't matter if the server sends them.   So it's probably not necessary
>to survey DHCP servers‹just survey DHCP clients and see what options they
>request.

Right, DHCP clients.

certain OSs allows applications to ask for certain DHCP options.

http://msdn.microsoft.com/en-us/library/windows/desktop/aa363298%28v=vs.85%
29.aspx

>
>> As far as your SIP example below, I see SIP server through DHCP just as
>>a
>> discovery step. Your SIP client should apply whatever security policies
>>to
>> accept or not that SIP Server.
>
>Right, but going a little farther into your example, this only works for
>clients that 


"Clients" here can be an application as above, not necessarily a DHCP
client that triggers everything.

>(a) request the SIP option and (b) have some way of validating the
>response they get back.   So we can have a very clear discussion about
>this security model, and also possibly ask whether existing clients
>actually do this, and whether this is a good idea, or just the best we
>could do with what services are available.
>
>And then this question can be asked about lots of other services as well.
> E.g., does it make sense to configure NTP this way, given that NTP
>provides replay protection for security protocols (that's a complicated
>question)?   Does it make sense to configure SMTP this way, given that
>SMTP servers are no longer really interchangeable as they were in the
>early days of the Internet?   POP?   IMAP?   Etc.
>