From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH v4 1/2] batman-adv: mcast: detect, distribute and maintain multicast router presence
Date: Tue, 11 Jun 2019 07:44:12 +0200 [thread overview]
Message-ID: <1705254.clgQh6sisM@sven-edge> (raw)
In-Reply-To: <20190610231414.GA10498@otheros>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
On Tuesday, 11 June 2019 01:14:14 CEST Linus Lüssing wrote:
> I'm currently unsure when we would need that. Are you suggesting
> to interpret it that way, just in case we might need it some day?
>
> Note that this would also be a "soft compatibility break". So old
> nodes would still interpret 0x1f the same way as 0x07, meaning
> they would send all multicast traffic to nodes announcing either
> 0x1f or 0x07. It'd be a "soft break" because it wouldn't cause
> packet loss, old nodes would just overestimate.
I am just unsure how we could/would interpret this in the future. Not that we
need support for it in the first version.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-11 5:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 0:45 [PATCH v4 0/2] batman-adv: Add routeable multicast optimizations Linus Lüssing
2019-06-10 0:45 ` [PATCH v4 1/2] batman-adv: mcast: detect, distribute and maintain multicast router presence Linus Lüssing
2019-06-10 5:39 ` Sven Eckelmann
2019-06-10 7:24 ` Sven Eckelmann
2019-06-10 23:14 ` Linus Lüssing
2019-06-10 23:45 ` Linus Lüssing
2019-06-11 5:44 ` Sven Eckelmann [this message]
2019-06-11 14:12 ` Linus Lüssing
2019-06-10 0:45 ` [PATCH v4 2/2] batman-adv: mcast: apply optimizations for routeable packets, too Linus Lüssing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1705254.clgQh6sisM@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.