# SRVName and XmppAddr support **URL:** \ **Category:** Feature Requests\ **Created:** [June 17, 2019, 7:15pm UTC](https://community.letsencrypt.org/t/srvname-and-xmppaddr-support/96026 "2019-06-17T19:15:40Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [June 17, 2019, 8:40pm UTC](https://community.letsencrypt.org/t/srvname-and-xmppaddr-support/96026/3 "2019-06-17T20:40:02Z")
> [@plinss](#): > > Since I don’t find any mention of these in the ACME spec and have no idea how I would authenticate such entries, I’m presuming Let’s Encrypt wouldn’t sign a request including these. Is that correct? You're correct. As @Osiris mentions (thanks!) ACME (RFC 8555) provides no challenge types associated with identifiers other than DNS type. > [@plinss](#): > > If so, any plans to add support? We have no plans to support these Subject Alternative Name types. Beyond the challenge of how you would validate them we are forbidden by the [CA/Browser forum baseline requirements](https://cabforum.org/baseline-requirements-documents/) from including them in our certificates. See Section 7.1.4.2. "Subject Information – Subscriber Certificates", specifically 7.1.4.2.1 "Subject Alternative Name Extension": > Each entry MUST be either a dNSName containing the Fully-Qualified Domain Name or an iPAddress containing the IP address of a server Including an OtherName type Subject Alternative Name with the OID for SRVName or XmppAddr would be a misissuance under the BRs by my reading. Hope that helps explain the situation, --- _[View the full topic](https://community.letsencrypt.org/t/srvname-and-xmppaddr-support/96026)._