[dhcwg] WGLC on draft-ietf-dhc-sedhcpv6-21 - summary

Tomek Mrugalski <tomasz.mrugalski@gmail.com> Wed, 05 April 2017 19:06 UTC

Return-Path: <tomasz.mrugalski@gmail.com>
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 2DA4F12947A; Wed, 5 Apr 2017 12:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Gc1iuKYckDqC; Wed, 5 Apr 2017 12:06:42 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (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 0C46F12706D; Wed, 5 Apr 2017 12:06:42 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id x137so15030270lff.3; Wed, 05 Apr 2017 12:06:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=qoqN1SrW8DRF2PZnqgxH4XXdrGOW/B8SA0QvHeEZinM=; b=fDw8u6tCFhLKFMzQ2hjWggNCzqbh2WbxrPPFHXLha1g8Mn6G0aQtFnMSFi9JNnPGwa CpAkEi0+kuX3UZUh3L1dLagASho6IxcRc65Jhz2rUfqGjG/VgzKveKt/DhWwuKnpFi5z iHTMXGBd6etZRGEHYV63evGsTihHqcQTZ47J0vRhM72213ISRNX8PD7xvoMz96H9wVpH D1OKCuu/C1Z0UWSvst2QIwsH8bT+MW6FYEi5xAWpios8vMD/jTpiomXn5pG+fbh8xNcm tyHJY0sBJszGsHeATYWNE1JNSkEqQMY3TkFsg1mWLkRM76IsxR6uzMRqq+Ygg4zYEJJL h7CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=qoqN1SrW8DRF2PZnqgxH4XXdrGOW/B8SA0QvHeEZinM=; b=gkkBgu47SLl+azCMi/kFwC3+Db0O3xJdiB50dOwCdsZcKnT86KbiaYcHnAOHbkKiFp C1ru0u98wu8eDWrGFSw99auc8qyg/+MCC3atrKEzMCudf2ENh5Tb9A2mjR34w3XTvDKv NtqlGEzhAUXybdCPdyPrYbBcCx+wF2/6ykMDDnWwHwNQi19tfhLqOlpxlY8EYEuIs/F+ BMy1fCu6c1RMFnRHBAmmgVhZul/U3SR+4dDA4EKzZqasLlygaB+TmHmiDipKIgSx7m9S TYgdMXpv1ylGb1SH14ywPeS9reUKAL93z4Z4B+7FUfsX+wPHd2U2UkigMvYz6GhhaxdJ 2Z3w==
X-Gm-Message-State: AFeK/H3Ar7CinOlJDxwozJcgJQLQ0ln1snX0eqwVnLN0AeBGSZIci8+9Gw5CkdyBIN3Oqg==
X-Received: by 10.46.84.22 with SMTP id i22mr8654974ljb.132.1491419199880; Wed, 05 Apr 2017 12:06:39 -0700 (PDT)
Received: from [192.168.0.5] (109241207033.gdansk.vectranet.pl. [109.241.207.33]) by smtp.googlemail.com with ESMTPSA id a16sm3943330lfk.24.2017.04.05.12.06.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Apr 2017 12:06:39 -0700 (PDT)
To: dhcwg <dhcwg@ietf.org>
References: <e08be0f6-f1b4-4f57-6cdf-ddd546f8b793@gmail.com>
Cc: draft-ietf-dhc-sedhcpv6 authors <draft-ietf-dhc-sedhcpv6@ietf.org>
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Message-ID: <1380758a-b7d0-bb73-bf58-4e318e88a6d0@gmail.com>
Date: Wed, 5 Apr 2017 21:06:36 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <e08be0f6-f1b4-4f57-6cdf-ddd546f8b793@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/YYEm0TsXyFSOneF4NKUZ_bMzdI8>
Subject: [dhcwg] WGLC on draft-ietf-dhc-sedhcpv6-21 - summary
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: Wed, 05 Apr 2017 19:06:44 -0000

It took a little bit more than planned, but the extra time gave us a
couple more comments.

We did receive a number of in depth reviews with technical comments. In
general, several people praised the significantly improved quality and
clarity of the document. Nobody said that is opposed to this work. So
from that perspective this last call is a success.

However, both chair and at least one co-author feel that an important
concern has not been addressed yet. There currently are no known
implementations or prototypes of this draft. For a typical DHCP draft
that adds an option or two that would probably be fine, but for this
particular draft it is not. For two reasons: First, we feel that this is
an essential piece of the whole DHCPv6 ecosystem and as such require
much more scrutiny then an average draft. Second, security is a complex
matter and any unclear aspects would gravely damage the
interoperability. Jinmei had put it well: "I suspect the current spec
still has some points that are critically unclear, which you would
immediately notice once you tried to implement it."

Given that, we declare that more effort is needed before this work is
deemed ready for IESG. At the same time, chairs would like to strongly
applaud authors' efforts to improve this work. This version is
significantly better than its predecessors. Thank you for your hard
work. You are doing excellent work. Please continue.

Also, to address the concern of missing implementations, chairs would
like to announce a DHCP hackathon in Prague. Details are TBD, but the
primary goal will be to have at least two independent implementations of
that draft. The hackathon will take place the weekend before IETF
meeting (that's July 15-16). A separate announcement will be sent soon.

That is well over 3 months away. Authors and supporters of this work,
please seriously consider dedicating some of your time implementing
prototypes and attending the hackathon, if you can. If you can't we will
organize some means for participating remotely.

Thank you to the authors and to everyone who commented.

Bernie & Tomek