Hi, A new revision of PPSP survey has been uploaded. Please review and comments= ! -Ning > -----Original Message----- > From: internet-drafts at ietf.org [mailto:internet-drafts= at ietf.org] > Sent: Monday, February 25, 2013 9:53 AM > To: ppsp-chairs at tools.ietf.org; draft-ietf-ppsp-survey at tools.ietf.o= rg; > martin.stiemerling at neclab.eu > Subject: New Version Notification - draft-ietf-ppsp-survey-04.txt >=20 >=20 > A new version (-04) has been submitted for draft-ietf-ppsp-survey: > http://www.ietf.org/internet-drafts/draft-ietf-pps= p-survey-04.txt >=20 >=20 > The IETF datatracker page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-ppsp-survey/ >=20 > Diff from previous version: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-ppsp-surv= ey-04 >=20 > IETF Secretariat.

On 26/02/2013 16:31, stefano previdi wrote:<= /DIV>

> Please, have a look at the dr= aft:

> http://www.ietf.org/internet-drafts/draft-ietf-= ppsp-problem-statement-13.txt

> and come back to the list wit= h any comment.

Hi all

I have the following comments:

* PPSP.OAM.REQ-1: PPSP MUST be sufficiently&= nbsp;configurable for

installation and initial setup.

I don't get the reference to "initial&n= bsp;setup" there. I suggest

to make the requirement "sufficiently config= urable" (which is =20

what we strived for with different chun= k addressing, content

protection methods) and state that the = configuration should

allow the proxy-based and end-client scenari= os.

* PPSP.OAM.REQ-2: PPSP MUST implement a = ;set of configuration

parameters with default values.

IMHO the descriptive text doesn't add a= nything and suggest it

be removed.

* PPSP.OAM.REQ-3: PPSP MUST be capable = of controlling traffic load to

existing networks.

I suggest to rephrase this to "PPSP&nbs= p;SHOULD allow steering by

network-load management protocols." Current phras= ing I find

unclear and very restrictive with the M= UST clause.

* PPSP.OAM.REQ-4: PPSP MUST support diagnost= ic operations.

Typo: "correct operations" -> "correct op= eration"

Typo: "*The* PPSP tracker should"

Rephrase: "obtained chunks in due time" = ;-> "whether it obtained

chunks in time".

* PPSP.OAM.REQ-5: PPSP MUST facilitate achie= ving quality acceptable to

streaming application.

I have problems with the last paragraph= about scalable

streaming. To me, it suggests scalable = streaming should be

supported. I suggest to rephrase to "PP= SP implementations MAY

use techniques such as scalable streaming&nb= sp;to handle bandwidth

shortages without disrupting playback."

Typo: "to streaming application" -> "to&n= bsp;*the* streaming ..."=20

* PPSP.OAM.REQ-6: PPSP MUST support remote&n= bsp;management using

centralized server, i.e. PPSP tracker. A&nbs= p;basic set of management

information MUST be implemented by PPSP = ;tracker.

The wording suggests a centralized design&nb= sp;where all management

operations are done via the tracker. Th= is image is not correct

IMHO. A tracker service can play an&nbs= p;important role in managing

a swarm. E.g. it can be used to&nb= sp;control publication of a swarm,

or to monitor the health of the sw= arm. Hence it should have a

standard management interface that supports = such functionality.

This interface should take into account = ;that the tracker

*service* may be implemented by multiple&nbs= p;*servers*. However,

PPSP should also support tracker-less design= s and should define

a management interface for (farms of) P= PSP seeders.

I suggest to rephrase the requirement s= o that the tracker

service and PPSP seeders should have a&= nbsp;remote management

interface. Current descriptive text should b= e tweaked to

explain the unique position of the trac= ker (sees both clients

and PPSP seeders).

* PPSP.OAM.REQ-9: PPSP MUST support accounti= ng management when content

provider wants to charge clients for ce= rtain content.

I suggest to change the "MUST" to = a "MAY" or "SHOULD allow

accounting management".

CU,

Arno

_______________________________________________

ppsp mailing list

ppsp@ietf.org

https://w

------=_001_NextPart648082581085_=------