Re: [homenet] The HOMENET WG has placed draft-lemon-homenet-naming-architecture in state "Candidate for WG Adoption"

Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> Mon, 25 July 2016 20:23 UTC

Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BFDF12DA03 for <homenet@ietfa.amsl.com>; Mon, 25 Jul 2016 13:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 PgHTbVtORCJv for <homenet@ietfa.amsl.com>; Mon, 25 Jul 2016 13:23:57 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) (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 AC44912D885 for <homenet@ietf.org>; Mon, 25 Jul 2016 13:23:57 -0700 (PDT)
Received: from trurl.pps.univ-paris-diderot.fr (unknown [IPv6:2a01:e34:ec22:84a1:4149:227c:fa5b:2b1c]) by smtp6-g21.free.fr (Postfix) with ESMTPS id 7487E78039F for <homenet@ietf.org>; Mon, 25 Jul 2016 18:44:51 +0200 (CEST)
Date: Mon, 25 Jul 2016 22:23:54 +0200
Message-ID: <87k2g9xy91.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: homenet@ietf.org
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/m05uUCGT2XyQ3NYEOVglKHhqb7Y>
Subject: Re: [homenet] The HOMENET WG has placed draft-lemon-homenet-naming-architecture in state "Candidate for WG Adoption"
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2016 20:23:59 -0000

I would like to reiterate my opposition to four requirements of this
draft (as described in my mail of 18 July):

 - the requirement for a new ND option;
 - the requirement for a RESTful management API;
 - the requirement for a local DNS resolver on each link;
 - the requirement for a ULA.

Speaking as the author of one of only two implementations of HNCP, I would
like to be very clear that I shall not implement a RESTful management API,
and I shall not implement a local DNS resolver.  I will also not make it
compulsory to deploy a ULA, although I'm willing to make it the default
behaviour.  (I have no objection to implementing the ND option, assuming
that somebody else gets it deployed in host implementations.)

I believe that it would be premature to adopt this draft now, at least
until people have had a chance to consider the consequences for
implementations.  The best way IMO would be to have a prototype implementation,
which I will be glad to review.

I shall not make too much of a fuss should the WG decide to adopt this
draft notwithstanding my objections.  However, I reserve the right to say
"I told you so" when we eventually run into trouble.

-- Juliusz

P.S. Our mail server is down until Thursday, please reply to the list.