idnits 2.17.1 draft-emaillogger-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ~~ Missing draftname component: the document name given in the document, 'draft-emaillogger-02', does not seem to contain all the document name components required ('draft' prefix, document source, document name, and revision) -- see https://www.ietf.org/id-info/guidelines#naming for more information. == It seems as if not all pages are separated by form feeds - found 0 form feeds but 3 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 5 instances of too long lines in the document, the longest one being 10 characters in excess of 72. ** There are 13 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (Apr 17, 2015) is 3268 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 4 errors (**), 1 flaw (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Pradeep Kumar Xplorer 2 Internet-Draft 3 Intended status: Standards Track Individual 4 Expires: Oct 17, 2015 Apr 17, 2015 6 Email provider should provide email owner an audit log 7 draft-emaillogger-02 9 Abstract 11 This document describes the need for an email service provider 12 to provie a feature to the email owner to log who and where has 13 logged into his email by an email itself if possible. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on Oct 17,2015. 32 Copyright Notice 34 Copyright (c) 2013 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 48 1. Introduction ............................................... 2 49 2. Background ..................................................2 50 3. General Information of the service ..........................3 51 4. Authors Addresses ...........................................3 52 5. Acknowledgements ............................................3 54 1. Introduction 56 To enforce standards for email providers to provide an audit or 57 email logging feature. So i own pradeepan88@hotmail.com, i should 58 be able to configure that whenever pradeepan88@hotmail.com is logged 59 in an email should be generated and send to the same email or some 60 other email. 62 2. Background 63 I have no clue who logs into my emails and this disturbs me. 64 I should know from which IP's my email was logged into. 66 3. General Information of the service 67 I should be able to go to security settings of my email and 68 provide an email where audit of logins to my email are send. 69 It can be send once every ten or hundred logins. 71 (Its a shame that these are not implemented a group trying to 72 murder me or make me a disabled and preventing me from leading 73 my life in California. Anyone can own this and use their 74 resources to implement these, they can just email me. As i am writing 75 this out of my own requirement, i demand my personal wealth not 76 used to maintain ietf.org or to send emails. Its my impression 77 that they are self sufficient. I would work on these when i have 78 my money in my bank at my speed) 80 4.Authors' Addresses 82 Pradeep Kumar Xplorer 83 EMail: pradeepan88@hotmail.com 84 URI: http://www.explodingmoon.org 85 http://www.dhyanayoga.info 86 http://www.pradeepkumarxplorer.com 88 5.Acknowledgement 90 I have been a publisher of http://www.dhyanayoga.info since 2004/2005 91 and http://www.explodingmoon.org since 2008. I am send money by many 92 groups but a group of shamless cybercriminals are logging into my emails 93 and handling those. I have no clue who logs into my emails and an audit log 94 would help.