[dhcwg] URIs for backend storage

Tony Finch <dot@dotat.at> Mon, 19 March 2018 22:39 UTC

Return-Path: <dot@dotat.at>
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 37201124BAC for <dhcwg@ietfa.amsl.com>; Mon, 19 Mar 2018 15:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 7oCNPtaV5dzL for <dhcwg@ietfa.amsl.com>; Mon, 19 Mar 2018 15:39:17 -0700 (PDT)
Received: from ppsw-40.csi.cam.ac.uk (ppsw-40.csi.cam.ac.uk [131.111.8.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11D321205F0 for <dhcwg@ietf.org>; Mon, 19 Mar 2018 15:39:17 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:49966) by ppsw-40.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.138]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1ey3Qx-000Sv5-lK (Exim 4.89_2) for dhcwg@ietf.org (return-path <dot@dotat.at>); Mon, 19 Mar 2018 22:39:15 +0000
Date: Mon, 19 Mar 2018 22:39:15 +0000
From: Tony Finch <dot@dotat.at>
To: dhcwg@ietf.org
Message-ID: <alpine.DEB.2.11.1803192228290.8194@grey.csi.cam.ac.uk>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/5g_MDiu_7zisrqnNcCfGO2ni81A>
Subject: [dhcwg] URIs for backend storage
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 19 Mar 2018 22:39:45 -0000

One of the questions that arose in the DHC WG meeting this afternoon was
about a standard YANG netconf way to describe backend storage for leases.
IIRC, someone asked if a URL would be enough and the general response was
um, maybe?

There is a de-facto quasi-standard for database connection URLs used by
JDBC - pretty much all SQL databases and some noSQL databases (including
Cassandra) have a spec for describing connection details in a URL,
including when there are multiple possible servers.

Of course, instead of a JDBC URL, you could also configure your DHCP
server with a file: URL for old school lease storage.

I found out about this from PostgreSQL -
https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING

I haven't found a good description of C* JDBC URLs other than
https://stackoverflow.com/questions/30743272/what-is-the-connection-url-to-be-used-for-cassandra#30795079
which suggests that they use `--` for separating hostnames (which from
my pedantic hostmaster point of view is mildly problematic...!)

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Sole, Lundy, Fastnet: Northeast 5 to 7, becoming variable 3 or 4. Moderate or
rough. Mainly fair. Good.