IETF Logo Mail Archive

Re: [v6ops] Bar BoF on a 6to4 replacement?

Gert Doering <gert@space.net> Thu, 13 November 2014 08:15 UTC

Return-Path: <gert@Space.Net>
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 82AD91A3B9E for <v6ops@ietfa.amsl.com>; Thu, 13 Nov 2014 00:15:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level:
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.594] 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 ajUYiuvEorBl for <v6ops@ietfa.amsl.com>; Thu, 13 Nov 2014 00:15:51 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 881891A1B8B for <v6ops@ietf.org>; Thu, 13 Nov 2014 00:15:50 -0800 (PST)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 6B470631B8 for <v6ops@ietf.org>; Thu, 13 Nov 2014 09:15:49 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 2B74B631A1 for <v6ops@ietf.org>; Thu, 13 Nov 2014 09:15:49 +0100 (CET)
Received: (qmail 7464 invoked by uid 1007); 13 Nov 2014 09:15:49 +0100
Date: Thu, 13 Nov 2014 09:15:49 +0100
From: Gert Doering <gert@space.net>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <20141113081549.GR31092@Space.Net>
References: <5454119C.3090601@network-heretics.com> <2134F8430051B64F815C691A62D9831832D75F09@XCH-BLV-504.nw.nos.boeing.com> <686FABB5-9A9E-4D0C-BD1A-19CA02A9C247@muada.com> <2134F8430051B64F815C691A62D9831832D76378@XCH-BLV-504.nw.nos.boeing.com> <AD4F3B9C-18D2-4B6F-867C-423368D6F489@muada.com> <4C77BAB8-38FD-4830-B779-E24586EB9275@delong.com> <5458294D.9000502@massar.ch> <64F92F49-4A31-4268-99D3-8A482E95735F@delong.com> <EB80E1B1-335F-45CA-BAFA-C2DB1BA58F1A@muada.com> <54643D0B.4070208@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <54643D0B.4070208@gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/O9A_8LgC3LZSDj43Eq7Tu-mL99c
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Bar BoF on a 6to4 replacement?
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: <http://www.ietf.org/mail-archive/web/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: Thu, 13 Nov 2014 08:15:53 -0000

Hi,

On Thu, Nov 13, 2014 at 06:09:31AM +0100, Alexandru Petrescu wrote:
> > - Is requiring DHCPv6 (the prefix delegation client role) problematic?
> 
> I guess it is problematic.  I am not aware of any operator of DSL or 
> cellular links that offers DHCPv6 Prefix Delegation service (a Server 
> that replies positively to requests for prefixes).

DHCPv6-PD is the standard method to hand out prefixes on DSL lines here
in DE.  ("What else could you use?").

So, now you are aware of DSL operators that do this, like "Deutsche Telekom".

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.46.0 | Report a Bug | By Email | System Status