Editing
HInternet/ApplicationLayer
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
= Application Layer = Operating under Part 97 of the FCC rules comes with some constraints on how the network can be used and what can be information can be communicated over it. Because of these rules and constraints, reasonable protections will need to be put into place to prevent both unauthorized use of the network by unlicensed individuals as well as unauthorized communications over the system by legitimately licensed operators. == Communication Constraints == === Obscured Communication === FCC rules state that "An amateur station shall not intentionally obscure the meaning of a transmission"<sup>[citation needed]</sup>. Does this mean that encryption is not allowed? Some would argue that this is debatable, and that encryption and coding schemes are allowed, provided that there is public documentation as to how a scheme works. For example, the ARRL HSMM working group recommended that a standard, publicly documented WEP key be used to prevent unauthorized control of Part 97 equipment by users of Part 15 licensed equipment. === "Alternative" Radio Services === FCC Part 97, section 113(a)(5) rules also stipulate that: * (a) No amateur station shall transmit: ** (5) Communications, on a regular basis, which could reasonably be furnished alternatively through other radio services. Does this mean that providing Internet access over amateur radio is competing with commercial IP transit? Again, some would argue that this is debatable. == Applications == With these constraints in mind, it may be prudent to design nodes to filter non-compliant traffic, or create applications (and maybe protocols) to facilitate legal communication. For example, we could create and use [http://www.multicastdns.org/ MDNS] over multicast IP to announce which stations are reachable, and which modes they can communicate with (voice over [http://en.wikipedia.org/wiki/Session_Initiation_Protocol SIP]/[http://en.wikipedia.org/wiki/Real-time_Transport_Protocol RTP], video over [http://en.wikipedia.org/wiki/Session_Initiation_Protocol SIP]/[http://en.wikipedia.org/wiki/Real-time_Transport_Protocol RTP], text over [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC], etc.). Ideally, this could become a point-and-click application for amateur stations. Sort of an [http://en.wikipedia.org/wiki/Automatic_link_establishment ALE (Automatic Link Establishment)] for IP communications.
Summary:
Please note that all contributions to Noisebridge are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see
Noisebridge:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Log in
Request account
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Dig in!
Noisebridge
- Status: MOVED
- Donate
- ABOUT
- Accessibility
- Vision
- Blog
Manual
MANUAL
Visitors
Participation
Community Standards
Channels
Operations
Events
EVENTS
Guilds
GUILDS
- Meta
- Electronics
- Fabrication
- Games
- Music
- Library
- Neuro
- Philosophy
- Funding
- Art
- Crypto
- Documentation/Wiki
Wiki
Recent Changes
Random Page
Help
Categories
(Edit)
Tools
What links here
Related changes
Special pages
Page information