All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: "b.a.t.m.a.n@lists.open-mesh.org" <b.a.t.m.a.n@lists.open-mesh.org>
Cc: Liunian Bian <mrbianliunian@outlook.com>
Subject: Re: How to cite the BATMAN routing protocol in a research paper?
Date: Mon, 08 Apr 2024 09:42:45 +0200	[thread overview]
Message-ID: <2269621.iZASKD2KPV@prime> (raw)
In-Reply-To: <MEYP282MB31231B4B48B7D9960334CEE4BF012@MEYP282MB3123.AUSP282.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]

On Sunday, April 7, 2024 11:46:49 AM CEST Liunian Bian wrote:
> Subject: How to cite the BATMAN routing protocol in a research paper?
> Hi, I cannot find a proper citation for the BATMAN routing protocol.
> 
> The citations I could find were:
> > A. Neumann, C. Aichele, M. Lindner, and S. Wunderlich, “Better approach to
> > mobile ad-hoc networking (B.A.T.M.A.N.)," IETF Draft, 2008 [Online] R.
> > Sanchez-Iborra, M. -D. Cano and J. Garcia-Haro, "Performance Evaluation
> > of BATMAN Routing Protocol for VoIP Services: A QoE Perspective," in IEEE
> > Transactions on Wireless Communications, Sept. 2014
> which are incomplete and outdated.
> Is there any references I can use for citing BATMAN IV or BATMAN V in a
> research paper? It would help me a lot.
> 

Hi Liunian Bian,

unfortunately we don't have a good way to cite batman-adv in a paper. What 
most people did is to cite the 2008 IETF draft (which is actually not supposed 
be cited) or refer to our website www.open-mesh.org/. Perhaps the best way is 
to cite both, referring to the website for up-to-date documentation.

Cheers,
       Simon


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-04-08  7:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-07  9:46 How to cite the BATMAN routing protocol in a research paper? Liunian Bian
2024-04-08  7:42 ` Simon Wunderlich [this message]

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=2269621.iZASKD2KPV@prime \
    --to=sw@simonwunderlich.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=mrbianliunian@outlook.com \
    /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.