RE: [Enum] ENUM Working Group Last call on ENUM Validation Architecture

"Pfautz, Penn L, NEO" <ppfautz@att.com> Thu, 09 February 2006 14:13 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 1F7CY7-0001Ss-BZ; Thu, 09 Feb 2006 09:13:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7CY5-0001RC-QV for enum@megatron.ietf.org; Thu, 09 Feb 2006 09:13:29 -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 JAA24523 for <enum@ietf.org>; Thu, 9 Feb 2006 09:11:37 -0500 (EST)
Received: from mail121.messagelabs.com ([216.82.241.195]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F7Ckf-0000tS-NL for enum@ietf.org; Thu, 09 Feb 2006 09:26:34 -0500
X-VirusChecked: Checked
X-Env-Sender: ppfautz@att.com
X-Msg-Ref: server-8.tower-121.messagelabs.com!1139494335!7399859!17
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 27255 invoked from network); 9 Feb 2006 14:13:02 -0000
Received: from unknown (HELO attrh2i.attrh.att.com) (134.24.146.4) by server-8.tower-121.messagelabs.com with SMTP; 9 Feb 2006 14:13:02 -0000
Received: from ACCLUST02EVS1.ugd.att.com (135.37.16.8) by attrh2i.attrh.att.com (7.2.052) id 43CF037500336E96; Thu, 9 Feb 2006 09:13:00 -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] ENUM Working Group Last call on ENUM Validation Architecture
Date: Thu, 09 Feb 2006 09:12:57 -0500
Message-ID: <34DA635B184A644DA4588E260EC0A25A0C1CEFD1@ACCLUST02EVS1.ugd.att.com>
Thread-Topic: [Enum] ENUM Working Group Last call on ENUM Validation Architecture
Thread-Index: AcYs2rtZ6tqak9J3SzmyfOyom/AfWQApswoA
From: "Pfautz, Penn L, NEO" <ppfautz@att.com>
To: Richard Shockey <richard@shockey.us>, enum@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: quoted-printable
Cc: Patrik Fältström <paf@cisco.com>, "Peterson, Jon" <jon.peterson@neustar.biz>, Allison Mankin <mankin@psg.com>
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

Nice summary of the validation issue. A couple of questions for Alexander and Bernie:

1. The disjoint roles example in Section 5.2 shows the Validation Entity in communication with the Number Assignment Entity. Is your intent that such communication be considered a requirement of validation or merely one way in which it may be accomplished?

2. You may want to consider the effects of number portability on the process when the CSP is the NAE. When a number is ported, the CSP that assigned the number may no longer be in a position to verify number assignment. And yet the new CSP for the number is not the entity that originally assigned the number and was delegated the range from the NNPA. Where proper NP architectures (i.e. all-call query) have been implemented there is a database that can, if accessible to the VE, identify the current CSP. In other architectures different procedures will be required.

Penn

-----Original Message-----
From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf Of Richard Shockey
Sent: Wednesday, February 08, 2006 1:05 PM
To: enum@ietf.org
Cc: Patrik Fältström; Peterson,Jon; Allison Mankin
Subject: [Enum] ENUM Working Group Last call on ENUM Validation Architecture



Title		        : ENUM Validation Architecture
	Author(s)	: A. Mayrhofer, B. Hoeneisen
	Filename	: draft-ietf-enum-validation-arch-01.txt
	Pages		: 17
	Date		: 2006-2-7
	
An ENUM domain name is tightly coupled with the underlying E.164
    number.  The process of verifying whether or not the Registrant of an
    ENUM domain name is identical to the Assignee of the corresponding
    E.164 number is commonly called "validation".  This document
    describes validation requirements and a high level architecture for
    an ENUM validation infrastructure.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-enum-validation-arch-01.txt



The intent of the last call is to solicit comments before submitting the
ID to the IESG as a Proposed Standard.

This document has been under discussion since early 2005.

The purpose of a working group Last Call is in the style of "speak now
or forever hold your peace" in case there are fundamental objections
which have not gotten previous or adequate discussion, or minor errors
which need correction.

Work group last call will extend for 2 weeks or so from today Feb 8
until at least Feb 24 though we can modify that if new issues come up.


-- 


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
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