|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
In Table B.3: NOTE 3 – The SDP "group" attribute is defined in [IETF RFC 33885888]. The "SRF" semantics attribute within this grouping framework is defined in [IETF RFC 3524].
|
|
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=3524
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[1] Handley, M. and V. Jacobson, "SDP: Session Description/
Protocol", RFC 2327, April 1998./
/
[2] Camarillo, G., Eriksson, G., Holler, J. and H. Schulzrinne,/
"Grouping of Media Lines in the Session Description Protocol/
(SDP)", December 2002./
/
[3] Bradner, S., "Key words for use in RFCs to indicate requirement/
levels", BCP 14, RFC 2119, March 1997./
/
Informative References/
/
[4] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,/
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:/
Session Initiation Protocol", RFC 3261, June 2002./
/
[5] Braden, R., Zhang, L., Berson, S., Herzog, S. and S. Jamin,/
"Resource ReSerVation protocol (RSVP) -- Version 1 Functional/
Specification", RFC 2205, September 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.
|
|
