Re: Getting 2822 to Draft
John C Klensin <john+smtp@jck.com> Tue, 06 January 2004 16:57 UTC
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.10/8.12.8) with ESMTP id i06Gvlib050548 for <ietf-822-bks@above.proper.com>; Tue, 6 Jan 2004 08:57:47 -0800 (PST) (envelope-from owner-ietf-822@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.10/8.12.9/Submit) id i06Gvl5M050547 for ietf-822-bks; Tue, 6 Jan 2004 08:57:47 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-822@mail.imc.org using -f
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by above.proper.com (8.12.10/8.12.8) with ESMTP id i06Gvkib050542 for <ietf-822@imc.org>; Tue, 6 Jan 2004 08:57:46 -0800 (PST) (envelope-from john+smtp@jck.com)
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.10) id 1AduWZ-000AXg-00; Tue, 06 Jan 2004 11:57:47 -0500
Date: Tue, 06 Jan 2004 11:57:47 -0500
From: John C Klensin <john+smtp@jck.com>
To: ietf-822@imc.org
cc: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Getting 2822 to Draft
Message-ID: <53940111.1073390267@scan.jck.com>
In-Reply-To: <3FFAC10B.5050801@verizon.net>
References: <p06100723bc1aa0f50ab0@[10.0.2.4]> <3FFAC10B.5050801@verizon.net>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>
--On Tuesday, 06 January, 2004 09:07 -0500 Bruce Lilly <blilly@verizon.net> wrote: > Pete Resnick wrote: > >> >> So, for the new year I started thinking about getting 2822 to >> Draft. (Also, 3822 is coming up in the RFC numbers :-) ). >> I've gotten started on getting a new draft together. There >> are a small bunch of nits to fix; that I can handle. There's >> also an implementation report to write. On that I'd like to >> get some help. >> >> The one possible big thing has to do with the ABNF in 2822. >> Out of either altruism or insanity, some time ago Bruce >> Lilly had written up changes to the ABNF in 2822 to do some >> cool things. On the plus side, it seems to get rid of all of >> the [C]FWS shift-reduce conflicts, and it is already done. >> On the minus side, I don't know anyone (myself included) who >> has gone over it with a fine tooth comb, it is a significant >> number of ABNF changes, and it therefore might recycle us at >> Proposed. I am open to suggestions on this. >> >> Comments? >> >> pr > > As > a) 2821 and 2822 are closely related > and > b) there remain a few inconsistencies between 2821 and 2822 > is there a draft of a 2821 successor that can be reviewed at > the same time > as the draft of the 2822 successor? The editor of 2821 also made a new year's resolution, and actually opened the document last week to incorporate more of the changes that have been suggested. The bad news is that the working copy is in Word XP. I'm not a Word fan -- all of my other I-Ds are in XML or directly edited in ASCII-- but because, after the experiences with DRUMS, I wanted to be sure that I could identify, in the working text, the source and justification for all of the requested changes if any controversy arose. The difficulty is that converting a Word document with as many comments, change markup, internal cross references, etc., as that one now has is far beyond the scope of RFC 3285 (the attempt was what produced the "RFC 3285 considered harmful" thread on the IETF list a year or so ago). So, I'm reluctant to go through the rather painful conversion until I have a complete draft. If you would like to look directly at the Word form, or a PDF display of it (our experience has been that Word XP documents with extensive comments and markup don't get along with Mac Word either), I think that could be arranged within the next week or two. john
- Re: X-* header fields Lyndon Nerenberg
- Re: X-* header fields Lyndon Nerenberg
- Re: X-* header fields ned+ietf-822
- Re: X-* header fields ned+ietf-822
- Re: X-* header fields ned+ietf-822
- Re: X-* header fields Charles Lindsey
- Re: X-* header fields Bruce Lilly
- Re: X-* header fields Paul Smith
- Re: X-* header fields Bruce Lilly
- Re: X-* header fields Bruce Lilly
- Re: X-* header fields Paul Smith
- Re: X-* header fields Paul Smith
- Re: X-* header fields Paul Smith
- Re: X-* header fields Keith Moore
- Re: X-* header fields ned+ietf-822
- Re: X-* header fields Keith Moore
- Re: X-* header fields Al Costanzo
- Re: X-* header fields ned+ietf-822
- Re: X-* header fields Dave Crocker
- Re: X-* header fields ned+ietf-822
- Re: X-* header fields Keith Moore
- Re: X-* header fields ned+ietf-822
- Re: X-* header fields pbdlists
- Re: X-* header fields ned+ietf-822
- Re: X-* header fields Bruce Lilly
- Re: Getting 2822 to Draft Arnt Gulbrandsen
- Re: Getting 2822 to Draft Charles Lindsey
- Re: Getting 2822 to Draft Pete Resnick
- Re: X-* header fields Russ Allbery
- Re: X-* header fields ned+ietf-822
- Re: X-* header fields Charles Lindsey
- Re: X-* header fields Keith Moore
- Re: X-* header fields Russ Allbery
- Re: Getting 2822 to Draft John C Klensin
- Re: Getting 2822 to Draft Bruce Lilly
- Re: X-* header fields Keith Moore
- Re: X-* header fields (Was: Getting 2822 to Draft) Arnt Gulbrandsen
- Re: X-* header fields (Was: Getting 2822 to Draft) Paul Smith
- Re: X-* header fields Kai Henningsen
- Re: X-* header fields Bruce Lilly
- Re: X-* header fields (Was: Getting 2822 to Draft) Bruce Lilly
- Re: X-* header fields Bruce Lilly
- Re: X-* header fields (Was: Getting 2822 to Draft) Keith Moore
- Re: X-* header fields (Was: Getting 2822 to Draft) ned+ietf-822
- Re: X-* header fields (Was: Getting 2822 to Draft) Charles Lindsey
- Re: Getting 2822 to Draft Charles Lindsey
- Re: X-* header fields (Was: Getting 2822 to Draft) Keith Moore
- Re: X-* header fields (Was: Getting 2822 to Draft) Adam M. Costello
- Re: X-* header fields Kai Henningsen
- Re: X-* header fields (Was: Getting 2822 to Draft) Pete Resnick
- Re: X-* header fields (Was: Getting 2822 to Draft) Bruce Lilly
- Re: Getting 2822 to Draft Bruce Lilly
- Re: X-* header fields (Was: Getting 2822 to Draft) ned+ietf-822
- Re: X-* header fields (Was: Getting 2822 to Draft) Arnt Gulbrandsen
- X-* header fields (Was: Getting 2822 to Draft) Pete Resnick
- Re: Re: Getting 2822 to Draft Dave Crocker
- Re: Getting 2822 to Draft Pete Resnick
- Re: Getting 2822 to Draft Keith Moore
- Re: Getting 2822 to Draft Al Costanzo
- Re: Getting 2822 to Draft Kurt Keller
- Re: Getting 2822 to Draft Keith Moore
- Re: Getting 2822 to Draft Pete Resnick
- Re: Getting 2822 to Draft Keith Moore
- Re: Getting 2822 to Draft Pete Resnick
- Re: Getting 2822 to Draft Pete Resnick
- Re: Getting 2822 to Draft Keith Moore
- Re: Getting 2822 to Draft WJCarpenter
- Re: Getting 2822 to Draft Arnt Gulbrandsen
- Re: Getting 2822 to Draft Keith Moore
- Re: Getting 2822 to Draft Simon Josefsson
- Re: Getting 2822 to Draft Al Costanzo
- Re: Getting 2822 to Draft Keith Moore
- Re: Getting 2822 to Draft Keith Moore
- Re: Getting 2822 to Draft Simon Josefsson
- Getting 2822 to Draft Pete Resnick
- X- fields (Re: Getting 2822 to Draft) Bruce Lilly