[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tired of Waiting



    From: Patrick Greenwell <patrick@namesecure.com>

    > Phone numbers aren't like routing information? Then why do we have area
    > codes and exchange prefixes?

You will note that the "local number portability" is just that - *local*
portability. Move from one state in the US to another, and get a new phone
number.

And even LNP is being done with Yet Another Giant Mapping Database, so that
when your incoming call arrives at a LATA, the IEC knows which LEC to give it
to. In other words, your "phone number" here in the New World Order *doesn't*
contain your exchange any more - rather, it's a portable "phone name" which
has to be mapped into a *real* phone number befire the phone switches can
route the call.

In other words, a phone number under LNP is just like a DNS name - it has to
be mapped into a real location before being useful. People don't think of
them that way because the *syntax* is identical - looks like a phone numbers,
works like a phone number. But they aren't really line numbers any more.


    > Further, I would love to have a truly permanent, portable IP
    > address(es).

Sure. Now, remembering the above details about how LNP really works, with
mapping on all inbound calls, please explain to us the details: are you going
to emit packets with these "portable" IP "addresses" in them?

If so, what happens: does each individual router along the path do a mapping
before routing the packet - or does the first hop router do the lookup once
and modify the packet? (If so, what about TCP checksums - not to mention
authentication...)


Gee, guys, where's Tim Bass? Maybe we could get him to explain all this to
Mr. Greenwell... :-) (Tim, if you're listening, my apologies in advance!)

	Noel


Privacy Policy | Terms of Service | Cookies Policy