From e2f963bb8c13808698ba287a5719f3dedd6bdf73 Mon Sep 17 00:00:00 2001 From: Tomek Mrugalski Date: Wed, 29 Mar 2017 13:20:17 -0500 Subject: [PATCH] [5132] Boilerplate description for flex_id --- doc/guide/hooks.xml | 47 ++++++++++++++++++++++++--------------------- 1 file changed, 25 insertions(+), 22 deletions(-) diff --git a/doc/guide/hooks.xml b/doc/guide/hooks.xml index 99997a1943..79b9bb629f 100644 --- a/doc/guide/hooks.xml +++ b/doc/guide/hooks.xml @@ -205,28 +205,23 @@ example and create your own custom logging hooks. - Lightweight 4over6 + Flexible Indentifier Support customers - Autumn 2016 - Lightweight 4over6 - (RFC 7596) - is a new IPv6 transition - technology that provides IPv4 as a service in IPv6-only - network. It assumes that dual-stack clients will get a regular IPv6 - address and IPv6 prefix, but only a fraction of an IPv4 address. The - fraction is specified as port-set, which is essentially a range of - TCP and UDP ports a client can use. By doing the transition on the - client side, this technology eliminates the need to deploy - expensive Carrier Grade NATs within the operator's network. The - problem on the DHCP side is the non-trivial logic behind it: each - client needs to receive an unique set of lightweight 4over6 options - (RFC 7598), - that include the IPv4 address (shared among several - clients), port-set (which is unique among clients sharing the same - IPv4 address) and a number of additional parameters. This hooks - library will generate values of those options dynamically, thus - eliminating the need to manually configure values for each client - separately. + Kea 1.2.0 beta + Kea software provides a way to handle host reservations + that include addresses, prefixes, options, client classes and + other features. The reservation can be based on hardware address, + DUID, circuit-id or client-id in DHCPv4 and using hardware address + or DUID in DHCPv6. However, there are sometimes scenario where the + reservation is more complex, e.g. uses other options that + mentioned above, uses part of specific options or perhaps even a + combination of several options and fields to uniquely identify a + client. Those scenarios are addressed by the Flexible Identifier + hook application. It allows defining an expression, similar to + the one used in client classiciation, + e.g. substring(relay6[0].option[37],0,6). Each incoming packet is + evaluated against that expression and its value is then searched + in the reservations database. @@ -341,7 +336,7 @@ and may have the zero or more of the following entries:
- Forensic Logging Hooks + legal_log: Forensic Logging Hooks This section describes the forensic log hooks library. This library provides hooks that record a detailed log of lease assignments @@ -551,6 +546,14 @@ link address: 3001::1, hop count: 1, identified by remote-id:
+ +
+ flex_id: Flexible Identifiers for Host Reservations + + This section describes ... TODO. + +
+
User contexts -- 2.47.3