Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Mohacsi Janos <mohacsi@niif.hu> Tue, 31 May 2011 11:10 UTC

Return-Path: <mohacsi@niif.hu>
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 33B89E0825 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 04:10:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.004
X-Spam-Level:
X-Spam-Status: No, score=-0.004 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xkYcWqL2TEyn for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 04:10:02 -0700 (PDT)
Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by ietfa.amsl.com (Postfix) with ESMTP id 52743E07A1 for <ipv6@ietf.org>; Tue, 31 May 2011 04:10:02 -0700 (PDT)
Received: from bolha.lvs.iif.hu (bolha.lvs.iif.hu [193.225.14.181]) by mail.ki.iif.hu (Postfix) with ESMTP id CFE7F87503; Tue, 31 May 2011 13:10:00 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at bolha.lvs.iif.hu
Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by bolha.lvs.iif.hu (bolha.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id krRIMbWvoEcK; Tue, 31 May 2011 13:09:56 +0200 (CEST)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id EFDDD874E5; Tue, 31 May 2011 13:09:55 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id EB452874CD; Tue, 31 May 2011 13:09:55 +0200 (CEST)
Date: Tue, 31 May 2011 13:09:55 +0200
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@mignon.ki.iif.hu
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
In-Reply-To: <805C1C3B-616E-4B2C-8774-5890E79BA13B@equinux.de>
Message-ID: <alpine.BSF.2.00.1105311301170.63146@mignon.ki.iif.hu>
References: <C9F53B85.11BE93%john_brzozowski@cable.comcast.com> <201105232010.p4NKAV9X012654@cichlid.raleigh.ibm.com> <53E999C4-E50D-49C9-9B02-8AD7B5641905@gmail.com> <BANLkTinByCkcvd6=wLE6=9h1xLX16AhPVQ@mail.gmail.com> <201105232111.p4NLBScJ013180@cichlid.raleigh.ibm.com> <20110524072631.737ee12c@opy.nosense.org> <3044C560-F46C-477A-BD87-DF252F689FAB@equinux.de> <m1QR93e-0001IXC@stereo.hq.phicoh.net> <62797F6E-20DF-4038-A29A-1FDB0A94C678@equinux.de> <m1QRL7I-0001h2C@stereo.hq.phicoh.net> <075E5D04-AF53-4DE9-9F45-432D96EBB03F@equinux.de> <alpine.BSF.2.00.1105311202520.63146@mignon.ki.iif.hu> <805C1C3B-616E-4B2C-8774-5890E79BA13B@equinux.de>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 31 May 2011 11:10:07 -0000

On Tue, 31 May 2011, Markus Hanauska wrote:

>
> On 2011-05-31, at 12:10 , Mohacsi Janos wrote:
>
>> If you get /64 and you need more subnets from your provider then probably you asked something wrong.
>
> Or you have the wrong provider...

I agree.

> but if this is the only provider 
> available in your area, that can offer you a symmetric 100 MBit/s fibre 
> connection for business purposes, what are you going to do? Move your 
> whole company elsewhere? I don't think so. Sometimes it is also a 
> question of money; you can have a larger prefix, if you are willing to 
> pay ten times the price, which is not acceptable for every company in 
> the world.

You have to explain your provider to assign more otherwise they are not 
following the registration policy documents of RIRs e.g Section 5.3 
and 5.4.x
http://www.ripe.net/ripe/docs/ripe-512


>
>> What collision? You should use 'u' bit accrdingly:
>> 1 - if automaticaly assigned
>> 0 - if manually assigned.
>
> But it is also 0 for SLAAC addresses w/ privacy extension and those are automatically assigned, in example.


You can argument for change in the RFC 4941 revision.

Best Regards,
 		Janos Mohacsi