/// Variable length string of octets containing the ATM address of the node to which this RR pertains.
/// When the format is AESA, the address is coded as described in ISO 8348/AD 2 using the preferred binary encoding of the ISO NSAP format.
/// When the format value is E.164, the Address/Number Digits appear in the order in which they would be entered on a numeric keypad.
/// Digits are coded in IA5 characters with the leftmost bit of each digit set to 0.
/// This ATM address appears in ATM End System Address Octets field (AESA format) or the Address/Number Digits field (E.164 format) of the Called party number information element [ATMUNI3.1].
/// Subaddress information is intentionally not included because E.164 subaddress information is used for routing.
/// A 16-bit unsigned integer specifying the order in which the NAPTR records MUST be processed in order to accurately represent the ordered list of Rules.
/// The ordering is from lowest to highest.
/// If two records have the same order value then they are considered to be the same rule and should be selected based on the combination of the Preference values and Services offered.
/// </summary>
publicushortOrder{get;privateset;}
/// <summary>
/// Although it is called "preference" in deference to DNS terminology, this field is equivalent to the Priority value in the DDDS Algorithm.
/// It specifies the order in which NAPTR records with equal Order values should be processed, low numbers being processed before high numbers.
/// This is similar to the preference field in an MX record, and is used so domain administrators can direct clients towards more capable hosts or lighter weight protocols.
/// A client may look at records with higher preference values if it has a good reason to do so such as not supporting some protocol or service very well.
/// The important difference between Order and Preference is that once a match is found the client must not consider records with a different Order but they may process records with the same Order but different Preferences.
/// The only exception to this is noted in the second important Note in the DDDS algorithm specification concerning allowing clients to use more complex Service determination between steps 3 and 4 in the algorithm.
/// Preference is used to give communicate a higher quality of service to rules that are considered the same from an authority standpoint but not from a simple load balancing standpoint.
///
/// It is important to note that DNS contains several load balancing mechanisms and if load balancing among otherwise equal services should be needed then methods such as SRV records or multiple A records should be utilized to accomplish load balancing.
/// </summary>
publicushortPreference{get;privateset;}
/// <summary>
/// Flags to control aspects of the rewriting and interpretation of the fields in the record.
/// Flags are single characters from the set A-Z and 0-9.
/// The case of the alphabetic characters is not significant.
/// The field can be empty.
///
/// It is up to the Application specifying how it is using this Database to define the Flags in this field.
/// It must define which ones are terminal and which ones are not.
/// </summary>
publicDataSegmentFlags{get;privateset;}
/// <summary>
/// Specifies the Service Parameters applicable to this this delegation path.
/// It is up to the Application Specification to specify the values found in this field.
/// </summary>
publicDataSegmentServices{get;privateset;}
/// <summary>
/// A substitution expression that is applied to the original string held by the client in order to construct the next domain name to lookup.
/// See the DDDS Algorithm specification for the syntax of this field.
///
/// As stated in the DDDS algorithm, The regular expressions must not be used in a cumulative fashion, that is, they should only be applied to the original string held by the client, never to the domain name produced by a previous NAPTR rewrite.
/// The latter is tempting in some applications but experience has shown such use to be extremely fault sensitive, very error prone, and extremely difficult to debug.
/// </summary>
publicDataSegmentRegexp{get;privateset;}
/// <summary>
/// The next domain-name to query for depending on the potential values found in the flags field.
/// This field is used when the regular expression is a simple replacement operation.
/// Any value in this field must be a fully qualified domain-name.
/// Name compression is not to be used for this field.
///
/// This field and the Regexp field together make up the Substitution Expression in the DDDS Algorithm.
/// It is simply a historical optimization specifically for DNS compression that this field exists.
/// The fields are also mutually exclusive.
/// If a record is returned that has values for both fields then it is considered to be in error and SHOULD be either ignored or an error returned.