Re: [iucg] Last Call: Modern Global Standards Paradigm

John C Klensin <john-ietf@jck.com> Tue, 14 August 2012 14:11 UTC

Return-Path: <john-ietf@jck.com>
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 E550021F855A for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 07:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level:
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, 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 crPdjcWxckdF for <ietf@ietfa.amsl.com>; Tue, 14 Aug 2012 07:11:47 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 63D4721F8548 for <ietf@ietf.org>; Tue, 14 Aug 2012 07:11:47 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T1HkM-000Izl-MD; Tue, 14 Aug 2012 10:05:26 -0400
Date: Tue, 14 Aug 2012 10:11:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eric Burger <eburger-l@standardstrack.com>, IETF list <ietf@ietf.org>
Subject: Re: [iucg] Last Call: Modern Global Standards Paradigm
Message-ID: <CB2AB8CF39768723422CB12E@JcK-HP8200.jck.com>
In-Reply-To: <E521F97C-24C8-4D2E-9471-844FCD69212C@standardstrack.com>
References: <DF4B6630-8BD1-4BFF-B872-99619B06FCF2@ietf.org> <CAMm+Lwio8=EyW-=LZE8BA4=6N=H4f7a1Nycg25LxB920ceZ6JA@mail.gmail.com> <1117B161-0454-4570-96BF-4045E4DB62A8@standardstrack.com> <276B7D303A96E840D2F95107@JcK-HP8200.jck.com> <CAMm+LwjL=tnYrtmHkV+=+VeOCo+1PjAu+pW0LnUyHYhVX_pPZA@mail.gmail.com> <C01C22690CE178AF8C2E52F7@JcK-HP8200.jck.com> <20120813012310.9F01A21F861E@ietfa.amsl.com> <5028C4C8.40508@tana.it> <F2E0F8B862341F3DC407A2DA@JcK-HP8200.jck.com> <E521F97C-24C8-4D2E-9471-844FCD69212C@standardstrack.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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, 14 Aug 2012 14:11:48 -0000

--On Monday, August 13, 2012 22:26 -0400 Eric Burger
<eburger-l@standardstrack.com> wrote:

> +1. The ITU is not evil. It just is not the right place for
> Internet standards development. As John points out, there are
> potential uses of the ITU-T for good.

Eric,

I'd narrow your first statement further and say "Internet
technical standards development" or "Internet protocol standards
development".  There are, at least potentially, other
categories.  Those at least mostly fall outside the IETF's scope
and there may well be useful work for the ITU to do in some of
them.  

I find it interesting that ISO and many of their Member Bodies
(including, fwiw, ANSI) make a careful distinction between
standards that have direct bearing on safety issues and other
types... and use different approval criteria for the former.
The IETF doesn't do safety standards (emergency reporting is
really not in that category) and I'm not quite sure what a
safety standard at the IP layer or above would look like (I can
imagine some at physical layer, but we don't do those either).
If there were such a thing as a safety standard involving
communications technology, I could imagine an ITU role there
(although I can't think of any examples for which ISO/IEC JTC1
would not be more appropriate).

I don't see that as contradicting the proposed statement in any
way although, if we had more opportunity to quibble about
wording, I might think some fine-tuning was in order.

    john