This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] Latest draft for RIPE554-bis
- Previous message (by thread): [ipv6-wg] Latest draft for RIPE554-bis
- Next message (by thread): [ipv6-wg] Latest draft for RIPE554-bis
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Timothy Winters
tim at qacafe.com
Wed Nov 24 19:11:33 CET 2021
Hi Jordi, Most of the testing requests that we have received for wired CPEs lately have been MAP based. We are aware of a couple ISPs considering XLAT464, but I'm not aware of it being used in production. For wireless XLAT464 makes sense, even for fixed wireless. ~Tim On Wed, Nov 24, 2021 at 12:31 PM JORDI PALET MARTINEZ via ipv6-wg < ipv6-wg at ripe.net> wrote: > Hi Tim, > > > > I understand that even if in the IETF we decide not to go for that, as we > know that the participation in IETF from operators is not as good as we > wish, we as a different community can have a totally different perspective. > > > > If we don’t want to have full support of the RFC8585, at least we must > mandate the 464XLAT section. The reason is clear: it is the only possible > way in mobile, and if you want to support “hybrid CPEs” (those that provide > for example a GPON WAN or Ethernet WAN + USB dongle for 3-5G) the easier > way is to provide 464XLAT. It is also a matter of subscriber numbers in one > technology vs all the others together. > > > > Regards, > > Jordi > > @jordipalet > > > > > > > > El 24/11/21 18:26, "ipv6-wg en nombre de Timothy Winters" < > ipv6-wg-bounces at ripe.net en nombre de tim at qacafe.com> escribió: > > > > 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/ > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://mailman.ripe.net/ > > ********************************************** > 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/c8c9a2e9/attachment.html>
- Previous message (by thread): [ipv6-wg] Latest draft for RIPE554-bis
- Next message (by thread): [ipv6-wg] Latest draft for RIPE554-bis
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]