Network Working Group A. Dulaunoy Internet-Draft SES ASTRA Intended status: Standards Track April 27, 2007 Expires: October 29, 2007 geographic location in syslog draft-dulaunoy-syslog-geolocation-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on October 29, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document describes how to add geographic location in syslog. It defines a STRUCTURED-DATA to add latitude, longitude and altitude in the syslog message. Dulaunoy Expires October 29, 2007 [Page 1] Internet-Draft geographic location in syslog April 2007 Table of Contents 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. latitude . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. longitude . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.3. altitude . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 4.1. Location Privacy . . . . . . . . . . . . . . . . . . . . . 4 4.2. Location Modification . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . . . 7 Dulaunoy Expires October 29, 2007 [Page 2] Internet-Draft geographic location in syslog April 2007 1. Terminology 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 [RFC2119]. The key words "STRUCTURED-DATA", "SD-ID", "SD-PARAM", "PARAM-NAME", "PARAM-VALUE" are to be interpreted as described in [I-D.ietf-syslog-protocol]. 2. Introduction An increasing number of network and security devices are becoming more mobile in their environment. Those mobile devices are now able to gather information like latitude and longitude about their respective geographic location. We use the STRUCTURED-DATA available in the syslog protocol to provide easily parseable geographic meta information. This memo defines a new SD-ID named "geo". The PARAM-NAMEs are latitude, longitude and altitude. PARAM-VALUEs are described below. The parameters have no influence in the existing parameters described in section 7 of [I-D.ietf-syslog-protocol]. Support of "geo" SD-ID is OPTIONAL. All SD-PARAMs are OPTIONAL. 2.1. latitude The latitude parameter contains the decimal latitude in the World Geodetic System 84 (WGS84) reference [NIMA TR8350.2]. If the latitude is unknown, the latitude parameter MUST NOT be present. 2.2. longitude The longitude parameter contains the decimal longitude in the World Geodetic System 84 (WGS84) reference [NIMA TR8350.2]. If the longitude is unknown, the longitude parameter MUST NOT be present. 2.3. altitude The altitude contains the decimal altitude in the World Geodetic System 84 (WGS84) reference [NIMA TR8350.2]. If the altitude is unknown, the altitude parameter MUST NOT be Dulaunoy Expires October 29, 2007 [Page 3] Internet-Draft geographic location in syslog April 2007 present. 3. Example The example shows only the structured data part in SD-ID "geo" of a syslog message with only a known latitude and longitude. The message is valid. [geo latitude="49.70475" longitude="5.42373"] The example shows only the structured data part in SD-ID "geo" of a syslog message with no SD-PARAM. The message is valid but the sender is unable to obtain is geographic location. [geo] 4. Security Considerations The security considerations described in syslog protocol applies when using the geographic location. 4.1. Location Privacy Location information of the syslog sender can be used by attackers to easily locate sender when observing the syslog message. Operators are advised to use a secure transport mapping to avoid such observation. 4.2. Location Modification Because message integrity is not guarantee in syslog message, an attacker may maliciously modify the location. Operators are advised to use other means for validating the integrity of the location. 5. IANA Considerations IANA is requested to register the SD-IDs and the PARAM-NAMEs described below : Dulaunoy Expires October 29, 2007 [Page 4] Internet-Draft geographic location in syslog April 2007 +-------+------------+----------+ | SD-ID | PARAM-NAME | | +-------+------------+----------+ | geo | | OPTIONAL | | | latitude | OPTIONAL | | | longitude | OPTIONAL | | | altitude | OPTIONAL | +-------+------------+----------+ Table 1 6. Acknowledgement We would like to thank the U-2010 research project (5th Call of the 6th European Research Frame Program) for providing the testing ground. 7. References 7.1. Normative References [I-D.ietf-syslog-protocol] Gerhards, R., "The syslog Protocol", draft-ietf-syslog-protocol-19 (work in progress), November 2006. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 7.2. Informative References [NIMA TR8350.2] National Imagery and Mapping Agency, "Department of Defense World Geodetic System 1984, Third Edition NIMA TR8350.2", 2000. Dulaunoy Expires October 29, 2007 [Page 5] Internet-Draft geographic location in syslog April 2007 Author's Address Alexandre Dulaunoy SES ASTRA Chateau de Betzdorf Betzdorf, L-6815 LU Phone: +352 710 725 463 Email: alexandre.dulaunoy@ses-astra.com Dulaunoy Expires October 29, 2007 [Page 6] Internet-Draft geographic location in syslog April 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Dulaunoy Expires October 29, 2007 [Page 7]