NFD » ndn-cxx

As I proposed in #1705 note-13, the string representation can have the following form:

default:
id:/my-identity
key:/my-identity/ksk-1
cert:/my-identity/KEY/ksk-1/ID-CERT/%FD%01
sha256:

20151027 conference call approves this feature.

The design is changed to:

• Empty string represents default signing.
• id key cert (as in note-1 design) represents signing by identity/key/certificate.
• id:/localhost/identity/digest-sha256 (#1705) represents signing with SHA256 digest.

Here is a rough change I made based on my understanding:
http://gerrit.named-data.net/#/c/2601/1

A couple questions I had regarding this issue: -- editted after gaining more implied information

1. Is the new string an alternative to the current SignerType and Name constructor? (Original should not be replaced)

   alternative, storing the SignerType and SignerName properties the same way as the original

2. Would it be a good idea to use the for parsing the input signing string? Will it compile on all platforms?

   regex does not need to be used in this case

3. How should the default signing for SigningInfo be represented, denoted by empty string input?

   use the default constructor, SigningInfo()

4. What does 'implement the encoding procedure as the stream output operator of SigningInfo type' in the issue statement refer to?

   used in representing SigningInfo constructor strings that were passed in to create the SigningInfo

5. What kind of error-handling should occur when an input string does not match any of the conditions (not matching default, id, sha, key or cert)?

   throw std::invalid_argument is to be used

6. Are the prefixes 'id:', 'key:' and 'cert:' apart of the signing string input?

   Are scheme identifiers, but are not a part of the actual signing names that start with '/'

7. Once a match indicating the kind of signing method to be used has been detected, should the currently implemented set signing methods be used?

   seems to be the way to go

8. How should digest algorithm and signature info of SigningInfo be represented in the output stream operator overloading?
   output stream operator is for using SigningInfo and outputting the string representation format that the constructor would take

new questions

1. Should the == operator be overloaded to be used for SigningInfo comparison?