idnits 2.17.1 draft-emailarchiveitoption-std-01.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: ---------------------------------------------------------------------------- == It seems as if not all pages are separated by form feeds - found 0 form feeds but 4 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 20 instances of too long lines in the document, the longest one being 23 characters in excess of 72. ** There are 4 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 (May 13, 2019) is 1809 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 (**), 0 flaws (~~), 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 Ex SUN Employee 3 Intended status: Standards Track Individual 4 Expires: Nov 13, 2019 May 13, 2019 6 Extensions to WHois service to allow query on email identities 7 draft-emailarchiveitoption-std-01 9 Abstract 11 This document describes the need for a email archive option 12 button or check box in email client to make sure of accountability 13 of emails, transmission delivery and control of email SPAM 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 May 13, 2019. 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 ...........................................4 52 5. Acknowledgements ............................................4 54 1. Introduction 56 This document describes the need for a email archive option 57 button or check box in email client to make sure of accountability 58 of emails, transmission delivery and control of email SPAM. 60 2. Background 61 If i send an email from pradeepan88@hotmail.com to sovereignamber@hotmail.com 62 theres no guarantee it would be delivered, theres no proof that pradeepan88@hotmail.com 63 wrote it, theres no guarantee originator is spam. I recieved emails 64 from efcc.nigeria.org@representative.com about a ATM valued 8.3 million dollars 65 issued to be in Feb 2013 i responded followed their instructions and still 66 does not have the ATM instead i was harmed in low class western medical hospitals 67 and the email pradeep@explodingmoon.org i used disabled by disabling the website 68 for nonpayment.If my email client had a archiveit checkbox then archive.org 69 can be used to archive it. 71 3. General Information of the service 72 Nowadays backup is not costly as terrabytes can be obtained for dollars 73 and not millions. I am stranded outside my natural land of california 74 because of racist criminals stealing my money and using a birth place 75 and the criminals there to exploit it and having been sending many SOS 76 emails. I have send emails with evidence of crime to many authortiy emails. 77 I do not have a solution by delivery of money and is being stolen. The authority 78 recipients cannot held liable as theres no evidence to public i have reported 79 the crime. If for every email for which the sender checks in archiveit option 80 as a checkbox or button then i can hold the authorities liable and punish 81 them for financial crime if it is archived in a specific URL in archive.org 82 that can be derived from the email. 84 4.Authors' Addresses 86 Pradeep Kumar Xplorer 87 EMail: pradeep@explodingmoon.org, pradeepan88@hotmail.com 88 URI: http://www.pradeepkumarxplorer.com 90 5.Acknowledgement 91 None