Subject: Re: [Sipping] [Sipping]Questions on draft-ietf-sipping-connect-reuse-reqs-00

From: Rohan Mahy <[email-masked]>
Date: Tue, 20 May 2003 13:09:03 -0700

Hi,

On Thursday, May 15, 2003, at 07:23 AM, Nicole Johnson wrote:

> I have a couple of questions about 
> draft-ietf-sipping-connect-reuse-reqs-00.

> 1.  Intended scope of alias parameter.
>
> Is the aim of this draft to enable connections to be reused within a 
> single
> dialog, or across multiple dialogs, i.e. can an alias learned within 
> the
> scope of one dialog be used in another?  Is the alias parameter valid 
> on
> out-of-dialog requests?

across multiple dialogs.  it would work on out-of-dialog requests (ex: 
OPTIONS).
perhaps these should be explicit requirements?

> 2.  Target address fails to authenticate.
>
> If a server receives a request containing the alias parameter and the 
> target
> address of the request fails authentication, how should the server 
> react?

it should not create the alias.

> It could drop the message, respond to the target address with a "not
> authorized" response, or continue processing the request as if the 
> "alias"
> parameter was not present.  Is there a recommended behaviour?

the behavior for handling the request should then do whatever normally 
happens when a request without an alias parameter arrives with failed 
or missing authentication.  frequently this is fine and will result in 
a digest authentication challenge (401 or 407).

hope this makes sense.

thanks,
-rohan

> Thanks,
> Nicole
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [email-masked] for questions on current sip
> Use [email-masked] for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP