IETF Logo Mail Archive

Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?

Ole Troan <otroan@employees.org> Fri, 15 December 2017 13:21 UTC

Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2211289B5 for <v6ops@ietfa.amsl.com>; Fri, 15 Dec 2017 05:21:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 LJ9gUd4utpzI for <v6ops@ietfa.amsl.com>; Fri, 15 Dec 2017 05:21:54 -0800 (PST)
Received: from accordion.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37A4C127B5A for <v6ops@ietf.org>; Fri, 15 Dec 2017 05:21:54 -0800 (PST)
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by accordion.employees.org (Postfix) with ESMTPSA id A5A7C2D5219; Fri, 15 Dec 2017 13:21:53 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 8CE042012FC4C2; Fri, 15 Dec 2017 14:21:50 +0100 (CET)
From: Ole Troan <otroan@employees.org>
Message-Id: <827FCFAE-6A5A-4BC8-AF20-0A7D65F4EEB1@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_7C6D73B5-D8D8-4B7D-881B-DF8A81462BE0"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Fri, 15 Dec 2017 14:21:49 +0100
In-Reply-To: <DB4EE076-6231-4305-8514-0CC165C9EFD9@gmail.com>
Cc: Fred Templin <Fred.L.Templin@boeing.com>, "v6ops@ietf.org list" <v6ops@ietf.org>
To: Fred Baker <fredbaker.ietf@gmail.com>
References: <b9e5919554204ad48f33740eaac4ccb8@XCH15-06-08.nw.nos.boeing.com> <DB4EE076-6231-4305-8514-0CC165C9EFD9@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Tnosg-FR2EtTnAejW_dmWbc8JlY>
Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Dec 2017 13:21:56 -0000

>> Please review and send any new comments to the list, and please confirm whether
>> earlier comments have been addressed.
> 
> It continue to describe the entity delegating the prefix as a "Delegating Router 'D'". The IPAM (IP address Management, and by extension IP Prefix Management) software can be implemented in a computer sold as a router, but there is no requirement that it be, and it usually is not. As a matter of fact, if a router is a system that forwards messages directed to addresses other than its own, in the context of an application such as a DHCPv6 address/prefix management process, it is acting as a host, not a router.

Prefix delegation, more so than address assignment is coupled with the routing system.
Which is why RFC3633 only described a model where the delegating router and requesting router was directly connected.

Cheers,
Ole

v2.23.0 | Report a Bug | By Email