Misplaced Pages

#709290

34-450: The GSSAPI is an IETF standard that addresses the problem of many similar but incompatible security services in use as of 2005. The GSSAPI, by itself, does not provide any security. Instead, security-service vendors provide GSSAPI implementations - usually in the form of libraries installed with their security software. These libraries present a GSSAPI-compatible interface to application writers who can write their application to use only

68-510: A charter that describes its focus; and what it is expected to produce, and when. It is open to all who want to participate and holds discussions on an open mailing list . Working groups hold open sessions at IETF meetings, where the onsite registration fee in 2024 was between US$ 875 (early registration) and $ 1200 per person for the week. Significant discounts are available for students and remote participants. As working groups do not make decisions at IETF meetings, with all decisions taken later on

102-674: A cooperative agreement, No. NCR-8820945, wherein CNRI agreed to create and provide a "secretariat" for the "overall coordination, management and support of the work of the IAB, its various task forces and, particularly, the IETF". In 1992, CNRI supported the formation and early funding of the Internet Society, which took on the IETF as a fiscally sponsored project, along with the IAB, the IRTF, and

136-421: Is also standardizing protocols for autonomic networking that enables networks to be self managing. It is a network of physical objects or things that are embedded with electronics, sensors, software and also enables objects to exchange data with operator, manufacturer and other connected devices. Several IETF working groups are developing protocols that are directly relevant to IoT . Its development provides

170-700: Is available from these statistics. The IETF chairperson is selected by the NomCom process for a two-year renewable term. Before 1993, the IETF Chair was selected by the IAB. A list of the past and current chairs of the IETF: The IETF works on a broad range of networking technologies which provide foundation for the Internet's growth and evolution. It aims to improve the efficiency in management of networks as they grow in size and complexity. The IETF

204-479: Is better than rough. It is up to the Chair to determine if rough consensus has been reached (IETF Working Group Guidelines and Procedures). The phrase is often extended into the saying "rough consensus and running code", to make it clear that the IETF is interested in practical, working systems that can be quickly implemented. There is some debate as to whether running code leads to rough consensus or vice versa. There

238-598: Is on implementing code that will improve standards in terms of quality and interoperability. The details of IETF operations have changed considerably as the organization has grown, but the basic mechanism remains publication of proposed specifications, development based on the proposals, review and independent testing by participants, and republication as a revised proposal, a draft proposal, or eventually as an Internet Standard. IETF standards are developed in an open, all-inclusive process in which any interested individual can participate. All IETF documents are freely available over

272-452: Is on the IETF meetings page. The IETF strives to hold its meetings near where most of the IETF volunteers are located. IETF meetings are held three times a year, with one meeting each in Asia, Europe and North America. An occasional exploratory meeting is held outside of those regions in place of one of the other regions. The IETF also organizes hackathons during the IETF meetings. The focus

306-569: Is overseen by an area director (AD), with most areas having two ADs. The ADs are responsible for appointing working group chairs. The area directors, together with the IETF Chair, form the Internet Engineering Steering Group (IESG), which is responsible for the overall operation of the IETF. The Internet Architecture Board (IAB) oversees the IETF's external relationships. The IAB provides long-range technical direction for Internet development. The IAB also manages

340-561: Is responsible for day-to-day management of the IETF. It receives appeals of the decisions of the working groups, and the IESG makes the decision to progress documents in the standards track . The chair of the IESG is the area director of the general area, who also serves as the overall IETF chair. Members of the IESG include the two directors, sometimes three, of each of the following areas: Liaison and ex officio members include: The Gateway Algorithms and Data Structures (GADS) Task Force

374-635: The Internet Research Task Force (IRTF), with which the IETF has a number of cross-group relations. A nominating committee (NomCom) of ten randomly chosen volunteers who participate regularly at meetings, a non-voting chair and 4-5 liaisons, is vested with the power to appoint, reappoint, and remove members of the IESG, IAB, IETF Trust and the IETF LLC. To date, no one has been removed by a NomCom, although several people have resigned their positions, requiring replacements. In 1993

SECTION 10

#1732801033710

408-489: The vendor-independent GSSAPI. If the security implementation ever needs replacing, the application need not be rewritten. The definitive feature of GSSAPI applications is the exchange of opaque messages ( tokens ) which hide the implementation detail from the higher-level application. The client and server sides of the application are written to convey the tokens given to them by their respective GSSAPI implementations. GSSAPI tokens can usually travel over an insecure network as

442-591: The IETF changed from an activity supported by the US federal government to an independent, international activity associated with the Internet Society , a US-based 501(c)(3) organization . In 2018 the Internet Society created a subsidiary, the IETF Administration LLC, to be the corporate, legal and financial home for the IETF. IETF activities are funded by meeting fees, meeting sponsors and by

476-620: The ISOC's board of directors. In 2018, ISOC established The IETF Administration LLC, a separate LLC to handle the administration of the IETF. In 2019, the LLC issued a call for proposals to provide secretariat services to the IETF. The first IETF meeting was attended by 21 US federal government-funded researchers on 16 January 1986. It was a continuation of the work of the earlier GADS Task Force. Representatives from non-governmental entities (such as gateway vendors ) were invited to attend starting with

510-644: The Internet Society via its organizational membership and the proceeds of the Public Interest Registry . In December 2005, the IETF Trust was established to manage the copyrighted materials produced by the IETF. The Internet Engineering Steering Group (IESG) is a body composed of the Internet Engineering Task Force (IETF) chair and area directors. It provides the final technical review of Internet standards and

544-481: The Internet Standards process, the Internet Standards or their technical content". In 1998, CNRI established Foretec Seminars, Inc. (Foretec), a for-profit subsidiary to take over providing secretariat services to the IETF. Foretec provided these services until at least 2004. By 2013, Foretec was dissolved. In 2003, IETF's RFC  3677 described IETFs role in appointing three board members to

578-588: The Internet and can be reproduced at will. Multiple, working, useful, interoperable implementations are the chief requirement before an IETF proposed specification can become a standard. Most specifications are focused on single protocols rather than tightly interlocked systems. This has allowed the protocols to be used in many different systems, and its standards are routinely re-used by bodies which create full-fledged architectures (e.g. 3GPP IMS ). Because it relies on volunteers and uses "rough consensus and running code" as its touchstone, results can be slow whenever

612-409: The ability of internet applications to send data over the Internet. There are some well-established transport protocols such as TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) which are continuously getting extended and refined to meet the needs of the global Internet. Rough consensus Rough consensus is a term used in consensus decision-making to indicate the "sense of

646-448: The dominant view of the working group shall prevail. (However, "dominance" is not to be determined on the basis of volume or persistence, but rather a more general sense of agreement). Consensus can be determined by a show of hands, humming, or any other means on which the WG agrees (by rough consensus, of course). Note that 51% of the working group does not qualify as "rough consensus" and 99%

680-470: The event a deficit occurs, CNRI has agreed to contribute up to USD$ 102,000 to offset it." In 1993, Cerf continued to support the formation of ISOC while working for CNRI, and the role of ISOC in "the official procedures for creating and documenting Internet Standards" was codified in the IETF's RFC   1602 . In 1995, IETF's RFC  2031 describes ISOC's role in the IETF as being purely administrative, and ISOC as having "no influence whatsoever on

714-459: The fourth IETF meeting in October 1986. Since that time all IETF meetings have been open to the public. Initially, the IETF met quarterly, but from 1991, it has been meeting three times a year. The initial meetings were very small, with fewer than 35 people in attendance at each of the first five meetings. The maximum attendance during the first 13 meetings was only 120 attendees. This occurred at

SECTION 20

#1732801033710

748-624: The group" concerning a particular matter under consideration. It has been defined as the "dominant view" of a group as determined by its chairperson . The term was used by the Internet Engineering Task Force (IETF) in describing its procedures for working groups (WGs). The means to establish rough consensus was described by the IETF as follows: Working groups make decisions through a "rough consensus" process. IETF consensus does not require that all participants agree although this is, of course, preferred. In general,

782-662: The identity of the remote user or remote host. The GSSAPI describes about 45 procedure calls. Significant ones include: The GSSAPI is standardized for the C (RFC 2744) language. Java implements the GSSAPI as JGSS, the Java Generic Security Services Application Program Interface. Some limitations of GSSAPI are: Anticipating new security mechanisms, the GSSAPI includes a negotiating pseudo mechanism , SPNEGO , that can discover and use new mechanisms not present when

