Re: Public disclosure of discovered vulnerabilities
From: Dave Thompson (david.thompson1_at_worldnet.att.net)
Date: 06/17/05
- Next message: Dave Thompson: "Re: Crypto++ error while loading RSA public key"
- Previous message: Joseph Ashwood: "Re: New Encryption Idea"
- In reply to: Andrew Swallow: "Re: Public disclosure of discovered vulnerabilities"
- Next in thread: Andrew Swallow: "Re: Public disclosure of discovered vulnerabilities"
- Reply: Andrew Swallow: "Re: Public disclosure of discovered vulnerabilities"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 17 Jun 2005 05:56:07 GMT
On Fri, 10 Jun 2005 15:32:28 +0000 (UTC), Andrew Swallow
<am.swallow@btopenworld.com> wrote:
<snip>
> Some systems recover from a full queue by telling the transmitter
> to wait. X.25 packet switching calls the message a RNR (Receive
> Not Ready) S Frame. However such a recovery is too complex for
> this example.
>
More precisely, it is called Receiver Not Ready by SDLC/HDLC/ADCCP
which is used as the level-2 protocol by X.25 (LAP-B) but in other
situations as well.
BSC calls it WACK, which is much more fun to say, e.g. when narrating
a trace over the phone. Also, ACK0 and ACK1 can be pronounced ack-oh
and ack-eye; just try that with RR-3 or worse I-3-1-P. Although SNRM
is suitably sinister sounding. (An almost Agnewian tongue twister!)
- David.Thompson1 at worldnet.att.net
- Next message: Dave Thompson: "Re: Crypto++ error while loading RSA public key"
- Previous message: Joseph Ashwood: "Re: New Encryption Idea"
- In reply to: Andrew Swallow: "Re: Public disclosure of discovered vulnerabilities"
- Next in thread: Andrew Swallow: "Re: Public disclosure of discovered vulnerabilities"
- Reply: Andrew Swallow: "Re: Public disclosure of discovered vulnerabilities"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]