IETF Logo Mail Archive

Re: [dhcwg] DHCPv6 APIs for applications

"Bernie Volz (volz)" <volz@cisco.com> Thu, 16 October 2014 18:33 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B49371A6FE8 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 11:33:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NC71YaXZ2tgg for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 11:33:30 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 645271A011E for <dhcwg@ietf.org>; Thu, 16 Oct 2014 11:33:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1281; q=dns/txt; s=iport; t=1413484410; x=1414694010; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=a0aUmFT5J/GqLmlyQwTEWpRJjh26UJgeEZvqDMbSX6A=; b=Js6tn1kdjjpnddJ1m/PwHDLOafgOcuGxtDf0vPyX5YQUuRWByKV5QBdX fKDpp88nvl/anYV6e955GYD/V3IqB6iYYmuN9XkjqcMBqSg3ZdVgGmDHA YLZHHVdyAsQH4ZO2JlN6tgKELphvxXvOixLA0e8OvKWBbS/35YF2CyZad Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAPMOQFStJV2T/2dsb2JhbABbgw5TXMwihndUAoEYFgF9hAIBAQEEOksEAgEIEQQBAQEKFAkHMhQJCAIEARIIiDYNyxUBAQEBAQEBAQEBAQEBAQEBAQEBARiQHDgGgyeBHgWFFYxqhEaIfpQwg3dsAYFHgQIBAQE
X-IronPort-AV: E=Sophos;i="5.04,733,1406592000"; d="scan'208";a="360772438"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-9.cisco.com with ESMTP; 16 Oct 2014 18:33:29 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s9GIXTph030554 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Oct 2014 18:33:29 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.78]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Thu, 16 Oct 2014 13:33:29 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHCPv6 APIs for applications
Thread-Index: AQHP6W+u4wpxJvcEy0W8Xyt1F0dl1w==
Date: Thu, 16 Oct 2014 18:33:29 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6D1A47@xmb-rcd-x04.cisco.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com> <16238.1413479677@sandelman.ca>
In-Reply-To: <16238.1413479677@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/SEcniRfCY3hiB0T67dHWLDKFdio
Subject: Re: [dhcwg] DHCPv6 APIs for applications
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 16 Oct 2014 18:33:31 -0000

Here's a link to Microsoft's - http://msdn.microsoft.com/en-us/library/windows/desktop/aa363351(v=vs.85).aspx.

If you know of others, perhaps worth providing those links.

Perhaps someone has interest in working to define such an API.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Michael Richardson
Sent: Thursday, October 16, 2014 1:15 PM
To: dhcwg
Subject: [dhcwg] DHCPv6 APIs for applications


Bernie Volz (volz) <volz@cisco.com> wrote:
    > I would guess that most clients trigger it when the refresh time
    > (OPTION_INFORMATION_REFRESH_TIME option) expires or when some
    > application request some data that hasn't been obtained (if the OS has
    > this capability)?

I think that maybe DHC WG should consider if having such an API defined would be important now... I think that applications *should* be given such an API would use it more.

I imagine that there are OS (and on Linux, distro-specific) ways to get the information, but I know of none that let an application request new info.

(In some cases, it should be unified with a service discovery system)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email