There is one TBD item that exists in section 5.3.2 of draft-ietf-regext-epp-eai related the “predefined placeholder email” that is used by the EAI supporting server and EAI supporting client where the opposite party doesn't support EAI. In both cases a valid email value needs to be provided to a non-EAI supporting client or server to satisfy a required email property when all that is available is an EAI value. To satisfy this requirement, a predefined placeholder email needs to be selected that meets the requirements:
1. A syntactically valid email address to pass client or server validation logic. 2. A non-EAI email address since the client or server doesn’t support EAI email addresses. 3. A single value that can indicate the lack of EAI support to the client or server. 4. An email address that is blackholed and never delivered. 5. Use of the email address will not cause operational issues. RFC 7535 defines a blackholed domain name with EMPTY.AS112.ARPA, which can be leveraged for the EAI predefined placeholder email. The proposal is to define the “predefined placeholder email” value as e...@empty.as112.arpa<mailto:e...@empty.as112.arpa>. This value looks to meet the requirements. We are looking for feedback from the working group as well as experts outside of the working group to help determine whether the value does meet the requirements and whether there are additional requirements that need to be considered. Once the predefined placeholder email is agreed to, the draft will be updated to define the predefined placeholder email value and use that value to replace the existing TBD values in section 5.3.2 of the draft. Thanks, -- JG [cid:image001.png@01D77EF1.F9899340] James Gould Fellow Engineer jgo...@verisign.com<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://verisigninc.com/>
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
