On 07/25/2018 04:48 PM, Eric Vyncke (evyncke) wrote: > Being a layer-3 person, I am a (just) little concerned by having one IPv6 > address per connection as it could put some stress on Neighbor Discovery > (mcast traffic draining battery, cache space/maintenance) if used by default > on very short live connections > > Just a thought
FWIW, while "one address per connection" is certainly mentioned as "an extreme case" in <https://tools.ietf.org/html/draft-gont-taps-address-analysis-00#page-4>, I do agree and share Eric's concern. If anything, one might think f "one address per module" (whatever that is), or one address per process/thread... but I'm not sure I'd default to "one address per connection". I think that there might only be specific cases/scenarios where one might want to do this. Thanks, -- Fernando Gont SI6 Networks e-mail: [email protected] PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492 _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
