Since the name is the hash value of the public key, it is a cryptic string of hexadecimal digits that is not user-friendly. The encoding does not specify the hash algorithm used to generate the name. The hash algorithm must be transferred out of band. This encoding scheme is used to authenticate and distribute a DH public value, for cases where the entity's name is the message digest of the public value. The following is how the public value is encoded for purposes of message digest computation and distribution in the network.
All values are in network order.
Prime contains the binary representation of the DH prime with the most significant byte first. Generator is the binary representation of generator with the most significant byte first. The Name associated with the public key and parameters is the cryptographic hash of the above encoding. When using this instead of signed certificates, certificate verification must be done by performing the message digest computation. The unsigned DH public value can only be used when entities are named using the message digest of their DH public value and these names are securely communicated.