[ax25-layer2] 7-byte address proposal

[Pete Loveall AE5PL]

> -----Original Message-----
> From: Robert Bruninga [mailto:bruninga at usna.edu] 
> Sent: Thursday, August 03, 2006 3:17 PM
> To: Pete Loveall AE5PL; ax25-layer2 at lists.tapr.org
> Subject: RE: [ax25-layer2] 7-byte address proposal
> 
> Just seeing if I am following correctly.... I cant even 
> remember what a TAPR-2 does with the PID.  Does it only 
> accept the standrd PID and completely ignore all other 
> packets with different PID's are does it display them?

Different TNCs handle PIDs differently.  Most in converse mode will display
the PID along with other header information.  In KISS mode, this is a
non-issue since the TNCs do not do header interpretation in KISS mode.

> I would prefer finding a way for the new 3.0 packets to be 
> displayed (even if not correctly) on legacy TNC's so that 
> any/all users of a channel can tell that there is other 
> traffic on the channel.  Changing the PID  makes this not 
> possible except by user action (which is an acceptible fall 
> back position, I guess)...

They will be displayable.  As stated above, KISS mode negates this issue
since you will be looking at an application, not the TNC data stream.  In
converse monitor mode, different TNCs will handle it differently.  But we
are writing a layer 2 protocol spec here, not something to accommodate how
somebody decided to display received packets.  In many cases, it is probably
best that some TNCs like the KPC-3 have the PID command to display only 0xF0
PIDs since some software may depend on this filter.

73,

Pete Loveall AE5PL 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3097 bytes
Desc: not available
Url : http://www.tapr.org/pipermail/ax25-layer2/attachments/20060803/6ad930cc/attachment.bin