PageRenderTime 39ms CodeModel.GetById 14ms RepoModel.GetById 0ms app.codeStats 0ms

/PcapDotNet/src/PcapDotNet.Packets/Dns/ResourceData/DnsSinkCodingSubcoding.cs

#
C# | 280 lines | 42 code | 35 blank | 203 comment | 0 complexity | f940ed04b51d9f1ea750f370d9a51076 MD5 | raw file
Possible License(s): BSD-3-Clause
  1. namespace PcapDotNet.Packets.Dns
  2. {
  3. /// <summary>
  4. /// Eastlake.
  5. /// </summary>
  6. public enum DnsSinkCodingSubCoding : ushort
  7. {
  8. /// <summary>
  9. /// Undefined value.
  10. /// </summary>
  11. None = 0x0000,
  12. /// <summary>
  13. /// The SNMP subset of ASN.1.
  14. /// Basic Encoding Rules.
  15. /// </summary>
  16. Asn1SnmpBasicEncodingRules = 0x0101,
  17. /// <summary>
  18. /// The SNMP subset of ASN.1.
  19. /// Distinguished Encoding Rules.
  20. /// </summary>
  21. Asn1SnmpDistinguishedEncodingRules = 0x0102,
  22. /// <summary>
  23. /// The SNMP subset of ASN.1.
  24. /// Packed Encoding Rules Aligned.
  25. /// </summary>
  26. Asn1SnmpPer = 0x0103,
  27. /// <summary>
  28. /// The SNMP subset of ASN.1.
  29. /// Packed Encoding Rules Unaligned.
  30. /// </summary>
  31. Asn1SnmpPerUnaligned = 0x0104,
  32. /// <summary>
  33. /// The SNMP subset of ASN.1.
  34. /// Canonical Encoding Rules.
  35. /// </summary>
  36. Asn1SnmpCanonicalEncodingRules = 0x0105,
  37. /// <summary>
  38. /// The SNMP subset of ASN.1.
  39. /// An OID preceded by a one byte unsigned length appears at the beginning of the data area to indicate which private encoding.
  40. /// </summary>
  41. Asn1SnmpPrivate = 0x01FE,
  42. /// <summary>
  43. /// OSI ASN.1 1990 [ASN.1].
  44. /// Basic Encoding Rules.
  45. /// </summary>
  46. Asn1Osi1990BasicEncodingRules = 0x0201,
  47. /// <summary>
  48. /// OSI ASN.1 1990 [ASN.1].
  49. /// Distinguished Encoding Rules.
  50. /// </summary>
  51. Asn1Osi1990DistinguishedEncodingRules = 0x0202,
  52. /// <summary>
  53. /// OSI ASN.1 1990 [ASN.1].
  54. /// Packed Encoding Rules Aligned.
  55. /// </summary>
  56. Asn1Osi1990Per = 0x0203,
  57. /// <summary>
  58. /// OSI ASN.1 1990 [ASN.1].
  59. /// Packed Encoding Rules Unaligned.
  60. /// </summary>
  61. Asn1Osi1990PerUnaligned = 0x0204,
  62. /// <summary>
  63. /// OSI ASN.1 1990 [ASN.1].
  64. /// Canonical Encoding Rules.
  65. /// </summary>
  66. Asn1Osi1990CanonicalEncodingRules = 0x0205,
  67. /// <summary>
  68. /// OSI ASN.1 1990 [ASN.1].
  69. /// An OID preceded by a one byte unsigned length appears at the beginning of the data area to indicate which private encoding.
  70. /// </summary>
  71. Asn1Osi1990Private = 0x02FE,
  72. /// <summary>
  73. /// OSI ASN.1 1994.
  74. /// Basic Encoding Rules.
  75. /// </summary>
  76. Asn1Osi1994BasicEncodingRules = 0x0301,
  77. /// <summary>
  78. /// OSI ASN.1 1994.
  79. /// Distinguished Encoding Rules.
  80. /// </summary>
  81. Asn1Osi1994DistinguishedEncodingRules = 0x0302,
  82. /// <summary>
  83. /// OSI ASN.1 1994.
  84. /// Packed Encoding Rules Aligned.
  85. /// </summary>
  86. Asn1Osi1994Per = 0x0303,
  87. /// <summary>
  88. /// OSI ASN.1 1994.
  89. /// Packed Encoding Rules Unaligned.
  90. /// </summary>
  91. Asn1Osi1994PerUnaligned = 0x0304,
  92. /// <summary>
  93. /// OSI ASN.1 1994.
  94. /// Canonical Encoding Rules.
  95. /// </summary>
  96. Asn1Osi1994CanonicalEncodingRules = 0x0305,
  97. /// <summary>
  98. /// OSI ASN.1 1994.
  99. /// An OID preceded by a one byte unsigned length appears at the beginning of the data area to indicate which private encoding.
  100. /// </summary>
  101. Asn1Osi1994Private = 0x03FE,
  102. /// <summary>
  103. /// Private abstract syntax notations.
  104. /// This coding value will not be assigned to a standard abstract syntax notation.
  105. /// An OSI Object Identifier (OID) preceded by a one byte unsigned length appears at the beginning of the data area to indicate which private abstract syntax is being used.
  106. /// Basic Encoding Rules.
  107. /// </summary>
  108. AsnPrivateBasicEncodingRules = 0x3F01,
  109. /// <summary>
  110. /// Private abstract syntax notations.
  111. /// This coding value will not be assigned to a standard abstract syntax notation.
  112. /// An OSI Object Identifier (OID) preceded by a one byte unsigned length appears at the beginning of the data area to indicate which private abstract syntax is being used.
  113. /// Distinguished Encoding Rules.
  114. /// </summary>
  115. AsnPrivateDistinguishedEncodingRules = 0x3F02,
  116. /// <summary>
  117. /// Private abstract syntax notations.
  118. /// This coding value will not be assigned to a standard abstract syntax notation.
  119. /// An OSI Object Identifier (OID) preceded by a one byte unsigned length appears at the beginning of the data area to indicate which private abstract syntax is being used.
  120. /// Packed Encoding Rules Aligned.
  121. /// </summary>
  122. AsnPrivatePer = 0x3F03,
  123. /// <summary>
  124. /// Private abstract syntax notations.
  125. /// This coding value will not be assigned to a standard abstract syntax notation.
  126. /// An OSI Object Identifier (OID) preceded by a one byte unsigned length appears at the beginning of the data area to indicate which private abstract syntax is being used.
  127. /// Packed Encoding Rules Unaligned.
  128. /// </summary>
  129. AsnPrivatePerUnaligned = 0x3F04,
  130. /// <summary>
  131. /// Private abstract syntax notations.
  132. /// This coding value will not be assigned to a standard abstract syntax notation.
  133. /// An OSI Object Identifier (OID) preceded by a one byte unsigned length appears at the beginning of the data area to indicate which private abstract syntax is being used.
  134. /// Canonical Encoding Rules.
  135. /// </summary>
  136. AsnPrivateCanonicalEncodingRules = 0x3F05,
  137. /// <summary>
  138. /// Private abstract syntax notations.
  139. /// This coding value will not be assigned to a standard abstract syntax notation.
  140. /// An OSI Object Identifier (OID) preceded by a one byte unsigned length appears at the beginning of the data area to indicate which private abstract syntax is being used.
  141. /// An OID preceded by a one byte unsigned length appears in the data area just after the coding OID.
  142. /// </summary>
  143. AsnPrivatePrivate = 0x3FFE,
  144. /// <summary>
  145. /// MIME structured data [RFC 2045, 2046].
  146. /// The data portion is a MIME structured message.
  147. /// The "MIME-Version:" header line may be omitted unless the version is other than "1.0".
  148. /// Note that, to some extent, the size limitations of DNS RRs may be overcome in the MIME case by using the "Content-Type: message/external-body" mechanism.
  149. /// 7 bit.
  150. /// </summary>
  151. Mime7Bit = 0x4101,
  152. /// <summary>
  153. /// MIME structured data [RFC 2045, 2046].
  154. /// The data portion is a MIME structured message.
  155. /// The "MIME-Version:" header line may be omitted unless the version is other than "1.0".
  156. /// Note that, to some extent, the size limitations of DNS RRs may be overcome in the MIME case by using the "Content-Type: message/external-body" mechanism.
  157. /// 8 bit.
  158. /// </summary>
  159. Mime8Bit = 0x4102,
  160. /// <summary>
  161. /// MIME structured data [RFC 2045, 2046].
  162. /// The data portion is a MIME structured message.
  163. /// The "MIME-Version:" header line may be omitted unless the version is other than "1.0".
  164. /// Note that, to some extent, the size limitations of DNS RRs may be overcome in the MIME case by using the "Content-Type: message/external-body" mechanism.
  165. /// Binary.
  166. /// </summary>
  167. MimeBinary = 0x4103,
  168. /// <summary>
  169. /// MIME structured data [RFC 2045, 2046].
  170. /// The data portion is a MIME structured message.
  171. /// The "MIME-Version:" header line may be omitted unless the version is other than "1.0".
  172. /// Note that, to some extent, the size limitations of DNS RRs may be overcome in the MIME case by using the "Content-Type: message/external-body" mechanism.
  173. /// Quoted-printable.
  174. /// </summary>
  175. MimeQuotedPrintable = 0x4104,
  176. /// <summary>
  177. /// MIME structured data [RFC 2045, 2046].
  178. /// The data portion is a MIME structured message.
  179. /// The "MIME-Version:" header line may be omitted unless the version is other than "1.0".
  180. /// Note that, to some extent, the size limitations of DNS RRs may be overcome in the MIME case by using the "Content-Type: message/external-body" mechanism.
  181. /// Base 64.
  182. /// </summary>
  183. MimeBase64 = 0x4105,
  184. /// <summary>
  185. /// MIME structured data [RFC 2045, 2046].
  186. /// The data portion is a MIME structured message.
  187. /// The "MIME-Version:" header line may be omitted unless the version is other than "1.0".
  188. /// Note that, to some extent, the size limitations of DNS RRs may be overcome in the MIME case by using the "Content-Type: message/external-body" mechanism.
  189. /// The data portion must start with an "x-" token denoting the private content-transfer-encoding immediately followed by one null (zero) octet
  190. /// followed by the remainder of the MIME object.
  191. /// </summary>
  192. MimePrivate = 0x41FE,
  193. /// <summary>
  194. /// Text tagged data.
  195. /// The data potion consists of text formated as specified in the TXT RR except that the first and every subsequent odd numbered text item
  196. /// is considered to be a tag labeling the immediately following text item.
  197. /// If there are an odd number of text items overall, then the last is considered to label a null text item.
  198. /// Syntax of the tags is as specified in RFC 1738 for the "Common Internet Scheme Syntax" without the two leading slashes ("//").
  199. /// Thus any organization with a domain name can assign tags without fear of conflict.
  200. /// ASCII.
  201. /// </summary>
  202. TextTaggedDataAscii = 0x4201,
  203. /// <summary>
  204. /// Text tagged data.
  205. /// The data potion consists of text formated as specified in the TXT RR except that the first and every subsequent odd numbered text item
  206. /// is considered to be a tag labeling the immediately following text item.
  207. /// If there are an odd number of text items overall, then the last is considered to label a null text item.
  208. /// Syntax of the tags is as specified in RFC 1738 for the "Common Internet Scheme Syntax" without the two leading slashes ("//").
  209. /// Thus any organization with a domain name can assign tags without fear of conflict.
  210. /// UTF-7 [RFC 1642].
  211. /// </summary>
  212. TextTaggedDataUtf7 = 0x4202,
  213. /// <summary>
  214. /// Text tagged data.
  215. /// The data potion consists of text formated as specified in the TXT RR except that the first and every subsequent odd numbered text item
  216. /// is considered to be a tag labeling the immediately following text item.
  217. /// If there are an odd number of text items overall, then the last is considered to label a null text item.
  218. /// Syntax of the tags is as specified in RFC 1738 for the "Common Internet Scheme Syntax" without the two leading slashes ("//").
  219. /// Thus any organization with a domain name can assign tags without fear of conflict.
  220. /// UTF-8 [RFC 2044].
  221. /// </summary>
  222. TextTaggedDataUtf8 = 0x4203,
  223. /// <summary>
  224. /// Text tagged data.
  225. /// The data potion consists of text formated as specified in the TXT RR except that the first and every subsequent odd numbered text item
  226. /// is considered to be a tag labeling the immediately following text item.
  227. /// If there are an odd number of text items overall, then the last is considered to label a null text item.
  228. /// Syntax of the tags is as specified in RFC 1738 for the "Common Internet Scheme Syntax" without the two leading slashes ("//").
  229. /// Thus any organization with a domain name can assign tags without fear of conflict.
  230. /// ASCII with MIME header escapes [RFC 2047].
  231. /// </summary>
  232. TextTaggedDataAsciiMimeHeaderEscapes = 0x4204,
  233. /// <summary>
  234. /// Text tagged data.
  235. /// The data potion consists of text formated as specified in the TXT RR except that the first and every subsequent odd numbered text item
  236. /// is considered to be a tag labeling the immediately following text item.
  237. /// If there are an odd number of text items overall, then the last is considered to label a null text item.
  238. /// Syntax of the tags is as specified in RFC 1738 for the "Common Internet Scheme Syntax" without the two leading slashes ("//").
  239. /// Thus any organization with a domain name can assign tags without fear of conflict.
  240. /// Each text item must start with a domain name [RFC 1034] denoting the private text encoding immediately followed by one null (zero) octet
  241. /// followed by the remainder of the text item.
  242. /// </summary>
  243. TextTaggedDataPrivate = 0x42FE,
  244. }
  245. }