[ppsp] 答复: FW: New Version Notification for draft-huang-ppsp-extended-tracker-protocol-03.txt

Hi Rachel,

I found some inconsistencies in the new revision as follows for you to
consider: 

1, There are inconsistent description about DISCONNECT messages: On Page 5,
in Section 4.1.2, paragraph #2, it is stated that "The DISCONNECT Request
message is used when the peer intends to no longer participate in *all*
warms." However, On page 6, in Section 4.2, paragraph #1, it goes "the peer
DISCONNECTs from the corresponding swarm (swarm_b) while still sharing the
first content (swarm_a)". Subsequent relevant texts all seem to be comply
with the first one.

2, There are inconsistent description about the exemplified session in
Section 4.2 between the text and the Figure 1. For the figure does not catch
the status of ""the peer DISCONNECTs from the corresponding swarm (swarm_b)
while still sharing the first content (swarm_a)".

3, Mino typo: on page 9, paragraph labeled with "7)", the last sentence
should be "..., and transitions to TERMINATE s*t*ate for that Peer-ID."

A few questions about the protocol design:

1, What's the objective behind the "init-timer" scheme?

2, How would a peer be "joining the swarm with invalid Swarm_Id"?

3, In section 4.5, since there are extended messages with newly introduced
fields (e.g. contentgroup), you may also need to handle cases with "Unknown
fields" as well as "Unknown Messages".

4, In case a peer specifies the peergroup S (a subset of all the segments)
it's currently interested in with a FIND message, does it make sense for a
tracker to return a peer with only a subset S' of S to the requestor?

Lastly, as for the arrangement of contentgroup, it could be rather
bit-consuming if a peer is FINDing a scattered group of segments. I have
been proposing to use compression method to mitigate this matter.
http://datatracker.ietf.org/doc/draft-deng-ppsp-bfbitmap/ 
I would like to hear any feedback or comments from you TR guys about it:-)

BR
Lingli

-----邮件原件-----
发件人: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] 代表
Huangyihong (Rachel)
发送时间: 2013年7月11日 9:46
收件人: ppsp@ietf.org
主题: [ppsp] FW: New Version Notification for
draft-huang-ppsp-extended-tracker-protocol-03.txt

Dear all,

We have just submitted a new version of
draft-huang-ppsp-extended-tracker-protocol. This update is just some
editorial changes. No significant modification. Comments are highly
appreciated. 

Best regards,
Rachel

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Thursday, July 11, 2013 9:29 AM
To: Mario Serafim Nunes; Rui Santos Cruz; Rui Sant Cruz; Zongning; Mario
Sera Nunes; Huangyihong (Rachel); Joao P. Taveira
Subject: New Version Notification for
draft-huang-ppsp-extended-tracker-protocol-03.txt

A new version of I-D, draft-huang-ppsp-extended-tracker-protocol-03.txt
has been successfully submitted by Rachel Huang and posted to the
IETF repository.

Filename:	 draft-huang-ppsp-extended-tracker-protocol
Revision:	 03
Title:		 PPSP Tracker Protocol--Extended Protocol
Creation date:	 2013-07-11
Group:		 Individual Submission
Number of pages: 26
URL:
http://www.ietf.org/internet-drafts/draft-huang-ppsp-extended-tracker-protoc
ol-03.txt
Status:
http://datatracker.ietf.org/doc/draft-huang-ppsp-extended-tracker-protocol
Htmlized:
http://tools.ietf.org/html/draft-huang-ppsp-extended-tracker-protocol-03
Diff:
http://www.ietf.org/rfcdiff?url2=draft-huang-ppsp-extended-tracker-protocol-
03

Abstract:
This document specifies an extended Peer-to-Peer Streaming Protocol -
Tracker Protocol, which is a new extension protocol complementing the
basic core messages and usages specified in the base tracker protocol
for the exchange of meta information between trackers and peers, such as
initial offer/request of participation in multimedia content streaming,
content information, peer lists and reports of activity and status. It
extends the base tracker protocol to include new optional messages
providing new usages in the communications between peer and tracker. The
extension protocol is retro-compatible with the base tracker protocol.

The IETF Secretariat

_______________________________________________
ppsp mailing list
ppsp@ietf.org
https://www.ietf.org/mailman/listinfo/ppsp