RE: [Enum] Additional Agenda Item for Chicago .. Infrastructure ENUMdocument status
"PFAUTZ, PENN L, ATTCORP" <ppfautz@att.com> Tue, 17 July 2007 21:51 UTC
Return-path: <enum-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAuxI-0008LV-6P; Tue, 17 Jul 2007 17:51:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAuxG-0008LN-Kg for enum@ietf.org; Tue, 17 Jul 2007 17:51:38 -0400
Received: from mail146.messagelabs.com ([216.82.245.131]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAuxF-0000IQ-AT for enum@ietf.org; Tue, 17 Jul 2007 17:51:38 -0400
X-VirusChecked: Checked
X-Env-Sender: ppfautz@att.com
X-Msg-Ref: server-15.tower-146.messagelabs.com!1184709095!9386572!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 27212 invoked from network); 17 Jul 2007 21:51:35 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-15.tower-146.messagelabs.com with AES256-SHA encrypted SMTP; 17 Jul 2007 21:51:35 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id l6HLpZ5h009716; Tue, 17 Jul 2007 17:51:35 -0400
Received: from ACCLUST02EVS1.ugd.att.com (acst03.ugd.att.com [135.37.16.8]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id l6HLpTVP009684; Tue, 17 Jul 2007 17:51:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7C8BC.A15DCA96"
Subject: RE: [Enum] Additional Agenda Item for Chicago .. Infrastructure ENUMdocument status
Date: Tue, 17 Jul 2007 17:51:25 -0400
Message-ID: <34DA635B184A644DA4588E260EC0A25A0FE33B56@ACCLUST02EVS1.ugd.att.com>
In-Reply-To: <016701c7c8b3$d6d6efe0$8484cfa0$@us>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: [Enum] Additional Agenda Item for Chicago .. Infrastructure ENUMdocument status
Thread-Index: AcfIs9OC2NQp5ehvTxifh6PnpT9pLQABz6Ww
References: <016701c7c8b3$d6d6efe0$8484cfa0$@us>
From: "PFAUTZ, PENN L, ATTCORP" <ppfautz@att.com>
To: Richard Shockey <richard@shockey.us>, enum@ietf.org
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b84f8c8fba0e1389e5eb998b64078964
Cc: Cullen Jennings <fluffy@cisco.com>, "Peterson, Jon" <jon.peterson@neustar.biz>
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>
Errors-To: enum-bounces@ietf.org
Rich: I believe there has been a new draft of the infrastructure ENUM requirements I-D for a while (draft-ietf-enum-infrastructure-enum-reqs-04.txt, 5/21) that addressed the last round of ISEG comments (I saw a couple of position changes in the I-D tracker) and the document passed to AD follow-up. Is there something else that needs to be done? I am trying to work with my co-authors on the draft-ietf-enum-infrastructure document to get a revision. Penn Pfautz AT&T National Access Management +1-732-420-4962 -----Original Message----- From: Richard Shockey [mailto:richard@shockey.us] Sent: Tuesday, July 17, 2007 4:48 PM To: enum@ietf.org Cc: 'Cullen Jennings'; 'Peterson,Jon' Subject: [Enum] Additional Agenda Item for Chicago .. Infrastructure ENUMdocument status In discussions with our AD Mr. Peterson there seems to be confusion on what the status of the 4 documents that represent the Infrastructure ENUM drafts. They are all basically waiting for revised drafts which is holding up "other matters". We will need to discuss the status of these documents in Chicago in order to expedite things along. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 <mailto:richard(at)shockey.us> <mailto:richard.shockey(at)neustar.biz> _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum
--- Begin Message ---A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : Infrastructure ENUM Requirements Author(s) : S. Lind, P. Pfautz Filename : draft-ietf-enum-infrastructure-enum-reqs-04.txt Pages : 8 Date : 2007-5-21 This document provides requirements for "infrastructure" or "carrier" ENUM (E.164 Number Mapping), defined as the use of RFC 3761 technology to facilitate interconnection of networks for E.164 number addressed services, in particular but not restricted to VoIP (Voice over IP.) A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum- reqs-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-infrastructure-enum-reqs-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.--- End Message ---
_______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum
- [Enum] Additional Agenda Item for Chicago .. Infr… Richard Shockey
- RE: [Enum] Additional Agenda Item for Chicago .. … PFAUTZ, PENN L, ATTCORP
- RE: [Enum] Additional Agenda Item for Chicago .. … Richard Shockey
- Re: [Enum] Additional Agenda Item for Chicago .. … Otmar Lendl
- RE: [Enum] Additional Agenda Item for Chicago- RE… Richard Shockey