I-D ACTION:draft-rosen-iptel-dialstring-04.txt

Hi,

Would it be possible to use dial-context also in option #1?

Because, if phone-context as a SIP-URI parameter confuses
with Tel-Uri,
doesn't it also confuses with Tel-Uri even more if it's
part of the user
part?

Regards,

Christer 

-----Original Message-----
From: Brian Rosen [mailto:brbrianrosen.net] 
Sent: 9. elokuuta 2006 18:22
To: 'Bob Penfield'; Christer Holmberg (JO/LMF); 'Francois
Audet'; 'Paul
Kyzivat'; 'Stastny Richard'
Cc: iptelietf.org
Subject: RE: [Iptel] Re: I-D
ACTION:draft-rosen-iptel-dialstring-04.txt

I am agreeing with option #1

> -----Original Message-----
> From: Bob Penfield [mailto:BPenfieldacmepacket.com]
> Sent: Wednesday, August 09, 2006 11:12 AM
> To: Brian Rosen; 'Christer Holmberg (JO/LMF)';
'Francois Audet'; 'Paul

> Kyzivat'; 'Stastny Richard'
> Cc: iptelietf.org
> Subject: Re: [Iptel] Re: I-D 
> ACTION:draft-rosen-iptel-dialstring-04.txt
> 
> Brian,
> 
> I am now totally confused as to what your current
proposal is.
> 
> If dialstring is going to be done in a SIP-URI 'like'
a telephone 
> number, then I would say the phone-context goes in the
user part. This

> makes sense to me because 'user=phone' means the
userinfo of the SIP 
> URI contains a tel-URI. Granted we don't have a
dial-URI, but it also 
> makes sense to me that 'user=dialstring' means that
the userinfo 
> contains all the information about the dialstring,
similar to a 
> tel-URI. If that is the case, then phone-context
belongs in the user 
> part.
> 
> On the other hand, if we insist on the context being a
SIP-URI 
> parameter, I would recommend we choose a different name
(e.g. 
> dial-context) so that its not confused with the tel-URI
phone-context.

