From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Rahul Bothra <rrbothra@gmail.com>, Tom Henderson <tomh@tomh.org>,
tahiliani.nitk@gmail.com
Subject: Re: bits 10 to 15 in OGM packets
Date: Thu, 25 Jun 2020 16:06:38 +0200 [thread overview]
Message-ID: <1752987.3nn1Mqi339@bentobox> (raw)
In-Reply-To: <CADhofF8ExwW+kYPDTX1W4ZZz_6gs3zEvzu_7oe1WrkP3-+fpiQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On Thursday, 25 June 2020 15:22:46 CEST Rahul Bothra wrote:
> I was going through the Internet Draft for B.A.T.M.A.N, and wanted to
> confirm if the bits 10 to 15 in the OGM packet are supposed to be all
> zeroes always?
Please don't implement the legacy draft which was never finished. This is
really, really, really, really, really, really, really, really, really,
really, really, really, really, really, really, really, really, really,
really, really, really, really, really, really, really, really, really,
really, really, really, really, really, really, really, really, really,
really, really, really, really, really, really, really, really, really,
really, really, really, really outdated.
But the batmand layer 3 compat version 5 handled these as reserved flags. So
it would have been a good idea at that time not to leave them in a random
state and just set them to 0. This would have allowed announcements of
additional features in the future.
See https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/
include/uapi/linux/batadv_packet.h for the B.A.T.M.A.N. IV and B.A.T.M.A.N. V
layer 2 packet definitions.
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:[~2020-06-25 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 13:22 bits 10 to 15 in OGM packets Rahul Bothra
2020-06-25 14:06 ` Sven Eckelmann [this message]
2020-06-25 15:16 ` Rahul Bothra
2020-06-25 16:07 ` Marek Lindner
2020-06-25 16:07 ` Sven Eckelmann
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=1752987.3nn1Mqi339@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=rrbothra@gmail.com \
--cc=tahiliani.nitk@gmail.com \
--cc=tomh@tomh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox