H.323 Addresses

[Chris Purvis WVdevmt-WS]

Radhika,

>We are discussing about H.323 addresing schemes in our bi-weekly H.323
>inter-GK conf calls.
>
>The H.323 addresses that are being considered are 1. E.164, 2. E-mail,
3.
>URL, and 4. TCP/UDP/RTP port addresses (and 5. aliases as well I guess).
>
>Although a hierarchical notion of addressing scehmes have been
discussed, we
>have also recognized that some other variations of addressing schemes
are
>there.
>
>For example, people change their physical locations, but they might have
to
>keep the same E.164 addresses. So, a translation is needed. Therefore,
the
>very physical relationship of E.164 addressing scheme (e.g., knowing
NPAs
>and NXXs, one can find the distance) has been broken.

I was under the impression that finally (after several weeks of
discussion) we'd reached closure on this in last Thursday's call.  The
solution that I understood had been agreed came in two parts:
1. Mobile IP solves most of the problem for us - E.164 number resolves to
an IP address which may be anywhere in the world at any given moment in
time.
2. If a user wants to move (and take their number with them) to being in
an administrative domain with an otherwise reasonably contiguous E.164
address space, this is easily handled as follows.  The domain that
"should" (in the hierarchical sense) "own" the number that the user is
keeping holds a record of where to contact the current holder of that
number (which will typically be an entity to which an LRQ message can be
sent).

>Another example can be 800 numbers where the translation is also needed.
It seemed to be agreed in the call that 800 numbers are not a special
case, but merely an example of number portability.

>In addition, from mobility point of view (device or person) wired (and
>wireless?) environement may also be looked into.
Does this mean anything at all?

>As we go froward, we may consider many of those aspects as pointed above
to
>provide solutions for the H.323 addressing schemes.
I was under the impression that we'd reached closure on most of these
already.

Regards
Chris
----------------------------------------
Dr Chris Purvis - Senior Development Engineer, WAVE CC Software
Madge Networks Ltd, Wexham Springs, Framewood Road, Wexham, Berks.
Phone:+44 1753 661359  email: cpurvis at madge.com