Re: [ltans] WG Action: Conclusion of Long-Term Archive and Notary Services (ltans)

On 7/19/2011 6:28 PM, IESG Secretary wrote:
> The Long-Term Archive and Notary Services (ltans) working group in the
> Security Area has concluded. The IESG contact persons are Sean Turner
> and Stephen Farrell.
So there is actually no Notary's process in any of this code. No 
Notarial signing ceremony and more importantly no Notarial Organization 
as a sponsor... As such - and since the term NOTORIAL pertains to a 
legal standing, i.e. as in 'from an act from a commissioned Notary 
Public" - something this protocol has none of the representing it as a 
replacement or extension of a commissioned Notary Public is a form of 
fraud.

No I am not kidding... If you dont believe me look at California's 
Apostilles Page for certifications issued under the Notary's Commission 
to perform signings. What you will see is that a Notary is similar to 
the term Judge, when used in an official context it applies to a person 
appointed under the Notarial commission of the issuing State or Entity.

http://www.sos.ca.gov/business/notary/authentication.htm which of course 
are further controlled under the International Definition of the 
Apostilles under the Hague Convention - read it at 
http://www.hcch.net/index_en.php?act=text.display&tid=37

The real issue here (and the sad one) is how much human effort went into 
this effort after the WG members were made aware of these legal issues 
with their work, and how far from the mark based on a simple reading of 
these documents that the WG ultimately landed.

Todd Glassey

> The ltans working group has completed its primary charter items, and is
> officially closing. The mailing list will be retained for future
> discussions involving ltans. The list archive will also be retained.
>
> The ltans working group was primarily focused on defining requirements,
> data structures and protocols for the secure usage of archive and notary
> services. In total the working group published five RFCs, including
> Long-Term Archive Service Requirements (RFC 4810), Evidence Record
> Syntax (ERS) (RFC 4998), Using the Server-Based Certificate Validation
> Protocol (SCVP) to Convey Long-Term Evidence Records (RFC 5276), Data
> Structure for the Security Suitability of Cryptographic Algorithms
> (DSSC) (RFC 5698), and Extensible Markup Language Evidence Record Syntax
> (RFC 6283).
>
> We would like to thank all of the IETF participants who have contributed
> to the various documents produced by the ltans working group and to the
> successful completion of these deliverables. We especially thank Carl
> Wallace and Tobias Gondrom who have chaired the working group from its
> inception.
> _______________________________________________
> ltans mailing list
> ltans@ietf.org
> https://www.ietf.org/mailman/listinfo/ltans
>

-- 
Todd S. Glassey
This is from my personal email account and any materials from this account come with personal disclaimers.

Further I OPT OUT of any and all commercial emailings.