Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Mohacsi Janos <mohacsi@niif.hu> Tue, 31 May 2011 09:21 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 89AF3E0817 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 02:21:10 -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 q8cxJlFoeF+M for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 02:21:10 -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 B7E5CE0736 for <ipv6@ietf.org>; Tue, 31 May 2011 02:21:09 -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 9B69C874F7; Tue, 31 May 2011 11:21:07 +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 pk2k9vEGHoAE; Tue, 31 May 2011 11:21:05 +0200 (CEST)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id 66061874DF; Tue, 31 May 2011 11:21:05 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id 6388F874CF; Tue, 31 May 2011 11:21:05 +0200 (CEST)
Date: Tue, 31 May 2011 11:21:05 +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: <62797F6E-20DF-4038-A29A-1FDB0A94C678@equinux.de>
Message-ID: <alpine.BSF.2.00.1105311115590.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>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
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 09:21:10 -0000

On Tue, 31 May 2011, Markus Hanauska wrote:

>
> On 2011-05-30, at 22:27 , Philip Homburg wrote:
>
>> If you are really worried about this, then I guess you can also just assign
>> two prefixes to a single link and use one for SLAAC and the other for DHCPv6.
>
> Of course this is possible, but this also means, that a node not doing 
> DHCPv6 (because it does not support it or because it is disabled on the 
> node), will only get an address of the SLAAC prefix and thus has to go 
> to through the network router to have its packets routed the other one. 
> So even though both nodes are on the same physical network, all traffic 
> has to pass through a router, instead of being exchanged directly 
> between the two nodes. This means a lot of unnecessary load for the this 
> router to route "local traffic".

Why would you do assign different prefixes via SLAAC and DHCPv6?

This is similar to the problem of IPv4 when you configured secondary 
addresses (from different subnet) to an interface.

Best Regards,
 		Janos Mohacsi