Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Philip Homburg <pch-6man@u-1.phicoh.com> Tue, 31 May 2011 10:40 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 245A4E0784 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 03:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.435
X-Spam-Level:
X-Spam-Status: No, score=-8.435 tagged_above=-999 required=5 tests=[AWL=0.164, 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 g2qbeZGjvWqK for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 03:40:35 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id CCD82E076F for <ipv6@ietf.org>; Tue, 31 May 2011 03:40:34 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #55) id m1QRMNF-0001ipC; Tue, 31 May 2011 12:40:33 +0200
Message-Id: <m1QRMNF-0001ipC@stereo.hq.phicoh.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
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> <alpine.DEB.2.00.1105311225350.13754@uplift.swm.pp.se>
In-reply-to: Your message of "Tue, 31 May 2011 12:28:01 +0200 (CEST) ." <alpine.DEB.2.00.1105311225350.13754@uplift.swm.pp.se>
Date: Tue, 31 May 2011 12:40:32 +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:40:39 -0000

In your letter dated Tue, 31 May 2011 12:28:01 +0200 (CEST) you wrote:
>On Tue, 31 May 2011, Philip Homburg wrote:
>> No, ND is more clever than that. All traffic between prefixes that are 
>> on-link goes directly between the hosts. Even when the prefix is 
>> off-link it is possible for the router the send a redirect ICMP to cause 
>> further traffic to be directly between the hosts.
>
>I hope there is a recommendation in the standard to have a knob to turn 
>this off? With security functions like forced-forwarding and alike, I'd 
>definitely not want the hosts to try to communicate directly between each 
>other.

A prefix only becomes on-link if there is a prefix option that says so.

Of course, absent secure ND, any host can fake a redirect ICMP. So you either
SEND or L2 devices that filter ICMPs. But you need that anyhow.

>I was under the impression that if I don't announce an on-link prefix at 
>all, and just do DHCPv6, there hosts would not try to communicate with 
>each other directly (ie there is no routing to support this function). 
>You're saying my presumption is not true?

If the prefix is not announced as on-link then hosts have to send their
packets to a default router until they get a redirect.

>Why would a host try to do ND for something that is not on-link according 
>to its routing table?

I was not implying that hosts would that without a router announcing the 
prefix as on-link. I just wanted to make clear that IPv6 *supports* direct
communication between hosts that use addresses from different prefixes.