ODF 1.2 Part 3 4.8.5 manifest:initialisation-vector underspecified

Replace the text of 4.8.5 manifest:inittialisation-vector with

"""
The manifest:initialisation-vector attribute carries the value of a binary sequence employed in initializing encryption and decryption using the specified algorithm. The left-to-right sequence of octets that contains the successive, left-adjusted bits of the value are represented in the attribute value using base64binary encoding. There shall be enough bits in the value to satisfy the requirements of the specified algorithm.

Note: The default Blowfish algorithm requires a 64-bit (8-octet) initialization vector for cipher-feedback (CFB) initialization. The initialization vector is used in CFB (and CBC) initialization to ensure that the same initial plaintext will not have the same initial ciphertext when the same derived key is used with more than one file. The initialization vector serves many of the same purposes as a key-derivation salt. Distinct initialization vectors derived from timestamps are useful for avoiding initialization-vector collisions. See [Blowfish] for more information on initialization vectors.
"""

1. In the schema definition for algorithm-attlist, make the manifest:initialization-vector attribute optional.

2. In section 4.8.5 manifest:initialisation-vector change the first sentence from
"""
"The manifest:initialization vector specifies the byte-sequence used as an initialization vector to a encryption algorithm.
"""
to
"""
The optional manifest:initialisation-vector attribute value provides the byte-sequence for the initialization vector used by the encryption algorithm when delivery of a required initialization vector is not specified as part of the encryption algorithm definition.
"""

Also in 4.8,5, add the final sentence:
"""
The format and length of the initialization vector, in bytes, shall be as required by the encryption algorithm specification.
"""