Re: [dhcwg] DHCP hackathon in Prague: SeDHCPv6

神明達哉 <> Wed, 31 May 2017 18:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 438EE12957B for <>; Wed, 31 May 2017 11:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HwxKzVW6thvJ for <>; Wed, 31 May 2017 11:01:45 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6FB36128BBB for <>; Wed, 31 May 2017 11:01:45 -0700 (PDT)
Received: by with SMTP id 19so18252692qke.2 for <>; Wed, 31 May 2017 11:01:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=dMI3GfRtGMiWl+3miRyhdj4Csim34+JwlIB841shssY=; b=WjFvHJie4NBGKKimErpcv+MvF2/lYK28GNwGl0RqJaJHW1npZ190uzlFKeGYVfxy34 6k4t9p0dNO1pKIZH74tOdOllj9gR9GuMZcAiny3FrSKeR0adccHyZXQBtfN3Zd6X5aDU s7tWRhSjEwB4gNCqEca4iZdk74YWASEhhv5SCiHVkPuI1RUstGn+GcF5OHcuV6iqRY1O FB1hFy0EnvuFsSBFnfZr7SWFOXz2GaDl7tSVF6hy1WEK78ixHAZUzMoWkdAUTj4NoIAi 8Gg0gCN4+5ZFGB1zvyg/MSyXumZ9Osu6h8YKM5Si7CDnV8kHVE+e7uO9GzyHivpv+yzd muCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=dMI3GfRtGMiWl+3miRyhdj4Csim34+JwlIB841shssY=; b=LcCb8ID3N6SzjQNYx2mJSleh/TZdQnpOSCstBriPPPvbBp+ZeEsRbXnTxnmN8JxyNY tKGwgDyOuiL+Iup/AIfqRdaUL8dSs2GHs2cFe+Hz/rvu6ylfinlYNGHnpRU/IwD8AvuB lyAev6BGscwEsu/xGrWWoGCefQUjR4JUDxiB2epptEEvpHm9RuHLDDsdwnBQIkCk51NU FUOKp9Xj+fUNC8jWKK0cJk3SHJ7drBo1Q1zfJLaBoTbgtjZKRIYP1rhwmlMw50leeloa qY5rDA+4u781VYlYESP0kz/nOe+s0UHb88jQhcfUlFWqDATtbfKC8+nTE0r3+FgRcomN Fzbg==
X-Gm-Message-State: AODbwcBYU6IZGKLt0hOUwNKVJZhrG0iiW5tZGdJlWL3Ap8mxuCfXNx+X oZ7BGHyuMG2jDUyWR10XmqspO8QUHG4ZWmo=
X-Received: by with SMTP id 62mr28043973qkw.242.1496253704428; Wed, 31 May 2017 11:01:44 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Wed, 31 May 2017 11:01:44 -0700 (PDT)
In-Reply-To: <>
References: <> <>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <>
Date: Wed, 31 May 2017 11:01:44 -0700
X-Google-Sender-Auth: 5mEMhVBVrix1pNyKTRmRuvTOziE
Message-ID: <>
To: Tomek Mrugalski <>
Cc: dhcwg <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [dhcwg] DHCP hackathon in Prague: SeDHCPv6
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 31 May 2017 18:01:47 -0000

At Wed, 31 May 2017 17:36:05 +0200,
Tomek Mrugalski <> wrote:

> As previously mentioned, we'll have a DHCP hackathon in Prague. As
> usual, the hackathon will take place on the weekend immediately before
> IETF (July 15-16). This time we will be focusing on SeDHCPv6. If you
> somehow missed all the discussions so far, the
> draft-ietf-dhc-sedhcpv6-21 defines Secure DHCPv6, an encrypted and
> possibly authenticated version of DHCPv6 protocol. The goal of this
> hackathon is to extend existing DHCPv6 implementations and attempt
> inter-operability testing for encryption and authentication. We hope to
> have the following implementations at various stages of maturity:

I guess there's at least one fundamental open issue to be resolved
before even trying to implement it:

I'm afraid this is so fundamental that it's almost useless to have a
hackathon without a consensus on it.  (For some other issues yet to be
uncovered hackathon would actually be a good opportunity to find them.
But I suspect this one is too fundamental to be that type of issue).

JINMEI, Tatuya