IETF
Click on the red underlined text to get to the source
...
This is not an IETF standards-track document [2], and thus the key
words MUST, MUST NOT, SHOULD, and MAY are NOT as in BCP ...
... requirements document, we refer to that document as the "data-format
specification". The second document to be produced should identify
existing IETF protocols that are best used for conveying the data so
formatted, and explain how to package this data in those existing
formats or the document should specify a new protocol ...
...
The IETF has already completed a great deal of research and work into
the areas of networks and security ...
... OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE ...
...
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights ...
...
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license ...
... such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
...
... http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
...
... rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
...