1 / 9

IP Protocol Interoperability

IP Protocol Interoperability. KDDI Proposal. Masaru Umekawa (umekawa@kddi.com) Masaaki Koga (koga@kddi.com) Masaru Fukumitsu (ma-fukumitsu@kddi.com) Anete Hashimoto (a-hashimoto@kddi.com). Establishing the next procedure

tave
Download Presentation

IP Protocol Interoperability

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. IP Protocol Interoperability KDDI Proposal Masaru Umekawa (umekawa@kddi.com) Masaaki Koga (koga@kddi.com) Masaru Fukumitsu (ma-fukumitsu@kddi.com) Anete Hashimoto (a-hashimoto@kddi.com) KDDI Confidential Proprietary

  2. Establishing the next procedure 1- Deciding about the type of message needed in the network. 2- Consider both RADIUS/L2TP attributes 3- Deciding for the routing method • Domain name ? • Domain name + suffix ? • Domain name + IMSI/MIN? KDDI Confidential Proprietary

  3. Type of message required to be interchanged in the network • RADIUS Authentication message • Access-Request • Access-Accept/Reject Accounting message • Accounting-Request (Start/Stop/Interim) • Accounting-Response • L2TP • SCCRQ/SCCRP/SCCCN • ICRQ/ICRP/ICCN • SLI KDDI Confidential Proprietary

  4. Required Attributes for Authentication KDDI Confidential Proprietary

  5. Required Attributes for Accounting KDDI Confidential Proprietary

  6. Required Attributes for L2TP KDDI Confidential Proprietary

  7. Deciding for the routing method (known Plan 1) Proposal 1 Domain names are registered on the serving RADIUS server in response to the request from home network carrier. • 【Advantage】 • This plan is standard. (?) • - Each serving RADIUS server does not need additional implementation to perform this plan. 【Disadvantage】 - It is necessary to register the routing parameter(domain name) on the serving RADIUS server every time new “Home ISP / Corp VPN “ domains are added in the home network. - Every time domain names are registered on the serving system, it will be necessary to perform tests on them. KDDI Confidential Proprietary

  8. Deciding for the routing method (known Plan 2) Proposal 2 - Putting a suffix in the handset - <cdmaone>@<au-net.ne.jp>@<kddi> (1) (2) (3) (1) User ID. To be used for user authentication. (2) Optional. To be used for routing within the home network. (3) Suffix. To be used for routing from the serving network to the home network. The serving network shall delete the suffix. 【Advantage】 It is unnecessary to register the routing parameter (domain name) on the serving RADIUS server every time new “Home ISP / Corp VPN “ domain are added in the home network. 【Disadvantage】 This plan is not standard. (?) Each serving RADIUS server needs additional implementation to perform this plan. KDDI Confidential Proprietary

  9. Deciding for the routing method (New Plan) Necessary RADIUS Parameters are a and b a) User-name containing Domain name “Internet Access via Serving Network” use b) Calling-station-id containing IRM(International Roaming MIN) or IMSI “WAP Connectivity to Home Gateway” and “Home ISP / Corp VPN Access” use Ex) Routing Method 【Advantage】 It is unnecessary to register the routing parameter (domain name) on the serving RADIUS server every time new “Home ISP / Corp VPN “ domain are added in the home network. Compare Domain OK Request Routing From roaming in MN NG Compare IRM or IMSI OK 【Disadvantage】 Each serving RADIUS server needs additional implementation to perform this plan. Routing NG Reject or Discard KDDI Confidential Proprietary

More Related