Harald Tveit Alvestrand | |
|---|---|
 | |
| Born | 29 June 1959 |
| Occupation | computer scientist |
| Known for | i18n, IETF, and Linux work |
| Notable work | RFC 2277 (BCP 18) |
| Children | 3 |
| Website | www |
Harald Tveit Alvestrand (born 29 June 1959) is a Norwegian computer scientist. He was chair of the Internet Engineering Task Force (IETF) from 2001 until 2005, succeeding Fred Baker. Within the IETF, Alvestrand was earlier the chair of the Areas for Applications from 1995 until 1997, and of Operations and Management in 1998.
Alvestrand was born in Namsos, Norway, received his education from Bergen Cathedral School and the Norwegian Institute of Technology, and has worked for Norsk Data, UNINETT, EDB Maxware, Cisco Systems, and Google.
He is an author of several important Request for Comments (RFCs), many in the general area of Internationalization and localization, [1] most notable the documents required for interoperability between SMTP and X.400. Since the start of the use of OIDs he has run a front end [2] to the hierarchy of assignments according to X.208. [3]
At the end of 2007 Alvestrand was selected for the ICANN Board, [4] where he remained until December 2010. In 2001 he became a member of the Unicode Board of Directors. [5] He was a co-chair of the IETF EAI and USEFOR WGs. [6] [7]
Harald Alvestrand was the executive director of the Linux Counter organization. [8] He was a member of the Norid Board, [9] and the RFC Independent Submissions Editorial Board. [10] As of 2008 [update] he lived in Trondheim, Norway, and has been working for Google since 2006. [11] [12]
Deployment of the Internet White Pages Service, Best Current Practice 15.
IETF Policy on Character Sets and Languages, Best Current Practice 18.
Guidelines for Writing an IANA Considerations Section in RFCs, Obsolete, was BCP 26. Obsoleted by RFC 8126 . Obsoletes RFC 2434 .
Advancement of MIB specifications on the IETF Standards Track, Best Current Practice 27.
Tags for the Identification of Languages, Obsolete. Obsoleted by RFC 3066 and 3282 .
Tags for the Identification of Languages, Obsolete, was BCP 47. Obsoleted by RFC 4646 and 4647 .
The IESG and RFC Editor Documents: Procedures, Obsolete, was BCP 92. Obsoleted by RFC 5742 . Updates RFC 3710 and 2026 .
A Mission Statement for the IETF, Best Current Practice 95.
X.400 Use of Extended Character Sets, Historic.
The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996, Informational. This memo prepared the UTF-8 50-years plan in RFC 2277.
Mapping between X.400 and RFC-822/MIME Message Bodies, Proposed Standard.
Content Language Headers, Draft Standard.
Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents, Informational.
A Generalized Unified Character Code: Western European and CJK Sections, Informational. This is an April Fools' Day Request for Comments . (With co-author John Klensin.)
A Request for Comments (RFC) is a publication in a series from the principal technical development and standards-setting bodies for the Internet, most prominently the Internet Engineering Task Force (IETF). An RFC is authored by individuals or groups of engineers and computer scientists in the form of a memorandum describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems. It is submitted either for peer review or to convey new concepts, information, or, occasionally, engineering humor.
A Uniform Resource Identifier (URI), formerly Universal Resource Identifier, is a unique sequence of characters that identifies an abstract or physical resource, such as resources on a webpage, mail address, phone number, books, real-world objects such as people and places, concepts. URIs are used to identify anything described using the Resource Description Framework (RDF), for example, concepts that are part of an ontology defined using the Web Ontology Language (OWL), and people who are described using the Friend of a Friend vocabulary would each have an individual URI.
UTF-8 is a character encoding standard used for electronic communication. Defined by the Unicode Standard, the name is derived from Unicode Transformation Format – 8-bit. Almost every webpage is stored in UTF-8.
The Internet Assigned Numbers Authority (IANA) is a standards organization that oversees global IP address allocation, autonomous system number allocation, root zone management in the Domain Name System (DNS), media types, and other Internet Protocol–related symbols and Internet numbers.
The Internet Research Task Force (IRTF) is an organization, overseen by the Internet Architecture Board, that focuses on longer-term research issues related to the Internet. A parallel organization, the Internet Engineering Task Force (IETF), focuses on the shorter term issues of engineering and standards making.
An email address identifies an email box to which messages are delivered. While early messaging systems used a variety of formats for addressing, today, email addresses follow a set of specific rules originally standardized by the Internet Engineering Task Force (IETF) in the 1980s, and updated by RFC 5322 and 6854. The term email address in this article refers to just the addr-spec in Section 3.4 of RFC 5322. The RFC defines address more broadly as either a mailbox or group. A mailbox value can be either a name-addr, which contains a display-name and addr-spec, or the more common addr-spec alone.
A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that uses the urn scheme. URNs are globally unique persistent identifiers assigned within defined namespaces so they will be available for a long period of time, even after the resource which they identify ceases to exist or becomes unavailable. URNs cannot be used to directly locate an item and need not be resolvable, as they are simply templates that another parser may use to find an item.
An internationalized domain name (IDN) is an Internet domain name that contains at least one label displayed in software applications, in whole or in part, in non-Latin script or alphabet or in the Latin alphabet-based characters with diacritics or ligatures. These writing systems are encoded by computers in multibyte Unicode. Internationalized domain names are stored in the Domain Name System (DNS) as ASCII strings using Punycode transcription.
The domain names example.com, example.net, example.org, and example.edu are second-level domain names in the Domain Name System of the Internet. They are reserved by the Internet Assigned Numbers Authority (IANA) at the direction of the Internet Engineering Task Force (IETF) as special-use domain names for documentation purposes. The domain names are used widely in books, tutorials, sample network configurations, and generally as examples for the use of domain names. The Internet Corporation for Assigned Names and Numbers (ICANN) operates websites for these domains with content that reflects their purpose.
The Internationalized Resource Identifier (IRI) is an internet protocol standard which builds on the Uniform Resource Identifier (URI) protocol by greatly expanding the set of permitted characters. It was defined by the Internet Engineering Task Force (IETF) in 2005 in RFC 3987. While URIs are limited to a subset of the US-ASCII character set, IRIs may additionally contain most characters from the Universal Character Set, including Chinese, Japanese, Korean, and Cyrillic characters.
Many email clients now offer some support for Unicode. Some clients will automatically choose between a legacy encoding and Unicode depending on the mail's content, either automatically or when the user requests it.
Frederick J. Baker, is an American engineer, specializing in developing computer network protocols for the Internet.
In the Internet addressing architecture, the Internet Engineering Task Force (IETF) and the Internet Assigned Numbers Authority (IANA) have reserved various Internet Protocol (IP) addresses for special purposes.
WHOIS is a query and response protocol that is used for querying databases that store an Internet resource's registered users or assignees. These resources include domain names, IP address blocks and autonomous systems, but it is also used for a wider range of other information. The protocol stores and delivers database content in a human-readable format. The current iteration of the WHOIS protocol was drafted by the Internet Society, and is documented in RFC 3912.
An IETF BCP 47 language tag is a standardized code that is used to identify human languages on the Internet. The tag structure has been standardized by the Internet Engineering Task Force (IETF) in Best Current Practice (BCP) 47; the subtags are maintained by the IANA Language Subtag Registry.
Mark Edward Davis is an American specialist in the internationalization and localization of software and the co-founder and chief technical officer of the Unicode Consortium, previously serving as its president until 2022.
International email arises from the combined provision of internationalized domain names (IDN) and email address internationalization (EAI). The result is email that contains international characters, encoded as UTF-8, in the email header and in supporting mail transfer protocols. The most significant aspect of this is the allowance of email addresses in most of the world's writing systems, at both interface and transport levels.
John C. Klensin is a political scientist and computer science professional who is active in Internet-related issues.
Barry Leiba is a computer scientist and software researcher. He retired from IBM's Thomas J. Watson Research Center in Hawthorne, New York in February 2009, and now works for FutureWei Technologies as a Director of Internet Standards. His work has focused for many years on electronic mail and anti-spam technology, on mobile computing and the Internet of things, and on Internet standards.
A uniform resource locator (URL), colloquially known as an address on the Web, is a reference to a resource that specifies its location on a computer network and a mechanism for retrieving it. A URL is a specific type of Uniform Resource Identifier (URI), although many people use the two terms interchangeably. URLs occur most commonly to reference web pages (HTTP/HTTPS) but are also used for file transfer (FTP), email (mailto), database access (JDBC), and many other applications.
| Authority control databases: Academics |
|---|
