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

Carl Wallace <> Wed, 20 July 2011 16:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A4E0B21F85AA; Wed, 20 Jul 2011 09:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.483
X-Spam-Status: No, score=-3.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xlO4YsiFs-GV; Wed, 20 Jul 2011 09:32:10 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E8DFB21F85A4; Wed, 20 Jul 2011 09:32:09 -0700 (PDT)
Received: by vws12 with SMTP id 12so364971vws.31 for <multiple recipients>; Wed, 20 Jul 2011 09:32:09 -0700 (PDT)
Received: by with SMTP id gg5mr2253800vcb.150.1311179529323; Wed, 20 Jul 2011 09:32:09 -0700 (PDT)
Received: from [] ( []) by with ESMTPS id bp11sm118615vcb.0.2011. (version=SSLv3 cipher=OTHER); Wed, 20 Jul 2011 09:32:08 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/
Date: Wed, 20 Jul 2011 12:32:04 -0400
From: Carl Wallace <>
To: todd glassey <>
Message-ID: <>
Thread-Topic: [ltans] WG Action: Conclusion of Long-Term Archive and Notary Services (ltans)
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [ltans] WG Action: Conclusion of Long-Term Archive and Notary Services (ltans)
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: LTANS Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Jul 2011 16:32:10 -0000

The good news is that none of the 5 completed specs address notary-related
concepts.  Each spec addresses fairly narrow concepts consistent with the
backgrounds of the volunteers contributing the work.  While it may be
unfortunate that the term notary appears in the working group name, the
notary concept was from the inception of the working group considered to
be a topic area that would not necessarily result in new standards.

On 7/20/11 12:10 PM, "todd glassey" <> wrote:

>On 7/20/2011 8:12 AM, Carl Wallace wrote:
>> On 7/20/11 10:49 AM, "todd glassey"<>  wrote:
>>> 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.
>> Correct.  In accord with the charter, a requirements gathering effort
>> potential notary-related work was conducted.
> From who - the engineers working on the protocol??? - do any of them
>have legal backgrounds which would be competent to advise here? Will any
>of their sponsors take legal culpability for those parties actions?  You
>see my point?
>Its time for accountability here in the IETF to be real.
>> The results were reviewed by
>> the working group and work on notary-related standards was suspended at
>> IETF 65 due to lack of interest in pursuing the topic.
>Which means that the terms and any reference to the concept of "Legal
>Document Control" per the apostles practices have to be cleansed from
>these works.  i.e. someone with a redline needs to cut out all
>references to Notary anything. That said, it means simply that this WG
>isnt done and that until those issues are completed, that NONE of the
>works can be finalized... or that they can and must all be pulled -
>since the IETF itself becomes a party to the fraud of misrepresenting
>its IP's as 'replacing legal roles' in the Human population.
>The IETF has never made a legal statement about any of its protocols
>before LTANS, but I think that by using the Legal Term "NOTARY" in both
>the WG's title and its operating practices, it opens the IETF to this
>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.