RFC 3486:Compressing the Session Initiation Protoc...
RFC-Ref

compression


Click on the red underlined text to get to the source

... application layer protocol. Examples of these layers are transport layer security and compression. If DNS was used to discover the availability of these layers for a ...
... transport security and SigComp for signaling compression, would need the 8 DNS entries listed below: ...
... 1. TCP, no security, no compression 2. TCP ...
... 3. TCP, TLS, no compression 4. TCP ...
... 5. SCTP, no security, no compression 6. SCTP ...
... 7. SCTP, TLS, no compression 8. SCTP ...
... an application layer mechanism to express support of signalling compression is needed. Note that for historical reasons both HTTP ...
... A SIP element that supports compression will need to be prepared to receive compressed and uncompressed messages on the same port. It ...


... URI for subsequent requests that are sent through the same outbound proxy using compression. RFC 3261prop ...
... sigcomp in their registrar. All incoming requests for the user will be sent to this SIP URI using compression. ...


... response MUST NOT be compressed. In order to avoid asymmetric compression (i.e., two SIP entities exchanging compressed requests in one direction and uncompressed ...


... times out without having received any response, the client SHOULD retry the same request without using compression. If the compressed request was sent over a TCP connection, the client ...


... parameters described above. The compression URI parameter is a "uri-parameter", as defined by the ...
... 1]): compression-param = "comp=" ("sigcomp" / other-compression) ...
... compression-param = "comp=" ("sigcomp" / other-compression) other-compression = token ...
... sigcomp" / other-compression) other-compression = token ...
... token The Via compression parameter is a "via-extension", as defined by the SIP ABNF ...
... 1]): via-compression = "comp" EQUAL ("sigcomp" / other-compression) ...
... via-compression = "comp" EQUAL ("sigcomp" / other-compression) other-compression = token ...
... sigcomp" / other-compression) other-compression = token ...


... proxy P2 does. Both proxies support compression, but they do not use it by default. UAC ...
... P1 forwards the INVITE (2) to P2. P1 does not use compression by default, so it sends the INVITE uncompressed to P2. ...
... P2 forwards the INVITE (3) to the UAS. P2 supports compression, but it does not use it by default. Therefore, it sends the INVITE ...


... IANA at http://www.iana.org/assignments/sip-parameters when new signalling compression schemes are published in standards track RFCs. The IANA Considerations section of the RFC MUST include the following ...
... number of the publication. o Name of the compression scheme. o Token ...
... registry for the time being is: Compression scheme Token Reference --------------------- --------- --------- ...
... --------------------- --------- --------- Signaling Compression sigcomp RFC 3486prop ...


... Price, R., Bormann, C., Christoffersson, J., Hannu, H., Liu, Z. and J. Rosenberg, "Signaling Compression (SigComp)", RFC 3320prop, January 2003. ...



Google
Web
RFC-Ref