IETF Logo Mail Archive

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

Teco Boot <teco@inf-net.nl> Wed, 26 June 2013 10:19 UTC

Return-Path: <teco@inf-net.nl>
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 2FF7511E81AF for <homenet@ietfa.amsl.com>; Wed, 26 Jun 2013 03:19:49 -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 RYQMVbVzBkHQ for <homenet@ietfa.amsl.com>; Wed, 26 Jun 2013 03:19:48 -0700 (PDT)
Received: from mail-ee0-x231.google.com (mail-ee0-x231.google.com [IPv6:2a00:1450:4013:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id CF70D11E80D2 for <homenet@ietf.org>; Wed, 26 Jun 2013 03:19:46 -0700 (PDT)
Received: by mail-ee0-f49.google.com with SMTP id b57so7306765eek.22 for <homenet@ietf.org>; Wed, 26 Jun 2013 03:19:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=BDtzSuvEy+t5Qct5b2MrHoI6b6/R/ANYPkk3Gn5gu9Q=; b=IHDyN9shCZcVH0F18Kx8GKRU4bh+NukVW835OIXFDXm1+Wh11vUunpd5AoyF4MF7Dh UkCykCeZUiMafNF0qCJp5gEB23zWjj36OwAVz7GE0tRNE229DNhqJR3kALFYRsS5H74H 6yEr7KFQhqisK6DIkNKImWjk11NBrCs0XUXloEQozl56fJsjsn7tMKbqdv1fDrXZ+/Th /Vkf9YVZWoAl9ly5l/ZlC5W2kHlMY3Q3mWJMaym99K8I2YCWQS+AXv3C03dduHKmb1gh oKvxw3IqFyHIV5IxjdZVfXSGRoVHRrmaKXxl3rvFyX2U8l6B9vwKtgTypVZTUfVRFOlI Y1Zw==
X-Received: by 10.14.95.69 with SMTP id o45mr3416350eef.48.1372241986103; Wed, 26 Jun 2013 03:19:46 -0700 (PDT)
Received: from [172.16.4.22] ([188.205.88.52]) by mx.google.com with ESMTPSA id b3sm41915364eev.10.2013.06.26.03.19.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Jun 2013 03:19:45 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <1A4D24AC-445C-422A-B2C8-D9C307347BA0@townsley.net>
Date: Wed, 26 Jun 2013 12:19:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CD3BE19C-540E-4F54-A7DC-722552D25EC9@inf-net.nl>
References: <878v1yqhje.wl%jch@pps.univ-paris-diderot.fr> <020301ce71e1$da38d120$8eaa7360$@comcast.net> <87wqphonkv.wl%jch@pps.univ-paris-diderot.fr> <1A4D24AC-445C-422A-B2C8-D9C307347BA0@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQkfM/TG6MZR+8B33/iAiYYtj0W4cVKC7i5r2mXZXSRzRG3XVv3w6PJB7+IYTvtk3LPaLGlD
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, 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: Wed, 26 Jun 2013 10:19:49 -0000

Op 26 jun. 2013, om 10:08 heeft Mark Townsley <mark@townsley.net> het volgende geschreven:

> On Jun 26, 2013, at 12:03 AM, Juliusz Chroboczek wrote:
> 
>>> Just a comment ...
>>> You say " There is an IETF standard configuration protocol, and that's
>>> DHCPv6."
>> 
>>> Actually, the IETF has a number of configuration protocol standards, not
>>> just DHCPv6.
> 
> Not to mention "HC" stands for "Host Configuration" not "Router Configuration." 
> 
> RFC 2131 is very clear, 
> "   DHCP is not intended for use in configuring routers."
> 
> That explicit statement went away in RFC 3315, though the terminology section makes it very clear that a Host is not a Router.

I guess you don't intend to turn off Internet access for many because DHCP is not for routers.

Teco

PS: Mail delivered via IPv4, via interfaces on multiple routers with DHCP client enabled.

v2.23.0 | Report a Bug | By Email