idnits 2.17.1 draft-httpi-12.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-httpi-12', 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 13 instances of too long lines in the document, the longest one being 12 characters in excess of 72. ** There are 5 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 (Jul 16, 2018) is 2110 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 HTTP Pradeep Kumar Xplorer 2 Internet-Draft Ex-Sun Employee 3 Intended status: Standards Track Individual 4 Expires: Jan 16, 2019 Jul 16, 2018 6 Need for an httpi intelligent service 7 draft-httpi-12 9 Abstract 11 This document describes the need for an httpi protocol similar to 12 https/http used for intelligent surfing of information. 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 Jan 16,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 an httpi:// service in browser similar to https/http 57 2. Background 58 Right now URL's are hardcoded. I propose an httpi:// service 59 that would allow dynamic links that can be updated by the httpi 60 service in the text that you are viewing. So every time interval like 61 a minute or so, the content you are viewing using the httpi:// service 62 in your browser can show links suggested by the WWW Brain 63 that you can traverse or navigate 65 3. General Information of the service 67 Having a parallel browser realm, that allows intelligent updates of 68 navigatable links from WWW intelligent computing realm. Instead of using 69 http:// you just need to type httpi:// in your URL and the texts you view 70 would have in addition to hardcoded navigatable links also those suggested by 71 the WWW brain. The URL's hardcoded in HTML would have the blue color and those 72 suggested by the WWW Brain would have a different color. 74 If i launch and type httpi://www.site.info , it would be showing navigatable 75 links that are not created manually in addition to that are created 76 manually. The WWW brain would suggest additional navigatable links. 78 If i publish a site with no hardcoded URL URI's and if i view the site 79 it would still show navigatable links.The navigatible links would chnage 80 depending on whats available in the WWW. 82 4.Authors' Addresses 84 Pradeep Kumar Xplorer 85 EMail: pradeepan88@hotmail.com 86 URI: http://www.pradeepkumarxplorer.com 88 5.Acknowledgement