|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 1034 (1987), Domain names - concepts and facilities, specifies functionalities relevant for 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 RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=1034
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
It is a mature document which is based on extensive previous experience as listed in the reference list below.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 1034 has a status of STANDARD and was published in November 1987. Since then it has been widely implemented and became one of the major components of Internet.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
The following file is maintained by ISOC/IETF and has all the requested information: http://www.ietf.org/iesg/1rfc_index.txt . Updated by RFC 1348, RFC 2065, RFC 2535, RFC 1982, RFC 4592, RFC 8020, RFC 2181, RFC 2308, RFC 5936, RFC 4034, RFC 1101, RFC 4033, RFC 4035, RFC 1876, RFC 4343, RFC 1183; Obsoletes RFC 973, RFC 883, RFC 882
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] "Hesiod", Project Athena Technical Plan - Name Service, April 1987, version 1.9./
[2] "Internet Name Server", IEN-116, USC/Information Sciences Institute, August 1979./
[3] "Notable Computer Networks", Communications of the ACM, October 1986, volume 29, number 10./
[4] ISOC/IETF "NAME/FINGER", RFC-742, Network Information Center, SRI International, December 1977./
[5] ISOC/IETF "User Datagram Protocol", RFC-768, USC/Information Sciences Institute, August 1980./
[6] ISOC/IETF "Transmission Control Protocol", RFC-793, USC/Information Sciences Institute, September 1981./
[7] ISOC/IETF "Internet Name Domains", RFC-799, COMSAT, September 1981./
[8] ISOC/IETF "Computer Mail Meeting Notes", RFC-805, USC/Information Sciences Institute, February 1982./
[9] ISOC/IETF "DOD Internet Host Table Specification", RFC-810, Network Information Center, SRI International, March 1982./
[10] ISOC/IETF "Hostnames Server", RFC-811, Network Information Center, SRI International, March 1982./
[11] ISOC/IETF "NICNAME/WHOIS", RFC-812, Network Information Center, SRI International, March 1982./
[12] ISOC/IETF "The Domain Naming Convention for Internet User Applications", RFC-819, Network Information Center, SRI International, August 1982./
[13] ISOC/IETF "Simple Mail Transfer Protocol", RFC-821, USC/Information Sciences Institute, August 1980./
[14] ISOC/IETF "A Distributed System for Internet Name Service", RFC-830, Network Information Center, SRI International, October 1982./
[15] ISOC/IETF "Domain names - Concepts and Facilities," RFC-882, USC/Information Sciences Institute, November 1983./
[16] ISOC/IETF "Domain names - Implementation and Specification," RFC-883, USC/Information Sciences Institute, November 1983./
[17] ISOC/IETF "Domain Requirements", RFC-920, USC/Information Sciences Institute October 1984./
[18] ISOC/IETF "DoD Internet Host Table Specification", RFC-952, SRI, October 1985./
[19] ISOC/IETF "HOSTNAME Server", RFC-953, SRI, October 1985./
[20] ISOC/IETF "Domain System Changes and Observations", RFC-973, USC/Information Sciences Institute, January 1986./
[21] ISOC/IETF "Mail routing and the domain system", RFC-974, CSNET CIC BBN Labs, January 1986./
[22] ISOC/IETF "Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and Methods", RFC-1001, March 1987./
[23] ISOC/IETF "Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed Specifications", RFC-1002, March 1987./
[24] ISOC/IETF "Assigned Numbers", RFC-1010, USC/Information Sciences Institute, May 1987./
[25] ISOC/IETF "MILNET Name Domain Transition", RFC-1031, November 1987./
[26] ISOC/IETF "Establishing a Domain - Guidelines for Administrators", RFC-1032, November 1987./
[27] ISOC/IETF "Domain Administrators Operations Guide", RFC-1033, November 1987./
[28] "The CSNET Name Server", Computer Networks, vol 6, nr 3, July 1982.
|
|
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".
|
|
