RFC Errata System
2011-04-16 14:35:40 UTC
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 <***@aliax.net>
Section: 5.5.2
Original Text
-------------
Message sequence for INVITE using Path:
F1 Invite UA2 -> REGISTRAR
INVITE ***@EXAMPLEHOME.COM SIP/2.0
Via: SIP/2.0/UDP 71.91.180.10:5060;branch=z9hG4bKe2i95c5st3R
To: UA1 <sip:***@EXAMPLEHOME.COM>
From: UA2 <sip:***@FOREIGN.ELSEWHERE.ORG>;tag=224497
Call-ID: ***@71.91.180.10
CSeq: 29 INVITE
Contact: <sip:***@71.91.180.10>
. . .
Corrected Text
--------------
Message sequence for INVITE using Path:
F1 Invite UA2 -> REGISTRAR
INVITE sip:***@EXAMPLEHOME.COM SIP/2.0
Via: SIP/2.0/UDP 71.91.180.10:5060;branch=z9hG4bKe2i95c5st3R
To: UA1 <sip:***@EXAMPLEHOME.COM>
From: UA2 <sip:***@FOREIGN.ELSEWHERE.ORG>;tag=224497
Call-ID: ***@71.91.180.10
CSeq: 29 INVITE
Contact: <sip:***@71.91.180.10>
. . .
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
"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 <***@aliax.net>
Section: 5.5.2
Original Text
-------------
Message sequence for INVITE using Path:
F1 Invite UA2 -> REGISTRAR
INVITE ***@EXAMPLEHOME.COM SIP/2.0
Via: SIP/2.0/UDP 71.91.180.10:5060;branch=z9hG4bKe2i95c5st3R
To: UA1 <sip:***@EXAMPLEHOME.COM>
From: UA2 <sip:***@FOREIGN.ELSEWHERE.ORG>;tag=224497
Call-ID: ***@71.91.180.10
CSeq: 29 INVITE
Contact: <sip:***@71.91.180.10>
. . .
Corrected Text
--------------
Message sequence for INVITE using Path:
F1 Invite UA2 -> REGISTRAR
INVITE sip:***@EXAMPLEHOME.COM SIP/2.0
Via: SIP/2.0/UDP 71.91.180.10:5060;branch=z9hG4bKe2i95c5st3R
To: UA1 <sip:***@EXAMPLEHOME.COM>
From: UA2 <sip:***@FOREIGN.ELSEWHERE.ORG>;tag=224497
Call-ID: ***@71.91.180.10
CSeq: 29 INVITE
Contact: <sip:***@71.91.180.10>
. . .
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