Presentation on theme: "KDDI Confidential Proprietary Slide 1 IP Address Management Issue and Data Survey in Reference Doc#79 2005/03/02 KDDI Masaru Umekawa."— Presentation transcript:
KDDI Confidential Proprietary Slide 1 IP Address Management Issue and Data Survey in Reference Doc#79 2005/03/02 KDDI Masaru Umekawa
KDDI Confidential Proprietary Slide 2 IP Address Management Issue A potential problem about IP address management which makes the coexistence of the recommended roaming configurations (Simple IP, Mobile IP and L2TP) difficult The gap of the address requirements in each roaming configuration causes the problem
KDDI Confidential Proprietary Slide 3 PDSN (Private/Global) Visited NW Home NW CRX/Internet MS (Global/Private*) Application Server (Global) Proxy-AAA (Global) RADIUS message Bearer Data FA/LAC(PDSN) (Global) CRX/Internet MS (Private/Global) Application Server (Private/Global) Proxy AAA (Global) Proxy-AAA (Global) RADIUS Message Mobile IP/L2TP message Bearer Data Home NW Simple IP Mobile IP/L2TP HA/LNS (Global) *IP masquerade IP Address Requirements Visited NW
KDDI Confidential Proprietary Slide 4 IP Address Requirements Proxy-AAA – Proxy-AAA Public IP address is definitely required Mobile Station – Application Server (DNS, E-mail, Web, etc.) –Simple IP Public IP address is required (IP masquerade is available for Mobile Station) –Mobile IP/L2TP Public IP address is NOT required. Private IP address is available. PDSN/FA/LAC – HA/LNS –Simple IP Public IP address is NOT required. Private IP address is available –Mobile IP/L2TP Public IP address is required. –IS-835 standard describes that the PDSN/HA shall use a publicly routable and visible IP address as a FA/HA address. –IP masquerade is not available. It changes only the source IP address of PDSN, but does not change the care of address in the packet payload. (as know NAT Problem)
KDDI Confidential Proprietary Slide 5 IP Address Management Issue Some home operators who normally provide Mobile IP or L2TP for their own subscribers assign private IP addresses to their application servers (DNS server, E-mail server and Web server, etc.) and request the tunnel solution from visited operators. On the other hand, Some visited operators who normally provide Simple IP for their own subscribers assign private IP addresses to their PDSN. In that case, the visited PDSN can not negotiate with the HA/LNS in the home NW across the public NW and can not provide the tunnel solution, even if it has these tunnel functions. Public IP address for all PDSN? Unrealistic… IP masquerade solution ? NOT available
KDDI Confidential Proprietary Slide 6 Survey Items 1. Which roaming configurations can you provide? 2. Which type of IP address (Public or Private) do you assign to your network elements? Operator Available Configurations as Visited operator Available Configurations as Home operator Address Type Mobile StationFA/LAC (PDSN) HA/LACAppreciation Server Operator ASimple IP Global - Mobile IP Private/GlobalGlobalPrivate/Global L2TP Private/GlobalGlobalPrivate/Global Operator BSimple IP GlobalPrivate-Global Operator CSimple IP Private (IP masquerade)Global Mobile IP Private/GlobalGlobal Private/Global ---L2TP--- GlobalPrivate/Global For example, operator A can provide all of the roaming configurations as visited operator as well as home operator. Operator B can provide only simp le IP as visited operator as well as home operator and assigns private IP address to their PDSN. Operator C has LNS but not LAC. Operators C can pr ovide all of the roaming configuration as home operator, but not support L2TP as the visited operator
Your consent to our cookies if you continue to use this website.