At some point I think we will need to make the following two changes to URI parsing. (I'm not proposing to do this now, but rather to get people thinking about it.)
1. Add "_" to the set of valid characters in host names. Historically, underscores are not allowed in host names. But they are now used at the beginning of labels (components) of DNS names for special purposes. (E.g., for SRV records.) But the new SIP provisioning system is planning on using an underscore in the address to which a phone should subscribe to get configuration updates. This address will appear in the request-URI of a SUBSCRIBE, and it would help if our stack could handle such requests. 2. Allow URNs to be parsed. There is a movement afoot to use URNs for certain special services. The leading example is "urn:service:sos" to route to the local emergency services. While we aren't worrying about supporting these for routing, I can envision them appearing as To-URIs fairly soon. To prevent URNs from triggering 484 errors, I think we should update the Url parser to handle these as having a scheme "UrnUrlScheme", with one of the component accessors returning the remainder of the URN. (E.g., "service:sos".) Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
