requirement
Click on the red underlined text to get to the source
... indicate that an organization cannot purposely keep an individual
in the dark about patents or patent applications just to avoid the
disclosure requirement. But this requirement should not be
interpreted as requiring the IETF ...
... in the dark about patents or patent applications just to avoid the
disclosure requirement. But this requirement should not be
interpreted as requiring the IETF Contributor or participant (or
...
...
No information or document that is subject to any requirement of
confidentiality or any restriction on its dissemination may be
...
... as MIB and PIB modules), subject to the requirements of
Section 5 (it also being understood that the licenses granted
under this paragraph (E) shall not be deemed to grant any
...
... Contribution. The IETF reserves the right to withdraw or cease using
any Contribution that does not comply with the requirements of
Section 3.4 and Section 3.3 or 4.2.
...
... Requirements from Section 3 ...
...
All RFC Editor Contributions must meet the requirements of Sections
3.1, 3.2, 3.4, 3.5 and 3.6.
...
... IETF
Documents, but subject to the limited exceptions noted in Section
5.2). This requirement protects IETF and its participants from
liabilities connected with these documents. The copyright notice
...
...
A fuller discussion of the rationale behind these requirements is
contained in Section 7.3 below.
...
... IETF
standards track documents and for most IETF non-standards track
documents. There are two exceptions to this requirement: documents
describing proprietary technologies and documents that are
republications of the work of other standards organizations.
...