The following errata report has been rejected for RFC3665, "Session Initiation Protocol (SIP) Basic Call Flow Examples". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=3665&eid=4516 -------------------------------------- Status: Rejected Type: Technical Reported by: Fritz <a@xxxxx> Date Reported: 2015-10-30 Rejected by: Ben Campbell (IESG) Section: 3.2 Original Text ------------- F3 ACK Alice -> Proxy 1 ACK sip:bob@xxxxxxxxxxxxxxxxxx SIP/2.0 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74b43 Max-Forwards: 70 From: Alice <sip:alice@xxxxxxxxxxxxxxxxxxx>;tag=9fxced76sl To: Bob <sip:bob@xxxxxxxxxxxxxxxxxx>;tag=3flal12sf Call-ID: 3848276298220188511@xxxxxxxxxxxxxxxxxxx CSeq: 1 ACK Content-Length: 0 Corrected Text -------------- F3 ACK Alice -> Proxy 1 ACK sip:bob@xxxxxxxxxxxxxxxxxx SIP/2.0 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK12345 Max-Forwards: 70 From: Alice <sip:alice@xxxxxxxxxxxxxxxxxxx>;tag=9fxced76sl To: Bob <sip:bob@xxxxxxxxxxxxxxxxxx>;tag=3flal12sf Call-ID: 3848276298220188511@xxxxxxxxxxxxxxxxxxx CSeq: 1 ACK Content-Length: 0 Notes ----- ACK is a new transaction and need a new value for via-branch --VERIFIER NOTES-- The flow in the RFC is correct. ACK is only a new transaction if the final response to the INVITE was in the 2xx class. In this case, the final response was a 407 - this ACK is hop-by-hop, and is part of the INVITE transaction. -------------------------------------- RFC3665 (draft-ietf-sipping-basic-call-flows-02) -------------------------------------- Title : Session Initiation Protocol (SIP) Basic Call Flow Examples Publication Date : December 2003 Author(s) : A. Johnston, S. Donovan, R. Sparks, C. Cunningham, K. Summers Category : BEST CURRENT PRACTICE Source : Session Initiation Proposal Investigation Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG _______________________________________________ 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