1.
|
Clear description of the referenced document:
|
|
Name:
|
IETF RFC 3398 (2002)
|
Title:
|
Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping
|
|
2.
|
Status of approval:
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
3.
|
Justification for the specific reference:
|
|
Q.CDIV refers to overall specification of IETF RFC 3398 (2002) for CDIV requirements.
|
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=3398
|
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:
|
|
18. Normative References/
/
[1] 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./
/
[2] Bradner, S., "Key words for use in RFCs to indicate requirement/
levels", BCP 14, RFC 2119, March 1997./
/
[3] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, F.,/
Watson, M. and M. Zonoun, "MIME media types for ISUP and QSIG/
objects", RFC 3204, December 2001./
/
[4] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part Two: Media Types", RFC 2046, November/
1996./
/
[5] Schulzrinne, H. and S. Petrack, "RTP Payload for DTMF Digits,/
Telephony Tones and Telephony Signals", RFC 2833, May 2000./
/
[6] Donovan, S., "The SIP INFO Method", RFC 2976, October 2000./
/
[7] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806, April/
2000./
/
[8] Faltstrom, P., "E.164 number and DNS", RFC 2916, September 2000./
/
[9] Schulzrinne, H., Camarillo, G. and D. Oran, "The Reason Header/
Field for the Session Initiation Protocol", RFC 3326, December/
2002./
/
[9A] Vemuri, A. and J. Peterson, "Session Initiation Protocol for/
Telephones (SIP-T): Context and Architectures", BCP 63, RFC/
3372, September 2002./
/
[9B] Peterson, J., "A Privacy Mechanism for the Session Initiation/
Protocol (SIP)", RFC 3323, November 2002./
/
19. Non-Normative References/
/
[10] International Telecommunications Union, "Application of the ISDN/
user part of CCITT Signaling System No. 7 for international ISDN/
interconnection", ITU-T Q.767, February 1991,/
http://www.itu.int./
/
[11] American National Standards Institute, "Signaling System No. 7;/
ISDN User Part", ANSI T1.113, January 1995,/
http://www.itu.int./
/
[12] International Telecommunications Union, "Signaling System No. 7;/
ISDN User Part Signaling procedures", ITU-T Q.764, December/
1999, http://www.itu.int./
/
[13] International Telecommunications Union, "Abnormal conditions -/
Special release", ITU-T Q.118, September 1997,/
http://www.itu.int./
/
[14] International Telecommunications Union, "Specifications of/
Signaling System No. 7 - ISDN supplementary services", ITU-T/
Q.737, June 1997, http://www.itu.int./
/
[15] International Telecommunications Union, "Usage of cause location/
in the Digital Subscriber Signaling System No. 1 and the/
Signaling System No. 7 ISDN User Part", ITU-T Q.850, May 1998,/
http://www.itu.int./
/
[16] International Telecommunications Union, "The international/
public telecommunications numbering plan", ITU-T E.164, May/
1997, http://www.itu.int./
/
[17] International Telecommunications Union, "Formats and codes of/
the ISDN User Part of Signaling System No. 7", ITU-T Q.763,/
December 1999, http://www.itu.int./
/
[18] Rosenberg, J. and H. Schulzrinne, "Reliability of Provisional/
Responses in SIP", RFC 3262, June 2002./
/
[19] Stewart, R., "Stream Control Transmission Protocol", RFC 2960,/
October 2000./
/
[20] Rosenberg, J., "The Session Initiation Protocol (SIP) UPDATE/
Method", RFC 3311, October 2002./
/
[21] Yu, J., "Extensions to the 'tel' and 'fax' URL in support of/
Number Portability and Freephone Service", Work in Progress./
|
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
|
|