Ben,
On Apr 27, 2011, at 5:45 PM, Ben Niven-Jenkins wrote:
Colleagues,
During the ALTO meeting at IETF80 I made some comments at the
microphone highlighting my concerns with the scope of draft-penno-
alto-cdn-03 being far too wide and that we should first focus on
documenting the use cases and requirements.
To that end I've been working with a couple of folks to co-author a
draft focussed on documenting the use cases for ALTO & CDNs, the
thinking being that a fresh draft with a tighter focus than draft-
penno-alto-cdn-03 makes highlighting and discussing the use cases
without slipping into possible solution mechanisms much simpler and
cleaner.
makes sense.
We have just published a -00 version which is available here:
http://tools.ietf.org/html/draft-jenkins-alto-cdn-use-cases-00
So far we have only included details on two use cases and included
placeholders for another two because we wanted to socialise the work
early to see if others were interested in contributing text for the
use cases they have as well as to solicit early feedback on the
structure and focus of the draft.
splitting the current alto-cdn document makes sense to me and we
need to define:
a. use cases
b. requirements
c. proposed solutions
your draft addresses the use cases and you may want to merge the
use cases sections we currently have in the alto-cdn draft so to
focus that one only on the proposed solution(s).
The question is about requirements: do we want to include them
in one of the two drafts or into a separate document ?
s.
Comments/Suggestions/etc on the draft are welcomed.
Ben
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
