Talk:Time to live
|WikiProject Computing||(Rated Start-class)|
|To-do list for Time to live:|
That first sentence is very awkward. Yeah, I know it parses correctly, but can someone make it more readable? Also, is it pronounced "live" as in "Liver" or "live" as in "Alive"? ThreeRocks (talk) 21:53, 12 May 2011 (UTC)
pakistan and inaccessible encyclopedia article. Don't rely so heavily on jargon and at least hyperlink those terms you will not define. —Preceding unsigned comment added by 22.214.171.124 (talk) 05:24, 7 March 2008 (UTC)
a "stub resolver"... this article is somewhat helpfull, but i have no idea what a stub resolver is, so it should be either explained further here or a hyerlink to some other article.
also, it is well known that routers reduce the TTL by on. However, do hubs, switches, bridges, and more importantly repeaters have any effect on the TTL? —Preceding unsigned comment added by 126.96.36.199 (talk) 00:49, 18 January 2008 (UTC)
- Hubs, switches, bridges and repeaters generally do not have any effect on TTL, because they operate in Layer 1 and/or Layer 2 (of the OSI Model) while TTL is a Layer 3 concept. However 'switch' became a marketing term some time ago, so for example a so-called Layer 3 switch may implement routing features, and be essentially a routing device. Rubasov (talk) 22:40, 24 March 2009 (UTC)
I've removed the table in the "Time to live of IP datagrams" section for the following reasons:
- The TTL field in the IP header is never used in this way. It could never be used in this way, because network topology is a very uncertain factor, and varying all the time. The TTL field is only there to keep stray data packets from surviving.
- The hop counts in the table are way to high, even the remotest outskirts of the internet can be reached in 30 or 35 hops.
Modern operating systems set the initial TTL field to a fixed value.
I've pasted the text I removed below. Jaho 21:53, 17 March 2007 (UTC)
The arbitrary values below represent how long the packet should live with respect to the given TTL value. The numbers are a rough estimate and are dependent on the number of routers in your network.
- 0 is restricted to the same host
- 1 is restricted to the same subnet
- 32 is restricted to the same site
- 64 is restricted to the same region
- 128 is restricted to the same continent
- 255 is unrestricted
- You removed not just the table but the whole section discussing TTL in IP. I assume this was unintentional and so I've put that back. --Kvng (talk) 23:25, 4 February 2009 (UTC)
Internet Protocol Introduction
The Time to Live is an indication of an upper bound on the lifetime of an internet datagram. It is set by the sender of the datagram and reduced at the points along the route where it is processed. If the time to live reaches zero before the internet datagram reaches its destination, the internet datagram is destroyed. The time to live can be thought of as a self destruct time limit. — Preceding unsigned comment added by 188.8.131.52 (talk) 12:13, 31 July 2012 (UTC)
Georgeh109 (talk · contribs) added an example. I am concerned about WP:HOWTO and WP:OR. I'm not convinced the example is necessary. I am concerned about WP:BITE so have improved formatting and invite editors to discuss this contribution here. -—Kvng 17:34, 24 December 2012 (UTC)
DNS records as a citable source for wikipedia articles
Wikipedia policy on citing sources for material in articles varies, for example, an obscure romantic fiction novel may be cited, or a newspaper article, but the UK`s Daily Mail is not allowed; Is it ok to cite DNS record(s), changes made to DNS records, changes made to TTL, etc, etc? i.e. If I wrote something like, "On the 11th November `11, the registrant of website-X was not (fictional) Sigismunder Reynisson, but on the 22nd of November `11 the registrant was the fictional Sigismunder Reynisson.The Registrar of Record of website-X made changes to the DNS records", if the DNS records cited are correct, that`s a certified source to cite, isn`t it? Can I cite these sources? CHeers184.108.40.206 (talk) 16:09, 18 October 2017 (UTC)
- DNS Records
- changes logged on DNS record