Re: [ltans] "Proof Source Provider" - new term for use in describing trust chains in document hierarchies
"Remo Tabanelli" <remo@t-bizcom.com> Tue, 15 September 2009 17:06 UTC
Return-Path: <remo@t-bizcom.com>
X-Original-To: ltans@core3.amsl.com
Delivered-To: ltans@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A923F28C129 for <ltans@core3.amsl.com>; Tue, 15 Sep 2009 10:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.032
X-Spam-Level:
X-Spam-Status: No, score=-3.032 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4]
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 Q8kjI56KAeq7 for <ltans@core3.amsl.com>; Tue, 15 Sep 2009 10:06:02 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id AF95C3A6AAE for <ltans@ietf.org>; Tue, 15 Sep 2009 10:06:02 -0700 (PDT)
Received: from ns2.t-bizcom.com (adsl-14-159.38-151.net24.it [151.38.159.14]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8FH6eGf011489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-ltans@imc.org>; Tue, 15 Sep 2009 10:06:48 -0700 (MST) (envelope-from remo@t-bizcom.com)
Received: from ns2.t-bizcom.com (localhost [127.0.0.1]) by ns2.t-bizcom.com (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id n8FH6XZX014267; Tue, 15 Sep 2009 19:06:36 +0200
Received: from 93.41.185.139 (SquirrelMail authenticated user remo) by ns2.t-bizcom.com with HTTP; Tue, 15 Sep 2009 19:06:36 +0200 (CEST)
Message-ID: <24910.93.41.185.139.1253034396.squirrel@ns2.t-bizcom.com>
In-Reply-To: <4AAFBEF3.8060607@earthlink.net>
References: <9DCCF5807745F9438462F1F6A66CADA403203A35D5@MAILR003.mail.lan> <4AAFBEF3.8060607@earthlink.net>
Date: Tue, 15 Sep 2009 19:06:36 +0200
From: Remo Tabanelli <remo@t-bizcom.com>
To: Todd Glassey <tglassey@earthlink.net>
User-Agent: SquirrelMail/1.4.6
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: "ietf-ltans@imc.org" <ietf-ltans@imc.org>, Bill Russell <brussell@pericore.com>
Subject: Re: [ltans] "Proof Source Provider" - new term for use in describing trust chains in document hierarchies
X-BeenThere: ltans@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: remo@t-bizcom.com
List-Id: LTANS Working Group <ltans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltans>, <mailto:ltans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltans>
List-Post: <mailto:ltans@ietf.org>
List-Help: <mailto:ltans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltans>, <mailto:ltans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 17:06:03 -0000
On Mar, 15 Settembre 2009 6:21 pm, Todd Glassey wrote: > Bill Russell wrote: >> We (Pericore) already use that term to express digitally signed >> authorizations. > Bummer - its copyrighted and not currently under any license. >> Also, Corestreet uses that term in one of their products. I think the >> term is overloaded and should not be used as you propose. >> > The term was used by me officially in print 10 years ago and it was > (c)'d on those works... your general counsel may get a kick out of that > and I can provide those documents to anyone that wants them. Bill & Todd Until now... and for more than two years I was silent on this list. and... today I'm very sad. IMHO a discussion in a IETF WG about copyrighted terms (or any other so called I.P. "wapor issue") is misplaced here. I'm not interested in hearing from anyone of us who was the first that used a plain english expression like "Proof Source Provider" because the first source of these terms is the common language... and I suppose you can find anyone of these word on a common dictionary! IMHO a phrase (in any language) is (or must be) without a specific and *explained contest* uncopyrightable. I'ts not realistic pretend to have a copyright on a term (or phrase) without the accluded (and this can be eventually copyrigthed not the single term or phrase) document/work. So if the WG think that using this terms is useful (IMHO) can decide to use it, if not we will not use it. Simply as that. Tank you all folks! Remo Tabanelli
- [ltans] "Proof Source Provider" - new term for us… Todd Glassey
- Re: [ltans] "Proof Source Provider" - new term fo… Bill Russell
- Re: [ltans] "Proof Source Provider" - new term fo… Todd Glassey
- Re: [ltans] "Proof Source Provider" - new term fo… Remo Tabanelli
- Re: [ltans] "Proof Source Provider" - new term fo… Carl Wallace
- Re: [ltans] "Proof Source Provider" - new term fo… Bill Russell
- Re: [ltans] "Proof Source Provider" - new term fo… Todd Glassey
- Re: [ltans] "Proof Source Provider" - new term fo… Todd Glassey
- Re: [ltans] "Proof Source Provider" - new term fo… Remo Tabanelli
- Re: [ltans] "Proof Source Provider" - new term fo… Todd Glassey
- Re: [ltans] "Proof Source Provider" - new term fo… Remo Tabanelli
- Re: [ltans] "Proof Source Provider" - new term fo… Todd Glassey