> But that still leaves the question of what does a
phone-context 
> SIP-URI parameter mean when user-dialstring is no
present?
> 
> In summary, I see two options:
> 
> 1) <sip:1234;phone-context=example.comexample.net;user=dialstring>
> 
> 2) <sip:1234example.net;user=dialstring;dial-context=example.com&
gt;
> 
> I personally prefer option #1.
> 
> cheers,
> (-:bob
> 
> Robert F. Penfield
> Chief Software Architect
> Acme Packet, Inc.
> 71 Third Avenue
> Burlington, MA 01803
> bpenfieldacmepacket.com
> 
> 
> ----- Original Message -----
> From: "Brian Rosen" <brbrianrosen.net>
> To: "'Christer Holmberg (JO/LMF)'"
<christer.holmbergericsson.com>; 
> "'Francois Audet'" <audetnortel.com>; "'Paul Kyzivat'"
> <pkyzivatcisco.com>; "'Stastny
Richard'" <Richard.Stastnyoefeg.at>
> Cc: <iptelietf.org>
> Sent: Wednesday, August 09, 2006 9:25 AM
> Subject: RE: [Iptel] Re: I-D 
> ACTION:draft-rosen-iptel-dialstring-04.txt
> 
> 
> > Aha.  I see where I have confused you.
> >
> > The first "GOOD" is how a telephone
number is expressed in a sip
uri.
> It
> > is
> > a correctly formed user=phone, copying the
phone-context parameter 
> > as described in the tel uri rfc.  It is NOT a
dialstring example, it

> > is a telephone number example.
> >
> > The three examples show that if a telephone number
with user=phone 
> > has a phone-context before the '', it
looks really wrong to show 
> > the same phone-context parameter after the '' if
user=dialstring.  
> > The
> user=phone
> > and user=dialstring parameters should look the
same.
> >
> > Even if you changed the name of the parameter, it
still would look 
> > 'wrong', even if the ABNF made it right.
> >
> > Brian
> >
> >> -----Original Message-----
> >> From: Christer Holmberg (JO/LMF)
> [mailto:christer.holmbergericsson.com]
> >> Sent: Wednesday, August 09, 2006 9:04 AM
> >> To: Brian Rosen; Francois Audet; Paul Kyzivat;
Stastny Richard
> >> Cc: iptelietf.org
> >> Subject: RE: [Iptel] Re: I-D 
> >> ACTION:draft-rosen-iptel-dialstring-04.txt
> >>
> >>
> >> Hi,
> >>
> >> >Please read the draft.
> >> >
> >> >We spent a long time in the evolution of
this draft on the 
> >> >question of
> >> whether or not we would extend the tel uri to
> >> >cover dialstrings, or do what this version
(and several previous
> >> versions) do, which is to NOT allow
dialstrings in a tel
> >> >uri, but rather restrict them to a sip
uri, with user=dialstring.

> >> >It
> >> was a consensus to NOT extend the tel uri, and
to
> >> >restrict dialstrings to sip uris only. 
I'd really rather not 
> >> >revisit
> >> that issue.
> >> >
> >> >If a SIP uri contains a dialstring, there
has to be something that
> >> tells you it's not a telephone number and is
a
> >> >dialstring, so your suggestion is not
acceptable I think.
> >>
> >> So, in the first GOOD, what tells you the
number is a dial string? 
> >> To
> me
> >> it looks like a normal Tel-Uri local number
which has been 
> >> converted into a SIP-Uri...
> >>
> >> Regards,
> >>
> >> Christer
> >>
> >>
> >>
> >> > -----Original Message-----
> >> > From: Christer Holmberg (JO/LMF)
> >> > [mailto:christer.holmbergericsson.com]
> >> > Sent: Wednesday, August 09, 2006 8:49 AM
> >> > To: Brian Rosen; Francois Audet; Paul
Kyzivat; Stastny Richard
> >> > Cc: iptelietf.org
> >> > Subject: RE: [Iptel] Re: I-D
> >> >
ACTION:draft-rosen-iptel-dialstring-04.txt
> >> >
> >> >
> >> > Hi,
> >> >
> >> > I think the first GOOD is good, but the
second GOOD is bad. Why 
> >> > would we need to define a new
phone-context SIP URI parameter? 
> >> > Also, the first GOOD is
"comaptible" with a Tel-Uri.
> >> >
> >> > IF we really need to indicate
"dialstring" somewhere I think it
> should
> >>
> >> > be a new Tel-Uri parameter.
> >> >
> >> > E.g.
> >> >
> >> > sip:1234;phone-
> context=atlanta.example.com;xxx=dialstringatlanta.exam
> >> > pl
> >> > e.com;user=phone
> >> >
> >> > Regards,
> >> >
> >> > Christer
> >> >
> >> >
> >> > -----Original Message-----
> >> > From: Brian Rosen [mailto:brbrianrosen.net]
> >> > Sent: 9. elokuuta 2006 15:41
> >> > To: Christer Holmberg (JO/LMF);
'Francois Audet'; 'Paul Kyzivat';

> >> > 'Stastny Richard'
> >> > Cc: iptelietf.org
> >> > Subject: RE: [Iptel] Re: I-D
> >> >
ACTION:draft-rosen-iptel-dialstring-04.txt
> >> >
> >> > In an effort to close this issue, I had a
private email exchange 
> >> > with Paul Kyzivat.  The part of that that
swayed me was that he 
> >> > pointed
> out
> >>
> >> > I was
> >> > advocating:
> >> >
> >> > GOOD:
sip:1234;phone-context=atlanta.example.comatlanta.example.com
> >> >           ;user=phone
> >> >
> >> > BAD:
sip:1234;phone-context=atlanta.example.comatlanta.example.com
> >> >           ;user=dialstring
> >> >
> >> > GOOD:
sip:1234atlanta.example.com;phone-context=atlanta.example.com
> >> >           ;user=dialstring
> >> >
> >> > I looked at that, and pretty quickly
decided I was wrong and he 
> >> > was right.
> >> >
> >> > Brian
> >> >
> >> > > -----Original Message-----
> >> > > From: Christer Holmberg (JO/LMF) 
> >> > > [mailto:christer.holmbergericsson.com]
> >> > > Sent: Wednesday, August 09, 2006
3:37 AM
> >> > > To: Francois Audet; Brian Rosen;
Paul Kyzivat; Stastny Richard
> >> > > Cc: iptelietf.org
> >> > > Subject: RE: [Iptel] Re: I-D
> >> > >
ACTION:draft-rosen-iptel-dialstring-04.txt
> >> > >
> >> > >
> >> > > Hi,
> >> > >
> >> > > Currently the draft does not talk
about Tel-Uri. Also, since 
> >> > > user=phone is not used, the user
part syntax is not even 
> >> > > required (as per RFC3261) to be
according to RFC3966. So, from 
> >> > > that perspective there is no
requirement to be consistent with
Tel-Uri.
> >> > >
> >> > > The draft only talks about a Sip-Uri
extension/parameter, so in
> that
> >>
> >> > > case the parameter should of be
located after the host part.
> >> > >
> >> > > HOWEVER, I DO agree with Farncois
(and others). We should talk
> about
> >>
> >> > > a
> >> >
> >> > > Tel-Uri extension. But, then we also
need to define that if 
> >> > > user=dialstrong, the user part shall
be parsed as defined in
> RFC3966
> >>
> >> > > (similar to user=phone).
> >> > >
> >> > > Regards,
> >> > >
> >> > > Christer
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > -----Original Message-----
> >> > > From: Francois Audet
[mailto:audetnortel.com]
> >> > > Sent: 8. elokuuta 2006 23:13
> >> > > To: Brian Rosen; Paul Kyzivat;
Stastny Richard
> >> > > Cc: iptelietf.org
> >> > > Subject: RE: [Iptel] Re: I-D
> >> > >
ACTION:draft-rosen-iptel-dialstring-04.txt
> >> > >
> >> > > I agree with Paul, Richard and
everybody else on this thread.
> >> > >
> >> > > I'm not sure why you say this is an
open issue. It seems that 
> >> > > everybody agrees but the author...
> >> > >
> >> > > It needs to be consistent with Tel
URI.
> >> > >
> >> > > A URI is a URI. It needs to be
Unique. The phone-context makes 
> >> > > it unique because it is in the user
part.
> >> > >
> >> > > > -----Original Message-----
> >> > > > From: Brian Rosen
[mailto:brbrianrosen.net]
> >> > > > Sent: Sunday, July 09, 2006
10:16 AM
> >> > > > To: 'Paul Kyzivat'; Stastny
Richard
> >> > > > Cc: iptelietf.org
> >> > > > Subject: RE: [Iptel] Re: I-D
> >> > > >
ACTION:draft-rosen-iptel-dialstring-04.txt
> >> > > >
> >> > > > The form of the parameter is an
open issue; I don't agree 
> >> > > > that it should be a URI
parameter.
> >> > > >
> >> > > > The * & # is an oversight,
and I'll get it fixed one way or
> >> another.
> >> > > >
> >> > > > Brian
> >> > > >
> >> > > > -----Original Message-----
> >> > > > From: Paul Kyzivat
[mailto:pkyzivatcisco.com]
> >> > > > Sent: Wednesday, July 05, 2006
5:20 PM
> >> > > > To: Stastny Richard
> >> > > > Cc: iptelietf.org; Rosen, Brian
> >> > > > Subject: Re: [Iptel] Re: I-D
> >> > > >
ACTION:draft-rosen-iptel-dialstring-04.txt
> >> > > >
> >> > > > I agree with Richard. And I
brought it up on the -03 (and the

> >> > > > -02 I
> >> > > > think) versions as well. There
is also the issue of * & #.
> >> > > > I'm attaching an old message
that covers most of that.
> >> > > >
> >> > > > Paul
> >> > > >
> >> > > > Stastny Richard wrote:
> >> > > > > Hi Brian,
> >> > > > >
> >> > > > > IMHO the examples are
wrong:
> >> > > > >
> >> > > > > e.g.:
> >> > > > >    sip:123sippbx.example.com;user=dialstring;
> >> > > > >      
phone-context=atlanta.example.com
> >> > > > >
> >> > > > > should read:
> >> > > > >
> >> > > >
sip:123;phone-context=atlanta.example.comsippbx.example.com;
> >> > > > u
> >> > > > ser=dialstring
> >> > > > >
> >> > > > > Phone-context is part of
the tel: URI and not from the sip 
> >> > > > > URI
> >> > > > >
> >> > > > > -sta
> >> > > > >
> >> > > > >
________________________________
> >> > > > >
> >> > > > > Von: Internet-Draftsietf.org 
> >> > > > >
[mailto:Internet-Draftsietf.org]
> >> > > > > Gesendet: Mi 28.06.2006
00:50
> >> > > > > An: i-d-announceietf.org
> >> > > > > Betreff: I-D
ACTION:draft-rosen-iptel-dialstring-04.txt
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > A New Internet-Draft is
available from the on-line 
> >> > > > > Internet-Drafts
> >> > > > directories.
> >> > > > >
> >> > > > >
> >> > > > >         Title           :
Dialstring parameter for the
Session
> >> > > > >                          
Initiation Protocol Uniform
Resource
> >> > > > >                          
Identifier
> >> > > > >         Author(s)       :
B. Rosen
> >> > > > >         Filename        :
draft-rosen-iptel-dialstring-04.txt
> >> > > > >         Pages           :
8
> >> > > > >         Date            :
2006-6-27
> >> > > > >
> >> > > > > RFC3966 explicitly states
that 'tel' URIs may not represent

> >> > > > > a
> >> dial
> >> > > > >    string.  That leaves no
way specify a dial string in a
> >> > > > standardized
> >> > > > >    way.  Great confusion
exists with the SIP URI parameter
> >> > > > "user=phone",
> >> > > > >    and specifically, if it
can represent a dial string.  
> >> > > > > This
> >> memo
> >> > > > >    creates a new value for
the user parameter "dialstring",
> >> > > > so that one
> >> > > > >    may specify
"user=dialstring" to encode a dial string as
> >> > > > a 'sip:' or
> >> > > > >    'sips:' URI.
> >> > > > >
> >> > > > > A URL for this
Internet-Draft is:
> >> > > > >
> >> > > >
> >>
http://www.ietf.org/internet-drafts/draft-ro
sen-iptel-dialstring-04.
> >> > > > tx
> >> > > > > t
> >> > > > >
> >> > > > > To remove yourself from
the I-D Announcement list, send a
> >> > > > message to
> >> > > > > i-d-announce-requestietf.org
with the word unsubscribe in
> >> > > > the body of
> >> > > > > the
> >> > > > message.
> >> > > > > You can also visit
> >> > > > h
ttps://www1.ietf.org/mailman/listinfo/I-D-announce
> >> > > > > to change your
subscription settings.
> >> > > > >
> >> > > > >
> >> > > > > Internet-Drafts are also
available by anonymous FTP. Login 
> >> > > > > with the
> >> > > > username
> >> > > > > "anonymous"
and a password of your e-mail address. After
> >> > > > logging in,
> >> > > > > type "cd
internet-drafts" and then
> >> > > > >         "get
draft-rosen-iptel-dialstring-04.txt".
> >> > > > >
> >> > > > > A list of Internet-Drafts
directories can be found in 
> >> > > > > http://www.ietf.org/s
hadow.html or 
> >> > > > >
ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >> > > > >
> >> > > > >
> >> > > > > Internet-Drafts can also
be obtained by e-mail.
> >> > > > >
> >> > > > > Send a message to:
> >> > > > >         mailservietf.org.
> >> > > > > In the body type:
> >> > > > >         "FILE
> >> >
/internet-drafts/draft-rosen-iptel-dialstring-04.txt".
> >> > > > >
> >> > > > > NOTE:   The mail server at
ietf.org can return the document
in
> >> > > > >         MIME-encoded form
by using the "mpack" utility.  To

> >> > > > > use
> >> > this
> >> > > > >         feature, insert
the command "ENCODING mime" before
> >> > > > the "FILE"
> >> > > > >         command.  To
decode the response(s), you will need
> >> > > > "munpack" or
> >> > > > >         a MIME-compliant
mail reader.  Different 
> >> > > > > MIME-compliant mail
> >> > > > readers
> >> > > > >         exhibit different
behavior, especially when dealing
> with
> >> > > > >        
"multipart" MIME messages (i.e. documents which
> >> > > > have been split
> >> > > > >         up into multiple
messages), so check your local
> >> > > > documentation on
> >> > > > >         how to manipulate
these messages.
> >> > > > >
> >> > > > >
> >> > > > > Below is the data which
will enable a MIME compliant mail
> reader
> >>
> >> > > > > implementation to
automatically retrieve the ASCII version 
> >> > > > > of the Internet-Draft.
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > >
------------------------------------------------------------
-
> >> > > > ----
> -
> >> > > > --
> >> > > > --
> >> > > > > --
> >> > > > >
> >> > > > >
_______________________________________________
> >> > > > > I-D-Announce mailing list
> >> > > > > I-D-Announceietf.org
> >> > > > > h
ttps://www1.ietf.org/mailman/listinfo/i-d-announce
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > >
------------------------------------------------------------
-
> >> > > > ----
> -
> >> > > > --
> >> > > > --
> >> > > > > --
> >> > > > >
> >> > > > >
_______________________________________________
> >> > > > > Iptel mailing list
> >> > > > > Iptelietf.org
> >> > > > > https://
www1.ietf.org/mailman/listinfo/iptel
> >> > > >
> >> > > >
> >> > > >
_______________________________________________
> >> > > > Iptel mailing list
> >> > > > Iptelietf.org
> >> > > > https://
www1.ietf.org/mailman/listinfo/iptel
> >> > > >
> >> > >
> >> > >
_______________________________________________
> >> > > Iptel mailing list
> >> > > Iptelietf.org
> >> > > https://
www1.ietf.org/mailman/listinfo/iptel
> >
> >
> > _______________________________________________
> > Iptel mailing list
> > Iptelietf.org
> > https://
www1.ietf.org/mailman/listinfo/iptel
> >

_______________________________________________
Iptel mailing list
Iptelietf.org
https://
www1.ietf.org/mailman/listinfo/iptel

I-D ACTION:draft-rosen-iptel-dialstring-04.txt

Thread: I-D ACTION:draft-rosen-iptel-dialstring-04.txt