Creating protobuf for reading list sync

components/sync/protocol/reading_list_specifics.proto

Index: components/sync/protocol/reading_list_specifics.proto
diff --git a/components/sync/protocol/reading_list_specifics.proto b/components/sync/protocol/reading_list_specifics.proto
new file mode 100644
index 0000000000000000000000000000000000000000..4ef91ca4f9e7c3767c6c222e6e797fde9efb1f03
--- /dev/null
+++ b/components/sync/protocol/reading_list_specifics.proto
@@ -0,0 +1,34 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+//
+// Sync protocol datatype extension for the reading list items.
+
+syntax = "proto2";
+
+option optimize_for = LITE_RUNTIME;
+option retain_unknown_fields = true;
+
+package sync_pb;
+
+// Properties of Reading list items..
+message ReadingListSpecifics {
+  optional string entry_id = 1;
+
+  optional string title = 2;
+
+  required string url = 3;
+
+  required int64 creation_time_us = 4;

[lody, 2016/08/12 09:47:55]

What's the "us" stand for?

[Olivier, 2016/08/12 09:58:13]

micro seconds.

[stkhapugin, 2016/08/12 11:25:39]

Is this a universal naming? I've never seen it before. 

[Olivier, 2016/08/12 11:42:21]

Universal, I guess not. Very common yes, especially in context where ascii is
needed.

https://www.google.com/?gfe_rd=cr&ei=7LWtV6yIJJPu8weAoJvoAw&gws_rd=cr&fg=1#q=...

+
+  optional int64 update_time_us = 5;
+
+  enum ReadingListEntryStatus {
+    UNKNOWN = 0;

[stkhapugin, 2016/08/12 09:53:12]

Do we need this? We have no code for such state. 

[Olivier, 2016/08/12 09:58:13]

Removed

+    UNREAD = 1;
+    READ = 2;
+  }
+
+  required ReadingListEntryStatus status = 6;
+}
+