Re: several messages

John C Klensin <john-ietf@jck.com> Fri, 30 January 2009 20:59 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D578528C1B7; Fri, 30 Jan 2009 12:59:49 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E68B128C1A3 for <ietf@core3.amsl.com>; Fri, 30 Jan 2009 12:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level:
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VL2TRFDGrJc8 for <ietf@core3.amsl.com>; Fri, 30 Jan 2009 12:59:48 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id CD74F3A69FA for <ietf@ietf.org>; Fri, 30 Jan 2009 12:59:47 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1LT0SV-000Mqk-K0; Fri, 30 Jan 2009 15:59:27 -0500
Date: Fri, 30 Jan 2009 15:59:26 -0500
From: John C Klensin <john-ietf@jck.com>
To: Dean Anderson <dean@av8.com>
Subject: Re: several messages
Message-ID: <346F35CC91DBDD0BFB9FBA3C@PST.JCK.COM>
In-Reply-To: <Pine.LNX.4.44.0901301333050.1287-100000@citation2.av8.net>
References: <Pine.LNX.4.44.0901301333050.1287-100000@citation2.av8.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: 'IETF Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

(I have drastically trimmed the cc list -- those who are not
following the IETF list probably don't care)

--On Friday, January 30, 2009 14:32 -0500 Dean Anderson
<dean@av8.com> wrote:

> You are indeed correct about ITU.
> 
> And possibly things have changed at ANSI.  However, my copy of
> ANSI T1.403.01-1999 is copyright 1999 by the Alliance for
> Telecommunications Industry Solutions, not the American
> National Standards Institute (ANSI)

Sorry, you need to understand how ANSI works.   ANSI is not a
standards developer and never has been.  They are an association
or federation that accredits standards bodies.  While there are
some edge cases, an ANSI number/ designation on a standard
basically indicates that the standards developer is an
ANSI-accredited body operating under ANSI rules (which are very
general) and ANSI approved-procedures.  You can actually see
that in the designation of the example you are citing: 

In
   ANSI T1.403.01-1999
the accredited standards committee is "T1" and this is a
document designated by T1 as 403.01, approved (or published) in
1999.  You might see ANSI/T1... instead, or other punctuation,
but the principle is the same.  I'd have to check, but I assume
that the "Alliance for Telecommunications Industry Solutions" is
the current sponsoring body for ASC T1.  "Sponsoring body for an
ASC" is, to a _very_ poor approximation, similar to the ISOC -
IETF relationship.

The actual authors/ editors/ contributors are not T1 or ATIS,
but some human beings or, in the most aggregate, companies who
participate in T1 or its subcommittees.

> ANSI standards (at least this one) also identifies (in a
> forward that is not technically a part of the standard) the
> ANSI members of the T1 committee that approved the standard
> and identifies each member company, member representative, and
> interest being represented.  ANSI also identifies the members
> of the Working Group (T1E1.2 on Wideband Access Interfaces in
> this case), and the participants and officials of that working
> group.

That is normal.  But none of those those folks or organizations
hold any copyright in the final document.  If the contributors
really held onto the copyrights, as you suggested, they
presumably would.  That document belongs, exclusively, to the
SDO (and, again, not to ANSI, which does not claim copyright to
documents).

Since I'm just trying to clarify the obviously factual parts of
this in relation to how other standards development
organizations do things, I'll leave responding to your other
comments, to others if they are so inclined.
>... 

   john

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf