IETF Logo Mail Archive

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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 15 January 2018 20:54 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 C3DA412EC27 for <v6ops@ietfa.amsl.com>; Mon, 15 Jan 2018 12:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 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, URIBL_BLOCKED=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 3I7Tc96H5DeA for <v6ops@ietfa.amsl.com>; Mon, 15 Jan 2018 12:54:22 -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 D507C12EC08 for <v6ops@ietf.org>; Mon, 15 Jan 2018 12:54:22 -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 w0FKsLDx055477; Mon, 15 Jan 2018 13:54:21 -0700
Received: from XCH15-06-09.nw.nos.boeing.com (xch15-06-09.nw.nos.boeing.com [137.136.239.172]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w0FKsKVT055463 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 15 Jan 2018 13:54:20 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-09.nw.nos.boeing.com (2002:8988:efac::8988:efac) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 15 Jan 2018 12:54:19 -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; Mon, 15 Jan 2018 12:54:19 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>, Gert Doering <gert@space.net>
Thread-Topic: [v6ops] draft-templin-v6ops-pdhost a working group draft?
Thread-Index: AdOOQvRDLl8emuHnQGO0WDphKQAHfA==
Date: Mon, 15 Jan 2018 20:54:19 +0000
Message-ID: <1275a519d5aa450abf382c7a41ef6d02@XCH15-06-08.nw.nos.boeing.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/vZdjD7C-iamd3Sbb6hhzKeSe3cM>
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: Mon, 15 Jan 2018 20:54:25 -0000

Hi Gert,

> -----Original Message-----
> From: Gert Doering [mailto:gert@space.net]
> Sent: Monday, November 20, 2017 10:38 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: Gert Doering <gert@space.net>; Ole Troan <otroan@employees.org>; v6ops@ietf.org
> Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
> 
> Hi,
> 
> On Mon, Nov 20, 2017 at 06:32:53PM +0000, Templin, Fred L wrote:
> > > > The DHCPv6 client piece in OpenVPN is a few hundred lines of code
> > > > and was not hard to implement. And, if the client needs to do
> > > > something to request, manage and maintain a delegated prefix it
> > > > might as well be DHCPv6.
> > >
> > > So what does your patch *do* with the received prefix (since it's
> > > an out of tree patch I haven't seen yet)?  "Just configure it on the
> > > tun interface" (you do not need DHCPv6-PD for that)?
> >
> > It configures addresses derived from the prefix and assigns them
> > to the tun interface. It does not join the solicited-node multicast
> > address nor perform DAD over the tun interface.
> 
> So where's the benefit of doing DHCPv6-PD here?  *This* is a function
> OpenVPN can do out of the box just fine... *scratch head*
> 
> Single address, or "many"?
> 
> > Right now, it is only assigning a single address but it can in fact assign
> > as many addresses as it wants as shown in Figure 3 of 'pdhost'
> > without having to invoke MLD or DAD.
> >
> > Do you want to see our code?
> 
> It would be nice to have a look, but the "do DHCPv6-PD handshake" is not
> the really challenging bit

Per your interest, and for the benefit of the community, we published our
code on 01/10/2018: 

https://www.ietf.org/mail-archive/web/v6ops/current/msg28860.html

> - "do something interesting with the prefix"
> is...

That subject is covered in detail in 'draft-templin-v6ops-pdhost', and the
code provides an example.

Thanks - Fred

> Gert Doering
>         -- NetMaster
> --
> have you enabled IPv6 on something today...?
> 
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279

v2.23.0 | Report a Bug | By Email