Elwell, John wrote:
Yes, I know we are talking SDP, but the SDP ABNF was so imprecise
that I looked elsewhere. I am not sure where the definitive source
is, but I just took SIP as an example, which seemed to suggest that
the people who wrote RFC 3261 thought that a single element (without
any dot) was wrong.
John: I would believe the authors of rfc3261 focused on
the signaling itself and relegated the nuances of body handling
to appropriate mechanisms and documents. We should probably
seek their opinion.
That said, I am not refuting your or Kevin's stance. Clearly,
implementers opt for the path of least resistance, and this
dictates that they parse the token from SDP "c=" line and feed
it directly into the DNS routines (which will certainly hiccup
when given ".invalid"). However, pedantically speaking, the SDP
ABNF seems to indicate that ".invalid" is legal (at least to my
reading.)
Thus, when a developer armed with the pedantic interpretation
squares off against a developer armed with an implementation
that took the path of least resistance, who is right? I am
sure you have been part of countless arguments where standards
say one thing and what is implemented is a bit ... well ...
different ;-)
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web: http://ect.bell-labs.com/who/vkg/
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
