IETF Logo Mail Archive

Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Wes Beebee <wbeebee@cisco.com> Fri, 13 May 2011 18:43 UTC

Return-Path: <wbeebee@cisco.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 BDB6EE0862 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 11:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.135
X-Spam-Level:
X-Spam-Status: No, score=-7.135 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 T6DqrZfsgqEK for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 11:43:39 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 7CA0EE072D for <ipv6@ietf.org>; Fri, 13 May 2011 11:43:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=wbeebee@cisco.com; l=2817; q=dns/txt; s=iport; t=1305312214; x=1306521814; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=iQD9wb0wVMGy2APNzmE2qBOcHDh+97nIPB4HKWujrH0=; b=ccArV/TU/9MDRpA+oIodMe1IziE7Y/HQSobrSkAeLB0Bj1svcoJwWPpm a7OWIPoYHYrC8uMF37X8TNa0HvwoFEibFd4XIlVT2lmgd+vpylUMSMzzv zjuY27DnotIWLlL2Wg9SsMvYdQKKp9V33/REoGa4DS0+rtjb3RUpUVDsw o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmMGABd7zU2tJXG9/2dsb2JhbACCZIY7nAZjAneIcJ51ngGGFQSQBoQ4hmmDbQ
X-IronPort-AV: E=Sophos; i="4.64,365,1301875200"; d="scan'208,217"; a="315195121"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-3.cisco.com with ESMTP; 13 May 2011 18:43:33 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p4DIhXEg022877; Fri, 13 May 2011 18:43:33 GMT
Received: from xmb-rcd-201.cisco.com ([72.163.62.208]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 13 May 2011 13:43:33 -0500
Received: from 161.44.175.134 ([161.44.175.134]) by XMB-RCD-201.cisco.com ([72.163.62.208]) with Microsoft Exchange Server HTTP-DAV ; Fri, 13 May 2011 18:43:33 +0000
User-Agent: Microsoft-Entourage/12.29.0.110113
Date: Fri, 13 May 2011 14:43:30 -0400
Subject: Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
From: Wes Beebee <wbeebee@cisco.com>
To: Cameron Byrne <cb.list6@gmail.com>, james woodyatt <jhw@apple.com>
Message-ID: <C9F2F412.12C414%wbeebee@cisco.com>
Thread-Topic: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Index: AcwRnac5w5Xz8+FqCk6P5D069MQrlQ==
In-Reply-To: <BANLkTikXCOy48EOT65Y+Wa2pYdQjcrOS5g@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3388142610_1328840"
X-OriginalArrivalTime: 13 May 2011 18:43:33.0112 (UTC) FILETIME=[A9144F80:01CC119D]
Cc: 6MAN Working Group <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: Fri, 13 May 2011 18:43:40 -0000

> I do not believe there needs to be special wording for mobile

Or for any other specific deployment for that matter.  The reason I
mentioned cable is because many popular operating system-based hosts as well
as specific devices have to be able to operate in a cable environment ­ and
the operational reality is that it is a MUST for all of them.  However,
since there are other, closed, controlled environments where DHCPv6 may not
be necessary, SHOULD is the perfect level to cover all of the deployment
environments.  SHOULD means that you have to follow it unless you have a
good case why not (see RFC 2119 below):

3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course

- Wes

v2.23.0 | Report a Bug | By Email