RE: Fwd: New Version Notification for draft-bradner-rfc3979bis-05.txt

Michael Cameron <michael.cameron@ericsson.com> Thu, 27 June 2013 16:11 UTC

Return-Path: <michael.cameron@ericsson.com>
X-Original-To: ipr-wg@ietfa.amsl.com
Delivered-To: ipr-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15F2C21F9E66 for <ipr-wg@ietfa.amsl.com>; Thu, 27 Jun 2013 09:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lc1ieIP022Yc for <ipr-wg@ietfa.amsl.com>; Thu, 27 Jun 2013 09:11:22 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 6563521F9E1F for <ipr-wg@ietf.org>; Thu, 27 Jun 2013 09:11:19 -0700 (PDT)
X-AuditID: c6180641-b7f5b6d000002d97-07-51cc6426232a
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 18.33.11671.6246CC15; Thu, 27 Jun 2013 18:11:18 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0328.009; Thu, 27 Jun 2013 12:11:17 -0400
From: Michael Cameron <michael.cameron@ericsson.com>
To: "ipr-wg@ietf.org" <ipr-wg@ietf.org>
Subject: RE: Fwd: New Version Notification for draft-bradner-rfc3979bis-05.txt
Thread-Topic: Fwd: New Version Notification for draft-bradner-rfc3979bis-05.txt
Thread-Index: AQHOcssOB4YjeMQxC0SxYwzfacJAEJlJN1iAgABln7A=
Date: Thu, 27 Jun 2013 16:11:17 +0000
Message-ID: <36BAA6A693139D4BBCB37CCCA660E08A1A066C@eusaamb101.ericsson.se>
References: <20130612152002.27844.95337.idtracker@ietfa.amsl.com> <67F8B04D-2636-4446-9D1C-DCE0A1A2E0C5@harvard.edu> <201306121641.r5CGfJ81012027@cichlid.raleigh.ibm.com> <51CB837A.7080701@gmail.com> <8D3D17ACE214DC429325B2B98F3AE71298332C14@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71298332C14@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOLMWRmVeSWpSXmKPExsUyuXRPiK5ayplAgzWd2hZvP3xhdmD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRm/fGtaC5siKr09msjYwvnftYuTkkBAwkXh84h8jhC0mceHe erYuRi4OIYGjjBIb1uxngXCWM0pM2LwHyOHgYAPqeP6MBaRBREBdouHYT1YQW1ggQGLlhofM EPFAie6ZHVA1VhKPf1wHs1kEVCUaFjewg9i8At4SMx9OAasXEuhlkriwyhrE5hTwktjXuoAN xGYEOuj7qTVMIDazgLjErSfzmSAOFZBYsuc8M4QtKvHy8T9WCFtZ4vucRywQ9ToSC3Z/YoOw tSWWLXzNDLFXUOLkzCcsExhFZyEZOwtJyywkLbOQtCxgZFnFyFFanFqWm25kuIkRGPjHJNgc dzAu+GR5iFGag0VJnHeD3plAIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYyzVfIq67n3i3M2 cbzxNrHe96Y1ZK7sjSW3i499OLs2j5Wv5bt8TXaT9JzMWUsF4ji/8Tx7cVVTce7jP097J+68 vdxA6acBuwzLd8HO+X2cSxUe7VI9qrHnkcCN7EPWQWfuOqyMdHmfx51xeolWYkbchFlqU2c9 nPP5IGfW+c+B3Y/73946PSdUiaU4I9FQi7moOBEAeJX9wkoCAAA=
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipr-wg>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 16:11:28 -0000

Another vote for dropping the "Without limiting..." sentence.

Before addressing the issue of whether "participating" in part of a live session means participating in the entire live session, we should confirm what "participating" means. Merely signing the blue sheet at a live session does not necessarily mean that a person is participating in that session.  In other words, implicit in the term participating is the requirement that one is trying to influence the outcome of an IETF standards process. As I recall, this tracks with what was agreed in Orlando--that participating requires more than passive observation at a live IETF meeting, just as merely receiving e-mails from a WG Discussion List does not mean one has met the standard for participating.

