![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
On Mon, 5 Dec 2005, JFC (Jefsey) Morfin wrote: > At 15:50 05/12/2005, Brian E Carpenter wrote: > >Simon, > >You are bit behind real time. We already updated this text. > >http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg01837.html > > Dear Brian, > Great! the three stupid points I am stubbornly interested in are > gathered here! Please read what follows with humour, however the > three issues are serious.
<snip>
> If I copy all the RFCs, sort their content, add a legal blabla paying
> my respects to all those who contributed through the IETF, make an
> open use e-book from them all, class their proposition in some
> orders, updating it when they change, mixing them with other SSDOs
> propositions, etc. translating parts in various languages, adding
> comments on their usage cons and pros and testing, linking the
> various comments people may have made on them, etc. quoting available
> open source/commercial libraries and their variations, etc. and the
> various registry repositories where they can find the values of the
> related parameters, i.e. what the users long for a while, will the
> IAOC sue me and send me to jail as the US DMCA and the French DADVSI would do?
Tounge firmly in cheek: Of course we won't send you to jail. We'll make you come live in a country with no real cheese and a lot of overly oak-y white wine. far worse. ;-)
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.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.