Issue 4194: In section 2.3.5.2 a transaction_ID is introduced without sufficient explan                                                                                                                             (pki-ftf)
Source: DSTC (Mr. Simon Gibson, gibson@dstc.edu.au)
Nature: Uncategorized Issue
Severity: 
Summary: In section 2.3.5.2 a transaction_ID is introduced without sufficient explanation.
Resolution: see above
Revised Text: 
Actions taken:
February 5, 2001: received issue
July 5, 2002: closed issue
Discussion: 
Add text as follows: 
A read only attribute representing an identifier for a particular 
transaction. This attribute relates directly to existing PKI 
entities. Currently a transaction will be given some unique identifier that 
relates to a particular transaction with an authority. In the case of using 
CORBA the unique identifier is not directly required due to the use of a 
RequestManager object for each transaction. This attribute is supplied so 
that the identifier provided by the back end authority can be obtained by a 
CORBA client
End of Annotations:=====
From: webmaster@omg.org
Message-Id: <200102060213.f162D0r18992@emerald.omg.org>
Date: 05 Feb 2001 22:14:13 -0500
To: <juergen@omg.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Issue/Bug Report
Content-Type: Text/html; charset=windows-1252
X-UIDL: ;7ld9"+#"!a/5!!CCf!!



Name: Simon Gibson 
Company: DSTC 
mailFrom: gibson@dstc.edu.au 
Notification: No 
Specification: Public Key Infrastructure 
Section: 2.3.5.2 
FormalNumber: dtc/2001-02-01 
Version: 1 
RevisionDate: 02/01/2001 
Page: 2-10 
Nature: Revision 
Severity: Minor 
HTTP User Agent: Mozilla/4.75 [en] (X11; U; SunOS 5.8 sun4u) 


Description

In section 2.3.5.2 a transaction_ID is introduced without sufficient
explanation.

X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: pmclaughlin@baltimore.com (Patrick McLaughlin),
   polar@adiron.com (Polar Humenn), gjarboe@promia.com (Gene Garboe),
   cwbinko@trcinc.com (Bill Binko), mcconnell@osm.net (Stephen
   McConnell),
   dflinn@iona.com (Don Flinn), Ronald.Monzillo@east.sun.com (Ron
   Monzillo),
   gibson@dstc.edu.au (Simon Gibson),
   christopher_milsom@hp.com (Christopher Milsom)
cc: pki-ftf@emerald.omg.org
Subject: PKI FTF issue # 4194
Mime-Version: 1.0
Date: Thu, 15 Feb 2001 08:52:04 +1000
From: Simon Gibson <gibson@dstc.qut.edu.au>
Content-Type: text/plain; charset=us-ascii
X-UIDL: i2+!!l;b!!KC1!!_Dfd9

This is issue # 4194	Simon Gibson gibson@dstc.edu.au

In section 2.3.5.2 a transaction_ID is introduced without sufficient
explan

-------------------------------------
Proposed Solution

Here is some proposed text to be added in relevant part of Section
2.3.5.2:

A read only attribute representing an identifier for a particular
transaction. This attribute relates directly to existing PKI
entities. Currently a transaction will be given some unique identifier
that
relates to a particular transaction with an authority. In the case of
using
CORBA the unique identifier is not directly required due to the use of
a
RequestManager object for each transaction. This attribute is supplied
so
that the identifier provided by the back end authority can be obtained
by a
CORBA client.



X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: pmclaughlin@baltimore.com (Patrick McLaughlin),
   polar@adiron.com (Polar Humenn), gjarboe@promia.com (Gene Garboe),
   cwbinko@trcinc.com (Bill Binko), mcconnell@osm.net (Stephen
   McConnell),
   dflinn@iona.com (Don Flinn), Ronald.Monzillo@east.sun.com (Ron
   Monzillo),
   gibson@dstc.edu.au (Simon Gibson),
   christopher_milsom@hp.com (Christopher Milsom)
cc: pki-ftf@emerald.omg.org
Subject: PKI FTF Request Vote on Issue #4194
Mime-Version: 1.0
Date: Tue, 26 Jun 2001 09:43:19 +1000
From: Simon Gibson <gibson@dstc.qut.edu.au>
Content-Type: text/plain; charset=us-ascii
X-UIDL: AT!!!WQ>e9ZLBe9_%Sd9

This is issue # 4194	Simon Gibson gibson@dstc.edu.au

In section 2.3.5.2 a transaction_ID is introduced without sufficient
explan

-------------------------------------
Proposed Solution

Here is some proposed text to be added in relevant part of Section
2.3.5.2:

A read only attribute representing an identifier for a particular
transaction. This attribute relates directly to existing PKI
entities. Currently a transaction will be given some unique identifier
that
relates to a particular transaction with an authority. In the case of
using
CORBA the unique identifier is not directly required due to the use of
a
RequestManager object for each transaction. This attribute is supplied
so
that the identifier provided by the back end authority can be obtained
by a
CORBA client.