[Sip-implementors] BNF for Route does not allow addr-spec?

[David Larson]

"addr-spec" is the form of specifying the SIP URI without angle brackets around the <URI>.  We have encountered the addr-spec form of the SIP URI used on Route headers that are a part of a REFER sequence ... which might be part of the reason why this form is used.   Is there a reason why the BNF does not allow using the addr-spec form for Route (and Record-Route)?  Being that we are encouraged to be loose on what we accept and be strict on what we generate, it seems we should accept a SIP URI without angle brackets in a Route header.  Is this safe, or should it cause an error for some reason?   Thanks in advance for your response!   The following was taken from the bis-09 draft for reference.   Line 5722 of BIS-09 has the BNF for Contact:     Contact = ("Contact" / "m") HCOLON           ( STAR / (contact-param           *(COMMA contact-param)))     contact-param = (name-addr / addr-spec)           *(SEMI contact-params) Line 5746 has the BNF for Route:     Route = "Route" HCOLON         route-param *(COMMA route-param)     route-param = name-addr *(SEMI rr-param)