idnits 2.17.1 draft-shafranovich-privacy-mailbox-00.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: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (May 31, 2018) is 2129 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Y. Shafranovich 3 Internet-Draft Nightwatch Cybersecurity 4 Intended status: Informational May 31, 2018 5 Expires: December 2, 2018 7 Common Mailbox Name for Privacy Issues 8 draft-shafranovich-privacy-mailbox-00 10 Abstract 12 Multiple Internet standards describe common mailbox names (mailbox @ 13 domain) to be used by organizations for operational and business 14 functions. This document defines a new mailbox called "privacy" that 15 SHOULD be used for contacting domain name owners about privacy 16 issues. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on December 2, 2018. 35 Copyright Notice 37 Copyright (c) 2018 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Mailbox Definition . . . . . . . . . . . . . . . . . . . . . 2 54 3. Security considerations . . . . . . . . . . . . . . . . . . . 2 55 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 56 5. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 6. Normative References . . . . . . . . . . . . . . . . . . . . 3 58 Appendix A. Note to Readers . . . . . . . . . . . . . . . . . . 3 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1. Introduction 63 Multiple Internet standards describe common mailbox names (mailbox @ 64 domain) to be used by organizations for operational and business 65 functions. This document defines a new mailbox called "privacy" that 66 SHOULD be used for contacting domain name owners about privacy 67 issues. 69 2. Mailbox Definition 71 Several mailboxes are defined in section 4 of [RFC2142] that are 72 intended to be used by outside parties to contact the organization 73 that own the domain name about specific operational issues. This 74 document updates section 4 of [RFC2142] with an addition of a new 75 mailbox that SHOULD be used to contact the domain name owner 76 regarding privacy issues. Further information regarding privacy 77 issues in Internet protocols can be found in [RFC6973]. 79 The new mailbox is defined as follows: 81 +---------+--------------------+-----------------------------+ 82 | MAILBOX | AREA | USAGE | 83 +---------+--------------------+-----------------------------+ 84 | PRIVACY | Customer Relations | Privacy issues and concerns | 85 +---------+--------------------+-----------------------------+ 87 Example of a new mailbox: 89 privacy@example.com 91 3. Security considerations 93 Organizations setting up this mailbox should be aware of potential 94 for spam, malware and other attacks via emails sent to this address. 96 4. IANA Considerations 98 This document has no IANA actions 100 However, an IANA registry for common mailbox names may be a good idea 101 in the future. 103 5. Terminology 105 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 106 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 107 and "OPTIONAL" are to be interpreted as described in [RFC2119]. 109 6. Normative References 111 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 112 Requirement Levels", BCP 14, RFC 2119, 113 DOI 10.17487/RFC2119, March 1997, 114 . 116 [RFC2142] Crocker, D., "Mailbox Names for Common Services, Roles and 117 Functions", RFC 2142, DOI 10.17487/RFC2142, May 1997, 118 . 120 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 121 Morris, J., Hansen, M., and R. Smith, "Privacy 122 Considerations for Internet Protocols", RFC 6973, 123 DOI 10.17487/RFC6973, July 2013, 124 . 126 Appendix A. Note to Readers 128 *Note to the RFC Editor:* Please remove this section prior to 129 publication. 131 Development of this draft takes place on Github at: 132 https://github.com/nightwatchcybersecurity/privacy-mailbox 134 Author's Address 136 Yakov Shafranovich 137 Nightwatch Cybersecurity 139 Email: yakov+ietf@nightwatchcybersecurity.com