RE: RFC 5378 representation

From: Christian Huitema <huitema at windows.microsoft.com>
To: Fred Baker <fred at cisco.com>, IETF discussion list <ietf at ietf.org>
Date: Fri, 19 Dec 2008 18:02:51 -0800
In-reply-to: <9C69123B-AC66-4435-8880-351CAA12EF8C at cisco.com>
References: <9DFF8BF6-6125-4126-9896-EC0D4E59CE8E at cisco.com> <5F20691E-AC69-4A06-8F3F-1DEB0E3578AE at cisco.com> <9C69123B-AC66-4435-8880-351CAA12EF8C at cisco.com>

On Thursday, December 18, 2008 3:10 PM, Fred Baker wrote:

> So, having just cleared this note with the Trustees, sending it in, and forwarding the note to the IETF > list, I observe http://trustee.ietf.org/docs/Contributor_Non-Exclusive_License_RFC5378.pdf.

Fred,

Some of these RFC were written when you were working for ACC. This is a fairly common situation among us. I have written RFC as an employee of INRIA, Bellcore/Telcordia, and Microsoft. Just curious, did you check with whoever bought ACC's intellectual property rights?

-- Christian Huitema
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Follow-Ups:
- Re: RFC 5378 representation
  - From: Fred Baker

References:
- Fwd: RFC 5378 representation
  - From: Fred Baker
- Re: RFC 5378 representation
  - From: Fred Baker

Prev by Date: Re: where to send RFC 5378 license forms
Next by Date: Re: where to send RFC 5378 license forms
Previous by thread: Re: RFC 5378 representation
Next by thread: Re: RFC 5378 representation
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

RE: RFC 5378 representation

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.