TODO: Mark Better unique ID task as done

2 files changed, 10 insertions, 12 deletions

diff --git a/TODO b/TODO
index 9dc57fcc..3b9a5ab9 100644
--- a/TODO
+++ b/TODO
@@ -80,18 +80,6 @@ SMS
   Complexity: C1
   Owner: Kristen Carlson Accardi <kristen@linux.intel.com>
 
-- Better unique ID for incoming / outgoing messages.  Currently oFono uses
-  a simple incremental counter stored in the settings store (NextMessageId).
-  This tends to break quite easily in strange situations (e.g. forced battery
-  removal, unexpected crashes).  This makes the uniqueness of this ID not
-  always guaranteed.
-
-  Proposed solution is to base the ID on SHA1 or MD5 hash.  Hash the contents
-  of the message + reception / sent time and the sender / originator address.
-
-  Priority: High
-  Complexity: C1
-
 - SMS Status Report support support according to 3GPP 23.040.  oFono should
   support SMS start reports.  For fragmented SMS messages oFono should take
   care of collating the status reports for each fragment and notifying once
diff --git a/doc/features.txt b/doc/features.txt
index 27ec74e3..534b8deb 100644
--- a/doc/features.txt
+++ b/doc/features.txt
@@ -86,3 +86,13 @@ Envelopes:
   and on a channel listed in EFcbmid, it is dispatched to the SIM using the
   CBS-PP Download envelope.  No user interaction is required or signaled
   whenever this occurs.
+
+Short Messaging Service
+=======================
+
+- Unique identifier for incoming and outgoing SMS messages.  Whenever a
+  message is received or sent by oFono, a unique ID is generated for that
+  message.  The id is relevant to all segments of an SMS and in the case of
+  incoming messages is only generated when the SMS is fully assembled.  The
+  hash used is SHA1.  This unique identifier is used to identify the SMS
+  message to history plugins as well.