enum-8----Page:12
1 2 3 4 5 6 7 8 9 10 11 12 13 14
|
Non-Terminal NAPTRs (NTNs) - 2 NTNs - what they meant to say in the standards: Note: RFC 3402 section 3 and RFC 3404 give the option of using either the REGEXP or the replacement field to generate or hold a domain name - no ENUM client handles this, so don’t provision NTNs with REGEXP field, as they will be ignored (at best :) AFAICT, no DDDS client actually implements this (other DDDS applications do not need/use NTNs) ENUM NTNs have empty flags and services fields ENUM NTNs have a non-empty replacement field (holding the target domain to look for more NAPTRs), and so must have an empty REGEXP field |