RE: [legalxml-enotary] Example - Authenticating Request For Servi ce

[Pieter Kasselman <pkasselman@baltimore.com>]

Hi Ram, could you explain what the notirization event is in this scenario?
Is the notarization event the creation of the public key certificate, or are
thre numerous notarization events in the process, all of them recorded as
the process unfolds? 

Cheers

Pieter

> -----Original Message-----
> From:	Moskovitz, Ram Austryjak [SMTP:ram@verisign.com]
> Sent:	18 October 2002 18:48
> To:	'legalxml-enotary@lists.oasis-open.org'
> Subject:	[legalxml-enotary] Example - Authenticating Request For
> Service
> 
> Hiya,
> 
> Here's my first contribution of an example - a real world example from our
> Public CA operations team.
> 
> When we are processing certificate requests we jump through a number of
> hoops to ensure that the request is legitimate (requestor is authorized
> by
> the company, company exists, right to use name, right to use domain
> name...
> - the details vary by class, product line, and
> political/social/geographical
> constraints etc).
> 
> We may use a third party (credit scorer, government agency) to lookup a
> corporate phone number in order to call back into the organization and
> ensure that the alleged employee who made the certificate request is in
> actual fact an employee of the named organization and/or is authorized to
> act on their behalf. If we are unable to get a third party reference to
> the
> phone # then we require the customer provide a notarized letter confirming
> the organization has in fact enrolled for a n ID as well as validating the
> name and email address of the technical contact.
> 
> ram
> 
> -----
> Ram Austryjak Moskovitz
> Director
> VeriSign Research
> VeriSign, Inc.
> Ram@VeriSign.Com
> +1(650)426-3485
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
> 
> 
> This footnote confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.


-----------------------------------------------------------------------------
The information contained in this message is confidential and is intended
for the addressee(s) only.  If you have received this message in error or
there are any problems please notify the originator immediately.  The 
unauthorised use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for
direct, special, indirect or consequential damages arising from alteration
of the contents of this message by a third party or as a result of any 
virus being passed on.

This footnote confirms that this email message has been swept for Content
Security threats, including computer viruses.
http://www.baltimore.com