On 12/8/10 1:16 PM, Peter Saint-Andre wrote: > On 12/8/10 12:50 PM, =JeffH wrote: > >> Also, given an >> input URI of "im:[email protected]", the derived service type is "sip" >> (since the "im" scheme is defined as an abstract scheme in the SIP >> context by [SIP-IM] (RFC 3428)), and the domain name is again >> "example.net". > > Well, the im: and pres: URIs can result in a derived service type of > "xmpp", too. It depends on what a service has deployed... > > http://tools.ietf.org/html/rfc3860 > > http://www.iana.org/assignments/im-srv-labels/im-srv-labels.xhtml
We can tweak it to: As an example, given an input URI of "sip:alice:pswd@ example.net;transport=tcp?subject=project%20x&priority=urgent", the client derives the service type "sip" from the scheme and the domain name "example.net" from the authority component. Also, given an input URI of "im:[email protected]", the derived service type might be "sip", depending on how the example.net service is deployed (since the "im" scheme [CPIM] is defined as an abstract scheme in the SIP context by [SIP-IM]), and the domain name would again be "example.net". /psa
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ certid mailing list [email protected] https://www.ietf.org/mailman/listinfo/certid
