Re: [Tzdist] [tzdist] #34 (service): should we include a raw tzdb format media type?
"tzdist issue tracker" <trac+tzdist@tools.ietf.org> Mon, 16 February 2015 17:41 UTC
Return-Path: <trac+tzdist@tools.ietf.org>
X-Original-To: tzdist@ietfa.amsl.com
Delivered-To: tzdist@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 4C4261A1B98
for <tzdist@ietfa.amsl.com>; Mon, 16 Feb 2015 09:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id GaAvlj6YOiDF for <tzdist@ietfa.amsl.com>;
Mon, 16 Feb 2015 09:41:57 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org
[IPv6:2001:1890:123a::1:2a])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 5D0301A1B6A
for <tzdist@ietf.org>; Mon, 16 Feb 2015 09:41:57 -0800 (PST)
Received: from localhost ([::1]:46328 helo=zinfandel.tools.ietf.org)
by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX)
(envelope-from <trac+tzdist@tools.ietf.org>)
id 1YNPgC-0003P6-5z; Mon, 16 Feb 2015 09:41:56 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "tzdist issue tracker" <trac+tzdist@tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: cyrus@daboo.name, mglt.ietf@gmail.com
X-Trac-Project: tzdist
Date: Mon, 16 Feb 2015 17:41:56 -0000
X-URL: http://tools.ietf.org/tzdist/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/tzdist/trac/ticket/34#comment:1
Message-ID: <070.c0bedf3439011293cdd3c01743bec888@tools.ietf.org>
References: <055.3273bd9c81e7cf06280617afb0cd8dc8@tools.ietf.org>
X-Trac-Ticket-ID: 34
In-Reply-To: <055.3273bd9c81e7cf06280617afb0cd8dc8@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: cyrus@daboo.name, mglt.ietf@gmail.com, tzdist@ietf.org
X-SA-Exim-Mail-From: trac+tzdist@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org);
SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/tzdist/_XxbBwauyuoM35r0fC4V6MXtLY0>
Cc: tzdist@ietf.org
Subject: Re: [Tzdist] [tzdist] #34 (service): should we include a raw tzdb
format media type?
X-BeenThere: tzdist@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <tzdist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tzdist>,
<mailto:tzdist-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tzdist/>
List-Post: <mailto:tzdist@ietf.org>
List-Help: <mailto:tzdist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tzdist>,
<mailto:tzdist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2015 17:41:59 -0000
#34: should we include a raw tzdb format media type? Changes (by mglt.ietf@gmail.com): * status: new => closed * resolution: => fixed Comment: the protocol can easily include additional format: section 4.1.2 Clients use the HTTP Accept header field (see Section 5.3.2 of [RFC7231]) to indicate their preference for the returned data format. Servers indicate the available formats that they support via the "capabilities" action response -- --------------------------------+------------------------------- Reporter: lear@cisco.com | Owner: cyrus@daboo.name Type: defect | Status: closed Priority: minor | Milestone: Component: service | Version: Severity: Active WG Document | Resolution: fixed Keywords: | --------------------------------+------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/tzdist/trac/ticket/34#comment:1> tzdist <http://tools.ietf.org/tzdist/>
- [Tzdist] [tzdist] #34 (service): should we includ… tzdist issue tracker
- Re: [Tzdist] [tzdist] #34 (service): should we in… Paul Eggert
- Re: [Tzdist] [tzdist] #34 (service): should we in… Eliot Lear
- Re: [Tzdist] [tzdist] #34 (service): should we in… Lester Caine
- Re: [Tzdist] [tzdist] #34 (service): should we in… Paul Eggert
- Re: [Tzdist] [tzdist] #34 (service): should we in… Lester Caine
- Re: [Tzdist] [tzdist] #34 (service): should we in… Tim Parenti
- Re: [Tzdist] [tzdist] #34 (service): should we in… Ken Murchison
- Re: [Tzdist] [tzdist] #34 (service): should we in… Tim Parenti
- Re: [Tzdist] [tzdist] #34 (service): should we in… Tim Parenti
- Re: [Tzdist] [tzdist] #34 (service): should we in… tzdist issue tracker