About site: Internet/RFCs/0501 - 0600 - RFC 0513
Return to Computers also Computers
  About site: http://www.faqs.org/rfcs/rfc513.html

Title: Internet/RFCs/0501 - 0600 - RFC 0513 Comments on the New Telnet Specifications. W. Hathaway. May 1973.
ClickRight_net_Corporate_Portal ClickRight.net offers applications to extend your existing intranet portal, or build an entire corporate portal site.

Kyren_Web Here you can visit Web Heaven, HellBound and Lairs representing all the sides of Nature. Each section has different resources to help you to design your pages.

Sigma_Seven_Systems_Ltd_ An engineering and manufacturing company that specializes in Apple Macintosh technology. Still sells some Lisa accessories.

baseSim A Borland Delphi based set of Simulation based components, standalone applications and 3rd party plug-ins. [Freeware, req. registration]

RFC_1693 An Extension to TCP : Partial Order Service. T. Connolly, P. Amer, P. Conrad. November 1994.

Rails_Cookbook By Rob Orsini; O'Reilly Media, 2007, ISBN 9780596527310. From basics (install Rails, set up development environment), to latest techniques (developing RESTful web services). Each recipe has tested sol

  Alexa statistic for http://www.faqs.org/rfcs/rfc513.html





Get your Google PageRank






Please visit: http://www.faqs.org/rfcs/rfc513.html
  Related sites for http://www.faqs.org/rfcs/rfc513.html
    Art_and_Design_of_Hayes_Raffle Art and Design of Hayes Raffle. Product and Graphic design. Sculpture, prints and photography focusing on the confluence of electronic technologies and culture.
    HexEdit A Macintosh hexadecimal file editor that handles both data and resource forks.
    Impreza_Computer_Services_Ltd A flexible and customizable Customer Relationship Management (CRM) and Contact Management System (CMS) software package transforming MS Exchange Server and Outlook into a business solution.
    Savano,_Inc_ Web-based contact management, reporting, Sales Force Automation (SFA) and Customer Relationship Management (CRM) software for medical and healthcare industries and equipment provide integration with b
    Free_Web_Counter Traffic counter that is free to use for any site.
    Sharoiko,_Oleg C/C++, UNIX, Perl, TCP/IP, DataBases programmer.
    Heroes_of_Might_and_Magic_2 Epic struggle between good and evil.
    eJaz Tools for general usage developer. Visual XCopy, IHA - ClassInfo (extract classes information from in .cpp/.pas/.html/.java files), dbAdmin programs.
    Australian_Interactive_Multimedia Supplier of scanners and printers from barcode to flatbed. Features reviews of many products. [Australia]
    Edocs,_Inc_ Developer of electronic bill presentment and payment software.
    Innova_Consulting_Company Effectively implemented and used, R/3 can provide truly integrated business processes and timely access to information throughout a company.
    ScanAlert Vulnerability testing and security verification. Provides real-time independent verification of a Web site's security.
    Wallpaper_Desktop Design creative wallpaper; generate colorful, creative, patterns. Use multiple images, send composition to the desktop or saved as a JPG-BMP or GIF file. A timer is present to change the background pe
    Win32_Assembly_Programming_Using_RosAsm Various Win32 assembly programs available.
    PACT_2000 International Conference on Parallel Architectures and Compilation Techniques. Philadelphia, Pennsylvania.
    Rasmussen,_Carl_Edward Gaussian processes, non-linear Bayesian inference, evaluation and comparison of network models.
    VietIMEW Provides an input method editor to convert chars from latin alphabet to vietnamese.
    Authentic_Designs_Etc_ Custom design and, database driven e-commerce sites, animation, domain registration, and site maintenance.
    Hud-1_Online Simplify the tedious task of completing real estate closing statements. The software enables you to quickly and easily complete the following forms in pdf format:
    TotalView_Technologies Developer of Totalview, a tool which aids in the development of multithreaded, multiprocess and network-distributed applications.
This is websites2007.org cache of m/ as retrieved on 2008.10.15 websites2007.org's cache is the snapshot that we took of the page as we crawled the web. The page may have changed since that time.
RFC 513 (rfc513) - Comments on the new Telnet specifications@import 'http://faqs.org/abstracts/css/default.css';@import 'http://faqs.org/search.css';function erfc(s){document.write("[ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ]Alternate Formats: rfc513.txt | rfc513.txt.pdfRFC 513 - Comments on the new Telnet specificationsSearch the Archives Display RFC by number     

RFC513 - Comments on the new Telnet specifications

Network Working Group Wayne HathawayRFC # 513 AMES-67NIC # 16444 30 May 1973 COMMENTS ON THE NEW TELNET SPECIFICATIONSI would like to make the following comments on the proposed new TELNETProtocol Specification (NIC # 15372) and TELNET Option Specification(NIC 15373). In general I feel the new TELNET protocol is far superiorto the previous version. There are, however, a few items of substancewhich I feel should be changed, as well as some recommended editorialchanges.I feel the most significant error concerns the "Note on 'Sub-negotiations'" section of the Option Specification (page 2). Theproblem stems from the statements "Each party is presumed to be able toparse the parameter(s)" and "Finally, if parameters in an option'subnegotiation' include a byte with a value of 255, it is not necessaryto double this byte in accordance with the general TELNET IAC." Thesetwo statements make the completely unwarranted but all too prevalentassumption that there is only one "Telnet Interpreter" and that allTELNET functions are carried out by it. In particular, problems arisewhen a TELNET "synch" is received, and the receiving NCP is required toscan the input looking for "interesting" things. If the subnegotiationwas in fact being carried out by a user process (and not the "TELNETinterpreter") then that user process is probably the only one that knowshow to interpret the SB parameters; the NCP itself would have no way ofparsing them. As a solution to this problem I propose that allsubnegotiation parameters be delimited at the end (perhaps with the sameTELNET command SB) and that they be required to obey all TELNET rules,including doubling of IAC's. It may be argued that the user processinterpreting the SB itself should do the scanning for "interesting"things, but I do not feel that this burden should be place on all userprocesses.The solution to the above problem is in fact fairly simple to define andimplement. The general problem, however, is one of not taking propercognizance of what I called "user processes" (processes which are notnetwork standards, but which are simply programs attempting to do workusing the network). I feel we must be more careful to shape all futurenetwork standards with these very real user processes in mind if in factthe network will ever be as useful as is possible.The second item I object to is the incredibly loose definition of"interesting" things (an aside: words which are so imprecise as torequire quotation marks should never appear in protocol specifications).The specifications do define some of these "interesting" things (eg,most TELNET commands) but they then include "and perhaps othercharacters or character strings as well". To eliminate the difficultyof implementing an undefined set of "interesting" things, I wouldpropose that the set of "interesting" things, contain only the DMcommand itself. The TELNET "synch" would thus be defined as "discardall input up to and including the next DM command." This change shouldcause no problems with user-generated "interesting" things if they aresent after the "synch" (as specified in the proposed new File TransferProtocol Specifications). System-generated signals (such as optionrequests) could be discarded, however, so some additional discussion isin order. If the recommendation that requests not be sent except whensomething changes is followed, the spontaneous generation of"interesting" things by TELNET itself (whatever that implies) would seemto be rare, especially at the same time that users are generating"synch's". A more positive solution could be had by defining a "synchresponse" (SR) TELNET command. The SR command would be sent when theINS and DM had both been processed (ie, when the "synch" had beencompletely received). If a process should ever receive an SR when ithas an option request outstanding, the request has been discarded andmust be repeated. User processes which carry on option negotiationswould be the generators of any "synch's" so they can handle discardedoption requests as desired. Note that this assumes that the TELNETprocess itself will never generate a spontaneous "synch"; comments aresolicited on this. Another possible solution would be to define a"TIMING-MARK" TELNET command (see "TELNET Timing Mark Option", NIC #16238), which would be sent immediately following the DM of a "synch".The response to the TIMING-MARK (also to be defined) would mean the sameas the proposed SR command.The final non-editorial comment concerns the need for some means ofspecifying horizontal tab positions and use. This is quite a nuisancewhen dealing with systems which normally handle tabs for localterminals. Perhaps this issue can be best handled with an appropriateoption; comments are solicited.The only editorial comments are on the TELNET Protocol document, which Ireference below by page number.On page 8 the parenthetical comment "(i.e., when a process at one end ofa TELNET connection is 'blocked on input')" should either be removed orrewritten to avoid the (to me) incomprehensible phrase "blocked oninput." If additional discussion is felt to be necessary, I wouldpropose "i.e., when a process at one end of a TELNET connection cannotproceed without additional input)." If examples are felt necessary, Iwould propose "(e.g., in the state characterized by the Multics term'blocked on input')." The parallel could also be drawn between the GAand the concept of a "read command" being issued to request more input.On page 10 I feel that there needs to be some more discussion of theAbort Output (AO) command, particularly the statement that it "allows aprocess... to run to completion... but without sending the output to theuser's terminal." The problem is that nothing is said about when outputis to resume (presumably at the next system prompt character). Irealized that the AO is meant only to invoke this function on systemswhich already provide it, but it would seem to be more useful if morefully specified.On page 11 I do not understand what the example "(e.g., an over-strike)"is trying to say. Speaking of an overstrike on output would imply to methat both characters are to be printed in the same print position,reducing the EC to a backspace. Some more discussion should also beadded as to what EC (and EL) mean on output (if anything).On page 11 I would like to see the word "promptly" (which is inquotation marks) either eliminated or defined, as per my earlier asidecomment. The phrase "if necessary" in the last line also seemsunnecessary.On page 12 my proposed redefinition of "interesting" signals wouldremove the middle paragraph entirely and would modify the thirdparagraph substantially. The line "discard all characters which wouldhave had an effect on the NVT printer" should be changed, however, as itseems BELL's should also be discarded.On page 14 I see no reason why the sequence "CR NUL" is required togenerate a "CR" only, and also object to "and the CR character must beavoided in other contexts." Either some supporting discussion should beadded or this restriction should be removed. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Alex McKenzie with ] [ support from GTE, formerly BBN Corp. 9/99 ] Previous: RFC 0512 - More on lost message detection Next: RFC 0514 - Network make-work [ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ] © 2008 FAQS.ORG. All rights reserved. 
 

Comments

on

the

New

Telnet

Specifications.

W.

Hathaway.

May

1973.

http://www.faqs.org/rfcs/rfc513.html

RFC 0513 2008 October

dvd rental

dvd


Comments on the New Telnet Specifications. W. Hathaway. May 1973.

Rules

© 2008 Internet Explorer 5+ or Netscape 6+
Recommended Sites: 1. Arts - Business - Computers - Games - Health - Home - Kids and Teens - News - Recreation - Reference - Regional - Science - Shopping - Society - Sports - World Miss Gallery - Top Anime Hentai - DVD rental by mail - Remortgages - Xbox Mod Chip - Credit Cards - Cheap Car Insurance - Internet Advertising
2008-10-15 18:53:09

Copyright 2005, 2006 by Webmaster
Websites is cool :) 119Agencja Reklamowa - Druk Wielkoformatowy - Pozycjonowanie Stron - Centrum Handlowe - Horses For Sale