|
| |
| | Internet Engineering Task Force - Wikipedia, the free encyclopedia |
 | | The IETF is overseen by the Internet Architecture Board (IAB), which oversees its external relationships, and relations with the RFC Editor. | | | The IAB also manages the Internet Research Task Force (IRTF), with which the IETF has a number of cross-group relations. | | | The majority of the IETF's work is done on mailing lists, however, and meeting attendance is not required for contributors. |
|
http://en.wikipedia.org/wiki/Internet_Engineering_Task_Force
|
|
| |
| | All About The Internet: Standards |
| | IETF specifications usually attempt to solve specific, immediate problems, rather than to encompass a wide-range of long-term goals. | | | In fact, the IETF is not very successful at fixing working groups that make the mistake of walking down the seductive path of long-term, general design. | | | It is another example of the ways in which the IETF work is highly accessible to the broadest audience, permitting better analysis and broader use. |
|
http://www.isoc.org/internet/standards/papers/crocker-on-standards.shtml
|
|
| |
| | OpenStandards.net - Organizations |
| | The IETF is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. | | | In general, the IETF, based on the 1996 publication of RFC 2026, permits Reasonable and Non-Discriminatory (RAND) access to the intellectual property required to implement a standard. | | | "The IETF is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. |
|
http://www.openstandards.net/viewOSnet2C.jsp?showModuleName=Organizations&mode=1&acronym=IETF
|
|
| |
| | RFC 1603 (rfc1603) - IETF Working Group Guidelines and Procedures |
| | The IETF is a large, open community of network designers, operators, vendors, users, and researchers concerned with the Internet and the technology used on it. | | | Request For Comments (RFC) The work of an IETF working group usually results in publication of one or more documents, as part of the Request For Comments (RFCs) [2] series. | | | Abstract The Internet Engineering Task Force (IETF) has responsibility for developing and reviewing specifications intended as Internet Standards. |
|
http://www.faqs.org/rfcs/rfc1603.html
|
|
| |
| | What is IETF? - A Word Definition From the Webopedia Computer Dictionary |
| | The IETF is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. | | | Describes the IETF benchmarking methodology working group and includes contact and mailing list information and links to Internet drafts and Request for Comments documents. | | | Describes the IETF Open Network Computing (ONC) Remote Procedure Call working group and provides contact and mailing list information, and links to Internet drafts and Request for Comments documents. |
|
http://www.webopedia.com/TERM/R/IETF.html
|
|
| |
| | All About ISOC: Related Organizations - IETF and ISOC Relationship by Vint Cerf |
| | Regardless of the outcome, I believe that the ISOC should continue to provide support for the IETF where possible because of the importance of its work to the continued well-being of the Internet. | | | At the June 1995 ISOC Board of Trustees meeting, the trustees confirmed that the highest ISOC goal was to "keep the Internet going." It was agreed that among the high priority activities associated with that goal was to provide support for the Internet Standards process carried out by the Internet Engineering Task Force. | | | RFC 1602 is the current version of this document). |
|
http://www.isoc.org/isoc/related/ietf
|
|
| |
| | IP Version 6 (IPv6) |
| | The Next Generation Transition working group in the IETF is responsible for designing the mechanisms and procedures to support the transition of the Internet from IPv4 to IPv6. | | | Internet Protocol Version 6 is abbreviated to IPv6 (where the "6" refers to it being assigned version number 6). | | | A complete overview of IPv6 and the motivations behind it can be found in the IPng Overview. |
|
http://playground.sun.com/pub/ipng/html/ipng-main.html
|
|
| |
| | Internet Engineering Task Force (IETF) |
| | IETF protocols are accessible from the descriptions of the Area and Working Groups (above) or via the Internet Drafts index or RFC index. | | | An OMG document for which OMG retains revision control can be published in IETF as an Informational RFC as a way to inform IETF about OMG documents and get a community critique. | | | But this is only worth doing if OMG wants a community review of its specifications from the IETF community and is willing to consider consequent proposed revisions. |
|
http://www.objs.com/survey/ietf.htm
|
|
| |
| | IETF - Hypertext Transfer Protocol (HTTP) Working Group |
| | This document suggests some possible areas for extending the IETF 'conneg' working group's capability description framework, described in [2,3,4]. | | | In 'A syntax for describing media feature sets', an expression format is presented for describing media feature capabilities using simple media feature tags. | | | This document also outlines an algorithm for feature set matching. |
|
http://www.ics.uci.edu/pub/ietf/http
|
|
| |
| | Current DNS standards activity |
| | Internet-Drafts are the working documents of the Internet Engineering Task Force (IETF). | | | Update of RFC 2916 to bring it in line with the Dynamic Delegation Discovery System. | | | Most RFCs started life as Internet-Drafts, but many Internet-Drafts never make it to RFC status. |
|
http://www.dns.net/dnsrd/docs/id.html
|
|
| |
| | Re: Draft: IETF listing of open source implementations of IETF specs |
| | Dave Crocker wrote: > The IETF process does not require development of a 'reference' > implementation, but their creation is often a major > contribution to > development of support and success for our standards. | | | It would be centeral point for all acheiving/ trees to bemaintained.... | | | Prev: Re: Official listing of "public" reference software for IETF specs |
|
http://www.cctec.com/maillists/ietf/msg05679.html
|
|
| |
| | Wireless LAN Security Site |
| | Liaison to IETF from IEEE 802.11 and IEEE 802.21 (May 2005) | | | Here are the references to the security analyses of VPN protocols as well as to the IETF standards for VPN. | | | Roaming, defined as the ability to connect to multiple ISPs while maintaining an account with only one, was tackled by the IETF ROAMOPS WG starting in 1996 and solutions based on this architecture are now widely deployed. |
|
http://www.drizzle.com/~aboba/IEEE
|
|
| |
| | Cover Pages: Atom Publishing Format and Protocol |
| | Over the course of the past year, the IETF Atom Publishing Format and Protocol Working Group has been working to define a standard XML format designed, in part, to allow clients to receive notification of when Web-based resources have been created or modified. | | | Joe Gregorio is the main author of the API, written in the IETF RFC format. | | | Tim Bray, technology director at Sun Microsystems Inc. and primary voice behind The Atom Project, has given the thumbs-up to the draft format and is proposing that the working group submit the specs for IETF ratification without further delay. |
|
http://xml.coverpages.org/atom.html
|
|
| |
| | Zero Configuration Networking (Zeroconf) |
| | Autoconfiguration for IP Networking: Enabling Local Communication is a Zeroconf tutorial article by Erik Guttman, which appeared in the June 2001 issue of IEEE Internet Computing. | | | In effect this draft is the embyonic form of a possible future RFC which could become an update to RFC 1122 (Host Requirements). | | | Rendezvous is now used by iChat, iTunes, iPhoto, Safari, file sharing, printing, and just about every other piece of software that does networking on a Mac, including trusty old favorites like telnet, ssh, and ftp. |
|
http://www.zeroconf.org
|
|
| |
| | ISOC: The IETF and Telecommunications Standards |
| | The IETF is a large open international community of network designers, operators, vendors, users and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. | | | The currently active formal relationships between the IETF and other SDOs are described in the following RFCs: | | | The IETF has been developing standards for Internet-related technologies since 1986. |
|
http://www.isoc.org/news/6.shtml
|
|
| |
| | [No title] |
| | It is an informational RFC generated by the IMPP working group. | | | Day, J. Rosenberg, H. Sugano "A Model for Presence and Instant Messaging "IETF Request For Comments (RFC) 2778, February 2000. | | | Day, J. Rosenberg, "A Model for Presence and Instant Messaging "IETF Internet draft draft-ietf-impp-model-00.txt, April 23, 1999. |
|
http://www.jdrosen.net/ietf.html
|
|
| |
| | IANA Matrix |
| | IETF Consensus (in the form of a RFC - No requirement that it be standards-track) | | | 0-99: IETF consensus 100-199: RFC 200-249: RFC 250-255: Reserved for vendor private use (section B1) | | | Extended Label Type or Version Number: IESG approval Option Code: RFC (section 7) |
|
http://www.iana.org/numbers.html
|
|
| |
| | Web Naming and Addressing Overview (URIs, URLs, ...) |
| | In situations where the base URL is well-defined and known to the parser (human or machine), it is useful to be able to embed URL references which inherit that context rather than re-specifying it in every instance. | | | Its grammar is complete and consistent, and there are several clarifying examples. | | | This documents the designer's intent, before it was revised by the standards process. |
|
http://www.w3.org/Addressing
|
|
| |
| | International Essential Tremor Foundation |
| | The IETF works to make current and up-to-date information available to you any time, day or night. | | | Information and understanding are the start to accepting essential tremor as part of your life. | | | Let us know about an event in your community so it can be added to the calendar. |
|
http://www.essentialtremor.org
|
|
| |
| | IETF - voip-info.org |
| | The tel URI was originally defined in RFC 2806, which was developed outside of any IETF working group. | | | This working group focuses on the application of the Session Initiation Protocol (SIP, RFC 3261) to the suite of services collectively known as instant messaging and presence (IMP). | | | The IETF has committed to producing an interoperable standard for these services compliant to the requirements for IM outlined in RFC 2779 (including the security and privacy requirements there) and in the Common Presence and Instant Messaging (CPIM) specification, developed within the IMPP working group. |
|
http://www.voip-info.org/wiki-IETF
|
|
| |
| | RSVP Project |
| | Version 1 of RSVP has been specified in RFC 2205 and several ancillary RFCs (see Publications), and the Internet Engineering Task Force (IETF) has reached consensus on the RSVP specification documents as Internet Proposed Standards. | | | USC Information Sciences Institute (ISI) has taken a leading role in the development of RSVP and Internet Integrated Services. | | | RSVP requests will generally result in resources being reserved in each node along the data path. |
|
http://www.isi.edu/div7/rsvp/rsvp.html
|
|
| |
| | IETF - HyperText Markup Language (HTML) Working Group |
| | This document summarizes the history of HTML development, and defines the 'text/html' MIME type by pointing to the relevant W3C recommendations; it is intended to obsolete the previous IETF documents defining HTML, including RFC 1866, RFC 1867, RFC 1980, RFC 1942 and RFC 2070, and to remove HTML from IETF Standards Track. | | | Proposed IETF Web Distributed Authoring and Versioning (WEBDAV) Working Group | | | This RFC is the product of the Hypertext Markup Language Working Group of the IETF. |
|
http://www.ics.uci.edu/pub/ietf/html
|
|
| |
| | SOCKS |
| | The SOCKS site is sponsored by Permeo, an independent software company involved through the Internet Engineering Task Force (IETF) in development of the SOCKS standard. | | | All software downloads available on this site are intended for non-commercial use by researchers, academic institutions, and individuals interested in understanding and working with SOCKS. | | | SOCKS is an IETF standard proxy protocol for IP-based applications. |
|
http://www.socks.permeo.com
|
|
| |
| | RFC-Editor Webpage |
| | The official specification documents of the Internet Protocol suite that are defined by the Internet Engineering Task Force (IETF) and the Internet Engineering Steering Group (IESG) are recorded and published as standards track RFCs. | | | For more information on the history of the RFC series, see " |
|
http://www.rfc-editor.org
|
|
| |
| | IETF Secretariat |
| | A principal activity of the IETF Secretariat is to provide support services to the open, international community of researchers, programmers, vendors and others, collectively known as the Internet Engineering Task Force (IETF), who are concerned with the evolution of the Internet's architecture and the overall operation of the Internet. | | | Information about the structure, operations, and standards-related activities are available from the IETF. | | | The IETF Secretariat was established by CNRI to provide administrative, management and coordination services to facilitate the development and evolution of the Internet and its related standards. |
|
http://www.cnri.reston.va.us/ietf.html
|
|
| |
| | IETF Operations & Management (OPS) Area Home Page |
| | In forthcoming MIB reviews the MIB Doctors will be applying these "Guidelines for Authors and Reviewers of MIB Documents [RFC4181, BCP111]", (RFC issued September 23rd, 2005). | | | IETF Operations & Management (OPS) Area Home Page |
|
http://www.ops.ietf.org
|
|
| |
| | HTML Working Group of the IETF (at W3C) |
| | The group's work is to be based on existing practice on the Internet, and will make due reference to the SGML standard. | | | If you are new to the IETF, you should probably do some background reading. | | | IETF working groups exist for the sole purpose of drafting, revising, and reviewing Internet Standards. |
|
http://www.w3.org/MarkUp/HTML-WG
|
|
| |
| | The Simpleweb - The SimpleWeb - Internet |
| | The RFCs for all IETF MIBs, the original modules that are derived from these RFCs, the same modules but than without errors, the easy browsable HTML versions of these MIBs (really cool!), the XML versions... | | | List of working groups which are active within the IETF Operations and management area. | | | You can use the online MIB module validator by uploading files or providing the URL |
|
http://snmp.cs.utwente.nl/ietf
|
|
| |
| | IETF Tools |
| | For current tools, there may also be a page in the IETF tools wiki (in addition to the tools page you can reach through the menu to the left) which summarises proposals and known deficiencies - feel welcome to check this out, and contribute your information! | | | The pages are currently under construction - not all content is in place, and page design is not finished. | | | The aim of these web-pages is to help the IETF community as follows: |
|
http://tools.ietf.org
|
|
| |
| | IETF WEBDAV Working Group Home Page |
| | This document is a revised version of RFC 2518, the WebDAV Distributed Authoring Protocol. | | | A normal part of the development of IETF protocols is revision based on operational experience from deployed implementations. | | | Note that the text version of the document is the authoritative representation, and if there are differences between the text version and other versions, the text version is always correct. |
|
http://www.ics.uci.edu/~ejw/authoring
|
|
| |
| | IETF 63 |
| | An internet draft (revised since IETF 62) decribing what the effort is intended to do, and the efforts up to this point is available at http://www.ietf.org/internet-drafts/draft-jaeggli-ietftv-ng-01.txt. | | | Local (to the) IETF 63 playlist containing all 8 channels | | | Streams are delivered as 64Kb/s unicast-http-streamed mp3 audio, a popular and relativly standard way to deliver internet radio. |
|
http://videolab.uoregon.edu/events/ietf
|
|
| |
| | CFP 2004 / Computer Freedom & Privacy Conference |
| | He served on National Research Council study committees on information systems trustworthiness and the privacy implications of authentication technologies; he was also a member of the information technology subcommittee of an NRC study group on science versus terrorism. | | | He was a member of the Internet Architecture Board from 1996-2002; he is currently the co-director of the Security Area of the IETF. |
|
http://www.cfp2004.org/program/speakers.html
|
|
| |
| | IETF leaders urge detente with rivals |
| | At the IETF's thrice-yearly meetings, winners of prestigious computer science awards rub shoulders with grad students. | | | This is particularly true in the IETF's Applications Area, where rivals such as the W3C, Organization for the Advancement of Structured Information Standards, the Liberty Alliance Project and others are conducting cutting-edge development. | | | For nearly 20 years, the IETF has boasted the leading developers of Internet technology among its participants. |
|
http://www.networkworld.com/news/2005/031405-ietf.html?ts
|
|
| |
| | IETF Syslog Working Group Home Page |
| | While this protocol was originally developed on the University of California Berkeley Software Distribution (BSD) TCP/IP system implementations, its value to operations and management has led it to be ported to many other operating systems as well as being embedded into many other networked devices. | | | The belief being that we can provide mechanisms that can be utilized in existing programs with few modifications to the protocol while providing significant security enhancements. | | | This document is a product of the Security Issues in Network Event Logging Working Group of the IETF. |
|
http://www.employees.org/~lonvick/index.shtml
|
|
| |
| | IETF RFC Page |
| | There is no index or search feature -- those capabilities are available at the RFC Editor Web page. | | | RFCs associated with an active IETF Working Group can also be accessed from the Working Group's web page via IETF Working Groups. | | | The first choice below connects to the RFC repository maintained by the IETF Secretariat. |
|
http://www.ietf.org/rfc.html
|
|
| |
| | Technorati Tag: IETF |
| | Anyone want to help me write an update to RFC 1149 for large content... | | | Though I mainly go to the IETF to work on LDAP (both with the LDAPBis working group and as an... | | | The part I found the most amusing, or... |
|
http://www.technorati.com/tag/IETF
|
|
| |
| | Yahoo sets up standard to combat spam Tech News on ZDNet |
| | Yahoo said it had submitted DomainKeys to the Internet Engineering Task Force (IETF), a standards-setting body, and will allow developers to implement it for free. | | | Visit Virus Threat Center's Netsky definition page for a list of free removal tools, the latest alerts, and breaking Netsky news. | | | Such techniques rely on widespread adoption for effectiveness. |
|
http://news.zdnet.com/2100-1009_22-5215381.html
|
|
| |
| | Internet Mail Consortium |
| | IMC is the host of numerous mailing lists that relate to Internet mail standards. | | | Some of these mailing lists are for work being done in the IETF, while others are for discussion of particular mail topics. | | | All of the mailing lists have complete list archives. |
|
http://www.imc.org
|
|
| |
| | ngtrans Home Page |
| | Where to find IPv6 transition and implementation information. | | | The new IPv6 Operations (v6ops) working group of the IETF has essentially replaced the ngtrans effort. | | | The IPng Transition (ngtrans) working group of the IETF is now closed. |
|
http://www.6bone.net/ngtrans
|
|
| |
| | IETF Education Team |
| | RFC 3979 - Intellectual Property Rights in IETF Technology | | | Introduction to Working Group Leadership @ IETF 62 | | | Please read the following documents regarding your intellectual property rights while participating in IETF activities: |
|
http://edu.ietf.org
|
|
| |
| | IetfCharter - Atom Wiki |
| | The feed format and HTTP will be used as the basis of work on a standards-track document specifying the editing protocol. | | | If other submissions are made to the working group under terms accepted by the IETF, the working group may consider them as alternatives, based upon their merits. | | | The Working Group will also take steps to ensure interoperability, by: |
|
http://www.intertwingly.net/wiki/pie/IetfCharter
|
|
| |
| | Hypertext Transfer Protocol -- HTTP/1.0 |
| | "Requirements for Internet hosts - application and support." STD 3, RFC 1123, IETF, October 1989. | | | Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. | | | Note that other groups may also distribute working documents as Internet-Drafts. |
|
http://www.w3.org/Protocols/HTTP/1.0/draft-ietf-http-spec.html
|
|
| |
| | Joe Gregorio BitWorking Projects Atom |
| | The previous version of the draft RFCs are available: | | | Rather than trying to keep up to date on all the activity in the Atom WG, I'll just send you over to look at the nice Atompub Status Pages that the IETF is now generating. | | | To provide feedback on this draft join the atom-protocol mailing list. |
|
http://bitworking.org/projects/atom
|
|
| |
| | IETF Agentx Working Group - Home page |
| | It defines processing entities called master agents and subagents, a protocol (AgentX) used to communicate between them, and the elements of procedure by which the extensible agent processes SNMP protocol messages. | | | The resulting technology specification will allow independently developed sub-agents to communicate with a master-agent running on an Internet device. | | | This document is a product of the SNMP Agent Extensibility Working Group of the IETF. |
|
http://www.scguild.com/agentx
|
|
|
