RE: [newtrk] Session chair summary - implementation reports
Larry Masinter <LMM@acm.org> Tue, 16 August 2005 15:52 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E53jS-0007Xn-Fi for newtrk-archive@megatron.ietf.org; Tue, 16 Aug 2005 11:52:09 -0400
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19359 for <newtrk-archive@lists.ietf.org>; Tue, 16 Aug 2005 11:52:03 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j7GFowbS004436; Tue, 16 Aug 2005 08:50:58 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j7GFovnW004422; Tue, 16 Aug 2005 08:50:57 -0700 (PDT)
Received: from psmtp.com (exprod6og8.obsmtp.com [64.18.1.128]) by darkwing.uoregon.edu (8.13.4/8.13.4) with SMTP id j7GFouVv004337 for <newtrk@lists.uoregon.edu>; Tue, 16 Aug 2005 08:50:56 -0700 (PDT)
Received: from source ([192.150.11.134]) by exprod6ob8.obsmtp.com ([64.18.5.12]) with SMTP; Tue, 16 Aug 2005 08:50:56 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id j7GFi3BM024871 for <newtrk@lists.uoregon.edu>; Tue, 16 Aug 2005 08:44:03 -0700 (PDT)
Received: from calsj-dev (calsj-dev.corp.adobe.com [153.32.1.193]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id j7GFoon2011345 for <newtrk@lists.uoregon.edu>; Tue, 16 Aug 2005 08:50:55 -0700 (PDT)
Received: from calsj-dev (localhost [127.0.0.1]) by mailsj-v1.corp.adobe.com (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTP id <0ILB00CHNO0QHP@mailsj-v1.corp.adobe.com> for newtrk@lists.uoregon.edu; Tue, 16 Aug 2005 08:50:50 -0700 (PDT)
Received: from MasinterT43p ([130.248.178.177]) by mailsj-v1.corp.adobe.com (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTP id <0ILB00CFIO0LLQ@mailsj-v1.corp.adobe.com> for newtrk@lists.uoregon.edu; Tue, 16 Aug 2005 08:50:50 -0700 (PDT)
Date: Tue, 16 Aug 2005 08:50:39 -0700
From: Larry Masinter <LMM@acm.org>
Subject: RE: [newtrk] Session chair summary - implementation reports
In-reply-to: <4301B101.8050808@zurich.ibm.com>
To: 'Brian E Carpenter' <brc@zurich.ibm.com>
Cc: 'NEWTRK Mailing List' <newtrk@lists.uoregon.edu>
Message-id: <0ILB00CFWO0MLQ@mailsj-v1.corp.adobe.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: AcWiRNVNG99HfQ5/Rd6h2mE8vzWnBgAMx5Lg
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Reply-To: Larry Masinter <LMM@acm.org>
Content-Transfer-Encoding: 7bit
> So I have something of an immediate request here - can > we have a draft that defines minimum criteria for an > implementation report, which the IESG could consider for > use in the short term as a guideline? It's very hard to > reject an implementation report for inadequacy when we have > no visible guidelines beynd 2026. I think this is an important point. If we're concerned about "standards track", and, in particular, that not many documents make the transition from PS -> DS, then being clear about the elements of that trek seems important. However, I think there's some disagreement about what the minimum criteria might be. Which of the following are required? * date(s) and author(s) of report (parts) (assertions of validity, if author disclaims knowing) * identity of implementations (to what detail) * assertions about independence of implementations (and licensing process for IPR) * list of features tested * success of interoperability for each feature identifying the implementations, or counting them or asserting that there are many What else should be required? How about if I update my draft to separate out the description of "content of an implementation report" from the "format for representing that content". Larry . newtrk resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html
- [newtrk] Session chair summary - implementation r… Harald Tveit Alvestrand
- RE: [newtrk] Session chair summary - implementati… Larry Masinter
- Re: [newtrk] Session chair summary - implementati… Brian E Carpenter
- RE: [newtrk] Session chair summary - implementati… Larry Masinter
- Re: [newtrk] Session chair summary - implementati… Brian E Carpenter
- Re: [newtrk] Session chair summary - implementati… Margaret Wasserman
- RE: [newtrk] Session chair summary - implementati… Larry Masinter
- Re: [newtrk] Session chair summary - implementati… Sam Hartman
- Re: [newtrk] Session chair summary - implementati… Douglas Otis
- [newtrk] scope and granularity of metadocuments: … Larry Masinter
- Re: [newtrk] scope and granularity of metadocumen… Brian E Carpenter
- Re: [newtrk] scope and granularity of metadocumen… Harald Tveit Alvestrand
- Re: [newtrk] scope and granularity of metadocumen… John C Klensin
- Re: [newtrk] scope and granularity of metadocumen… Brian E Carpenter
- Re: [newtrk] scope and granularity of metadocumen… Harald Tveit Alvestrand
- Re: [newtrk] scope and granularity of metadocumen… Douglas Otis
- RE: [newtrk] Session chair summary - implementati… Wijnen, Bert (Bert)