RFC 6302: Logging Recommendations for Internet-Facing Servers
In plain English — editorial summary, not part of the RFC
In the wake of IPv4 exhaustion and deployment of IP address sharing techniques, this document recommends that Internet-facing servers log port number and accurate timestamps in addition to the incoming IP address. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6302
- Published
- June 2011
- Authors
- A. Durand; I. Gashinsky; D. Lee; S. Sheppard
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- int
- Pages
- 5
- Also known as
- BCP162
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6316Sockets Application Program Interface (API) for Multihoming ShimCurrent
July 2011
- RFC 6317Basic Socket Interface Extensions for the Host Identity Protocol (HIP)Current
July 2011
- RFC 6320Protocol for Access Node Control Mechanism in Broadband NetworksUpdated
October 2011
- RFC 6282Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based NetworksUpdated
September 2011
- RFC 6279Proxy Mobile IPv6 (PMIPv6) Localized Routing Problem StatementCurrent
June 2011
- RFC 6276DHCPv6 Prefix Delegation for Network Mobility (NEMO)Current
July 2011
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 6273The Secure Neighbor Discovery (SEND) Hash Threat AnalysisCurrent
June 2011
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?