Re: [AFS3-std] Re: Last Call: draft-allbery-afs-srv-records (DNS SRV Resource Records for AFS) to Proposed Standard

Jeffrey Hutzelman <jhutz@cmu.edu> Thu, 04 February 2010 17:01 UTC

Return-Path: <jhutz@cmu.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ED573A68F9 for <ietf@core3.amsl.com>; Thu, 4 Feb 2010 09:01:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.297
X-Spam-Level:
X-Spam-Status: No, score=-6.297 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WhMvIXDVCzeC for <ietf@core3.amsl.com>; Thu, 4 Feb 2010 09:01:35 -0800 (PST)
Received: from smtp01.srv.cs.cmu.edu (SMTP01.SRV.CS.CMU.EDU [128.2.217.196]) by core3.amsl.com (Postfix) with ESMTP id 4C11E3A682A for <ietf@ietf.org>; Thu, 4 Feb 2010 09:01:35 -0800 (PST)
Received: from atlantis-home.pc.cs.cmu.edu (SIRIUS.FAC.CS.CMU.EDU [128.2.216.216]) (authenticated bits=0) by smtp01.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id o14H2Kao020177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Feb 2010 12:02:20 -0500 (EST)
Date: Thu, 04 Feb 2010 12:02:20 -0500
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Russ Allbery <rra@stanford.edu>, SM <sm@resistor.net>
Subject: Re: [AFS3-std] Re: Last Call: draft-allbery-afs-srv-records (DNS SRV Resource Records for AFS) to Proposed Standard
Message-ID: <074A3073AEF8CAE1D59D5470@atlantis.pc.cs.cmu.edu>
In-Reply-To: <87d40loq7u.fsf@windlord.stanford.edu>
References: <6.2.5.6.2.20100203140241.08c1a838@resistor.net> <87d40loq7u.fsf@windlord.stanford.edu>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.217.196
Cc: ietf@ietf.org, afs3-standardization@openafs.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2010 17:01:36 -0000

--On Wednesday, February 03, 2010 03:27:01 PM -0800 Russ Allbery 
<rra@stanford.edu> wrote:

> SM <sm@resistor.net> writes:
>> At 17:03 01-02-10, Russ Allbery wrote:
>
>>> Ah, thank you.  Changed to SHOULD on the assumption that the (pre-2119)
>>> language in RFC 1034 was intended to have roughly the same meaning.
>
>> "SHOULD" as a requirement first appeared in RFC 1122.  It does not
>> necessarily apply to RFCs published before RFC 2119.
>
> I guess I'm not clear on what you think the correct fix is.  I'm hesitant
> to use a lowercase "should" in a document that explicitly references RFC
> 2119, since then it's ambiguous what that is supposed to mean in terms of
> a standard requirement.

Agree.  I think we want to elevate this to SHOULD in this case, even if the 
original 1034 requirement was not that strong.  Clients failing to operate 
this way presents real operational problems for AFS cell administrators.  I 
would suggest a slight rewording, so that the present text cannot be read 
to imply that 1034 says "SHOULD" in the 2119 sense, when in fact it is 
somewhat more ambiguous.

-- Jeff