| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 07:01:25 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=vB.IWErZpDdB2tZ5JXsALtZedFXgN2GEZTIKgfxQWOM-1760079685-1.0.1.1-7c6pLgQ1WeY0I0AtmT.sLo0nchaLqETBqPPixJWQhcTcugmoJuWPZkdxz32ponBKxEFnMzu6F3bdMxIZn79eJzWO_8Mp7qSecIxrk_xaFDs; path=/; expires=Fri, 10-Oct-25 07:31:25 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c43f0d1f331ec2-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 4001 » RFC Editor
Search RFCs
RFC 4001
Textual Conventions for Internet Network Addresses, February 2005
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 3291
- Authors:
- M. Daniele
B. Haberman
S. Routhier
J. Schoenwaelder - Stream:
- IETF
- Source:
- NON WORKING GROUP
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4001
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 4001
Abstract
This MIB module defines textual conventions to represent commonly used Internet network layer addressing information. The intent is that these textual conventions will be imported and used in MIB modules that would otherwise define their own representations. [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