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] RIPE554-bis
- Previous message (by thread): [ipv6-wg] RIPE554-bis
- Next message (by thread): [ipv6-wg] RIPE554-bis
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Fernando Gont
fgont at si6networks.com
Thu Oct 29 09:45:14 CET 2020
On 29/10/20 05:26, Jens Link wrote: > Fernando Gont <fgont at si6networks.com> writes: > >>> The SEND requirment? No OS I'm aware of does support it and it only >>> makes sense when the networking hardware and the OS support it. >> >> I think SEND is a smart spec/artifact... but I also think that I would >> probably have a hard time finding a reason to deploy it. :-) > > Sure, but a) I always have to explain to people what SEND is and that it > doesn't work when I'm doing IPv6 workshops FWIW, when doing workshops, I don't use more than two slides to give a high-level overview of what SEND is about, and note why it's not currently deployable, and while it is very unlikely that it will be deployable any time soon. (For similar reasons, I don't even bother with things like mobile IPv6). > and b) I know people putting > something like "hardware must comply to RIPE 554" into tenders. The effect of that would be interesting to see (whether it would push implementation, or actually back-fire). I do think that, if/when considering inclusion of SEND in RIPE-554, the fact that it is IPR-encumbered be considered in the decision process. Thanks, -- Fernando Gont SI6 Networks e-mail: fgont at si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
- Previous message (by thread): [ipv6-wg] RIPE554-bis
- Next message (by thread): [ipv6-wg] RIPE554-bis
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]