[ipv6-wg] Latest draft for RIPE554-bis

Hi Jordi,

I see you also brought up on the v6ops list.   Let's see what the operator
community has to say about this topic.

I'm not opposed to changing this, but I'm also aware that's CPEs rarely
support all the mechanisms listed in that RFC.

~Tim

On Wed, Nov 24, 2021 at 11:58 AM JORDI PALET MARTINEZ via ipv6-wg <
ipv6-wg at ripe.net> wrote:

> Hi Tim, all,
>
> I've reviewed the latest version of the document and in general I agree.
> However, today is unacceptable that a CPE doesn't support IPv6-only +
> IPv4aaS, so RFC8585 must be a must in this type of document.
>
> I think there must be a clear statement on that.
>
> Regards,
> Jordi
> @jordipalet
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the exclusive use of
> the individual(s) named above and further non-explicilty authorized
> disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited and will be considered a criminal offense. If you are not the
> intended recipient be aware that any disclosure, copying, distribution or
> use of the contents of this information, even if partially, including
> attached files, is strictly prohibited, will be considered a criminal
> offense, so you must reply to the original sender to inform about this
> communication and delete it.
>
>
>
>
> To unsubscribe from this mailing list, get a password reminder, or change
> your subscription options, please visit:
> https://mailman.ripe.net/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ipv6-wg/attachments/20211124/ce5cc824/attachment.html>