Plaza C,Tuesday Aftern=
oon Session III, Nov 5, 2013<=
/pre>

16:10 Agenda bashing (=
Chairs, 5 minutes)
No comments

16:15 Status of the WG=
 (Chairs, 10 minutes)
1)  Peer draft =A8C more review =
needed, especially on security and encoding perspectives.
2)  Tracker base draft =A8C need=
 author team to progress the draft faster, more calls are needed.
3=
=A3=A9S=
urvey draft =A8C need 2^nd WGLC befor=
e submitting to IESG.<=
/pre>

16:25 Peer Protocol (A=
rno remotely,50 minutes), draft-ietf-ppsp-peer-protocol-08
1)  New revision has addressed a=
ll comments from AD review.
2)  Some comments from Roni need to be address=
ed, e.g. if peer protocol need to define how to do NAT traversal. To be disc=
ussed on the list.
3)  Chunk size issue from Yunfei=
?
4) 
Chunk addressing iss=
ue 
=A8C negotiation is b=
etter. 
Lingli: in the latest version, the part for online translation be=
tween communicating peers using different chunk addressing schemes are remo=
ved. Why?
A: It is too complicated and not necessary.
 =
;
17:15 Tracker Protocol=
 (Rui remotely, 50 minutes), draft-ietf-ppsp-base-tracker-protocol-02 =

1)  In the draft, still XML form=
at in main body. Need to move XML example to appendix with more references.=

Yunfei: The new version doesn=A1=AFt reflect the consensus made i=
n the last meeting, which is to move the encoding
 issues to the appendix while keep the main body to just define messages. C=
urrently the messages are still text based. Is there any consideration on t=
he situation where different encodings are used? E.g., some peers use text =
encoding while others use binary.
Lingli: There is different understanding between Rui and the othe=
r co-authors. By binary encoding, Rui thinks it=A1=AFs
 the binary encoding of the XML, while others think it=A1=AFs the binary encoding of the tracker protocol. There are stand=
ards from ISO for binary encoding of XML, which is EXI.
Yunfei: But EXI can=A1=AFt do the translation between binary enco=
ding of the messages to XML of the messages.
Lingli: Websocket has similar mechanisms to do this kind of trans=
lation. We can reference it. I can help with the new version.

18:05 Efficient Chunk =
Availability Compression (Lingli,20 minutes), draft-deng-ppsp-bfbitmap-03
Arno: in=
 reality, streaming downloading happens sequentially, hence scope-based sch=
emes works well.
A: in Vo=
D cases, user behavior can interrupt the sequential viewing pattern. And ev=
en in live streaming case, because the concurrently peer-to-peer downloadin=
g pattern, out-of-order chunk transmission is inevitable.=

Dave: wh=
at is the objective of introducing BF scheme?
A: the m=
otive is elaborated in the last meeting=A1=AFs presentation. There is an co=
mparison of the worst case performance of different bitmap compression sche=
mes in terms of various bitmap relevant operations in PPSP.
Arno: in=
 peer protocol, peers don=A1=AFt share bitmaps, only chunk ranges updates a=
re exchanged. Peer protocol doesn=A1=AFt need b=
itmap compression.
A: range=
s or updates are special forms of compression. BF scheme can be introduced =
into peer protocol as a new chunk addressing method.

open issue 1 =A8C looks like the pro=
posed option is better no need to translation
Open iss=
ue 2 =A8C looks like it is helpful to include content scope into requests=
, but not to the responses.
No adoption at the mom=
ent. Need more mailing list discussion and offline with the tracker protoco=
l author.

Rachel: =
in extended tracker protocol, the content scope information is already inco=
rporated in the requests. But if we incorporate the same information into t=
he responses, it would be duplicated with the subsequent peer information h=
andshaking.
Ning: Wo=
uld it be possible to increase neighborhood establishment by always includi=
ng SEEDER peers in response?
A: I thi=
nk it make sense to do so to ensure FIND always hit, as long as the specifi=
c content range in need is incorporated in corresponding requests.
&nb=
sp;
18:25 Conclusion and n=
ext step (Chairs, 10 minutes)
Peer dra=
ft needs more review. <=
/span>Tracker=
 base draft needs call between co-authors to progress the draft faster. 2nd WGLC on survey draft starts soon.

18:35 End
=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 =

Than=
ks,

-Yun=
fei & Ning.
 =

 =

 =