Re: [ltans] WG Action: Conclusion of Long-Term Archive and Notary Services (ltans)
todd glassey <tglassey@earthlink.net> Wed, 20 July 2011 19:04 UTC
Return-Path: <tglassey@earthlink.net>
X-Original-To: ltans@ietfa.amsl.com
Delivered-To: ltans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F26F21F847D; Wed, 20 Jul 2011 12:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.262
X-Spam-Level:
X-Spam-Status: No, score=-3.262 tagged_above=-999 required=5 tests=[AWL=-0.664, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zjnA2UP3Ejvn; Wed, 20 Jul 2011 12:04:50 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id C8EB321F8450; Wed, 20 Jul 2011 12:04:44 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=fFp+V/N+F10QFQ3t47hkdC97z8f731pC9n++O4IKI221GGjAHSCgl6JC8deZrqr8; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [207.111.209.5] (helo=[192.168.1.100]) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Qjc4Z-0005UZ-OC; Wed, 20 Jul 2011 15:04:44 -0400
Message-ID: <4E2726EB.8030002@earthlink.net>
Date: Wed, 20 Jul 2011 12:05:15 -0700
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
References: <4E26FDEA.1050706@earthlink.net> <CA4C777C.73BA%carl@redhoundsoftware.com> <CAMm+LwjGgC5Q_2MqU33-17iBgAyOJ7ah-=mrShYBuHvvNrBf+A@mail.gmail.com>
In-Reply-To: <CAMm+LwjGgC5Q_2MqU33-17iBgAyOJ7ah-=mrShYBuHvvNrBf+A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040600020703000806070807"
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79ea18772e16d46dd8df832c666ce14ec3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 207.111.209.5
Cc: chair@ietf.org, ltans@ietf.org
Subject: Re: [ltans] WG Action: Conclusion of Long-Term Archive and Notary Services (ltans)
X-BeenThere: ltans@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: LTANS Working Group <ltans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 20 Jul 2011 19:04:54 -0000
On 7/20/2011 9:48 AM, Phillip Hallam-Baker wrote: > Exactly, a WG should do something right or not at all. In this case > they choose not at all. That is fine with me. The problem is they didnt remove the SCOPE STATEMENT from the WG Name and so now whenever a search is done for those documents they are tied to the term NOTARIAL even though they have nothing to do with it... Todd > > Todd seems to be giving some pretty good reasons to not do notary. > > > What I am interested in is probably a little speculative. I would like > to have a form of data repository that we could establish some pretty > good expectations of it surviving for a very long time and for the > integrity of the data within it to be witnessed by a sufficiently > large set of witnesses that forgery is implausible. > > > > On Wed, Jul 20, 2011 at 12:32 PM, Carl Wallace > <carl@redhoundsoftware.com <mailto:carl@redhoundsoftware.com>> wrote: > > 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" <tglassey@earthlink.net > <mailto:tglassey@earthlink.net>> wrote: > > >On 7/20/2011 8:12 AM, Carl Wallace wrote: > >> On 7/20/11 10:49 AM, "todd glassey"<tglassey@earthlink.net > <mailto:tglassey@earthlink.net>> 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 > >>for > >> 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 > >review. > > > >t. > > > > > > > >-- > >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. > > > > > _______________________________________________ > ltans mailing list > ltans@ietf.org <mailto:ltans@ietf.org> > https://www.ietf.org/mailman/listinfo/ltans > > > > > -- > Website: http://hallambaker.com/ > -- 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.
- [ltans] WG Action: Conclusion of Long-Term Archiv… IESG Secretary
- Re: [ltans] WG Action: Conclusion of Long-Term Ar… todd glassey
- Re: [ltans] WG Action: Conclusion of Long-Term Ar… Carl Wallace
- Re: [ltans] WG Action: Conclusion of Long-Term Ar… todd glassey
- Re: [ltans] WG Action: Conclusion of Long-Term Ar… Carl Wallace
- Re: [ltans] WG Action: Conclusion of Long-Term Ar… Phillip Hallam-Baker
- Re: [ltans] WG Action: Conclusion of Long-Term Ar… todd glassey
- Re: [ltans] WG Action: Conclusion of Long-Term Ar… todd glassey
- Re: [ltans] WG Action: Conclusion of Long-Term Ar… Tobias Gondrom