Re: [sipcore] [Technical Errata Reported] RFC7118 (5937)

Roman Shpount <roman@telurix.com> Sat, 14 December 2019 20:42 UTC

MIME-Version: 1.0
References: <20191214200623.98A51F406CB@rfc-editor.org> <CALiegfk0DmcB0Kak+1Y6jDLqzY_0zVo0qweY1+0CCo-E3C-c6w@mail.gmail.com> <CAD5OKxsK+2VH-3a=RbSkOhHB=HPbVOs-CEHbho-CX0PWXuyqZA@mail.gmail.com>
In-Reply-To: <CAD5OKxsK+2VH-3a=RbSkOhHB=HPbVOs-CEHbho-CX0PWXuyqZA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Sat, 14 Dec 2019 15:42:33 -0500
Message-ID: <CAD5OKxtZK+irOGk5r6Gj1QKSnEqw5bc7_sxN+VBZxoyURk=DOA@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, José Luis Millán <jmillan@aliax.net>, Ben Campbell <ben@nostrum.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, Adam Roach - SIPCORE Chair <adam@nostrum.com>, Brian Rosen <br@brianrosen.net>, "A. Jean Mahoney" <mahoney@nostrum.com>, SIPCORE <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fa63490599b00486"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/6YU8Ax-Yaz6YtnALBTSj_Rkv_Ks>
Subject: Re: [sipcore] [Technical Errata Reported] RFC7118 (5937)
Precedence: list

It looks like RFC 5630 allows this and there is a description of such flow
in  https://tools.ietf.org/html/rfc5630#section-6.4.

Please disregard this errata.
_____________
Roman Shpount


On Sat, Dec 14, 2019 at 3:18 PM Roman Shpount <roman@telurix.com> wrote:

