Browse Prior Art Database

Compressing the Session Initiation Protocol (SIP) (RFC3486)

IP.com Disclosure Number: IPCOM000011488D
Original Publication Date: 2003-Feb-01
Included in the Prior Art Database: 2003-Feb-26
Document File: 13 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Camarillo: AUTHOR

Abstract

This document describes a mechanism to signal that compression is desired for one or more Session Initiation Protocol (SIP) messages. It also states when it is appropriate to send compressed SIP messages to a SIP entity.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � G. Camarillo

Request for Comments: 3486� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � Ericsson

Category: Standards Track� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � February 2003

� � � � � � � � � � Compressing the Session Initiation Protocol (SIP)

Status of this Memo

� � This document specifies an Internet standards track protocol for the

� � Internet community, and requests discussion and suggestions for

� � improvements.� Please refer to the current edition of the "Internet

� � Official Protocol Standards" (STD 1) for the standardization state

� � and status of this protocol.� Distribution of this memo is unlimited.

Copyright Notice

� � Copyright (C) The Internet Society (2003).� All Rights Reserved.

Abstract

� � This document describes a mechanism to signal that compression is

� � desired for one or more Session Initiation Protocol (SIP) messages.

� � It also states when it is appropriate to send compressed SIP messages

� � to a SIP entity.

Table of Contents

� � 1.� � Introduction ...............................................� 2

� � 2.� � Overview of operation ......................................� 3

� � 3.� � SigComp implementations for SIP ............................� 3

� � 4.� � Sending a Request to a Server ..............................� 3

� � � � � � � 4.1� � Obtaining a SIP or SIPS URI with comp=sigcomp ........� 4

� � 5.� � Sending a Response to a Client .............................� 5

� � 6.� � Double Record-Routing ......................................� 6

� � 7.� � Error Situations ...........................................� 6

� � 8.� � Augmented BNF ..............................................� 7

� � 9.� � Example ....................................................� 7

� � 10.� Security Considerations .................................... 10

� � 11.� IANA Considerations ........................................ 10

� � 12.� Acknowledgements............................................ 10

� � 13.� Normative References ....................................... 10

� � 14.� Informative References ..................................... 11

� � 15.� Author's Address............................................ 11

� � 16.� Full Copyright Statement.................................... 12

Camarillo� � � � � � � � � � � � � � � � � � Standards Track� � � � � � � � � � � � � � � � � � � � [Page 1]

RFC 3486� � � � � � � � � � � � � � � � � � � Compressing SIP� � � � � � � � � � � � � � � February 2003

1.� � Introduction

� � A SIP [1] client sending a request to a SIP server typically performs

� � a DNS lookup for the domain name of the server.� When NAPTR [4] or

� � SRV [5] records are available for the server, the client can specify

� � the type of service it wants.� The service in this context is the

� � transport protocol to be used by SIP (e.g., UDP, TCP or SCTP).� A SIP

� � server that support...