Re: [ftpext] RFC Errata for consideration
Anthony Bryan <anthonybryan@gmail.com> Tue, 03 August 2010 22:29 UTC
Return-Path: <anthonybryan@gmail.com>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 147983A69E6 for <ftpext@core3.amsl.com>; Tue, 3 Aug 2010 15:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level:
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118, 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 z9gHV04QTaNz for <ftpext@core3.amsl.com>; Tue, 3 Aug 2010 15:29:04 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id EAC583A6B39 for <ftpext@ietf.org>; Tue, 3 Aug 2010 15:29:03 -0700 (PDT)
Received: by iwn3 with SMTP id 3so1527421iwn.31 for <ftpext@ietf.org>; Tue, 03 Aug 2010 15:29:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=FIocsKnWKZdJdZm7CzKddq7qH7u6vUicA+h1nvmHpMc=; b=NqU+EETrngUYrOnFAYOnZQXP+P8v1+q4PCmeu4CYU4Gr+wz6KeWHgmHFsz02xhv56a wxBVLGhMClzpvrIUklmxFy1F6+qkQZirWJsBWL8Unw3VY46icnIn1wdo146PSsMWLv9R FAMeB1WOugnPupnbehK9gvh/vqtrls8rqxRzY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=XA/jGmzNX8LI6y2fEZcnM8cyD2aO/r6th7SqdutQFJtU4ByOMy7N8aCa49IMGWxVKk aRcEfipT87ENh9eE+n9VFNZj6xBGSgI1rTFjKnAcmV2w138FklXYXpYqkTe3b287NCwA swao9tJ3eYnVa6M3OtaLwcOKkp0z8MLOPoMk0=
MIME-Version: 1.0
Received: by 10.231.59.212 with SMTP id m20mr9369686ibh.130.1280874571192; Tue, 03 Aug 2010 15:29:31 -0700 (PDT)
Received: by 10.231.159.143 with HTTP; Tue, 3 Aug 2010 15:29:31 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1007301540330.15461@iskra.ottix.net>
References: <Pine.LNX.4.64.1007301540330.15461@iskra.ottix.net>
Date: Tue, 03 Aug 2010 18:29:31 -0400
Message-ID: <AANLkTimqJxcTzH2BQM+NhGixM5Z+kpSVnUBauQSiqftJ@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: "William F. Maton" <wmaton@ottix.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] RFC Errata for consideration
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2010 22:29:05 -0000
On Fri, Jul 30, 2010 at 3:43 PM, William F. Maton <wmaton@ottix.net> wrote: > > If this WG gains traction, would RFC errata (such as the ones I came > across for RFC 3659) also be dealt with as part of a charter? while on the subject of errata, I've come across a few in RFC 959 that I'll be posting for verification & discussion with the group. most are editorial though. here's one: RFC 959 type The data representation type used for data transfer and storage. Type implies certain transformations between the time of data storage and data transfer. The representation types defined in FTP are described in the Section on Establishing Data Connections. Errata The representation types defined in FTP are described in Section 3.1, Data Representation and Storage, or more specifically 3.1.1, Data Types. They don't seem to be described in 3.2, Establishing Data Connections. also, RFC 1123 contains a number of updates to RFC 959 (& others). (presumably, "Updates: XXXX" wasn't in use in 1989?) should this be reported as errata to RFC 1123? -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] )) Easier, More Reliable, Self Healing Downloads
- [ftpext] RFC Errata for consideration William F. Maton
- Re: [ftpext] RFC Errata for consideration Anthony Bryan
- Re: [ftpext] RFC Errata for consideration Anthony Bryan
- Re: [ftpext] RFC Errata for consideration William F. Maton
- Re: [ftpext] RFC Errata for consideration Anthony Bryan
- Re: [ftpext] RFC Errata for consideration William F. Maton
- Re: [ftpext] RFC Errata for consideration Anthony Bryan
- Re: [ftpext] RFC Errata for consideration William F. Maton
- Re: [ftpext] RFC Errata for consideration Anthony Bryan
- Re: [ftpext] RFC Errata for consideration William F. Maton