Final block ID is returned to the spec
git-svn-id: svn+ssh://dyadis.cs.arizona.edu/NDN-spec/spec-sphinx@200 c5937c81-b952-4fd9-96ba-3036b240b622
diff --git a/data.rst b/data.rst
index 6296ad3..165392e 100644
--- a/data.rst
+++ b/data.rst
@@ -30,6 +30,7 @@
MetaInfo ::= META-INFO-TYPE TLV-LENGTH
ContentType?
FreshnessPeriod?
+ FinalBlockId?
Compared with CCNx, four fields are removed: PublisherPublicKeyDigest, ExtOpt, Timestamp, and FinalBlockID for the following reasons.
@@ -79,6 +80,20 @@
The effect is the same as if that stale Data did not exist (i.e., the Interest might be matched by some other Data in the store, or, failing that, get forwarded to other nodes).
If an exact duplicate of a stale Data arrives, the effect is the same as if the stale Data had not been present. In particular, the Data in the store is no longer stale. As a practical matter, a stale Data should be ranked high on the list of things to discard from the store when a storage quota has been reached.
+FinalBlockId
+++++++++++++
+
+::
+
+ FinalBlockId ::= FINAL-BLOCK-ID-TLV TLV-LENGTH
+ NameComponent
+
+The optional FinalBlockId indicates the identifier of the final block
+in a sequence of fragments.
+It should be present in the final block itself, and may also be present in other fragments to provide advanced warning of the end to consumers.
+The value here should be equal to the last explicit Name Component of the final block.
+
+
.. _Content:
Content