Hi Syam, I'm not sure that is what RFC 3325 says - it looks like it must remove that header if the user's privacy settings require it. But there are also cases where it must not remove the header when forwarding to untrusted nodes, and cases where it's recommended that it shouldn't do so.
Section 7 is the important section: " Parties who wish to request the removal of P-Asserted-Identity header fields before they are transmitted to an element that is not trusted may add the "id" privacy token defined in this document to the Privacy header field. The Privacy header field is defined in [6]. If this token is present, proxies MUST remove all the P-Asserted- Identity header fields before forwarding messages to elements that are not trusted. If the Privacy header field value is set to "none" then the proxy MUST NOT remove the P-Asserted-Identity header fields. When a proxy is forwarding the request to an element that is not trusted and there is no Privacy header field, the proxy MAY include the P-Asserted-Identity header field or it MAY remove it. This decision is a policy matter of the Trust Domain and MUST be specified in Spec(T). It is RECOMMENDED that the P-Asserted-Identity header fields SHOULD NOT be removed unless local privacy policies prevent it, because removal may cause services based on Asserted Identity to fail." Rob On 20 September 2013 06:52, Pendyala Syam <[email protected]> wrote: > Hi All, > > I am studing rfc 3325 which says proxy MUST remove all the > P-Asserted-Identity headers while forwarding to next device which is not in > Trust domain. Can somebody please tell me what are the possible problems of > not removing them while forwarding. > > > Thanks > Syam > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
