[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: email@example.com
- Subject: request-routing requirements
- From: brad cain <firstname.lastname@example.org>
- Date: Mon, 15 Jan 2001 18:24:39 -0500
- Delivery-date: Mon, 15 Jan 2001 15:25:51 -0800
- Envelope-to: email@example.com
As the volunteer who is coordinating the requirements draft for
request routing, I am trying to gather all high level
requirements for request-routing.
At this point we DO NOT solicit suggestion for implementation
details and mechanisms of the system but rather are interested in higher
level requirements. (For example: we want to know things like
the request routing system has to know which CDN caches a particular
set of URLs. We DO NOT want to know if caches get advertised or
content gets advertised ....). If you feel you can contribute
to this effort please post to the mailing list your requirements
for the request routing system and indicate if you feel the
requirement belongs in the IETF MUST, SHOULD or MAY category.
A very "drafty" version of the requirements will be available
on 1/19. Therefore, it is important that your requirements are posted
to the list at the latest by 1/17 to allow us to combine them into
a draft. Please note that this is just a first cut at
the requirements -- more will be added as we go.