IETF Logo Mail Archive

[dhcwg] DHCPv6 APIs for applications

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 16 October 2014 17:14 UTC

Return-Path: <mcr@sandelman.ca>
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 831561A026C for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 10:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] 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 ObiOoe3aQ8ij for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 10:14:38 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C240F1A0282 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 10:14:38 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5362D20031 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 13:15:11 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 4F3F063B40; Thu, 16 Oct 2014 13:14:37 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 34D1963B3F for <dhcwg@ietf.org>; Thu, 16 Oct 2014 13:14:37 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: dhcwg <dhcwg@ietf.org>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6D107D@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>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Thu, 16 Oct 2014 13:14:37 -0400
Message-ID: <16238.1413479677@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/u0VH9XHtpxqIWH-WVwqzsiIIctw
Subject: [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 17:14:41 -0000

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