Harald Alvestrand

Revision as of 23:07, 3 February 2011 by Pulasthi (talk | contribs)
Country: Norway
Website:

   [www.alvestrand.no www.alvestrand.no]

Twitter:    @alvestrand

Harald Alvestrand was born in Norway in 1959, and graduated from the Norwegian Institute of Technology (NTH) in 1984. He has worked for Norsk Data, UNINETT (the university network of Norway), EDB Maxware, Cisco Systems and, since 2006, for Google.

He has been active in Internet standardization via the Internet Engineering Task Force (IETF) since 1991, and has written a number of RFCs, including RFC 1766, the first standard for language tags in Internet protocols.

In the IETF, he has been an area director of the Applications area (1995-1998) and of the Operations & Management area (1998-1999; a member of the Internet Architecture Board (1999-2001), and served as chair of the IETF from 2001 to 2006.

He was alternate chair of the ICANN DNSO General Assembly from December 1999 to April 2001, and was a member of the WIPO panel of experts on the DNS in 1998-1999.

He is currently a board member of NORID, the .no domain name registry, and of the Unicode Consortium.

He lives in Trondheim, Norway, is married, and has 3 children.

Harald Alvestrand was selected for the ICANN Board by the Nominating Committee. His current term, which started after the 2007 annual meeting, will end after the conclusion of ICANN's annual meeting in 2010.[1]

Publications edit

  • Best Current Practices
   * RFC 2148 (BCP 15) Deployment of the Internet White Pages Service
   * RFC 2277 (BCP 18) IETF Policy on Character Sets and Languages
   * RFC 5226 (BCP 26) Guidelines for Writing an IANA Considerations Section in RFCs
   * RFC 2438 (BCP 27) Advancement of MIB specifications on the IETF Standards Track
   * RFC 1766 + RFC 3066 Tags for the Identification of Languages (was BCP 47)
   * RFC 3932 (BCP 92) The IESG and RFC Editor Documents: Procedures
   * RFC 3935 (BCP 95) A Mission Statement for the IETF
  • Other important RFCs[2]
   * RFC 2130 (this memo prepared the UTF-8 50-years plan in RFC 2277)
   * RFC 2157 Mapping between X.400 and RFC-822/MIME Message Bodies
   * RFC 3282 Content Language Headers (draft standard)
   * RFC 4450 Getting Rid of the Cruft (major RFC cleanup work)
   * RFC 5242 A Generalized Unified Character Code: Western European and CJK Sections (with John Klensin) April 1, 2008

References edit