RE: FW: MIB copyright statement

I have not reacted much yet, because I am not good at
copy-right law (or any law for that matter).

But I have some comment/questions inline:

Thanks,
Bert 

> -----Original Message-----
> From: C. M. Heard [mailto:[email protected]]
> Sent: woensdag 30 juli 2003 19:22
> To: [email protected]
> Cc: [email protected]
> Subject: Re: [Bridge-mib] FW: MIB copyright statement
> 
> 
> On Wed, 30 Jul 2003, C. M. Heard wrote:
> > On Wed, 30 Jul 2003, Scott Bradner wrote:
> > > if the IETF is republishing the material it must have a
> > > non-exclusive grant of copyright to do so so the ISOC copyright
> > > is correct - if the IEEE is not granting that non-exclusive
> > > right then the RFC can not be published
> > 
> > Well, it's not obvious that a grant of copyright, as opposed to
> > permission to use the material, is required for republication.
> > 
> > But even if ISOC does get a non-exclusive grant of copyright, the
> > point still stands that the standard abbreviated MIB copyright
> > notice would be misleading since it mentions ISOC only, and not
> > the IEEE, which in this case is the principal copyright holder.
> 
And so we point back to the RFC for the full legal notice.
I would personally have no problem to adapt the text somewhat
to also indicate IEEE copy-right. But which lawyer is goin to
formulate the proper text. The text we now use for MIB modules
has been passed by our IETF lawyer. If we modify it for this
specific MIB module, I guess we need to run it by our lawyer as
well.

> Another point to be noted is that extraction of a MIB module from
> an RFC (or an Internet-Draft) amounts to creation of a derivative
> work.  The IEEE can grant permission for the IETF to republish the
> MIB module in an informational RFC without necessarily granting
> permission for the MIB module to be extracted;  that permission
> needs to be granted separately.

If the MIB module cannot be extracted because derivative works
are not allowed, then I see no use at all to publish this MIB
document as an RFC. 

An alternative option might be to publish the RFC without the MIB 
module and just include a pointer to the inline MIB module at the
IEEE web site.

Bert