<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.ietf.ipr">
    <title>gmane.ietf.ipr</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6041"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6040"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6039"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6038"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6037"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6036"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6035"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6034"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6033"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6032"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6031"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6030"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6029"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6028"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6027"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6026"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6025"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6024"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6023"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.ietf.ipr/6022"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6041">
    <title>The IPR filing form has a flaw... Patent Assignee's dont alwayscontrol or have licensing authority on them.</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6041</link>
    <description>&lt;pre&gt;  The IPR filing form assumes that the Party the Patent in the filing is 
assigned to also controls the licensing and that is not always true.  
dTo that end - some form of notation or role-specific type statement 
needs to be created for this form as well to meet this specific (and 
more and more common) situation.

Todd Glassey
&lt;/pre&gt;</description>
    <dc:creator>tsg</dc:creator>
    <dc:date>2013-05-21T20:35:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6040">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6040</link>
    <description>&lt;pre&gt;The ONLY way this works is if the previous license to use the earlier 
DRAFT is formally revoked and if not then this is meaningless. If you 
are not formally changing the license to the previous IP by the new 
publication then the limiting power of the new draft to protect the WG 
and its sponsors is vapor... by the way did the sponsor's legal teams 
issue any statement on this? I bet not...

The real issue is whether this august bunch of professionals is able to 
convince the world it never considered these things and plausible 
deniablity applies here too. I personally think you stand a snowball's 
chance in hell but hey... it is what it is.

todd



On 04/26/2013 02:43 PM, Black, David wrote:
&lt;/pre&gt;</description>
    <dc:creator>tsg</dc:creator>
    <dc:date>2013-04-29T17:40:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6039">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6039</link>
    <description>&lt;pre&gt;When the DISCLOSURE in and of itself has an IP Publication License such 
that the IP is published under that license, then any disclosure as you 
put it is in fact a licensing event for IP in that disclosure. So no...

Todd

&lt;/pre&gt;</description>
    <dc:creator>tsg</dc:creator>
    <dc:date>2013-04-29T17:07:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6038">
    <title>Biggest Fake Conference in Computer Science</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6038</link>
    <description>&lt;pre&gt;Biggest Fake Conference in Computer Science


