1 / 13

IANA Registration for ENUMservice Mobile Web draft-ra-shin-enum-mobileweb-01

IANA Registration for ENUMservice Mobile Web draft-ra-shin-enum-mobileweb-01. Aug. 5. 2005 Jongyun Ra, Sungwoo Shin, Yongwan Ju, Weon Kim National Internet Development Agency of Korea Lawrence Conroy Roke Manor Research Ltd. Unit : K. Africa. Europe. 50,962.7. 442,838.4. 1,367,518.1.

cherryj
Download Presentation

IANA Registration for ENUMservice Mobile Web draft-ra-shin-enum-mobileweb-01

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IANA Registration for ENUMservice Mobile Web draft-ra-shin-enum-mobileweb-01 Aug. 5. 2005 Jongyun Ra, Sungwoo Shin, Yongwan Ju, Weon Kim National Internet Development Agency of Korea Lawrence Conroy Roke Manor Research Ltd

  2. Unit : K Africa Europe 50,962.7 442,838.4 1,367,518.1 America 293,498.6 559,206.6 17,264.6 Asia Oceania 2003 Mobile Subscriber from ITU Reports Background • As the market of mobile telephony service has kept growing up, the number of mobile internet users has been gradually increasing • In Korea, the number of mobile internet users has reached nearly 7,180K (23% of total Internet users in Korea) • Mobile ENUM usage will be of high importance according to its convenience and portability; the number of mobile devices with Internet access that can take advantage of the convenience may well outweigh those with fixed connectivity

  3. Abstract o There are various services that can be associated with E.164 number used in ENUM. Some RFC documents define types, subtypes and URI schemes for registering some of them as ENUMservices- RFC3762(h.323), RFC3764(sip), RFC3953(presence), RFC4002(web and ft) o This document registers the ENUMservice ‘mobileweb’ using the URI scheme ‘http:’ , ‘https:’ as per the IANA registration process defined in the ENUM specification RFC3761 o Mobile webpages are smaller and simpler than web pages for general use; the mobile webpages are designed to fit within the pocket-sized display of mobile terminals, and to reflect the ‘long pipes’ by which these terminals are connected. o This ENUMservice indicates that the resource identified by the associated URI is capable of being a source of information through a mobile webpage.

  4. General Web vs Mobile Web Mobile web service registration not described in RFC4002

  5. WAP vs ME vs i-mode

  6. WAP vs ME vs i-mode(cont’d) WAP (1.x) Device WAP G/W Web server WML Page WML Page WSP WSP HTTP HTTP WTP WTP WTLS WTLS SSL SSL WDP WDP TCP TCP Bearer Bearer IP IP ME Terminal Web server m-HTML Page m-HTML Page HTTP HTTP SSL/TLS Interworking Function SSL TCP TCP TCP TCP IP IP IP IP Wireless Wireless Wired Wired i-mode Web server Terminal HTTP cHTML Page cHTML Page cHTML Page HTTP M-PGW TLS TLS TLS TLS TL PPM TL TCP TCP CallCtl CallCtl IP(PMAP) IP(PMAP) IP IP Wireless Wireless Wired Wired Wired Wired

  7. Mobile Web Environment The standard described in RFC 4002 can not cover mobile web at all RFC 4002 +82-2-2186-4500 “E2U+web:http” “!^.*$!http://www.ibm.com!” “E2U+web:http” “!^.*$!http://m.ibm.com!” How to distinguish general web from mobile web ?

  8. Mobile Web Environment(cont’d) i-mode ME WAP URI http://w.ibm.com http://m.ibm.com http://i.ibm.com Terminals Cellular(Mobile) Phone RFC 4002 +82-2-2186-4500 “E2U+web:http” “!^.*$!http://w.ibm.com!” “E2U+web:http” “!^.*$!http://m.ibm.com!” “E2U+web:http” “!^.*$!http://i.ibm.com!” How to distinguish the protocol for mobile webpage from another protocol? ME Support WAP Support i-mode support

  9. Draft Proposals o The ENUMservice registration used by a mobile web must be classified according to the protocol architecture that mobile web uses; it needs to use another ENUMservice registration from that specified in RFC 4002 o There are two choices of ENUMservice registration of mobile web; these are ‘Diverse Mobile Web Service Registration’ and ‘Uniform Mobile Web Service Registration’ o ‘Diverse Mobile Web Service Registration’ uses ENUMservice Type ‘mobileweb’ and different ENUMservice Subtypes according to the mobile web protocol architectures(WAP, ME, i-mode) o ‘Uniform Mobile Web Service Registration’ uses ENUMservice Type ‘mobileweb’ but does not use any ENUMservice Subtype

  10. Draft Proposals(cont’d) ENUMservices mobileweb ‘Diverse Mobile Web Service Registration’ Enumservice Name: "mobileweb" Enumservice Type: "mobileweb" Enumservice Subtype: "wap", "me", "imode" URI Scheme: 'http:', 'https' Functional Specification: This ENUMservice indicates that the associated resource identified by URI scheme is a mobile webpage Example : “E2U+mobileweb:me” “!^.*$!http://m.ibm.com!”

  11. Draft Proposals(cont’d) • What if the mobile web service is provided using a same URI regardless of the protocols of mobile web service?(namely, mobile web server is intelligent and can branch connection properly) 2. What if the protocols of mobile web service are unified and integrated to one(e.g WAP2 or other) in the future ? So, this draft proposes ‘Uniform Mobile Web Service Registration’ Enumservice Name: "mobileweb" Enumservice Type: "mobileweb" Enumservice Subtype: N/A URI Scheme: 'http:', 'https' Functional Specification: This ENUMservice indicates that the associated resource identified by URI scheme is a mobile webpage Example : “E2U+mobileweb” “!^.*$!http://mobile.ibm.com!”

  12. Conclusion RFC 4002 draft-ra-shin-enum-mobileweb Mobile web registration General web registration

  13. Thank you

More Related