Re: [dhcwg] sunset4 & DHCP4o6

Tomek Mrugalski <tomasz.mrugalski@gmail.com> Tue, 21 July 2015 11:51 UTC

Return-Path: <tomasz.mrugalski@gmail.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 65B341A0A6A for <dhcwg@ietfa.amsl.com>; Tue, 21 Jul 2015 04:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 OxqAPu6w9NtX for <dhcwg@ietfa.amsl.com>; Tue, 21 Jul 2015 04:51:46 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF57F1A09C9 for <dhcwg@ietf.org>; Tue, 21 Jul 2015 04:51:45 -0700 (PDT)
Received: by wibxm9 with SMTP id xm9so54407893wib.1 for <dhcwg@ietf.org>; Tue, 21 Jul 2015 04:51:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+98zFWxsQx+oag0/y6kXWwF756tTtkqCFeIH2ueUwGg=; b=MpgDGU5UZ/cCcfjLQjIRFd3zNlEdh6QMBmF29WEqnq0xMR15/rurOLlncrVPNcHY76 q7K6temesNv6B2wcLxybn2lSqMj7YvEvgmWgOUYcfzxkNA88xZCTGFmZ4nAOimYYELxi O739lMt75i+R8u8PLwWYAJk/qNiiPYKXXGdxzcdEawR7r4qgZjWvgemIUuE0YhkPbY61 4jTo5irRiR74i6/uXJ9MQvWsPwwCfhHsb/RNxpfWhk4vRczU2b+ztt6qB6duopQaBWLi F2vFxn4AYXu30Jel/ktoBW0N5gYdqLdxyJLxnaL9hY4BohKr0Fk/OTcnfQbOKIPKkewF 1tUQ==
X-Received: by 10.194.142.209 with SMTP id ry17mr70364324wjb.5.1437479504634; Tue, 21 Jul 2015 04:51:44 -0700 (PDT)
Received: from dhcp-b2d4.meeting.ietf.org (dhcp-b2d4.meeting.ietf.org. [31.133.178.212]) by smtp.googlemail.com with ESMTPSA id c11sm16490455wib.1.2015.07.21.04.51.43 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Jul 2015 04:51:43 -0700 (PDT)
Message-ID: <55AE324F.9080509@gmail.com>
Date: Tue, 21 Jul 2015 13:51:43 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@fdupont.fr>, dhcwg@ietf.org
References: <201507211117.t6LBH4Cr022993@givry.fdupont.fr>
In-Reply-To: <201507211117.t6LBH4Cr022993@givry.fdupont.fr>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/jL5BaYhCJsbjlucpk0X3eCpP9J8>
Subject: Re: [dhcwg] sunset4 & DHCP4o6
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: <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: Tue, 21 Jul 2015 11:51:47 -0000

On 21/07/15 13:17, Francis Dupont wrote:
> Looking the slides of the "Gap analysis" at the sunset4+v6ops session
> of IETF 93 it seems a good idea to collect and publish an implementation
> summary for DHCP4o6 (i.e., the list of available and planned implementations
> of DHCP4o6 clients and servers). 
Feel free to research this topic a bit and assemble such a list. While
the availability of existing implementations (or lack of thereof) does
not make or break a standard proposal, it may be useful to have some
insight into how popular a given mechanism really is. Having multiple,
hopefully interoperating implementation is certainly a desired thing in
the draft phase, but please do note that we're talking about published
RFC here.

If that information is of any use for you or anyone else, I'm aware of 4
implementations:
- patch for Kea (server), implemented by Tsinghua University, currently
semi-abandoned/stuck in review
- patch for ISC-DHCP (server), by Zagreb University
- patch for ISC-DHCP (server/client), you may know a bit more about this
as you were the implementor ;)
- Tsinghua University also had a very basic stub client implementation

> IMHO a typical job for the DHC WG.
It is not. Tracking current state of commercial and open source software
and its suport for published RFCs is in general case out of scope of the
DHC WG (any WG in my opinion). Otherwise, the traffic on WG mailing list
could quickly turn into endless stream of marketing-like announcements
from all DHCP implementations.

Tomek