We are researchers from different parts of the world and conducted a study on  
the world’s biggest bogus computer science conference WORLDCOMP 
( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia 
from University of Georgia, USA.


We submitted a fake paper to WORLDCOMP 2011 and again (the same paper 
with a modified title) to WORLDCOMP 2012. This paper had numerous 
fundamental mistakes. Sample statements from that paper include: 

(1). Binary logic is fuzzy logic and vice versa
(2). Pascal developed fuzzy logic
(3). Object oriented languages do not exhibit any polymorphism or inheritance
(4). TCP and IP are synonyms and are part of OSI model 
(5). Distributed systems deal with only one computer
(6). Laptop is an example for a super computer
(7). Operating system is an example for computer hardware


Also, our paper did not express any conceptual meaning.  However, it 
was accepted both the times without any modifications (and without&lt;/pre&gt;</description>
    <dc:creator>johnsonhammond1&lt; at &gt;hushmail.com</dc:creator>
    <dc:date>2013-04-27T17:47:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6037">
    <title>RE: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6037</link>
    <description>&lt;pre&gt;I agree w/Brian - an effective thing to do in this particular case would be
to submit a disclosure against the revised version of the draft stating
that changes to the draft have rendered the previous disclosure no longer
applicable.  That combo of two disclosures turning up in an IPR search on
that draft should lead people to the correct conclusion (no longer applicable).

Thanks,
--David

&lt;/pre&gt;</description>
    <dc:creator>Black, David</dc:creator>
    <dc:date>2013-04-26T21:43:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6036">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6036</link>
    <description>&lt;pre&gt;
I think a bit more is needed, such as

If there is a substantive change to the draft that affects an existing
disclosure, an updated disclosure should be made as soon as reasonably
possible.

     Brian
&lt;/pre&gt;</description>
    <dc:creator>Brian E Carpenter</dc:creator>
    <dc:date>2013-04-26T21:17:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6035">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6035</link>
    <description>&lt;pre&gt;
"Claimants should be aware that as drafts evolve, text may be added or
removed, and it is recommended that they keep this in mind when
composing text for disclosures."
&lt;/pre&gt;</description>
    <dc:creator>Scott Brim</dc:creator>
    <dc:date>2013-04-26T21:12:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6034">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6034</link>
    <description>&lt;pre&gt;
Certainly, but my question was whether we need either a specific rule
or (more likely) a recommended procedure for the case where the
encumbered technology is removed from a draft.

    Brian
&lt;/pre&gt;</description>
    <dc:creator>Brian E Carpenter</dc:creator>
    <dc:date>2013-04-26T21:04:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6033">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6033</link>
    <description>&lt;pre&gt;No William - it doesnt. The issue here is whether the IETF process has 
the potential to be used to create IP Fraud and the answer is of course 
it can.  Any IP licensing process which creates a one-way publication 
and disclosure/use license is an issue if that is true.

The real issue is who pays for that damage.

Todd


On 04/26/2013 01:24 PM, GTW wrote:
&lt;/pre&gt;</description>
    <dc:creator>tsg</dc:creator>
    <dc:date>2013-04-26T21:04:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6032">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6032</link>
    <description>&lt;pre&gt;

Resubmit cleaned-up draft under new name.

Grüße, Carsten
&lt;/pre&gt;</description>
    <dc:creator>Carsten Bormann</dc:creator>
    <dc:date>2013-04-26T20:58:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6031">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6031</link>
    <description>&lt;pre&gt;
That should be handled as an education problem (of both claimants and
IETF participants), not a problem with freedom of what to say in
disclosures.
&lt;/pre&gt;</description>
    <dc:creator>Scott Brim</dc:creator>
    <dc:date>2013-04-26T20:55:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6030">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6030</link>
    <description>&lt;pre&gt;George,

On 27/04/2013 08:24, GTW wrote:

Yes, for someone who follows up the details, there is no issue,
but meanwhile there is the chilling effect of a disclosure that
is objectively no longer relevant. We know from experience that
many IETF participants simply recoil in horror when they see a
disclosure, without looking at the details.

    Brian
&lt;/pre&gt;</description>
    <dc:creator>Brian E Carpenter</dc:creator>
    <dc:date>2013-04-26T20:49:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6029">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6029</link>
    <description>&lt;pre&gt;it depends on what the patent holder has stated in the disclosure.  In this 
case:

"The Patent Holder states that its position with respect to licensing any 
patent claims contained in the patent(s) or patent application(s) disclosed 
above that would necessarily be infringed by implementation of the 
technology required by the relevant IETF specification ("Necessary Patent 
Claims"), for the purpose of implementing such specification"

If no patent claims would necessarily be infringed then ...

George T. Willingmyre, P.E.
President GTW Associates
-----Original Message----- 
From: tsg
Sent: Friday, April 26, 2013 3:50 PM
To: ipr-wg&amp;lt; at &amp;gt;ietf.org
Subject: Re: Status of a disclosure when technology is removed from a draft?

Brian - the IETF published with a permanent and non revokable license to
use the first IP publication. Now that it has a piece of objectionable
IPR in it - its too late. The cat is already out of the bag and based on
the license there is an issue.

todd


On 04/26/2013 12:44 PM, Brian E Carpen&lt;/pre&gt;</description>
    <dc:creator>GTW</dc:creator>
    <dc:date>2013-04-26T20:24:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6028">
    <title>Re: Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6028</link>
    <description>&lt;pre&gt;Brian - the IETF published with a permanent and non revokable license to 
use the first IP publication. Now that it has a piece of objectionable 
IPR in it - its too late. The cat is already out of the bag and based on 
the license there is an issue.

todd


On 04/26/2013 12:44 PM, Brian E Carpenter wrote:
&lt;/pre&gt;</description>
    <dc:creator>tsg</dc:creator>
    <dc:date>2013-04-26T19:50:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6027">
    <title>Status of a disclosure when technology is removed from a draft?</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6027</link>
    <description>&lt;pre&gt;Hi,

A case has just occurred of the following sequence:

1. A draft is posted that contains an algorithm;
2. A corresponding IPR disclosure is posted;
3. After WG discussion, the draft is updated with the algorithm removed.

What next? The IPR disclosure is still there. Normally, we assume
that the disclosure remains relevant to following versions of the
draft without being re-posted each time. (In fact, do we even expect
a repeat disclosure for the eventual RFC? I don't think so.)

Is there a need for a formal rule for this case?

And what should the IPR holder do now? If they do nothing, the
updated draft might be assumed to be encumbered.

(FYI the draft is draft-krishnan-opsawg-large-flow-load-balancing
and the disclosure is https://datatracker.ietf.org/ipr/2060/ .)

    Brian
&lt;/pre&gt;</description>
    <dc:creator>Brian E Carpenter</dc:creator>
    <dc:date>2013-04-26T19:44:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6026">
    <title>Re: 1.k in draft-bradner-rfc3979bis-04: scope of "participation"</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6026</link>
    <description>&lt;pre&gt;
Why not just require all parties to register and lose the entire 
potential for this problem. Why does the IETF need anonymity in its IP 
suppliers?

No other organization on earth uses this model and bluntly - none of the 
commercial or otherwise players can participate in that type of behavior 
in the real world so why is it necessary here?

It isnt about tradition - because today's IETF has NOTHING TO DO WITH 
THE IETF's ROOTS, it is a completely different animal and it works on 
leading edge protocols and processes instead of being a place where 
protocols which were already in existence are standardized and 
interoperability ensured between the various versions available to the 
consumer.

So again - why is anonymity necessary?

Todd

&lt;/pre&gt;</description>
    <dc:creator>tsg</dc:creator>
    <dc:date>2013-04-18T12:45:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6025">
    <title>Re: 1.k in draft-bradner-rfc3979bis-04: scope of "participation"</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6025</link>
    <description>&lt;pre&gt;

FWIW, I agree with what Thomas says above.

Jari
&lt;/pre&gt;</description>
    <dc:creator>Jari Arkko</dc:creator>
    <dc:date>2013-04-18T12:03:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6024">
    <title>Q: do we have any IETF Publication Mirror and Mailing List RetentionRequirements.</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6024</link>
    <description>&lt;pre&gt;Folks
In regard to IETF Mailing List Archives and WG operations... what is the 
period of retention? Also is it possible this needs to also apply to the 
document mirrors?

So there are some issues we need to pull out and put on the list of 
things we need to deal with in IETF participation. The issue I want to 
bring up here pertains to RECORD RETENTION and AVAILABILITY POLICY for 
both the submissions and for the WG Mirrors.

Documents and Mailing Lists must be retained for seven years (7 years)
============================================
As to why there are legal tax issues for needing to prove participation 
in the IETF and so since as much as  75% of its participants today (we 
figure it actually may be higher) from the commercial world are using 
tax write-downs under employee benefits to support IETF costing, so the 
ability to prove that participation for the full tax-document retention 
period just became a real issue.

What does this mean for WG's who outsource that? -
============================&lt;/pre&gt;</description>
    <dc:creator>tsg</dc:creator>
    <dc:date>2013-04-15T17:16:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6023">
    <title>Re: 1.k in draft-bradner-rfc3979bis-04: scope of "participation"</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6023</link>
    <description>&lt;pre&gt;
Why? - are they not practicing as a fiduciary in some form if they 
represent someone else? If they represent their own IP Interests - and 
they are there harvesting IP for other projects (through their exposure 
if nothing else) then there is a disclosure requirement one would think.

Again this all boils down to the idea that there can be no lurkers - 
everything and everyone must be out in the public for all to see - total 
transparency.

Todd


 inute presentation slot?
&lt;/pre&gt;</description>
    <dc:creator>tsg</dc:creator>
    <dc:date>2013-04-15T15:40:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6022">
    <title>RE: 1.k in draft-bradner-rfc3979bis-04: scope of "participation"</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6022</link>
    <description>&lt;pre&gt;


+2


I believe that obligation to disclose needs to stay scoped to the actual participation. Otherwise, folk may find themselves obligated to disclose in areas where they really are not paying attention at all and will not realistically know they need to disclose. This appears to place new burdens on a participatant.

For example, participating in one discussion in a meeting could obligate an individual to disclose in a bunch of areas where they practically have no knowledge (they may have knowledge of IPR, but not know it covers some document they haven't even read).  I do not think it is advisable or practical to place obligations on individuals that are not "making a contribution", per the traditional definition.

Consider WGs that have a relatively large scope, where an individual only has interest in one or two documents/technologies. The individual does not care about (or follow) everything the WG is involved in (or happens to discuss during a specific meeting). Look at a WG like DHCP, where one fin&lt;/pre&gt;</description>
    <dc:creator>Michael Cameron</dc:creator>
    <dc:date>2013-04-15T14:46:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.ietf.ipr/6021">
    <title>Re: 1.k in draft-bradner-rfc3979bis-04: scope of "participation"</title>
    <link>http://permalink.gmane.org/gmane.ietf.ipr/6021</link>
    <description>&lt;pre&gt;I was not able to attend the BOF, so was not able to participate
there.

Barry Leiba &amp;lt;barryleiba&amp;lt; at &amp;gt;computer.org&amp;gt; writes:



+1.


I believe that obligation to disclose needs to stay scoped to the
actual participation. Otherwise, folk may find themselves obligated to
disclose in areas where they really are not paying attention at all
and will not realistically know they need to disclose. This appears to
place new burdens on a participatant.

For example, participating in one discussion in a meeting could
obligate an individual to disclose in a bunch of areas where they
practically have no knowledge (they may have knowledge of IPR, but not
know it covers some document they haven't even read).  I do not think
it is advisable or practical to place obligations on individuals that
are not "making a contribution", per the traditional definition.

Consider WGs that have a relatively large scope, where an individual
only has interest in one or two documents/technologies. The individual
does not care about (or follow) e&lt;/pre&gt;</description>
    <dc:creator>Thomas Narten</dc:creator>
    <dc:date>2013-04-15T14:08:21</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.ietf.ipr">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.ietf.ipr</link>
  </textinput>
</rdf:RDF>
