--- 1/draft-ietf-intarea-server-logging-recommendations-00.txt 2011-01-19 20:23:10.000000000 +0100 +++ 2/draft-ietf-intarea-server-logging-recommendations-01.txt 2011-01-19 20:23:10.000000000 +0100 @@ -1,23 +1,23 @@ Internet Engineering Task Force A. Durand Internet-Draft Juniper Networks Intended status: BCP I. Gashinsky -Expires: June 12, 2011 Yahoo! Inc. +Expires: July 23, 2011 Yahoo! Inc. D. Lee Facebook, Inc. S. Sheppard ATT Labs - December 9, 2010 + January 19, 2011 Logging recommendations for Internet facing servers - draft-ietf-intarea-server-logging-recommendations-00 + draft-ietf-intarea-server-logging-recommendations-01 Abstract 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. Status of this Memo @@ -27,44 +27,44 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on June 12, 2011. + This Internet-Draft will expire on July 23, 2011. Copyright Notice - Copyright (c) 2010 IETF Trust and the persons identified as the + Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Recommendations . . . . . . . . . . . . . . . . . . . . . . . . 3 3. ISP Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1. Normative references . . . . . . . . . . . . . . . . . . . 5 6.2. Informative references . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction According to the most recent predictions, the global IPv4 address free pool at IANA will exhaust sometime in 2011. After that, service providers will have a hard time finding enough IPv4 global addresses @@ -105,45 +105,51 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. It is RECOMMENDED as best current practice that Internet facing servers logging incoming IP addresses also log: o The source port number. - o A timestamp accurate to the second, with associated time zone. + o A timestamp, preferably in UTC, accurate to the second, from a + traceable time source (e.g. NTP). o The transport protocol (usually TCP or UDP) and destination port number, when the server application is defined to use multiple transports or multiple ports. Discussion: Carrier-grade NATs may have different policies to recycle ports, some implementations may decide to reuse ports almost immediately, some may wait several minutes before marking the port ready for reuse. As a result, servers have no idea how fast the ports will be reused and, thus, should log timestamps using a reasonably accurate clock. At this point the RECOMMENDED accuracy - for timestamps is to the second or better. + for timestamps is to the second or better. Representation of + timestamps in UTC is preffered to localtime with UTC-offset or time + zone as this extra information can be lost in the reporting chain. Examples of Internet facing servers include, but are not limited to, web servers and email servers. Although the deployment of address sharing techniques is not immediately foreseen in IPv6, the above recommendations apply to both IPv4 and IPv6, if only for consistency and code simplification reasons. Discussions about data retention policies are out of scope for this document. + The above recommendation also applies to devices such as load- + balancers logging incoming connections on behalf of actual servers. + 3. ISP Considerations ISP deploying IP address sharing techniques should also deploy a corresponding logging architecture to maintain records of the relation between customers identity and IP/port resources they utilize. However, recommendation on this topic are out of scope for this document. 4. IANA Considerations @@ -181,25 +187,25 @@ Email: adurand@juniper.net Igor Gashinsky Yahoo! Inc. 45 West 18th St. New York, NY 10011 USA Email: igor@yahoo-inc.com - Donn Lee Facebook, Inc. 1601 S. California Ave. Palo Alto, CA 94304 USA - Email: donn@facebook.com + Email: donn@fb.com + Scott Sheppard ATT Labs 575 Morosgo Ave, 4d57 Atlanta, GA 30324 USA Email: Scott.Sheppard@att.com