Hi Jim, I am not into all details, but why not using an email adress, such as e...@example.com?
My understanding of RFC2606 is, that you can use example.com/org/net for that purpose, too, as they are reserved TLDs. empty.as112.arpa has no MX record, too, therefore, I don‘t get the advantage of it. Best, Tobias > Am 22.07.2021 um 18:06 schrieb Gould, James > <jgould=40verisign....@dmarc.ietf.org>: > > > 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. > 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 > > <image001.png> > > > James Gould > Fellow Engineer > jgo...@verisign.com > > 703-948-3271 > 12061 Bluemont Way > Reston, VA 20190 > > Verisign.com > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
