IETF Logo Mail Archive

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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 15 December 2017 15:15 UTC

Return-Path: <Fred.L.Templin@boeing.com>
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 7F5A5124205 for <v6ops@ietfa.amsl.com>; Fri, 15 Dec 2017 07:15:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 XAEvkQGUcdNf for <v6ops@ietfa.amsl.com>; Fri, 15 Dec 2017 07:15:09 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14C351200CF for <v6ops@ietf.org>; Fri, 15 Dec 2017 07:15:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id vBFFF7Ia043876; Fri, 15 Dec 2017 08:15:08 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id vBFFF5Nd043811 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 15 Dec 2017 08:15:05 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Fri, 15 Dec 2017 07:15:04 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1347.000; Fri, 15 Dec 2017 07:15:04 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
CC: "v6ops@ietf.org list" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-templin-v6ops-pdhost a working group draft?
Thread-Index: AdN0/pQbESM/pUHWTBC3IMugjrlkIwAh2vmAAAwwYIA=
Date: Fri, 15 Dec 2017 15:15:04 +0000
Message-ID: <067dd11055934a3489e90a12de6d0da6@XCH15-06-08.nw.nos.boeing.com>
References: <b9e5919554204ad48f33740eaac4ccb8@XCH15-06-08.nw.nos.boeing.com> <DB4EE076-6231-4305-8514-0CC165C9EFD9@gmail.com>
In-Reply-To: <DB4EE076-6231-4305-8514-0CC165C9EFD9@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/JwRYngWSoSzaKHeCJKgmggliJww>
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 15:15:15 -0000

Hi Fred,

> -----Original Message-----
> From: Fred Baker [mailto:fredbaker.ietf@gmail.com]
> Sent: Thursday, December 14, 2017 5:21 PM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: v6ops@ietf.org list <v6ops@ietf.org>
> Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
> 
> 
> 
> On Dec 14, 2017, at 9:19 AM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
> > 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.

The Delegating Router / Requesting Router relationship is the same as in
RFC3633. If the Delegating Router does not implement the actual prefix
delegation service locally, then it forwards prefix delegation requests to
some other node in the operator's network that provides the service.
That node need not be a router (it could be a simple server running in
some VM). But, the Delegating Router is still a router.

See also Section 14 of RFC3633 for discussion about DHCPv6 relay agents
on Delegating Routers.

Thanks - Fred

> https://www.google.com/search?q=ipam
> For example, https://en.wikipedia.org/wiki/IP_address_management

v2.23.0 | Report a Bug | By Email