Again, network resources include:
- b/w (bandwidth)
- b/w availability
- latency
- latency availability
- data storage
- data storage availability
- link count
- link count availability
Are we yet missing a basic "network level" resource?
The lone neurone strikes again: A typical network use pattern is: - connect - begin download So link reservation windows where the pertinent parameter is time T, may be complemented with "data xmit" total, either at link setup, and/ or "shortly" after link has been set up. So this protocol might be e.g. - connect, default time reservation e.g. 2 minutes - begin download - (e.g. HTTP) headers identify the download as being say 160MiB - link/switch request to modify "T=2 minutes" to "xmit=170MiB" - ack or nack from peer nodes as they are willing/able