Issues for Telecommunications Service Access and Subscription (TSAS) FTF mailing list

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 4071: Section 5.5 Service Discovery segment

Issue 4071: Section 5.5 Service Discovery segment (tsas-ftf)

TSAS Section 5 - [Optional] Service Access Segments 
Most of this section is not addressed by Parlay 2.1, with the exception of the Service Discovery segment…

Section 5.5 Service Discovery segment 

·	TSAS permits the retailer (Parlay framework) to invoke discovery functions on the service provider (Parlay service supplier).  Only the opposite is supported in Parlay: i.e. the service supplier may invoke discovery functions on the framework.
·	TSAS does not appear to support retrieval of, or selection by, Service Type.  Specifically TSAS does not support the Parlay listServiceTypes and describeServiceType methods, or the Service Type parameter in the Parlay discoverService method.
·	The TSAS get_service_info method has no close equivalent in Parlay. 
·	5.5.1 ServiceDiscovery Interface, discover_services: The desired_properties parameter includes more filtering capabilities (use of Match & Which syntax) than the equivalent parameter in the Parlay discoverService method.
·	5.5.1 ServiceDiscovery Interface, discover_services: The return parameter (services) is a superset of the information returned by the corresponding parameter of the Parlay method; i.e. the latter does not return a service name attribute for each "discovered" service.