Re: Outside plant - prewire customer demarc preference
Thanks Brandon Martin, I agree 1-inch smurf tube is overkill for FTTH. From my quick research into all things FTTH, which I didn't know anything a week ago :-) ... The regulators in other countries still believe they will create competition. The 25mm/32mm access duct (I'm going to make up a new term, and just call it "access duct", i.e. that smurf tube, conduit, pathway thing) is big enough for either a fiber microduct, cat 6 copper or RG6 coax. Even a 12/24/48-volt DC power cable for active equipment at the NID/demarc. The regulators keep all their competitors happy by not favoring any particular technology. In practice, the countries with the biggest FTTH deployments have very little FTTH competition at the physical access layer. Microduct, microduct, microduct is what the dominant access provider wants in those countries. The dominant carrier wants builders to install "direct fiber" or "bypass fiber" microducts in new construction directly from every dwelling (house or apartment) to the carrier's central access point for the builder's development (apartment buildings or neighborhood). Microduct only means no pre-built access for other competitors. Apartment construction in Asia is very large. Several countries are also adding in-building mobile/wireless service requirements for new MDU building construction. My interpretation, not understanding the country-specific FTTH fights... The regulators appear to say, Ok, dominant carrier - you can have "direct fiber" microduct but builders must also provide an "open competition" 25mm/32mm access duct from the building entrance point (NID) or apartment consolidation points (CP) to the individual distribution box (DD) inside each dwelling. Just my uninformed take, corrections welcome.
Weekly Global IPv4 Routing Table Report
This is an automated weekly mailing describing the state of the Global IPv4 Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG UKNOF, TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-st...@lists.apnic.net. For historical data, please see https://thyme.apnic.net. If you have any comments please contact Philip Smith . IPv4 Routing Table Report 04:00 +10GMT Sat 25 Nov, 2023 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary BGP routing table entries examined: 935642 Prefixes after maximum aggregation (per Origin AS): 356140 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 454675 Total ASes present in the Internet Routing Table: 75088 Prefixes per ASN: 12.46 Origin-only ASes present in the Internet Routing Table: 64431 Origin ASes announcing only one prefix: 26523 Transit ASes present in the Internet Routing Table: 10657 Transit-only ASes present in the Internet Routing Table:478 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 1036 Number of instances of unregistered ASNs: 1038 Number of 32-bit ASNs allocated by the RIRs: 43101 Number of 32-bit ASNs visible in the Routing Table: 35439 Prefixes from 32-bit ASNs in the Routing Table: 178053 Number of bogon 32-bit ASNs visible in the Routing Table:29 Special use prefixes present in the Routing Table:1 Prefixes being announced from unallocated address space:525 Number of addresses announced to Internet: 3049330944 Equivalent to 181 /8s, 193 /16s and 25 /24s Percentage of available address space announced: 82.4 Percentage of allocated address space announced: 82.4 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 310583 APNIC Region Analysis Summary - Prefixes being announced by APNIC Region ASes: 249008 Total APNIC prefixes after maximum aggregation: 71753 APNIC Deaggregation factor:3.47 Prefixes being announced from the APNIC address blocks: 242249 Unique aggregates announced from the APNIC address blocks:99279 APNIC Region origin ASes present in the Internet Routing Table: 13790 APNIC Prefixes per ASN: 17.57 APNIC Region origin ASes announcing only one prefix: 4151 APNIC Region transit ASes present in the Internet Routing Table: 1859 Average APNIC Region AS path length visible:4.4 Max APNIC Region AS path length visible: 32 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9120 Number of APNIC addresses announced to Internet: 771834752 Equivalent to 46 /8s, 1 /16s and 67 /24s APNIC AS Blocks4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-153913 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary Prefixes being announced by ARIN Region ASes:273658 Total ARIN prefixes after maximum aggregation: 124133 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 278450 Unique aggregates announced from the ARIN address blocks:132343 ARIN Region origin ASes present in the Internet Routing Table:19075 ARIN Prefixes per ASN:
Re: Outside plant - prewire customer demarc preference
Sorry long, detailed message. TL;DR - Use 1-inch trade size smurf tube for new North America FTTH construction. North American FTTH may not have standards for the in-building access conduit between the demarc point, Minimum Point of Entry (MPOE) in the old terminology, and the dwelling's distribution point. But thanks to Christopher Hawker for pointing me to other country's national broadband deployment guidance. In the US, we don't even have a consistent word to describe that line on the network drawings. That line seems to be an "out of scope" gap between the the FCC demarc rules and TIA inside wiring standards. Other countries with strong FTTH deployments have written a lot of rules about that line. Germany has extremely detailed FTTH building standards which influenced other European country FTTH standards. Carriers in several Middle East and other Commonwealth countries with national FTTH deployments have lots of documents for new builders. Bear with me, because I'm going to translate nominal metric measurements and translate country-specific "pre-wire" rules using North American terms. Conduit, tube, pathway generally mean the same thing to me, but some people have been annoyed because their country uses different words. Most FTTH countries specify a nominal 25mm I.D./32mm O.D. (equivalent to 1-inch US trade size) conduit/duct/pathway between the "dwelling" Distribution Point and the NID/demarc entrance point for new construction. In multi-dwelling unit buildings (i.e. apartments) the 25mm/32mm duct is between the apartment and a "consolidation point" for a group of apartments or the floor. Mansions (palaces) and other building types specify larger access conduit sizes. Countries vary a little, i.e. UK and Ireland have the smallest minimum access duct size (20mm I.D./25 mm O.D.) and some Middle Eastern countries have the largest (40mm ID/50 mm OD). Australia is just weird with a Telstra legacy conduit size. Overall 25mm ID/32mm OD (equivalent 1-inch trade size) is the most common. The biggest difference between country's FTTH rules are rigid vs. flexible conduit and the material specified, i.e. schedule 40 PVC vs. HDPE vs. other. Also very confusing because the metric "Diametre nominel" size for pipes/conduit isn't the actual size of the conduits in metric measurements. 25mm is really 26.64mm inside diameter. Likewise the American National Pipe Standard isn't the actual measurement either. American 1-inch trade size is 1.029" inside diameter. The convention metric countries uses for 32mm outside diameter is really 33.40 mm. Confused yet? Google translate does not help with construction codes. The good news for North America construction, a 1-inch trade size HDPE/Schedule 40 PVC or smurf tube/duct/conduit/pathway requires drilling a 1-3/8 inch hole through framing studs. A 1-3/8 hole is just smaller than the maximum sized hole size allowed in a standard 2x4 framing stud (which isn't actually 2-inches by 4-inches) by North American building codes. So the builder does not need to charge extra to 'double' the framing studs for 'structural integrity' according to the building code. Builder's scare quotes are intentional. Insert NSFW construction joke here :-) Mine (and my friend who will own the the new house) assumption is the builder's proposed $1,000 charge is really a "stop listening to your crazy friend, and let me build your house" charge.
Re: CPE/NID options
I don't know about specific SKUs, but IP Infusion make a very popular set of L2 switches. On Wed, Nov 22, 2023 at 8:42 PM Ross Tajvar wrote: > I'm evaluating CPEs for one of my clients, a regional ISP. Currently, > we're terminating the customer's service (L3) on our upstream equipment and > extending it over our own fiber to the customer's premise, where it lands > in a Juniper EX2200 or EX2300. > > At a previous job, I used Accedian's ANTs on the customer prem side. I > like the ANT because it has a small footprint with only 2 ports, it's > passively cooled, it's very simple to operate, it's controlled centrally, > etc. Unfortunately, when I reached out to Accedian, they insisted that the > controller (which is required) started at $30k, which is a non-starter for > us. > > I'm not aware of any other products like this. Does anyone have a > recommendation for a simple L2* device to deploy to customer premises? Not > necessarily the exact same thing, but something similarly-featured would be > ideal. > > *I'm not sure if the ANT is exactly "layer 2", but I don't know what else > to call it. >
