;A FidoNet Nodelist for Friday, December 31, 1999 -- Day number 365 : 33026 D20 A1 ;A FidoNet Nodelist for Friday, January 07, 2000 -- Day number 007 : 07090 C201 D1 A1 Pvt,746,Alien_Biker_Kat_BBS,San_Diego_CA,Bud_Jamison,-Unpublished-,9600 C419 D1 A1 ,1,Lawboard_Fido,Champaign_IL,Fred_Grosser,1-217-352-6118,2400 C144 D1 A1 Pvt,999,New_Node,Wayne_County_MI,New_Sysop,-Unpublished-,9600 C34 D1 A1 Down,114,Myles'_Games_Extravaganza,Ottawa_On,Myles_Bunbury,-Unpublished-,2400 C90 D1 A1 Pvt,999,*Application_Address*,Net_225,New_SysOp,-Unpublished-,2400 C368 D1 A1 ,28,JNS_Software_Support_BBS,Barboursville_WV,Rusty_Johnson,1-304-733-4148,9600,CM,XX,V32B,V42B C107 D1 A1 Pvt,210,frackit.com,Harrisburg_PA,dave_ratcliffe,-Unpublished-,9600 C281 D1 A1 ,440,NeverLand,Maryland_Heights_MO,Timothy_Trace,1-314-993-3750,9600,CM,LO,V34,XA C33 D1 A1 ,9999,New_Fidonet_Node,Anywhere_MN,New_Fido_SysOp,1-000-000-0000,9600 C78 D1 A1 Pvt,7,Lloyd's_BBS,Columbia_MO,Lloyd_McKenzie,-Unpublished-,2400 C135 D1 A1 ,59,Bob's_Place_BBS,Mesa_AZ,Bob_Adkins,1-480-835-0550,9600,XR,CM,V32B,V42B,V34 C44 D1 A1 Pvt,999,New_Node,Colorado_Springs_CO,New_Sysop,-Unpublished-,9600 C3715 D2 C6579 D1 A1 ,440,Dragon_Sun_ip_only,Moscow,Vova_Golubkov,7-095-742-0534,300 C114 D1 A1 ,1014,Serpent_Station,Moscow,Andrew_Zharov,7-095-583-3258,300 C5533 D1 A1 Pvt,121,Atlantis_Point,Gisborne,Kristofer_Clayton,-Unpublished-,9600 C77 D1 A1 Region,88,FidoNet-Chile,Chile,Pedro_Aguilera,56-2-292-2093,9600,V32b,V42b,ZYX C227 D1 A1 ,17,DELUXE_BBS,Bahia_Blanca_BA,Christian_Mugione,54-291-42-9440,9600,V32b,V42b,XA C5 D1 A1 ,4,Soft_Code_BBS,Guadalajara_Jal,Juan_Jose_Rodriguez,52-3-647-5621,9600,CM,XA,V32B,V34,V42B,MNP10 C56 D2 A2 Host,7321,Uganda,Kampala,Charles_Musisi,256-41-532440,2400 ,1,Makerere_University,Kampala,Charles_Musisi,256-41-532440,2400 C79 D2 A2 ,113,OPUShelp_East,Bangkok_Thailand,David_Hanks,662-275-4966,9600,H16,V32B,V42B,CM ,262,R62_Echomail_Coord,Tainan_TAIWAN,Chinian_Wang,886-6-283-3337,9600,CM,XA,HST,V42b C38 D1 A1 Down,225,MAGIC's_32,SINGAPORE,Gary_Heng,65-2421133,2400 C32 D1 A1 ,405,PEACE,SINGAPORE,Edward_Han,65-2783734,9600,V32b,V42b,VFC,CM C38 D2 A2 Hub,700,Singapore_Hub_700,SINGAPORE,Kaven_Yeo,65-4552157,9600,V34,VFC,V32b,V42b,MNP,CM,XA ,701,SpaceCamp_BBS,SINGAPORE,Kaven_Yeo,65-4552157,9600,V34,VFC,V32b,V42b,MNP,CM,XA C1 D1 A1 ,709,Information_Server_Online_BBS,SINGAPORE,Tralvex_Yeap,65-2708066,9600,V32b,V42b,XA,CM C1 D1 A1 ,713,ACT_BBS,SINGAPORE,Alakappan_Chinniah,65-2892209,9600,V32B,V42B,VFC,MNP,XA,CM C26 D1 A1 ,20,CASS_Info_X-Press,MALAYSIA,Azman_Abdul_Aziz,60-3-7034336,9600 C4 D3 A3 Host,608,Thailand_Net,Bangkok_Thailand,David_Hanks,662-2754966,9600,V34,CM ,2,BUG_III,Bangkok_Thailand,John_Carls,662-381-3109,9600,V32B,CM ,3,CCAN,Bangkok_Thailand,Yongchai_Jerdampai,662-428-5615,9600,V32,CM C1 D5 A5 ,6,KITS_Pro,Bangkok_Thailand,Chawalit_Limsowan,662-331-8210,9600,V32B,CM ,7,Thesis_Maker,Chonburi_Thailand,Surakrai_Nikrothanonda,663-838-1725,9600,ZYX,V32B ,9,Scuba,Bangkok_Thailand,Napat_Kantanon,662-578-1018,9600,V32B ,10,SETA,Bangkok_Thailand,Phongpat_Greeprom,662-259-7526,9600,V32B ,11,Rosebud,Bangkok_Thailand,Craig_Emmott,662-555-1212,9600,V32B C1 D3 A3 ,18,Samart_BBS,Bangkok_Thailand,Samart_Siriangkana,662-389-5169,9600,V32B,CM ,20,Thai_info,Patum-thani_Thailand,Anote_Vachrapibool,662-997-7146,9600,32b,Z19 ,49,Casa_Guacamole,Bangkok_Thailand,David_Hanks,662-275-4966,9600,V34,CM C88 D1 A1 ,344,PSL#6_Touch_BBS,Tuen_Mun,Nobel_Man,852-2618-1945,9600 C2 D1 A1 ,351,CompuMark_BBS_#2,Sham_Shui_Po,Jack_Cheung,852-2788-4452,9600 C18 D1 A1 ,425,Lonely_BBS_#1,Shatin,Bowie_Chan,852-2608-1351,9600 C66 D1 A1 Down,758,Paramount_BBS,HO_MAN_TIN,SIMON_CHIU,852-2768-8397,9600 C443 D1 A1 ,502,Aladdint's_Lamp,ChungLi_Taiwan,Knight_Feng,886-3-436-6346,9600,V32b,V42_b,MNP,MO C375 D4 A4 ;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. C81 D1 A1 ;S | XX Argus 2.00 and higher | C41 D1 A1 ;S be strung together with no intervening commas, eg. C8 D1 A1 ;S flag any additional support to be arranged via agreement C13 A5 ;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. C1 D4 A4 ;S Conversion from old to new ISDN capability flags: ;S ISDNA -> V110L ;S ISDNB -> V110H ;S ISDNC -> X75 C1 D4 A1 ;S H: INTERNET CAPABILITY FLAGS: C1 D1 A1 ;S FLAG MEANING C1 D1 A22 ;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. C1 D22 A1 ;S Conversion from R46/R50 Internet capabilty flags to the new flags: C1 D1 A5 ;S BND -> IBN ;S TEL -> ITN ;S TELNET -> ITN ;S VMD -> IVM ;S TCP -> IP C1 D5 A9 ;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. C1 D1 A15 ;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 C1 D7 A2 ;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. C1 D5 A2 ;S Note: All IP nodes *must* have mailer capabilities. E-Mail/FTP etc. denote ;S supplemental capabilities only. C1 D2 A1 ;S I: SYSTEM ONLINE USERFLAGS C1 D1 A3 ;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): C1 D4 A8 ;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. C1 D2 A1 ;S For example TuB shows an online period from 20:30 until 1:00 UTC. C1 D2 A1 ;S Daylight saving time C1 D1 A14 ;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. C1 D3 A1 ;S J: BAUD RATES: C1 D8 A1 ;S The following baud rates are authorized for use in the nodelist: C1 D1 A1 ;S 300, 1200, 2400, 4800, 9600, 14400, 16800, 19200, 28800, 33600 C1 D1 A4 ;S ;S Userflags authorized for use in the nodelist ;S ------------ ;S A. FORMAT OF USER FLAGS C1 D14 A9 ;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. C1 D1 A7 ;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. C1 D1 A4 ;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. C1 D1 A3 ;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. C1 A3 ;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. C1 D3 A3 ;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. C1 D9 A3 ;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. C1 D7 C1 D4 A1 ;S SDS Software Distribution System C1 D3 A2 ;S SMH SecureMail Hub - or one of the following variations, ;S indicating the specific level of the hub: C1 D3 A4 ;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 C1 D3 A4 ;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. C1