;A Zone Nodelist for Friday, October 19, 2001 -- Day number 292 : 50302 ;A ;A Copyright 2001, Fidonet Philippines, All rights reserved. ;A ;A The FidoNet(r) NodeList, a listing of the systems within FidoNet. ;A ;A Copyright 1999, Fido Software. All rights reserved except for the following: ;A ;A o The FidoNet NodeList is compiled so that computer systems within FidoNet ;A may communicate with each other. Use and intra-FidoNet distribution ;A rights are granted to all FidoNet system operators for the purposes of ;A communication within FidoNet or applying for a FidoNet node number. ;A ;A o This is a compilation of individual nodelist segments contributed by the ;A drafters and compilers of those segments. Contribution of these segments ;A to this compilation does not diminish the rights of the contributors. ;A ;A Specific authority is hereby granted to FidoNet Coordinators to ;A process this list in any manner necessary to its inclusion in the ;A FidoNet Nodelist, provided only that it continues to be protected by ;A a compilation copyright in all composite lists. ;S ;S Fidonet Nodelist Segment - Philippine Segment Only ;S ;S Prepared By William Villanueva - Majesty BBS 6:751/2.0 Aka 6:64/0 ;S Regional Coordinator For the Philippines (Region 64) ;S ;S NOTICE -- NOTICE -- NOTICE -- NOTICE -- NOTICE -- NOTICE -- NOTICE ;S -------------------------------------------- ;S ;S Fidonet nodes are reminded that the current version of policy is ;S Version 4.07, published on June 9th, 1989. All aspects of Policy 4.07 ;S are now and shall remain in force until such time as a new policy is ;S ratified. ;S ;S Please check the END of the nodelist for additional technical information. ;S ;S This is Distribution Fidonet Nodelist containing Region 64 PHILIPPINES ;S Networks and Nodes only. ;S Those who do not wish to use the Worldwide Fidonet Nodelist or ;S the Zone 6 nodelist can use this R64-LIST.Znn . Just rename this file ;S to NODELIST.nnn . The n stands Day Number of the Year, every Friday. ;S ;S This nodelist should be made available to all sysops wishing to join ;S Fidonet International Philippines. ;S ;S This list is generated automatically and distributed every Friday of ;S each week to all Network Coordinators who are responsible for distribution ;S to Hub Coordinators and their downlinks. If you don't have the ;S current nodelist from your NC, it is available for FREQ at 6:64/0 with ;S the following magic names : ;S ;S NODELIST - For Latest Fidonet Worldwide Nodelist ;S R64-LIST - Fidonet RP Nodelist Segment (This File) ;S ;S The Regional Coordinator processes the nodelist every Thursday. ;S For any errors, ommisions, changes and updates regarding your ;S regarding your bbs information in the nodelist, please inform ;S the Regional Coordinator for Region 64 by netmail at 6:64/0 or ;S your Network or Hub Coordinator. ;S ;S Schedule For Processing And Submission of Nodelist Segments : ;S ;S Saturday - Hubs submit their nodelist segments to their ;S Network Coordinators. ;S International Nodediffs are released by RC64. ;S Tuesday - Network Coordinators submits nodelist segments to RC64. ;S Thursday - Processing of nodelist segments by RC64. ;S Friday - Region 64 nodelist segment is submitted to Zone 6 ;S Coordinator. Region 64 nodelist segments are released ;S via RP-SDS Tick System. Nodediffs are released either ;S Friday or Saturday. ;S ;S Route - Nodes => Hubs => NCs => RC64 => Z6C ;S ;S Nodes that are going to be down for several days should be ;S be marked "Down" in the nodelist entry. ;S Nodes that are down and plan to come back online should be ;S be marked "Hold" in the nodelist entry. ;S Nodelist compilation should produce no CRC errors. ;S If there are CRC errors, this means you are getting a modfified ;S nodelist and not the original distribution list. ;S ; Zone,6,ASIA,Shanghai,Bin_Li,86-21-6260-7052,9600,CM,XA,V32b,V42b ; Region,64,Philippines_Regional_Coordinator,PHILIPPINES,Terry_Roati,63-2-896-3116,9600,CM,XR,V32b,V42b,V34 ,5,CyberPhil_Gateway,Philippines,Peter_Que,63-2-361-3089,9600,XA,V32b,V42b,V34 ,750,N750_Echomail_Coordinator,Manila_Philippines,Peter_Que,63-2-361-3089,9600,XA,V32b,V42b,V34 ,751,N751_Echomail_Coordinator,Makati_Philippines,Terry_Roati,63-2-896-3116,9600,CM,XR,V32b,V42b,V34 ; Host,750,NORTHERN_METRO_MANILA_NET,Ermita_Manila,Peter_Que,63-2-361-3089,9600,XA,V32b,V42b Hub,100,WEST_MANILA_HUB,Ermita_Manila,Peter_Santiago,63-2-524-5116,9600,LO,XA,V32b,V42b ,101,PSInergy_BBS,Ermita_Philippines,Peter_Santiago,63-2-524-5116,9600,LO,XA,V32b,V42b,V34 Hub,200,EAST_MANILA,Quezon_City_Philippines,Patrick_Basister,63-2-940-4665,9600,XA,V32b,V42b,V34 ,223,The_Banker's_Council,Marikina_Philippines,Patrick_Basister,63-2-940-4665,9600,XA,V32b,V42b,V34 Hub,300,SOUTH_MANILA_HUB,Ermita_Manila,Peter_Que,63-2-896-3116,9600,XA,V32b,V42b,V34 Hub,400,KAMANAVA_HUB,Ermita_Manila,Peter_Que,63-2-361-3089,9600,XA,V32b,V42b,V34 ,402,Lighthouse,Malabon_Philippines,Peter_Que,63-2-361-3089,9600,XA,V32b,V42b,V34 ; Host,751,SOUTHERN_METRO_MANILA_NET,Makati_City_Philippines,Eddie_Salonga,63-2-578-8212,9600,CM,XR,V32b,V42b,V34 ,5,CyberPhil_Gateway,Malabon_Philippines,Peter_Que,63-2-361-3089,9600,XA,V32b,V42b,V34 ,12,The_Chili_Channel,Subic_Zambales_Philippines,Stewart_Buckingham,63-47-232-4463,9600,CM,XA,V32b,V42b,V34 ,15,The_SkyWalker's_Court,San_Fernando_Pampanga,Jun_Martin,63-45-963-2049,9600,XA,V32b,V42b Hub,100,PASIG_HUB,Pasig_Philippines,Eddie_Salonga,63-2-578-8212,9600,CM,XR,V32b,V42b,V34 ,111,LiveWire!_Node_1,Pasig_Philippines,Eddie_Salonga,63-2-578-8212,9600,CM,XR,V32b,V42b,V34 Hub,200,QUEZON_CITY_HUB,Quezon_City_Philippines,Eddie_Salonga,63-2-578-8212,9600,CM,XR,V32b,V42b,V34 Hub,300,MAKATI_CITY_HUB,Makati_Philippines,Terry_Roati,63-2-896-3116,9600,CM,XR,V32b,V42b,V34 ,301,The_File_Bank_BBS!_Node_2,Makati_City_Philippines,Terry_Roati,63-2-897-0009,9600,CM,XR,V32b,V42b,V34 ,321,The_File_Bank_BBS!_Node_1,Makati_City_Philippines,Terry_Roati,63-2-896-3116,9600,CM,XR,V32b,V42b,V34 ,333,AALGLATT/ZZ_DigItaL_UniVersE,Makati_Philippines,Jeremiah_A._Leviste,63-2-897-1872,9600,LO,XA,V32b,V42b,V34 Hub,400,DOWN_SOUTH_HUB,Las_Pinas_Philippines,Emerson_Balbin,63-2-803-4359,9600,CM,XR,V32b,V42b,V34 ,492,System_Online_Network,Las_Pinas_Philippines,Emerson_Balbin,63-2-803-4359,9600,CM,XA,V32b,V42b ; ;S Zone Mail Hour For Zone 6 Region 64 PHILIPPINES ;S ;S 04:00-05:00 Philippine Time (A.M.) ;S OR ;S 20:00-21:00 UTC/GMT ;S ;S ZMH shoudl be free from echomail processing and bbs callers. ;S ZMH Is Mandatory and should be reserved for netmail purposes only. ;S ;S The following flags define special operating conditions: ;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 ;S The following flags define modem protocols supported: ;S ;S Flag Meaning ;S ;S V21 CCITT V21 300 bps full duplex ;S V22 CCITT V22 1200 bps full duplex ;S V29 CCITT V29 9600 bps half duplex ;S V32 CCITT V32 9600 bps full duplex ;S V32b CCITT V32bis 14400 bps full duplex ;S V33 CCITT V33 ;S V34 CCITT V34 ;S V42b CCITT V42bis ;S H96 Hayes V9600 ;S HST USR HST up to 9600 BPS ;S H14 USR HST up to 14400 BPS ;S H16 USR HST up to 16800 BPS ;S MAX Microcom AX/96xx series ;S PEP Packet Ensemble Protocol ;S CSP Compucom Speedmodem ;S ZYX ZyXEL up to 14400 BPS ;S Z19 ZyXEL up to 19200 BPS ;S V32t AT&T/Phylon's "V.32terbo" ;S VFC Hayes/Rockwell's "V.Fast Class" ;S ;S NOTE: Many V22 modems also support Bell 212A. ;S ;S If no modem flag is given, Bell 212A is assumed for 1200 bps ;S systems, CCITT V22bis is assumed for 2400 bps systems. ;S ;S A separate modem capability flag should not be used when it can be ;S determined by the modem flag. For instance, a modem flag of HST ;S implies MNP. V32b implies V32 and V42b implies V42. MNP,HST and ;S H14,MNP and H16,MNP and V32,V32b and V42,V42b flag pairs are ;S unnecessary. H14 implies HST, H16 implies H14 and V42.Bis and Z19 ;S implies ZYX as well as V.42Bis. ;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 NOTE: The only compression method standard in ;S FidoNet is archiving, using the standard SEA ARC ;S format, with archive names defined by the ;S specification for ARCMail 0.6. The absence of the ;S MN flag indicates that ARCMail 0.6 compression is ;S supported by this node. ;S ;S The following flags indicate the types of file/update requests ;S supported. ;S ;S The following flags indicate the types of file/update requests ;S supported. ;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 The following software is qualified to use the specified ;S file request flag: ;S ;S |---------------------------------------| ;S | File Req Flag Software Package | ;S |---------------------------------------| ;S | XA Frontdoor <1.99b | ;S | Frontdoor 2.02+ | ;S | Dutchie 2.90c | ;S | Binkleyterm >2.1 | ;S | D'Bridge <1.3 | ;S | TIMS | ;S |---------------------------------------| ;S | XB Binkleyterm 2.0 | ;S | Dutchie 2.90b | ;S |---------------------------------------| ;S | XC Opus >1.03 | ;S |---------------------------------------| ;S | XP Seadog | ;S |---------------------------------------| ;S | XR Opus 1.03 | ;S | Platinum Xpress All | ;S |---------------------------------------| ;S | XW Fido >12M | ;S | Tabby | ;S |---------------------------------------| ;S | XX D'Bridge 1.30 | ;S | Frontdoor 1.99b | ;S |---------------------------------------| ;S | None QMM | ;S |---------------------------------------| ;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 'x..x' ;S are assigned by the FidoNet International ;S Coordinator. This flag is not authorized for use by ;S any node unless specifically authorized by the IC or ;S FidoNet Inter-Network Coordinator. Registered ;S domain gateways include: ;S uucp to be used only by nodes in a list of ;S authorized fidonet.org sites available at ;S 1:1/31. ;S ;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 (18:00 - 19: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 standard ;S within a node's zone should be given. Since ;S observance of mail hour within one's zone is ;S mandatory, it should not be indicated. ;S ;S There is also a user flag which defines user-specific values. If ;S present, this flag MUST be the last flag present in a nodelist entry. ;S For further technical details about this flag, consult FidoNet ;S Technical Standard document FTS-0005 which is available for file ;S request under that magic name from 6:6/0 and 6:720/303 outside of the ;S Zone Mail Hour (+/- 2 hours). ;S ;S NOTE: There are currently NO user flags authorised ;S for use in Zone 6. If you have questions concerning ;S the use of this flag, or wish to have such a flag ;S authorised for use in Zone 6, please contact the ;S Zone 6 Coordinator. ;S ;S The following flag defines user-specific values. If present, this ;S flag MUST be the last flag present in a nodelist entry. ;S ;S Flag Meaning ;S ;S Ux..x A user-specified string, which may contain any ;S alphanumeric character except blanks. This string ;S may contain one to thirty-two characters of ;S information that may be used to add user-defined ;S data to a specific nodelist entry. The character "U" ;S should NOT be repeated, eg, "UXXX,YYY" not "UXXX,UYYY". ;S ;S This flag is NOT to be used for advertisements, or ;S non-essential information. If you have questions ;S concerning the use of this flag, please contact your ;S Regional Coordinator, or request the file USERFLAG. ;