Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Philip Homburg <pch-6man@u-1.phicoh.com> Mon, 30 May 2011 11:04 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 0D092E078F for <ipv6@ietfa.amsl.com>; Mon, 30 May 2011 04:04:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level:
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[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 t+s-MRmrgAZ8 for <ipv6@ietfa.amsl.com>; Mon, 30 May 2011 04:04:34 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 0A997E069A for <ipv6@ietf.org>; Mon, 30 May 2011 04:04: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 m1QR0Gr-0001gzC; Mon, 30 May 2011 13:04:29 +0200
Message-Id: <m1QR0Gr-0001gzC@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>
In-reply-to: Your message of "Mon, 30 May 2011 12:47:19 +0200 ." <3044C560-F46C-477A-BD87-DF252F689FAB@equinux.de>
Date: Mon, 30 May 2011 13:04:29 +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: Mon, 30 May 2011 11:04:35 -0000

In your letter dated Mon, 30 May 2011 12:47:19 +0200 you wrote:
>Conflict resolution is not really necessary. What kind of conflict do you have
> to solve? If a network runs a DHCPv6 server that also hands out addresses, th
>e network operators probably want people to use DHCPv6 over SLAAC, so if a hos
>t obtains both, an interface address via SLAAC and DHCPv6, then it should pref
>er the DHCPv6 address for all outgoing traffic, since if it uses the SLAAC add
>ress, a router may not forward their traffic or a firewall may drop it. 

There is an 'A-bit' in the Prefix Information option. I'd suggest that 
operators use that bit to control the assignment of SLAAC addresses.