RE: [Enum] [Fwd: RFC 4238 on Voice Message Routing Service]
"Creighton, Tom" <Tom_Creighton@cable.comcast.com> Thu, 03 November 2005 17:32 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 1EXixE-00046A-4K; Thu, 03 Nov 2005 12:32:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EXixC-000462-SS for enum@megatron.ietf.org; Thu, 03 Nov 2005 12:32:46 -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 MAA16270 for <enum@ietf.org>; Thu, 3 Nov 2005 12:32:24 -0500 (EST)
Received: from pacdcoavas09.cable.comcast.com ([208.17.33.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EXjC2-0005KB-KD for enum@ietf.org; Thu, 03 Nov 2005 12:48:06 -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="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Enum] [Fwd: RFC 4238 on Voice Message Routing Service]
Date: Thu, 03 Nov 2005 12:32:05 -0500
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C7301FBCAAA@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: [Enum] [Fwd: RFC 4238 on Voice Message Routing Service]
Thread-Index: AcXei6PPtLMWx5fgSieWb+e3dtJGXACC0uxQ
From: "Creighton, Tom" <Tom_Creighton@cable.comcast.com>
To: Richard Shockey <richard@shockey.us>, enum@ietf.org
X-OriginalArrivalTime: 03 Nov 2005 17:32:06.0484 (UTC) FILETIME=[82DB0940:01C5E09C]
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Content-Transfer-Encoding: quoted-printable
Cc:
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
>From section 2.2 of RFC 4238: > Example: > > Query: 2.1.2.1.5.5.5.3.1.6.1.e164.arpa > Responses: > IN NAPTR 10 10 "U" "E2U+VPIM:LDAP" \ > "!^.*$!ldap://vdir1.Zcorp.com/telephoneNumber=\1!" . > > IN NAPTR 10 20 "U" " E2U+VPIM:LDAP" \ > "!^.*$!ldap://vdir2.Zcorp.com/telephoneNumber=\1!" . It appears that a backref expression is being used in the repl portion of the substitution expression. Since the ERE section of the substituion expression is not enclosed by '(' and ')', it doesn't appear to be a properly formatted substituion expression. If the desired result is to have the '\1' replaced by original telephone number used in the query, then the regular expression would have to look like one of the following: IN NAPTR 10 10 "U" "E2U+VPIM:LDAP" \ "!(^.*$)!ldap://vdir1.Zcorp.com/telephoneNumber=\1!" . Which would result in: ldap://vdir1.Zcorp.com/telephoneNumber=+16135551212 Or: IN NAPTR 10 10 "U" "E2U+VPIM:LDAP" \ "!^+(.*)$!ldap://vdir1.Zcorp.com/telephoneNumber=\1!" . Which would result in: ldap://vdir1.Zcorp.com/telephoneNumber=16135551212 Regards, Tom -----Original Message----- From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf Of Richard Shockey Sent: Monday, October 31, 2005 9:22 PM To: 'enum@ietf.org' Subject: [Enum] [Fwd: RFC 4238 on Voice Message Routing Service] FYI -------- Original Message -------- Subject: RFC 4238 on Voice Message Routing Service Date: Mon, 31 Oct 2005 16:56:33 -0800 From: rfc-editor@rfc-editor.org To: ietf-announce@ietf.org CC: vpim@ietf.org, rfc-editor@rfc-editor.org A new Request for Comments is now available in online RFC libraries. RFC 4238 Title: Voice Message Routing Service Author(s): G. Vaudreuil Status: Standards Track Date: October 2005 Mailbox: GregV@ieee.org Pages: 10 Characters: 18902 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-vpim-routing-10.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4238.txt Voice messaging is traditionally addressed using telephone number addressing. This document describes two techniques for routing voice messages based on a telephone number. The complete service uses the Voice Profile for Internet Mail (VPIM) Directory service to lookup a VPIM email address with a telephone number and confirm that the address is both valid and associated with the intended recipient. However, this service will take time to become widely deployed in the near term. This document also describes a basic send-and-pray service that routes and delivers messages using only the ENUM telephone number resolution service and the existing DNS mail routing facilities. This document is a product of the Voice Profile for Internet Mail Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 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] [Fwd: RFC 4238 on Voice Message Routing Se… Richard Shockey
- RE: [Enum] [Fwd: RFC 4238 on Voice Message Routin… Creighton, Tom