List Info

Thread: RE: "*" and "#" signs in the userinfo of SIP URI




RE: "*" and "#" signs in the userinfo of SIP URI
country flaguser name
United States
2007-03-09 09:47:13
Meaning you insist I rev the draft again, and wait another
IESG cycle?

Brian

> -----Original Message-----
> From: David R Oran [mailto:orancisco.com]
> Sent: Friday, March 09, 2007 10:40 AM
> To: Henning Schulzrinne
> Cc: iptelietf.org; Juha Heinanen; Christer Holmberg
(JO/LMF)
> Subject: Re: [Iptel] "*" and "#"
signs in the userinfo of SIP URI
> 
> 
> On Mar 9, 2007, at 9:06 AM, Henning Schulzrinne wrote:
> 
> >
> > On Mar 9, 2007, at 9:01 AM, Christer Holmberg
((JO/LMF)) wrote:
> >
> >> I don't think your draft needs to talk about
what has to be escapted
> >> etc, because that is handled by 3261.
> >>
> >
> > I think a reasonable mechanism is to focus on the
"input" character
> > set and encoding, before URL encoding. The latter
is largely a
> > mechanical process that's invisible to the user,
except when
> > writing URLs on napkins. If we later (3261bis)
change our minds and
> > say that # does not need to be escaped,
"old" (escaped) URLs will
> > still work and have the same meaning.
> >
> > Personally, I think using E and F is a hack that
will likely lead
> > to mistakes and confusion since nobody will be
able to remember
> > whether E represents # or * (or that they are at
all connected).
> >
> > My suggestion: Briefly describe the issues
surrounding # and say
> > that it needs to be %-encoded. Done. (There
doesn't seem to be a
> > need to encode *.)
> >
> > Henning
> >
> >
> I agree with Henning.
> DaveO.
> 
> > _______________________________________________
> > 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

Re: "*" and "#" signs in the userinfo of SIP URI
country flaguser name
United States
2007-03-09 09:50:34
I suspect compared to the time it will take from here to RFC
 
publication, an IESG cycle is likely less than 10% of the
total. I  
wish it were different, but this seems like the wrong
optimization  
point.

On Mar 9, 2007, at 10:47 AM, Brian Rosen wrote:

> Meaning you insist I rev the draft again, and wait
another IESG cycle?
>
> Brian


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

Re: "*" and "#" signs in the userinfo of SIP URI
country flaguser name
United States
2007-03-09 09:55:15
On Mar 9, 2007, at 10:47 AM, Brian Rosen wrote:

> Meaning you insist I rev the draft again, and wait
another IESG cycle?
>
Not necessarily. Changes of this magnitude are often made
without  
another last call.
> Brian
>
>> -----Original Message-----
>> From: David R Oran [mailto:orancisco.com]
>> Sent: Friday, March 09, 2007 10:40 AM
>> To: Henning Schulzrinne
>> Cc: iptelietf.org; Juha Heinanen; Christer Holmberg
(JO/LMF)
>> Subject: Re: [Iptel] "*" and
"#" signs in the userinfo of SIP URI
>>
>>
>> On Mar 9, 2007, at 9:06 AM, Henning Schulzrinne
wrote:
>>
>>>
>>> On Mar 9, 2007, at 9:01 AM, Christer Holmberg
((JO/LMF)) wrote:
>>>
>>>> I don't think your draft needs to talk
about what has to be  
>>>> escapted
>>>> etc, because that is handled by 3261.
>>>>
>>>
>>> I think a reasonable mechanism is to focus on
the "input" character
>>> set and encoding, before URL encoding. The
latter is largely a
>>> mechanical process that's invisible to the
user, except when
>>> writing URLs on napkins. If we later (3261bis)
change our minds and
>>> say that # does not need to be escaped,
"old" (escaped) URLs will
>>> still work and have the same meaning.
>>>
>>> Personally, I think using E and F is a hack
that will likely lead
>>> to mistakes and confusion since nobody will be
able to remember
>>> whether E represents # or * (or that they are
at all connected).
>>>
>>> My suggestion: Briefly describe the issues
surrounding # and say
>>> that it needs to be %-encoded. Done. (There
doesn't seem to be a
>>> need to encode *.)
>>>
>>> Henning
>>>
>>>
>> I agree with Henning.
>> DaveO.
>>
>>>
_______________________________________________
>>> 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

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )