Re: [Enum] Sufficient information in NAPTRs, MSG, and VOVI

[lconroy <[e-mail]>]

Hi Richard, folks,
Re. application:network identifier vs network identifier:application:
I note that this issue wasn't raised before or during the WGLC or IETF 
LC for MSG,
which includes a registration for 'tel:fax'. Are we really running out 
of reasons
to block/re-assess the MSG draft?

----
Re. do I remember VOVI? - it's indelibly burnt into my brain.
(BTW, I threw this in this originally only so that the Helpdesk crowd 
will know who
 to thank for their full lives - not me :).

SIP was airbrushed out of VOVI-01 way back in 2003 as a reaction to The 
SIP Community
who saw a problem with it. When we next had a chance to talk with Orit 
(who couldn't
be heard in the original meeting for the enthusiasm of The Community :) 
we removed
h323 from the mix as well, in -02 which came out last year after the 
Seoul meeting.
Since then VOVI dealt exclusively with voice and video services using 
E.164 network
identifiers. The only reference to SIP or H323 is to indicate that a 
call to a PLMN
(or PSTN) device may be made indirectly (via a SIP or H323 to PSTN 
gateway).

VOVI-02 has some minor cut-and-paste typos and a reference to RFC2806 
so it needed
a refresh but, as there is an objection, I guess we just let it expire 
in the IETF.
It's in use already so isn't worth the grief.

----
The esteemed co-chair has spoken - I'm not sure in what Language, but I 
get the tone.

all the best,
  Lawrence
On 6 Mar 2005, at 20:43, Richard Shockey wrote:
At 11:08 AM 3/6/2005, lconroy wrote:
Hi folks,
  The conf-service thread has pushed me to a couple of general issues
that have been lurking around.
As "whatever happened to VOVI?" is down on the agenda, I offer this
generalisation for your comments, as I think they're related.
Sorry for its length - those with ADD can skip to the last bit 
starting "In short...".
----

*  The web Enumservice is very similar to a TXT resource record - it's
   general. That's good, and TXT records are already being used to 
show
   a person's name (and/or the textual label one could pop up for this
   E-number). The SIP Enumservice is also general - this generated URI
   "points to" a SIP service and you "do the SIP thing" to negotiate
   further. From a protocol perspective, this is enough information -
   the ENUM client fires up a Web or SIP client and we're done.

    [Of course the provider for that service and the registered SIP
     device set "behind" it may or may not support the communications
     ->mode<- the querying user wants to use. He or she can find out 
by
     firing up a SIP invite, have their machine spend some CPU cycles
     with any puzzle challenge, and then potentially find out that 
they
     don't do IM, for example, or that the registrant hasn't told that
     SIP registrar about their IM-capable device and/or their 
preferred
     presence/IM service with a chained registration.
     It is left as an exercise for the various providers' help desk(s)
     to explain this to their customers. :-]
Yes ... we had this debate before remember there was substantial 
objections by the SIP community to adding granular information or 
hints to the registration as in E2U+sip:voice   E2U+sip:im   etc .. 
personally Ive never seen the reason for the objection but I respect 
the opinion of those who see a problem here. I'd be willing to revisit 
the issue if there was as good argument to do so.

Now on the issue of the VOVI draft ..no it is not on the agenda since 
I did not have a request for it..but frankly I dont like it.

What I want is a comprehensive tel registration document and we need 
that now for several reasons.

What I would like to see is where tel is the type and everything else 
is a subtype.

tel:voice
tel:fax
tel:sms
tel:mms
i dont want them reversed  IMHO voice is not a "type" in this  context
maybe

*  ______________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   sip:57141 at fwd.pulver.com
ENUM [phone]
PSTN Office +1 571.434.5651 PSTN Mobile: [phone],  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 at ietf.org
https://www1.ietf.org/mailman/listinfo/enum

---------------------------------------
lawrence conroy    |tel:[phone]
_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum