RFC 2430: A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)
In plain English — editorial summary, not part of the RFC
This document describes the Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) for Internet Service Providers (ISPs). This memo provides information for the Internet community.
Document record
- Document ID
- RFC2430
- Published
- October 1998
- Authors
- T. Li; Y. Rekhter
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2267Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address SpoofingObsoleted
January 1998
- RFC 2751Signaled Preemption Priority Policy ElementObsoleted
January 2000
- RFC 3178IPv6 Multihoming Support at Site Exit RoutersCurrent
October 2001
- RFC 2490A Simulation Model for IP Multicast with RSVPCurrent
January 1999
- RFC 2547BGP/MPLS VPNsObsoleted
March 1999
- RFC 2260Scalable Support for Multi-homed Multi-provider ConnectivityCurrent
January 1998
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?