Re: [Enum] a suggestion re: using flags to distinguish post-ENUM signaling f lows
Richard Shockey <richard@shockey.us> Tue, 07 February 2006 18:37 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 1F6Xi6-0003XT-Vh; Tue, 07 Feb 2006 13:37:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6Xi2-0003WX-1l; Tue, 07 Feb 2006 13:37:05 -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 NAA18980; Tue, 7 Feb 2006 13:35:13 -0500 (EST)
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6XuL-00028Z-I2; Tue, 07 Feb 2006 13:49:45 -0500
Received: from [10.31.13.183] (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k17IapLF028802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 10:36:52 -0800
Message-ID: <43E8E897.3060609@shockey.us>
Date: Tue, 07 Feb 2006 13:36:07 -0500
From: Richard Shockey <richard@shockey.us>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Stafford, Matthew" <matthew.stafford@cingular.com>
Subject: Re: [Enum] a suggestion re: using flags to distinguish post-ENUM signaling f lows
References: <DE175C3426C51144B22109E3346CFFA421774074@S75202E004049.sbms.sbc.com>
In-Reply-To: <DE175C3426C51144B22109E3346CFFA421774074@S75202E004049.sbms.sbc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Found to be clean
X-Songbird-From: richard@shockey.us
X-Spam-Score: 0.8 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Cc: enum@ietf.org, speermint@ietf.org, lconroy <lconroy@insensate.co.uk>
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
> ==> I take your point regarding the headaches w/changes to clients. > ==> However, I'm not sure I agree that this is limited to carrier/infra- > ==> ENUM, at least if we think of that in terms of traditional telcos/ > ==> cellcos. For example, does this discussion really bear no relevance > ==> to enterprise applications (e.g., I want to call into my company's > ==> IP PBX while I'm on the road?) > > It appears that the proposed 'g' flag is appropriate only for SIP use > within Carrier ENUM, so one could WELL argue that this is an issue for the > SIP URI - I don't see how it can be used for other Enumservices (like > email:mailto, for example). Perhaps adding a SIP parameter (akin to ;user=phone) > would be more appropriate, or adding a new Enumservice to run alongside the > existing SIP one (i.e. to develop a new Enumservice definition RFC to specify > a SIP Gateway service)? That would be my strong recommendation. Something like E2U+sip:pstngw > > ==> That would have a similar effect to the flag proposal, in the sense > ==> that the contents of the ENUM NAPTR offer guidance on what to do next > ==> (which is really what I'm after) > > ==> For the sake of discussion, here's a similar example using the > recently-==> standardized Enumservice mms:mailto... an 'm' flag > indicating that the ==> NAPTR recipient should now look for an MX > Resource Record. Lets not even start a discussion over using the flag field ..I do't think that will go very far. IMHO a non starter. URI extentions or Enumservice definitions are the way to go > > all the best, > Lawrence > > -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 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] a suggestion re: using flags to distinguis… Stafford, Matthew
- Re: [Enum] a suggestion re: using flags to distin… lconroy
- Re: [Enum] a suggestion re: using flags to distin… Richard Shockey
- Re: [Enum] a suggestion re: using flags to distin… Tony Rutkowski
- RE: [Speermint] Re: [Enum] a suggestion re: using… Henry Sinnreich
- [Enum] ENUM Test Specificatiobns Tony Rutkowski
- Re: [Enum] ENUM Test Specificatiobns Jim Reid
- Re: [Enum] ENUM Test Specificatiobns Adrian Georgescu
- Re: [Enum] ENUM Test Specificatiobns lconroy
- RE: [Enum] a suggestion re: using flags to distin… Stafford, Matthew
- RE: [Enum] a suggestion re: using flags to distin… Stafford, Matthew
- RE: [Enum] a suggestion re: using flags to distin… Stafford, Matthew
- Re: [Enum] a suggestion re: using flags to distin… Richard Shockey
- Re: [Enum] a suggestion re: using flags to distin… Adrian Georgescu
- Re: [Enum] a suggestion re: using flags to distin… Stastny Richard
- Re: [Enum] a suggestion re: using flags to distin… Richard Shockey
- RE: [Enum] a suggestion re: using flags to distin… Stafford, Matthew
- Re: [Speermint] Re: [Enum] a suggestion re: using… Dean Willis
- Re: [Speermint] RE: [Enum] a suggestion re: using… Duane