On 7/19/07 10:19 AM, Frank W. Miller wrote:
FM: While I applaud the time and effort that the large vendors have
obviously invested in this, this is a qualitative statement.  Perhaps Cisco
and/or Microsoft have empirical data they would be willing to share about
robustness and performance?

That's the kind of data you get between "proposed standard" and "draft standard" -- not *prior* to publication. I'm not sure why there's so much noise about setting the bar much, much higher for ICE than we do for other IETF proposals.

To be clear: to get this kind of experience (especially as it pertains to interoperability), you need to have a stable (i.e., frozen) specification. Internet Drafts simply don't provide an appropriate basis for the kinds of proof that you and others are demanding.

I think we would all benefit from a quick review of RFC 2026:

   A Proposed Standard specification is generally stable, has resolved
   known design choices, is believed to be well-understood, has received
   significant community review, and appears to enjoy enough community
   interest to be considered valuable.  However, further experience
   might result in a change or even retraction of the specification
   before it advances.

   Usually, neither implementation nor operational experience is
   required for the designation of a specification as a Proposed
   Standard.
...
   Implementors should treat Proposed Standards as immature
   specifications.  It is desirable to implement them in order to gain
   experience and to validate, test, and clarify the specification.
   However, since the content of Proposed Standards may be changed if
   problems are found or better solutions are identified, deploying
   implementations of such standards into a disruption-sensitive
   environment is not recommended.


/a


_______________________________________________
Sip mailing list  https://www1.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

Reply via email to