ndn-sci

I owe you guys a proposal for the configuration file, and here it is. Let me know if you have any questions.

; The query section contains settings of queryAdapter
query
{
prefix ndn:/cmip5/test ; Set the prefix that the QueryAdapter is listening on
; the prefix would be further separated to prefix/query-results and prefix/query
signingId ndn:/cmip5/test/query/singingId ; Set the Identity that signs data which answers the queries
; The database section contains settings of database
database
{
dbServer 127.0.0.1 ; Specify the database server
dbName cmip5-test ; Specify the database name
dbUser testUser2 ; Specify the database user name
dbPasswd test123 ; Specify the associated password for the dbUser
}
}
; The publish section contains settings of publishAdapter
publish
{
prefix ndn:/cmip5/test/publish ; Set the prefix that the PublishAdapter is listening on
signingId ndn:/cmip5/test/publish/singingId ; Set the identity that signs the published data
; ; The published_file_security section contains the rules for the adapter to verify the published files
; ; indeed come from a valid publisher.
; published_file_security
; {
; }
; The database section contains settings of database
; The user in publishAdapter may differ from the one in queryAdapter, to provide different access control
database
{
dbServer 127.0.0.1 ; Specify the database server
dbName cmip5-test ; Specify the database name
dbUser testUser2 ; Specify the database user name
dbPasswd test123 ; Specify the associated password for the dbUser
}
sync
{
prefix ndn:/ndn/broadcast ; Set the prefix for sync messages, default 'ndn:/ndn/broadcast'
; ; The sync_data_security section contains the rules that are required for ChronoSync nodes to
; ; verify published data by other ChronoSync nodes.
; ; The ChronoSync validator will be disabled when sync_data_security section is missing.
; sync_data_security
; {
; ; ; This section defines the trust model for the ChronoSync data Management. It consists of rules and
; ; ; trust-anchors, which are briefly defined in this file.
; ; rule
; ; {
; ; id "NDN Testbed Hierarchy Rule"
; ; for data ; rule for Data (to validate NDN certificates)
; ; filter
; ; {
; ; type name ; condition on data name
; ; regex ^[]<><>$
; ; }
; ; checker
; ; {
; ; type hierarchical ; the certificate name of the signing key and
; ; ; the data name must follow the hierarchical model
; ; sig-type rsa-sha256 ; data must have a rsa-sha256 signature
; ; }
; ; }
; ; trust-anchor
; ; {
; ; type file
; ; file-name keys/default.ndncert ; the file name, by default this file should be placed in the
; ; ; same folder as this config file.
; ; }
; }
}
}

Here is the new version based on the discussion on May 5th afternoon.

As suggested, I move the prefix out of subsections, as a generic prefix for the catalog. And the subsections are named as queryAdapter and publishAdapter.

; The catalog section contains settings of catalog
catalog
{
prefix ndn:/cmip5/catalog ; Set the catalog prefix, so that adapters can extend it as their own prefix
; e.g., QueryAdapter has the prefix "ndn:/cmip5/catalog/query" and "ndn:/cmip5/catalog/query-results"
; PublishAdapter has the prefix "ndn:/cmip5/catalog/publish"
; The query section contains settings of queryAdapter
queryAdapter
{
signingId ndn:/cmip5/test/query/singingId ; Set the Identity that signs data that responds the queries
; The database section contains settings of database for QueryAdapter
database
{
dbServer 127.0.0.1 ; Specify the database server
dbName cmip5-test ; Specify the database name
dbUser testUser2 ; Specify the database user name
dbPasswd test123 ; Specify the associated password for the dbUser
}
}
; The publish section contains settings of publishAdapter
publishAdapter
{
signingId ndn:/cmip5/test/publish/singingId ; Set the identity that signs published data
; ; The published_file_security section contains the rules for the adapter to verify the published files
; ; indeed come from a valid publisher.
; published_file_security
; {
; }
; The database section contains settings of database
; The user in publishAdapter may differ from the one in queryAdapter, to provide different access control
database
{
dbServer 127.0.0.1 ; Specify the database server
dbName cmip5-test ; Specify the database name
dbUser testUser2 ; Specify the database user name
dbPasswd test123 ; Specify the associated password for the dbUser
}
; The sync section contains settings of ChronoSync
sync
{
prefix ndn:/ndn/broadcast ; Set the prefix for sync messages, default 'ndn:/ndn/broadcast'
; ; The sync_data_security section contains the rules that are required for ChronoSync nodes to
; ; verify published data by other ChronoSync nodes.
; ; The ChronoSync validator will be disabled when sync_data_security section is missing.
; sync_data_security
; {
; ; ; This section defines the trust model for the ChronoSync data Management. It consists of rules and
; ; ; trust-anchors, which are briefly defined in this file. Multiple rules can be included.
; ; rule
; ; {
; ; id "ChronoSync Messages Rule"
; ; for data ; rule for Data (to validate NDN certificates)
; ; filter
; ; {
; ; type name ; condition on data name
; ; regex ^[]<><>$
; ; }
; ; checker
; ; {
; ; type hierarchical ; the certificate name of the signing key and
; ; ; the data name must follow the hierarchical model
; ; sig-type rsa-sha256 ; data must have a rsa-sha256 signature
; ; }
; ; }
; ; trust-anchor
; ; {
; ; type file
; ; file-name keys/default.ndncert ; the file name, by default this file should be placed in the
; ; ; same folder as this config file.
; ; }
; }
}
}
}