Re: [homenet] Selecting a routing protocol for HOMENET

Lorenzo Colitti <lorenzo@google.com> Sat, 04 April 2015 02:44 UTC

Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 353461A88EB for <homenet@ietfa.amsl.com>; Fri, 3 Apr 2015 19:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 rmBoYL5RDVRu for <homenet@ietfa.amsl.com>; Fri, 3 Apr 2015 19:44:48 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (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 0EE561A88F0 for <homenet@ietf.org>; Fri, 3 Apr 2015 19:44:47 -0700 (PDT)
Received: by iebrs15 with SMTP id rs15so16030624ieb.3 for <homenet@ietf.org>; Fri, 03 Apr 2015 19:44:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qCEn77vpf2UDgeDh4RNokU0sY79N1v4F8IgEbzo9W7U=; b=Gef2xO2kAGAIYjo7pHcHmwjOZ2iTk1dPlu8F7MCqMn6JqmSNxgllRtilj/UIJu0dER gquJYxZyv/LYgIIAUEaAKQq5tKb9kAVfpPBw0MXguZhnCNp/9CET9dPeypXo7Pw5k/BK E0bFrTa1ROPDwtAHP3VbjWIHZt9CkLUO9xAfa8a1vc6cvVoUmZ6iJl3SsuLbP37meWC+ DRUGaaqBsO35T4RXz6l8Y8AtXkzNeqAoLrVd5+O4o17nOdVinXdlutwGaXHj6QwH8r5E dk4rNC6AEdruv87pXdbHumBeDR+x7cTrkY8KD1oHdlbqEnndbGW4qtQxmKazGssQxBYD 99pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=qCEn77vpf2UDgeDh4RNokU0sY79N1v4F8IgEbzo9W7U=; b=OxjA/R6Rdt5NHex/x0lqEJv+zQ2nwy2jYl0gGSDaY0J4zhMU5zeOiEJbLKDMbsN4b0 t5VTSrsqdS50RUyKiVvjvwsNx5S036LCLX9RphRytH3draYf8JRn65O4KAG9g0gpAwis yAHu7p8O/DSZDSjuH2pRYKUWc7Ve3WA5Ke5RGbkNGaOg10Q2Jnk4x3UyjSAmAOkv+yJY Oc/0EqcTLZscJ4HutfjJFQ2olQSM0947TkMPttmofliiGlvsHzX8dZShSnPkY51ctS4Q 54LFTkBxqo/Ls4In3q5yCpmqGXD9f8WI95kb7w4HAm/m3I/vH2F3cLbuJG5f3OW5Fg3B 6pRw==
X-Gm-Message-State: ALoCoQmHpRKMUVNpOZlvw1/AWyH1rmhUhKUsvW5oBcn9cz1fJJdLinqnXjO8R5ZCN03r1T/ofwEX
X-Received: by 10.50.122.5 with SMTP id lo5mr8643003igb.37.1428115486473; Fri, 03 Apr 2015 19:44:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Fri, 3 Apr 2015 19:44:25 -0700 (PDT)
In-Reply-To: <CAG4d1rfT+Ej9LadM48Wn8G17ZuOwLFynxA0DGidCMu=mvv0hhQ@mail.gmail.com>
References: <D13A6CCE.570B1%terry.manderson@icann.org> <CAKD1Yr1aO=OrUyhCpBHYEsEvp1i5n80Yb0YpidhQesgui_PExA@mail.gmail.com> <D13A8708.570F4%terry.manderson@icann.org> <CAKD1Yr2s894VKJ4Kxhsn5bWy2CbEm=obEaUJLLAechtaYRy_wg@mail.gmail.com> <CADhXe50DFJR=CDuHUKeDY-pYNJNx1XRdTy_9kDx7P2Sq8sPQwQ@mail.gmail.com> <D140117E.57599%terry.manderson@icann.org> <CAA93jw4UMWhw69WFiip9hUqQCZrg1hcx12VZAECdgz4HO6FtqA@mail.gmail.com> <B616C12A-CA9D-4ED6-AC75-C72E627FD354@nominet.org.uk> <551AC4FE.3090106@joelhalpern.com> <57AFB8D5-2F79-49DF-B251-49423506F31E@gmail.com> <551AD21B.2070400@joelhalpern.com> <CAG4d1rcuYOPr_NBP+KzC9jnNGu0v2H+o-yzPK+Z5YV8KOfq-ew@mail.gmail.com> <87bnj8bz12.wl-jch@pps.univ-paris-diderot.fr> <CAG4d1rfT+Ej9LadM48Wn8G17ZuOwLFynxA0DGidCMu=mvv0hhQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 04 Apr 2015 11:44:25 +0900
Message-ID: <CAKD1Yr3eHs_JZPmJu+EbBpPAgdKNxEQjPJQS4cH5xNcfQ98yyg@mail.gmail.com>
To: Alia Atlas <akatlas@gmail.com>
Content-Type: multipart/alternative; boundary="089e015388b64536f20512dd0c94"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/c61C3UuCWN4SsPURD4oDsc-j0eY>
Cc: "int-ads@ietf.org" <int-ads@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>, Margaret Wasserman <margaretw42@gmail.com>, Dave Taht <dave.taht@gmail.com>, Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org" <homenet@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [homenet] Selecting a routing protocol for HOMENET
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 04 Apr 2015 02:44:49 -0000

On Fri, Apr 3, 2015 at 12:04 AM, Alia Atlas <akatlas@gmail.com> wrote:

> In the light of the above figures -- can I trust an IETF working group to
>> understand that a huge amount of effort has been put into removing
>> mechanisms from this protocol, and to respect that work?
>
>
> Yes, I think that the requirement for minimal mechanisms and a simple
> easy to implement and troubleshoot protocol can be clearly expressed.  How
> well the WG handles this depends in part on the WG chairs and how strongly
> the participants are reminded of that requirement and how stringently the
> need
> for truly active consensus is focused on.
>

Alia - can we put something to that effect in the charter?

There is a real risk that any WG working on standardizing babel will start
proposing lots of changes to the protocol (due to NIH syndrome, general
bikeshedding, etc.), alienating its author and leading to lost time and the
usual failures of design-by-committee.

To avoid this, can we see to it that the charter of any group chartered to
take babel to proposed standard status be chartered to do so without making
substantial changes to the protocol mechanics?

That way, if the protocol works well as is, we'll get a standard soon. If
it doesn't, the WG can always throw up its hands and fail fast.