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

SM <sm@resistor.net> Thu, 21 January 2010 19:44 UTC

Return-Path: <sm@resistor.net>
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 5A00D3A67E3 for <ietf@core3.amsl.com>; Thu, 21 Jan 2010 11:44:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 HR7CJ3X-zI4v for <ietf@core3.amsl.com>; Thu, 21 Jan 2010 11:44:08 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 432353A67A6 for <ietf@ietf.org>; Thu, 21 Jan 2010 11:44:08 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.4/8.14.4) with ESMTP id o0LJhGIk000357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jan 2010 11:43:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1264103042; x=1264189442; bh=GSCSMen3rh8fEbHcJR4AiDpmH7gJwDlxiMGNWDjyAfg=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=RqM/kivqHn0EHUZjVqN25sfh/8VDejYRF/o6UejjZn/uIli9FG0s36RAMBMu//iaO oR61ZXmoIeLG9M+vNglU3cEIFTJODNUHu/TGWCKGJubeetulkD2i+KlNNoNXQV9o9H NNhRt8Kn+qNglYbBLhAOhPdOq3egWkJRadah5z44=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=bLuRatnWnNo5zeZo9ZLwh3NJWhTpw7neOgET4OAxsf3tF2SnXNC+jrRwMTZILCBtt 3IqhEfMOStmfVFMZRXX6xpxQf4ggvAtUM3tCz2ETWcWvwSp1cpFGv9EykH5SJJ8zE7x 29aNrern5MXSLBtAo62IJITX6MX+XXfBySr4mOk=
Message-Id: <6.2.5.6.2.20100121092706.080ebe38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 21 Jan 2010 11:42:20 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: draft-allbery-afs-srv-records (DNS SRV Resource Records for AFS) to Proposed Standard
In-Reply-To: <20100108152851.7AB5A3A6800@core3.amsl.com>
References: <20100108152851.7AB5A3A6800@core3.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: 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, 21 Jan 2010 19:44:09 -0000

At 07:28 08-01-10, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>
>- 'DNS SRV Resource Records for AFS '
>    <draft-allbery-afs-srv-records-03.txt> as a Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send substantive comments to the

In Section 4:

   "<proto> MUST be "udp" for the current AFS protocol, which uses Rx
    over UDP."

It would be better to specify what the current AFS protocol is.

   "As specified in [RFC1034], DNS RRs MUST be discarded after their TTL,
    and the DNS query repeated."

RFC 1034 actually says:

   "The TTL describes how long a RR can be cached before it should be 
discarded."

RFC 2782 refers to RFC 1035.  The same reference could be used in 
this I-D.  I suggest changing that paragraph to:

   The time-to-live (TTL) is defined in RFC 1035.  The TTL describes how long
   the SRV record can be cached before it should be discarded.  Any information
   derived from the SRV record, such as preference ranks, MUST be 
discarded when the
   DNS SRV RR is expired.

Quoting the last paragraph of that section:

   "AFS clients MAY remember which targets are inaccessible by that
    client and ignore those targets when determining which server to
    contact first.  Clients which do this SHOULD have a mechanism to
    retry targets which were previously inaccessible and reconsider them
    according to their priority and weight if they become accessible
    again."

In the "TTL" paragraph, it is specified that any information derived 
from the SRV record must be discarded.  That would include the target.

In the example in Section 6:

       "afsdb1               A     172.30.79.10
        afsdb2               A     172.30.79.11
        afsdb3               A     172.30.79.12"

IPv4 addresses from TEST-NET-1 (RFC 5737) can be used:

        afsdb1               A     192.0.2.10
        afsdb2               A     192.0.2.11
        afsdb3               A     192.0.2.12

Please add an IANA Considerations section that says:

   This document contains no IANA actions.

Regards,
-sm