idnits 2.17.1 draft-xplorer-device-association-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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 3) being 62 lines == 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 41 instances of too long lines in the document, the longest one being 37 characters in excess of 72. ** There are 12 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 11, 2019) is 1811 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 (~~), 3 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: Nov 11, 2019 May 11, 2019 6 Need for associating Internet Unique names to device address and phone numbers 7 and emails ability to send messages using sms and email 8 draft-xplorer-device-association-02 10 Abstract 12 This document describes the need for associating Internet Unique names to device address 13 and phone numbers and ability to send messages using sms and email 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 Nov 11,2019. 32 Internet-Draft Need for associating Internet Unique names to device address and phone numbers 33 and emails ability to send messages using sms and email Feb 03, 2019 35 Copyright Notice 37 Copyright (c) 2013 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 (http://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 51 1. Introduction ............................................... 2 52 2. Background ..................................................2 53 3. General Information of the service ..........................3 54 4. Authors Addresses ...........................................3 55 5. Acknowledgements ............................................3 57 1. Introduction 59 To implement a standard that can allow an Internet Unique Name to be mapped to a device 60 address and phone number and email addresses 62 2. Background 63 I have to be able to buy an smart phone and associate my unique name that can be used 64 as my email to that device.I should be able to associate my phone number also to that 65 and send and recieve emails. 67 Internet-Draft Need for associating Internet Unique names to device address and phone numbers 68 and emails ability to send messages using sms and email may 11, 2019 70 3. General Information of the service 72 For the user who just want emails and not net savvy, He or she has to be able 73 to walk into a store and get a device like android smart phone and associate his or her 74 Internet unique name with that smart phone. The buyer should also be to map his phone number to unique name. 75 I should be able to type phone number or Unique name in the to field of email or sms and get it delivered 76 to the device that has the phone number or device MAC Address. 78 As an example My Unique name is Pradeep Kumar Xplorer Califorina that i have chosen to use. 79 WHen i buy a device i should be able to map the device MAC address of that device to that Unique 80 name. If it is not available i have to chose a different name. 82 Some one in their sixties or seventies most probably are not internet web savvy. Those who 83 are in other domains professions may also not be internet web savvy.He or 84 she may not want or know how to install an Application like MailDroid and setup Imap 85 settings. They just need to type the Internet Unique name of the person they want to send message 86 to send emails.This prevents hidden cost of signing up for a service provider like gmail.com 87 or hotmail.com and also protects privacy by not having their messages on some remote servers. 89 This increases usability. This with restrictions on functions to a device 90 by using some programming like https://datatracker.ietf.org/doc/draft-pradeep-kumar-xplorer-posvm/ 91 to allow a device to be used only for emails can make emails usable to a wider 92 audience who are not computer savvy. 94 I am victim of a very serious cybercrime as a yoga guide for last 15 years i created and published 95 as self employed in individual capacity a website with some unique intellectual property. I do not know who 96 is accessing my website. I added some software scripts to print the IP address and location of 97 the viewers of my website. The crime is that some others know who my website viewers are lying 98 about me and running an organisation company in black by contacting them. These are the logs 99 http://www.pradeepkumarxplorer.com/2016/vieweremails.txt 100 Instead of IP address if i get the device MAC or Unique name then i can send them an email 101 and have a channel to communicate to them directly. 103 When i purchase a smart phone or computer i should be able to associate my Device MAP to my 104 Unique name in some internet databases. This is just a matter of software implementation. 105 To communicate to a willing recipient who can send messages back i just need the 106 Internet Unique name of that person. 108 I am victim of being forced to use facebook one decade and i have developed really no 109 frendships. Even now the same status quo continues. I have been prevented from being 110 in California where i used to meet and be with community in yoga studios and hotsprings 111 and other places and forced to use facebook and has been used as a Guinea pig and they have 112 probably used my money also. 114 I propose an email for any phone number or device mac. SO to email +91.6238940417 you 115 have to send email to +91.6238940417@phoneemail.com or to send email to devicemacaddr 116 you have to send email to devicemacaddr@phoneemail.com. 118 4.Authors' Addresses 120 Pradeep Kumar Xplorer 121 EMail: pradeepan88@hotmail.com 122 URI: http://www.pradeepkumarxplorer.com 124 5.Acknowledgement 126 Internet-Draft Need for associating Internet Unique names to device address and phone numbers 127 and emails ability to send messages using sms and email may 11, 2019