FYI, the ticket has been closed without merging, and the existing regular expressions will remain in the current document.
-- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast > -----Original Message----- > From: Alessandro Vesely <[email protected]> > Sent: Saturday, October 19, 2024 1:59 PM > To: [email protected] > Subject: [dmarc-ietf] Re: Update of IPv6 regular expressions [was: DMARC > Aggregate PR 19] > > On Sat 19/Oct/2024 19:29:25 +0200 John R Levine wrote: > >> On 10/19/24 13:06, Daniel K. wrote: > >> > >> The value in source_ip SHOULD either be a globally > >> routable IPv4 unicast address in the dotted-decimal > >> format, or a globally routable IPv6 Global Unicast > >> address in the canonical textual representation format; > >> see RFC 5952 for details. > > > > That's OK with me with the usual caveat that you need to say why it's > > SHOULD and not MUST. > > > +1, the caveat would be about obsolete library functions...? > > > > Given that nobody seems to look at the regex, and just uses library IP > > address routines to produce and read the IPs, how about just using the > > really short one I suggested? > > > +1! > > > Best > Ale > -- > > > > > _______________________________________________ > dmarc mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
