RE: FW: IETF copying conditions

From: Paul Hoffman <paul.hoffman at vpnc.org>
To: lrosen at rosenlaw.com, <ietf at ietf.org>
Cc: ipr-wg at ietf.org
Date: Wed, 17 Sep 2008 15:18:45 -0700
In-reply-to: <067b01c9190e$7aaa7dc0$6701a8c0 at LROSENTOSHIBA>
References: <063b01c918ec$e0943e90$6701a8c0 at LROSENTOSHIBA> <p06240607c4f6f5bcac93 at [10.227.68.237]> <064001c918f1$d0a50370$6701a8c0 at LROSENTOSHIBA><p0624060ac4f6fcf65e14 at [10.2 27.68.237]> <48D1735D.8040602 at gmail.com> <067b01c9190e$7aaa7dc0$6701a8c0 at LROSENTOSHIBA>

At 2:43 PM -0700 9/17/08, Lawrence Rosen wrote:
>I'm moving this to ietf at ieft.org. There are important policy implications
>here that the entire community should understand before we let the IPR WG
>decide for us on a policy so opposite to open source and open standards!

Larry, I'm confused. What about the statement that "We don't want to 
see other SDOs publishing *incompatible* versions of our protocols, 
period" is the opposite of the policy of open standards (emphasis 
added)?

Which SDOs that you participate in want to see other SDOs publishing 
*incompatible* versions of their protocols?

--Paul Hoffman, Director
--VPN Consortium
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Follow-Ups:
- RE: FW: IETF copying conditions
  - From: Ian Jackson
- RE: FW: IETF copying conditions
  - From: Lawrence Rosen

References:
- RE: FW: IETF copying conditions
  - From: Lawrence Rosen

Prev by Date: RE: FW: IETF copying conditions
Next by Date: RE: FW: IETF copying conditions
Previous by thread: RE: FW: IETF copying conditions
Next by thread: RE: FW: IETF copying conditions
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: FW: IETF copying conditions

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