BCP 175, RFC 6557 on Procedures for Maintaining the Time Zone Database
rfc-editor@rfc-editor.org Wed, 29 February 2012 19:05 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C747F21F87C1 for <ietf-announce@ietfa.amsl.com>; Wed, 29 Feb 2012 11:05:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UUGnlou+d2yf for <ietf-announce@ietfa.amsl.com>; Wed, 29 Feb 2012 11:05:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 47A0E21F87B3 for <ietf-announce@ietf.org>; Wed, 29 Feb 2012 11:05:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C599D72E118; Wed, 29 Feb 2012 11:00:05 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 175, RFC 6557 on Procedures for Maintaining the Time Zone Database
From: rfc-editor@rfc-editor.org
Message-Id: <20120229190007.C599D72E118@rfc-editor.org>
Date: Wed, 29 Feb 2012 11:00:05 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 19:05:44 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 175
RFC 6557
Title: Procedures for Maintaining the Time
Zone Database
Author: E. Lear, P. Eggert
Status: Best Current Practice
Stream: IETF
Date: February 2012
Mailbox: lear@cisco.com,
eggert@cs.ucla.edu
Pages: 9
Characters: 18469
See Also: BCP0175
I-D Tag: draft-lear-iana-timezone-database-05.txt
URL: http://www.rfc-editor.org/rfc/rfc6557.txt
Time zone information serves as a basic protocol element in
protocols, such as the calendaring suite and DHCP. The Time Zone
(TZ) Database specifies the indices used in various protocols, as
well as their semantic meanings, for all localities throughout the
world. This database has been meticulously maintained and
distributed free of charge by a group of volunteers, coordinated by a
single volunteer who is now planning to retire. This memo specifies
procedures involved with maintenance of the TZ database and
associated code, including how to submit proposed updates, how
decisions for inclusion of those updates are made, and the selection
of a designated expert by and for the time zone community. The
intent of this memo is, to the extent possible, to document existing
practice and provide a means to ease succession of the database
maintainers. This memo documents an Internet Best Current Practice.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC