[Simple] In context of MSRP; How to tell if incoming connection request is of type TLS or TCP?

Prasun Bheri <prasun.bheri@gmail.com> Thu, 17 January 2013 08:16 UTC

Return-Path: <prasun.bheri@gmail.com>
X-Original-To: simple@ietfa.amsl.com
Delivered-To: simple@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D585B21F88D6 for <simple@ietfa.amsl.com>; Thu, 17 Jan 2013 00:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id akwJ8hOLQt0j for <simple@ietfa.amsl.com>; Thu, 17 Jan 2013 00:16:33 -0800 (PST)
Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) by ietfa.amsl.com (Postfix) with ESMTP id 5011D21F88E3 for <Simple@ietf.org>; Thu, 17 Jan 2013 00:16:33 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id x4so2255481obh.24 for <Simple@ietf.org>; Thu, 17 Jan 2013 00:16:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=KBLfW3gEQCLMO/8n54kkEVaNcoOJWNnb1C2Fca9PQaU=; b=Hhc5/7OqgMKQvjxDGgSd7vYwAgUyzbPgyBeMOC8HFgVBaWHuHEYzZPSAm3KuiBXKTp W3uzvn98KIipw4CHdNTEvBu+PWSP1e/xjcUgDc/qcxTk3kx0u7GYFDX4at9OWMdg/x0t NbRjN65c2laksyoBcgv2pAnpLDwmBSiSV1SBAznFTkPG24G8i3IQuix2U+UnaCOzTU5e ql5j8cBD2IABXLIaLl43MF0zerVcn4fe2kwzZeK69P7ldT2DePQy1GGHpj55Mp0w821s co1k7zRELhfcFad1tyoSBHZPB1AgTYn+BZvTDoSsb68axL3ihqgDbz0GBBTUW6VsJFNs 57kA==
X-Received: by 10.182.188.69 with SMTP id fy5mr3204873obc.74.1358410592774; Thu, 17 Jan 2013 00:16:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.172.41 with HTTP; Thu, 17 Jan 2013 00:15:52 -0800 (PST)
From: Prasun Bheri <prasun.bheri@gmail.com>
Date: Thu, 17 Jan 2013 13:45:52 +0530
Message-ID: <CADUAairF4cSdAQR81=sT+_UdYZGa8pp-F5DBuZVvXPwbpc=HVw@mail.gmail.com>
To: Simple@ietf.org
Content-Type: multipart/alternative; boundary="f46d0447f2a8d76be404d3779c3e"
Subject: [Simple] In context of MSRP; How to tell if incoming connection request is of type TLS or TCP?
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 08:16:34 -0000

Hello Group,

In regards to TLS over MSRP.

Scenario:
There are two sessions between  UE-A and UE-B, in which B chose to be
active endpoint in both the sessions (a=setup:active), of which one session
is over TLS and another is over TCP.

Two incoming connection requests will arrive at A.
What is the best approach for A to distinguish TLS request from TCP?

In case of SIP its easy as there are separate ports for TCP and TLS. so the
connection request will be identified based on the port upon which the
request arrived. But for MSRP rfc 4975 doesn't recommend a different port,
so both requests could arrive at same 2855 port.

Thanks & Regards,
Prasun Bheri