[apps-discuss] more editing questions

Anthony Bryan <anthonybryan@gmail.com> Sun, 03 March 2013 08:41 UTC

Return-Path: <anthonybryan@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1304E21F8628 for <apps-discuss@ietfa.amsl.com>; Sun, 3 Mar 2013 00:41:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.297
X-Spam-Level:
X-Spam-Status: No, score=-3.297 tagged_above=-999 required=5 tests=[AWL=0.302, 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 LYfUvN2AjRa5 for <apps-discuss@ietfa.amsl.com>; Sun, 3 Mar 2013 00:41:52 -0800 (PST)
Received: from mail-qe0-f52.google.com (mail-qe0-f52.google.com [209.85.128.52]) by ietfa.amsl.com (Postfix) with ESMTP id 4943F21F8626 for <apps-discuss@ietf.org>; Sun, 3 Mar 2013 00:41:52 -0800 (PST)
Received: by mail-qe0-f52.google.com with SMTP id s14so2895365qeb.11 for <apps-discuss@ietf.org>; Sun, 03 Mar 2013 00:41:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=wCctMRquwvN1BnhZFWBmzYSnQ2gsWbSliMjXtOw64r8=; b=vmuSjB6SE+rxRajwUjzzGPvUEs+unJX6X8tgeUo9twd23mhfIEZdU8muwIv9eCfFC+ a34/rr2c0MpL1Q425XBbjzPklqM1aMbHCinS5ZJ+kxsPJCT8d67CyEGNm5oVwn2ibW5V JanHLwr/IWdcdBrDuUnMq6+zuK+6Gzbmer8jmGfNHQUf47dCTmA+40aX/Tnw5x5t8Lv8 EK5ehsXXF0SyVVnnY7jc/JYeE51SOiDcb3lA/KBJkRxlF42PtNLxeMFcowNUOIHKCZDI r/4vwzwAiYcgGFKICdS8boLHh/weNk4AF5QUd/w+/fWjf0X1JoluzLeI3L53ClP54UhX 67rw==
MIME-Version: 1.0
X-Received: by 10.49.127.139 with SMTP id ng11mr27626679qeb.54.1362300111853; Sun, 03 Mar 2013 00:41:51 -0800 (PST)
Received: by 10.49.71.140 with HTTP; Sun, 3 Mar 2013 00:41:51 -0800 (PST)
Date: Sun, 03 Mar 2013 03:41:51 -0500
Message-ID: <CANqTPehTmYfwW4yASS7QWCtRMbHY-Vu5+zWNhb3C49ZeUsEbgA@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [apps-discuss] more editing questions
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Mar 2013 08:41:53 -0000

RFC 5854 describes the Metalink/XML format but it only has the barest normative
requirements for clients - but not all, hence this new draft on clients.

http://tools.ietf.org/html/draft-bryan-metalink-client

what's the best way to call attention to these, just quote them outright?

"RFC 5854 introduced these requirements for Metalink clients, which
are still in effect..."?

we're not updating any requirements from RFC 5854, just adding more,
but we'd like them all in the same place.


we also have the FTP RANG command to specify a byte range. we use this
with the HASH command, for partial file hashing.

inside the RANG ID, we specify how it works with RETR & STOR (section
4) as well. RANG is well solidified on it's own, but we're still
working on section 4.

my question is, should we split section 4 into a separate ID so
there's just RANG on it's own, with HASH and a "RANG with RETR/STOR"
both depending on it. that seems like it would make RANG on it's own
more simple.

http://tools.ietf.org/html/draft-bryan-ftp-range
http://tools.ietf.org/html/draft-bryan-ftpext-hash

thanks,
--
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads