Re: IPR and I-D boilerplate

John C Klensin <john+ietf@jck.com> Thu, 27 June 2002 18:23 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06695; Thu, 27 Jun 2002 14:23:55 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA10101 for ietf-outbound.10@loki.ietf.org; Thu, 27 Jun 2002 14:24:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id OAA09997 for <ietf-mainout@loki.ietf.org>; Thu, 27 Jun 2002 14:15:14 -0400 (EDT)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA06082 for ietf-mainout; Thu, 27 Jun 2002 14:14:29 -0400 (EDT)
X-Authentication-Warning: ietf.org: majordom set sender to owner-ietf@ietf.org using -f
Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06073 for <ietf@ietf.org>; Thu, 27 Jun 2002 14:14:25 -0400 (EDT)
Received: from [209.187.148.217] (helo=P2) by psg.com with esmtp (Exim 3.36 #1) id 17NdnN-0002bv-00; Thu, 27 Jun 2002 11:15:05 -0700
Date: Thu, 27 Jun 2002 14:15:03 -0400
From: John C Klensin <john+ietf@jck.com>
To: Lloyd Wood <L.Wood@EIM.SURREY.AC.UK>
cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: IPR and I-D boilerplate
Message-ID: <6518388.1025187303@localhost>
In-Reply-To: <Pine.SOL.4.43.0206271418270.13654-100000@artemis.ee.surrey.ac.uk>
References: <Pine.SOL.4.43.0206271418270.13654-100000@artemis.ee. surrey.ac.uk>
X-Mailer: Mulberry/3.0.0a3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

--On Thursday, 27 June, 2002 14:24 +0100 Lloyd Wood
<l.wood@eim.surrey.ac.uk> wrote:

> Given that a large number of drafts, including even
> draft-bradner-submission-rights-00.txt
> currently end in a boilerplate saying copyright "(year)"
> or an out-of-date year because the boilerplate has been cut
> and pasted from a previous draft, it would be impossible to
> rely on the information that you propose. Draft authors aren't
> generally awfully hot on proofing such details.

ok, so?  (see below)

> The IETF has mailing list records, where draft submissions are
> announced and ideas are recorded. Isn't that sufficient?

I don't think so.  If one is looking for a reliable source of
information, there is typically less of it in a title, and may
be less in an abstract, than the material you point to.  Nor are
those records indexed in any useful way.  But neither, I think,
is the point. 

I'm not a lawyer, I don't play one on television, and I really
hoped to be able to make this suggestion without starting the
"amateur lawyer" loop again.  I haven't said a word about what
can be trusted -- from either a legal or a technical/ "security"
standpoint -- and really don't intend to.  

I made the suggestion because I thought it might be helpful to
offer authors of something that someone else might consider an
invention or  component of one an opportunity to record and
maintain a backtrace.  No requirement.  If a given author can't
be bothered, or can't be bothered to do it accurately, no
problem.

If I'm a potential patent applicant, and I've been working on
something, and I'm acting in good faith (that does happen), and
I run across an I-D that seems to overlap what I'm doing, I'd be
happy to have a hint that it has a publication history.  Whether
that publication history is relevant or authoritative is
something I'll just have to figure out, regardless of what is in
the backchain.  And, as I just told someone in response to a
private note, I'd think, personally, that I'd be much more
likely to skim whatever is in front of me and then try to
initiate a discussion with the author.  I would not try to
derive meaning from the specific dates beyond the observation
that the author considered them relevant.

Now, whether this would be of any use at all in cases where good
faith is questionable, I'll leave to the [real] lawyers.  I'd
think it would be a bit harder to claim first invention or first
publication, with no reference to prior work, if there is an RFC
or active I-D out there that points to an earlier publication
that predates my claim of when I thought of the idea.  I'd also
think it would be harder to make that claim with documents (like
RFCs and many I-Ds) that are picked up by indexing systems than
it would be on the basis of a mailing list announcement of an
I-D, when the mailing list announces hundreds or thousands of
I-Ds a year.   But that is just common sense, not legal advice
or estimates of what lawyers might tell you.

> and if you're going to use ISO 8601 date format, specify it's
> that.

I tend to use that date format when I'm expressing all of
month-day-year and when I don't want to explicitly label it as a
date.  Personal habit... Because I think this should be
voluntary and informal, I think specifying the format of dates
or other details would be a waste of time.  I would strongly
oppose any such rules for I-Ds.  It is conceivable that the RFC
Editor might have rules that they would like to apply for dates
in RFCs, but that is an entirely different issues.

    john