The following are few comments and questions concerning draft-sparks-sip-invfix-01.
Section 8.2: The "MUST NOT" is rather strict. Depending upon interpretation, it can interfere with a stateful proxy choosing to temporarily act like a stateless proxy for a short interval after a restart. Section 8.4: Concerning timer D and "zero seconds for reliable transports", is "reliable" obtained from INVITE or ACK. Concerning timer D being zero, at first glance it looks like the state machine text no longer ensures ACK will be sent for extra 2xx or 300-699. The same applies, to ensuring ACK resent in situations where transport not reliable end-to-end. Per 7.2 paragraph 2, this might be intentional; if so, the motivation and flexibility in handling from section 7.2 should potentially also be included within 8.4. If I'm misinterpreting the fix, where does it say the ACK MUST, SHOULD, or MAY still be (re-)sent for the extra responses when timer D is 0? Thanks, Brett _______________________________________________ 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
