RFC Errata
RFC 5346, "Operational Requirements for ENUM-Based Softswitch Use", October 2008
Source of RFC: enum (rai)
Errata ID: 1537
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-10-07
Held for Document Update by: Robert Sparks
Section 4.1.1,pg.5 says:
The case where a valid URI was present is covered in Section 4.1.2 (rule 2 A, second point). The case where an ENUM entry was not provisioned for a number that had an active PSTN Point of | Interconnect is covered in Section 4.1.2 (rule 2 B). For "ENUM only" ranges, where a given number in that range was in service (i.e., there was an IP-based Point of Interconnect to a carrier), a valid SIP or H.323 URI was always provisioned into the | associated ENUM domain. This is covered in Section 4.1.2 (rule 2 A, second point). In such an "ENUM only" range, if the number was not in service, a TXT record was provisioned but no valid NAPTRs would be present. This ensured that a query for NAPTRs in a given (out of service, "ENUM only" range) domain would succeed (i.e., return a RCODE of 0), but that the number of answers would also be zero. This is covered in | Section 4.1.2 (rule 2 A, first point). Note that this point also covers the case where only NAPTRs that cannot be used to initiate a call exist in such a zone.
It should say:
The case where a valid URI was present is covered in Section 4.1.2 | (rule 3 A, second point). The case where an ENUM entry was not provisioned for a number that had an active PSTN Point of | Interconnect is covered in Section 4.1.2 (rule 3 B). For "ENUM only" ranges, where a given number in that range was in service (i.e., there was an IP-based Point of Interconnect to a carrier), a valid SIP or H.323 URI was always provisioned into the | associated ENUM domain. This is covered in Section 4.1.2 (rule 3 A, second point). In such an "ENUM only" range, if the number was not in service, a TXT record was provisioned but no valid NAPTRs would be present. This ensured that a query for NAPTRs in a given (out of service, "ENUM only" range) domain would succeed (i.e., return a RCODE of 0), but that the number of answers would also be zero. This is covered in | Section 4.1.2 (rule 3 A, first point). Note that this point also covers the case where only NAPTRs that cannot be used to initiate a call exist in such a zone.
Notes:
All (4) instances of "rule 2" should say "rule 3".