Have you are seen this document? - MWC
-----------------------------------
Attached is the RUP v1 document. It incorporated discussions people made in
the last IETF and on the mailing list.
Revision Log:
1. state that RUP requirements focus on cache invalidation, and not on
content retrieval or content push.
2. state that RUP should strive to provide hooks so that future inclusion
of richer functionality is possible.
3. merge "scoping requirement" into "functional requirement".
4. classify various functional requirements into five areas.
5. describe the requirements for strong and weak cache consistency.
6. state that both server and client may initiate message exchange.
7. state that resource grouping is decided outside of RUP and not
negotiable dynamically.
8. state that the protocol semantics and message formats should be
self-contained and portable.
9. state that use cases include internet proxy, surrogates, CDNs, intranet
proxy/surrogate, and non-intermediary uses.
10. remove "content update" from the use cases.
11. switch the sections of the use cases and the functional requirements.
12. acknowledge people who've given comments on the mailing list or at the
IETF meetings.
We are moving this document to closure, so if you have comments, please
send to the list.
Dan
rup-v1.txt
Description: Text document