PIO-X in draft-pioxfolks-6man-pio-exclusive-bit-01 and earlier draft-kaiser-nd-pd-02

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 30 March 2017 15:49 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D94B412952C for <ipv6@ietfa.amsl.com>; Thu, 30 Mar 2017 08:49:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.332
X-Spam-Level:
X-Spam-Status: No, score=-0.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665] autolearn=no 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 FJ9P1PgtFRWJ for <ipv6@ietfa.amsl.com>; Thu, 30 Mar 2017 08:49:18 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 CD67A128BE1 for <ipv6@ietf.org>; Thu, 30 Mar 2017 08:49:17 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v2UFnFvl010277 for <ipv6@ietf.org>; Thu, 30 Mar 2017 17:49:15 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CAE47209041 for <ipv6@ietf.org>; Thu, 30 Mar 2017 17:49:15 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BF046208EE5 for <ipv6@ietf.org>; Thu, 30 Mar 2017 17:49:15 +0200 (CEST)
Received: from [132.166.85.9] ([132.166.85.9]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v2UFnEeQ013443 for <ipv6@ietf.org>; Thu, 30 Mar 2017 17:49:15 +0200
Subject: PIO-X in draft-pioxfolks-6man-pio-exclusive-bit-01 and earlier draft-kaiser-nd-pd-02
References: <CAOv0Pi-f+epkdYKvOUFLU+EiX+gz4rzU-LOA0qXjNovejgO0FQ@mail.gmail.com>
To: ipv6@ietf.org
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <8b0b8ece-c41b-910f-28e0-083e04073bf1@gmail.com>
Date: Thu, 30 Mar 2017 10:48:59 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAOv0Pi-f+epkdYKvOUFLU+EiX+gz4rzU-LOA0qXjNovejgO0FQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------E7A6AA9C5831E23213EC3616"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/F7rX3N6xNnNwcXfgkp8RzXRMi1Q>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Mar 2017 15:49:21 -0000

Hi, authors of PIO-X,

My comment on the microphone:

This is an earlier draft I co-authored that uses RS/RA messages to do 
Prefix Delegation.

draft-kaiser-nd-pd-02

https://tools.ietf.org/html/draft-kaiser-nd-pd-02


I can resurrect it if necessary.

Alex


Le 28/03/2017 à 11:57, Alexandre Petrescu a écrit :
> In addition to asking how is this draft helping with DHCPv6 Prefix 
> Delegation,
>
> I suggest addition of the following references.
>
> Where draft-pioxfolks-6man-pio-exclusive-bit-01 says:
> >    There are several initiatives that propose network side practices
> >    that provide customer isolation, enhanced operational scalability,
> >    power efficiency, security and other benefits in IPv6 network
> >    deployments.  Some of these involve isolating a host (or RA accepting
> >    client node) so that the host is the only node to receive a specific
> >    prefix, including
> >
> >    o  DHCPv6 Prefix Delegation to hosts (<https://tools.ietf.org/html/
> >       draft-templin-v6ops-pdhost>), and
> >
> >    o  advertising a unique prefix per host via unique RAs.
> >       (<https://tools.ietf.org/html/draft-ietf-v6ops-unique-ipv6-prefix-
> >       per-host>).
>
> it makes sense to add:
>
>     o  Prefix Delegation extensions to ND protocol have been introduced
>        in <draft-kaiser-nd-pd-02>, <draft-lutchann-ipv6-delegate-
>        option-00> and <draft-haberman-ipngwg-auto-prefix-02>, and
>        probably earlier.
>
> Alex
>
> Le 04/03/2017 à 06:31, Alexandre Petrescu a écrit :
> > I do not oppose a slot presenting PIO-X if time allows.
> >
> > However, as I understand it, PIO-X has a single goal - that to
> > accomodate 64share.
> >
> > I wonder whether PIO-X could work with DHCPv6-PD?  Would PIO-X help
> > DHCPv6-PD deployment?
> >
> > This is what I am going to ask at the mic.
> >
> > Alex
> >
> >
> >
> > Le 01/03/2017 à 11:27, Erik Kline a écrit :
> >> Ole,
> >>
> >> It's on me to get a -02 of PIO-X written and uploaded.  Might it be
> >> possible to get 5 minutes on that?
> >>
> >> -ek
> >>
> >> On 27 February 2017 at 06:16, <otroan@employees.org 
> <mailto:otroan@employees.org>
> >> <mailto:otroan@employees.org <mailto:otroan@employees.org>>> wrote:
> >>
> >>     The 6MAN chairs are planning the meeting in Chicago at IETF98.
> >>
> >>     If you have a draft you would like to discuss, please send your
> >>     request for agenda time to the 6man chairs. Please include in the
> >>     request, the title of the presentation, file name of the draft, the
> >>     speaker's name (and email), and how much time you would like.
> >>
> >>     We will prioritise drafts that are working group items and drafts
> >>     that have been actively discussed on the list.
> >>
> >>     We expect at least half of each talk’s presentation time to be used
> >>     for open discussion,
> >>     please plan your presentation accordingly.
> >>
> >>     New drafts not discussed on the mailing list prior to the meeting,
> >>     or drafts that do not appear to have support from the working group
> >>     are unlikely to get time at the meeting.
> >>
> >>     Please have agenda items to us by 2017-03-15.
> >>
> >>     Regards,
> >>
> >>     Bob & Ole
> >>
> >> --------------------------------------------------------------------
> >>     IETF IPv6 working group mailing list
> >> ipv6@ietf.org <mailto:ipv6@ietf.org> <mailto:ipv6@ietf.org 
> <mailto:ipv6@ietf.org>>
> >>     Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>     <https://www.ietf.org/mailman/listinfo/ipv6>
> >> --------------------------------------------------------------------
> >>
> >>
> >>
> >>
> >> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> ipv6@ietf.org <mailto:ipv6@ietf.org>
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >> --------------------------------------------------------------------
> >>
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org <mailto:ipv6@ietf.org>
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------