[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Sip] Record-Route, Path, Service Route, and Multi-Homed Prox ies
>
> So what if we needed to do a re-write for SIGCOMP reasons, or
> SIP/SIPS reasons. It seems that regarding RR is unavoidable. Rgds/gf
>
Perhaps. Could you make the examples more obvious. I'm apparently
suffering from a clue deficiency this morning.
You need to change the record-route header field in response processing
to allow sigcomp? I would think one might compress the R-R like all
(other header fields) but I'm currently not cognizant of a situation
where it would need to be semantically analyzed and changed . . . Of
course I may just not be particularly cognizant at the moment, if ever.
--
Dean
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip
- Prev by Date:
RE: [Sip] Record-Route, Path, Service Route, and Multi-Homed Prox ies
- Next by Date:
RE: [Sip] Record-Route, Path, Service Route, and Multi-Homed Prox ies
- Previous by thread:
RE: [Sip] Record-Route, Path, Service Route, and Multi-Homed Prox ies
- Next by thread:
RE: [Sip] Record-Route, Path, Service Route, and Multi-Homed Prox ies
- Index(es):