> If you look at this message:
>
> INVITE sip:bob@example.com SIP/2.0
> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
> From: sip:alice@example.com;tag=asdyka899
> To: sip:bob@example.com
> Call-ID: asidkj3ss
> CSeq: 1 INVITE
> Max-Forwards: 70
> Supported: path, outbound, gruu
> Route: <sip:proxy.example.com:443;transport=ws;lr>
> Contact: <sip:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob>
> Content-Type: application/sdp
>
> Then WS, not WSS should be used to send it. In order for WSS to be used,
> Route header should be "Route: <sip*s*:proxy.example.com:443;tra
> nsport=ws;lr>" .
>
> There is currently no standard compliant way to send a SIP message over
> WSS (or any other secure protocol) and then have it forwarded over an
> insecure protocol (UDP). Current example implies this is possible.
> _____________
> Roman Shpount
>
>
> On Sat, Dec 14, 2019 at 3:08 PM Iñaki Baz Castillo <ibc@aliax.net> wrote:
>
>> As replied in JsSIP mailing list, this is not a bug in 7118 but a general
>> design issue in RFC 3261.
>>
>> El sáb., 14 dic. 2019 21:06, RFC Errata System <rfc-editor@rfc-editor.org>
>> escribió:
>>
>>> The following errata report has been submitted for RFC7118,
>>> "The WebSocket Protocol as a Transport for the Session Initiation
>>> Protocol (SIP)".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> https://www.rfc-editor.org/errata/eid5937
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Roman Shpount <roman@telurix.com>
>>>
>>> Section: 8.2
>>>
>>> Original Text
>>> -------------
>>> INVITE sip:bob@example.com SIP/2.0
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> From: sip:alice@example.com;tag=asdyka899
>>> To: sip:bob@example.com
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>> Max-Forwards: 70
>>> Supported: path, outbound, gruu
>>> Route: <sip:proxy.example.com:443;transport=ws;lr>
>>> Contact: <sip:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob>
>>> Content-Type: application/sdp
>>>
>>>
>>> F2 100 Trying  proxy.example.com -> Alice (transport WSS)
>>>
>>> SIP/2.0 100 Trying
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> From: sip:alice@example.com;tag=asdyka899
>>> To: sip:bob@example.com
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>>
>>>
>>> F3 INVITE  proxy.example.com -> Bob (transport UDP)
>>>
>>> INVITE sip:bob@203.0.113.22:5060 SIP/2.0
>>> Via: SIP/2.0/UDP proxy.example.com;branch=z9hG4bKhjhjqw32c
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> Record-Route: <sip:proxy.example.com;transport=udp;lr>,
>>>  <sip:h7kjh12s@proxy.example.com:443;transport=wss;lr>
>>> From: sip:alice@example.com;tag=asdyka899
>>> To: sip:bob@example.com
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>> Max-Forwards: 69
>>> Supported: path, outbound, gruu
>>> Contact: <sip:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob>
>>> Content-Type: application/sdp
>>>
>>> F4 200 OK  Bob -> proxy.example.com (transport UDP)
>>>
>>> SIP/2.0 200 OK
>>> Via: SIP/2.0/UDP proxy.example.com;branch=z9hG4bKhjhjqw32c
>>>  ;received=192.0.2.10
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> Record-Route: <sip:proxy.example.com;transport=udp;lr>,
>>>  <sip:h7kjh12s@proxy.example.com:443;transport=ws;lr>
>>> From: sip:alice@example.com;tag=asdyka899
>>> To: sip:bob@example.com;tag=bmqkjhsd
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>> Contact: <sip:bob@203.0.113.22:5060;transport=udp>
>>> Content-Type: application/sdp
>>>
>>>
>>> F5 200 OK  proxy.example.com -> Alice (transport WSS)
>>>
>>> SIP/2.0 200 OK
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> Record-Route: <sip:proxy.example.com;transport=udp;lr>,
>>>  <sip:h7kjh12s@proxy.example.com:443;transport=ws;lr>
>>> From: sip:alice@example.com;tag=asdyka899
>>> To: sip:bob@example.com;tag=bmqkjhsd
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>> Contact: <sip:bob@203.0.113.22:5060;transport=udp>
>>> Content-Type: application/sdp
>>>
>>>
>>> F6 ACK  Alice -> proxy.example.com (transport WSS)
>>>
>>> ACK sip:bob@203.0.113.22:5060;transport=udp SIP/2.0
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bKhgqqp090
>>> Route: <sip:h7kjh12s@proxy.example.com:443;transport=ws;lr>,
>>>  <sip:proxy.example.com;transport=udp;lr>,
>>> From: sip:alice@example.com;tag=asdyka899
>>> To: sip:bob@example.com;tag=bmqkjhsd
>>> Call-ID: asidkj3ss
>>> CSeq: 1 ACK
>>> Max-Forwards: 70
>>>
>>> F7 ACK  proxy.example.com -> Bob (transport UDP)
>>>
>>> ACK sip:bob@203.0.113.22:5060;transport=udp SIP/2.0
>>> Via: SIP/2.0/UDP proxy.example.com;branch=z9hG4bKhwpoc80zzx
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bKhgqqp090
>>> From: sip:alice@example.com;tag=asdyka899
>>> To: sip:bob@example.com;tag=bmqkjhsd
>>> Call-ID: asidkj3ss
>>> CSeq: 1 ACK
>>> Max-Forwards: 69
>>>
>>>
>>> F8 BYE  Bob -> proxy.example.com (transport UDP)
>>>
>>> BYE sip:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob SIP/2.0
>>> Via: SIP/2.0/UDP 203.0.113.22;branch=z9hG4bKbiuiansd001
>>> Route: <sip:proxy.example.com;transport=udp;lr>,
>>>  <sip:h7kjh12s@proxy.example.com:443;transport=ws;lr>
>>> From: sip:bob@example.com;tag=bmqkjhsd
>>> To: sip:alice@example.com;tag=asdyka899
>>> Call-ID: asidkj3ss
>>> CSeq: 1201 BYE
>>> Max-Forwards: 70
>>>
>>>
>>> F9 BYE  proxy.example.com -> Alice (transport WSS)
>>>
>>> BYE sip:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob SIP/2.0
>>> Via: SIP/2.0/WSS proxy.example.com:443;branch=z9hG4bKmma01m3r5
>>> Via: SIP/2.0/UDP 203.0.113.22;branch=z9hG4bKbiuiansd001
>>> From: sip:bob@example.com;tag=bmqkjhsd
>>> To: sip:alice@example.com;tag=asdyka899
>>> Call-ID: asidkj3ss
>>> CSeq: 1201 BYE
>>> Max-Forwards: 69
>>>
>>>
>>> F10 200 OK  Alice -> proxy.example.com (transport WSS)
>>>
>>> SIP/2.0 200 OK
>>> Via: SIP/2.0/WSS proxy.example.com:443;branch=z9hG4bKmma01m3r5
>>> Via: SIP/2.0/UDP 203.0.113.22;branch=z9hG4bKbiuiansd001
>>> From: sip:bob@example.com;tag=bmqkjhsd
>>> To: sip:alice@example.com;tag=asdyka899
>>> Call-ID: asidkj3ss
>>> CSeq: 1201 BYE
>>>
>>>
>>> F11 200 OK  proxy.example.com -> Bob (transport UDP)
>>>
>>> SIP/2.0 200 OK
>>> Via: SIP/2.0/UDP 203.0.113.22;branch=z9hG4bKbiuiansd001
>>> From: sip:bob@example.com;tag=bmqkjhsd
>>> To: sip:alice@example.com;tag=asdyka899
>>> Call-ID: asidkj3ss
>>> CSeq: 1201 BYE
>>>
>>> Corrected Text
>>> --------------
>>> F1 INVITE  Alice -> proxy.example.com (transport WSS)
>>>
>>> INVITE sips:bob@example.com SIP/2.0
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> From: sips:alice@example.com;tag=asdyka899
>>> To: sips:bob@example.com
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>> Max-Forwards: 70
>>> Supported: path, outbound, gruu
>>> Route: <sips:proxy.example.com:443;transport=wss;lr>
>>> Contact: <sips:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob>
>>> Content-Type: application/sdp
>>>
>>>
>>> F2 100 Trying  proxy.example.com -> Alice (transport WSS)
>>>
>>> SIP/2.0 100 Trying
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> From: sips:alice@example.com;tag=asdyka899
>>> To: sips:bob@example.com
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>>
>>>
>>> F3 INVITE  proxy.example.com -> Bob (transport TLS)
>>>
>>> INVITE sips:bob@203.0.113.22 SIP/2.0
>>> Via: SIP/2.0/TLS proxy.example.com;branch=z9hG4bKhjhjqw32c
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> Record-Route: <sips:proxy.example.com;lr>,
>>>  <sips:h7kjh12s@proxy.example.com:443;transport=ws;lr>
>>> From: sip:alice@example.com;tag=asdyka899
>>> To: sips:bob@example.com
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>> Max-Forwards: 69
>>> Supported: path, outbound, gruu
>>> Contact: <sips:alice@example.com
>>>  ;gr=urn:uuid:f81-7dec-14a06cf1;ob>
>>> Content-Type: application/sdp
>>>
>>> F4 200 OK  Bob -> proxy.example.com (transport TLS)
>>>
>>> SIP/2.0 200 OK
>>> Via: SIP/2.0/TLS proxy.example.com;branch=z9hG4bKhjhjqw32c
>>>  ;received=192.0.2.10
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> Record-Route: <sips:proxy.example.com;lr>,
>>>  <sips:h7kjh12s@proxy.example.com:443;transport=ws;lr>
>>> From: sips:alice@example.com;tag=asdyka899
>>> To: sips:bob@example.com;tag=bmqkjhsd
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>> Contact: <sips:bob@203.0.113.22>
>>> Content-Type: application/sdp
>>>
>>>
>>> F5 200 OK  proxy.example.com -> Alice (transport WSS)
>>>
>>> SIP/2.0 200 OK
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bK56sdasks
>>> Record-Route: <sips:proxy.example.com;lr>,
>>>  <sips:h7kjh12s@proxy.example.com:443;transport=ws;lr>
>>> From: sips:alice@example.com;tag=asdyka899
>>> To: sips:bob@example.com;tag=bmqkjhsd
>>> Call-ID: asidkj3ss
>>> CSeq: 1 INVITE
>>> Contact: <sips:bob@203.0.113.22>
>>> Content-Type: application/sdp
>>>
>>>
>>> F6 ACK  Alice -> proxy.example.com (transport WSS)
>>>
>>> ACK sips:bob@203.0.113.22 SIP/2.0
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bKhgqqp090
>>> Route: <sips:h7kjh12s@proxy.example.com:443;transport=ws;lr>,
>>>  <sips:proxy.example.com;lr>,
>>> From: sips:alice@example.com;tag=asdyka899
>>> To: sips:bob@example.com;tag=bmqkjhsd
>>> Call-ID: asidkj3ss
>>> CSeq: 1 ACK
>>> Max-Forwards: 70
>>>
>>> F7 ACK  proxy.example.com -> Bob (transport TLS)
>>>
>>> ACK sips:bob@203.0.113.22 SIP/2.0
>>> Via: SIP/2.0/TLS proxy.example.com;branch=z9hG4bKhwpoc80zzx
>>> Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bKhgqqp090
>>> From: sips:alice@example.com;tag=asdyka899
>>> To: sips:bob@example.com;tag=bmqkjhsd
>>> Call-ID: asidkj3ss
>>> CSeq: 1 ACK
>>> Max-Forwards: 69
>>>
>>>
>>> F8 BYE  Bob -> proxy.example.com (transport TLS)
>>>
>>> BYE sips:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob SIP/2.0
>>> Via: SIP/2.0/TLS 203.0.113.22;branch=z9hG4bKbiuiansd001
>>> Route: <sips:proxy.example.com;lr>,
>>>  <sips:h7kjh12s@proxy.example.com:443;transport=ws;lr>
>>> From: sips:bob@example.com;tag=bmqkjhsd
>>> To: sips:alice@example.com;tag=asdyka899
>>> Call-ID: asidkj3ss
>>> CSeq: 1201 BYE
>>> Max-Forwards: 70
>>>
>>>
>>> F9 BYE  proxy.example.com -> Alice (transport WSS)
>>>
>>> BYE sips:alice@example.com;gr=urn:uuid:f81-7dec-14a06cf1;ob SIP/2.0
>>> Via: SIP/2.0/WSS proxy.example.com:443;branch=z9hG4bKmma01m3r5
>>> Via: SIP/2.0/TLS 203.0.113.22;branch=z9hG4bKbiuiansd001
>>> From: sips:bob@example.com;tag=bmqkjhsd
>>> To: sips:alice@example.com;tag=asdyka899
>>> Call-ID: asidkj3ss
>>> CSeq: 1201 BYE
>>> Max-Forwards: 69
>>>
>>>
>>> F10 200 OK  Alice -> proxy.example.com (transport WSS)
>>>
>>> SIP/2.0 200 OK
>>> Via: SIP/2.0/WSS proxy.example.com:443;branch=z9hG4bKmma01m3r5
>>> Via: SIP/2.0/TLS 203.0.113.22;branch=z9hG4bKbiuiansd001
>>> From: sips:bob@example.com;tag=bmqkjhsd
>>> To: sips:alice@example.com;tag=asdyka899
>>> Call-ID: asidkj3ss
>>> CSeq: 1201 BYE
>>>
>>>
>>> F11 200 OK  proxy.example.com -> Bob (transport TLS)
>>>
>>> SIP/2.0 200 OK
>>> Via: SIP/2.0/TLS 203.0.113.22;branch=z9hG4bKbiuiansd001
>>> From: sips:bob@example.com;tag=bmqkjhsd
>>> To: sips:alice@example.com;tag=asdyka899
>>> Call-ID: asidkj3ss
>>> CSeq: 1201 BYE
>>>
>>> Notes
>>> -----
>>> This example states that WSS protocol is used, but Route header
>>> specifies SIP URI with transport=ws. which would mean WS (insecure Web
>>> Socket). Furthermore, if SIPS URI is used in Route header, then all other
>>> URI must be SIPS as well and message cannot be forwarded over UDP, SIPS
>>> over TLS must be used instead. I have modified the entire example to use
>>> SIPS and TLS, instead of SIP and UDP.
>>>
>>> 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.
>>>
>>> --------------------------------------
>>> RFC7118 (draft-ietf-sipcore-sip-websocket-10)
>>> --------------------------------------
>>> Title               : The WebSocket Protocol as a Transport for the
>>> Session Initiation Protocol (SIP)
>>> Publication Date    : January 2014
>>> Author(s)           : I. Baz Castillo, J. Millan Villegas, V. Pascual
>>> Category            : PROPOSED STANDARD
>>> Source              : Session Initiation Protocol Core RAI
>>> Area                : Real-time Applications and Infrastructure
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>>
>>

Re: [sipcore] [Technical Errata Reported] RFC7118… Roman Shpount