Can I make a suggestion to you, the chairs and the rest of the group? That
nothing be advanced in this area to PS until you have shown real and
interoperable
versions that are deployed in real life situations? Not in the DS kind
of rigor,
but at least _something_ that demonstrates that that this is a) not
academic and
b) there's real community interest in deploying.
For DKIM, a small group of us (me, Murray from sendmail, Arvel from
Alt-n and others) kept on top of the spec and pushed out deployed code
sooner rather than later. This was a huge help for both interoperability,
but much more importantly to test out to see where the real-life corner
cases are.
Mike, who generally thinks that IETF needs more running code
Eric Burger wrote:
[SIP Forum Chair Hat On]
This is a sad state of affairs, if we have to break SIP to make it
work for broken implementations.
I can see this kind of work going on outside the IETF, but it seems
out of place to hack Internet protocols willy-nilly to make them work
for either non-Internet deployments or to interoperate with obsolete
or broken implementations.
On Jul 14, 2008, at 8:02 AM, Dan York wrote:
On Jul 13, 2008, at 12:49 PM, Hadriel Kaplan wrote:
But for a lot of cases they're not modifying To/From for that reason
- they're modifying it to either "fix" them for specific interop
reasons, or to hide topology (ie, when it contains IP Addresses or
hostnames). Those are the cases I'm trying to get the information
through.
DY> Just to add to what Hadriel said, one of the additional arguments
*for* an SBC that I've had given to me by different vendors at
various shows is that they can "normalize" SIP and make SIP
interoperability actually work between different vendors. The SBC
understands how exactly Vendor X speaks SIP and how exactly Vendor Y
speaks SIP and can then enable the interconnection/interoperability.
So the reality is that there are SBCs out there that view as part of
their function to "fix" SIP so that it can be interoperable. In
doing this "fixing", one can expect that the SBCs would be changing
headers.
Regards,
Dan
--
Dan York, CISSP, Director of Emerging Communication Technology
Office of the CTO Voxeo Corporation [EMAIL PROTECTED]
Phone: +1-407-455-5859 Skype: danyork http://www.voxeo.com
Blogs: http://blogs.voxeo.com http://www.disruptivetelephony.com
Build voice applications based on open standards.
Find out how at http://www.voxeo.com/free
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
