Correct. keep=yes must be in the client Via, in order for the client to
receive it.

Regards,

Christer 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Bharrat, Shaun
Sent: 13. toukokuuta 2008 4:49
To: Dean Willis; [email protected]
Subject: Re: [Sip] Keep draft and manipulation of Via header on-stack

> draft-holmberg-sip-keep-00 section 7 says:
> When an edge proxy that supports the method defined in this 
> specification recieves a SIP REGISTER request which contains a "keep"
> parameter in the topmost Via header the edge proxy MUST add a "yes"  
> value to the "keep" parameter. In addition the edge proxy MAY include 
> a Flow-Timer header field if the associated SIP REGISTER response.
> I think this is the first time I've seen a specification that causes a

> proxy to modify a Via that was already in the request.
> So we really want to do this, or do we want the proxy to be adding its

> own Via with "keep=yes"?

Aside from the received= counter example, I'm not sure that adding the
keep=yes to the proxy's via would even work. Isn't the keep=yes also
used by the *client* to know that STUN is allowed on the SIP port? If
the keep=yes is only on the proxy's via, that is not there in the
response finally seen by the client.

Cheers,
Shaun



_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
[EMAIL PROTECTED] for questions on current sip Use
[EMAIL PROTECTED] for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
[EMAIL PROTECTED] for questions on current sip Use
[EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to