Internet DRAFT - draft-shafranovich-privacy-mailbox
draft-shafranovich-privacy-mailbox
Network Working Group Y. Shafranovich
Internet-Draft Nightwatch Cybersecurity
Intended status: Informational May 31, 2018
Expires: December 2, 2018
Common Mailbox Name for Privacy Issues
draft-shafranovich-privacy-mailbox-00
Abstract
Multiple Internet standards describe common mailbox names (mailbox @
domain) to be used by organizations for operational and business
functions. This document defines a new mailbox called "privacy" that
SHOULD be used for contacting domain name owners about privacy
issues.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
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 https://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 December 2, 2018.
Copyright Notice
Copyright (c) 2018 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
(https://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.
Shafranovich Expires December 2, 2018 [Page 1]
Internet-Draft Common Mailbox Name for Privacy Issues May 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Mailbox Definition . . . . . . . . . . . . . . . . . . . . . 2
3. Security considerations . . . . . . . . . . . . . . . . . . . 2
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Normative References . . . . . . . . . . . . . . . . . . . . 3
Appendix A. Note to Readers . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction
Multiple Internet standards describe common mailbox names (mailbox @
domain) to be used by organizations for operational and business
functions. This document defines a new mailbox called "privacy" that
SHOULD be used for contacting domain name owners about privacy
issues.
2. Mailbox Definition
Several mailboxes are defined in section 4 of [RFC2142] that are
intended to be used by outside parties to contact the organization
that own the domain name about specific operational issues. This
document updates section 4 of [RFC2142] with an addition of a new
mailbox that SHOULD be used to contact the domain name owner
regarding privacy issues. Further information regarding privacy
issues in Internet protocols can be found in [RFC6973].
The new mailbox is defined as follows:
+---------+--------------------+-----------------------------+
| MAILBOX | AREA | USAGE |
+---------+--------------------+-----------------------------+
| PRIVACY | Customer Relations | Privacy issues and concerns |
+---------+--------------------+-----------------------------+
Example of a new mailbox:
privacy@example.com
3. Security considerations
Organizations setting up this mailbox should be aware of potential
for spam, malware and other attacks via emails sent to this address.
Shafranovich Expires December 2, 2018 [Page 2]
Internet-Draft Common Mailbox Name for Privacy Issues May 2018
4. IANA Considerations
This document has no IANA actions
However, an IANA registry for common mailbox names may be a good idea
in the future.
5. Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in [RFC2119].
6. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC2142] Crocker, D., "Mailbox Names for Common Services, Roles and
Functions", RFC 2142, DOI 10.17487/RFC2142, May 1997,
<https://www.rfc-editor.org/info/rfc2142>.
[RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
Morris, J., Hansen, M., and R. Smith, "Privacy
Considerations for Internet Protocols", RFC 6973,
DOI 10.17487/RFC6973, July 2013,
<https://www.rfc-editor.org/info/rfc6973>.
Appendix A. Note to Readers
*Note to the RFC Editor:* Please remove this section prior to
publication.
Development of this draft takes place on Github at:
https://github.com/nightwatchcybersecurity/privacy-mailbox
Author's Address
Yakov Shafranovich
Nightwatch Cybersecurity
Email: yakov+ietf@nightwatchcybersecurity.com
Shafranovich Expires December 2, 2018 [Page 3]