[P2PSIP] RELOAD - AppAttach and Transport Connections
"Bless, Roland (TM)" <roland.bless@kit.edu> Mon, 08 December 2014 12:28 UTC
Return-Path: <roland.bless@kit.edu>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78C551A1C06 for <p2psip@ietfa.amsl.com>; Mon, 8 Dec 2014 04:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.951
X-Spam-Level:
X-Spam-Status: No, score=-1.951 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 qV_X0ykMORxL for <p2psip@ietfa.amsl.com>; Mon, 8 Dec 2014 04:28:22 -0800 (PST)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF1951A1BBB for <p2psip@ietf.org>; Mon, 8 Dec 2014 04:28:21 -0800 (PST)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=i72vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25 iface 141.3.10.81 id 1XxxQJ-0002LJ-CO for <p2psip@ietf.org>; Mon, 08 Dec 2014 13:28:19 +0100
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id 70FDAB006E4 for <p2psip@ietf.org>; Mon, 8 Dec 2014 13:28:23 +0100 (CET)
Message-ID: <54859967.8000401@kit.edu>
Date: Mon, 08 Dec 2014 13:28:23 +0100
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: P2PSIP WG <p2psip@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1418041699.
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/YxTinJxW7WhEdv51WlBXgE_EmWo
Subject: [P2PSIP] RELOAD - AppAttach and Transport Connections
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/p2psip/>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 12:28:28 -0000
Hi, while implementing a SIP usage we found it difficult to actually demultiplex between different transport links when using (App)AttachReq/Rsp. 1.) The RELOAD RFC https://tools.ietf.org/html/rfc6940 doesn't clearly describe whether it is possible to have several transport links per usage (i.e., Application-ID), which could be useful. 2.) In case that AttachReq and AppAttachReq are sent at the same time, the initiating node cannot easily distinguish which transport link/connection belongs to which request, other than using different ports for each request (not so NAT/FW friendly). 3.) One potential workaround is to have only one open AppAttachReq "per peer". However, if an AppAttachReq is directed to a Resource-ID, one doesn't know which peer (Node-ID) will actually sent back the AppAttachRsp. Moreover, the incoming transport links can only be distinguished by using different port numbers, since the node-ID is probably not known beforehand. Any other ideas than using different ports? Regards, Roland
- [P2PSIP] RELOAD - AppAttach and Transport Connect… Bless, Roland (TM)