Re: [Enum] DNS for E.164-IP Address Mapping

Richard Shockey <rshockey@ix.netcom.com> Fri, 07 January 2000 19:35 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25727 for <enum-archive@ietf.org>; Fri, 7 Jan 2000 14:35:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15264; Fri, 7 Jan 2000 14:34:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15235 for <enum@optimus.ietf.org>; Fri, 7 Jan 2000 14:34:10 -0500 (EST)
Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25710 for <enum@ietf.org>; Fri, 7 Jan 2000 14:35:05 -0500 (EST)
Received: from laptop (stl-mo16-50.ix.netcom.com [207.222.134.50]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id OAA25363; Fri, 7 Jan 2000 14:34:57 -0500 (EST)
Message-Id: <4.2.0.58.20000107132445.00a18210@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date: Fri, 07 Jan 2000 13:34:18 -0600
To: James Yu <james.yu@neustar.com>
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: Re: [Enum] DNS for E.164-IP Address Mapping
Cc: enum@ietf.org, jdrosen@dynamicsoft.com, paf@swip.net
In-Reply-To: <38763438.F32B1369@dynamicsoft.com>
References: <ED88182BFF78D211A4D800A0C9E9435C3BE9ED@dc02.npac.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org

At 01:45 PM 1/7/2000 -0500, Jonathan Rosenberg wrote:
>I used the work "mechanism" when URI scheme is the correct term. Check
>rfc2396 for a general discussion. There are many URI schemes defined;
>I'm not sure if there is an IANA procedure somewhere defined for
>registering them.
>
>-Jonathan R.


Well for telephony applications there is a draft outlining how the URL's 
should be defined. I'm sure if there were other types of applications that 
need to be referenced in NAPTR records... Universal Messaging Servers, 
T.38, it should be no trouble defining a simple registration procedure.

Jonathan.... one of the things I'm increasingly concerned about is DNS 
security here. Do you have any thoughts on how much of DNSSEC we might have 
to require?


Title           : URLs for Telephone Calls
         Author(s)       : A. Vaha-Sipila
         Filename        : draft-antti-telephony-url-12.txt
         Pages           : 22
         Date            : 29-Dec-99

This document specifies URL (Uniform Resource Locator) schemes
'tel', 'fax' and 'modem' for specifying the location of a
terminal in the phone network and the connection types (modes of
operation) that can be used to connect to that entity. This
specification covers voice calls (normal phone calls, answering
machines and voice messaging systems), facsimile (telefax) calls and
data calls, both for POTS and digital/mobile subscribers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-antti-telephony-url-12.txt



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
GSTN Fax 314.918.9015
MediaGate iPost VoiceMail and Fax 800.260.4464
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

_______________________________________________
enum mailing list
enum@ietf.org
http://www.ietf.org/mailman/listinfo/enum