This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] Easy to remember IP-address
- Previous message (by thread): [address-policy-wg] Easy to remember IP-address
- Next message (by thread): [address-policy-wg] Easy to remember IP-address
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Garry Glendown
garry at nethinks.com
Tue Mar 30 15:30:07 CEST 2010
On 30.03.2010 14:37, Masataka Ohta wrote: > Sergey Gotsulyak wrote: > > >> For this project we?ll need an easy to remember IP-address, for >> example like the one for Google Public DNS service (8.8.8.8) >> > I'm afraid you typed wrong characters for "we'll", which is > a problem, among many, of unicode > > Anyway, 4 byte addresses of IPv4 is not so bad to memorize. > > You are right, however, that IPv6 addresses are impossible to > remember not only for end users but also for network operators, > which is one of a reason why IPv6 is NOT deployable. > Sorry, but you must be one sieve-brain (is there such a word in english?) of a network operator if you aren't able to remember your /32 prefix .. As for end users - end users do not have to remember ANY IPs ... that's what DHCP, DNS etc. are for, as well as (if necessary) documents given to end users when they sign up and receive their login information... or would you state that the initial setup information for a dial-up account (e.g. username/password) is shorter than some single IP-address (both v4 and v6)? Please stop spreading FUD about IPv6, just because _YOU_ are either incapable or unwilling to deploy IPv6 doesn't mean that the other currently >2000 prefix owners would prefer to wait another n years to see whether your RFC-draft would be implemented by one single vendor ... > The magic number for memory is 7. That is, one can easily remember > 4 bytes and may be able to remember 8 bytes. However, it is virtually > impossible to remember 16 bytes. > Let's see. "ipv6.google.com". Looks easy to remember to me. And my computer - what a surprise - automagically converts that to those "impossible" to remember numbers like 2a00:1450:8001::63. Just like that. Seems like at least the computer had no trouble at all remembering them ... Oh, and I have no trouble remembering the IPs for my mailserver ... both v4 and v6 ... along with several dozens of other v4 and v6 addresses for personal and customer servers, firewalls and routers that I need more or less ... as do many if not all of our tech staff ... and in case somebody may not remember a specific IP from time to time - that's what documentation is for ... > That is, for fairness, IPv6 is unusable. > for you, maybe. Now go home and play with your draft while the rest of the world goes ahead with technical progress ... > Instead, everyone should be able to remember 4 byte IPv4 > addresses and 2 byte short port numbers as was documented in > <draft-ohta-e2e-nat-00.txt> > Exactly. Because "www.site1.de:1234" and "www.site2.com:1324" and "www.site3.org:1243" are so d at mn easy to remember for the average-joe-enduser ... compared to impossible to remember "www.site1.de", "www.site2.com" and "www.site3.org", which unnoticed by the enduser are resolved to either IPv4 or IPv6 addresses and just simply work ... now tell me, what exactly does the end user gain from sticking with YAPOSNL? (yet another POS nat layer) -gg
- Previous message (by thread): [address-policy-wg] Easy to remember IP-address
- Next message (by thread): [address-policy-wg] Easy to remember IP-address
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]