|
Issue # |
Issue Title |
Issue Description |
Related Work |
Responsible Forum |
|
1 |
Accommodate E.164 Number Portability
(Related to Issue 14)
|
This issues relates to the three types of portability;
- Service Provider
- Location
- Service
|
- ITU Number Portability Supplement
- Q.769.1
- ENUM
- SIP
- DNSEXT
- ETSI TIPHON
- SG2(WP1/2)
- SGs 11, and 16
|
IETF-ITU |
|
2 |
Transfer of Caller and Called Party information |
The transfer of Caller and Called Party involves only one
layer. Transfer of Caller and Called Party information between
both parties |
- ETSI STF 157
- SIP
- H.323
- H.248
- MEGACO
- SIGTRAN
- SG2(WP1/2)
- SGs 11, 13 and 16
|
IETF-ITU |
|
3 |
E.164 Number for IP based End-User |
The allocation of E.164 resources to IP based users |
- H.323
- H.248
- SIP
- ETSI TIPHON
- SG2(WP1/2)
- SGs 11, and 16
|
ITU |
|
4 |
E.164-DNS Interworking
(Related to Issue 8)
|
Collaboration on the identification of specific issues and
appropriate work parameters related to E.164 – DNS
interworking (such as Interworking concepts and principles, Administrative and operational
aspects, Identification of other relevant aspects.)
|
- DNSEXT
- ENUM
- 3GPP
- 3GPP2
- SG2(WP1/2)
- SGs 4, 11, and 16
|
IETF-ITU |
|
5 |
Carrier Selection/Preselection
|
Originating networks often have to support ability of
customer to decide, e.g., "send all my international calls
via operator X." As such, where the originator is IP-based,
the "E.164-IP Resolution Process" will have to
determine a result, e.g., egress gateway based on the
combination of destination E.164 number and user preference/CLI,
i.e., the answer may vary according to context and there may be
no universal answer for a given E.164 number. |
- ITU Supplement on Carrier Selection
- SG2(WP1/2)
|
ITU Lead and IEFT-ITU
|
|
6 |
E.164, URL’s and "Telephony" |
Wide range of E.164 "telephony" issues raised in
Internet drafts proposing URLs, e.g.,
- Tel/fax/modem
- Global/local
- Dialling & post dialling
- Options & features; and
meta-issue of process (individual’s drafts vs. those
associated with Working Groups). |
Internet drafts such as
- afifi-sixtel-00.txt
- antti-telephony-url-12.txt
- kurrasch-tmar-00.txt
- gelman-phone2web-00.txt
Internet drafts such as those related to "VPIM" and
to IETF working groups |
IETF |
|
7 |
E.212 – IMSIs & mobility with IP |
In IETF documents, IMSI’s are mentioned but ITU-T Rec E.212
is not often referenced. A review of the IETF documents is
needed to ensure that the appropriate use of the term IMSI is
used. |
Rec. E.212
Rec. E.214
3GPP
3GPP2 |
IETF |
|
8 |
Administration of E.164 numbers in domain name servers
(Related to Issue 4)
|
How are numbers distributed among domain name servers in
different situations? An example, a DNS rule is one
authoritative server per telephone number. What if two SPs wish
to list information on a telephone number? |
ENUM |
IETF |
|
9 |
How changes get propagated throughout the proposed ENUM DNS
service |
One example, if an Area Code changed – propagation must be
timely (within expected range). |
ENUM requirements related work |
IETF |
|
10 |
DNS/ENUM Service logic |
How does DNS/ENUM resolve whether service logic is needed,
e.g., via TRIP protocol, for a particular E.164 name lookup?
What is the response to a user if service logic is needed (DNS/ENUM protocol issue)?
|
DNSEXT
ENUM
IPTEL
SG2(WP1/2)
|
IETF – ITU (Q10/2) |
|
11 |
IN Routing Methods |
Need to provide IN-based routing methods across IP- and TDM-based networks |
IPTEL
SIGTRAN
3GPP
3GPP2
SG2(WP1/2)
SIP
PINT
SPIRITS
Q.1200 Series
|
IETF-ITU (SGs 2 & 11) |
|
12 |
QoS Routing Support |
Need to support QoS routing methods e.g., dynamic bandwidth
reservation/protection across IP- & TDM- based networks |
MPLS
RSVP
ISSLL
SG2(WP1/2)
TEWG
E.350
E.351
E.352
SG 13
I.350
I.351
I.352
I.370
|
IETF – ITU |
|
13 |
Tracking of Routing Address |
Support tracking of E.164- name to IP-address (or
international network routing address, etc.) for wireless and
portable terminals |
Dynamic DNS
SIP
E.212
E.214
E.353
H.323
SG2
SG16
|
IETF |
|
14 |
Interworking of routing addresses and IP names/addresses
(Related to Issue 1)
|
ITU are defining an "international" routing address
plan, e.g., for use in the portability of [global] E.164
numbers, and routing of calls to potential regional country
codes (ETNS). There may be a need to interwork routing addresses
with IP Technologies. |
E.353
SG2(WP1/2)
|
ITU Lead & Collaborate with IETF
|
The identified issues are not listed in order of importance.