The focus should be on those who are actively influencing the outcome of discussions related to an IETF standards process (whether by formal Contributions, comments to the WG list and/or speaking at the microphone at an IETF session)  Most IETF attendees are interested in only a subset of the many sessions available at a live IETF Meeting--they often passively attend other sessions out of curiosity and/or to inform their work in the WGs in which they are participating (as defined above). As a result, in any particular live session there may be more passive attendees in the room compared to the active participants. Imposing IPR disclosure obligations on passive attendees would tend to discourage their attendance and dampen cross-collaboration and sharing of ideas across WGs. 

Thanks,
--Mike

-----Original Message-----
From: ipr-wg-bounces@ietf.org [mailto:ipr-wg-bounces@ietf.org] On Behalf Of Black, David
Sent: Wednesday, June 26, 2013 11:15 PM
To: Brian E Carpenter
Cc: ipr-wg@ietf.org
Subject: RE: Fwd: New Version Notification for draft-bradner-rfc3979bis-05.txt

> > Looking at the diffs, the new version still seems not quite right to 
> > me. There was wording introduced in the -04 version that is still in 
> > the new revision. Specifically:
> >
> >>    k. "Participating in an IETF discussion or activity": means making a
> >>       Contribution, as described above, or in any other way acting in
> >>       order to influence the outcome of a discussion relating to the
> >>       IETF Standards Process.  Without limiting the generality of the
> >>       foregoing, participating in any part of a session at a live IETF
> >>       meeting is deemed to mean participating in the entire session.
> >
> > Per discussion we had since Orlando, I don't think we don't want to 
> > say or imply that participating in one part of a meeting 
> > automatically implies participating "in the entire session".
> 
> That's fair comment, but who decides where to draw the line? "In the 
> entire session" is about the only fully objective criterion. 
> Alternatives such as "participating in part of the discussion of a given topic...
> is deemed to mean participating in all discussion of that topic" seem 
> to be too elastic to be much use (or would at any rate be something to 
> be argued over during litigation).

Uhm - "in any other way acting in order to influence" is not objective.
Having the session scope be objective does not result in a fully objective criterion, so I'd just drop the "Without limiting ..." sentence.

> > Another way to look at it, it seems to me that the real obligation 
> > is already (and has been) well defined in 5.1.1 A:
> >
> >>  A. Any Contributor who reasonably and personally knows of IPR meeting
> >>       the conditions of Section 5.6 which the Contributor believes
> >>       Covers or may ultimately Cover his or her written Contribution
> >>       (other than a Contribution that is not intended to be used as an
> >>       input into the IETF Standards Process), or which the Contributor
> >>       reasonably and personally knows his or her employer or sponsor may
> >>       assert against Implementing Technologies based on such written
> >>       Contribution, must make a disclosure in accordance with this
> >>       Section 5.
> >
> > Why is the above not sufficient?

It's limited to written contributions.  The k text above also covers influencing discussions.  

Thanks,
--David

