[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IANA MIB copyright update (WAS: Protocol Action: 'IETF Rights in Contributions' to BCP)
- To: "mibs (E-mail)" <mibs@ops.ietf.org>
- Subject: IANA MIB copyright update (WAS: Protocol Action: 'IETF Rights in Contributions' to BCP)
- From: "C. M. Heard" <heard@pobox.com>
- Date: Tue, 4 Nov 2003 07:43:09 -0800 (PST)
- In-reply-to: <E1AGlI1-0008Ep-U8@asgard.ietf.org>
MIB module authors --
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
A new version of the MIB review guidelines document that reflects
this change will be issued in the near future.
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.