True. Thanks for pointing that out, I'll correct this in RFC 2806bis I-D.

--
Antti V�h�-Sipil� / Nokia Mobile Phones
My views and opinions are not necessarily those of my employer.
Send personal email to [EMAIL PROTECTED] only. http://www.iki.fi/avs/


> -----Original Message-----
> From: EXT Jonathan Rosenberg [mailto:[EMAIL PROTECTED]]
> Sent: 01. November 2000 06:54
> To: 'Alexandre Charest'; '[EMAIL PROTECTED]'
> Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> Subject: RE: '#' in tel url
> 
> 
> Good catch. I presume they should, although the BNF as 
> defined does allow
> it. I suspect this is a mistake in the BNF.
> 
> I've cc'ed Antti for comments.
> 
> -Jonathan R.
> 
> ---
> Jonathan D. Rosenberg                       72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> [EMAIL PROTECTED]                     FAX:   (973) 952-5050
> http://www.cs.columbia.edu/~jdrosen         PHONE: (973) 952-5000
> http://www.dynamicsoft.com
>  
> 
> > -----Original Message-----
> > From: Alexandre Charest [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, October 30, 2000 3:11 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: '#' in tel url
> > 
> > 
> > According to RFC2806 local phone number and other parts of 
> the url can
> > contain the dtmf-digit '#'. But this character is disallowed in URI
> > according to RFC2396 as it is used to delimit a URI from a fragment
> > identifier in URI references. Must it be escaped?
> > 
> > Alexandre Charest
> > Software Designer
> > Mediatrix Telecom Inc. (www.mediatrix.com)
> > t�l:(819) 829-8749 #275
> > fax: (819) 829-5100
> > 
> 

Reply via email to