Re: [apps-discuss] process and editing questions: RFC errata

t.petch <ietfc@btconnect.com> Thu, 21 February 2013 11:08 UTC

Return-Path: <ietfc@btconnect.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 E21D621F8E65 for <apps-discuss@ietfa.amsl.com>; Thu, 21 Feb 2013 03:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.361
X-Spam-Level:
X-Spam-Status: No, score=-5.361 tagged_above=-999 required=5 tests=[AWL=1.238, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 CHX4hecrrigu for <apps-discuss@ietfa.amsl.com>; Thu, 21 Feb 2013 03:08:11 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe003.messaging.microsoft.com [207.46.163.26]) by ietfa.amsl.com (Postfix) with ESMTP id E166421F8E5E for <apps-discuss@ietf.org>; Thu, 21 Feb 2013 03:08:10 -0800 (PST)
Received: from mail18-co9-R.bigfish.com (10.236.132.235) by CO9EHSOBE003.bigfish.com (10.236.130.66) with Microsoft SMTP Server id 14.1.225.23; Thu, 21 Feb 2013 11:08:05 +0000
Received: from mail18-co9 (localhost [127.0.0.1]) by mail18-co9-R.bigfish.com (Postfix) with ESMTP id ED26C3A013F; Thu, 21 Feb 2013 11:08:04 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: PS-19(zz9371I542I1432Izz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275ch1033IL177df4h17326ah8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh304l1155h)
Received: from mail18-co9 (localhost.localdomain [127.0.0.1]) by mail18-co9 (MessageSwitch) id 136144488393228_15075; Thu, 21 Feb 2013 11:08:03 +0000 (UTC)
Received: from CO9EHSMHS023.bigfish.com (unknown [10.236.132.235]) by mail18-co9.bigfish.com (Postfix) with ESMTP id 13E7634006A; Thu, 21 Feb 2013 11:08:03 +0000 (UTC)
Received: from AM2PRD0710HT001.eurprd07.prod.outlook.com (157.56.249.213) by CO9EHSMHS023.bigfish.com (10.236.130.33) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 21 Feb 2013 11:08:02 +0000
Received: from DB3PRD0511HT002.eurprd05.prod.outlook.com (157.56.254.213) by pod51017.outlook.com (10.255.165.36) with Microsoft SMTP Server (TLS) id 14.16.263.1; Thu, 21 Feb 2013 11:07:57 +0000
Message-ID: <000901ce1023$3c4b7140$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Erik Wilde <dret@berkeley.edu>, apps-discuss@ietf.org
References: <5124D91C.1000703@berkeley.edu>
Date: Thu, 21 Feb 2013 11:04:28 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.213]
X-OriginatorOrg: btconnect.com
Subject: Re: [apps-discuss] process and editing questions: RFC errata
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: Thu, 21 Feb 2013 11:08:12 -0000

----- Original Message -----
From: "Erik Wilde" <dret@berkeley.edu>
To: <apps-discuss@ietf.org>
Sent: Wednesday, February 20, 2013 2:09 PM

> hello.
>
> i have two process and editing questions:
> http://tools.ietf.org/html/draft-wilde-xml-patch-03#section-6
> specifically links to errata i have filed regarding RFC 5261. it seems
> to me that these errata are legitimate, and that they simply weren't
> caught earlier. draft-wilde-xml-patch is almost complete, and i am
> wondering about the following things:
>
> - how to best sync draft development, and the submitted errata. there
> seems to be no way to predict when and how errata are processed, in
> particular for RFC 5261 because the author seems to be unreachable.

Indeed!  Bear in mind that the text of an RFC is available for further
processing within the IETF so while it is desirable that the original
author is involved in any updates thereto, that is not a requirement
thereof so if you cannot get any response from them, then submitting an
RFC5261-bis yourself is quite in order; but quite a lot of work.

A simpler approach is to include the relevant changes in
draft-wilde-xml-patch
and state that this is an update to the relevant sections of  RFC5261.
These should give more context than the errata do but need not be much
longer.

Or you can include sections that clarify the issues you have identified
in RFC5261 and state in your I-D that your I-D is based on this
interpretation ie you are not updating RFC5261 for the world at large
but are modifiying the content thereof for the purposes of your I-D.

Or you can make normative references to errata by URL once they are
approved.  I think this the most fraught approach and so the least
desirable.

Tom Petch

> - if the errata are accepted, how to reference them in the draft. it
> would be important that people following references to RFC 5261 from
the
> draft do not just read the RFC, but also take the errata into account
> when implementing the spec.
>
> thanks a lot and cheers,
>
> dret.
>
> --
> erik wilde | mailto:dret@berkeley.edu  -  tel:+1-510-2061079 |
>             | UC Berkeley  -  School of Information (ISchool) |
>             | http://dret.net/netdret http://twitter.com/dret |>