re: http://www.garlic.com/~lynn/2009l.html#3 VTAM security issue http://www.garlic.com/~lynn/2009l.html#7 VTAM security issue http://www.garlic.com/~lynn/2009l.html#11 VTAM security issue http://www.garlic.com/~lynn/2009l.html#13 SNA: conflicting opinions
a "network" layer with feature like ARP ... also enables BOOTP&DHCP ... with things like "reverse ARP" ... a machine dynamically loading their network characteristic from service in local environment. bootp/dhcp provides for dynamic network configuration for things like roaming laptops in wireless environment. from my IETF RFC index: http://www.garlic.com/~lynn/rfcietff.htm click on "Term (term->RFC#)" in the "RFCs listed by" section; then in the "Acronym fastpath" section there is "BOOTP": bootstrap protocol (BOOTP ) see also configuration , reverse address resolution protocol 2132 1542 1534 1533 1532 1497 1395 1084 1048 951 "DHCP": dynamic host configuration protocol (DHCP ) see also configuration , host , reverse address resolution protocol 5505 5460 5417 5223 5192 5139 5107 5071 5010 5007 4994 4941 4833 4776 4704 4703 4702 4701 4676 4649 4580 4578 4477 4436 4390 4388 4361 4332 4280 4243 4242 4174 4076 4039 4030 4014 3993 3942 3927 3925 3898 3825 3736 3679 3646 3634 3633 3594 3527 3495 3456 3442 3397 3396 3361 3319 3315 3256 3203 3118 3074 3046 3041 3011 3004 2939 2937 2855 2610 2563 2489 2485 2322 2242 2241 2132 2131 1541 1534 1533 1531 and "RARP" reverse address resolution protocol (RARP ) see also address resolution 5505 5460 5417 5223 5192 5139 5107 5071 5010 5007 4994 4941 4833 4776 4704 4703 4702 4701 4676 4649 4580 4578 4477 4436 4390 4388 4361 4332 4280 4243 4242 4174 4076 4039 4030 4014 3993 3942 3927 3925 3898 3825 3736 3679 3646 3634 3633 3594 3527 3495 3456 3442 3397 3396 3361 3319 3315 3256 3203 3118 3074 3046 3041 3011 3004 2939 2937 2855 2610 2563 2489 2485 2322 2242 2241 2132 2131 1931 1542 1541 1534 1533 1532 1531 1497 1395 1084 1048 951 903 ... clicking on RFC number brings up the corresponding summary in the lower frame, clicking on the ".txt=nnn" field (in the summary) retrieves the actual RFC. the attempts by the communication division to preserve the terminal communication paradigm ... showed up in lots of ways. one of the ways was veto'ing numerous disk division's attempts to come out with advanced access products for the distributed environment (as part of stemming the flight of data out off the mainframe) communication division could escalate to corporate with claim that they had responsibility for all products that involved communication crossing the datacenter boundary (at the peak, disk division was seeing double digit per annum percentage flight of data out off the mainframe). another trivial example were PC lan cards. high-powered workstations represented the quickly evolving direction for PCs ... requiring increasingly powerful networking. the AWD division had done the PC/RT and had produced their own ISA 4mbit T/R LAN card. When it came time for the rs/6000, they thought that they would do their own microchannel 16mbit T/R LAN card ... but they were wrong ... they were forced into using lots of the PS2 microchannel adapter cards. It turns out that the PS2 microchannel 16mbit T/R LAN card had design point of terminal emulation with 300 (or more) stations all sharing the same 16mbit T/R bandwidth. As a result, the PS2 microchannel 16mbit T/R LAN card had lower per card thruput than the PC/RT ISA 4mbit T/R LAN card (significantly restricting its ability to participate in high-powered networking environments ... PC/RT ISA 4mbit T/R card had higher thruput than the PS2 microchannel 16mbit T/R card). references to old 3tier presentation from the late 80s (attempting to give the terminal communication paradigm as much benefit as possible in the comparison): http://www.garlic.com/~lynn/96.html#17 http://www.garlic.com/~lynn/2002q.html#40 other posts mentioning 3-tier architecture http://www.garlic.com/~lynn/subnetwork.html#3tier misc. past posts discussing many of the issues and downside related to the attempts to preserve the terminal communication paradigm. http://www.garlic.com/~lynn/subnetwork.html#terminal -- 40+yrs virtualization experience (since Jan68), online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
