RFC 2317 - Classless IN-ADDR.ARPA delegation / "reverse" DNS delegation for IPv4 for smaller than /24

So,

RFC 2317 - Classless IN-ADDR.ARPA delegation / "reverse" DNS delegation for IPv4 for smaller than /24

for at least Comcast Business Customers that have one or more static IPv4 addresses,

does Comcast [Business] offer/support this?  Querying the forums seems to paint an inconsistent

picture.  E.g. they've done it (at least in past), "vs." many asking about it and no particularly clear

answers.

I know when I first inquired about it about 6 years ago, at that time,

Comcast Business support, at least on the phone verbally, told me,

perhaps incorrectly, that they didn't at all support such.

But other evidence suggests they do (or at least have in past).

So, ... what's the actual answer?  Yes, support it, or no, don't, and if not, any plans to

support it?  And if so, is there like a "feature request" or the like that's been submitted

that one can watch/track to see if/when it's actually implemented/supported?

And if Comcast Business won't support/allow RFC 2317,

do they at least provide API or even a web form or the like for customers to

much more directly update their "reverse" DNS for IPv4?  Because yeah,

the whole existing service request route and long delays to get such changes

done is pretty gawd awful, and yes, Comcast Business will increasingly bleed off customers

with that lack of service.  Yeah, when i relocate my current Comcast Business account (probably

in next few years), Comcast Business absolutely isn't currently my top pick, and, well, as things

have and haven't been going, I may drop Comcast Business sooner than that.

So ... if Comcast Business isn't yet supporting RFC 2317 for customers with static IPv4s,

do they at least have a feature request in queue to do so?  If not, consider this a request for that feature.  :-)

I'm sure I'm not the only one that wants to see RFC 2317 support.

And ... bonus points if Comcast Business adds DNSSEC to their "reverse" (in-addr.arpa.) DNS

(I see that as unimplemented, at least thus far on (at least some of) Comcast's zones, such as 86.96.in-addr.arpa.)

Really ought be present on their DNS in general, ... at least I do see it in some places (e.g. comcast.com.),

so, well, at least got some things right.  :-)