RE: [Enum] The larger issue here.

Because the IETF defines the voice mail service for the PSTN as the VPIM
standard. We generally don't go around creating enum services for things
that are not defined as a standard.

Frankly,  from the comments you are seeing I would not be optimistic on the
chances a draft along the lines you propose would make it through the WG.

> -----Original Message-----
> From: Jackson, James [mailto:james_jackson@labs.att.com]
> Sent: Tuesday, January 30, 2007 10:58 PM
> To: richard@shockey.us; Stastny Richard; Paul Kyzivat
> Cc: enum@ietf.org
> Subject: RE: [Enum] The larger issue here.
> 
> 
> That's fine. RFC4238 works great if the voicemail system implements VPIM
> - most do not. The VPIM service defines e-mail access to voicemail much
> like the ifax service defines e-mail access to fax. However, there is
> also a fax service for PSTN. If someone could shed some light on why a
> voicemail service for PSTN is unreasonable that would be appreciated.
> 
> Thanks,
> James
> 
> -----Original Message-----
> From: Richard Shockey [mailto:richard@shockey.us]
> Sent: Tuesday, January 30, 2007 9:20 PM
> To: 'Stastny Richard'; 'Paul Kyzivat'
> Cc: enum@ietf.org
> Subject: [Enum] The larger issue here.
> 
> 
> Chair hat off .. I agree with Mr. Stastny and Mr. Kyzivat as well. And
> with
> the argument that Jason Livingood makes that this is really covered By
> RFC
> 4238.
> 
> Chair hat on...
> 
> The larger issue is one we will need to deal with in Prague is that this
> work group is winding down. With the Infrastructure ENUM issues now in
> the
> hands of "higher authority" we have only one real task which is the
> advancement of RFC 3761 to Draft.
> 
> We do need to declare victory here and start to close up shop unless
> there
> is compelling technical reasons not to do so and frankly I have not seen
> one
> recently.
> 
> 
> > -----Original Message-----
> > From: Stastny Richard [mailto:Richard.Stastny@oefeg.at]
> > Sent: Tuesday, January 30, 2007 4:03 PM
> > To: Paul Kyzivat
> > Cc: enum@ietf.org
> > Subject: Re: [Enum] Proposal for new enumservice "voicemail", using
> SIP
> > URI
> >
> > I fully support this argument
> > Richard
> >
> > ________________________________
> >
> > Von: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Gesendet: Di 30.01.2007 20:33
> > An: Jackson, James
> > Cc: enum@ietf.org; Shawn Pouliotte; Duane
> > Betreff: Re: [Enum] Proposal for new enumservice "voicemail", using
> SIP
> > URI
> >
> >
> >
> > A fundamental problem I have with using ENUM is that it is
> fundamentally
> > tied to cases where the address of the callee is an E.164 number. That
> > is fine in cases where the problem is intrinsically tied to the use of
> a
> > phone number. But it is an unappealing solution to any problem that
> also
> > applies when the callee is identified by a SIP URI. I certainly see
> that
> > to be the case here. I just as well may want to get to the VM for
> > sip:alice@atlanta.com as for tel:+12125551234.
> >
> > BTW, that also means that indicating you want VM by prefixing the
> > address with *99 isn't an ideal interface. I guess it is *an*
> interface,
> > that might be suitable for UAs that can only deal with numbers. But
> > another interface will be needed for alphanumeric calling. I don't
> think
> > the concept of adding to the callee's URI is appropriate in this case.
> > Whatever technique does work for alphanumeric URIs would hopefully
> work
> > for phone numbers as well. In general a sip UA supports a telephone
> > dialing interface already needs to recognize and locally process some
> > star codes, so it ought to be able to do so for this one too.
> >
> >         Paul
> >
> > Jackson, James wrote:
> > > I have been thinking about the PSTN service in another context, but
> > > perhaps it is more generally applicable here. Specifically, consider
> the
> > > case where the called number is purely PSTN and you want to reach
> their
> > > voicemail. In theory an ENUM query could return the Call Forwarding
> > > Number and the call could be forwarded out a Media Gateway. The
> mailbox
> > > would be indicated by the Redirecting Number.
> > >
> > > James
> > >
> > > -----Original Message-----
> > > From: Duane [mailto:duane@e164.org]
> > > Sent: Tuesday, January 30, 2007 9:57 AM
> > > To: Paul Kyzivat
> > > Cc: Jackson, James; enum@ietf.org; Shawn Pouliotte
> > > Subject: Re: [Enum] Proposal for new enumservice "voicemail", using
> SIP
> > > URI
> > >
> > > Paul Kyzivat wrote:
> > >
> > >> The above assumes that the VM system is arranged in a suitable way.
> > >> Notably that it has a unique and globally routable URI of its own
> for
> > >> each mailbox (possibly by a common URI plus a parameter identifying
> > > the
> > >> mailbox). Or at least that there is a single globally routable URI
> for
> > >
> > >> the VM server and that the caller will be satisfied with having to
> > > enter
> > >> the target phone number a second time.
> > >
> > > While I won't go into the merits of having such an enum service,
> > > (although couldn't it just be a sub-type of pstn?) it seems pretty
> > > trivial to me to be just another SIP URI that could easily be setup,
> > > both in DNS and in most/all software driven PBXs.
> > >
> > > eg
> > >
> > > sip:123456@example.com
> > > voicemail:vm-123456@example.com
> > >
> > > On the PBX you simply look for vm- strip it and send the call into
> the
> > > voicemail system.
> > >
> > > eg
> > >
> > > 100 10 "u" "E2U+PSTN" "!^(.*)$!sip:\\1@example.com!" .
> > > 100 10 "u" "E2U+PSTN" "!^(.*)$!voicemail:vm-\\1@example.com!" .
> > >
> >
> > _______________________________________________
> > enum mailing list
> > enum@ietf.org
> > https://www1.ietf.org/mailman/listinfo/enum
> >
> >
> >
> >
> > _______________________________________________
> > enum mailing list
> > enum@ietf.org
> > https://www1.ietf.org/mailman/listinfo/enum
> 
> 
> _______________________________________________
> enum mailing list
> enum@ietf.org
> https://www1.ietf.org/mailman/listinfo/enum

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum