- Test - lists.nanog.org

CfP - ICANN DNSSEC and Security Workshop for ICANN76 Community Forum in Cancún
by Jacques Latour 29 Nov '22

29 Nov '22

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN76 Community Forum In cooperation with the ICANN Security and Stability Advisory Committee (SSAC), we are planning a DNSSEC and Security Workshop for the ICANN76 Community Forum being held as a hybrid meeting from 11-16 March 2023 in the Eastern Time Zone (GMT -5). This workshop date will be determined once ICANN creates a block schedule for us to follow; then we will be able to request a day and time. The DNSSEC and Security Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent sessions were held at the ICANN75 Annual General Meeting on Wednesday, 21 September 2022. The presentations and transcripts are available at https://75.schedule.icann.org/meetings/hvW7BbDtvbw4hoSTx, https://75.schedule.icann.org/meetings/WLtBZqEydncda7Dsr, and https://75.schedule.icann.org/meetings/8jcmXcKTEoPTr3NQw. The DNSSEC Workshop Program Committee is developing a program for the upcoming meeting. Proposals will be considered for the following topic areas and included if space permits. In addition, we welcome suggestions for additional topics either for inclusion in the ICANN75 workshop, or for consideration for future workshops. 1. Global DNSSEC Activities Panel For this panel, we are seeking participation from those who have been involved in DNSSEC deployment as well as from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment, including Root Key Signing Key (KSK) Rollover activities and plans. 2. DNSSEC Best Practice Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? * Do you still submit/accept DS records with Digest Type 1? * What is the best practice around key roll-overs? * What about Algorithm roll-overs? * Do you use and support DNSKEY Algorithms 13-16? * How often do you review your disaster recovery procedures? * Is there operational familiarity within your customer support teams? * What operational statistics have been gathered about DNSSEC? * Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? Activities and issues related to DNSSEC in the DNS Root Zone are also desired. 3. DNSSEC Deployment Challenges The program committee is seeking input from those that are interested in implementation of DNSSEC but have general or particular concerns with DNSSEC. In particular, we are seeking input from individuals that would be willing to participate in a panel that would discuss questions of the following nature: * Are there any policies directly or indirectly impeding your DNSSEC deployment? (RRR model, CDS/CDNSKEY automation) * What are your most significant concerns with DNSSEC, e.g., complexity, training, implementation, operation or something else? * What do you expect DNSSEC to do for you and what doesn't it do? * What do you see as the most important trade-offs with respect to doing or not doing DNSSEC? 4. Security Panel The program committee is looking for presentations on DNS, DNSSEC, routing and other topics that could impact the security and/or stability of the Internet. We are looking for presentations that cover implementation issues, challenges, opportunities and best practices for: * Emerging threats that could impact the security and/or stability of the Internet * DoH and DoT * RPKI (Resource Public Key Infrastructure) * BGP routing & secure implementations * MANRS ( Mutually Agreed Norms for Routing Security) * Browser security - DNS, DNSSEC, DoH * EMAIL & DNS related security - DMARC, DKIM, TLSA, etc... If you are interested in participating, please send a brief (1-3 sentence) description of your proposed presentation to dnssec-security-workshop(a)icann.org<mailto:dnssec-security-workshop@icann.org> by COB Friday, 20 January 2023. Thank you, Jacques On behalf of the DNSSEC Workshop Program Committee: Steve Crocker, Shinkuro Mark Elkins, DNS/ZACR Jacques Latour, .CA Russ Mundy, Parsons Ondrej Filip, CZ.NIC Yoshiro Yoneya, JPRS Fred Baker, ISC Dan York, Internet Society

1 0

Newbie Concern: (BGP) AS-Path Oscillation
by Pirawat WATANAPONGSE 28 Nov '22

28 Nov '22

Dear Guru(s), My apologies upfront if this question has already been asked. If that’s the case, please kindly point me to the solution|thread so that the mailing list bandwidth is not wasted. Situation: On one of our prefixes, we are detecting continuous “BGP AS-Path Changes” in the order of 1,000 announcements per hour---practically one every 3-4 seconds. Those paths oscillate between two of our immediate upstreams. Questions: 1. Is this number of events “normal” for a prefix? 2. Is there any way we, as the tail-end (Origin Announcer), can do to reduce it? Or should I just “let it be”? 3. [Extra] Is this kind of oscillation affecting user experience, say, throughput and/or latency? Thank you in advance for all the pointers and help. Best Regards, Pirawat.

4 3

MAP-T Implementation
by Will Duquette 28 Nov '22

28 Nov '22

Has anyone successfully deployed MAP-T? We are in the process of testing and have it working in our lab. We are running into an issue where the last half of the ipv4 prefix doesn't work. I.E. x.x.x.0/24 assigned x.x.x.0-127 works, x.x.x.128-255 does not. We are able to manipulate our DHCP config to allow for the handing out of IPv4 IP's. The CPE gets an IPV6 address and IPv6 only works, anything trying to be routed with an ipv4 address in the last half of the ipv4 prefix will not work. -Will

1 0

Fwd: [apops] APRICOT 2023 Call for Presentations
by Mark Tinka 26 Nov '22

26 Nov '22

FYI. Mark. -------- Forwarded Message -------- Subject: [apops] APRICOT 2023 Call for Presentations Date: Sat, 15 Oct 2022 20:03:11 +1000 From: Philip Smith <philip(a)apricot.net> Organization: Asia Pacific Regional Conference on Operational Technologies To: apops(a)apops.net Hi everyone, Forwarding the APRICOT 2023 call for presentations on behalf of the PC Chairs. Best wishes! philip -- APRICOT 2023 20th February - 2nd March, Manila, Philippines https://2023.apricot.net CALL FOR PRESENTATIONS ====================== The APRICOT 2023 Programme Committee is now seeking contributions for Presentations and Tutorials for the APRICOT 2023 Conference. We are looking for presenters who would: - Offer a technical tutorial on an appropriate topic; - Participate in the technical conference sessions as a speaker; - Convene and chair panel sessions of relevant topics; - Lead informal Birds of Feather break out sessions. Please submit on-line at: http://papers.apricot.net/user/login.php?event=161 CONFERENCE MILESTONES --------------------- Call for Papers Opens: Now Outline Programme Published: As Papers Confirmed Final Deadline for Submissions: 30th January 2023 Final Program Published: 6th February 2023 Final Slides Received: 20th February 2023 *SLOTS ARE FILLED ON A FIRST COME, FIRST SERVED BASIS, REGARDLESS OF PUBLISHED DEADLINES* PROGRAMME CONTENT ----------------- The APRICOT Conference Programme consists of three parts, these being Tutorials, the Peering Forum, and Conference Sessions. Topics proposed must be relevant to Internet Operations and Technologies, for example: - IPv4 / IPv6 Routing and Operations - Routing Security, including RPKI and MANRS - Internet backbone operations - Peering, Interconnects and IXPs - Content Distribution Network technology & operations - Chip shortages impact on equipment acquisition and operations - Research on Internet Operations and Deployment - Pandemic impact on network deployment and operations - Network Virtualisation - Network Automation/Programming - Network Infrastructure security - IPv6 deployment on fixed and Wireless/Cellular networks - DNS / DNSSEC and KINDNS - Access and Transport Technologies - Technical application of Web 3.0, public blockchains and cryptocurrency - Content & Service Delivery and "Cloud Computing" CfP SUBMISSION -------------- Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions otherwise the submission will be rejected immediately. For work in progress, the most current information available at time of submission is acceptable. All draft and complete slides must be submitted in PDF format only. Slides must be of original work, with all company confidential marks removed. Final slides are to be provided by the specified deadline for publication on the APRICOT website. Prospective presenters should note that the majority of speaking slots will be filled well before the final submission deadline. The PC may, at their discretion, retain a limited number of slots up to the final submission deadline for presentations that are exceptionally timely, important, or of critical operational importance. Every year we turn away submissions, due to filling up all available programme slots before the deadline. Presenters should endeavour to get material to the PC sooner rather than later. Any questions or concerns should be addressed to the Programme Committee Chairs by e-mail at: pc-chairs at apricot.net We look forward to receiving your presentation proposals. Mark Tinka & Marijana Novakovic APRICOT 2023 Programme Committee Chairs -- _______________________________________________ Go to the apops mailing list on Orbit -- orbit.apnic.net/mailing-list/apops@apops.net Explore orbit.apnic.net, where the APNIC community connect, discuss and share information related to Internet addressing and networking. To unsubscribe send an email to apops-leave(a)apops.net

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 25 Nov '22

25 Nov '22

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 TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net. For historical data, please see https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 26 Nov, 2022 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: 916410 Prefixes after maximum aggregation (per Origin AS): 346196 Deaggregation factor: 2.65 Unique aggregates announced (without unneeded subnets): 442878 Total ASes present in the Internet Routing Table: 73851 Prefixes per ASN: 12.41 Origin-only ASes present in the Internet Routing Table: 63411 Origin ASes announcing only one prefix: 26014 Transit ASes present in the Internet Routing Table: 10440 Transit-only ASes present in the Internet Routing Table: 416 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 991 Number of instances of unregistered ASNs: 998 Number of 32-bit ASNs allocated by the RIRs: 40721 Number of 32-bit ASNs visible in the Routing Table: 33758 Prefixes from 32-bit ASNs in the Routing Table: 164456 Number of bogon 32-bit ASNs visible in the Routing Table: 20 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 519 Number of addresses announced to Internet: 3063543424 Equivalent to 182 /8s, 153 /16s and 246 /24s Percentage of available address space announced: 82.7 Percentage of allocated address space announced: 82.7 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: 311115 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 239651 Total APNIC prefixes after maximum aggregation: 68233 APNIC Deaggregation factor: 3.51 Prefixes being announced from the APNIC address blocks: 234616 Unique aggregates announced from the APNIC address blocks: 97365 APNIC Region origin ASes present in the Internet Routing Table: 13129 APNIC Prefixes per ASN: 17.87 APNIC Region origin ASes announcing only one prefix: 3814 APNIC Region transit ASes present in the Internet Routing Table: 1756 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 31 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8380 Number of APNIC addresses announced to Internet: 773709568 Equivalent to 46 /8s, 29 /16s and 223 /24s APNIC AS Blocks 4608-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-151865 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: 267370 Total ARIN prefixes after maximum aggregation: 121947 ARIN Deaggregation factor: 2.19 Prefixes being announced from the ARIN address blocks: 268887 Unique aggregates announced from the ARIN address blocks: 129472 ARIN Region origin ASes present in the Internet Routing Table: 19076 ARIN Prefixes per ASN: 14.10 ARIN Region origin ASes announcing only one prefix: 6975 ARIN Region transit ASes present in the Internet Routing Table: 1934 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4685 Number of ARIN addresses announced to Internet: 1289378560 Equivalent to 76 /8s, 218 /16s and 91 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-401308 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 262443 Total RIPE prefixes after maximum aggregation: 121256 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 259105 Unique aggregates announced from the RIPE address blocks: 154703 RIPE Region origin ASes present in the Internet Routing Table: 28130 RIPE Prefixes per ASN: 9.21 RIPE Region origin ASes announcing only one prefix: 11967 RIPE Region transit ASes present in the Internet Routing Table: 3956 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10893 Number of RIPE addresses announced to Internet: 716124032 Equivalent to 42 /8s, 175 /16s and 47 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-213403 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 117281 Total LACNIC prefixes after maximum aggregation: 28363 LACNIC Deaggregation factor: 4.13 Prefixes being announced from the LACNIC address blocks: 116654 Unique aggregates announced from the LACNIC address blocks: 48886 LACNIC Region origin ASes present in the Internet Routing Table: 11006 LACNIC Prefixes per ASN: 10.60 LACNIC Region origin ASes announcing only one prefix: 2663 LACNIC Region transit ASes present in the Internet Routing Table: 2267 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8764 Number of LACNIC addresses announced to Internet: 175912448 Equivalent to 10 /8s, 124 /16s and 54 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 28674 Total AfriNIC prefixes after maximum aggregation: 5642 AfriNIC Deaggregation factor: 5.08 Prefixes being announced from the AfriNIC address blocks: 36629 Unique aggregates announced from the AfriNIC address blocks: 12024 AfriNIC Region origin ASes present in the Internet Routing Table: 1708 AfriNIC Prefixes per ASN: 21.45 AfriNIC Region origin ASes announcing only one prefix: 595 AfriNIC Region transit ASes present in the Internet Routing Table: 329 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 37 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1036 Number of AfriNIC addresses announced to Internet: 108127744 Equivalent to 6 /8s, 113 /16s and 230 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/8, 45/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 9808 9139 8884 50 CHINAMOBILE-CN China Mobile Communicati 7545 5948 786 695 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4880 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3624 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3515 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3365 1867 82 VNPT-AS-VN VNPT Corp, VN 9498 2543 499 237 BBIL-AP BHARTI Airtel Ltd., IN 4766 2536 11252 601 KIXS-AS-KR Korea Telecom, KR 24560 2301 849 417 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2180 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 7661 10622 2886 AMAZON-02, US 11492 4579 303 539 CABLEONE, US 7155 3966 265 32 VIASAT-SP-BACKBONE, US 22773 3729 3061 327 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3588 1879 2570 AKAMAI-AS, US 6327 3524 1320 63 SHAW, CA 749 3065 50661 2332 DNIC-AS-00749, US 30036 2589 369 312 MEDIACOM-ENTERPRISE-BUSINESS, US 7018 2585 24059 1552 ATT-INTERNET4, US 396982 2564 3482 359 GOOGLE-CLOUD-PLATFORM, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 6952 1730 145 UNI2-AS, ES 9121 6401 1692 17 TTNET, TR 20940 4107 3400 183 AKAMAI-ASN1, NL 39891 4010 234 47 ALJAWWALSTC-AS, SA 8551 3979 374 38 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2950 2290 912 ROSTELECOM-AS, RU 9009 2647 253 1361 M247, RO 47331 2548 377 1923 TTNET, TR 34984 2246 357 610 TELLCOM-AS, TR 6849 2194 339 20 UKRTELNET, UA Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10889 3350 600 Uninet S.A. de C.V., MX 10620 3455 506 852 Telmex Colombia S.A., CO 11830 2301 369 64 Instituto Costarricense de Electricidad 13999 2125 348 550 Mega Cable, S.A. de C.V., MX 28573 1336 2327 262 Claro NXT Telecomunicacoes Ltda, BR 6503 1293 338 521 Axtel, S.A.B. de C.V., MX 3816 1287 728 154 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11664 1131 183 478 Techtel LMDS Comunicaciones Interactiva 6147 1087 369 22 Telefonica del Peru S.A.A., PE 26615 988 2466 43 TIM SA, BR Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24835 1545 537 31 RAYA-AS, EG 24863 1539 393 21 LINKdotNET-AS, EG 36992 1356 1520 269 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1011 67 40 ORANGE-COTE-IVOIRE, CI 36935 879 520 42 Vodafone-, EG 6713 613 1863 34 IAM-AS, MA 15399 530 54 45 WANANCHI-, KE 37342 441 32 1 MOVITEL, MZ 23889 400 231 14 MauritiusTelecom, MU Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10889 3350 600 Uninet S.A. de C.V., MX 9808 9139 8884 50 CHINAMOBILE-CN China Mobile Communicati 16509 7661 10622 2886 AMAZON-02, US 12479 6952 1730 145 UNI2-AS, ES 9121 6401 1692 17 TTNET, TR 7545 5948 786 695 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4880 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4579 303 539 CABLEONE, US 20940 4107 3400 183 AKAMAI-ASN1, NL 39891 4010 234 47 ALJAWWALSTC-AS, SA Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9139 9089 CHINAMOBILE-CN China Mobile Communications Grou 12479 6952 6807 UNI2-AS, ES 9121 6401 6384 TTNET, TR 7545 5948 5253 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4880 4805 ERX-CERNET-BKB China Education and Research Net 16509 7661 4775 AMAZON-02, US 11492 4579 4040 CABLEONE, US 39891 4010 3963 ALJAWWALSTC-AS, SA 8551 3979 3941 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7155 3966 3934 VIASAT-SP-BACKBONE, US Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 65000 PRIVATE 2.92.64.0/20 8371 VIMPELCOM-NN Vimpelcom, Nizh 65000 PRIVATE 2.92.80.0/20 8371 VIMPELCOM-NN Vimpelcom, Nizh 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 16641 UNALLOCATED 8.10.194.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.10.210.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.12.76.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.12.250.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.14.115.0/24 3356 LEVEL3, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.131.184.0/24 Origin: 174 COGENT-174, US 23.131.184.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.185.0/24 Origin: 174 COGENT-174, US 23.131.185.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.186.0/24 Origin: 174 COGENT-174, US 23.131.186.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.187.0/24 Origin: 174 COGENT-174, US 23.131.187.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.188.0/24 Origin: 46450 PILOT, US 23.131.188.0/24 Transit: 1299 TWELVE99 Arelion, fka Telia Carrier, SE Complete listing at https://thyme.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:13 /10:39 /11:100 /12:295 /13:587 /14:1201 /15:2045 /16:13523 /17:8317 /18:13914 /19:25200 /20:44361 /21:52438 /22:110265 /23:97998 /24:545272 /25:826 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 5983 6952 UNI2-AS, ES 9121 5553 6401 TTNET, TR 8151 4834 10889 Uninet S.A. de C.V., MX 11492 3485 4579 CABLEONE, US 8551 3443 3979 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3332 3524 SHAW, CA 39891 3193 4010 ALJAWWALSTC-AS, SA 7155 3055 3966 VIASAT-SP-BACKBONE, US 22773 2752 3729 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2247 2589 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1870 2:1029 3:166 4:5 5:4046 6:117 7:5 8:1585 9:1 11:173 12:1617 13:380 14:2377 15:287 16:72 17:366 18:386 20:239 21:4 22:188 23:6020 24:2465 25:6 27:2701 29:19 31:2483 32:98 34:8 35:94 36:1806 37:4544 38:3870 39:770 40:144 41:3951 42:1195 43:2303 44:303 45:16369 46:4144 47:379 49:1716 50:1933 51:244 52:1506 54:398 55:798 56:8 57:78 58:1797 59:1157 60:1005 61:2428 62:2564 63:1953 64:5649 65:2339 66:4851 67:3003 68:1381 69:4178 70:1293 71:688 72:2999 74:2645 75:1472 76:600 77:2253 78:3964 79:3155 80:2043 81:1830 82:1500 83:1220 84:1511 85:3752 86:745 87:1929 88:2842 89:3483 90:573 91:7614 92:1991 93:2573 94:3543 95:4827 96:1338 97:348 98:1174 99:740 100:69 101:1055 102:2455 103:30537 104:4555 105:477 106:828 107:2532 108:919 109:4280 110:2016 111:3318 112:2039 113:1571 114:1613 115:2073 116:1908 117:2468 118:2335 119:1871 120:1726 121:1112 122:2600 123:2137 124:1577 125:2200 128:1260 129:979 130:972 131:2024 132:842 133:401 134:1914 135:295 136:880 137:910 138:2542 139:1521 140:1049 141:1482 142:1417 143:1408 144:1200 145:352 146:1896 147:1511 148:2273 149:1846 150:866 151:1145 152:1836 153:456 154:3807 155:1387 156:1633 157:1290 158:1041 159:2241 160:2571 161:1424 162:3518 163:1455 164:1673 165:1641 166:843 167:1718 168:3863 169:918 170:4553 171:867 172:3517 173:3113 174:1032 175:1170 176:3629 177:4782 178:3551 179:2140 180:2359 181:3341 182:3240 183:1921 184:2356 185:19942 186:4611 187:3953 188:4034 189:3445 190:9052 191:1459 192:10995 193:8771 194:7192 195:5078 196:2995 197:2421 198:6009 199:6097 200:7648 201:5832 202:10595 203:10089 204:4602 205:3458 206:3836 207:3400 208:4108 209:4808 210:4420 211:2442 212:4035 213:3520 214:1104 215:57 216:6554 217:2613 218:1289 219:575 220:2048 221:953 222:837 223:2037 End of report

1 0

ingress/egress 9/8 gov.xxx.ticket; was: Re: pls pls me 80/81...
by AQ Glass 24 Nov '22

24 Nov '22

anybody interested in this project? @oracle can own the .ticket tld; NS * ticket. -> virtualhost 96hr netflow + tech/biz/admin for adnetworks to reg their new xxx. with gov.xxx.ticket signup and further instructions // https://twitter.com/element9v/status/1579552246911885312?t=NdYwACGQsPkg0o0s… codedevs can commit to https://github.com/element9v/takebackdarpa thx -e On Thu, Nov 17, 2022, 3:50 PM AQ Glass <element9v(a)gmail.com> wrote: > > https://twitter.com/element9v/status/1592162934658334720?t=f1cpwD_kr3wwIVln… > > #routetonull discuss > > #takebackdarpa > > -e >

3 3

Happy Thanksgiving! Betty Burke Tribute Video + OARC Event
by Nanog News 23 Nov '22

23 Nov '22

*Happy Thanksgiving * *We are Grateful for Community Members Like You! * *NANOG truly takes a village, and we wouldn't be here without members like you. * Thank you for your support in building the Internet of Tomorrow. We wish you and yours a very Happy Thanksgiving. *VIDEO - In Memory of Betty Burke* *A Tribute to Former NANOG Executive Director* *NANOG would not be what it is today without the leadership of Betty Burke.* We have included a tribute video to honor her service and enormous contribution. Our Community Memorial <https://community.nanog.org/t/betty-burke-feb-6-1955-nov-7-2022/56596>can be accessed by anyone with a free account on NANOG's website. *WATCH NOW * <https://www.nanog.org/stories/in-memory-of-betty-burke/> *OARC 40 in Co-Location with NANOG 87 * *The Workshop Will be Held in Atlanta - 16, 17 Feb. 2023* DNS-OARC is a non-profit membership organization that seeks to improve the security, stability, and understanding of the Internet's DNS infrastructure. *OARC 40 will be held after the NANOG 87 conference. REGISTER NOW <https://indico.dns-oarc.net/event/46/>*

1 0

BCP38 For BGP Customers
by Charles Rumford 22 Nov '22

22 Nov '22

Hello - I'm are currently working on getting BCP38 filtering in place for our BGP customers. My current plan is to use the Juniper uRPF feature to filter out spoofed traffic based on the routing table. The mentality would be: "If you don't send us the prefix, then we don't accept the traffic". This has raised some issues amongst our network engineers regarding multi-homed customers. One of the issues raised was if a multi-homed BGP customer revoked a prefix from one of their peerings, but continued sending us traffic on the link then we would drop the traffic. I would like to hear what others are doing for BCP38 deployments for BGP customers. Are you taking the stance of "if you don't send us the prefix, then we don't accept the traffic"? Are you putting in some kind of fall back filter in based on something like IRR data? Thanks! -- Charles Rumford (he/his/him) Network Engineer | Deft 1-312-268-9342 | charlesr(a)deft.com deft.com

17 28

SPF (and other email security protocols) Survey
by Taejoong (tijay) Chung 21 Nov '22

21 Nov '22

Greetings, The Sender Policy Framework (SPF) is an easy way to check whether the sender is authorized to send emails – however, it may cause some security holes if it causes too many DNS lookups. Together with researchers from Virginia Tech and Max-Planck-Institut für Informatik, we would like to understand which challenges operators face when configuring the proper limit of DNS queries for SPF lookups and when deploying other email security protocols. Filling out the survey should take between 5 and 10 minutes; we would highly appreciate your participation. https://www.surveymonkey.com/r/D9M3ZHV Please note that we do NOT collect any personal information, thus the Institutional Review Board (IRB) at Virginia Tech determined the survey as Non-Human Subjects Research. We will aggregate and anonymize all responses during evaluation and share the results after evaluation. Please do not hesitate to drop me a mail if you have questions or comments. Also, please excuse us if you have received this email from different mailing lists. Thank you. Taejoong "Tijay" Chung, Assistant Professor Virginia Tech | Computer Science Knowledge Works II, RM 2228 2202 Kraft Drive, Blacksburg, VA 24060 (540) 231-0667| tijay(a)vt.edu

1 0

Random shower thought: GBIC with LC connector...
by Warren Kumari 18 Nov '22

18 Nov '22

Hi there all, While looking through my big box of random optics I suddenly realized that I'd never seen a GBIC with an LC connector, and I started wondering if anyone else had / if such a thing actually exists. Yes, I realize that this would be a fairly niche device - if you arrived somewhere with a device that took GBICs and there was existing fiber with LC connectors you could just replace the patch cable or use an LC-SC convertor, but that doesn't really satisfy my curiosity. A quick look through the GBIC MSA / SFF documentation implies that such a thing *could* probably exist (there is a defined value for the 'LC' connector), but I wasn't able to actually find any. It might not actually be compliant with the specs (the document I found only lists SC fiber or copper (coax with BNC, TNC or DB-9?!)), but that doesn't mean that no-one made them. So, has anyone seen a regular (30mm/1.2") GBIC with LC connectors? And, if so, "pics or it didn't happen"... :-) Obviously I don't have an actual use for this, it's just to satisfy my (OCD) curiosity... W

12 13