idnits 2.17.1 draft-httpemaildevphone-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: ---------------------------------------------------------------------------- ~~ Missing draftname component: the document name given in the document, 'draft-httpemaildevphone-00', 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 14 instances of too long lines in the document, the longest one being 42 characters in excess of 72. ** There are 6 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 (Dec 13, 2018) is 1958 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 INT Pradeep Kumar Xplorer 2 Internet-Draft Ex-Sun Employee 3 Intended status: Standards Track Individual 4 Expires: May 13, 2019 Dec 13, 2018 6 Need for associating email address to device address and phone numbers 7 draft-httpemaildevphone-00 9 Abstract 11 This document describes the need for associating email address to device address 12 and phone numbers 14 Status of This Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF). Note that other groups may also distribute 21 working documents as Internet-Drafts. The list of current Internet- 22 Drafts is at http://datatracker.ietf.org/drafts/current/. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 This Internet-Draft will expire on May 13,2019. 31 Copyright Notice 33 Copyright (c) 2013 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (http://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 Table of Contents 47 1. Introduction ............................................... 2 48 2. Background ..................................................2 49 3. General Information of the service ..........................3 50 4. Authors Addresses ...........................................3 51 5. Acknowledgements ............................................3 53 1. Introduction 55 To implement a standard that can allow an email address to be mapped to a device 56 address and phone number 58 2. Background 59 I have to be able to buy an android and get an email address also from 60 that vendor. I should be able to associate my phone number also to that 61 and send and recieve emails. 63 3. General Information of the service 65 For the user who just want emails and not net savvy, He or she has to be able 66 to walk into a store and get a device like android and get an email address also from 67 that vendor. The buyer should also be to map his phone number to email address. 68 I should be able to type phone number or even the device MAC address in the to field of email and get it delivered 69 to the device that has the phone number or device MAC Address. 71 This increases usability. This with restrictions on functions to a device 72 by using some programming like https://datatracker.ietf.org/doc/draft-pradeep-kumar-xplorer-posvm/ 73 to allow a device to be used only for emails can make emails usable to a wider 74 audience who are not computer savvy. 76 4.Authors' Addresses 78 Pradeep Kumar Xplorer 79 EMail: pradeepan88@hotmail.com 80 URI: http://www.pradeepkumarxplorer.com 82 5.Acknowledgement