The following errata report has been submitted 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=3295 -------------------------------------- Type: Technical Reported by: David Waiting <dwaiting@xxxxxxxxx> Section: 3.8. Original Text ------------- F18 ACK Proxy 1 -> Proxy 2 ACK sip:bob@xxxxxxxxxxxxxxxxxx SIP/2.0 Via: SIP/2.0/UDP ss2.biloxi.example.com:5060;branch=z9hG4bK721e4.1 Max-Forwards: 70 From: Alice <sip:alice@xxxxxxxxxxxxxxxxxxx>;tag=9fxced76sl To: Bob <sip:bob@xxxxxxxxxxxxxxxxxx>;tag=314159 Call-ID: 2xTb9vxSit55XU7p8@xxxxxxxxxxxxxxxxxxx CSeq: 1 ACK Content-Length: 0 Corrected Text -------------- F18 ACK Proxy 1 -> Proxy 2 ACK sip:bob@xxxxxxxxxxxxxxxxxx SIP/2.0 Via: SIP/2.0/UDP ss1.atlanta.example.com:5060;branch=z9hG4bK2d4790.1 Max-Forwards: 70 From: Alice <sip:alice@xxxxxxxxxxxxxxxxxxx>;tag=9fxced76sl To: Bob <sip:bob@xxxxxxxxxxxxxxxxxx>;tag=314159 Call-ID: 2xTb9vxSit55XU7p8@xxxxxxxxxxxxxxxxxxx CSeq: 1 ACK Content-Length: 0 Notes ----- Proxy 1 includes an incorrect Via header in the ACK. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- 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
