[30] Polk, J. and B. Rosen, "Session Initiation Protocol Location
Conveyance", Work in Progress, July 2005.
[31] Charlton, N., Gasson, M., Gybels, G., Spanner, M., and A. van
Wijk, "User Requirements for the Session Initiation Protocol
(SIP) in Support of Deaf, Hard of Hearing and Speech-impaired
Individuals", RFC 3351, August 2002.
[32] van Wijk, A., "Framework of requirements for real-time text
conversation using SIP", Work in Progress, September 2005.
[33] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
"RTP: A Transport Protocol for Real-Time Applications", STD 64,
RFC 3550, July 2003.
[34] Friedman, T., Caceres, R., and A. Clark, "RTP Control Protocol
Extended Reports (RTCP XR)", RFC 3611, November 2003.
[35] Pendleton, A., "SIP Package for Quality Reporting Event", Work
in Progress, February 2006.
[36] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC
2246, January 1999.
[37] Heinanen, J., Baker, F., Weiss, W., and J. Wroclawski, "Assured
Forwarding PHB Group", RFC 2597, June 1999.
[38] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. Jamin,
"Resource ReSerVation Protocol (RSVP) -- Version 1 Functional
Specification", RFC 2205, September 1997.
[39] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video
Conferences with Minimal Control", STD 65, RFC 3551, July 2003.
[40] ITU-T Recommendation G.711, available online at
http://www.itu.int.
[41] Andersen, S., Duric, A., Astrom, H., Hagen, R., Kleijn, W., and
J. Linden, "Internet Low Bit Rate Codec (iLBC)", RFC 3951,
December 2004.
[42] Duric, A. and S. Andersen, "Real-time Transport Protocol (RTP)
Payload Format for internet Low Bit Rate Codec (iLBC) Speech",
RFC 3952, December 2004.
[43] Herlein, G., et al., "RTP Payload Format for the Speex Codec",
Work in Progress, October 2005.
[44] TIA/EIA-810-A, "Transmission Requirements for Narrowband Voice
over IP and Voice over PCM Digital Wireline Telephones", July
2000.
[45] TIA-EIA-IS-811, "Terminal Equipment - Performance and
Interoperability Requirements for Voice-over-IP (VoIP) Feature
Telephones", July 2000.
[46] Alvestrand, H., "Tags for the Identification of Languages", BCP
47, RFC 3066, January 2001.
[47] Wing, D., "Symmetric RTP and RTCP Considered Helpful", Work in
Progress, October 2004.
[48] Rosenberg, J., Weinberger, J., Huitema, C., and R. Mahy, "STUN -
Simple Traversal of User Datagram Protocol (UDP) Through Network
Address Translators (NATs)", RFC 3489, March 2003.
[49] Jennings, C., "NAT Classification Test Results", Work in
Progress, July 2005.
[50] Rosenberg, J., "Interactive Connectivity Establishment (ICE): A
Methodology for Network Address Translator (NAT) Traversal for
Offer/Answer Protocols", Work in Progress, July 2005.
[51] Boulton, C. and J. Rosenberg, "Best Current Practices for NAT
Traversal for SIP", Work in Progress, October 2005.
[52] P. Eggert, "Sources for time zone and daylight saving time
data." Available at http://www.twinsun.com/tz/tz-link.htm.
[53] Campbell, B. and R. Sparks, "Control of Service Context using
SIP Request-URI", RFC 3087, April 2001.
[54] Mahy, R., "Connection Reuse in the Session Initiation Protocol
(SIP)", Work in Progress, February 2006.
[55] Jennings, C. and R. Mahy, "Managing Client Initiated Connections
in the Session Initiation Protocol", Work in Progress, March
2006.
[56] Petrie, D., "A Framework for SIP User Agent Profile Delivery",
Work in Progress, July 2005.
[57] Jennings, C., "SIP Tutorial: SIP Security", presented at the VON
Spring 2004 conference, March 29, 2004, Santa Clara, CA.
[58] Jennings, C., Peterson, J., and M. Watson, "Private Extensions
to the Session Initiation Protocol (SIP) for Asserted Identity
within Trusted Networks", RFC 3325, November 2002.
[59] Chokhani, S., Ford, W., Sabett, R., Merrill, C., and S. Wu,
"Internet X.509 Public Key Infrastructure Certificate Policy and
Certification Practices Framework", RFC 3647, November 2003.
[60] Jennings, C. and J. Peterson, "Certificate Management Service
for The Session Initiation Protocol (SIP)", Work in Progress,
March 2006.
[61] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions
(S/MIME) Version 3.1 Message Specification", RFC 3851, July
2004.
[62] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)", RFC
3711, March 2004.
[63] Audet, F. and C. Jennings, "NAT Behavioral Requirements for
Unicast UDP", Work in Progress, September 2005.
[64] Jennings, C., "Example call flows using SIP security
mechanisms", Work in Progress, February 2006.
[65] Peterson, J., "Session Initiation Protocol (SIP) Authenticated
Identity Body (AIB) Format", RFC 3893, September 2004.
Author’s Addresses
Henry Sinnreich
Pulver.com
115 Broadhollow Road
Melville, NY 11747, USA
EMail: henry@pulver.com
Phone: +1-631-961-8950
Steven Lass
Verizon
1201 East Arapaho Road
Richardson, TX 75081, USA
EMail: steven.lass@verizonbusiness.com
Phone: +1-972-728-2363
Christian Stredicke
snom technology AG
Gradestrasse, 46
D-12347 Berlin, Germany
EMail: cs@snom.de
Phone: +49(30)39833-0
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).