Browse Prior Art Database

Resource Allocation, Control, and Accounting for the Use of Network Resources (RFC1346)

IP.com Disclosure Number: IPCOM000002170D
Original Publication Date: 1992-Jun-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 6 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Jones: AUTHOR

Related Documents

10.17487/RFC1346: DOI

Abstract

The purpose of this RFC is to focus discussion on particular challenges in large service networks in general, and the International IP Internet in particular. No solution discussed in this document is intended as a standard. Rather, it is hoped that a general consensus will emerge as to the appropriate solutions, leading eventually to the adoption of standards. This memo provides information for the Internet community. It does not specify an Internet standard.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 26% of the total text.

Network Working Group P. Jones Request for Comments: 1346 Joint Network Team, UK June 1992

Resource Allocation, Control, and Accounting for the Use of Network Resources

Status of this Memo

This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited.

0. MANAGEMENT SUMMARY

This paper gives reasons for wanting better sharing mechanisms for networks. It concludes that the challenge of sharing network resources (and for example intercontinental link resources) between groups of users is neither well understood, nor well catered for in terms of tools for those responsible for managing the services. The situation is compared with other fields, both inside and outside IT, and examples are cited. Recommendations for further work are made.

The purpose of this RFC is to focus discussion on particular challenges in large service networks in general, and the International IP Internet in particular. No solution discussed in this document is intended as a standard. Rather, it is hoped that a general consensus will emerge as to the appropriate solutions, leading eventually to the adoption of standards.

The structure of the paper is as follows:

1. Findings 2. Conclusions 3. Recommendations

1. FINDINGS

Issues arising from contention in the use of networks are not unusual. Once connectivity and reliability have been addressed to a reasonable level, bandwidth becomes (or appears to become?) the main issue. Usage appears to have a strong tendency to rise to fill the resources available (fully in line with the principles of Parkinson’s Law). Line-speed upgrades have an effect, but with no guarantee of permanently alleviating the problem. Line-speeds are increasing as technology improves over time, but the variations on matters like availability and funding are wide, and users remain avaricious.

Jones [Page 1]

RFC 1346 Resource Allocation, Control, and Accounting June 1992

Often the situation can appear worse than having to survive in a jungle, in the sense that the strong (even if "good") seem to have little advantage over the weak. It may seem that it is the determined person rather than the important work that gets service.

Most people will have experienced poor service on an overloaded network at some time. To help the end-users, it seems on the face of it that one must help the IT Service Manager he relates to. Examples relating to the relationship between the network manager and his customers, IT Service Managers at institutions connecting to his network, include the following:

(a) If the IT Service Manager finds his link to the Network Manager’s network overloaded, he may be offered a link upgrade, probably with a cost estimate. He might prefer control mechanisms whereby he can say that department X deserves more resources than department Y, or that interactive terminal use takes preference over file transfers, or that user U is more important than user V.

(b) Where an IT Service...

Processing...
Loading...