70 likes | 179 Views
Explore the essential features required for the next generation of keyword lookup services, focusing on backward compatibility and future application support. Discuss the potential for a new protocol (e.g., KWLSP) and the relationship with existing services like ENUM and IDN. Consider the syntax, delegation, and the user-centric approach for a convenient and efficient lookup service.
E N D
Requirement of Keyword Xiaodong Lee 李晓東 CNNIC
Two crucial premise • Has backward compatibility • The final lookup service of Internet? NO, so it MUST provide necessary support for future application or service based on keyword. • Any system , anywhere , any application?
Some comments • Name lookup service • Special service with unique entrance for all user and all application ??? • Layer 2 or layer 3 ??? • Share and based on existed namespace or substitute existed namespace • Substitute DNS/IDN ? • Common goal for IDN and keyword is convenient for users • Easy to use and hard to make perfect definition, and perfect definition bring constraint and in-convenient for user. • IDN has strict architecture now, but keyword has not. Maybe for basing on application . MicroSoft?
Protocol • New protocol must be developed to support lookup service of keyword (KWLSP?) • How to deal with the existed protocol ,such as CNRP.
Relationship to other service • Such as ENUM • ENUM disappear? Or become the fundamental service of the lookup service of telephone number based on E.164. • IDN • Move IDN namespace to keyword namespace ? • Maybe or maybe not. • Others
Syntax of keyword • To do some process based on semantics and context? such as TS/SC. • 李晓东 • 李晓東 • 李曉東 • 李曉东 • Delegation of keyword , based on country, language, region and others? Or no delegation , just flat architecture. • ……