[TLS] Resolution on gmt_time
"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> Mon, 23 June 2014 05:18 UTC
Return-Path: <jsalowey@cisco.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A78E1B286A for <tls@ietfa.amsl.com>; Sun, 22 Jun 2014 22:18:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 3KQkyXg6wo6l for <tls@ietfa.amsl.com>; Sun, 22 Jun 2014 22:17:59 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B80E11A045D for <tls@ietf.org>; Sun, 22 Jun 2014 22:17:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=793; q=dns/txt; s=iport; t=1403500679; x=1404710279; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=W1FbkaXDfQNxhjWBlCGUBzLEQI41lwZ48qzFI+mWAks=; b=b+YGN+Dm64TJGd04alteVxZID2K1yMo12CnrukdKDkOVRwrobx8aDMBt Y19U8XHR2wN/IxBmSr+mNvpHlUWqvl6hcX7u2pYSkby5AVLIG09gd/eOd KCc7tftA82X+R1/QrCk0NwCW+ZFfAiRTWA5RgKfvQAFyEQiHRAXlmxjV3 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArAFANy3p1OtJV2Z/2dsb2JhbABZgw2BLKozAQEBAQEBBQGaPBZ1hAo6UQE+QicEiFWZGax1F4VjjE2BFgSaTIs1iC6DQoIw
X-IronPort-AV: E=Sophos;i="5.01,527,1400025600"; d="scan'208";a="55142604"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-5.cisco.com with ESMTP; 23 Jun 2014 05:17:59 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s5N5HxRK006755 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tls@ietf.org>; Mon, 23 Jun 2014 05:17:59 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.143]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Mon, 23 Jun 2014 00:17:58 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "<tls@ietf.org>" <tls@ietf.org>
Thread-Topic: Resolution on gmt_time
Thread-Index: AQHPjqJ/wY/3f0zKxEu+heHKOI3tZw==
Date: Mon, 23 Jun 2014 05:17:58 +0000
Message-ID: <338B3B88-CCE5-4D79-97DC-1EC7D84891AA@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.33.248.22]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FA3250BE673E314ABB9A7798B859D544@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/ErOz9OpC29Hfgwwh_1XR7crhmRg
Subject: [TLS] Resolution on gmt_time
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 05:18:01 -0000
Thanks all. Based on the list discussion, the chairs believe there is rough consensus on the following points: For TLS 1.3: - Remove GMT time from the ClientHello entirely. - Remove GMT time from the ServerHello at the MUST or SHOULD level. For TLS 1.2: - Remove GMT time from the ClientHello entirely. - Remove GMT time from the ServerHello at the SHOULD level. Next steps for TLS 1.3 are as follows: The editor is directed to remove GMT time from both random values and open an issue as to whether or not the ServerHello can have a time value in it. Next steps for TLS 1.2 are as follows: Absent any objections, the chairs intend to adopt draft-matthewson as a WG draft. Anyone who objects to this, please say something by Friday June 27. Joe (For the chairs)
- [TLS] Resolution on gmt_time Joseph Salowey (jsalowey)
- Re: [TLS] Resolution on gmt_time Eric Rescorla
- Re: [TLS] Resolution on gmt_time Dan Wing
- Re: [TLS] Resolution on gmt_time Eric Rescorla