• MIBs from RFCs

    From Craig Small@21:1/5 to All on Thu Oct 3 00:50:01 2019
    Hello,

    Please CC me, I'm not on debian-legal email list.

    I'm the Debian Developer for net-snmp. This package includes MIB files
    that translate human-readable SNMP parameters into numbers computers can understand. Sort of like a DNS hosts file for SNMP.

    I'm not re-visiting the freeness or otherwise of the RFC documents
    themselves. Let's all agree that the license of the RFCs is still non-free
    as per [1].

    Way back in 2008, a bug was put on net-snmp [2] saying that the MIB files
    used a non-free license. The offending MIB files based on RFCs were removed.

    To use a specific example, the reasoning was we couldn't put, say SNMPv2-MIB.txt[3] into net-snmp in main because they have in that file:
    Copyright (C) The Internet Society (2002). This
    version of this MIB module is part of RFC 3418;
    see the RFC itself for full legal notices.
    which leads us to the problematic RFC license[4].

    So, what's different?

    In 2010 IETF produced their "Copyright Policy and Trust Legal Provisions
    (TLP) Frequently Asked Questions"[5] which (section 3) states Code
    Components are licensed under the Simplified BSD license if produced after
    10 November 2008. Code Components between March 2005 to 10 November 2008
    are licensed under something found in 3.3.C in RFC 3978 [5]

    The License to Code components (for items post-November 2008) is found at
    [6]
    Code Components are defined at [7] and include MIB files.

    I think what this all means is:
    * MIB files created from RFCs pre-dating March 2005 are still a problem
    unless the RFC itself has some sort of copyright fix. e.g. no happiness for SNMPv2-MIB.txt which is before that date.
    * MIB files created from RFCs dated March 2005 to 10 November 2008 might be
    OK, depending on what people think of the clauses in 3.3.C in RFC 3978[5]
    * MIB files created from RFCs after 10 November 2008 are licensed as
    Simplified BSD and (assuming the RFC itself has no special restrictions for
    its code components) can go in main.

    I'd like that confirmed by the group here. I think a nice summary could go
    on the wiki at [1] for MIBS and everything else listed at [7].

    - Craig


    1: https://wiki.debian.org/NonFreeIETFDocuments
    2: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498475
    3: http://www.net-snmp.org/docs/mibs/SNMPv2-MIB.txt
    4: https://tools.ietf.org/html/rfc3418#page-26
    5: https://tools.ietf.org/html/rfc3978#section-3.3
    6: https://trustee.ietf.org/documents/IETF-TLP-5_001.html
    7: https://trustee.ietf.org/license-info/Code-Components-List-4-23-09.txt

    <div dir="ltr">Hello,<div><br></div><div>Please CC me, I&#39;m not on debian-legal email list.</div><div><br><div> I&#39;m the Debian Developer for net-snmp. This package includes MIB files that translate human-readable SNMP parameters into numbers
    computers can understand. Sort of like a DNS hosts file for SNMP.</div><div><br></div><div>I&#39;m not re-visiting the freeness or otherwise of the RFC documents themselves. Let&#39;s all agree that the license of the RFCs is still non-free as per [1].</
    <div><br></div><div>Way back in 2008, a bug was put on net-snmp [2] saying that the MIB files used a non-free license. The offending MIB files based on RFCs were removed.</div><div><br></div><div>To use a specific example, the reasoning was we couldn&
    #39;t put, say SNMPv2-MIB.txt[3] into net-snmp in main because they have in that file:</div><div>            Copyright (C) The Internet Society (2002). This<br>             version of this MIB module is part of RFC 3418;<br>           
     see the RFC itself for full legal notices.<br></div><div>which leads us to the problematic RFC license[4].</div><div><br></div><div>So, what&#39;s different?</div><div><br></div><div>In 2010 IETF produced their &quot;Copyright Policy and Trust Legal
    Provisions (TLP) Frequently Asked Questions&quot;[5] which (section 3) states Code Components are licensed under the Simplified BSD license if produced after 10 November 2008. Code Components between March 2005 to 10 November 2008 are licensed under
    something found in 3.3.C in RFC 3978 [5]</div><div><br></div><div>The License to Code components (for items post-November 2008) is found at [6]</div><div>Code Components are defined at [7] and include MIB files.</div><div><br></div><div>I think what
    this all means is:</div><div>* MIB files created from RFCs pre-dating March 2005 are still a problem unless the RFC itself has some sort of copyright fix. e.g. no happiness for SNMPv2-MIB.txt which is before that date.</div><div>* MIB files created from
    RFCs dated March 2005 to 10 November 2008 might be OK, depending on what people think of the clauses in 3.3.C in RFC 3978[5]</div><div>* MIB files created from RFCs after 10 November 2008 are licensed as Simplified BSD and (assuming the RFC itself has no
    special restrictions for its code components) can go in main.</div><div><br></div><div>I&#39;d like that confirmed by the group here. I think a nice summary could go on the wiki at [1] for MIBS and everything else listed at [7].</div><div><br></div><div>
    - Craig</div><div><br></div><div><br></div><div>1: <a href="https://wiki.debian.org/NonFreeIETFDocuments">https://wiki.debian.org/NonFreeIETFDocuments</a></div><div>2: <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498475">https://bugs.
    debian.org/cgi-bin/bugreport.cgi?bug=498475</a></div><div>3: <a href="http://www.net-snmp.org/docs/mibs/SNMPv2-MIB.txt">http://www.net-snmp.org/docs/mibs/SNMPv2-MIB.txt</a></div><div>4: <a href="https://tools.ietf.org/html/rfc3418#page-26">https://
    tools.ietf.org/html/rfc3418#page-26</a></div><div>5: <a href="https://tools.ietf.org/html/rfc3978#section-3.3">https://tools.ietf.org/html/rfc3978#section-3.3</a></div><div>6: <a href="https://trustee.ietf.org/documents/IETF-TLP-5_001.html">https://
    trustee.ietf.org/documents/IETF-TLP-5_001.html</a></div><div>7: <a href="https://trustee.ietf.org/license-info/Code-Components-List-4-23-09.txt">https://trustee.ietf.org/license-info/Code-Components-List-4-23-09.txt</a></div><div><br></div><div><br></
    </div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Wise@21:1/5 to All on Thu Oct 3 06:50:01 2019
    On Thu, Oct 3, 2019 at 6:45 AM Craig Small wrote:

    I'm the Debian Developer for net-snmp. This package includes MIB files that translate human-readable SNMP parameters into numbers computers can understand. Sort of like a DNS hosts file for SNMP.

    These sound like things that should not be copyrightable, I guess due
    to the inclusion of descriptions that they are though.

    * MIB files created from RFCs dated March 2005 to 10 November 2008 might be OK, depending on what people think of the clauses in 3.3.C in RFC 3978[5]

    This RFC appears to be only about what contributors to RFCs grant to
    the IETF, not the general public?

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)