Re: [MMUSIC] base64 and datetimes in 2326bis
Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 07 October 2013 12:45 UTC
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D8B621E81C6 for <mmusic@ietfa.amsl.com>; Mon, 7 Oct 2013 05:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.206
X-Spam-Level:
X-Spam-Status: No, score=-105.206 tagged_above=-999 required=5 tests=[AWL=1.043, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, 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 ji3Y4oSDjYwz for <mmusic@ietfa.amsl.com>; Mon, 7 Oct 2013 05:45:42 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 220AC21E81F5 for <mmusic@ietf.org>; Mon, 7 Oct 2013 05:45:33 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f738e000003ee3-c2-5252aceb3d76
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 52.A3.16099.BECA2525; Mon, 7 Oct 2013 14:45:32 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.26) with Microsoft SMTP Server id 14.2.328.9; Mon, 7 Oct 2013 14:44:12 +0200
Message-ID: <5252ACCC.50303@ericsson.com>
Date: Mon, 07 Oct 2013 14:45:00 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <52446E97.8030700@stpeter.im>
In-Reply-To: <52446E97.8030700@stpeter.im>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFLMWRmVeSWpSXmKPExsUyM+Jvre6bNUFBBit+CVssvLOZ3WLq8scs Fsf29DM7MHtsffeO0WPJkp9MHnP3vGAOYI7isklJzcksSy3St0vgylj0uIul4JRuxYc9U5kb GFcrdzFycEgImEh0rc3rYuQEMsUkLtxbz9bFyMUhJHCYUWLT+YVQzjJGiefzW1hAqngFNCWe f1zDDmKzCKhIzPl0mBXEZhOwkLj5o5ENxBYVCJZo3/6VDaJeUOLkzCdgvSICWhKXrvWB9TIL uEjsmdYK1issYCqxf3Y7I4gtBDL//msmEJsTqP7ogensENdJSmxbdAyqV09iytUWRghbXqJ5 62xmiF5tiYamDtYJjEKzkKyehaRlFpKWBYzMqxjZcxMzc9LLDTcxAsP34JbfujsYT50TOcQo zcGiJM774a1zkJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQZGm6DDm/tCVq9KbUoJuzH75IPI Q7Xhe/mc+BYq/u74cr1ycW1g30/v3Oyy7Ru7c+8zya1N0bvWf2b/onsKGpUHTKOe3j7yoU3v peaqBQL6GYoHe5+9mXyoW+kpk5PwA8nVIo+VoxNULu7nWLQk3WfD7Qc1PraSfaX7JpouFwpa mdvU8Ga/vFWBEktxRqKhFnNRcSIAvJMC0i0CAAA=
Cc: mmusic@ietf.org, Claudio Allocchio <Claudio.Allocchio@garr.it>
Subject: Re: [MMUSIC] base64 and datetimes in 2326bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Oct 2013 12:45:54 -0000
Hi Peter, Thanks for your feedback, and see inline. Especially on the DATE and Time issue I would appreciate feedback. On 2013-09-26 19:27, Peter Saint-Andre wrote: > Here is some brief feedback on 2326bis. I'm sorry that I don't > have time for a longer review. > > BASE64 > > The usages of Base64 do not specify which exact encoding of Base64 > they require and what to do about padding bits. For example, > Section 18.54 says: > > The binary MIKEY message SHALL be Base64 [RFC4648] encoded before > being included in the value part of the parameter. > > If the specification assumes that the rules from Section 4 of RFC > 4648 are to be used, that text would be more accurate as: > > The binary MIKEY message SHALL be BASE64 [RFC4648] encoded before > being included in the value part of the parameter, where the > encoding adheres to the definition in Section 4 of RFC 4648 and > where the padding bits are set to zero. Yes, you are correct, it is the Section 4 BASE64 mode of the RFC that we want to use here. This will effect three places: Section 18.2: Each credential MUST consist of one URI identifying the proxy or server, the hash algorithm identifier, and the hash over that agent's ASN.1 distinguished encoding rules (DER) encoded certificate [RFC5280] in BASE64, according to Section 4 of [RFC4648] and where the padding bits are set to zero. Section 18.13: The header MUST include the URI of the next hop (proxy or server) and a BASE64 (according to Section 4 of [RFC4648] and where the padding bits are set to zero) encoded binary structure containing a sequence of DER encoded X.509v3 certificates [RFC5280]. Section 18.54: Under MIKEY parameter This parameter can be included both in request and response messages. The binary MIKEY message SHALL be BASE64 [RFC4648] encoded before being included in the value part of the parameter, where the encoding adheres to the definition in Section 4 of RFC 4648 and where the padding bits are set to zero. > > DATETIME FORMATS > > Section 4.4.3 seems to be underspecified: > > Absolute time is expressed as ISO 8601 [ISO.8601.2000] timestamps, > using UTC (GMT). Fractions of a second may be indicated. > > Example for clock format range request for a starting time of > November 8, 1996 at 14h 37 min and 20 and a quarter seconds UTC > playing for 10 min and 5 seconds, a Media-Properties header's > "Time- Limited UTC property for 24th of December 2014 at 15 hours > and 00 mins, and a Terminate-Readon headers "time" property for > 18th of June 2013 at 16 hours, 12 minutes and 56 seconds: > > clock=19961108T143720.25Z-19961108T144725.25Z > Time-Limited=20141224T1500Z time=20130618T161256Z > > ISO 8601 has many profiles. Is the profile defined in RFC 3339 > supported? That would result in a datetime of the following form: > > 1996-11-08T14:37:20.25Z > > Also are timezone offsets allowed? > > If the answers are "no" then it would be good to explain that in > the text. The answers are no on both accounts. The reasons is really the ABNF syntax specified since RTSP 1.0 for this. Thus, I have written a new more complete specification for this time format that matches the ABNF and still uses ISO 8601 relevant sections for some clarifications and specifications. Feedback are much appreciated if you think this is complete. 4.4.3. Absolute Time Absolute time is expressed following a specific types of ISO 8601 [ISO.8601.2000] based timestamps. The date is complete representation calendar date in basic format (YYYYMMDD) without separators (per Section 5.2.1.1 of [ISO.8601.2000]). The time of day is provided in the complete representation basic format (hhmmss) as specified in Section 5.3.1.1 of [ISO.8601.2000], allowing decimal fractions of seconds following Section 5.3.1.3 requiring "." (full stop) as decimal separator and limiting the number of digits to no more than nine (9). The time expressed MUST be using UTC (GMT), i.e. no timezone offsets allowed. The full date and time specification is the eight digit date followed by a "T" followed by the six digits time value, optionally followed by a full stop followed by one to nine fractions of a second and ended by "Z", e.g. YYYYMMDDThhmmss.ssZ. The reason for this time format rather than using "Date and Time on the Internet: Timestamps" [RFC3339] are historic and using the format specified in RTSP 1.0. The motivations raised in RFC 3339 applies to why a selection from ISO 8601 was done, but a different and even more restrictive selection was applied in this case. Example for clock format range request for a starting time of November 8, 1996 at 14h 37 min and 20 and a quarter seconds UTC playing for 10 min and 5 seconds, a Media-Properties header's "Time- Limited UTC property for 24th of December 2014 at 15 hours and 00 mins, and a Terminate-Readon headers "time" property for 18th of June 2013 at 16 hours, 12 minutes and 56 seconds: clock=19961108T143720.25Z-19961108T144725.25Z Time-Limited=20141224T1500Z time=20130618T161256Z cheers Magnus Westerlund ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com ----------------------------------------------------------------------
- [MMUSIC] base64 and datetimes in 2326bis Peter Saint-Andre
- Re: [MMUSIC] base64 and datetimes in 2326bis Magnus Westerlund
- Re: [MMUSIC] base64 and datetimes in 2326bis Magnus Westerlund
- Re: [MMUSIC] base64 and datetimes in 2326bis Claudio Allocchio
- Re: [MMUSIC] base64 and datetimes in 2326bis Magnus Westerlund