Search results
Jump to navigation
Jump to search
Page title matches
- ...net, as well as knowledge exchange among developers, takes place in the '''Internet Engineering Task Force'''. For historical reasons, the major technical publications are called [[R6 KB (843 words) - 03:23, 14 February 2010
- 101 bytes (12 words) - 07:41, 22 October 2010
- Auto-populated based on [[Special:WhatLinksHere/Internet Engineering Task Force]]. Needs checking by a human.1 KB (167 words) - 14:59, 20 March 2024
Page text matches
- === From IETF (Internet Engineering Task Force) ===949 bytes (121 words) - 20:10, 11 February 2010
- #REDIRECT [[Internet Engineering Task Force]]45 bytes (5 words) - 15:26, 6 June 2008
- {{r|Internet Engineering Task Force}}761 bytes (100 words) - 09:48, 22 October 2010
- ...ation protocol (LISP)''' is an experimental networking protocol in the [[Internet Engineering Task Force]] draft stage.<ref>{{citation | publisher = [[Internet Engineering Task Force]]946 bytes (126 words) - 13:53, 25 March 2011
- {{r|Internet Engineering Task Force}}262 bytes (38 words) - 21:53, 30 June 2009
- {{r|Internet Engineering Task Force}}352 bytes (42 words) - 14:59, 20 March 2024
- {{r|Internet Engineering Task Force}}924 bytes (116 words) - 18:42, 11 January 2010
- {{r|Internet Engineering Task Force}}932 bytes (116 words) - 11:20, 9 December 2009
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force4 KB (596 words) - 16:23, 30 March 2024
- Auto-populated based on [[Special:WhatLinksHere/Internet Engineering Task Force]]. Needs checking by a human.1 KB (167 words) - 14:59, 20 March 2024
- | url = http://www.ietf.org/rfc/rfc3918.txt}}</ref> In 2004, the [[Internet Engineering Task Force]] (IETF) IPFIX project <ref name=IPFIX>{{citation | publisher = Internet Engineering Task Force}}</ref> analyzed methods,<ref name=RFC3955>{{citation2 KB (315 words) - 21:33, 22 February 2009
- {{r|Internet Engineering Task Force}}567 bytes (82 words) - 22:33, 25 March 2011
- {{r|Internet Engineering Task Force}}575 bytes (71 words) - 19:12, 11 January 2010
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force3 KB (426 words) - 15:00, 20 March 2024
- ...ET)''' is a family of technologies, and a technical Working Group of the [[Internet Engineering Task Force]].<ref>{{citation | author = Internet Engineering Task Force}}</ref> MANET applications include the [[Automatic identification system]]2 KB (316 words) - 14:34, 27 August 2008
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force2 KB (310 words) - 15:00, 20 March 2024
- While the [[Internet Engineering Task Force]] develops the technical specifications for the networking [[protocol (comp2 KB (290 words) - 22:50, 5 October 2008
- A product of the [[Internet Engineering Task Force]] (IETF) [[Internet Protocol version 6]] Operations Working Group (v6ops),942 bytes (133 words) - 18:03, 25 March 2011
- | publisher = Internet Engineering Task Force931 bytes (125 words) - 14:40, 16 January 2010
- | publisher = Internet Engineering Task Force}}</ref> The device that performs these functions is called a [[router]].<r | publisher = Internet Engineering Task Force3 KB (398 words) - 12:35, 30 March 2024
- | publisher = [[Internet Engineering Task Force]]1 KB (164 words) - 19:17, 2 October 2010
- | publisher = [[Internet Engineering Task Force]] | publisher = [[Internet Engineering Task Force]]4 KB (587 words) - 14:57, 20 March 2024
- ..."The Standard for Collaborative Authoring on the World Wide Web" by the [[Internet Engineering Task Force]]. <ref>http://ftp.ics.uci.edu/pub/ietf/webdav/intro/webdav_intro.pdf</ref>831 bytes (109 words) - 04:14, 14 September 2013
- While other groups, such as the [[Internet Engineering Task Force]] (IETF) designs complex internetworking mechanisms such as the Border Gate3 KB (368 words) - 15:00, 20 March 2024
- | publisher = [[Internet Engineering Task Force]]}}</ref> | publisher = [[Internet Engineering Task Force]]}}</ref>3 KB (383 words) - 05:48, 8 April 2024
- While other groups, such as the [[Internet Engineering Task Force]] (IETF) designs complex internetworking mechanisms such as the Border Gate2 KB (259 words) - 15:00, 20 March 2024
- ...setup, as distinct from data transfer. It is a Proposed Standard in the [[Internet Engineering Task Force]] standards track. <ref name=RFC2205>{{citation2 KB (257 words) - 13:50, 15 August 2008
- Of these protocols, the first three are open standards from the [[Internet Engineering Task Force]], while EIGRP is a proprietary protocol of [[Cisco Systems]].916 bytes (131 words) - 22:12, 6 February 2010
- ...he [[ARPANET]], was just being started). The RFC process arose from the [[Internet Engineering Task Force]] (IETF)<ref name="IETF">{{cite web|url=http://www.garykessler.net/library/ | publisher = Internet Engineering Task Force5 KB (796 words) - 14:09, 8 December 2022
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force5 KB (740 words) - 16:23, 30 March 2024
- In the [[Internet Engineering Task Force]], enabling technologies for self-organizing networks are in the Mobile Ad1 KB (160 words) - 12:12, 1 May 2024
- ...LS information that is used to refine the routing table computation. The [[Internet Engineering Task Force]] (IETF) intends to keep the functionality, if not the syntax, of this addi2 KB (351 words) - 18:23, 10 February 2011
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force4 KB (548 words) - 19:32, 31 January 2009
- | date = November 1996 | publisher = Internet Engineering Task Force}}</ref>1 KB (162 words) - 15:00, 20 March 2024
- {{r|Internet Engineering Task Force}}1 KB (185 words) - 21:09, 22 September 2010
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force8 KB (1,172 words) - 16:22, 30 March 2024
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force8 KB (1,226 words) - 12:37, 30 March 2024
- | url = http://www.ietf.org/rfc/rfc5246.txt}}</ref>, by the [[Internet Engineering Task Force]]. TLS is a derivative of SSL.1 KB (210 words) - 05:49, 8 April 2024
- | publisher = Internet Engineering Task Force2 KB (365 words) - 20:36, 16 May 2009
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force7 KB (1,057 words) - 05:18, 31 May 2009
- | publisher = Internet Engineering Task Force3 KB (431 words) - 15:32, 23 August 2008
- According to the [[W3C Consortium]] and the [[Internet Engineering Task Force]], a '''safe''' transaction takes no action other than reading a file, webp | publisher = Internet Engineering Task Force5 KB (784 words) - 11:58, 22 July 2008
- *[[Open Shortest Path First]] (OSPF), an [[Internet Engineering Task Force]] (IETF) protocol, which supports hierarchy and primarily uses [[link state4 KB (647 words) - 15:00, 20 March 2024
- According to the [[Internet Engineering Task Force]] specification for such certificates, they are data structures that bind p2 KB (365 words) - 05:49, 8 April 2024
- .... It is absolutely necessary that, for a given protocol developed by the [[Internet Engineering Task Force]], the internal identifiers of that protocol be unique. The IETF issues sta5 KB (784 words) - 10:53, 2 April 2024
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force13 KB (1,980 words) - 16:23, 30 March 2024
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force6 KB (985 words) - 12:34, 30 March 2024
- ...ayer, but below it, although they may take information from it. When the [[Internet Engineering Task Force]] was dealing with MPLS and some other things that "don't quite fit", and s2 KB (316 words) - 11:40, 10 February 2011
- ...net, as well as knowledge exchange among developers, takes place in the '''Internet Engineering Task Force'''. For historical reasons, the major technical publications are called [[R6 KB (843 words) - 03:23, 14 February 2010
- | publisher = [[Internet Engineering Task Force]]}}</ref>3 KB (387 words) - 15:56, 14 March 2010
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force15 KB (2,421 words) - 05:49, 8 April 2024
- ...and much more informal, networking reference model is that defined by the Internet Engineering Task Force. As a result of the academic and industry emphasis on teaching the now-obso ==Internet Engineering Task Force reference model and protocol development==18 KB (2,694 words) - 16:22, 30 March 2024
- ...|url=http://www.ietf.org/rfc/rfc1958.txt |date=June 1996 |work= |publisher=Internet Engineering Task Force |accessdate=Sept. 17, 2009}}</ref>. Internet architectural experts deprecat ...rl=http://tools.ietf.org/html/rfc1812 |date=Dec. 1, 2006 |work= |publisher=Internet Engineering Task Force |accessdate=Sept. 17, 2009}}</ref>. Each protocol layer utilizes the servic14 KB (2,021 words) - 17:02, 22 March 2024
- '''Session Initiation Protocol (SIP)''' was developed by the [[Internet Engineering Task Force]] Session as part of the infrastructure for user-visible functions such as4 KB (599 words) - 14:29, 8 May 2010
- Developed by the [[Internet Engineering Task Force]], the '''Routing Policy Specification Language (RPSL)''' is a means of des6 KB (945 words) - 15:00, 20 March 2024
- ...rior routing policies, except that doing so was outside the charter of the Internet Engineering Task Force (IETF) working group that created the language. For example, it would be a6 KB (946 words) - 16:24, 30 March 2024
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force26 KB (4,062 words) - 15:00, 20 March 2024
- In the [[Internet Engineering Task Force]], the Application-Layer Traffic Optimization (alto) Working Group has been | publisher = [[Internet Engineering Task Force]]}}</ref></blockquote>9 KB (1,351 words) - 14:13, 6 April 2024
- ...s well as the [[ARPANET]], [[NSFNET]], and other research arose from the [[Internet Engineering Task Force]] (originally the ''Network Working Group'') (IETF)<ref name="IETF">{{cite9 KB (1,333 words) - 10:08, 28 February 2024
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force24 KB (3,628 words) - 21:04, 17 April 2014
- ...and the architectural principles supporting them, that are defined by the Internet Engineering Task Force (IETF) in Request for Comments (RFC) specifications. It must be understood ...ols, if the experiments are successful, may enter the standards track. See Internet Engineering Task Force (IETF) for a discussion of its standards process.16 KB (2,394 words) - 07:30, 18 March 2024
- | author = Internet Engineering Task Force}}</ref> The automatic identification system (AIS), a means of improving saf5 KB (799 words) - 16:23, 30 March 2024
- In the Internet Engineering Task Force, two working groups in the Operations & Maintenance Area deal with aspects10 KB (1,511 words) - 07:30, 18 March 2024
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force38 KB (6,049 words) - 06:54, 27 August 2013
- | publisher = Internet Engineering Task Force | publisher = Internet Engineering Task Force38 KB (6,053 words) - 12:06, 30 March 2024
- | publisher = Internet Engineering Task Force9 KB (1,432 words) - 15:01, 20 March 2024
- ...ivision Multiple Access]] (SOTDMA) technology, is an example of what the [[Internet Engineering Task Force]] terms [[mobile ad hoc networking]] (MANET).6 KB (862 words) - 07:23, 24 August 2010
- | date = August 1998 | publisher = [[Internet Engineering Task Force]]10 KB (1,519 words) - 20:08, 10 June 2010
- | publisher = Internet Engineering Task Force13 KB (2,000 words) - 16:21, 30 March 2024
- ...-IS and EIGRP all can be considered third-generation. In particular, the [[Internet Engineering Task Force]] (IETF), while as neutral as standards bodies can get, had a number of ven23 KB (3,713 words) - 12:20, 30 March 2024
- ...internet movement. In the words of Dave Clark, a prominent member of the [[Internet Engineering Task Force]] (IETF), "We [as internet and web technologists] reject: kings, presidents34 KB (5,092 words) - 04:24, 12 October 2012
- ...'Site Multihoming by IPv6 Intermediation (SHIM6)''' Working Group of the [[Internet Engineering Task Force]] has been charged with39 KB (5,823 words) - 12:18, 30 March 2024
- ...engineering, there can be a very vigorous peer review process, as in the [[Internet Engineering Task Force]], but it is not a classical journal process, but one adapted to electronic ...pplied sciences, there are thorough peer review mechanisms -- I cite the [[Internet Engineering Task Force]] -- that again don't have quite the desire for stating alternate views, al56 KB (8,977 words) - 15:00, 20 March 2024
- ::::I would suggest looking at major professional mailing lists, such as the Internet Engineering Task Force or North American Network Operators' Group. No one minds if there's a quic33 KB (5,693 words) - 10:45, 7 March 2024
- I can speak from quite a number of years of experience with the Internet Engineering Task Force, which has a well-organized structure of Workgroups, an intermediate tier o216 KB (35,266 words) - 10:45, 7 March 2024