|
Apologies for the late
additional comment on this document. Based on some earlier
comments I made on the SIP list we made the policyContactURI extensible to
allow in the future the possibility to use other URI schemes for the policy
channel other than SIP and SIPS. I think though that in order
to ensure we don’t have any future backward compatibility issues with
other URI schemes we need to also include in the document a statement that UAs
that receive policyContactURIs with URI schemes they don’t understand in
Policy-Contact headers must ignore those policyContactURIs. Andrew
Allen Manager
Standards Research
In Motion Ltd Office +1
847-793-0861 x20824 BlackBerry
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. |
_______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf