Internet Engineering Task Force

Summary

Internet Engineering Task Force is a standards organization^[1]. It ranks in the top 3% of standards_organization entities by monthly Wikipedia readership (1,056 views/month).^[2]

Key Facts

• Internet Engineering Task Force's field of work was access^[3].
• Internet Engineering Task Force's field of work was censorship^[4].
• Internet Engineering Task Force's field of work was democracy^[5].
• Internet Engineering Task Force's field of work was digital divide^[6].
• Internet Engineering Task Force's field of work was digital rights^[7].
• Internet Engineering Task Force's field of work was freedom of information^[8].
• Internet Engineering Task Force is located in Fremont^[9].
• Internet Engineering Task Force is in the country of United States^[10].
• Internet Engineering Task Force's instance of is recorded as standards organization^[11].
• Internet Engineering Task Force's instance of is recorded as nonprofit organization^[12].
• Internet Engineering Task Force's instance of is recorded as project^[13].
• Internet Engineering Task Force's logo image is recorded as Internet Engineering Task Force logo.svg^[14].
• Internet Engineering Task Force's headquarters location is recorded as Fremont^[15].
• Internet Engineering Task Force's ISNI is recorded as 000000012217224X^[16].
• Internet Engineering Task Force's VIAF cluster ID is recorded as 129329229^[17].
• Internet Engineering Task Force's GND ID is recorded as 5570557-1^[18].
• Internet Engineering Task Force's Library of Congress authority ID is recorded as no99050167^[19].
• Internet Engineering Task Force's child organization or unit is recorded as Internet Architecture Board^[20].
• Internet Engineering Task Force's child organization or unit is recorded as Internet Engineering Steering Group^[21].
• Internet Engineering Task Force's child organization or unit is recorded as Internet Research Task Force^[22].
• Internet Engineering Task Force's child organization or unit is recorded as Internet Engineering Task Force Administrative Oversight Committee^[23].
• Internet Engineering Task Force's Commons category is recorded as Internet Engineering Task Force^[24].
• +1986-01-17T00:00:00Z marks the founding of Internet Engineering Task Force^[25].
• Internet Engineering Task Force's Freebase ID is recorded as /m/03ydv^[26].
• Internet Engineering Task Force's NL CR AUT ID is recorded as kn20080504011^[27].

Body

Founding

+1986-01-17T00:00:00Z marks the founding of Internet Engineering Task Force^[25].

Identity

Internet Engineering Task Force's official name is recorded as {'lang': 'en', 'text': 'it'}^[28]. Its short name is recorded as {'lang': 'en', 'text': 'IETF'}^[29].

Operations

Internet Engineering Task Force's headquarters location is recorded as Fremont^[15]. Its parent organization or unit is recorded as Internet Society^[30]. Subsidiaries include Internet Architecture Board^[20], a committee^[31], in United States^[32], founded in 1979^[33]; Internet Engineering Steering Group^[21], a committee^[34], founded in 1986^[35]; Internet Research Task Force^[22], an organization^[36], founded in 1986^[37]; and Internet Engineering Task Force Administrative Oversight Committee^[23], a committee^[38].

Industry

Fields of work include access^[3]; censorship^[4]; democracy^[5], a form of government^[39]; digital divide^[6], a social inequality^[40]; digital rights^[7], in Costa Rica^[41]; and freedom of information^[8], a concept^[42].

Why It Matters

Internet Engineering Task Force ranks in the top 3% of standards_organization entities by monthly Wikipedia readership (1,056 views/month).^[2] It has Wikipedia articles in 30 language editions, a strong signal of global cultural recognition.^[43] It is known by 42 alternative names across languages and contexts.^[44]

Works attributed to it include CalDAV^[45], a computer network protocol^[46], written by it^[47]; Datagram Transport Layer Security^[48], a computer network protocol^[49], written by it^[50]; CardDAV^[51], a computer network protocol^[52], written by it^[53]; and Optimized Link State Routing Protocol^[54], a link-state routing protocol^[55], written by it^[56].