[address-policy-wg] Easy to remember IP-address

Actually it is quite possible to memorize IPv6 addresses - break it into two
pieces (say, perhaps, network and host).

Especially when the high-order side of your address is fairly static ...
although obviously this becomes less easy when some portion was randomly
chosen, but those addresses aren't usually the ones you need to memorize.

And I didn't realize "memorizability" was a key design criteria for a
network protocol - if only we had some way of converting words into those
oh-so-hard-to-remember numbers ...


/TJ
*And with continued deployment advances from Google, Microsoft, NetFlix,
Comcast, Verizon Wireless, certain US DoD Components, etc. etc. ... overall,
it is looking like a good year for IPv6 :).*

On Tue, Mar 30, 2010 at 08:37, Masataka Ohta <
mohta at necom830.hpcl.titech.ac.jp> 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.
>
> 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.
>
> That is, for fairness, IPv6 is unusable.
>
> 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>
>
>   When an ISP
>   operate a NAT gateway, the ISP should, for fairness between
>   customers, reserve some well know port numbers and assign small port
>   numbers evenly to all the customers.
>
> > We have contacted RIPE NCC with a request to get a block of addresses
> > 2.2.2.0/24, but were told that the standard procedure does not allow
> > us to choose an address range.
> >
> > Is it possible to modify current Address Policy?
>
> You had better to abandone IPv6 and IPv6 address policies and just
> stick to IPv4 with A+P including, but not limited to,
> <draft-ohta-e2e-nat-00.txt>.
>
>                                                Masataka Ohta
>
>
-- 
/TJ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20100330/7f089fbc/attachment.html>