Subject: [rohc] Rewriting Record Route by Proxy

From: Ankita Taparia <[email-masked]>
Date: Wed, 14 Jun 2006 11:32:17 +0530

Hi,

Given the example in the rfc 3486 ->

   UAC            P1            P2           UAS

    |(1)INVITE(c) |             |             |
    |------------>| (2) INVITE  |             |
    |             |------------>| (3) INVITE  |
    |             |             |------------>|
    |             |             | (4) 200 OK  |
    |             | (5) 200 OK  |<------------|
    |(6)200 OK(c) |<------------|             |
    |<------------|             |             |
    |             |  (7)ACK(c)  |             |
    |-------------------------->|   (8) ACK   |
    |             |             |------------>|
    |             |             |             |
    |             |             |             |

Is it necessary for the proxy P2 to  rewrite its Record Route Entry in 
order to avoid asymmetric 
compression ? 
 Ideally the proxy P2 should have added the "comp = sigcomp " parameter in 
the  RR header the
first time itself ,  since "comp = sigcomp" implies support and 
willingness . While it influences the use
 of sigcomp in a given case , it dosnt make it mandatory for the other end 
point to send compressed messages . 
So while the UAS in the above case can simply ignore "comp = sigcomp" , 
the UAC can send compressed messages
to  P2. 

Please clarify .

Regards
Ankita Taparia
Intern , FSS

***********************  FSS-Unclassified   ***********************

_______________________________________________
Rohc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/rohc