server design and the use of URLs and URIs. From SMTP, SIP borrowed a textencoding scheme and header style. For example, SIP reuses SMTP headers such as To, From, Date, and Subject.

SIP is also a protocol still under development. A number of key extensions are still being developed. As a result, this book will contain some references to Internet Drafts instead of RFCs. Implementers must be very careful when working from an Internet Draft as there may be an issued RFC that replaces it, or another Internet Draft may come out in the future to replace it. In short, an understanding of the IETF process and the stage of development of a particular extension may be needed in some areas. In this book, only stable and mature SIP extensions are discussed; the few that have Internet Draft references will likely be published as RFCs around the same time this edition is published.

1.9 Conclusion

This chapter has introduced the Internet, Internet architecture, and standards processes. Various bodies involved in Internet standards including the IETF, IRTF, IESG, and IAB have been discussed, as well as the basics of the Domain Name Service and Uniform Resource Locators and Indicators.

References

[1]Rosenberg, J., H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, and E. Schooler, “SIP: Session Initiation Protocol,” RFC 3261, June 2002.

[2]“Internet Protocol,” RFC 791, 1981.

[3]Deering, S., and R. Hinden, “Internet Protocol, Version 6 (IPv6) Specification,” RFC 1883, 1995.

[4]Wilder, F., A Guide to the TCP/IP Protocol Suite, Norwood, MA: Artech House, 1998.

[5]Rekhter, Y., et al., “Address Allocation for Private Internets,” RFC 1918, February 1996.

[6]Alexander, S., and R. Droms, “DHCP Options and BOOTP Vendor Extensions,” RFC 2132, March 1997.

[7]“Transmission Control Protocol,” RFC 793, 1981.

[8]Postal, J., “User Datagram Protocol,” RFC 768, 1980.

[9]Dierks, T., et al., “The TLS Protocol Version 1.0,” RFC 2246, 1999.

[10]Stewart, R., et al., “Stream Control Transmission Protocol,” RFC 2960, 1999.

[11]Phelan, T., “Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP),” RFC 5238, May 2008.

[12]Schulzrinne, H., “Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers,” RFC 3361, August 2002.

[13]Crocker, D., “Standard for the Format of ARPA Internet Text Messages,” STD 11, RFC 822, August 1982.

[14]Crocker, D., and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” STD 68, RFC 5234, January 2008.

[15]Berners-Lee, T., L. Masinter, and M. McCahill, “Uniform Resource Locators (URL),” RFC 1738, December 1994.

[16]Moats, R., “URN Syntax,” RFC 2141, May 1997.

[17]Mockapetris, P., “Domain Names—Implementation and Specification,” STD 13, RFC 1035, November 1987.

[18]Faltstrom, P., and M. Mealling, “The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM),” RFC 3761, April 2004.

[19]Thomson, S., et al., “DNS Extensions to Support IP Version 6,” RFC 3596, October 2003.

[20]Gulbrandsen, A., P. Vixie, and L. Esibov, “A DNS RR for Specifying the Location of Services (DNS SRV),” RFC 2782, February 2000.

[21]Mealling, M., and R. Daniel, “The Naming Authority Pointer (NAPTR) DNS Resource Record,” RFC 2915, September 2000.

[22]http://www.ietf.org.

[23]Hoffman, P., and S. Harris, “The Tao of IETF—A Novice’s Guide to the Internet Engineering Task Force,” RFC 4677, September 2006.

[24]http://www.iesg.org.

[25]http://www.rfc-editor.org.

[26]http://www.iab.org.

[27]http://www.irtf.org.

[28]http://www.iana.org.

[29]http://www.icann.org.

[30]http://www.w3c.org.

[31]http://www.sipforum.org.

[32]http://www.sipforum.org/sipconnect.

[33]Handley, M., et al., “SIP: Session Initiation Protocol,” RFC 2543, March 1999.