![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Um, I just looked at that thread, and it was talking more about whether or not SDO's should be allowed to "fork" an RFC specification without getting prior permission from the IETF or not, and worries about "fake" RFC's. That has nothing to do with shoving all of the liabilities associating with assuring that all contributions following the IPR responsibilities onto the I-D author/editors. Maybe you thought it was implicit in the argument, but it certainly wasn't obvious to me. So if your goal was to advance that point of view, it probably wasn't the best strategy as an advocate. Regards, - Ted _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.