Talk:Mobile IP
This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
|
The contents of the FMIPv6 page were merged into Mobile IP on 2015-09-14. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. |
Too technical
editThis article is way too technical. I am a scientist, do a lot of programming, but this article was over my head. Please someone with some communication skills clean this up!—Preceding unsigned comment added by 71.111.193.88 (talk • contribs)
It really helps understanding IP routing before trying to understand mobile ip. However, I think adding
- a post office analogy - where you move to a new residence and ask the post office to forward your mail to the new address. - a diagram
would help most people get a general concept of how it works. — Preceding unsigned comment added by Noyabronok (talk • contribs) 11:15, 7 December 2015 (UTC)
NetBIOS
editI was very surprised by the mentioned "netbios" similarities. I'm working in MIPv4/v6 since 1999, and I'm finishing my PhD on mobile data networks, were i've proposed the "TIMIP" micro-mobility scheme.
Through this time i've never seen any reference for this netbios similarity in any of teh extensive bibliography that I've studied.
Also, concerning rfcs 1001 and 1002, eventough I haven't read them, I couldn't find any of these mobility-related keywords in the RFCs: mobile / mobility / handover / handoff / terminal / agent / tunneling / encapsulation.
Thus, besides questioning this comment without further references, I also think that this line is extremly exagerated for the casual wikipedia reader "Readers may be intrigued to know that..." --Pedro Estrela (12:59, 11 May 2006 (UTC))
- I don't believe the NetBIOS part either. The purpose of NetBIOS is entirely different.—Preceding unsigned comment added by 84.161.101.123 (talk • contribs)
- NetBIOS works on the session layer, while Remote IP defines a behavior of IP discovery which is on the Network layer. Both NetBIOS and Mobile IP permit identification of remote host, but since most modern implementation of NetBIOS uses NetBIOS-over-TCP (as decribed in rfc1002) and thus requires a valid IP adresse assigned to a host, you need a lower form of IP-discovery fonctionnality like static IP, DHCP, or if the host tends to move from in and out of the network, Mobile IP. Mobile IP, in theory, autmagicaly creates a VPN with the old network, and re-acquires the old IP. It's a bit simplified, but I think it explains the difference between the 2. Sepper 16:00, 15 May 2006 (UTC)
NetBios
editI have only found the following link which includes the same content copy/pasted in this article on the similarities between MIP and NetBios, but couldn't find any further references. If anyone can add additional references, please do, otherwise I believe this part should be deleted due to insufficient credible citing.--Goarany 07:39, 11 December 2006 (UTC)
Invalid link
editOne of the references in this article gives me a 404 error as of 12 June 2010 —Preceding unsigned comment added by 41.202.225.145 (talk) 10:12, 12 June 2010 (UTC)
History and Missing Bits
editMobile IP has evolved over time to its current state. Where historical forms deviate significantly from the description in the article, at least some note should be made to that effect to avoid being misleading.
Mobile IP is also not a single entity. This is mentioned in the article, but could probably be improved on. Suggested sources for helping with this:
- Hierarchical Mobile IP: https://www.ietf.org/rfc/rfc4140.txt and http://tools.ietf.org/html/rfc5380
- Proxy Mobile IPv6: http://tools.ietf.org/html/rfc5213
- Fast Mobile IPv6: http://tools.ietf.org/search/rfc5269
- Route Optimization: http://www.rfc-editor.org/rfc/rfc4866.txt
- Adaptive Route Optimization: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.79.843
- Official Mobile IPv6 conformance test suite: http://cert.v6pc.jp/mipv6/ —Preceding unsigned comment added by 173.11.23.233 (talk) 17:46, 27 April 2011 (UTC)
Copyright problem removed
editPrior content in this article duplicated one or more previously published sources. The material was copied from: http://www.apps.ietf.org/rfc/rfc2005.html, http://searchmobilecomputing.techtarget.com/definition/Mobile-IPv6. Infringing material has been rewritten or removed and must not be restored, unless it is duly released under a compatible license. (For more information, please see "using copyrighted works from others" if you are not the copyright holder of this material, or "donating copyrighted materials" if you are.) For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or published material; such additions will be deleted. Contributors may use copyrighted publications as a source of information, but not as a source of sentences or phrases. Accordingly, the material may be rewritten, but only if it does not infringe on the copyright of the original or plagiarize from that source. Please see our guideline on non-free text for how to properly implement limited quotations of copyrighted text. Wikipedia takes copyright violations very seriously, and persistent violators will be blocked from editing. While we appreciate contributions, we must require all contributors to understand and comply with these policies. Thank you. NortyNort (Holla) 01:24, 4 June 2011 (UTC)
Role of the remote agent
editHi all,
I modified the following points:
- As mentioned on the care of address page, and as specified in the main RFC, the remote agent is not mandatory. Otherwise, how would one use mobile IP on a host network where it is not implemented yet?
- incoming traffic does not necessarily "go through" the remote agent, it only does when the remote agent exists and has the same IP address as the mobile devices. In all cases, the care-of address is used as the endpoint of the tunnel, be it shared with the FA or not
- similarly, outgoing connexions have no reason to go through the remote agent (even though the remote agent is often the exit router at the same time, but it's unrelated)
If people disagree with these changes, I'm open to the (technical) discussion. --MathsPoetry (talk) 12:05, 17 August 2011 (UTC)
Actual usage
editDo all cell phone service providers implement mobile ip? If not, what ip mobility alternatives are they using? A detailed list of supporting providers and communication protocol, e.g. LTE, HSPA, EDGE, etc., would be most useful. Noyabronok (talk) 11:01, 7 December 2015 (UTC)
Mobile Node vs Mobile Host
editWhy are we confusing between the two terms, 'node' and 'host', in Section 3?
External links modified (February 2018)
editHello fellow Wikipedians,
I have just modified one external link on Mobile IP. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive http://webarchive.loc.gov/all/20011116164536/http%3A//www.monarch.cs.cmu.edu/ to http://www.monarch.cs.cmu.edu/
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}}
(last update: 5 June 2024).
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot (Report bug) 04:15, 3 February 2018 (UTC)