Enum trust_dns_proto::rr::domain::usage::AppUsage [−][src]
pub enum AppUsage {
Normal,
Loopback,
LinkLocal,
NxDomain,
}Application Software:
Are writers of application software expected to make their software recognize these names as special and treat them differently? In what way? (For example, if a human user enters such a name, should the application software reject it with an error message?)
Variants
NormalApplication software SHOULD NOT recognize these names as special, and SHOULD use these names as they would other reverse-mapping names.
Application software SHOULD NOT recognize test names as special, and SHOULD use test names as they would other domain names.
Application software SHOULD NOT recognize example names as special and SHOULD use example names as they would other domain names.
LoopbackApplication software MAY recognize localhost names as special, or MAY pass them to name resolution APIs as they would for other domain names.
LinkLocalLink local, generally for mDNS
NxDomainApplication software MAY recognize "invalid" names as special or MAY pass them to name resolution APIs as they would for other domain names.
Trait Implementations
impl Clone for AppUsage[src]
impl Clone for AppUsagefn clone(&self) -> AppUsage[src]
fn clone(&self) -> AppUsageReturns a copy of the value. Read more
fn clone_from(&mut self, source: &Self)1.0.0[src]
fn clone_from(&mut self, source: &Self)Performs copy-assignment from source. Read more
impl Copy for AppUsage[src]
impl Copy for AppUsageimpl PartialEq for AppUsage[src]
impl PartialEq for AppUsagefn eq(&self, other: &AppUsage) -> bool[src]
fn eq(&self, other: &AppUsage) -> boolThis method tests for self and other values to be equal, and is used by ==. Read more
fn ne(&self, other: &Rhs) -> bool1.0.0[src]
fn ne(&self, other: &Rhs) -> boolThis method tests for !=.
impl Eq for AppUsage[src]
impl Eq for AppUsage