This document specifies an Internet standards track protocol for providing guaranteed quality of service (QoS) in IP internets. It defines the requirements for network elements to support guaranteed service, which ensures firm bounds on end-to-end datagram queueing delays and bandwidth. The specification follows a service specification template and is independent of the setup mechanism used to request the service. Key features include: 1. **Guaranteed Service Requirements**: Network elements must ensure that the service approximates the "fluid model" of service, with queueing delays bounded by a function of token bucket parameters and data rate. 2. **Traffic Specification (TSpec)**: TSpec describes the traffic characteristics using a token bucket, peak rate, minimum policed unit, and maximum datagram size. 3. **Resource Specification (RSpec)**: RSpec includes a reserved rate and a slack term to achieve the desired delay. 4. **Policing and Reshaping**: Policing ensures traffic conforms to TSpec, while reshaping restores distorted traffic to meet TSpec. 5. **Ordering and Merging**: Rules for ordering and merging TSpecs and RSpecs to handle shared reservations. 6. **Implementation Guidelines**: Recommendations for implementing the service, including buffer allocation and handling of non-conforming datagrams. 7. **Evaluation Criteria**: Requirements for scheduling and admission control algorithms to ensure delay bounds are never violated. 8. **Security Considerations**: Discussion of potential denial of service attacks and how to mitigate them. The document also includes examples of use and references to related protocols and algorithms.This document specifies an Internet standards track protocol for providing guaranteed quality of service (QoS) in IP internets. It defines the requirements for network elements to support guaranteed service, which ensures firm bounds on end-to-end datagram queueing delays and bandwidth. The specification follows a service specification template and is independent of the setup mechanism used to request the service. Key features include: 1. **Guaranteed Service Requirements**: Network elements must ensure that the service approximates the "fluid model" of service, with queueing delays bounded by a function of token bucket parameters and data rate. 2. **Traffic Specification (TSpec)**: TSpec describes the traffic characteristics using a token bucket, peak rate, minimum policed unit, and maximum datagram size. 3. **Resource Specification (RSpec)**: RSpec includes a reserved rate and a slack term to achieve the desired delay. 4. **Policing and Reshaping**: Policing ensures traffic conforms to TSpec, while reshaping restores distorted traffic to meet TSpec. 5. **Ordering and Merging**: Rules for ordering and merging TSpecs and RSpecs to handle shared reservations. 6. **Implementation Guidelines**: Recommendations for implementing the service, including buffer allocation and handling of non-conforming datagrams. 7. **Evaluation Criteria**: Requirements for scheduling and admission control algorithms to ensure delay bounds are never violated. 8. **Security Considerations**: Discussion of potential denial of service attacks and how to mitigate them. The document also includes examples of use and references to related protocols and algorithms.