RFC 3033: The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol
In plain English — editorial summary, not part of the RFC
The purpose of this document is to specify the assignment of the information field and protocol identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet protocol. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3033
- Published
- January 2001
- Authors
- M. Suzuki
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3077A Link-Layer Tunneling Mechanism for Unidirectional LinksCurrent
March 2001
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
- RFC 2584Definitions of Managed Objects for APPN/HPR in IP NetworksCurrent
May 1999
- RFC 3609Tracing Requirements for Generic TunnelsCurrent
October 2003
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-ISCurrent
October 2008
- RFC 3168The Addition of Explicit Congestion Notification (ECN) to IPUpdated
September 2001
- RFC 2834ARP and IP Broadcast over HIPPI-800Updated
May 2000
- RFC 2827Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address SpoofingUpdated
May 2000
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?