Changes between Version 71 and Version 72 of ExDescLang


Ignore:
Timestamp:
Nov 5, 2010 5:08:31 PM (14 years ago)
Author:
sunshine
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ExDescLang

    v71 v72  
    4545
    4646The entire system has a domain knowledge database that contains domain-specific information, such as:
    47   * Context:
     47  * Context: This will probably be expressed in a mix of [CurrentlyProposedLanguage] and regular expressions
    4848   * what is an IP address
    4949   * what is an IP flow
    … …  
    5353   * what is an HTTP request/reply, what makes a reply match the request
    5454   * what is the syntax of a DNS record
    55   * Parameterization:
     55  * Parameterization: This will probably be expressed using [CurrentlyProposedLanguage]
    5656   * for each type of object and each type of event in any metadescription what kind of parameters can be defined. E.g., for HTTP request this would be timing of requests and content of requests (type=GET/PUT/POST, filename). Note that this is divorced from the actual generator of such event, parameters are strictly related to events, regardless of how they are generated.
    57   * Relationships:
    58    * One type of traffic induces another: HTTP traffic leads to DNS traffic leads to ARP traffic
    59    * Nodes have IP and ARP addresses per each interface
    60    * Web files may contain forms that require user input
    61    * HTTP replies depend on Web files stored at a server-specific location
    62    * DNS records reside in caches and have info about name=address mappings, and info about authorities for domains
    6357
    6458The context part would be mostly populated by us. The parameterization and relationship parts would be seeded by us but then extended by other experts that create meta-descriptions. There is an automated way of identifying unknowns from a meta-description that must be defined in the knowledge DB.
    6559
    66 = Generator Descriptions =
     60= Generator Library =
    6761
    6862Our system keeps the following info about each generator:
    … …  
    7468  * How the parameters can be customized, e.g., randomized, input by user, selected from a list ...
    7569  * Other inputs of the generator, their range of values and their relationship to the parameters from the above two items
     70This information is expressed using [CurrentlyProposedLanguage] and fixed section/function names
     71
     72= Function Library =
     73
     74We have a library of functions such as:
     75  * Getting an IP address of a node, or an ARP address or DNS name
     76  * What does it mean for a request to match a reply for a given request/reply subclass (e.g., DNS request/reply)
     77These will likely be expressed using [CurrentlyProposedLanguage]
    7678
    7779= Mapping elements of Meta-description to generators during experiment design =