[ppsp] Regarding clause "2.3.2 error conditios" in PPSP-TP

현욱 <whyun@etri.re.kr> Mon, 19 October 2015 08:46 UTC

Return-Path: <whyun@etri.re.kr>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11A8C1A86F0 for <ppsp@ietfa.amsl.com>; Mon, 19 Oct 2015 01:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.511
X-Spam-Level:
X-Spam-Status: No, score=-96.511 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=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 Wi9XdvjAyFaS for <ppsp@ietfa.amsl.com>; Mon, 19 Oct 2015 01:46:50 -0700 (PDT)
Received: from smtpeg.etri.re.kr (smtpeg2.etri.re.kr [129.254.27.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A8811A802E for <ppsp@ietf.org>; Mon, 19 Oct 2015 01:46:49 -0700 (PDT)
Received: from SMTP3.etri.info (129.254.28.73) by SMTPEG2.etri.info (129.254.27.142) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 19 Oct 2015 17:46:48 +0900
Received: from SMTP1.etri.info ([169.254.1.101]) by SMTP3.etri.info ([10.2.6.32]) with mapi id 14.01.0355.002; Mon, 19 Oct 2015 17:46:43 +0900
From: =?ks_c_5601-1987?B?x/a/7Q==?= <whyun@etri.re.kr>
To: "ppsp@ietf.org" <ppsp@ietf.org>
Thread-Topic: [ppsp] Regarding clause "2.3.2 error conditios" in PPSP-TP
Thread-Index: AdEKSu3CS4xk/LVuSWKsP+auNVOHtw==
Date: Mon, 19 Oct 2015 08:46:42 +0000
Message-ID: <3547C9BBE62E844093C527F2EE9D9E3A1E237A57@SMTP1.etri.info>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [129.254.164.147]
Content-Type: multipart/alternative; boundary="_000_3547C9BBE62E844093C527F2EE9D9E3A1E237A57SMTP1etriinfo_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ppsp/typ1_C0IeGbnD5K-0h7tOEEkajw>
Subject: [ppsp] Regarding clause "2.3.2 error conditios" in PPSP-TP
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppsp/>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2015 08:46:52 -0000

Hi all,

I have a question regarding clause 2.3.2 Error conditions.
In sub-clause B) it says,

B) At the TRACKING state (while the "track timer" has not expired)
      receiving a CONNECT message from that Peer ID with invalid swarm
      actions (section 5.1) is considered an error condition.  The
      Tracker responds with error code Forbidden (described in
      section 4.3), stops the "track timer", deletes the registration,
      transitions to TERMINATE state for that Peer ID and the SM is
      destroyed.

If a peer that has already joined multiple overlay networks(swarms) tries to join invalid swarm,
it looks like that the registration should be removed according to above sentence.

Am I understanding right?

I think that such situation probably happen often, since a user may mistype or session may be removed by owner.
How about don’t going TERMINATE state but just send error message for the transaction.


Regards,..
W.Hyun