|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2782 (2000)
|
|
Title:
|
A DNS RR for specifying the location of services (DNS SRV), February 2000.
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation uses a DNS SRV record as defined in this specification.
|
|
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=2782
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
It is a mature document which is based on extensive previous experience. RFC 2782 obsoletes EXPERIMENTAL RFC 2052.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2782 has a status of PROPOSED STANDARD and was published in February 2000. Since then it has been adopted by many Internet protocols (such as LDAP and SIP) and has been deployed over Internet.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
The following file is maintained by ISOC/IETF and has the requested information: http://www.ietf.org/iesg/1rfc_index.txt .
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] ISOC/IETF "Assigned Numbers", RFC 1700, October 1994./
[2] ISOC/IETF "Domain names - concepts and facilities", RFC 1034, November 1987./
[3] ISOC/IETF "Domain names - Implementation and Specification", RFC 1035, November 1987./
[4] ISOC/IETF "Mail routing and the domain system", RFC 974, January 1986./
[5] ISOC/IETF "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997./
[6] ISOC/IETF "Clarifications to the DNS Specification", RFC 2181, July 1997./
[7] ISOC/IETF "Use of DNS Aliases for Network Services", RFC 2219, October 1997./
[8] ISOC/IETF "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997.
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
