70 likes | 129 Views
Ideas for ENUM Plugtests. Lawrence Conroy Lwc@roke.co.uk. Plugtests - where and what?. Plugtests can be local or remote Is it useful to be in one place? Plugtests can involve remote elements Clients may need to be remote (Telephone Exchange/Gateway). What is needed for Plugtest?.
E N D
Ideas for ENUM Plugtests Lawrence Conroy Lwc@roke.co.uk
Plugtests - where and what? • Plugtests can be local or remote • Is it useful to be in one place? • Plugtests can involve remote elements • Clients may need to be remote (Telephone Exchange/Gateway)
What is needed for Plugtest? • Client understands data on Server • Server publishes data that a reasonable set of clients will understand • Client (& server) have “sane” defaults • Client (& server) have “sane” defaults in face of problems/stupidities
BCPs – DNS 4 ENUM • What to do if someone breaks these? • What is a BCP, in this context? • UDP/TCP//EDNS0 support in server & client • What happens when intermediary systems are broken? • Do we test compliance to BCP features? • Does no support == failure? • For end systems & servers? • For network environments (including intermediaries)?
BCPs - Experiences • Experiences work covers “sane” defaults • Focus is on ENUM content and intent • Do we test compliance to Experiences features? • What does non-compliance mean?
BCP – TS 102 172 • Classes of client (what is this client intended to do?) • Stand-alone client • Application with embedded client • Remote Client (e.g. SIP proxy) • Other – trigger negotiation of transcoding service, … • Lists of Enumservices to be supported
Profiles? • Will we see profiles specified in ITTs? • Is developing a profile a Plugtest task? • Is it a TYPHON task? • If not, who? • Is a Plugtest proof of profile support? • Do companies care, or will they define their own?