Re: draft-york-sipping-p-charge-info-12: ABNF
Dan York <[email protected]> Thu, 1 Dec 2011 11:00:44 -0500
| Newsgroups | gmane.ietf.sipping |
|---|---|
| Message-ID | <[email protected]> |
--===============7221278626441226227== Content-Type: multipart/alternative; boundary="Apple-Mail=_0707FB52-E4DD-4004-8353-9E4DD8F6AA92" --Apple-Mail=_0707FB52-E4DD-4004-8353-9E4DD8F6AA92 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Brett, On Nov 30, 2011, at 3:41 PM, Brett Tate wrote: > If charge-param remains within userinfo, generic-param should likely = be changed to a more limited extention parameter since UTF8-NONASCII is = not allowed within SIP-URI and tel URI because of escaping limitations. = RFC 3986 provides a mechanism for escaping UTF8-NONASCII within newer = URI schemes. DY> Do you have a suggestion for how I would change this to a more = limited parameter within the ABNF? =20 DY> Alternatively, what if the ABNF remained as is but the formal syntax = included a statement below the ABNF that UTF8-NONASCII is not allowed in = the "generic-param" due to limitations in the SIP and tel URIs? Would = that not be sufficient enough for implementors to understand? Thanks, Dan >=20 > RFC 3261: >=20 > generic-param =3D token [ EQUAL gen-value ] >=20 > gen-value =3D token / host / quoted-string >=20 > quoted-string =3D SWS DQUOTE *(qdtext / quoted-pair ) DQUOTE >=20 > qdtext =3D LWS / %x21 / %x23-5B / %x5D-7E / UTF8-NONASCII >=20 > _______________________________________________ > Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping > This list is for NEW development of the application of SIP > Use [email protected] for questions on current sip > Use [email protected] for new developments of core SIP --=20 Dan York [email protected] http://www.danyork.com/ skype:danyork Phone: +1-802-735-1624 Twitter - http://twitter.com/danyork -------------------------------------------------------- All comments and opinions are entirely my own and have no connection = whatsoever to any employer, past or present. Indeed, by tomorrow even I = might be disavowing these comments. -------------------------------------------------------- --Apple-Mail=_0707FB52-E4DD-4004-8353-9E4DD8F6AA92 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; = ">Brett,<div><br><div><div>On Nov 30, 2011, at 3:41 PM, Brett Tate = wrote:</div><br><blockquote type=3D"cite"><div>If charge-param remains = within userinfo, generic-param should likely be changed to a more = limited extention parameter since UTF8-NONASCII is not allowed within = SIP-URI and tel URI because of escaping limitations. RFC 3986 = provides a mechanism for escaping UTF8-NONASCII within newer URI = schemes.<br></div></blockquote><div><br></div><div>DY> Do you have a = suggestion for how I would change this to a more limited parameter = within the ABNF? </div><div><br></div><div>DY> Alternatively, = what if the ABNF remained as is but the formal syntax included a = statement below the ABNF that UTF8-NONASCII is not allowed in the = "generic-param" due to limitations in the SIP and tel URIs? = Would that not be sufficient enough for implementors to = understand?</div><div><br></div><div>Thanks,</div><div>Dan</div><br><block= quote type=3D"cite"><div><br>RFC 3261:<br><br>generic-param =3D = token [ EQUAL gen-value ]<br><br>gen-value = =3D token / host / = quoted-string<br><br>quoted-string =3D SWS DQUOTE *(qdtext / = quoted-pair ) DQUOTE<br><br>qdtext =3D LWS = / %x21 / %x23-5B / %x5D-7E / = UTF8-NONASCII<br><br>_______________________________________________<br>Si= pping mailing list <a = href=3D"https://www.ietf.org/mailman/listinfo/sipping">https://www.ietf.or= g/mailman/listinfo/sipping</a><br>This list is for NEW development of = the application of SIP<br>Use <a = href=3D"mailto:[email protected]">[email protected]= bia.edu</a> for questions on current sip<br>Use <a = href=3D"mailto:[email protected]">[email protected]</a> for new developments of = core SIP<br></div></blockquote></div><br><div> <span class=3D"Apple-style-span" style=3D"border-collapse: separate; = color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; = font-variant: normal; font-weight: normal; letter-spacing: normal; = line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: = 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: = 0px; -webkit-border-horizontal-spacing: 0px; = -webkit-border-vertical-spacing: 0px; = -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: = auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span = class=3D"Apple-style-span" style=3D"border-collapse: separate; color: = rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: = normal; font-weight: normal; letter-spacing: normal; line-height: = normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; = text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; = -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: = 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: = auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div = style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; "><div><div style=3D"word-wrap: = break-word; -webkit-nbsp-mode: space; -webkit-line-break: = after-white-space; ">-- <br>Dan York <a = href=3D"mailto:[email protected]">[email protected]</a><br><a = href=3D"http://www.danyork.com/">http://www.danyork.com/</a> &n= bsp;<a href=3D"skype:danyork">skype:danyork</a><br>Phone: = +1-802-735-1624<br>Twitter - <a = href=3D"http://twitter.com/danyork">http://twitter.com/danyork</a></div><d= iv style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; = ">--------------------------------------------------------</div></div><div= style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; ">All comments and opinions are = entirely my own and have no connection whatsoever to any employer, past = or present. Indeed, by tomorrow even I might be disavowing these = comments.</div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: = space; -webkit-line-break: after-white-space; = ">--------------------------------------------------------</div></div></sp= an></span> </div> <br></div></body></html>= --Apple-Mail=_0707FB52-E4DD-4004-8353-9E4DD8F6AA92-- --===============7221278626441226227== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use [email protected] for questions on current sip Use [email protected] for new developments of core SIP --===============7221278626441226227==--