Subject: RE: [Sipping] FW: I-D ACTION:draft-elwell-sipping-update-pai-01.t xt

From: "Elwell, John" <[email-masked]>
Date: Fri, 02 Mar 2007 07:54:38 +0000

Venkatesh,
 
That's true, but I have been careful in my draft to limit the cases where
PAI can be used in a response.
 
John

  _____  

From: Venkatesh [mailto:[email-masked]] 
Sent: 02 March 2007 05:49
To: Elwell, John
Cc: [email-masked]; [email-masked]; Gonzalo Camarillo; Keith
Drage; Dean Willis
Subject: Re: [Sipping] FW: I-D ACTION:draft-elwell-sipping-update-pai-01.txt

John:
 
The proposal to use PAI in responses was first proposed by
draft-venkatar-sipping-called-name-00.txt. I believe there were a number of
issues raised w.r.t a proxy not being able to 'challenge' the identify to
verify the identity and such and thus didn't make much headway. Not sure if
this draft suffers from the same issues. 
 
Thanks,
Venkatesh

On 3/1/07, Elwell, John <[email-masked]
<mailto:[email-masked]> > wrote: 

Since 00 this has been enhanced to clarify the inclusion of
P-Asserted-Identity by a UAC and use of the header field in responses. 

The need for further changes might arise as a result of
draft-munakata-sip-privacy-clarified if that draft is progressed. It may be
necessary for the update to RFC 3325 to mention the new privacy types
defined in that draft. 

A question for the chairs of SIPPING and SIP. Given that a) there is a
strong relationship between this draft and the Munakata draft, and given
also that RFC 3325 is cited as a core SIP specification in the hitchhiker's 
guide, would it make sense for discussions on RFC 3325 update to take place
in the SIP WG?

John

> -----Original Message-----
> From: [email-masked]  <mailto:[email-masked]>
[mailto:[email-masked] <mailto:[email-masked]> ]
> Sent: 28 February 2007 23:50
> To: [email-masked] <mailto:[email-masked]> 
> Subject: I-D ACTION: draft-elwell-sipping-update-pai-01.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>       Title           : The use of Asserted Identity in the 
> Session Initiation Protocol (SIP) UPDATE method
>       Author(s)       : J. Elwell
>       Filename        : draft-elwell-sipping-update-pai-01.txt
>       Pages           : 9
>       Date            : 2007-2-28 
>
> SIP has a mechanism for conveying the asserted identity of the
>    originator of a request by means of the P-Asserted-Identity header
>    field.  This header field is specified for use in requests using a 
>    number of SIP methods, in particular the INVITE method.
> However, RFC
>    3325 does not specify the insertion of this header field by a UAC,
>    does not specify the use of this header field with the SIP UPDATE 
>    method, and is unclear on the use of this header field in
> responses.
>    This document extends RFC 3325 to cover these situations.
>
>    This work is being discussed on the [email-masked]
<mailto:[email-masked]>  mailing list.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-elwell-sipping-updat
<http://www.ietf.org/internet-drafts/draft-elwell-sipping-updat> 
> e-pai-01.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> [email-masked] <mailto:[email-masked]>  with
the word unsubscribe in 
> the body of
> the message.
> You can also visit
> https://www1.ietf.org/mailman/listinfo/I-D-announce
<https://www1.ietf.org/mailman/listinfo/I-D-announce> 
> to change your subscription settings. 
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then 
> "get draft-elwell-sipping-update-pai-01.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html <http://www.ietf.org/shadow.html> 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
<ftp://ftp.ietf.org/ietf/1shadow-sites.txt> 
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>       [email-masked] <mailto:[email-masked]> .
> In the body type:
>       "FILE /internet-drafts/draft-elwell-sipping-update-pai-01.txt".
>
> NOTE: The mail server at ietf.org <http://ietf.org>  can return the
document in 
>       MIME-encoded form by using the "mpack" utility.  To use this
>       feature, insert the command "ENCODING mime" before the "FILE"
>       command.  To decode the response(s), you will need "munpack" or 
>       a MIME-compliant mail reader.  Different MIME-compliant
> mail readers
>       exhibit different behavior, especially when dealing with
>       "multipart" MIME messages (i.e. documents which have been split 
>       up into multiple messages), so check your local documentation on
>       how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the 
> Internet-Draft.
>

---------- Forwarded message ----------
From: 
To: 
Date: Thu, 01 Mar 2007 07:04:18 +0000
Subject: 

_______________________________________________ 
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
<https://www1.ietf.org/mailman/listinfo/sipping> 
This list is for NEW development of the application of SIP
Use [email-masked]
<mailto:[email-masked]>  for questions on current sip
Use [email-masked] <mailto:[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