Re: [P2PSIP] RFC6940: Detecting Partitioning

Michael Chen <michaelc@idssoftware.com> Tue, 16 October 2018 01:00 UTC

Return-Path: <michaelc@idssoftware.com>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 880321274D0 for <p2psip@ietfa.amsl.com>; Mon, 15 Oct 2018 18:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.1
X-Spam-Level: *
X-Spam-Status: No, score=1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no
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 wNGERAaS9z3n for <p2psip@ietfa.amsl.com>; Mon, 15 Oct 2018 18:00:06 -0700 (PDT)
Received: from p3plsmtpa11-08.prod.phx3.secureserver.net (p3plsmtpa11-08.prod.phx3.secureserver.net [68.178.252.109]) (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 45079127332 for <p2psip@ietf.org>; Mon, 15 Oct 2018 18:00:06 -0700 (PDT)
Received: from [10.67.206.12] ([166.170.46.27]) by :SMTPAUTH: with ESMTPSA id CDiOgp1IkFlPzCDiPg5B7t; Mon, 15 Oct 2018 18:00:05 -0700
Date: Mon, 15 Oct 2018 18:00:02 -0700
Message-ID: <9584548e-e9bb-4845-92d2-78bd040a95c5@email.android.com>
X-Android-Message-ID: <9584548e-e9bb-4845-92d2-78bd040a95c5@email.android.com>
In-Reply-To: <1539590214.1981.2@smtp.gmail.com>
From: Michael Chen <michaelc@idssoftware.com>
To: Evgeny <xramtsov@gmail.com>
Cc: p2psip@ietf.org
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
X-CMAE-Envelope: MS4wfLsMfoKjy1KjCAOUC+v9vdB1Q+GANYy0xeXp3QVeLH1NIxgJjqzXAG5zAUK+oBbozdNCWfoTJkkQomYk5yjsbwv/Cq0GXCcpA9KiV/Oeo3xqlph6HW0/ zv4orPt7JCaWpTZTdGTi2R1DOJ+0Co7/TGhgnSe18tbbbCC0XYIK9yey1XG24+TMCAQ/mjUOkebllpWbIXnnVHeE4i2Z5rhcQPo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/Q5XRMW2xWGcosQg7QMTe7IK9oPU>
Subject: Re: [P2PSIP] RFC6940: Detecting Partitioning
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 16 Oct 2018 01:00:08 -0000

This is universal for all RELOAD requests and responses, regardless how many forwarding node involved:

1. The security block of a request belongs to (signed by) the requesting node.

2. The security block of a response belongs to (signed by) the responding node.

3. A forwarding node only changes the header (e.g. via list, which is why you won't find the requester and responder in via list).

Therefore, the partition check response header and body are both useless to the requester, only it's security block matters, which has the responders identity.

I hope that helps.

--Michael