Nieminen Klaus wrote:
Clearly these are national issues but this brings up the subject of how much information any ENUM registry should keep, carrier or public.Penn, Michael and all, My message was that in most cases we do have the required information available and I think that we should not focus on the implementation details in this question. As Penn mentioned, I believe that these issues can be solved. However, there are cases that may cause problems and my question is: Should we take also these cases into account in our work or do you think that this is should more likely to be solved nationally? This a well known issue in classic domain registry operations ..the Thick vs Thin model of Registry. Time and Time again its has been conclusively shown that the maintance of a Thick Registry is in the long term best interests of all parties. One of the things this WG has done is move forward IRIS EREG as a potential repository for information associated with a TN that might be useful to NRA - LEA etc. In the US ENUM TAC LLC requirements document we specified the use of IRIS for "Contact-Info" http://enumllc.com/tac/docs/t1b/V7-052605_TAC_Tier1B-Reqs.doc Penn is right .. the situation in Europe is complicated by the lack of independent registry data associated with a TN. Way too often the incumbent i is permitted to hold such data which complicates the process of NP. It is clear that many European countries now realize the disadvantages of centeralized databases and are reconsidering their options. IMHO the Thick ENUM registry is the only way to go ..its only then a question of what data is necessary to keep centrally and how that data is protected by various privacy regulations etc. NRA's looking at Carrier ENUM should consider carefully what requirements are necessary to maintain ligitimate centralzed ancillary data on a TN that might be useful in the future. - Klaus - -----Original Message----- From: Pfautz, Penn L, NEO [mailto:ppfautz at att.com] Sent: 11. lokakuuta 2005 16:26 To: Nieminen Klaus; enum at ietf.org Subject: RE: [Enum] A proposal for Carrier ENUM Klaus: Unfortunately not all portability implementations use network databases (I assume it's network databases rather Rather than admin ones to which you refer) Maybe some of those whose countries use "onward routing" etc. can confirm whether there is any centralized database outside of the network detailing those arrangements. Nonetheless, I do think that for the most part it will be possible to determine who the carrier providing the PSTN point of interface for an E.164 number is and thus the carrier-of-record for carrier ENUM. If this information were not generally available the E.164 number would not be of much use anyway. I could think of workarounds even in the non-centralized LNP situations and, frankly, if those cause some pain, if should be thought of in terms of penance for making an erroneous choice with respect to the implementation of number portability. (:-) The day may/should/will come when interconnection is all IP-based and some form of ENUM Registry IS the database of record for number assignment and then we can have a debate about what it means to be carrier of record again, but for now the approach of using the entity that provides the number assignment/PSTN PoI is, I think, quite workable. Penn Pfautz -----Original Message----- From: enum-bounces at ietf.org [mailto:enum-bounces at ietf.org] On Behalf Of Nieminen Klaus Sent: Tuesday, October 11, 2005 9:00 AM To: enum at ietf.org Subject: RE: [Enum] A proposal for Carrier ENUM Hello, One clarification:-----Original Message----- From: enum-bounces at ietf.org [mailto:enum-bounces at ietf.org] On BehalfOf Stastny RichardSent: 11. lokakuuta 2005 14:28 To: Antoin Verschuren; enum at ietf.org Subject: RE: [Enum] A proposal for Carrier ENUM -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 <mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz> <http://www.neustar.biz> ; <http://www.enum.org> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< |
_______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum