pub enum UserUsage {
Normal,
Loopback,
LinkLocal,
NxDomain,
}
Expand description
Users:
Are human users expected to recognize these names as special and use them differently? In what way?
Variants§
Normal
Users are free to use these names as they would any other reverse-mapping names. However, since there is no central authority responsible for use of private addresses, users SHOULD be aware that these names are likely to yield different results on different networks.
Loopback
Users are free to use localhost names as they would any other domain names. Users may assume that IPv4 and IPv6 address queries for localhost names will always resolve to the respective IP loopback address.
LinkLocal
Multi-cast link-local usage
NxDomain
Users are free to use “invalid” names as they would any other domain names. Users MAY assume that queries for “invalid” names will always return NXDOMAIN responses.
Trait Implementations§
impl Copy for UserUsage
impl Eq for UserUsage
impl StructuralPartialEq for UserUsage
Auto Trait Implementations§
impl Freeze for UserUsage
impl RefUnwindSafe for UserUsage
impl Send for UserUsage
impl Sync for UserUsage
impl Unpin for UserUsage
impl UnwindSafe for UserUsage
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§unsafe fn clone_to_uninit(&self, dst: *mut T)
unsafe fn clone_to_uninit(&self, dst: *mut T)
clone_to_uninit
)Source§impl<Q, K> Equivalent<K> for Q
impl<Q, K> Equivalent<K> for Q
Source§impl<Q, K> Equivalent<K> for Q
impl<Q, K> Equivalent<K> for Q
Source§fn equivalent(&self, key: &K) -> bool
fn equivalent(&self, key: &K) -> bool
key
and return true
if they are equal.