Re: [apps-discuss] draft-ietf-appsawg-rfc3462bis: PS or DS?

Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Sat, 03 September 2011 00:10 UTC

Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@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 9A90D21F8DDF for <apps-discuss@ietfa.amsl.com>; Fri, 2 Sep 2011 17:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.951
X-Spam-Level:
X-Spam-Status: No, score=-102.951 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uXvHResZ1Dpp for <apps-discuss@ietfa.amsl.com>; Fri, 2 Sep 2011 17:10:35 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0738A21F8DDE for <apps-discuss@ietf.org>; Fri, 2 Sep 2011 17:10:34 -0700 (PDT)
Received: by pzk33 with SMTP id 33so10768951pzk.18 for <apps-discuss@ietf.org>; Fri, 02 Sep 2011 17:12:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=dTZ5AxIXCJJm5NMxPusqvwACkziwIJFGsuJ4h3i8l/Q=; b=n9SBN5wVIQIkJnLVmlgb/Gsww3BHgLZAslCHAcAlUsotu77V9nHrlVLJlXet1I75xC RCf6WUg7baoaZsKSOaCw8l/MxtkPI0vpWc5D3b/ZOUwbbFev4FTV6fJehDJoDJWIPl0E 8loiT7AjBVEX7ihTzHnH/2INnvwaguQykxsqU=
Received: by 10.68.28.167 with SMTP id c7mr2610614pbh.358.1315008732118; Fri, 02 Sep 2011 17:12:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.98.5 with HTTP; Fri, 2 Sep 2011 17:11:32 -0700 (PDT)
In-Reply-To: <01O5L1MUPLD200RCTX@mauve.mrochek.com>
References: <20110830041853.24036.37.idtracker@ietfa.amsl.com> <F5833273385BB34F99288B3648C4F06F13512DFA7F@EXCH-C2.corp.cloudmark.com> <CAC4RtVBfyO4qDKEQp+0tsiN65oyUAvAdFs1-y5v3r1q7o+Ve4w@mail.gmail.com> <CAHhFybq=YWpaxpUVacZ-4UZASwJ_DFZrFqxAQHw_Fon+Tn2xeg@mail.gmail.com> <01O5L1MUPLD200RCTX@mauve.mrochek.com>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Sat, 03 Sep 2011 02:11:32 +0200
Message-ID: <CAHhFybpzft19fJfR8BgUZDK56sHXkyAv+tOyYpbe-PddOWfOFA@mail.gmail.com>
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Barry Leiba <barryleiba@computer.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] draft-ietf-appsawg-rfc3462bis: PS or DS?
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: Sat, 03 Sep 2011 00:10:35 -0000

On 3 September 2011 01:31, Ned Freed wrote:

> AFAICT the argument to move to full standard has not been made

Well, I tried some days ago.  The interoperability reports for DS
are rather old, but at least they do not mention "multipart/report
not at the top level" issues:

<http://www.ietf.org/iesg/implementation/report-rfc1891-1894.txt>

> full is about deployment, and that's harder to justify.

If all these "significant" and "successful" in RFC 2026 4.1.3 are
to be interpreted as "e.g., 4409bis", then I'd have no idea how
to demonstrate a similar significance or success of RFC 3462...

...for 4409bis I could at least produce "significant" amounts of
messages posted by me, or the "successful" publication of a BCP
formerly known as draft-hutzler-spamops.

Maybe you don't like "three steps" because you interpret RFC 2026
4.1.3 more strictly.  I consider the "third step" as last chance
to fix errata and polish a good DS before it's seriously time to
start something new and better at PS (e.g., 282?, 532?, 532?bis).

-Frank