Re: [apps-discuss] draft-wilde-xml-patch and updates to RFC 5261

Barry Leiba <barryleiba@computer.org> Thu, 28 February 2013 15:51 UTC

Return-Path: <barryleiba.mailing.lists@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 0857F21F8B70 for <apps-discuss@ietfa.amsl.com>; Thu, 28 Feb 2013 07:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.959
X-Spam-Level:
X-Spam-Status: No, score=-102.959 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 8KhGLD636E2k for <apps-discuss@ietfa.amsl.com>; Thu, 28 Feb 2013 07:51:07 -0800 (PST)
Received: from mail-vc0-f174.google.com (mail-vc0-f174.google.com [209.85.220.174]) by ietfa.amsl.com (Postfix) with ESMTP id CEFE621F87C3 for <apps-discuss@ietf.org>; Thu, 28 Feb 2013 07:51:06 -0800 (PST)
Received: by mail-vc0-f174.google.com with SMTP id n11so1306937vch.33 for <apps-discuss@ietf.org>; Thu, 28 Feb 2013 07:51:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9bAhE8drnGC1kxl4UTOH89fsCHZSSRreR+2+v+aOUM4=; b=HJxm4VG4HgrcTMIzc8mW7IeZJCN3G7ar64XZx0V/MZ9pMdlci0BIddYLRcq+7RtzEi 1Ui/L9++YnDcoNbltLqWxjZVQM6OMbuL0o+8kpmke9WFnkTW4bmCooysb+yil4nZ/2zB HB0qIjca1H13373dcWZd5pR9jOUMewSqdrKMAgvsfZM8JV/7BsIaBLHUzQ14Z7a1Cg94 1oF62Z3RrP6y/KDfAOczoYjA1uMeDe2X7/+LckdkpGcn6E/+ykvn/1Fx75KutSiqHD5e rNlQloyng/q9B5Kd3F9xaXcNOrov695evn0vPq6ETa0FKvBwv0Dw1S05HD3OFY9kCW7/ BiTQ==
MIME-Version: 1.0
X-Received: by 10.220.116.5 with SMTP id k5mr2684196vcq.55.1362066660762; Thu, 28 Feb 2013 07:51:00 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Thu, 28 Feb 2013 07:51:00 -0800 (PST)
In-Reply-To: <015c01ce15c9$17585dc0$4001a8c0@gateway.2wire.net>
References: <5124D91C.1000703@berkeley.edu> <000901ce1023$3c4b7140$4001a8c0@gateway.2wire.net> <51263634.7040906@berkeley.edu> <015e01ce1052$3098b540$4001a8c0@gateway.2wire.net> <5128ED20.6030502@berkeley.edu> <512E1574.50504@berkeley.edu> <015c01ce15c9$17585dc0$4001a8c0@gateway.2wire.net>
Date: Thu, 28 Feb 2013 10:51:00 -0500
X-Google-Sender-Auth: 9yijXyvbynydjWRQM6692DI6J-s
Message-ID: <CAC4RtVCEsO58tSNc1uuhgZuXsBQjegm=zC_8XnWbfjOspgQT8w@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "t.petch" <ietfc@btconnect.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] draft-wilde-xml-patch and updates to RFC 5261
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, 28 Feb 2013 15:51:35 -0000

> You posted errata against RFC5261, an RFC which was produced by simple.
> Therefore notification of the errata went to the simple WG mailing list
> which was shut down two days ago so your good work has found a very
> effective black hole.
...
> Normally, the AD picks up an erratum and runs with it but since the WG
> has shut down, doubtless the ADs have as well, so you will need to find
> a friendly AD elsewhere

This is nonsensical.

Errata are associated with the area that the document was produced
in.[1]  Even if the RFC came from an individual submission (no WG) or
from a WG that has closed (recently, or years ago), the ADs for the
area the report is assigned to will see it, and will eventually deal
with it.  The IESG has been putting more emphasis, over the past
couple of years, on handling errata and keeping the number left at
"Reported" to an absolute minimum.

The RAI ADs will deal with this one, I'm sure.

Barry


[1] Errata against very old RFCs can get into a sort of "black hole"
situation if they are not assigned to an area.  That's not an issue in
this case.