IETF Logo Mail Archive

Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 23 May 2011 21:52 UTC

Return-Path: <brian.e.carpenter@gmail.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 4DA5EE07B8 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2011 14:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.585
X-Spam-Level:
X-Spam-Status: No, score=-103.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 LigdVR3r2fkU for <ipv6@ietfa.amsl.com>; Mon, 23 May 2011 14:52:03 -0700 (PDT)
Received: from mail-px0-f179.google.com (mail-px0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id BAB7DE069C for <ipv6@ietf.org>; Mon, 23 May 2011 14:52:03 -0700 (PDT)
Received: by pxi2 with SMTP id 2so3636419pxi.38 for <ipv6@ietf.org>; Mon, 23 May 2011 14:52:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m9SeFFEmrGDVvKsDi3EPvk0ugrWkEm00ByQqK92AuUI=; b=XnK3FlUdsryq88UNU2H8/3YlVG66Sfo9q9wPwLaKzwDiLuvpDlBCuwa7HMQpeDjbdD JFElmDL5OVjSVCwIrs32CfGkVUIUt9MWbVs3mtfWTv5FfrGD9PI/gGx59XURIFZHS7DX 4LqaYvY27EemYexcDcCLX7gpMw+Ow7iQ1xa20=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=ZGaIwHsyGbVG8UnCZZOMMJAR2dKYrArqLuR+0C48qRuSDmkyaQOVzChMvvca0QWJRc JdlPO/G4nYIQCWGBn6tBcRQ9JTAwVHgk0WRDXTjtHCxyysOBS8nWjxJgm+4vLPHzr5Tm WEZGzZqezNMFkmRKL2vh6OxKQWukchGcutfnY=
Received: by 10.142.149.15 with SMTP id w15mr887918wfd.325.1306187523315; Mon, 23 May 2011 14:52:03 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id k7sm6161796wfa.2.2011.05.23.14.52.00 (version=SSLv3 cipher=OTHER); Mon, 23 May 2011 14:52:02 -0700 (PDT)
Message-ID: <4DDAD6FE.2030807@gmail.com>
Date: Tue, 24 May 2011 09:51:58 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
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>
In-Reply-To: <201105232111.p4NLBScJ013180@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
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, 23 May 2011 21:52:04 -0000

Thomas,

On 2011-05-24 09:11, Thomas Narten wrote:
> Christopher Morrow <christopher.morrow@gmail.com> writes:
> 
>> one gotcha with 'dhcp only' is perhaps folks mean: "slaac to signal v6
>> is on-net, but require full config from a dhcpv6 server".
>> How does a host know that v6 is available otherwise? (this may be why
>> someone said "you don't really want to do that..')
> 
> Well, if I could go back in time, I would never have defined the M&O
> bits at all.
> 
> Just say that at startup time, invoke SLAAC & DHCPv6 both. Then use
> whatever is available. That would have been simple and
> predictable. (And avoided 10GB of mailing list discussion!)
> 
> (Hmm, maybe I should just write such a spec now, 

Please do. It is one of the gaps identified in RFC 5887, btw.

   Brian


given the M&O bit
> definitions are in the twilight zone anyway... Discussion of what to
> do with them was effectively removed from the last revisions of the
> SLAAC documents, so now there is no clear guidance on how to process
> them. The IETF at its finest...)
> 
> Thomas
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email