CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 11:47:58 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=QcgQEXQ4zzmy_PP8zKxmi4USFxYC4n5yJs8uwRhHOCk-1760183278-1.0.1.1-8h2NxNckqIMD8ZAS5g8w6vPaTvktt7g.9osjtFcMqjUdRH8AXzRL.3JUkhM.naygd4CNcTfEa1Knqx94umilk9Hy7etxhTA8DaFJ9oifhcg; path=/; expires=Sat, 11-Oct-25 12:17:58 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98ce202a6c7e7fa8-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2667 » RFC Editor
Search RFCs
RFC 2667
IP Tunnel MIB, August 1999
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 4087
- Author:
- D. Thaler
- Stream:
- IETF
- Source:
- ifmib (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2667
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2667
Abstract
This memo defines a Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing tunnels of any type over IPv4 networks. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us