Re: [94attendees] [homenet] IPv6 Prefix delegation on IETF network, please ?

Alexandre Petrescu <alexandru.petrescu@gmail.com> Wed, 04 November 2015 02:05 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: 94attendees@ietfa.amsl.com
Delivered-To: 94attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7593E1A8988 for <94attendees@ietfa.amsl.com>; Tue, 3 Nov 2015 18:05:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-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 RmxBViK-EAyW for <94attendees@ietfa.amsl.com>; Tue, 3 Nov 2015 18:05:07 -0800 (PST)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9AE01A8989 for <94attendees@ietf.org>; Tue, 3 Nov 2015 18:05:06 -0800 (PST)
Received: by pabfh17 with SMTP id fh17so36147184pab.0 for <94attendees@ietf.org>; Tue, 03 Nov 2015 18:05:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=UuyafETfYiK2cdc2QvNxIZUgbJupjy/TcMze4CFBANo=; b=IHFAmrAEtguVHEDCNJqsAK0cEShPsPD9HY6rWDGVLRvWYvKXHRQXcIOcdQY97ogwKF iIvtXyF3GuUydVOA8zuoCik0V2BBL6q37IEGoy/UbMGTaqrVC3SBG18jaSBj4wFFmbKc iMTqhOxIOpwWY9J4KGhf0GJQOQWo72XTBr7+32WrViOR+a+1Ql/lC+NO3ytviAm6rAEq UoOnrpCT8OWtsARYtx5YFf2cQFS7xboL8uKIxR0Q929JPuhQDlPomd9ouDorz8zP9Fei CSlKUr8xMwzr+mTGnCge6j/UrzFgwzX8b2WV3ubYylry0O+5UwXRNDg2qFc5tBHU7aKJ si9g==
X-Received: by 10.66.199.40 with SMTP id jh8mr37572355pac.123.1446602706635; Tue, 03 Nov 2015 18:05:06 -0800 (PST)
Received: from ?IPv6:2001:c40:0:3032:3c7e:d05:2025:9fc5? (t20010c40000030323c7e0d0520259fc5.v6.meeting.ietf94.jp. [2001:c40:0:3032:3c7e:d05:2025:9fc5]) by smtp.googlemail.com with ESMTPSA id c3sm31901215pbu.24.2015.11.03.18.05.04 for <94attendees@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Nov 2015 18:05:05 -0800 (PST)
From: Alexandre Petrescu <alexandru.petrescu@gmail.com>
X-Google-Original-From: Alexandre Petrescu <alexandre.petrescu@cea.fr>
To: 94attendees@ietf.org
References: <20151102055200.GI31730@cisco.com> <7iio5k5kpz.wl-jch@pps.univ-paris-diderot.fr> <5136.1446543935@dooku.sandelman.ca> <CAL0WyWyTiuMP2gXKaM+oLyY2MzHU4Bw-NpaBZSfLLJntQFeWXA@mail.gmail.com> <20151103211649.4A0CD3BBF89A@rock.dv.isc.org>
Message-ID: <563967CE.2040206@cea.fr>
Date: Wed, 04 Nov 2015 11:05:02 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151103211649.4A0CD3BBF89A@rock.dv.isc.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/94attendees/pMf3HK5rJpT7E9mglBhUNUdPFUQ>
X-Mailman-Approved-At: Wed, 04 Nov 2015 15:19:00 -0800
Subject: Re: [94attendees] [homenet] IPv6 Prefix delegation on IETF network, please ?
X-BeenThere: 94attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 94 attendees that have opted in on this list. " <94attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/94attendees>, <mailto:94attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/94attendees/>
List-Post: <mailto:94attendees@ietf.org>
List-Help: <mailto:94attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/94attendees>, <mailto:94attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2015 02:05:08 -0000

Hi,

Le 04/11/2015 06:16, Mark Andrews a écrit :
>
> In message <CAL0WyWyTiuMP2gXKaM+oLyY2MzHU4Bw-NpaBZSfLLJntQFeWXA@mail.gmail.com>,
>   Gabriel Kerneis writes:
>> On Tue, Nov 3, 2015 at 10:45 AM, Michael Richardson <mcr+ietf@sandelman.ca>
>> wrote:
>>
>>> Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>>>> However, a number of ISPs (including the IETF, it seems) do not allow
>>>> prefix delegation.
>>>
>>> No, that's not correct.
>>
>>
>> The "including the IETF" aside might not be correct, but the sentence as a
>> whole is correct.
>>
>>
>>>> Do we ignore the problem
>>>
>>> It's not a problem.
>>>
>>
>> Having dealt with several (French and British) ISPs providing modems with
>> crappy firmwares, let me assure you that this is a very real problem.
>>
>> Gabriel
>
> Different problems.
>
> Getting the IETF's DHCPv6 servers and routers configured to serve
> and support PD requests is a very different problem to getting CPE
> devices to properly support PD.
>
> Getting DHCPv6 servers to respond to PD requests is easy.  Integrating
> that with the routers is harder.  This is having the IETF simulate
> being a ISP with wired home customers (assuming a wired connection)
> compared to being a hotspot provider which it currently is.  If we
> want to do it over wireless as well then the IETF needs to simulate
> being a WISP.
>
> Now doing a demo network w/o integrating the DHCPv6 servers and the
> routers is also possible but requires a different planning.

This sounds like a sensible option.

I wonder whether the existing DHCPv4 deployment at IETF uses DHCPv4 
Relays or not?

I offer as a tester for next IETF.

Testing is very easy.  Download some DHCPv6-PD capable client and run 
it.  It will not install anything on the computer, just show whether or 
not it receives a prefix.

Alex

>
> Providing CTMS and similar is yet again a different problem.  We
> have the vendors in the IETF that can supply all the gear with
> suitable planning.  They have brought this sort of gear for
> Bit-and-Bites in the past.
>
> So what is the scope of the request and what needs to be simulated?
>
> Mark
>