Re: PS Characterization Clarified

Olaf Kolkman <olaf@NLnetLabs.nl> Tue, 17 September 2013 10:14 UTC

Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0E1511E80F8 for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 03:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, 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 7ZPuiEpqRr0L for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 03:14:55 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F51E11E80F3 for <ietf@ietf.org>; Tue, 17 Sep 2013 03:14:54 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:7211:24ff:fe8c:627a] ([IPv6:2001:7b8:206:1:7211:24ff:fe8c:627a]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r8HAEcVT050829 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 17 Sep 2013 12:14:39 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl r8HAEcVT050829
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1379412880; bh=RP0rEJCd/AGuU7zixwAxrQtejjGOakgMwKW7pvUijJM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=mTlYOJIXELkwglXbGrrydjiSgnwnLARJSlBd5CIc19KBKUI5+XVyhUKyRBeCkqOmW Ugc0JNJ8HAYC2J477WCfb/10C1GdGDipkL6DpF4H8c03c72j6762u3b7RAZzpaA7ya xXxJP9L6MDfpc/XZ4w7U8n1no1KkHMAW16hEXvDU=
Content-Type: multipart/signed; boundary="Apple-Mail=_9E018A10-100E-4C60-81DF-D43FE6FF2C8A"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: PS Characterization Clarified
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <24CA51F99F2393948000F42F@JcK-HP8200.jck.com>
Date: Tue, 17 Sep 2013 12:14:37 +0200
Message-Id: <A87588E1-9447-4AA6-9FB3-BEB8234A26A7@NLnetLabs.nl>
References: <B8F661D1-1C45-4A4B-9EFE-C7E32A7654E7@NLnetLabs.nl> <9B5010D3-EA47-49AD-B9D0-08148B7428FC@piuha.net> <CAC4RtVDXVqZkCi1stmuoxawUVDi6+uG-bXWp36CM6-bsqNjiew@mail.gmail.com> <EC75AB54-8B11-42B9-8049-F70D09DB1775@NLnetLabs.nl> <CAC4RtVDj3tBChrJBiBiD6uwOtGRJHLDYeh62XbERrHp0i1Fmfg@mail.gmail.com> <CAPv4CP-DXq0=FX9nFDCo0HXvWKNRTJ+8ay=m7J=JyRxJciN-vw@mail.gmail.c om> <522761EB.2000002@gmail.com> <13BBB594-4510-4903-917B-67D39F60E2BD@NLnetLabs.nl> <A87B7462DC459B3D64373984@JcK-HP8200.jck.com> <6A29D567-0C5A-4CB4-ABDF-450D52D2C642@NLnetLabs.nl> <24CA51F99F2393948000F42F@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Tue, 17 Sep 2013 12:14:40 +0200 (CEST)
Cc: Barry Leiba <barryleiba@computer.org>, IETF list <ietf@ietf.org>, Scott O Bradner <sob@sobco.com>, SM Moonesamy <sm+ietf@elandsys.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2013 10:14:57 -0000

On 16 sep. 2013, at 17:31, John C Klensin <john-ietf@jck.com> wrote:

>> 
>> As actionable for this draft I take that I explicitly mention
>> that Section 4.1 2026 is exclusively updated.
> 
> While I understand your desire to keep this short, the pragmatic
> reality is that your non-IETF audience is likely to read this
> document (especially after you hand it to them) and conclude
> that it is the whole story.  Since the natural question that
> immediately follows "why should we accept your standards at all"
> is "why can't you hand them off to, e.g., ISO, the way that many
> national bodies and organizations like IEEE do with many of
> their documents".  
> 
> Suggestion in the interest of brevity: in addition to mentioning
> the above, mention explicitly that there are requirements in
> other sections of 2026 that affect what is standardized and how. 

Second paragraph of the introduction now reads:


      This document exclusively updates the characterization of
      Proposed Standards from RFC2026 Section 4.1.1 and does not speak
      to or alter the procedures for the maintenance of Standards
      Track documents from RFC 2026 and <xref target="RFC6410">RFC
      6410</xref>. For complete understanding of the requirements for
      standardization those documents should be read in conjunction
      with this document.
    
> By the way, while I understand all of the reasons why we don't
> want to actually replace 2026 (and agree with most of them),
> things are getting to the point that it takes far too much
> energy to actually figure out what the rules are.  Perhaps it is
> time for someone to create an unofficial redlined version of
> 2026 that incorporates all of the changes and put it up on the
> web somewhere.   I think we would want a clear introduction and
> disclaimer that it might be be exactly correct and that only the
> RFCs are normative, but the accumulation of changes may
> otherwise be taking us too far into the obscure.  If we need a
> place to put it, it might be a good appendix to the Tao.  And
> constructing it might be a good job for a relative newcomer who
> is trying to understand the ins and outs of our formal
> procedures.

I guess this is a call for volunteers.

--Olaf