|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3407 (2002)
|
|
Title:
|
Session Description Protocol (SDP) Simple Capability Declaration, October 2002
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
This reference defines a set of Session Description Protocol, SDP attributes that enables SDP to provide minimal and backwards compatibility. V.151 uses this protocol as a means to establish connectivity and ensuring interoperability between peer Gateways.
|
|
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=3407
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since October 2002.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 3407 was published in October, 2002. It 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 3407 is a basic component of the basic suite of internet protocols and standards. Although its publication is recent, it is anticipated that it will be widely used by the internet community.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996./
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[3] Handley, M. and V. Jacobson, "SDP: session description protocol", Request for Comments 2327, April 1998.
|
|
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.
|
