[OZAPRS] European v USnewparadigmand pathlimiting +confusion....

[Ron Perry]

On Tue, 2006-11-07 at 19:43 +1100, Dion Bramich wrote:
> On Tue, 07 Nov 2006 19:41:06 +1100, Ron Perry <ronk at sunlinux.com.au>
wrote:
> 
> > Hi All,
> > Just back from our ride to the Vic Alps. My, hasn't this list been
> > busy.  :-)
> >
> > On Tue, 2006-11-07 at 18:40 +1100, Dion Bramich wrote:
> >> Roaming mobiles would use WIDE1-1,WIDE2-2 or whatever.  Mobiles not
> >> expecting to cross zone boundaries would use ZONE1-1,ZONE2-2 thus
> >> eliminating interzone QRM.
> >>
> > Just a couple of thoughts.
> > The idea of using ZONE1-1, ZONE2-2 for as well as WIDE1-1,WIDE2-2 just
> > creates more confusion and complexity for the users.  Are we not
trying
> > to simplify it so, at least for mobiles, one standard path works?
> >
> 
> Explain why its more confusing.  The new paradigm is simple, moreso than

> the old system.
> 
> One standard mobile path will be WIDE1-1,WIDE2-2.  It will work  
> everywhere. 
To this I agree.


But then you need to educate the users how this will benefit them?
>  Those wishing to not generate QRM will use ZONE1-1,ZONE2-2.  

IMHO that to most, particularly mobile, users, would seem more complex.
>  
> All they need to know is which zone suits them best.  Better yet,
ZONEing  
> keeps packets short, they arent lengthened each hop like with the
WIDEn-N  
> path, thus saving bandwidth.

"They need to know which suites zone them best."...is introducing the
problems we are trying to avoid. More confusion.

Not convinced...yet. :)

Regards,
Ron
vk3ecv








> 
> > There would still be interzone QRM, even if it was not digipeated, as
> > the packet would still be heard by the neighbouring digipeater(s).
> >
> 
> If its not repeated then its one less heard be the next digi.
> 
> 
> Dion.
> 
> > Regards,
> > Ron
> > vk3ecv/vk3wrm
> >
> >> Dion.
> >>
> >>
> >> On Tue, 07 Nov 2006 18:35:01 +1100, Richard Hoskin <vk3jfk at amsat.org>
> >> wrote:
> >>
> >> >
> >> > Dion,
> >> >
> >> > If you where using any ZONEn-n / SSn-n path you would need to
change  
> >> it
> >> > when
> >> > you crossed Zone boundaries. This does not apply to the VK3 Zone  
> >> system
> >> > as
> >> > it is transparent to users.
> >> >
> >> > Cheers
> >> > Richard
> >> > VK3JFK
> >> >
> >> >> -----Original Message-----
> >> >> From: ozaprs-bounces at aprs.net.au
[mailto:ozaprs-bounces at aprs.net.au]  
> >> On
> >> >> Behalf Of Dion Bramich
> >> >> Sent: Tuesday, 7 November 2006 5:14 PM
> >> >> To: VK / ZL APRS Users
> >> >> Subject: Re: [OZAPRS] European v USnewparadigmand pathlimiting
> >> >> +confusion....
> >> >>
> >> >> On Tue, 07 Nov 2006 16:58:34 +1100, Andrew McDade
> >> >> <amcdade at iprimus.com.au>
> >> >> wrote:
> >> >>
> >> >> > Gday Richard and all,
> >> >> >
> >> >> >> Zoning would make more sense. We use a different implementation
of
> >> >> Zones
> >> >> >> in
> >> >> >> VK3 already
> >> >> >
> >> >> > Noting your comment above. I think that we should be trying to
> >> >> > standardize
> >> >> > on one form or another of a zoning system that will best suit
the
> >> >> whole
> >> >> > of
> >> >> > Australia. You could say that each region / zone is independent,

> >> and
> >> >> so
> >> >> > it
> >> >> > doesn't really matter which way this is setup. However it would
be
> >> >> nice
> >> >> > from
> >> >> > a documentation and new user setup point of view, if a standard

> >> set of
> >> >> > guidelines is developed with regards to this.
> >> >>
> >> >> Nicer, eg, if someone down here could get on the boat, drive and
be  
> >> seen
> >> >> without the need for him to take all his documentation to learn
how  
> >> to
> >> >> reprogram, and his laptop to do the programming?
> >> >>
> >> >> >
> >> >> > BTW... perhaps you could tell us more about the Vic zoning
> >> >> > implementation.
> >> >> > Perhaps , it'll suit the rest of us as well !!.
> >> >>
> >> >> Dion.
> >> >>
> >> >> >
> >> >> > Regards .. Andrew
> >> >> >
> >> >> >
> >> >> > _______________________________________________
> >> >> > Ozaprs mailing list
> >> >> > Ozaprs at aprs.net.au
> >> >> > http://aprs.net.au/mailman/listinfo/ozaprs
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Using Opera's revolutionary e-mail client:
http://www.opera.com/mail/
> >> >> Send instant messages to your online friends
> >> >> http://au.messenger.yahoo.com
> >> >> _______________________________________________
> >> >> Ozaprs mailing list
> >> >> Ozaprs at aprs.net.au
> >> >> http://aprs.net.au/mailman/listinfo/ozaprs
> >> >
> >> > _______________________________________________
> >> > Ozaprs mailing list
> >> > Ozaprs at aprs.net.au
> >> > http://aprs.net.au/mailman/listinfo/ozaprs
> >>
> >>
> >>
> >
> > _______________________________________________
> > Ozaprs mailing list
> > Ozaprs at aprs.net.au
> > http://aprs.net.au/mailman/listinfo/ozaprs
> 
> 
> 
> -- 
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> Send instant messages to your online friends
http://au.messenger.yahoo.com 
> _______________________________________________
> Ozaprs mailing list
> Ozaprs at aprs.net.au
> http://aprs.net.au/mailman/listinfo/ozaprs

_______________________________________________
Ozaprs mailing list
Ozaprs at aprs.net.au
http://aprs.net.au/mailman/listinfo/ozaprs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://second.aprs.net.au/pipermail/ozaprs/attachments/20061107/7e6c9db6/attachment.htm