<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2900.2523" name=GENERATOR></HEAD>
<BODY><!-- Converted from text/plain format -->
<P><FONT size=2><FONT face=Arial color=#0000ff>Responses
Below...</FONT></FONT></P><FONT size=2><FONT face=Arial
color=#0000ff></FONT><FONT face=Arial color=#0000ff></FONT><FONT face=Arial
color=#0000ff></FONT>
<P><BR>-----Original Message-----<BR>From: aprssig-bounces@lists.tapr.org [<A
href="mailto:aprssig-bounces@lists.tapr.org">mailto:aprssig-bounces@lists.tapr.org</A>]
On Behalf Of Greg Noneman<BR>Sent: Wednesday, January 05, 2005 11:11<BR>To: TAPR
APRS Mailing List<BR>Subject: Re: [aprssig] The new N-N paradigm summary
(fwd)<BR><BR><BR>I agree that WIDEn-N was bringing in these stations. But,
is one<BR>packet an hour from a handful of DX stations really going to
kill the<BR>local network. Also, if everyone suddenly got rid of WIDEn-N,
what do<BR>you think these DX digis would do to their paths? Back to long
WIDE<BR>paths, like was the case before? And with this, the packets get
REALLY<BR>long and can chew up a lot of bandwidth.<BR><BR><FONT face=Arial
color=#0000ff>Yes it is killing local networks all over! We have seen this
too many times before. We shouldn't be going back to the long WIDE paths
but should be using the new SSn-N. So if you use RELAY,NC2-2 then that
would be the equivelant of using RELAY,WIDE2-2 except the packet is now
contained within a geographical area where it can be
managed.</FONT></P></FONT></BODY></HTML>