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: https://www.rfc-editor.org/errata/eid6984 -------------------------------------- Type: Technical Reported by: Xiaoxi Li <xiaoxi.li@xxxxxxxxxxxxxxx> Section: 3.2 Original Text ------------- F5 INVITE Proxy 1 -> Proxy 2 INVITE sip:bob@xxxxxxxxxxxxxxxxxx SIP/2.0 Via: SIP/2.0/TCP ss1.atlanta.example.com:5060;branch=z9hG4bK2d4790.1 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74bf9 ;received=192.0.2.101 Max-Forwards: 69 F7 INVITE Proxy 2 -> Bob INVITE sip:bob@xxxxxxxxxxxxxxxxxxxxxxxxx SIP/2.0 Via: SIP/2.0/TCP ss2.biloxi.example.com:5060;branch=z9hG4bK721e4.1 Via: SIP/2.0/TCP ss1.atlanta.example.com:5060;branch=z9hG4bK2d4790.1 ;received=192.0.2.111 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74bf9 ;received=192.0.2.101 Max-Forwards: 68 F16 ACK Proxy 1 -> Proxy 2 ACK sip:bob@xxxxxxxxxxxxxxxxxxxxxxxxx SIP/2.0 Via: SIP/2.0/TCP ss1.atlanta.example.com:5060;branch=z9hG4bK2d4790.1 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74b76 ;received=192.0.2.101 Max-Forwards: 69 F17 ACK Proxy 2 -> Bob ACK sip:bob@xxxxxxxxxxxxxxxxxxxxxxxxx SIP/2.0 Via: SIP/2.0/TCP ss2.biloxi.example.com:5060;branch=z9hG4bK721e4.1 Via: SIP/2.0/TCP ss1.atlanta.example.com:5060;branch=z9hG4bK2d4790.1 ;received=192.0.2.111 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74b76 ;received=192.0.2.101 Max-Forwards: 68 From: Alice <sip:alice@xxxxxxxxxxxxxxxxxxx>;tag=9fxced76sl Corrected Text -------------- the branch id in the topmost Via header(s) in the F16 F17 messages shouldn't be the same as the via headers added in F5 F7 messages. the ACK message shall only copy the same branch id in Via if it's for non-200 ok responses. this example deviates from the description in RFC 3261 chapter 16.6 Notes ----- the branch id in the topmost Via header(s) in the F16 F17 messages shouldn't be the same as the via headers added in F5 F7 messages. the ACK message shall only copy the same branch id in Via if it's for non-200 ok responses. this example deviates from the description in RFC 3261 chapter 16.6 Instructions: ------------- This erratum 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 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
