3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W
IETF
Click on the red underlined text to get to the source
...
It is the intent of RMT to re-submit this specification as an IETF
Proposed Standard as soon as the above condition is met.
...
... port number that has been chosen via means outside
the context of the given NormSession. Other IETF data format and
protocol standards exist that may be applied to describe and convey
...
... Internet unless the NORM implementation is adapted
to use another IETF-sanctioned reliable multicast congestion control
...
... Mankin, A., Romanow, A., Bradner, S., and V. Paxson, "IETF Criteria for Evaluating Reliable Multicast Transport and Application Protocols", RFC 2357 ...
...
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights ...
... might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can
be found in BCP 78 ...
... made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can
be found in BCP 78 and BCP 79 ...
...
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.
...