;A fsxNet Nodelist for Friday, August 26, 2016 -- Day number 239 : 21027 ;S Copyright 2016, fsxNet, All rights reserved. ;S ;S ;S fsxNet - [F]un, [S]imple, e[X]perimental Network ;S ;S ==== A weekly nodelist for the fsxNet ==== ;S ;S Infopack (bbs.geek.nz/fsxnet.zip) ;S ;S fsxNet is a fun, simple and experimental network established in late 2015 ;S ;S fsxNet is not a perscriptive network. e[X]perimentation is at heart ;S of its name and members are actively encouraged to be creative in their ;S use of the network. Only a handfull of message areas and file bases are ;S used - setup is quick and [S]imple. ;S ;S Technologies covered by the network include (but are not limited to) ;S BBSing, ANSI art, Vintage Computers & Gaming, FTN communications, ;S network protocols & topologies, encryption methods and more... ;S ;S fsxNet sees around 600-800 messages posted every week. It is the primary ;S and most active support network for Mystic BBS software. ;S ;S Do you find it [F]un to learn about and use retro computing technologies? ;S Would you like to be part of a group that enjoy experimenting and developing ;S those technologies further? If the answer is yes, then we invite you to ;S join us :) ;S ;S == GOALS ==================================================================== ;S ;S * Develop and encourage international communications between 50 (or more) ;S geographically diverse bulletin board systems. ;S ;S * Support and create learning and experimental opportunities between ;S members. ;S ;S * Foster borderless international friendships. ;S ;S * Explore and develop new and interesting methods of online communication ;S between members. ;S ;S * Have fun, be respectful and helpful to each other. ;S ;S == Housekeeping ============================================================= ;S ;S * Members using fsxNet to conduct themselves with the above goals in mind. ;S ;S * The use of the network for illegal purposes is not permitted. Members ;S deemed to be engaged in such activities will be delisted by the Network ;S Coordinator. ;S ;S * Real names used in the nodelist, aliases or real names welcome in ;S all echoareas. ;S ;S * Please post messages containing ANSI but do so with an [ANSI] prefix in ;S the message subject line. This allows members who can't view ANSI content ;S to opt out reading it if they are unable to do so. ;S ;S e.g. Subject: [ANSI] Something I drew last night ;S ;S == Echoareas ================================================================ ;S ;S Message Echos: ;S ;S FSX_GEN - A general discussion echoarea that covers 99% of topics. ;S Test messages and other experimentation is welcome. ;S If it's on fsxNet the chances are it happens here. ;S Real names not required. ;S ;S File Bases: ;S ;S FSX_NODE - Weekly fsxNet nodelist - FSXNET.ZIP ;S FSX_INFO - Weekly fsxNet infopack - FSXINFO.ZIP ;S ;S FSX_MYST - Mystic BBS Software ;S FSX_MUTL - Mystic BBS Utils, Mods etc. ;S ;S FSX_BBS - BBS Software (Current + Legacy) ;S FSX_DOOR - BBS Doors, Games etc. ;S FSX_UTLS - BBS Utils, Tools, Networking etc. ;S FSX_NETS - BBS Networks, Infopacks, Nodelists ;S ;S FSX_ART - ANSI Art - Groups, Individuals etc. ;S ;S The fsxNet HUB (21:1/100) accepts BinkD connections via ;S ipv4.agency.bbs.geek.nz:24556 ;S ;S == ChangeLog ================================================================ ;S ;S Recent entries are recorded below. For a full history exmaine history.txt ;S contained in the fsxNet infopack :) ;S ;S ;S 2016-08-14 ;S Added - Node 162 - Razor's Domain BBS (USA) - He's back.. Hi and welcome to ;S Kevin Nunn who ran many versions of his BBS back in the ;S 90's. Now time poor (like us all!) he's giving Mystic a ;S crack to avoid messing with Allfix + FastEcho + BinkD etc ;S Welcome back Kevin - feel free to ask lots of questions :) ;S ;S ;S Added - Node 161 - The Search BBS (USA) - Hello and welcome to Karl Harris ;S who joins the NET with a Mystic system set up and running ;S using a Raspberry Pi. Have fun Karl and thanks for taking ;S the time to join fsxNet :) ;S ;S 2016-08-13 ;S Added - Node 160 - SLiME CiTY BBS (SWE)- Welcome to David Jacoby aka m00p ;S who is running a Mystic system under Windows. David is ;S based in Ahus in Sweden. Great to have you with us ;S m00p :) ;S ;S Added - Node 159 - The GateHouse BBS (CAN) - Welcome to John Riley who is ;S setting up a Mystic system using a Raspberry Pi and is ;S based in Ontario, Canada. Great to have you as part of ;S the NET John - welcome :) ;S ;S 2016-08-11 ;S Added - Node 158 - Starlight BBS (NLD) - Welcome to Lars van Dijk who is ;S setting up a Mystic system running under Linux. ;S ;S 2016-08-10 ;S Added - Node 157 - Shadowscope BBS (USA) - Welcome to Richard Miles from ;S Temple, Georgia, USA. Running a Mystic system and just ;S getting set up in a move from Synchronet. ;S ;S ============================================================================= ;S ;S ;S ; Zone,21,fsxNet_Coordinator,Dunedin_NZL,Paul_Hayton,-Unpublished-,300,CM,INA:ipv4.agency.bbs.geek.nz,IBN:24556 ; Region,1,fsxNet_The_World,Dunedin_NZL,Paul_Hayton,-Unpublished-,300,CM,INA:ipv4.agency.bbs.geek.nz,IBN:24556 ,100,fsxNet_HUB,Dunedin_NZL,Paul_Hayton,-Unpublished-,300,CM,INA:ipv4.agency.bbs.geek.nz,IBN:24556 ,101,Agency_BBS,Dunedin_NZL,Paul_Hayton,-Unpublished-,300,CM,INA:ipv4.agency.bbs.geek.nz,IBN:24555 ,102,Error_404_BBS,Perrysburg_USA,Todd_Zieman,-Unpublished-,300,CM,INA:error404bbs.ddns.net,IBN Pvt,103,Micro_Link_BBS,Maryborough_AUS,Lloyd_Russell,-Unpublished-,300 ,104,fido.ricsi.priv.at,Vienna_AUT,Richard_Menedetter,-Unpublished-,300,CM,XW,INA:fido.ricsi.priv.at,IBN ,105,Fluph_BBS,Elkview_USA,Leslie_Given,-Unpublished-,300,CM,INA:fluph.darktech.org,IBN ,106,BlackICE_BBS,Duesseldorf_DEU,Vitus_Zeel,-Unpublished-,300,CM,INA:blackice.bbsindex.com,IBN ,107,CyberNet_BBS,Lindale_USA,Chad_Adams,-Unpublished-,300,CM,INA:bbs.cybernetbbs.net,IBN Pvt,108,Sector_7_BBS,Philedelphia_USA,James_Coyle,-Unpublished-,300 ,109,Freeway_BBS,Bendigo_AUS,Tony_Langdon,-Unpublished-,300,CM,INA:freeway.apana.org.au,IBN ,110,Rusty_Mailbox_BBS,Penticton_CAN,Alan_Ianson,-Unpublished-,300,CM,INA:trmb.ca,IBN ,111,Mutiny_BBS,Auckland_NZL,James_Kelly,-Unpublished-,300,CM,INA:mutiny.av4rist.nz,IBN ,112,Black_Flag_BBS,Hudson_USA,Hawk_Hubbard,-Unpublished-,300,CM,INA:blackflag.acid.org,IBN ,113,Alcoholiday_BBS,South_Carolina_USA,Andrew_Haworth,-Unpublished-,300,CM,INA:alco.bbs.io,IBN ,114,Throwback_BBS,Meriden_USA,Todd_Yatzook,-Unpublished-,300,CM,INA:bbs.throwbackbbs.com,IBN ,115,1st_Choice_Core_BBS,Ashburton_NZL,Ian_Segers,-Unpublished-,300,CM,INA:1stchoicecore.co.nz,IBN ,116,Delta_City_BBS,Vallentuna_SWE,Joacim_Melin,-Unpublished-,300,CM,INA:78.108.60.254,IBN ,117,Mystic_Dreams_BBS,Warminster_USA,Mark_Iezzi,-Unpublished-,300,CM,INA:mysticdreams.dyndns.org,IBN:24555 ,118,Crystal_Peak_BBS,Pine_City_USA,Will_Du_Chene,-Unpublished-,300,CM,INA:crystalp.duckdns.org,IBN ,119,Sysgod_BBS,Sydney_AUS,Scott_Little,61-2-9727-7775,300,CM,XA,V32b,V34,V42b,VFC,INA:ftn.sysgod.org,IBN,ITN:60177,IFC,PING ,120,Cyberia_BBS,Kingwood_USA,Darryl_Perry,-Unpublished-,300,CM,INA:cyberia.darktech.org,IBN ,121,Xibalba_BBS,Salt_Lake_City_USA,Bryan_Ashby,-Unpublished-,300,CM,INA:xibalba.l33t.codes:44510,IBN:54554 ,122,Necronomicon_BBS,New_Bedford_USA,Carlos_Roldan,-Unpublished-,300,CM,INA:necrobbs.strangled.net,IBN ,123,The_Void_BBS,Troy_USA,Mitch_Greive,-Unpublished-,300,CM,INA:thevoid.servebbs.org,IBN ,124,Dogtown_BBS,Los_Angeles_USA,Christopher_Taylor,-Unpublished-,300,CM,INA:bbs.kiwi.net,IBN ,125,Voodoo_BBS,Toowoomba_AUS,Andrew_Pamment,-Unpublished-,300,CM,INA:bbs.magickabbs.com:2023,IBN ,126,Twinkle_BBS,Albuquerque_USA,Christopher_Malo,-Unpublished-,300,CM,INA:tbbs.homeip.net,IBN ,129,SpaceSST_BBS,Montreal_CAN,Luc_McCarragher,-Unpublished-,300,CM,INA:mccarragher.org,IBN ,127,Capital_Station_BBS,Nassau_USA,Gregory_Deyss,-Unpublished-,300,CM,INA:csbbs.dyndns.org,IBN ,128,The_OuijaBoard_BBS,Anoka_USA,Jeff_Smith,-Unpublished-,300,CM,INA:bbs.ouijabrd.net,IBN ;E ,129,SpaceSST_BBS,Montreal_CAN,Luc_McCarragher,-Unpublished-,300,CM,INA:mccarragher.org,IBN ;E -- Duplicate Node number -- '129' ,130,Tiny's_BBS,Oshawa_CAN,Shawn_Highfield,-Unpublished-,300,CM,INA:tinysbbs.com,IBN ,131,Weather_Station_HUB,Bel_Air_USA,Mark_Hofmann,-Unpublished-,300,CM,INA:bbs.weather-station.org,IBN:24555 ,132,Weather_Station_BBS,Bel_Air_USA,Mark_Hofmann,-Unpublished-,300,CM,INA:bbs.weather-station.org,IBN ,133,The_Parity_Error_BBS,Kelowna_CAN,Ian_McLaughlin,-Unpublished-,300,CM,INA:theparityerror.com,IBN ,134,Mystic_Prison_Board_BBS,Mesquite_USA,Ruben_Figueroa,-Unpublished-,300,CM,INA:pb.darktech.org:24,IBN:24555 ,135,Return_to_The_Lair_of_the_Wolverine_BBS,Salt_Lake_City_USA,Kevin_Taylor,-Unpublished-,300,CM,INA:bbs.r2lotw.com,IBN ,136,force9_BBS,London_GBR,David_Stephens,-Unpublished-,300,CM,INA:bbs.force9.org,IBN ,137,Nitemare_Cafe_BBS,Cardington_USA,Rod_Barnhart,-Unpublished-,300,CM,INA:bbs.nitemarecafe.com:2002,IBN ,138,The_Cell_Block_BBS,London_CAN,Blair_Lovell,-Unpublished-,300,CM,INA:thecellblock.ddns.net,IBN ,139,Satellite_of_Madness_BBS,Jacksonville_USA,Matthew_Blocker,-Unpublished-,300,CM,INA:madness.synchro.net,IBN ,140,HappyLand_BBS,Toowoomba_AUS,Andrew_Pamment,-Unpublished-,300,CM,INA:andrew.homeunix.org:2023,IBN ,141,Pie33_BBS,Amsterdam_NLD,Moises_Aranas,-Unpublished-,300,CM,INA:pie33.com:2224,IBN ,142,SmokyThing_BBS,San_Antonio_USA,Shannon_Kuchler,-Unpublished-,300,CM,INA:inflecto.org,IBN ,143,The_Bridge_BBS,Bendigo_AUS,Tony_Langdon,-Unpublished-,300,CM,INA:bridge.vkradio.com,IBN ,144,Aloryn_Avalon_BBS,Bellevue_USA,Joshua_Cain,-Unpublished-,300,CM,INA:alorynavalon.ddns.net,IBN ,145,Mystic_Pi_BBS,Nashua_USA,Brian_Wallace,-Unpublished-,300,CM,INA:bcw142.zapto.org,IBN:24556 ,146,Saturn's_Orbit_BBS,Rio_de_Janeiro_BRA,Flavio_Bessa,-Unpublished-,300,CM,INA:saturnsorbit.hopto.org,IBN ,147,MPrah_BBS,Harrison_USA,Michael_Prah,-Unpublished-,300,CM,INA:mprah.net,IBN ,148,International_LiveWire_BBS,Kentucky_USA,Allen_Prunty,-Unpublished-,300,CM,INA:livewirebbs.com,IBN ,149,reDMud_System_BBS,Oklahoma_USA,David_Snyder,-Unpublished-,300,CM,INA:107.208.153.41:55444,IBN:44455 ,150,Southend_BBS,Frederikshavn_DNK,Lars_Wiberg,-Unpublished-,300,CM,INA:bbs.slartie.com,IBN ,151,Solar_BBS,Pahrump_USA,Dave_Holtzman,-Unpublished-,300,CM,INA:solar.bbsindex.com,IBN ,152,2nd_Choice_Core_BBS,Ashburton_NZL,Ian_Segers,-Unpublished-,300,CM,INA:2ndchoicecore.ddns.net:1024,IBN:24555 ,153,Solar_Pi_BBS,Buffalo_USA,Corey_Reichle,-Unpublished-,300,CM,INA:bbs.solarpi.net,IBN ,154,Stepping_Stone_BBS,Wichita_USA,John_Justvig,-Unpublished-,300,CM,INA:vintagebbsing.com,IBN ,155,Gerlach_BBS,Zvolen_SVK,Dominik_Madarasz,-Unpublished-,300,CM,INA:bbs.zaklaus.me:28,IBN ,156,Oxford_Mills_Remote_BBS,Campbellford_CAN,Mike_Manning,-Unpublished-,300,CM,INA:oxfordmi.synchro.net,IBN ,157,Shadowscope_BBS,Temple_USA,Richard_Miles,-Unpublished-,300,CM,INA:bbs.shadowscope.com,IBN ,158,Starlight_BBS,Beek_en_Donk_NLD,Lars_van_Dijk,-Unpublished-,300,CM,INA:starlight.altimit.nl:2323,IBN ,159,The_GateHouse_BBS,Hockley_Valley_CAN,John_Riley,-Unpublished-,300,CM,INA:76.10.159.60,IBN ,160,Slime_City_BBS,Ahus_SWE,David_Jacoby,-Unpublished-,300,CM,INA:bbs.retrohack.se,IBN ,161,The_Search_BBS,Goshen_USA,Karl_Harris,-Unpublished-,300,CM,INA:bbs.thehomesteadinghippy.com,IBN ,162,Razors_Domain_BBS,McAllen_USA,Kevin_Nunn,-Unpublished-,300,CM,INA:bbs.razorsdomain.com,IBN Pvt,999,New_System,AnyTown_AnyCountry,New_Sysop,-Unpublished-,300 ; Region,2,fsxNet_Usenet,Dunedin_NZL,Paul_Hayton,-Unpublished-,300,CM,INA:ipv4.agency.bbs.geek.nz,IBN:24556 ,100,Usenet_HUB,Dunedin_NZL,Paul_Hayton,-Unpublished-,300,CM,INA:ipv4.agency.bbs.geek.nz,IBN:24556 ,101,Agency_BBS,Dunedin_NZL,Paul_Hayton,-Unpublished-,300,CM,INA:ipv4.agency.bbs.geek.nz,IBN:24555 ;S ;S ;S --- NODELIST FLAGS --- ;S ;S A. OPERATING CONDITION FLAGS: ;S ;S Flag Meaning ;S ;S CM Node accepts mail 24 hours a day ;S MO Node does not accept human callers ;S LO Node accepts calls Only from Listed ;S FidoNet addresses ;S ICM Node accepts 24/7 IP-mail but has limited ;S "open"-hours only via PSTN and/or ISDN ;S ;S B. MODEM FLAGS: ;S The following flags define modem protocols supported: ;S ;S Flag Meaning ;S ;S V21 CCITT V.21 300 bps full duplex ;S V22 CCITT V.22 1200 bps full duplex ;S V29 CCITT V.29 9600 bps half duplex ;S V32 CCITT V.32 9600 bps full duplex ;S V32b ITU-T V.32 bis 14400 bps full duplex ;S V32T V.32 Terbo ;S V33 CCITT V.33 ;S V34 CCITT V.34 ;S HST USR Courier HST ;S H14 USR Courier HST 14.4 ;S H16 USR Courier HST 16.8 ;S H96 Hayes V9600 ;S MAX Microcom AX/96xx series ;S PEP Packet Ensemble Protocol ;S CSP Compucom Speedmodem ;S ZYX Zyxel series ;S VFC V.Fast Class ;S Z19 Zyxel 19,200 modem protocol ;S V90C ITU-T V.90 modem Client ;S V90S ITU-T V.90 Server. ;S X2C US Robotics x2 client. ;S X2S US Robotics x2 server. ;S ;S The following flags define type of error correction available. A ;S separate error correction flag should not be used when the error ;S correction type can be determined by the modem flag. For instance ;S a modem flag of HST implies MNP. ;S ;S Flag Meaning ;S ;S MNP Microcom Networking Protocol error correction ;S of type MNP1 to MNP4 ;S V42 LAP-M error correction w/fallback to MNP ;S ;S C. COMPRESSION FLAGS: ;S ;S The following flags define the type(s) of compression of mail ;S packets supported. ;S ;S Flag Meaning ;S ;S MN No compression supported ;S ;S The following flags define the type(s) of data compression ;S available. ;S ;S V42b ITU-T V42bis ;S ;S D. FILE/UPDATE REQUEST FLAGS: ;S ;S The following flags indicate the types of file/update requests ;S supported. ;S ;S ;S |--------------------------------------------------| ;S | | Bark | WaZOO | ;S | |---------------------|---------------------| ;S | | File | Update | File | Update | ;S | Flag | Requests | Requests | Requests | Requests | ;S |------|----------|----------|----------|----------| ;S | XA | Yes | Yes | Yes | Yes | ;S | XB | Yes | Yes | Yes | No | ;S | XC | Yes | No | Yes | Yes | ;S | XP | Yes | Yes | No | No | ;S | XR | Yes | No | Yes | No | ;S | XW | No | No | Yes | No | ;S | XX | No | No | Yes | Yes | ;S |--------------------------------------------------| ;S ;S ;S ;S The following software is qualified to ;S use the appropriate file request flag ;S according to information provided by ;S developers: ;S ;S |-----------------------------------| ;S | Flag Software Package | ;S |-----------------------------------| ;S | XA Frontdoor 1.99b and lower | ;S | Frontdoor 2.01 and higher | ;S | Dutchie 2.90c | ;S | Binkleyterm 2.1 and higher | ;S | D'Bridge 1.2 and lower | ;S | Melmail | ;S | TIMS | ;S | Xenia | ;S |-----------------------------------| ;S | XB Binkleyterm 2.0 | ;S | Dutchie 2.90b | ;S |-----------------------------------| ;S | XC Opus 1.1 | ;S |-----------------------------------| ;S | XP Seadog | ;S |-----------------------------------| ;S | XR Opus 1.03 | ;S | Platinum Xpress | ;S |-----------------------------------| ;S | XW Fido 12N and higher | ;S | Tabby | ;S | TrapDoor No update processor| ;S | The Brake! | ;S |-----------------------------------| ;S | XX Argus 2.00 and higher | ;S | BeeMail ;S | D'Bridge 1.30 and higher | ;S | Frontdoor 1.99c/2.00 | ;S | InterMail 2.01 | ;S | McMail 1.00 | ;S | T-Mail | ;S | TrapDoor - Update Processor | ;S |-----------------------------------| ;S | None QMM | ;S |-----------------------------------| ;S ;S ;S E. GATEWAY FLAG: ;S ;S The following flag defines gateways to other domains (networks). ;S ;S Flag Meaning ;S ;S Gx..x Gateway to domain 'x..x', where 'x..x` is a string ;S of alphanumeric characters. Valid values for ;S 'x..x' are assigned by the FidoNet International ;S Coordinator. Current valid values of 'x..x' may ;S be found in the notes at the end of the FidoNet ;S nodelist. ;S ;S F. MAIL PERIOD FLAGS: ;S The following flags define the dedicated mail periods supported. ;S They have the form "#nn" or !nn where nn is the UTC hour the mail ;S period begins, # indicates Bell 212A compatibility, and ! ;S indicates incompatibility with Bell 212A. ;S ;S Flag Meaning ;S ;S #01 Zone 5 mail hour (01:00 - 02:00 UTC) ;S #02 Zone 2 mail hour (02:30 - 03:30 UTC) ;S #08 Zone 4 mail hour (08:00 - 09:00 UTC) ;S #09 Zone 1 mail hour (09:00 - 10:00 UTC) ;S #18 Zone 3 mail hour (17:00 - 18:00 UTC) ;S #20 Zone 6 mail hour (20:00 - 21:00 UTC) ;S ;S NOTE: When applicable, the mail period flags may ;S be strung together with no intervening commas, eg. ;S "#02#09". Only mail hours other than that ;S standard within a node's zone should be given. ;S Since observance of mail hour within one's zone is ;S mandatory, it should not be indicated. ;S ;S G. ISDN CAPABILTY FLAGS: ;S ;S Nodelist Specification of minimal support required for this flag; ;S flag any additional support to be arranged via agreement ;S between users ;S ;S V110L ITU-T V.110 19k2 async ('low'). ;S V110H ITU-T V.110 38k4 async ('high'). ;S V120L ITU-T V.120 56k async, layer 2 framesize 259, window 7, ;S modulo 8. ;S V120H ITU-T V.120 64k async, layer 2 framesize 259, window 7, ;S modulo 8. ;S X75 ITU-T X.75 SLP (single link procedure) with 64kbit/s B ;S channellayer 2 max.framesize 2048, window 2, non-ext. ;S mode (modulo 8)layer 3 transparent (no packet layer). ;S ISDN Other configurations. Use only if none of the above ;S fits. ;S ;S NOTE: No flag implies another. Each capability MUST be specifically ;S listed. ;S If no modem connects are supported, the nodelist speed field should ;S be 300. ;S ;S Conversion from old to new ISDN capability flags: ;S ISDNA -> V110L ;S ISDNB -> V110H ;S ISDNC -> X75 ;S ;S H. INTERNET CAPABILITY FLAGS: ;S ;S FLAG MEANING ;S ;S IBN - denotes a system that does BINKP ;S IFC - denotes a system that is capable of RAW or IFCICO ;S ITN - denote a system that does TELNET ;S IVM - denotes a system that is capable of VMODEM ;S IFT - denotes a system that allows FTP ;S ITX - denotes a system that uses TransX encoding for email ;S tunneling ;S IUC - denotes a system that uses UUEncode for email tunneling ;S IMI - denotes a system which uses MIME encoding for email ;S tunneling ;S ISE - denotes a system which supports SEAT receipts for anonymous ;S mail ;S IP - denotes a system that can receive TCP/IP connects using a ;S protocol that is not covered by any other flag. ;S IEM - is a deprecated flag, and new implementations must not ;S write it in nodelist entries. This was used as a single ;S placeholder for the InterNet address of the system if it ;S supported several transport methods. Instead of placing ;S the system address in the deprecated form specified below ;S in each flag, the address would be placed once only in this ;S flag. Implementations may need to parse this information ;S from nodelists created with older programs. ;S INA - Place to list a Fully Qualified Domain Name Or Static IP ;S Address, to be followed by applicable protocol flags ;S offered. Usage: INA:| ;S ;S ;S Conversion from R46/R50 Internet capabilty flags to the new flags: ;S ;S BND -> IBN ;S TEL -> ITN ;S TELNET -> ITN ;S VMD -> IVM ;S TCP -> IP ;S ;S The Internet Address should be placed in the BBS name field. ;S ;S Previous usage has placed the InterNet address as part of the ;S I-flag (for example ITX:r10_tx@thevision.net) ;S In this format the flag, colon, and address combined cannot exceed 32 ;S characters. However, this practice is deprecated, and new implementations ;S must not place address data in the flag section of the nodelist entry, ;S implementations may however be required to read this data from the ;S flag section. ;S ;S Telnet default port is 23. If the port is not 23 then the port ;S number must be placed after the ITN flag (eg ITN:60177) if the ;S Telnet address is part of the ITN flag (eg ITN:farsi.dynip.com) then ;S the port number should be last (eg ITN:kraut.dynip.com:60177) always ;S remember that the flag cannot exceed 32 characters total. ;S ;S The default ports for other protocols are shown below, and changes ;S from the default port must be flagged in a similar way. ;S ;S Protocol Flag Default Port ;S ;S FTP IFT 21 ;S BINKP IBN 24554 ;S RAW/IFCICO IFC 60179 ;S VMODEM IVM 3141 ;S ;S Actual IP addresses can also be placed in the phone number field ;S using the country code of 000, however, the use of a FQDN is prefered. ;S ;S Note: All IP nodes *must* have mailer capabilities. E-Mail/FTP etc. denote ;S supplemental capabilities only. ;S ;S I. SYSTEM ONLINE TIME FLAGS ;S ;S The flag Tyz is used by non-CM nodes online not only during ZMH, ;S y is a letter indicating the start and z a letter indicating the ;S end of the online period as defined below (times in UTC): ;S ;S A 0:00, a 0:30, B 1:00, b 1:30, C 2:00, c 2:30, ;S D 3:00, d 3:30, E 4:00, e 4:30, F 5:00, f 5:30, ;S G 6:00, g 6:30, H 7:00, h 7:30, I 8:00, i 8:30, ;S J 9:00, j 9:30, K 10:00, k 10:30, L 11:00, l 11:30, ;S M 12:00, m 12:30, N 13:00, n 13:30, O 14:00, o 14:30, ;S P 15:00, p 15:30, Q 16:00, q 16:30, R 17:00, r 17:30, ;S S 18:00, s 18:30, T 19:00, t 19:30, U 20:00, u 20:30, ;S V 21:00, v 21:30, W 22:00, w 22:30, X 23:00, x 23:30. ;S ;S For example TuB shows an online period from 20:30 until 1:00 UTC. ;S ;S Daylight saving time ;S ;S If a node changes online times with respect to UTC when daylight ;S saving time becomes effective (which would be the case with most ;S part time nodes), then this is to be taken into account when ;S assigning this flag. An online times flag assigned to a node should ;S not be altered for the specific purpose of adjusting due to ;S daylight saving time, since large difference files (NODEDIFF's) ;S would result if every node was allowed to do this, e.g. my node ;S used to be online from 2300 to 0800 in local time, which in winter ;S is UTC, but in the summer it becomes BST (British Summer Time). ;S This is one hour ahead of UTC, and the corresponding availability ;S times of my node during the summer period were 2200 to 0700 UTC. ;S Therefore my online times flag would have indicated availability ;S between the hours of 2300 and 0700 UTC, the daily time period ;S encompassing both times, so the flag would be TXH. ;S ;S J. BAUD RATES: ;S ;S The following baud rates are authorized for use in the nodelist: ;S ;S 300, 1200, 2400, 4800, 9600, 14400, 16800, 19200, 28800, 33600 ;S ;S K. Special flag: "PING" without any arguments ;S ;S Meaning: ;S ;S Nodes flying this flag will adhere to the following functionality: ;S ;S 1) PING-function: ;S """"""""""""""""" ;S If a message destined to "PING" arrives at its final destination ;S and this final destination flies the "PING"-flag, then the ;S receiving node will bounce the message back to the original ;S sender clearly displaying all the original via-lines. ;S ;S If a message destined to "PING" arrives at its final destination ;S but this final destination does _not_ fly the "PING"-flag then the ;S message may be deleted from the inbound-queue without further ;S follow-up. ;S ;S 2) TRACE-function: ;S """""""""""""""""" ;S If a message destined to "PING" arrives at a node which flies ;S the PING-flag but is merely passing-through to another destination ;S then the in-transit node will notify the sender of this occurence ;S and will forward the original mail unaltered towards its final ;S destination. ;S ;S ;S Userflags authorized for use in the nodelist ;S ------------ ;S A. FORMAT OF USER FLAGS ;S ;S U,x..x ;S A user-specified string, which may contain any ;S alphanumeric character except blanks. This string may ;S contain one to thirty-two characters of information ;S that may be used to add user-defined data to a specific ;S nodelist entry. The character "U" must not be ;S repeated, eg, ",U,XXX,YYY,ZZZ" not ",U,XXX,U,YYY,UZZZ". ;S The 32 character limitation is per userflag, not for ;S the total of all userflags. ;S ;S New implementations must place a comma after the ;S initial "U" before the user flags. Some ;S implementations will not place a separating comma ;S between the "U" and the first user flag, but this ;S practice is deprecated. Implementations should be ;S prepared to read flags in this format, and must strip ;S the "U" from the flag before analysis in this case. ;S ;S Entries following the "U" flag must be of a technical ;S or administrative nature. While experimentation of new ;S software functions using this flag is encouraged, ;S advertisement is strictly prohibited. ;S ;S For applications other than those shown, or if you ;S have questions concerning the use of this field, please ;S contact your Regional or Zone Coordinator. ;S ;S ZEC Zone EchoMail Coordinator. Not more than one entry ;S in the zone segment may carry this flag and that entry ;S must be the current Zone EchoMail Coordinator. ;S ;S REC Regional EchoMail Coordinator. Not more than one ;S entry in any region may carry this flag and that entry ;S must be the current Regional EchoMail Coordinator. ;S ;S NEC Network EchoMail coordinator. Not more than one entry ;S in any net may carry this flag and that entry must be ;S the current Network EchoMail Coordinator of that Net. ;S ;S ;S SDS Software Distribution System ;S ;S SMH SecureMail Hub - or one of the following variations, ;S indicating the specific level of the hub: ;S ;S NSMH - Net SecureMail Host - only one per net ;S RSMH - Region SecureMail Host - only one per region ;S ZSMH - Zone SecureMail Host - only one in Zone 1 ;S ISMH - International SecureMail Host - only one in Fidonet ;S ;S NC Network Coordinator. This flag is ONLY to be used by ;S the Network Coordinator of a net which has split the ;S duties of NC and Host and the NC does NOT occupy the ;S Net/0 position in the nodelist.