Re: [Enum] Re: Update of Carrier ENUM requirements I-D
"Stastny Richard" <Richard.Stastny@oefeg.at> Thu, 01 December 2005 14:55 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ehppx-00070U-81; Thu, 01 Dec 2005 09:55:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ehppv-0006y0-L3 for enum@megatron.ietf.org; Thu, 01 Dec 2005 09:55:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00091 for <enum@ietf.org>; Thu, 1 Dec 2005 09:54:16 -0500 (EST)
Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EhqAO-00007K-Aw for enum@ietf.org; Thu, 01 Dec 2005 10:16:15 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Enum] Re: Update of Carrier ENUM requirements I-D
Date: Thu, 01 Dec 2005 15:58:39 +0100
Message-ID: <32755D354E6B65498C3BD9FD496C7D462C46D8@oefeg-s04.oefeg.loc>
Thread-Topic: [Enum] Re: Update of Carrier ENUM requirements I-D
Thread-Index: AcX2hj7ZrdZbTG7YQRa0+NzvR2EokQAAKnT8
From: Stastny Richard <Richard.Stastny@oefeg.at>
To: "Lupton, Ronan" <ronan.lupton@ie.mci.com>, "Pfautz, Penn L, NEO" <ppfautz@att.com>, Patrik Fältström <paf@cisco.com>
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 7f3fa64b9851a63d7f3174ef64114da7
Content-Transfer-Encoding: quoted-printable
Cc: enum@ietf.org
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Sender: enum-bounces@ietf.org
Errors-To: enum-bounces@ietf.org
Yes, you both may be correct, Was just a try ;-) PATS may be too restrictive in some countries (note that I did not use the abbreviation) BTW, in Austria the regulator just decided that any "interconnected" VoIP service (in FCC Emergency service meaning) is PATS. There is no ECS. PSTN could do, if we do not find anything else some other proposals: ITU and ETSI sometimes use: PSTN/ISDN/PLMN we could also use Telephone Services according E.105 Richard ________________________________ Von: Lupton, Ronan [mailto:ronan.lupton@ie.mci.com] Gesendet: Do 01.12.2005 15:43 An: 'Pfautz, Penn L, NEO'; Stastny Richard; Patrik Fältström; timothy.dwight@mci.com Cc: enum@ietf.org Betreff: RE: [Enum] Re: Update of Carrier ENUM requirements I-D Penn, I think you might be correct. Richard, as your aware OFCOM are querying the PATS logic and definition below with the EU Commission DG Information Soc. It's highly contentious with XoIP and NGN services, which may be uni or multi directional. *Old might be good e.g. PSTN* (See Or option below which might offer a compromise in meaning) Definition of PATS: Publicly Available Telephone Service Means a service available to the public for originating and receiving national and international calls and access to emergency services through a number or numbers in a national or international telephone numbering plan, and in addition may, where relevant, include one or more of the following services: the provision of operator assistance, directory enquiry services, directories, provision of public pay phones, provision of service under special terms, provision of special facilities for customers with disabilities or with special social needs and/or the provision of non-geographic services. Ref: http://europa.eu.int/eur-lex/pri/en/oj/dat/2002/l_108/l_10820020424en00510077.pdf Article 2. Definitions. Page 9 of 27. (c) -> Or we could use this text (b) Ibid: Public Telephone Network Means an electronic communications network which is used to provide publicly available telephone services; it supports the transfer between network termination points of speech communications, and also other forms of communication, such as facsimile and data. Ronan Lupton -----Original Message----- From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf Of Pfautz, Penn L, NEO Sent: 01 December 2005 14:28 To: Stastny Richard; Patrik Fältström; timothy.dwight@mci.com Cc: enum@ietf.org Subject: RE: [Enum] Re: Update of Carrier ENUM requirements I-D Richard: I'm fine with the other changes but would prefer to keep the term PSTN. My memory of PATS is that is has an even more specific meaning and that some parties issued numbers by NRAs are not PATS. Penn -----Original Message----- From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf Of Stastny Richard Sent: Thursday, December 01, 2005 8:01 AM To: Patrik Fältström; timothy.dwight@mci.com Cc: enum@ietf.org Subject: RE: [Enum] Re: Update of Carrier ENUM requirements I-D Agreed, but the Carrier-of-Record in Infrastructure ENUM is the pendant to the End-user in User ENUM. I propose to leave the term Carrier-of-Record Reading the meeting minutes, it was agreed to move the definitions in the Haberler draft over to the requirements draft I copy here the relevant part: <snip> 2. The Carrier of Record In User ENUM, the entity or person having the right-to-use in a number has the sole discretion about the content of the associated domain and thus the zone content. Within a Carrier ENUM namespace, we use the term "carrier of record" for the entity having that discretion. This right typically lies with a service provider authorized to issue E.164 numbers for the provisioning of PSTN service under the authority of a National Regulatory Authority (NRA), but generally exhibits one or more of the following properties: o it has been assigned one or more national number ranges by an NRA. o it has been assigned a number range directly by the ITU, for instance a code under "International Networks" (+882) or "Universal Personal Telecommunications (UPT)" (+878). o it can be the recipient of a number porting operation. o it provides a PSTN point-of-interconnect for the number. </snip> Since it was also mentioned on the list that the term PSTN was too narrow, I propose to replace the term PSTN with Public Available Telephony Service So the sentence will read: This right typically lies with a service provider authorized to issue E.164 numbers for the provisioning of a Publicly Available Telephony Service under the authority of a National Regulatory Authority (NRA), ... This sentence includes BTW also the term "service provider" ;-) Regards Richard > -----Original Message----- > From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf > Of Patrik Fältström > Sent: Thursday, December 01, 2005 8:13 AM > To: timothy.dwight@mci.com > Cc: enum@ietf.org > Subject: Re: [Enum] Re: Update of Carrier ENUM requirements I-D > > Be careful... > > When running DNS, we have one party that is responsible for the DNS > service that make DNS records available. We might have a different > organization that is deciding what the records are. And then a third > party responsible for the service the record refer to. And of course a > fourth that is administrative responsible for the domain name itself. > > Example: > > Organization A is the registrant for example.com. > > Organization B is asked to administer the example.com zone (do the > provisioning). > > Organization C is running the DNS that holds the example.com zone. > > Organization D is running the mailserver MX record for example.com > refer to. > > If you are curious of difference between B and C, think of the root > zone where ICANN decide what the content of the root zone is, and the > root server operators as a collective is making the zone available. > > > What term you use doesn't matter. The important thing is that you in a > terminology section is extremely explicit with what you talk about. > > paf > > On 30 nov 2005, at 22.47, Tim Dwight wrote: > > > I'm not sure that I agree with changing "carrier of record" to > > "service provider of record". Depends on what the latter means I > > suppose. If (as > > seems intuitive) "service provider" means "the entity that the > > customer > > perceives as providing the service", and "carrier of record" means > > "the > > entity providing PSTN access for calls to or from the customer", > > then is a > > "service provider of record" an entity that does both? And is that > > the > > appropriate semantic? > > > > At the risk of inviting flames I'd say that "carrier of record" is > > the appropriate term and the Telco-bashing that seems to motivate > > this change, is juvenile. > > > > Tim > > > > > > -----Original Message----- > > From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf > > Of Richard Shockey > > Sent: Wednesday, November 30, 2005 3:31 PM > > To: Pfautz, Penn L, NEO > > Cc: enum@ietf.org > > Subject: [Enum] Re: Update of Carrier ENUM requirements I-D > > > > Pfautz, Penn L, NEO wrote: > >> Having looked over the Vancouver minutes of the WG I want to ask > >> if I should replace "carrier ENUM" with "infrastructure ENUM" > >> before resubmitting draft-lind-infrastructure-enum-reqs-01 as > >> draft-ietf-enum-infrastructure-enum-reqs-00. > > > > Yes .. it seemed to be the consensus of the WG that the word carrier > > seems to be associated with some form of disease. > > > > > >> If so, I would also propose to render "carrier of record" as > >> "service provider of record" going forward. > > > > excellent idea. > > > >> > >> Your views? > >> > >> Thanks, > >> Penn > > > > -- > > > > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > > 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@ietf.org > > https://www1.ietf.org/mailman/listinfo/enum > > > > > > _______________________________________________ > > enum mailing list > > enum@ietf.org > > https://www1.ietf.org/mailman/listinfo/enum > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum
- [Enum] Update of Carrier ENUM requirements I-D Pfautz, Penn L, NEO
- [Enum] Re: Update of Carrier ENUM requirements I-D Richard Shockey
- RE: [Enum] Re: Update of Carrier ENUM requirement… Tim Dwight
- Re: [Enum] Re: Update of Carrier ENUM requirement… Patrik Fältström
- RE: [Enum] Re: Update of Carrier ENUM requirement… Stastny Richard
- RE: [Enum] Re: Update of Carrier ENUM requirement… Pfautz, Penn L, NEO
- RE: [Enum] Re: Update of Carrier ENUM requirement… Lupton, Ronan
- Re: [Enum] Re: Update of Carrier ENUM requirement… Stastny Richard
- RE: [Enum] Re: Update of Carrier ENUM requirement… McGarry, Tom
- RE: [Enum] Re: Update of Carrier ENUM requirement… Pfautz, Penn L, NEO
- Re: [Enum] Re: Update of Carrier ENUM requirement… lconroy
- Re: [Enum] Re: Update of Carrier ENUM requirement… Richard Shockey
- Re: [Enum] Re: Update of Carrier ENUM requirement… lconroy
- Re: [Enum] Re: Update of Carrier ENUM requirement… Stastny Richard
- RE: [Enum] Re: Update of Carrier ENUM requirement… McGarry, Tom
- RE: [Enum] Re: Update of Carrier ENUM requirement… Stastny Richard