Re: [P2PSIP] RFC6940: Detecting Partitioning
Michael Chen <michaelc@idssoftware.com> Sun, 14 October 2018 22:25 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 E74FC130DEC for <p2psip@ietfa.amsl.com>; Sun, 14 Oct 2018 15:25:55 -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 q7TBTM4KH6ct for <p2psip@ietfa.amsl.com>; Sun, 14 Oct 2018 15:25:54 -0700 (PDT)
Received: from p3plsmtpa06-04.prod.phx3.secureserver.net (p3plsmtpa06-04.prod.phx3.secureserver.net [173.201.192.105]) (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 CDD2D12D4EA for <p2psip@ietf.org>; Sun, 14 Oct 2018 15:25:54 -0700 (PDT)
Received: from [10.16.177.171] ([166.176.59.30]) by :SMTPAUTH: with ESMTPSA id Bopdgiry3Zb9HBopegMPZr; Sun, 14 Oct 2018 15:25:54 -0700
Date: Sun, 14 Oct 2018 15:25:52 -0700
Message-ID: <af644580-13fb-41e5-aee8-b0126e2e0d2a@email.android.com>
X-Android-Message-ID: <af644580-13fb-41e5-aee8-b0126e2e0d2a@email.android.com>
In-Reply-To: <1539543879.1981.0@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: MS4wfMQj3ZacImES0kjo1flwyMeAf38qKvEv9/ev9tWVfMgqC/evUznqnRG0+nwi3mT81HVnR13+fYkh0fVcFKPmKKknMFJpAOqOSB9gL8RlTTBl+IuTBK3V m9Q4Wii/Ro63lyDcRz8U6xmbFO+Ok/zq+F7rkW3jbLGO5woGB0hilTEg+jzWykdbAgj5hhCfXyIWSRG3uy5zWWL1C//15Mcawto=
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/m2ARmsiQiP2wTE3pwexuR_mJF84>
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: Sun, 14 Oct 2018 22:25:56 -0000
Hi thereI have hard time understanding the mechanism described in 10.7.4.4 (Detecting Partitioning) [1]:> P SHOULD then send a Ping for its own Node-ID routed through B.> If a response is received from peer S', which is not P's successor,> then the overlay is partitionedHow is it even possible? Given the Symmetric Recursive Routing, the Ping answer will always come from node B.I tried to grasp through the RFC about special routing rules of Ping answers, but I didn't find anything specialexcept the statement in 6.1.2 (Other ID) [2] which I *fail* to understand:> The node MUST implement support for> returning responses to a Ping or Attach request made by a Joining> Node Attaching to its responsible peer"made by a Joining Node At taching to its responsible peer"? What does that mean exactly? Why is "Attaching"with a capital letter?[1] https://tools.ietf.org/html/rfc6940#section-10.7.4.4" rel="nofollow">https://tools.ietf.org/html/rfc6940#section-10.7.4.4[2] https://tools.ietf.org/html/rfc6940#section-6.1.2" rel="nofollow">https://tools.ietf.org/html/rfc6940#section-6.1.2
- [P2PSIP] RFC6940: Detecting Partitioning Evgeny
- Re: [P2PSIP] RFC6940: Detecting Partitioning Michael Chen
- Re: [P2PSIP] RFC6940: Detecting Partitioning Bless, Roland (TM)
- Re: [P2PSIP] RFC6940: Detecting Partitioning Evgeny
- Re: [P2PSIP] RFC6940: Detecting Partitioning Michael Chen
- Re: [P2PSIP] RFC6940: Detecting Partitioning Michael Chen
- Re: [P2PSIP] RFC6940: Detecting Partitioning Roland Bless
- Re: [P2PSIP] RFC6940: Detecting Partitioning Evgeny