Re: [ltans] "Proof Source Provider" - new term for use in describing trust chains in document hierarchies

"Carl Wallace" <CWallace@cygnacom.com> Tue, 15 September 2009 17:33 UTC

Return-Path: <cwallace@cygnacom.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 54D793A6AAE for <ltans@core3.amsl.com>; Tue, 15 Sep 2009 10:33:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.322
X-Spam-Level:
X-Spam-Status: No, score=-4.322 tagged_above=-999 required=5 tests=[AWL=1.724, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 7trL2lYKEkvV for <ltans@core3.amsl.com>; Tue, 15 Sep 2009 10:32:59 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 2EBC53A6A24 for <ltans@ietf.org>; Tue, 15 Sep 2009 10:32:58 -0700 (PDT)
Received: from p03c11o141.symantecmail.net (p03c11o141.symantecmail.net [208.65.144.84]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8FHP6nE012997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-ltans@imc.org>; Tue, 15 Sep 2009 10:25:11 -0700 (MST) (envelope-from cwallace@cygnacom.com)
Received: from unknown [65.242.48.5] (EHLO scygexch1.cygnacom.com) by p03c11o141.symantecmail.net (mxl_mta-5.7.0-7) with ESMTP id 7fdcfaa4.2679081904.20321.00-023.p03c11o141.symantecmail.net (envelope-from <cwallace@cygnacom.com>); Tue, 15 Sep 2009 11:25:11 -0600 (MDT)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 15 Sep 2009 13:25:02 -0400
Message-ID: <FAD1CF17F2A45B43ADE04E140BA83D48CD7A34@scygexch1.cygnacom.com>
In-Reply-To: <4AAFAFEE.9090201@earthlink.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [ltans] "Proof Source Provider" - new term for use in describing trust chains in document hierarchies
Thread-Index: Aco2F57h5g5xOY64SE6ww5Eim0S1wwAEKbwQ
References: <4AAFAFEE.9090201@earthlink.net>
From: Carl Wallace <CWallace@cygnacom.com>
To: Todd Glassey <tglassey@earthlink.net>, ietf-ltans@imc.org
X-Spam: [F=0.2000000000; S=0.200(2009090401)]
X-MAIL-FROM: <cwallace@cygnacom.com>
X-SOURCE-IP: [65.242.48.5]
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
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:33:00 -0000

It's not clear to me what you are proposing, i.e., alteration of
existing specs to use the new terminology, preparation of auditing
guidelines, specification of protocols for distributing trust anchors,
definition of structures for binding trust anchors to document
hierarchies, or something else.  A draft may help establish context.
Depending on the nature of the work, LTANS may not be the best place to
pursue it, but if pursued here re-chartering would be required. 

> -----Original Message-----
> From: ltans-bounces@ietf.org [mailto:ltans-bounces@ietf.org] On Behalf
> Of Todd Glassey
> Sent: Tuesday, September 15, 2009 11:17 AM
> To: ietf-ltans@imc.org
> Subject: [ltans] "Proof Source Provider" - new term for use in
> describing trust chains in document hierarchies
> 
> Folks -
> I want to propose a new term for describing certain relationships in a
> network model. The term is  "Proof Source Provider" or PSP and it
means
> some service which is providing a trust-anchor for some other process
> or
> the like. The PSP is the party or system which provides the oversight
> and process control for an TRUST-ANCHOR - the component of the trust
> element which ties the specific content to that trust element. The
Term
> Trust Anchor (now widely in use in Secure DNS) was coined in PKIX
> several years ago but is critically valuable now in other areas and we
> should embrace both it and the idea of the Proof Source Provider and
> the
> Proof Source they use to cerate admissibility for the evidence.
> 
> It (PSP)  pertains then to auditing trust relationships and their
> ability to convey policy and control over a larger methodology and is
a
> key part of relational trust models which are propagated across
> multiple
> technologies and would be used in LTANS Security and other key
> processes.
> 
> Why this is important is that systems and processes which we would
> build
> from these technologies would also perform functions in the real world
> which would have legal implications and so the ability to represent
> trust-anchor processes in the records created would admissible in
> global
> courts. This nomenclature provides a resource for this and other uses.
> 
> Todd Glassey
> 
> 
> _______________________________________________
> ltans mailing list
> ltans@ietf.org
> https://www.ietf.org/mailman/listinfo/ltans