IETF Logo Mail Archive

Re: [homenet] Configuration must not be carried by the routing protocol

Lorenzo Colitti <lorenzo@google.com> Wed, 26 June 2013 06:44 UTC

Return-Path: <lorenzo@google.com>
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 E08C121E8095 for <homenet@ietfa.amsl.com>; Tue, 25 Jun 2013 23:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64KPc0JcxsZW for <homenet@ietfa.amsl.com>; Tue, 25 Jun 2013 23:44:15 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id C33A111E813F for <homenet@ietf.org>; Tue, 25 Jun 2013 23:44:14 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id cz10so10849885veb.8 for <homenet@ietf.org>; Tue, 25 Jun 2013 23:44:14 -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=ZaDjXQCho0FmVMEtwLrGVcyJr4XlBg6bKQZ8CRNI3RA=; b=C+ut3Mm0HTFUtujrWZmDv1ZQQT3NSUpffroaUOiBQulMR5Wq3PXDqnACBoWrim30dT zAd/zgy8ZdhjBAqOJimyhoBjdYFYxIgRJkCEKITGQ6chOkjBr6pU80TnDxJ2GY9SdBht DtmqpELgeoPRBrgLZdqsGLRk7v+XBEnvnQ98ZHtGTJ0jYCZAYTupn2g6Y0sTnDZel/YT U2xfz4L0gXPoM2Q4EmmdQDsksmVxWh7Hs7+INTgX7f4XZw+7M5A2Rzts6ar4ZQpzoZm+ kK9bNfciUK28+meCZL0SjC2by3H3iak3aEQtQQ4J8A7qLnPqsY/bwsKeGxddRxxiNi4Z oRNQ==
X-Google-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:x-gm-message-state; bh=ZaDjXQCho0FmVMEtwLrGVcyJr4XlBg6bKQZ8CRNI3RA=; b=Ircc8TeKki3DkEWwr0qky7Pq9aDea/H8+xgy5nRlOga5CjEAJj5en9MhL9FZoMUAOu 7FH/E0nyuhZVjwoHLMG5fg/gqD98xmDMU0m4fpfx5cur0WuhvldzIiKuDGssZcsD+YZz IqzvwZz7nXdwvTPFCyFVyZqcVRX/BO17LFko18IQnMM9mVDznZbv+NDIpzj8Glzg0h9C udXOrumcxITt3sFaVdnH1BNF2BMdXaT3zcSekhvz+HXuAlyfQ8Qt+hOA1AGBk0ERZ+QJ IpLRCt3oBHCj02ZVEkfD1LJnFI+MHYoaoORY+HDxgA6tG2Q9xVd4QM017hG9dZsVBU0c f3Gg==
X-Received: by 10.58.76.34 with SMTP id h2mr1131226vew.93.1372229054137; Tue, 25 Jun 2013 23:44:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.172.66 with HTTP; Tue, 25 Jun 2013 23:43:53 -0700 (PDT)
In-Reply-To: <878v1yqhje.wl%jch@pps.univ-paris-diderot.fr>
References: <878v1yqhje.wl%jch@pps.univ-paris-diderot.fr>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 26 Jun 2013 15:43:53 +0900
Message-ID: <CAKD1Yr1FhwdtrSpXJQhdBHmuH37M3u_DzAiTpkKyV1L+dpstrw@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary="047d7b3437e452bb0904e008f9ec"
X-Gm-Message-State: ALoCoQnGuJhHdYRUjsPKxGN5l6GzKbR2WdDt+nJikBxXDw2takVs/bLwhAciHkBgEZjx6x8xVJG76pgkrY3Q+qD23OL0tbQcaA6SyTeTW9cTzG6zyfQhW1PwIkt5RI7vv+Cf1a/YGbsXx69MtwTVVN3pJ/sCyPDGCW8G6Vtkra7PKrJCHwKpYdEZfMG09iJWRBRaCgSsGKiO
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Configuration must not be carried by the routing protocol
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 26 Jun 2013 06:44:16 -0000

On Wed, Jun 26, 2013 at 1:30 AM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> (i)   distributing configuration information on a simple dedicated
>       protocol makes monitoring and trouble-shooting easier;
>

Actually, it doesn't, because in the "advantages of a routing protocol"
section above you forgot to mention one important advantage: fate sharing.

If you have one protocol that is distributing all the information in the
network, then all the information is either disseminated to a particular
device or it isn't, and when it is disseminated, it is disseminated all
together.

If you have two protocols, then the two sets of information are
disseminated asynchronously, and potentially - if there is a problem with
one of the two - not at all.

As running IPv4 and IPv6 in parallel shows, it's way harder to make two
things work than just one, because it's so much harder to figure out if
things are working or not.

v2.23.0 | Report a Bug | By Email