Re: RA "requires" DHCPv6 ?

Karl Auer <kauer@biplane.com.au> Sat, 31 March 2012 12:12 UTC

Return-Path: <kauer@biplane.com.au>
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 7070C21F848A for <ipv6@ietfa.amsl.com>; Sat, 31 Mar 2012 05:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V2lfEUcs0RSk for <ipv6@ietfa.amsl.com>; Sat, 31 Mar 2012 05:12:11 -0700 (PDT)
Received: from ipmail04.adl6.internode.on.net (unknown [IPv6:2001:44b8:8060:ff02:300:1:6:4]) by ietfa.amsl.com (Postfix) with ESMTP id 8119921F8478 for <ipv6@ietf.org>; Sat, 31 Mar 2012 05:12:10 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBACj0dk+WZX+7/2dsb2JhbAANNoVUtkcBAQEEI2YLGCoCAlcGE7URig2QBIEYBKEXh3Q
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.202]) ([150.101.127.187]) by ipmail04.adl6.internode.on.net with ESMTP; 31 Mar 2012 22:42:08 +1030
Subject: Re: RA "requires" DHCPv6 ?
From: Karl Auer <kauer@biplane.com.au>
To: "ipv6@ietf.org" <ipv6@ietf.org>
In-Reply-To: <CB9D3D7B.2263B%hesham@elevatemobile.com>
References: <CB9D3D7B.2263B%hesham@elevatemobile.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-AIlDD9+d0xExncbKQUvB"
Date: Sat, 31 Mar 2012 23:12:05 +1100
Message-ID: <1333195925.11943.10.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3
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: Sat, 31 Mar 2012 12:12:12 -0000

On Sat, 2012-03-31 at 23:03 +1100, Hesham Soliman wrote:
> >There was a bunch of stuff about the M and O flags in RFC2462, almost
> >all of which was removed in RFC4862. In RFC2462, the word
> >"should" (*not* capitalised) was used, along with phrases like "is to
> >be".
> 
> => "should" does not need to be capitalised to indicate that it's a
> keyword. It's a common misunderstanding.

Oh, I don't misunderstand that point. But reading RFC2462, and seeing
things like "is to be" and seeing how the word "should" was used in
context, I got the feeling that it was not being treated with the
respect it deserved - i.e., that sometimes it was not being used
prescriptively. In any case, that's all gone from RFC4862, which
obsoletes RFC2462. Leaving me still wondering.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer

GPG fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017
Old fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687