@techreport{elwell-sipping-update-pai-02,
    number =    {draft-elwell-sipping-update-pai-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-elwell-sipping-update-pai/02/},
    author =    {John Elwell},
    title =     {{Updates to Asserted Identity in the Session Initiation Protocol (SIP)}},
    pagetotal = 9,
    year =      2007,
    month =     nov,
    day =       16,
    abstract =  {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 trusted UAC, does not specify the use of this header field with the SIP UPDATE, MESSAGE or PUBLISH methods, 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 sipping@ietf.org mailing list.},
}