> -----Original Message-----
> From: ipr-wg-bounces@ietf.org [mailto:ipr-wg-bounces@ietf.org] On 
> Behalf Of Brian E Carpenter
> Sent: Wednesday, June 26, 2013 8:13 PM
> To: Thomas Narten
> Cc: Bradner, Scott; ipr-wg@ietf.org
> Subject: Re: Fwd: New Version Notification for 
> draft-bradner-rfc3979bis-05.txt
> 
> Thomas,
> 
> I've been mulling this over for a couple of weeks. Some comments 
> below:
> 
> On 13/06/2013 04:41, Thomas Narten wrote:
> > Scott,
> >
> > Thanks for getting a revision out we could look at.
> >
> > Looking at the diffs, the new version still seems not quite right to 
> > me. There was wording introduced in the -04 version that is still in 
> > the new revision. Specifically:
> >
> >>    k. "Participating in an IETF discussion or activity": means making a
> >>       Contribution, as described above, or in any other way acting in
> >>       order to influence the outcome of a discussion relating to the
> >>       IETF Standards Process.  Without limiting the generality of the
> >>       foregoing, participating in any part of a session at a live IETF
> >>       meeting is deemed to mean participating in the entire session.
> >
> > Per discussion we had since Orlando, I don't think we don't want to 
> > say or imply that participating in one part of a meeting 
> > automatically implies participating "in the entire session".
> 
> That's fair comment, but who decides where to draw the line? "In the 
> entire session" is about the only fully objective criterion. 
> Alternatives such as "participating in part of the discussion of a given topic...
> is deemed to mean participating in all discussion of that topic" seem 
> to be too elastic to be much use (or would at any rate be something to 
> be argued over during litigation).
> 
> >
> > "Participation" (in the sense of defining a "contribution") needs to 
> > be scoped to the topic under discussion. An entire session can cover 
> > very many completely different topics (e.g., completely different 
> > drafts).
> >
> > The "participating in an IETF discussion or activity" definition is 
> > new to this ID. It does not appear in RFC 3979.
> 
> True, but the word "participating" without a definition was clearly 
> confusing.
> 
> >
> > In thinking about how to fix the language, I think the issue is that 
> > adding a new definition of "participating in", is effectively 
> > bordering on redefining what "making a contribution" is. But we 
> > already have a definition for that. If that defintion is not 
> > sufficient, what is missing from it? And if there is a problem, 
> > shouldn't we further clarify that definition then?
> 
> The best fix I can think of is to get rid of the word "participating"
> completely, with whatever deletions and rewriting that leads to.
> 
> >
> > When defining a contribution (or "participating in an IETF 
> > discussion or activity") one really has to scope that to the 
> > specific activity one is participating in. But, that really needs to 
> > be about a topic or technology (i.e., in many/most cases a specific 
> > ID -- which is where the disclosure obligation really kicks in).  If 
> > you try to apply the scope to a more artificial boundary (e.g., a WG 
> > "meeting" or "session"), I think we may be getting into trouble.
> >
> > Another way to look at it, it seems to me that the real obligation 
> > is already (and has been) well defined in 5.1.1 A:
> >
> >>  A. Any Contributor who reasonably and personally knows of IPR meeting
> >>       the conditions of Section 5.6 which the Contributor believes
> >>       Covers or may ultimately Cover his or her written Contribution
> >>       (other than a Contribution that is not intended to be used as an
> >>       input into the IETF Standards Process), or which the Contributor
> >>       reasonably and personally knows his or her employer or sponsor may
> >>       assert against Implementing Technologies based on such written
> >>       Contribution, must make a disclosure in accordance with this
> >>       Section 5.
> >
> > Why is the above not sufficient?
> 
> Good point; maybe we are simply trying to say too much.
> 
>    Brian
> 
> > To further tease apart the proposed text in -05:
> >
> >>    k. "Participating in an IETF discussion or activity": means making a
> >>       Contribution, as described above, or in any other way acting in
> >>       order to influence the outcome of a discussion relating to the
> >>       IETF Standards Process.
> >
> > This seems OK, not really adding anything new.
> >
> >>       Without limiting the generality of the
> >>       foregoing, participating in any part of a session at a live IETF
> >>       meeting is deemed to mean participating in the entire session.
> >
> > Per above, IMO too broad.
> >
> >>       Sending a message to an email list is deemed to constitute
> >>       participating in the associated email discussion for its entire
> >>       duration and any successor email discussions.
> >
> > I'm OK with the first part, but only partly with the latter. How 
> > does one define "for its entire duration"? If we are talking about a 
> > thread that continues for a few days or a couple of weeks, no 
> > problem. If a thread goes on for several months (rare, but not 
> > unheard of), and someone tunes out and stops participating, what 
> > does that imply? And defining what constitues an "email discussion for its entire duration"
> > is a judgement call (i.e., what happens if the subject changes few
> > times??)
> >
> >> In contrast,
> >>       attending a session at a live IETF meeting without making a
> >>       Contribution or acting in order to influence the outcome of a
> >>       discussion relating to the IETF Standards Process, subscribing to
> >>       an IETF email list or reading messages received from an IETF email
> >>       list without responding or sending any messages to the list do not
> >>       constitute participation in the relevant IETF discussion.
> >
> > I think the above is additional clarification that we've come to in 
> > the last few months. I'm fine with keeping this somewhere. But do we 
> > really want to add a new definition of "participation" that at least 
> > partially overlaps with "contribution", when "contribution" is 
> > really the key definition that matters?
> >
> > Thomas
> >
> > _______________________________________________
> > Ipr-wg mailing list
> > Ipr-wg@ietf.org
> > https://www.ietf.org/mailman/listinfo/ipr-wg
> >
> _______________________________________________
> Ipr-wg mailing list
> Ipr-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/ipr-wg

_______________________________________________
Ipr-wg mailing list
Ipr-wg@ietf.org
https://www.ietf.org/mailman/listinfo/ipr-wg