Medianet Files

Dhcp configuration generation tool
----------------------------------

sdcat is a tool meant to generate the configuration data for Service
Discovery on DHCPv4 in the format required by different DHCP servers.
The goal is to provide a way to write human friendly configuration files and
produce the required data to put into the config file.

The inverse operation is also supported: reading a configuration file,
extracting the Service Discovery parts and presenting them in a human readable
format.

Command invocation
----------------------------------

Usage: sdcat -e|-d <format> -i <in_file> [-o <out_file>]

  -e, --encode
      Encode the human readable format into the destination format
  -d, --decode
      Decode the encoded configuration into an human readable format
  -i, --input
      Specify the input file.
  -o, --output
      Specify the output file. Optional, will use stdout if missing

Supported formats are: ISC CNR Windows

For example: ./sdcat -e ISC -i in.txt -o out.conf

Report bugs to support-msi@cisco.com.

Configuration file format
---------------------------------

See samples/simple.txt in the source distribution for a simple
example of the config file format.

The input file will be a description of the Service Description options in an
easily readable format

# Lines starting with a # are comments, and are ignored
# The # must be the at the beginnning of the line
#
# EnterpriseID is the first item. Cisco assigned value is 9
EnterpriseID = 9

# The second item will be the name given to the Dhcp option inside the
# configuration file
# Option name needs to be an identifier: a letter optionally followed by other
# letters, numbers, dash and underscores.
# option-1_-25 is a good identifier
# _option125 is not
OptionName = option-125

# After enterprise id and option name, the actual configuration of Service
# Discovery begins.
# A group is just a named regroupment of rules.
# A rule is composed by an item to match, followed by one or more entries to
# reply, up to 31 entries.

# The group name is a string. You can put anything on a string, but not
# printable characters must be escaped. String must be on a single line.
# The group will containing a set of rules, enclosed in curly braces.
# Syntax is:
#            Group = "Name in string form" { .... }
#
Group = "A named\ngrou\x20p" {

# A match is just a string that will be compared with the data sent by the
# client. String rules apply.
# Syntax is:
#            Match = "String to match"
    Match = "SOME:Service:To  match"

# An entry contains the data needed to contact the service provider.
# It's composed of an IPv4 address in dotted quad notation, a port and a
# transport protocol (TCP or UDP).
# The port can be specified as a number or as a service name.
# Syntax is:
#            IP/PORT/PROTO
    Entry = 10.10.10.10 / http / TCP
    Entry = 20.20.20.20 / 80 / UDP

}



# Whitespace is not important, so you can format the file as it suits better.
# The following are legal examples
Group=
"Group_A" {
Match="Match1" Entry=10.10.10.10/10/TCP
}