IANA MIB copyright update (WAS: Protocol Action: 'IETF Rights in Contributions' to BCP)

["C. M. Heard" <heard@pobox.com>]

MIB Doctors --

Be aware that the IESG note accompanying the recent announcement of
the IPR documents that update RFC 2026 Section 10 has changed the
copyright notice that goes in IANA-maintained MIB modules from what
is stated in the current MIB review guidelines document

http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-02.txt

My presumption (Bert can correct me if this is wrong) is that the
new IANA MIB copyright text takes effect immediately and should be
applied in forthcoming MIB reviews.

I wish I could promise a quick update to the MIB review guidelines
document, but unfortunately I am still in the aftermath of a move
and the computer that has my nroff tools is still packed away in
boxes.  So it will be a while before I can get to it.  And of course
before we can put that document to bed as a BCP it will be necessary
to rewrite all the copyright stuff to comform to the practices set
forth in the new IPR documents (and hopefully also in the next
version of RFC 2223bis).

Regards,

Mike Heard

On Mon, 3 Nov 2003, The IESG wrote:
> The IESG has approved following documents:
> 
> - 'Guidelines for Working Groups on Intellectual Property Issues '
>    <draft-ietf-ipr-wg-guidelines-05.txt> as an Informational RFC
> - 'IETF Rights in Contributions '
>    <draft-ietf-ipr-submission-rights-08.txt> as a BCP
> - 'Intellectual Property Rights in IETF Technology '
>    <draft-ietf-ipr-technology-rights-12.txt> as a BCP
> 
> These documents are products of the Intellectual Property Rights Working 
> Group. 
> 
> The IESG contact person is Harald Alvestrand.
> 
> Technical summary
> 
>   This set of 3 documents replaces section 10 of RFC 2026, and provides
>   a much more detailed description of the considerations regarding
>   intellectual property that need to be taken into account when working
>   in the IETF.
>   Particular attention is paid to copyright issues and issues concerning
>   requirements for implementation, such as patent licensing.
>   The "Guidelines" document relates useful experience gathered when
>   working with IPR issues in the IETF.
> 
> Working Group summary
> 
>   The working group was chartered to document existing IPR practice in
>   the IETF, and discuss whether updates were needed.
>   After a great deal of debate, a strong consensus emerged that the
>   fundamental IPR practice in the IETF should not be changed at this time.
>   The details of IPR practice were gone over in minute detail, and the
>   documents are believed to represent WG consensus on the practice that
>   the IETF should follow at present.
> 
> Protocol Quality
> 
>    The documents were reviewed for the IESG by Harald Alvestrand.
> 
> RFC EDITOR NOTE:
> 
> In section 5.6 of draft-ietf-ipr-submission-rights, please make the 
> following changes:
> 
> OLD:
> 
>          "Copyright (C) The Internet Society <year>.  The initial
>          version of this MIB module was published in RFC XXXX; for full
>          legal notices see the RFC itself or see:
>          http://www.ietf.org/copyrights/ianamib.html.";
> 
> NEW:
> 
>          "Copyright (C) The Internet Society <year>.  The initial
>          version of this MIB module was published in RFC XXXX; for full
>          legal notices see the RFC itself. Supplementary information
>          may be available on http://www.ietf.org/copyrights/ianamib.html.";
> 
> OLD:
> 
>       Substitute "PIB" for "MIB" in the statement for PIB modules.  In
>       the case of MIB and PIB modules this statement should be placed in
>       the DESCRIPTION clause of the MODULE-IDENTITY macro.
> 
> NEW:
> 
>       For other types of components than "MIB", substitute "MIB module" with
>       an appropriate identifier. In
>       the case of MIB and PIB modules this statement should be placed in
>       the DESCRIPTION clause of the MODULE-IDENTITY macro.
> 
> 
> 
>