public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Bastian Bittorf <bittorf@bluebottle.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Wimax-Stuff and Ideas
Date: Fri, 13 Feb 2009 16:20:07 +0100	[thread overview]
Message-ID: <20090213152007.GA28964@amd> (raw)
In-Reply-To: <20090213142309.GB17394@pandem0nium>

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

* Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de> [13.02.2009 15:30]:

> > > limit is of course the allowed transmit power, or EIRP. The limit is
> > 
> > Thats not true for special tasks like disaster management.
> > It's no problem (and allowed) to work with 40.000 mW in such a situation.
> > Ask somebody from the german THW for details.
> 
> Thanks for pointnig that out, i did not know that. :)
> So you can get an exception from the RegTP for special purposes like
> desaster management?

Yes. I would think, that this is global. In germany you have also                                                                              
much more possibilities if you are a certified "Amateur Funker",
that means you have completed a government-controlled seminar
for "radio knowledge". (sorry, can't describe it better in english)

Bastian Bittorf


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-02-13 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.134.1234470500.960.b.a.t.m.a.n@open-mesh.net>
2009-02-12 21:30 ` [B.A.T.M.A.N.] B.A.T.M.A.N Digest, Vol 26, Issue 7 Tim LePes
2009-02-13  0:21   ` Simon Wunderlich
2009-02-13 13:08     ` [B.A.T.M.A.N.] Wimax-Stuff and Ideas Bastian Bittorf
2009-02-13 14:23       ` Simon Wunderlich
2009-02-13 15:20         ` Bastian Bittorf [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=20090213152007.GA28964@amd \
    --to=bittorf@bluebottle.com \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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