|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Published 1985-10
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 952 (1985), DoD Internet host table specification specifies functionalities being relevant for the ECI Host IP stack resource API and thus is a normative reference for draft new J.1012 (ex J.dmcd-part3).
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding document is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
long term usage
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
stable
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Obsoletes RFC 810; Updated by RFC 1123
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
1. Feinler, E., Harrenstien, K., Su, Z. and White, V., "Official DoD/
Internet Host Table Specification", RFC-810, Network Information/
Center, SRI International, March 1982./
2. Harrenstien, K., Stahl, M., and Feinler, E., "Hostname Server",/
RFC-953, Network Information Center, SRI International, October/
1985./
3. Kudlick, M. "Host Names Online", RFC-608, Network Information/
Center, SRI International, January 1973./
4. Postel, J., "Internet Protocol", RFC-791, Information Sciences/
Institute, University of Southern California, Marina del Rey,/
September 1981./
5. Postel, J., "Address Mappings", RFC-796, Information Sciences/
Institute, University of Southern California, Marina del Rey,/
September 1981./
6. Postel, J., "Domain Name System Implementation Schedule", RFC-921,/
Information Sciences Institute, University of Southern California,/
Marina del Rey, October 1984./
7. Reynolds, J. and Postel, J., "Assigned Numbers", RFC-943,/
Information Sciences Institute, University of Southern California,/
Marina del Rey, April 1985.
|
|
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):
|
|
|
None
|
|