816-542: The mechanisms provide inherent message security. After the exchange of some number of tokens, the GSSAPI implementations at both ends inform their local application that a security context is established. Once a security context is established, sensitive application messages can be wrapped (encrypted) by the GSSAPI for secure communication between client and server. Typical protections guaranteed by GSSAPI wrapping include confidentiality (secrecy) and integrity (authenticity). The GSSAPI can also provide local guarantees about

850-479: The modern Internet: Examples of Internet services: The Internet Engineering Task Force ( IETF ) is a standards organization for the Internet and is responsible for the technical standards that make up the Internet protocol suite (TCP/IP). It has no formal membership roster or requirements and all its participants are volunteers. Their work is usually funded by employers or other sponsors. The IETF

884-423: The number of volunteers is either too small to make progress, or so large as to make consensus difficult, or when volunteers lack the necessary expertise. For protocols like SMTP , which is used to transport e-mail for a user community in the many hundreds of millions, there is also considerable resistance to any change that is not fully backward compatible , except for IPv6 . Work within the IETF on ways to improve

918-419: The organization of annual INET meetings. Gross continued to serve as IETF chair throughout this transition. Cerf, Kahn, and Lyman Chapin announced the formation of ISOC as "a professional society to facilitate, support, and promote the evolution and growth of the Internet as a global research communications infrastructure". At the first board meeting of the Internet Society, Cerf, representing CNRI, offered, "In

952-605: The original application was built. The dominant GSSAPI mechanism implementation in use is Kerberos . Unlike the GSSAPI, the Kerberos API has not been standardized and various existing implementations use incompatible APIs. The GSSAPI allows Kerberos implementations to be API compatible. IETF Early research and development: Merging the networks and creating the Internet: Commercialization, privatization, broader access leads to

986-525: The speed of the standards-making process is ongoing but, because the number of volunteers with opinions on it is very great, consensus on improvements has been slow to develop. The IETF cooperates with the W3C , ISO / IEC , ITU , and other standards bodies. Statistics are available that show who the top contributors by RFC publication are. While the IETF only allows for participation by individuals, and not by corporations or governments, sponsorship information

1020-543: The twelfth meeting, held during January 1989. These meetings have grown in both participation and scope a great deal since the early 1990s; it had a maximum attendance of 2810 at the December 2000 IETF held in San Diego, California . Attendance declined with industry restructuring during the early 2000s, and is currently around 1200. The locations for IETF meetings vary greatly. A list of past and future meeting locations

1054-490: The working group mailing list , meeting attendance is not required for contributors. Rough consensus is the primary basis for decision making. There are no formal voting procedures. Each working group is intended to complete work on its topic and then disband. In some cases, the working group will instead have its charter updated to take on new tasks as appropriate. The working groups are grouped into areas by subject matter ( see § Steering group , below ). Each area

Generic Security Services Application Program Interface - Misplaced Pages Continue

1088-573: Was Mike Corrigan, who was then the technical program manager for the Defense Data Network (DDN). Also in 1986, after leaving DARPA, Robert E. Kahn founded the Corporation for National Research Initiatives (CNRI), which began providing administrative support to the IETF. In 1987, Corrigan was succeeded as IETF chair by Phill Gross. Effective March 1, 1989, but providing support dating back to late 1988, CNRI and NSF entered into

1122-588: Was initially supported by the federal government of the United States but since 1993 has operated under the auspices of the Internet Society , a non-profit organization with local chapters around the world. There is no membership in the IETF. Anyone can participate by signing up to a working group mailing list, or registering for an IETF meeting. The IETF operates in a bottom-up task creation mode, largely driven by working groups. Each working group normally has appointed two co-chairs (occasionally three);

1156-646: Was the precursor to the IETF. Its chairman was David L. Mills of the University of Delaware . In January 1986, the Internet Activities Board (IAB; now called the Internet Architecture Board) decided to divide GADS into two entities: an Internet Architecture (INARC) Task Force chaired by Mills to pursue research goals, and the IETF to handle nearer-term engineering and technology transfer issues. The first IETF chair

#709290