The following errata report has been submitted for RFC3327, "Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts".
-------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=3327&eid=2778 -------------------------------------- Type: Technical Reported by: Iñaki Baz Castillo <[email protected]> Section: 5.5.2 Original Text ------------- Message sequence for INVITE using Path: F1 Invite UA2 -> REGISTRAR INVITE [email protected] SIP/2.0 Via: SIP/2.0/UDP 71.91.180.10:5060;branch=z9hG4bKe2i95c5st3R To: UA1 <sip:[email protected]> From: UA2 <sip:[email protected]>;tag=224497 Call-ID: [email protected] CSeq: 29 INVITE Contact: <sip:[email protected]> . . . Corrected Text -------------- Message sequence for INVITE using Path: F1 Invite UA2 -> REGISTRAR INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 71.91.180.10:5060;branch=z9hG4bKe2i95c5st3R To: UA1 <sip:[email protected]> From: UA2 <sip:[email protected]>;tag=224497 Call-ID: [email protected] CSeq: 29 INVITE Contact: <sip:[email protected]> . . . Notes ----- In all the example flow the Request URI is wrong as doesn't contain the URI scheme ("sip" / "sips"). 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. -------------------------------------- RFC3327 (draft-willis-sip-path-08) -------------------------------------- Title : Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts Publication Date : December 2002 Author(s) : D. Willis, B. Hoeneisen Category : PROPOSED STANDARD Source : Session Initiation Protocol Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG
_______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is essentially closed and only used for finishing old business. Use [email protected] for questions on how to develop a SIP implementation. Use [email protected] for new developments on the application of sip. Use [email protected] for issues related to maintenance of the core SIP specifications.
