Re: [v6ops] PD to hosts [was: DAD again [was: draft-ietf-v6ops-host-addr-availability discussion] ]
<mohamed.boucadair@orange.com> Tue, 17 November 2015 15:39 UTC
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECA7A1AC42E for <v6ops@ietfa.amsl.com>; Tue, 17 Nov 2015 07:39:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level:
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 fRXi-E-Kd_Mp for <v6ops@ietfa.amsl.com>; Tue, 17 Nov 2015 07:39:36 -0800 (PST)
Received: from relais-inet.orange.com (relais-nor35.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 752201A9136 for <v6ops@ietf.org>; Tue, 17 Nov 2015 07:39:36 -0800 (PST)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id DFD432008F; Tue, 17 Nov 2015 16:39:34 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.18]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id BA6CC1A0061; Tue, 17 Nov 2015 16:39:34 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM34.corporate.adroot.infra.ftgroup ([fe80::cba:56d0:a732:ef5a%19]) with mapi id 14.03.0248.002; Tue, 17 Nov 2015 16:39:34 +0100
From: mohamed.boucadair@orange.com
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] PD to hosts [was: DAD again [was: draft-ietf-v6ops-host-addr-availability discussion] ]
Thread-Index: AQHRISjBKXywGSjIXkWLXwLhOaFsAZ6gWXVw
Date: Tue, 17 Nov 2015 15:39:34 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9F53A@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <m1ZyNBq-0000HnC@stereo.hq.phicoh.net> <2134F8430051B64F815C691A62D9831832F4CF07@XCH-BLV-504.nw.nos.boeing.com> <m1ZyNyc-0000EoC@stereo.hq.phicoh.net> <564B0B65.6080305@gmail.com>
In-Reply-To: <564B0B65.6080305@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/tCKAkWiR0kyl2iqr4XxLxMZk38E>
Subject: Re: [v6ops] PD to hosts [was: DAD again [was: draft-ietf-v6ops-host-addr-availability discussion] ]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Nov 2015 15:39:38 -0000
Hi Alex, all, Please see inline. Cheers, Med > -----Message d'origine----- > De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de Alexandre > Petrescu > Envoyé : mardi 17 novembre 2015 12:12 > À : v6ops@ietf.org > Objet : Re: [v6ops] PD to hosts [was: DAD again [was: draft-ietf-v6ops- > host-addr-availability discussion] ] > > > > Le 16/11/2015 18:53, Philip Homburg a écrit : > >>> 1) How do packets reach the host. Is that documented somewhere? > >> > >> RFC3633 is largely silent on this, but when P is delegated to N, it > >> is implied that the delegating router must somehow inject > >> information into the routing system that will guide packets with > >> destination address A to N. > > > > I wonder where this should be documented. > > I agree it shoul dbe documented. > > > There seem to be some other interesting interactions: a DHCPv6 server > > running on a host should not hand out a PD to a host (because it > > doesn't work), but can hand it out to a router. And can hand it out > > when there request comes through a relay agent. > > > > A relay agent running on a router should install a routing table > > entry if the PD request comes from a host. > > Certainly yes. > > In the past we tried a problem statement draft about how PD impacts > routing at Relay. [Med] Better with pointers: * https://tools.ietf.org/html/draft-petrescu-relay-route-pd-problem-00 And * https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-03
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Philip Homburg
- [v6ops] PD to hosts [was: DAD again [was: draft-i… Philip Homburg
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Templin, Fred L
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Templin, Fred L
- Re: [v6ops] PD to hosts sthaug
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Philip Homburg
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Templin, Fred L
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Philip Homburg
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Alexandre Petrescu
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Alexandre Petrescu
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Alexandre Petrescu
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… mohamed.boucadair
- Re: [v6ops] PD to hosts [was: DAD again [was: dra… Templin, Fred L