IETF-64 - ENUM WG1 ENUM validation status update Alex Mayrhofer enum.at / 3.4.e164.arpa Bernie Höneisen SWITCH / 1.4.e164.arpa draft-mayrhofer-enum-validation-arch-00 draft-hoeneisen-enum-validation-epp-01 draft-lendl-enum-validation-token-00

IETF-64 - ENUM WG2 overview Requirements Role modelProcess & trust assumptions validation data transport validation data format draft-ietf-enum-validation-arch draft-ietf-enum- validation-epp EPP SOAP? draft-ietf- enum- validation- token XML IRIS? alternative formats? Other? E.115

IETF-64 - ENUM WG3 Changes: draft-ietf-enum-validation-arch-00 Name changed to reflect WG adoption Concept remains unchanged Minor cleanups and clarifications References updated

IETF-64 - ENUM WG4 Changes: draft-ietf-enum-validation-epp-01 Aligned with other ENUM validation drafts, i.e. with: –draft-ietf-enum-validation-arch, and –draft-ietf-enum-validation-token Added more explanation for “Id”-Attribute –Usually assigned by the Registrar –Uniqueness per Registry recommended Updated references

IETF-64 - ENUM WG5 Changes: draft-ietf-enum-validation-token-00 Token can now describe the validation of number blocks. –New tag –Input from Sweden, should be helpful for all countries with a fixed length numbering plan.

IETF-64 - ENUM WG6 Changes: draft-ietf-enum-validation-token-00 Tag names synchronized with other drafts (validation-*, IRIS-EREG) Schema/namespace IDs changed from http: to urn:ietf. Minor simplification of the XML schema Streamlined text (hopefully) clearer explanations Thanks for the input! –(especially Michael Haberler and Lawrence Conroy)

IETF-64 - ENUM WG7 TODOs Architecture: check for NITS and review EPP: Align XML element names in the examples with token and iris-ereg drafts to improve readability (just minor change) Token: check for NITS and review, receive feedback about civic address format How to proceed after that?