IETF Logo Mail Archive

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

Tim Chown <tjc@ecs.soton.ac.uk> Tue, 25 June 2013 21:12 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 3EEA611E8152 for <homenet@ietfa.amsl.com>; Tue, 25 Jun 2013 14:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 TkFgPxKtIgsV for <homenet@ietfa.amsl.com>; Tue, 25 Jun 2013 14:12:13 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id F1BCB11E814C for <homenet@ietf.org>; Tue, 25 Jun 2013 14:12:09 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r5PLC1o4021681; Tue, 25 Jun 2013 22:12:01 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r5PLC1o4021681
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1372194721; bh=lKeM9RidvCoj1qPIqoSSUdwrL7E=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=Sn1EAucx+N3Ns6s7P95v9lo3xov++Mx/CAac5k+SAnf3cL/f634MSOhA85/rej06d /vlZHwDwiTnR3ii0gOErywqMro8k/Yum7oYI8Nn4udEB32gHMfOp76AWUEiEB3tJlD 3pRlJmb0Ay5YZwa4GfuSvtGZpZV3+LbKAeQgVn7A=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p5OMC10544557017uJ ret-id none; Tue, 25 Jun 2013 22:12:01 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r5PLBqH5020371 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 Jun 2013 22:11:53 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <94A203EA12AECE4BA92D42DBFFE0AE47189B02@eusaamb101.ericsson.se>
Date: Tue, 25 Jun 2013 22:11:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|8589f92e277a45c58b19f81e7bf00082p5OMC103tjc|ecs.soton.ac.uk|3BC166B2-EAAE-4AF8-9B20-0DE59ADB1FA0@ecs.soton.ac.uk>
References: <878v1yqhje.wl%jch@pps.univ-paris-diderot.fr> <020301ce71e1$da38d120$8eaa7360$@comcast.net> <94A203EA12AECE4BA92D42DBFFE0AE47189B02@eusaamb101.ericsson.se> <3BC166B2-EAAE-4AF8-9B20-0DE59ADB1FA0@ecs.soton.ac.uk>
To: Acee Lindem <acee.lindem@ericsson.com>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p5OMC1054455701700; tid=p5OMC10544557017uJ; client=relay,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r5PLC1o4021681
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "<homenet@ietf.org>" <homenet@ietf.org>, ietfdbh <ietfdbh@comcast.net>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
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: Tue, 25 Jun 2013 21:12:14 -0000

On 25 Jun 2013, at 21:34, Acee Lindem <acee.lindem@ericsson.com> wrote:

> In any case, I just scanned the architecture document and there doesn't appear to be anything that implies a routing protocol will be used to disseminate configuration. Hence, this discuss can be independent of the WGLC. 

Indeed.

Tim

v2.23.0 | Report a Bug | By Email