|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
RFC - Internet Standard (August 1980; No errata) - a.k.a. STD 6
|
|
3.
|
Justification for the specific reference:
|
|
|
Annex B (clauses B.7 to B.13) describes a discovery protocol and a service announcement protocol usable with TCP/IP binding. These protocols need UDP, defined in RFC 768, for transmission of multicast (or broadcast) requests and reception of responses.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=768
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since August 1980.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This reference is a standards-track document and is currently in the "Proposed Standard" state. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 768 is a fundamental component of the basic suite of internet protocols and standards.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Postel, J., "Internet Protocol,", RFC 760, January 1980./
[2] Postel, J., "Transmission Control Protocol", RFC 761, January 1980./
[3] Postel, J., "Internet Name Server", IEN 116, August 1979./
[4] Sollins, K., "The TFTP Protocol,", IEN 133, January 1980./
[5] Postel, J., "Assigned Numbers", RFC 762, January 1980.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
If the Study Group decides to make the reference to the RFC, the reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic".
|
