A B D E H I M O Q R S T

RFC6759

/in /by

 

RFC6759 Metadata Components

  • http://www.rfc-editor.org/rfc/rfc6759.txt
  • https://datatracker.ietf.org/doc/rfc6759/
  • General DNS-AS TXT record syntax: “CISCO-CLS=<option>:<val>{|<option>:<val>}*”
  • Option-value pairs may appear in the same record, separated by a pipe character ‘|’.
  • Example for such a TXT record with app metadata would be: “CISCO-CLS=app-name:EXCHANGE“

Supported Attributes:

  • Application Name
  • Application ID (as in RFC 6759)
  • Application Category
  • Application Sub-Category
  • Attributes (tunneled, encrypted, p2p)
  • Traffic Class (QoS)
  • Business Relevance
  • Server Port Range (to identify an application with ports)
  • IP Protocol Specifier
  • IP Version Specifier
  • Min/Avg/Max Bandwidth consumption
  • Max. Possible Packet Loss (in %)
  • Max. Possible Jitter (in ms.)
  • Max. Possible Latency (in ms.)
  • Source of Metadata (NBAR2, DNS-AS server etc.)