IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Sun, 15 December 2019 22:54 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B269D120128 for <sipcore@ietfa.amsl.com>; Sun, 15 Dec 2019 14:54:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aliax-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SV2__ytUHejY for <sipcore@ietfa.amsl.com>; Sun, 15 Dec 2019 14:54:51 -0800 (PST)
Received: from mail-ua1-x942.google.com (mail-ua1-x942.google.com [IPv6:2607:f8b0:4864:20::942]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80B58120119 for <sipcore@ietf.org>; Sun, 15 Dec 2019 14:54:51 -0800 (PST)
Received: by mail-ua1-x942.google.com with SMTP id f7so1433007uaa.8 for <sipcore@ietf.org>; Sun, 15 Dec 2019 14:54:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=StJGulM4deQ0SyI1rJqFTY23lAf8vy7RD+7pMd0/cQc=; b=n48lo0SjNMtnATspnUUSV+2rx/JBXfi7ZYn28HyBkYoSt57ZcP+yKHcyM3WiWci+PB +z0L5uMP/LnvC9dEghdSdunfPYWA/vhVvKgcXM+XYoPRAj2tUh1sodB/ge8G3Rr4hL3O 9eS/gJ9mLl2nh1gnvdqVLJTsMs4xsUfoMvhaQBNjTKQtcgbdUYDs+8gzrjNRjG1Yd5M/ bf9OY1hLIwSqpMyEnWDtMfZD3FntcmMB/zAzdpO/kUmHXLxLkDYgDX87qnay3ebMxqRV UX+WbcxzdNVXdN6begOTSMAsbsTIV1AqCBJGFlreX8opms7hUU41BmHa/pAelMQKrap2 S+kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=StJGulM4deQ0SyI1rJqFTY23lAf8vy7RD+7pMd0/cQc=; b=luG9/Zty6JCbWR+VxPk43sC19cUGq7oAJNkQGhRSOPkQoH7f59d6GhChZVPdYB0aJu 8vv/UfhrqWMvr5LlhL0/yVNxYRUx1cmvYFjqwhaMA+F5x/rarfpGa0BsWKqQDTFtanaZ uDGqYhwWCE+CiqClXwNiVPBpwRMnA+GneBAAR7IxujyjJM9woh/iSOzB0jrmkbVyaE1T 8+WeMmq6fPZ25qxCOg1XOsd8sPvMHJjgRwtLvue2KXfH2ww1hjX7jzl2PZgmpyMEPRIq HV0APEIW0JbH+Xe0uWnN84jLTrMTr1QtDFiwTFvEi1RrWzQnyZNe+sX8GmBS12qu1r5m 1x5w==
X-Gm-Message-State: APjAAAVxHlGrn0YbpnUy3eIfsfcTq+Oang5pSlXWnBVIA3ek0WvgRzPP 7vKP5iD74s/9VsMXz/+wRewt5V+GQ1rZUZmUYDeAaw==
X-Google-Smtp-Source: APXvYqwJsra9dmM9sxVJHcuC6P639noaRUsoaechgQ0WNAFsVweLSLAgldTaiAMl/bwVUt+K+4IGk0clLNisZxJJJ1Q=
X-Received: by 2002:ab0:24cd:: with SMTP id k13mr22092066uan.66.1576450490293; Sun, 15 Dec 2019 14:54:50 -0800 (PST)
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> <CAD5OKxtZK+irOGk5r6Gj1QKSnEqw5bc7_sxN+VBZxoyURk=DOA@mail.gmail.com>
In-Reply-To: <CAD5OKxtZK+irOGk5r6Gj1QKSnEqw5bc7_sxN+VBZxoyURk=DOA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Sun, 15 Dec 2019 23:54:39 +0100
Message-ID: <CALiegfk4M-U75XFSygL85Pqazuf642ig8iHiVqw5gNzfnD2jmw@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
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: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/Qm93Q9d6dFbGCNJaLJbDIgdCN30>
Subject: Re: [sipcore] [Technical Errata Reported] RFC7118 (5937)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Dec 2019 22:54:58 -0000

Yeah, that's exactly the section I meant :)

On Sat, 14 Dec 2019 at 21:42, Roman Shpount <roman@telurix.com> wrote:
>
> 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: <sips:proxy.example.com:443;transport=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



-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email