Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Philip Homburg <pch-6man@u-1.phicoh.com> Tue, 31 May 2011 10:35 UTC

Return-Path: <pch-b2B3A6689@u-1.phicoh.com>
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 90D4DE0784 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 03:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.407
X-Spam-Level:
X-Spam-Status: No, score=-8.407 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
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 p8cRb8m3+QG1 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 03:35:04 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id C8870E06AE for <ipv6@ietf.org>; Tue, 31 May 2011 03:35:03 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #55) id m1QRMHt-0001h3C; Tue, 31 May 2011 12:35:01 +0200
Message-Id: <m1QRMHt-0001h3C@stereo.hq.phicoh.net>
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
From: Philip Homburg <pch-6man@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
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>
In-reply-to: Your message of "Tue, 31 May 2011 11:54:57 +0200 ." <075E5D04-AF53-4DE9-9F45-432D96EBB03F@equinux.de>
Date: Tue, 31 May 2011 12:35:01 +0200
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 10:35:04 -0000

In your letter dated Tue, 31 May 2011 11:54:57 +0200 you wrote:
>I don't think this related to ND, is it? ICMP redirects also exist for =
>IPv4 and IPv4 doesn't know ND. I think only difference is that ICPMv6 =
>optionally allows an link layer address in the redirect message. How =
>good IPv6 implementations really support ICMPv6 redirects as of today is =
>another question.

The difference is that IPv4 has a model of one subnet per link. If you
get an ICMP for something that is not on your subnet, then it is best to 
ignore it. There is no problem get the link layer address: just ARP for it.

>My main problem with that approach is, that not everyone has a $5000++ =
>Cisco router available and the configuration capabilities of some more =
>inexpensive routers are quite limited; especially regarding IPv6, which =
>is still not mainstream (the majority of routers on the market still has =
>no IPv6 support at all). 

That's always that case if you want a configuration that is not mainstream:
you either have to buy a more expensive product that has more configuration
options or, in many cases, you can also use open source.