Re: moving DHCPv6 to SHOULD

RJ Atkinson <rja.lists@gmail.com> Fri, 13 May 2011 23:12 UTC

Return-Path: <rja.lists@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 68A8CE08E1 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 16:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 4exsMf+SeL3D for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 16:12:54 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id B9F15E07E9 for <ipv6@ietf.org>; Fri, 13 May 2011 16:12:54 -0700 (PDT)
Received: by qyk29 with SMTP id 29so628714qyk.10 for <ipv6@ietf.org>; Fri, 13 May 2011 16:12:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=3B9g8KYI2YXxuTrh6shL3RYGni5FoHRyFr0fi99z2k4=; b=Lim+IQoDMi0hVRNu1yNJvk347We269wQ4cLbOY1H0CVF59Lcyjyzdaw2aQ6MW579In PgZzufbu+/DMCZTTY+bcLaqGiTeZsBxwJaH/mPIW6WBCOU1XoTogyvJi1Cdk3K8M5AMA /ksY8+qzRNqQmsS5U1iK5qDLU3vpcMvL4zG9s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=PYYrHC8W26mBHyfwF2RmYIHHR2kgkK8BDXBWIYwZFrLEM8L6tAEAjQZk3zuykzWsEw u6bWcwMPUNGi6nzY9SdxRiqwwkP3mhcdHYFmaDNTIPZ9yYHimu/2hBAbZxSf0oN0GLBm G3DYUpjSzHjIP7pPz3XdCZ+3rKHfewIQ6s/3Q=
Received: by 10.224.113.81 with SMTP id z17mr1622399qap.158.1305328374134; Fri, 13 May 2011 16:12:54 -0700 (PDT)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id s16sm1649934qco.13.2011.05.13.16.12.52 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 May 2011 16:12:53 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: moving DHCPv6 to SHOULD
Date: Fri, 13 May 2011 19:12:51 -0400
Message-Id: <A527AD2B-7D09-4E48-8C50-AEB265553E5F@gmail.com>
To: ipv6@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
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 23:12:55 -0000

I support moving DHCPv6 to SHOULD instead of MAY.

I like Bob Hinden's proposed edit because it more neutrally
describes the wide range of deployment environments where
DHCPv6 might be a practical requirement, but I'm flexible
on the wording.

Ran